the primavera p6 eps activity code is great when we want to have a set of activity codes available to certain projects based on where they sit in your eps structure. an example might be having a set of activity codes for each department in your database. typically, eps nodes would be set up for each department, allowing an organization to specific a set of eps activity codes for each department that are only available to their projects.
many organizations setup and use primavera’s eps activity codes as a means to establish standardized codes for groups of projects.
but what happens if we want to move the project to another eps node and need to preserve the coding? what if the eps activity codes don’t exist at the project’s new eps node? will we have to redo all of that coding inside the project? and what happens if we need to export the project to another database? will the coding come along?
fortunately, there is a way to preserve the coding in both of these situations. it is possible to convert an eps activity code to a project-level activity code in primavera p6 allowing you to preserve your coding when moving or exporting a project. here’s how:
step 1 – eps activity code setup
assuming we’ve got an eps activity code set up like so:
step 2 – open the project
open the project that uses the eps activity code.
step 3 – copy and move
copy the project and paste it to an eps node where the eps activity codes do not exist. you’ll see a message like this one.
to preserve the eps coding, primavera p6 will copy the eps activity code to a project activity code to be stored inside the project and the coding assignments will stay put.
if it makes sense, move the copied project back the original eps node. you can chose to keep or delete the original project – it’s up to you. and now you can also export the project with the coding intact.
was this tip helpful? leave us a comment and have your say.
