Project/WBS Key Mappings - EcoSys - Help - Hexagon PPM

EcoSys SAP Adapter Help

Language
English (United States)
Product
EcoSys
Search by Category
Help
EcoSys Version
8.8

EcoSys cost objects map to the following types of objects in SAP. These mappings are done by assigning the Cost Object External Key ID in EcoSys to match the value of the individual element in SAP.

  • Projects

  • WBS elements

  • Networks

  • Network Activities

  • Activity Elements

  • Work Orders

  • SAP projects having more than one root WBS element are not supported for export from EcoSys to SAP. The interface can import multi-root projects from SAP to EcoSys, but bi-directional synchronization is not supported for projects with more than one root WBS element.

  • When exporting cost objects created in EcoSys, you must pay special attention to external key IDs. The first time that you export WBS cost objects created from EcoSys to SAP system, the external key ID field must be populated in EcoSys. However, the first time that you export Network Headers and Network activities created in EcoSys, the external key ID fields must to be empty. Most configurations in SAP create their own Network Header IDs. Consequently, the first time that you export network headers and activities, the export operation creates the headers in SAP. The export operation then reads the newly created network header IDs, and then updates them automatically in EcoSys.

General Case (WBS and Project have different identifiers in SAP)

  • The root cost object in EcoSys must have its cost object ID mapped to the SAP project element ID.

  • Each cost object in EcoSys must have its cost object external key ID mapped to the SAP WBS element ID.

Special Case (SAP project ID and root WBS ID are the same value)

Sometimes the SAP project ID and SAP root WBS ID have the same value but map to different cost objects in EcoSys. In this cases only, you should add a PRJ prefix to the external cost object key ID of the root cost object in EcoSys to make it distinct from the root WBS value. The following table specifies the situations in which the PRJ prefix is recommended.

Project Node

Root WBS Node

EcoSys

Configure as: Root Cost Object

Cost Object ID: N-P0001

External key ID: PRJ N-P0001 (match WBS)

Configure as: Level 1 Cost Object *

Cost Object ID: N-P0001

External key ID: N-P0001

SAP

Configure as: Project Element

Element ID: N-P0001

Configure as: WBS Element

Element ID: N-P0001

* Because only one root WBS element can exist in SAP, only one level-1 cost object can exist in EcoSys.