This section explains how to create mappings for additional fields including activity-level data for import into EcoSys. These are advanced import settings that cannot be configured within the application, and require additions to the Server Settings file.
You can import the following:
-
Project ID
-
Project Name
-
Project Status
-
WBS ID
-
WBS Name
-
Activity ID
-
Activity Name
-
Planned Start (activity OR resource assignment )
-
Planned Finish (activity OR resource assignment)
-
Resource ID
-
Resource Name
-
Planned/Budgeted Cost (resource assignment OR expense)
-
Actual Start (activity OR resource assignment)
-
Actual Finish (activity OR resource assignment)
To import this data, you must first define Custom Fields (also called UDFs) in EcoSys.
The following table lists the Custom Field types that should be created, and the data type.
|
EcoSys UDF Type |
EcoSys UDF Data Type |
EcoSys UDF Type |
EcoSys UDF Data Type |
|---|---|---|---|
|
PROJECT_ID |
Text |
TASK_NAME |
Text |
|
PROJ_SHORT_NAME |
Text |
TARGET_START_DATE |
Date |
|
PROJ_NAME |
Text |
TARGET_END_DATE |
Date |
|
PROJ_STATUS_CODE |
Text |
TASKRSRC_ID |
Text |
|
WBS_ID |
Text |
RSRC_ID |
Text |
|
WBS_SHORT_NAME |
Text |
EST_START_DATE |
Date |
|
WBS_NAME |
Text |
EST_END_DATE |
Date |
|
PHASE_ID |
Text |
BUDGET_AMT |
Money |
|
STATUS_CODE |
Text |
ACT_START_DATE |
Date |
|
TASK_ID |
Text |
ACT_END_DATE |
Date |
|
TASK_CODE |
Text |
You can import Primavera Project, WBS, Activity, Assignment and Expense fields into Transaction Custom Fields. You must first create the Custom Fields in EcoSys. Sample syntax and code is included for both resource assignments and expenses.
The import of P6 UDFs into EcoSys custom fields is also support. Information about this functionality is included at
the end of this appendix.