Example of a Mapping Set to Override the Source Transaction Account

This is an example of a mapping set that replaces the natural account segment value in joint venture payables invoices that are associated with the payment of revenue. You can use this as an example to override any segment of the account.

Mapping sets map a combination of input source values to specific output values. You specify which input values to use through reference keys that are preconfigured with joint venture attributes for payables invoices. You can also use the Payables Invoice Transaction Source “ORA_AP_JV” as an input value to restrict the mapping to only joint venture payables invoices.

In this example, “Invoices” is selected for the event class.

The following example shows the Edit Mapping Set page for a mapping set named "Joint Venture Payables Expense Account - Invoice" with "Segment" for the Output Type. The input sources selected for the mapping set are Invoice Source and AIL_REFERENCE_KEY4. HEPPLedger is specified as the chart of accounts that includes the natural account that will override the original natural account.

The following image shows the Mappings section with values entered for the input and output sources. The two input columns named Invoice Source and AIL_REFERENCE_KEY4 are mapped to the values ORA_AP_JV and EAGLEFORD respectively. The output column named HEPPAccount is mapped to the account 56666. This means that all payables invoices created for the joint venture EAGLEFORD will be recorded in the natural account 56666.