Example of a Mapping Set to Override the Account from Subledger Accounting, General Ledger, and Manual Joint Venture Source Transactions

This is an example of a mapping set for overriding the account from subledger accounting, general ledger, and manual transactions. The purpose of the mapping set is to replace the natural account segment in the account from the transaction.

The following image shows the Create Mapping Set page with a Receivables mapping set named "JV Reimbursement Partner Accounts for SLA GL Manual Transactions” and its short name and description. The output type is "Segment" and the subledger application is automatically set to “Receivables."

This image shows the Create Mapping Set page for a Receivables mapping set, the details of which are described in the surrounding text.

The next image shows the Input Sources, Chart of Accounts, and HEPPLedger: Mappings sections. The Input Sources section includes these inputs: Transaction Source Name, Transaction Line Flexfield Attribute 2, and Transaction Line Flexfield Attribute 4. In the Chart of Accounts section, HEPPLedger is selected for the chart of accounts and HEPPAccount is selected for the segment. The Mappings section includes three columns in this order for the inputs: Transaction Source Name, Transaction Line Flexfield Attribute 2, and Transaction Line Flexfield Attribute 4. The next column is an Output column named HEPPAccount which is followed by the Effective Start Date column. There are three rows for mapping inputs to the output. Row 1 inputs are Oracle Joint Ventures, 1001, and E in the respective input columns, with 49001 in the output column. Row 2 inputs are Oracle Joint Ventures, 1001, and A in the respective input columns, with 49002 in the output column. Row 3 inputs are Oracle Joint Ventures, 1001, and S, with 49006 in the output column.

This image shows the Input Sources, Chart of Accounts, and HEPPLedger: Mappings sections and the values in each section, which are described in surrounding text.