Expenses - EcoSys - Help - Hexagon PPM

EcoSys Primavera P6 Adapter Help

Language
English
Product
EcoSys
Search by Category
Help
EcoSys Version
8.7
  • Create field maps for importing P6 project field values. The syntax is:

    import.actual.expense.ProjectUDFMap.Count=[Total fields]
    import.actual.expense.ProjectUDFMap.[#]=[API Project Field Name]|[FM UDF Type Name]
    import.forecast.expense.ProjectUDFMap.Count=[Total fields]
    import.forecast.expense.ProjectUDFMap.[#]=[API Project Field Name]|[FM UDF Type Name]

Make sure the Count matches number of field maps.

Example: (for forecast and actuals)

import.actual.expense.ProjectUDFMap.Count=4
import.actual.expense.ProjectUDFMap.1=ObjectId|PROJECT_ID
import.actual.expense.ProjectUDFMap.2=Id|PROJ_SHORT_NAME
import.actual.expense.ProjectUDFMap.3=Name|PROJ_NAME
import.actual.expense.ProjectUDFMap.4=Status|PROJ_STATUS_CODE

 

import.forecast.expense.ProjectUDFMap.Count=4
import.forecast.expense.ProjectUDFMap.1=ObjectId|PROJECT_ID
import.forecast.expense.ProjectUDFMap.2=Id|PROJ_SHORT_NAME
import.forecast.expense.ProjectUDFMap.3=Name|PROJ_NAME
import.forecast.expense.ProjectUDFMap.4=Status|PROJ_STATUS_CODE

  • Create field maps for importing P6 WBS field values. The syntax is:

    import.actual.expense.WBSUDFMap.Count=[Total fields]
    import.actual.expense.WBSUDFMap.[#]=[API WBS Field Name]|[FM UDF Type Name]
    import.forecast.expense.WBSUDFMap.Count=[Total fields]
    import.forecast.expense.WBSUDFMap.[#]=[API WBS Field Name]|[FM UDF Type Name]

    Make sure the Count matches number of field maps.

    Example: (for forecast and actuals)

    import.actual.expense.WBSUDFMap.Count=2
    import.actual.expense.WBSUDFMap.1=Status|STATUS_CODE
    import.actual.expense.WBSUDFMap.2=WBSCategoryObjectId|PHASE_ID

     

    import.forecast.expense.WBSUDFMap.Count=2
    import.forecast.expense.WBSUDFMap.1=Status|STATUS_CODE
    import.forecast.expense.WBSUDFMap.2=WBSCategoryObjectId|PHASE_ID

  • Create field maps for importing P6 Activity field values. The syntax is:

    import.actual.expense.ActivityUDFMap.Count=[Total fields]
    import.actual.expense.ActivityUDFMap.[#]=[API Activity Field Name]|[FM UDF Type Name]
    import.forecast.expense.ActivityUDFMap.Count=[Total fields]
    import.forecast.expense.ActivityUDFMap.[#]=[API Activity Field Name]|[FM UDF Type Name]

Make sure the Count matches number of field maps.

Example: (for forecast and actuals)

import.actual.expense.ActivityUDFMap.Count=8
import.actual.expense.ActivityUDFMap.1=ObjectId|TASK_ID
import.actual.expense.ActivityUDFMap.2=Id|TASK_CODE
import.actual.expense.ActivityUDFMap.3=Name|TASK_NAME
import.actual.expense.ActivityUDFMap.4=PlannedStartDate|TARGET_START_DATE
import.actual.expense.ActivityUDFMap.5=PlannedFinishDate|TARGET_END_DATE
import.actual.expense.ActivityUDFMap.6=WBSObjectId|WBS_ID
import.actual.expense.ActivityUDFMap.7=WBSCode|WBS_SHORT_NAME
import.actual.expense.ActivityUDFMap.8=WBSName|WBS_NAME

 

import.forecast.expense.ActivityUDFMap.Count=8
import.forecast.expense.ActivityUDFMap.1=ObjectId|TASK_ID
import.forecast.expense.ActivityUDFMap.2=Id|TASK_CODE
import.forecast.expense.ActivityUDFMap.3=Name|TASK_NAME
import.forecast.expense.ActivityUDFMap.4=PlannedStartDate|TARGET_START_DATE
import.forecast.expense.ActivityUDFMap.5=PlannedFinishDate|TARGET_END_DATE
import.forecast.expense.ActivityUDFMap.6=WBSObjectId|WBS_ID
import.forecast.expense.ActivityUDFMap.7=WBSCode|WBS_SHORT_NAME
import.forecast.expense.ActivityUDFMap.8=WBSName|WBS_NAME

  • Create Field maps for importing P6 Expense field values. The syntax is:

    import.actual.expense.UDFMap.Count=[Total fields]
    import.actual.expense.UDFMap.[#]=[API Assignment Field Name]|[FM UDF Type Name]
    import.forecast.expense.UDFMap.Count=[Total fields]
    import.forecast.expense.UDFMap.[#]=[API Assignment Field Name]|[FM UDF Type Name]

Make sure the Count matches number of field maps.

Example: (for forecast and actuals)

import.actual.expense.UDFMap.Count=1
import.actual.expense.UDFMap.1=PlannedCost|BUDGET_AMT

 

import.forecast.expense.UDFMap.Count=1
import.forecast.expense.UDFMap.1=PlannedCost|BUDGET_AMT

  • Importing P6 UDFs

User-defined fields may be imported into EcoSys custom fields.The following conditions apply:

  • The custom fields must first be created in EcoSys.

  • The EcoSys custom fields must be configured within the subject area in which the data is to be imported. An activity level P6 UDF will be imported to an EcoSys transaction level custom field. Configure the EcoSys custom field to the Working Forecast (or Actual) Transaction subject area.

  • The EcoSys custom field must be of the same data type as the P6 UDF (for example date>date, number>number, and so forth).

  • Designate that the field to be imported is a UDF in P6 by prefixing the name of the field with UDF:

Example:

import.forecast.expense.ActivityUDFMap.Count=1

import.forecast.expense.ActivityUDFMap.1=UDF:ActText2|TEXT2

The bold text is the UDF syntax that imports activity level UDF values for the field ActText2 to an EcoSys custom field called TEXT2 (for forecast expense assignments).

The count indicates the total of number of maps to use and must be equal to or less than the number of maps listed under. For example, if you set count = 1, then only the first map is used be used. Likewise, if count = 0, then no fields are imported as transaction custom fields.

 When importing activities with resource assignments:

import.forecast.assignment.ActivityUDFMap.1=UDF:ActText1|TEXT1