Adding P6 Enterprise Data Fields - 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

By default, the P6 Connector import jobs have been configured without including P6 Enterprise Data fields, such as Project Codes, Activity Codes, or User Defined Fields. This applies to jobs such as WBS, Activity, or Forecast imports.

Example

The following example demonstrates the procedure to add a P6 Activity Code, called "Item", to the "P6 Activity to Task Import".

To perform the steps below, you must have the basic knowledge of EcoSys Connect development.

  1. Add the "Item" Activity Code to the master data import.

    This is accomplished by adding the intended Task Category to the EcoSys Connect Global Settings list. This will add the new field to the "P6 Activity Code to Task Category" import. For more information, see EcoSys Connect Global Settings under Connect List Properties.

  2. Run the "P6 Activity Code to Task Category" import job to import the P6 Activity Code records to the EcoSys Task Category.

  3. Modify the EcoSys API for importing Activities to add the new "P6 Item" Category field.

  4. Add the "P6 Item (External Key)". The External Key is used as a mapping to the P6 Activity Code ObjectId. After the EcoSys spreadsheet is saved, the API schema will be updated with the new field.

  5. In EcoSys Connect, go to Repository screen and re-save the repository for the "EcoSys P6 Activity Import" API.

    This will update the schema within Connect so the new field is available.

  6. Edit the Connect Job, "P6 Activity to Task Import" to add the Activity Code field.

  7. At the step after the P6 Activities are read, add a "P6 Join" processor. The Join processor will read the P6 Activity Codes and join to the Activity record set.

  8. Add a SOAP Reader within the Join processor. For the Connector, select "P6 Activity Code Assignment", and the Operation for "ReadActivityCodeAssignments".

  9. In the Step Inputs of the Reader, add fields for "Activity Code Object Id" and "Activity Object Id"

  10. Set the filter field to the same value as the previous step to read Activities and add a filter for ActivityCodeTypeName=’Item’.

    For example, ActivityCodeTypeName='Item' and ProjectObjectId='$__CTX(ProjectObjectId)' and WBSObjectId!='$__CTX(ProjectWBSObjectId)'

  11. In the Join Processor step, set the Input Key Attribute field to "objectId" and the Reader Key Attribute field to "activityObjectId". Also, in the Advanced section, enable the checkbox for Left Join.

  12. Map the new Activity Code value to the EcoSys API. This is done by mapping the P6 activityCodeObjectId to the EcoSys p6ItemExternalKey field.

  13. Save the Job.

    You can now run the job from EcoSys and it will import the new P6 Activity Code on the EcoSys Activity import.