Adding or Editing Field Mapping Templates

Field mapping templates are used by master data and project data business flows to transfer data between any two applications supported by Primavera Gateway.

A field mapping template contains a list of business objects and fields that are to be transferred from the source application to the destination application. It also contains information on how each source business object and a destination business object is mapped with a corresponding Gateway business object. The field-mapping templates determine how a Gateway object, and the corresponding provider object with its supported fields are used in a business flow.

A business flow is a combination of a specific set of field mapping templates that fulfill a data transfer requirement. To create a business flow that processes specific data between any two applications, appropriate field-mapping templates must be created and included in a business flow to support data transfer in a business flow.

Gateway delivers field-mapping templates for Gateway objects that can be used in business flows. Alternatively, you can also create additional field-mapping templates to suit your requirements.

Note: Field-mapping templates can be created using Groovy code or the canonical format (Direct) format of Gateway.

To add or edit field mapping templates:

  1. In the sidebar, select Configuration and then select the Field Mapping Templates tab.
  2. Select a Gateway business object from the drop-down.

    All field-mapping templates associated with the Gateway business object display in the field-mapping template table.

  3. To add a field-mapping template, select Add....

    or

    In the Field Mapping Name column, select a field mapping template and then select Edit....

  4. In the General step:
    1. In the Template Name field, enter a name for the field mapping template.

      This is the only field that can be changed if you choose to edit a field mapping template.

    2. Select the type of template being created from the Template Type list.
      • Select Groovy if the template will use Groovy code.
      • Select Direct if the template will use the canonical format of Gateway.
    3. Select a provider from the Provider 1 list.
    4. Select a provider from the Provider 2 list.
    5. Select the object to be supported by the field mapping template from the Provider 1 Object list.
    6. Select the object to be supported by the field mapping template from the Provider 2 Object list.
    7. (Optional) Select Use Criteria Step to set a specific condition to filter data within the field-mapping template.

      Note: Select Next on each screen to advance to the next step.

  5. In the Criteria step, specify the condition for field mappings:
    1. Select the field from the Fields list of Provider 1.
    2. Select the field from the Fields list of Provider 2.
    3. Enter the Conditions to be satisfied by Provider1 and Provider 2 fields respectively.
    4. Select Validate Condition to validate the syntax entered in the Condition text box for the provider fields.
  6. In the Mappings step, specify field mappings supported by the template:
    1. Select Auto Generate to generate mappings for fields that are common to both providers and Gateway.

      For identical fields existing in both providers and Gateway, field mapping names are auto-suggested and populated for each provider.

    2. Specify additional field mappings as follows:
      1. Select the fields supported by the template in the list of both providers, and Gateway.
      2. Select Add.
      3. Repeat Step b to add multiple fields.
  7. In the Summary step:
    1. Review all the selections made in the previous steps.
    2. Select any of the following actions:
      • Select Back to navigate to a specific step and make changes.
      • Select Save to add the field-mapping template.

        Note: Multiple provider objects can be mapped to a single provider object. For example, when you select Sample as Provider 1 and P6 as Provider 2, both objects in the Sample provider, WorkOrder and WBS, map to the WBS object in P6 EPPM.



Legal Notices | Your Privacy Rights
Copyright © 2016, 2021

Last Published Tuesday, October 12, 2021