A direct field mapping template defines a series of simple one-to-one field mapping for one object. The integration product that is built on Primavera Gateway should come with a list of direct field mapping templates already, but you can add more if this becomes necessary. Here is an example from the customization.xml in the sample customization project that maps the CostCode field of the Activity business object and the TotalPlannedCost field of the Project business object:
<FieldMapTemplates>
<App1Name>Sample</App1Name>
<App2Name>P6</App2Name>
<FieldMapTemplate>
<Description>Cost code mapping for activity object</Description>
<App1BusinessObjectName>Operation</App1BusinessObjectName>
<Name>Activity Cost Code Mapping</Name>
<PDIBusinessObjectName>Activity</PDIBusinessObjectName>
<FieldMap>
<App1>SampleCostCode</App1>
<App2>CostCode</App2>
<PDI>CostCode</PDI>
</FieldMap>
</FieldMapTemplate>
<FieldMapTemplate>
<Description>Total planned cost for project object</Description>
<Name>Project Customization Mapping</Name>
<PDIBusinessObjectName>Project</PDIBusinessObjectName>
<FieldMap>
<App1>TotalPlannedCost</App1>
<App2>TotalPlannedCost</App2>
<PDI>TotalPlannedCost</PDI>
</FieldMap>
</FieldMapTemplate>
</FieldMapTemplates>
Legal Notices
Copyright © 2013, 2015,
Oracle and/or its affiliates. All rights reserved.
Last Published Wednesday, March 25, 2015