Adding Custom Mappings

SRP enables you to create custom field-level mappings for each integration flow. This is useful when you want to:

In either case, you must create a new mapping. If a mapping for the target field already exists, it is overridden.

The sections below provide more information about the supported mapping types and basic examples with steps on how to create mappings.

Supported Mapping Types

SRP supports the following mapping types:

Notes:

Relationship path mappings from the source object are not supported in SRP Fall 2021. For example, from the Billing Event object, you cannot map the name of the region of the related project to a field on the Sales Invoice object. To achieve this, you must create a formula field on the Billing Event object and map it to the field on the Sales Invoice.

Name to lookup mappings are also not supported in Fall 2021. For example, your regions might have the same names as your dimension 1 records and you might have a formula field on the Billing Event object that retrieves the name of the related region. You cannot map the formula field from the Billing Event to Dimension 1 on the Sales Invoice. As a workaround, you can create a Dimension 1 lookup on the Region object, populate the value for all the regions and update the formula field to retrieve the ID of the dimension 1 record related to the region. You can then map formula field to Dimension 1 on the Sales Invoice.

Examples

The following examples provide steps for creating different types of mappings supported by SRP. For a full list of the options available in the FDN Mappings Lightning component, see Adding Custom Mappings from the FDN Mappings Component in the Foundations Help.

Note:

When creating a mapping, only the fields that you have access to are displayed. If a field is not displayed, ensure that you have access to it.

This example demonstrates how to map a custom formula field on the Billing Event object to the Dimension 1 lookup field on the Sales Invoice object. The formula fields retrieves the ID of the dimension 1 record linked to the region of the billing event. The region and the billing event are linked through a project record. For this example, we assume that you have already done the following:

  • Created a Dimension 1 lookup field on the Region object.
  • Populated the Dimension 1 lookup field on the relevant region records.
  • Created a formula field named Dimension 1 ID on the Billing Event object with the following formula: pse__Project__r.pse__Region__r.Dimension_1__r.Id.

For more information about this scenario and similar scenarios, see Configuring Dimension and Analysis Fields in SRP.

To create the mapping:

  1. Open the mappings for the Billing Event to Sales Invoice flow. For more information, see Viewing Mappings.
  2. Click Add Mapping.
  3. Set the following values:
    • Source Type: "Field"
    • Source Field Path: Dimension 1 ID
    • Target Type: "Field"
    • Target Field: Dimension 1
  4. Click Save.

This example demonstrates how to map the Project lookup field from the Vendor Invoice Item object to the Project lookup field on the Payable Invoice Expense Line Item object.

To create the mapping:

  1. Open the mappings for the Vendor Invoice to Payable Invoice flow. For more information, see Viewing Mappings.
  2. In the row with the source of pse__Vendor_Invoice_Items__r and target of c2g__PurchaseInvoiceExpenseLineItems__r, click Down icon. and then click Add Child Mapping.
  3. Set the following values:
    • Source Type: "Field"
    • Source Field Path: Project
    • Target Type: "Field"
    • Target Field: Project
  4. Click Save.

This example demonstrates how to map the Project lookup field from the Miscellaneous Adjustment object to the Project lookup field on the Journal Line Item object.

To create the mappings:

  1. Open the mappings for the Miscellaneous Adjustment to Journal flow. For more information, see Viewing Mappings.
  2. In the row with the source of Miscellaneous Adjustment and target of c2g__JournalLineItems__r, click Down icon. and then click Add Child Mapping.
  3. Set the following values:
    • Source Type: "Field"
    • Source Field Path: Project
    • Target Type: "Field"
    • Target Child Type: Default
    • Target Field: Project
  4. Click Save & New. This saves the mapping for the default journal line item and enables you to create an additional mapping for the balancing line item.
  5. Set the following values:
    • Source Type: "Field"
    • Source Field Path: Project
    • Target Type: "Field"
    • Target Child Type: Balancing
    • Target Field: Project
  6. Click Save. This saves the mapping for the balancing journal line item.

When you create a billable miscellaneous adjustment from a payable invoice expense line item, you might want to ensure that it can be included in the billing process. You can achieve this by creating static mappings for the Payable Invoice Expense Line to Miscellaneous Adjustment Recharge Customer flow. This example demonstrates how to map a static value of true to the Approved for Billing and Include in Financials checkbox fields on the Miscellaneous Adjustment object.

To create the mappings:

  1. Open the mappings for the Payable Invoice Expense Line to Miscellaneous Adjustment Recharge Customer flow. For more information, see Viewing Mappings.
  2. Click Add Mapping.
  3. Set the following values:
    • Source Type: "Static"
    • Source Description: Approved for Billing = true
    • Source Data: true
    • Target Type: "Field"
    • Target Field: Approved for Billing
  4. Click Save & New.
  5. Set the following values:
    • Source Type: "Static"
    • Source Description: Include in Financials = true
    • Source Data: true
    • Target Type: "Field"
    • Target Field: Include In Financials
  6. Click Save.