What is a Primavera P6 Project Code?

Project Code is a hierarchical element; A Project code must have one code Name and one or more code values. The purpose of the P6 Project Code is to distinguish the projects.

For example, An organization like L&T can have many projects around the world. In this case, I want to identify total budget allocated to the projects running in each country. To get this, I need to group the projects by country wise and read the cost information in EPS summaries.

In another use case, I want to identify total budget allocated to HYDRO & THERMAL projects running in each country. The use cases might differ project to project. The question is how to achieve this in Primavera P6 EPPM?

In the above two situations, P6 needs COUNTRY_LOCATION field contains a list of countries and PROJECT_TYPE, and PROJECT_TYPE field contains HYDRO & THERMAL values. Now we can associate a location and project_type to a project

The Out of box fields comes with P6 does not have any of the custom values. P6 provides a feature ‘Project Codes’ to solve this feature. If your application has LIST OF PRE_DEFINED VALUES available (Ex: Country: Country names) then create it in Project codes and associate it with the project. The project codes are suitable only for you have pre-defined values available. If don’t have one then consider Project UDF.

Using Project Code:

Group the project by P6 Project code

Filter the project by Project code

Identify the project field values that not come with Out Of box

Create a Portfolio by filter by Project code values

Filter the dashboard by project code value

Run a custom report by project code values

Much more……

Below is the how Primavera P6 Project code & values look like:

The root level is Project Code Name and all its children are project code values.

Thank you for visiting my personal blog. Myself Govindan, Software Developer by profession since 2006 and hence I started this blog early in 2016 and ever since I've been writing about technologies experienced and learnings of everyday life.

The views expressed on this blog are my personal views and do not necessarily reflect the views of my employer.

Please feeling free to reach me on any comments and feedbacks you have. Would be more than glad to listen and reply 🙂