When defining data load mapping details, you can define the data to extract, including whether or not to extract:
The amount type—Only monetary, statistical, or both, monetary and statistical amounts
Zero balance accounts where the debits and credits for an account total zero
Adjustment periods—Determines whether to extract balances in the adjustment period
Standard or Average balances—Average balances only contain balance sheet data.
Source balance type—Actual, Budget, or Encumbrance
In ERP Integrator you classify the data that you want to transfer with the valid types in the source accounting entity of Actual, Budget, and Encumbrance. Typically, you do not map a segment from the chart of accounts to the Scenario dimension, so you choose a default member as part of the data rule definition. When the data is extracted, it is defined with the Scenario column defined in accordance with the default selected.
You can extract only functional balances, which are stored in the base currency of the selected ledger or business unit. For example, if transactions are entered in multiple currencies, the total of all transaction balances is expressed in the functional currency.
To define the data load source filter for Fusion and E-Business Suite source systems:
Monetary
Statistical—The balance selection of entered or functional currency does not apply.
Monetary and Statistical
In the *Include Zero Balance drop-down, select whether to include zero balances.
Select Yes to extract zero balances. If you select No, accounts with zero balances are not extracted.
Select the Amount for Balance Sheet Accounts and Amount for Income Statement Accounts:
YTD—Year-to-date account balance, where account balances are accumulated from the beginning of the year to the current period. Typically, balance sheet accounts (assets, liabilities, and equities) are specified with a YTD balance. (The default is YTD.)
Periodic—Account balance for the specific period. Typically, income statement accounts (revenues and expenses) are specified with a periodic balance. (The default is PTD.)
Standard—In Oracle General Ledger, accounting transaction balances are stored as-is, also known as standard balances.
Average—Average balances only contain balance sheet data. If you selected Statistical as the amount type, the Balance Method is ignored.
Select the balance type to extract:
Actual
Budget—If you select the Budget source balance type, click Add to select budget types to include in the extraction.
Encumbrance—If you select the Encumbrance source balance type, click Add to select encumbrance types to include in the extraction.
Select the segment values to extract.
If you do not want to extract all data from the source general ledger, filter data by the balancing segments of the source. Options include:
All
Selected
In Oracle E-Business Suite, the balancing segment ensures that at this level, balancing debits equal credits. When you create a data load rule, you can decide whether to extract the general ledger balances relating to all the members of the balancing segment or for specific members of it.
To select the balancing segment values, click
, and then select segment values and click OK.To deselect a value, click
, and then in the Select Balancing Segment Values dialog box, clear any values and click OK.
Select the Beginning, Ending, and Average exchange rate options.
ERP source systems maintain comprehensive exchange rate information for transaction processing. This information can be used by the target applications by extracting the exchange rates. You can select a beginning, ending, and average rate type from the source system. (The types in the source system may not explicitly define those rates types but are mapped to the rates types in the ERP Integrator interface table.)
Note:
For Planning applications, exchange rates are loaded only if the “Classic” data load method is selected.
Note:
You define exchange rate options only if the target application is multi-currency.
Define the target filter options.
After you define the target filter options, run the data rule. See Running the Data Load .