Field Mappings - EcoSys - 1.0.01 - Help - Hexagon PPM

Integrating EcoSys with P6 Connector

Language
English
Product
EcoSys
Search by Category
Help
EcoSys Version
1.0.01

In general, the Forecast and Baseline imports follow the same business logic. However, there is one key difference in how the transactions map to the EcoSys Cost Object structure. Since the Forecast import is reading data directly from the P6 Project, it is possible to map the P6 WBS Object ID field to the Cost Object External Key, as is done in most other P6 Connector interfaces.

For the Baseline Import it is not possible to use the WBS Object ID since the P6 creates a completely new copy of all Project records for the Baseline which also creates new Object ID’s. In addition, it could be possible that the Project diverges somewhat from the original Baseline, such as creating new WBS that didn’t exist when the Baseline was created. For this reason, the mapping for Baseline data is done by the WBS Hierarchy Path ID.

There are small differences in the field mapping for Forecast and Baseline imports so separate field mapping tables are provided for both interfaces.

Forecast Import Field Mapping

EcoSys

P6 Resource Assignment

P6 Expense

Cost Object (External Key)

WBS Object Id

WBS Object Id

P6 Activity (External Key)

Activity Object Id

Activity Object Id

Transaction Cost

Remaining Cost

Remaining Cost

Units

Remaining Units

Remaining Units

Transaction Date

Spread Start Date

Depending on Accrual Type, Activity Start Date, Finish Date or spread evenly between Start and Finish Date

Resource (External Key)

Resource Object Id

N/A

P6 Role (External Key)

Role Object Id

N/A

P6 Cost Account (External Key)

Cost Account Object Id

Cost Account Object Id

Description

N/A

Expense Item

P6 Accrual Type (ID)

"Resource Spread"

Start of Activity, End of Activity, Uniform Over Activity

P6 Transaction Type (ID)

"Resource Assignment"

"Expense"

Baseline Import Field Mapping

EcoSys

P6 Resource Assignment

P6 Expense

Cost Object Hierarchy Path ID

Calculated based on the WBS parent/child relationship

Calculated based on the WBS parent/child relationship

P6 Activity Hierarchy Path ID

Calculated based on the WBS parent/child relationship, plus Activity ID

Calculated based on the WBS parent/child relationship, plus Activity ID

Transaction Cost

Planned Cost

Planned Cost

Units

Planned Units

Planned Units

Transaction Date

Spread Start Date

Depending on Accrual Type, Activity Start Date, Finish Date or spread evenly between Start and Finish Date

Resource (External Key)

Resource Object Id

N/A

P6 Role (External Key)

Role Object Id

N/A

P6 Cost Account (External Key)

Cost Account Object Id

Cost Account Object Id

Description

N/A

Expense Item

P6 Accrual Type (ID)

"Resource Spread"

Start of Activity, End of Activity, Uniform Over Activity

P6 Transaction Type (ID)

"Resource Assignment"

"Expense"