This job will import P6 Projects and WBS to EcoSys. This requires that the EcoSys and P6 Projects have already been mapped in the Project Setup process, see Map an existing EcoSys Project to a P6 Project. This jobs performs the following functions:
-
Update the EcoSys Project record
-
Create or Update P6 WBS to EcoSys Cost Objects
The P6 WBS and EcoSys Cost Object are mapped by assigning the P6 Object Id to the EcoSys WBS Cost Object External Key field.
-
Connect Job: P6 Project and WBS Import
-
EcoSys Action: ITG P6 Project WBS Import
At the WBS level, Structure Type category will be set to “PRJ” if the Scheduler Method is “External Schedule 1:1 WBS”. If the Scheduler Method is “External Schedule WBS Mapping”, then it will be “SCH”.
Field Mappings
The following table shows the field mapping for the Project update part of the job:
|
EcoSys Field |
EcoSys Subject Area |
P6 Field |
|---|---|---|
|
Cost Object ID |
Cost Object |
N/A |
|
Cost Object Name |
Cost Object |
Project Name |
|
P6 Project Status (ID) |
Cost Object Category |
Project Status |
|
P6 Project (ID) |
Cost Object Category |
Project Id |
|
P6 Object Id |
Custom Field (Text) |
Project Object Id |
The following table shows the field mapping for the WBS create/update part of the job:
|
EcoSys Field |
EcoSys Subject Area |
P6 Field |
|---|---|---|
|
Cost Object ID |
Cost Object |
WBS Code |
|
Cost Object Name |
Cost Object |
WBS Name |
|
Hierarchy Path ID |
Cost Object |
Calculated based on the WBS parent/child relationship |
|
External Key |
Cost Object |
WBS Object Id |