Refer to the Planning Locations section for assistance with determining the Locations required. To configure Locations:
-
Click the Location link located within the Setup section on the Tasks navigator.
-
Click the Add button.
-
Provide a Name for the Location. In general, it is good practice to include in the Location name descriptive information about the source system from which balances are obtained and the ARM Process for which Profiles will be mapped. The Location name is visible in ARM and can be used to initiate specific data loads. Therefore, having a descriptive name will be helpful. For example:
-
EBS_GL_BSProcess (Oracle EBS general ledger balances for the Balance Sheet Reconciliation Process)
-
EBS_GL_ConsolProcess (Oracle EBS general ledger balances for the Consolidation System Reconciliation Process)
-
EBS_AP_BSProcess (Oracle EBS Accounts Payable subledger balances for the Balance Sheet Reconciliation Process)
-
Select the Import Format that should be used when importing balances from this Location. Recall that the Import Format determines which information is extracted from the source system and how it is stored in the ERPi staging table.
-
Functional Currency: If the Location pertains to a Source System of “Flat File” and the file does not contain a currency code column (because all balances in the file pertain to a single currency), then the currency must be specified in the Functional Currency column. If applicable, enter the 3 digit ISO currency code associated with the balances in the file. Refer to Appendix 2 for the list of supported currencies.
-
Press the Save button.
Note that Accounting Entity typically should be left blank. When configuring the Data Load Rules associated with the Location, an Accounting Entity or Entity Group can be assigned to each Data Load Rule, enabling a single Location to be used for importing balances from more than one Accounting Entity. If an Accounting Entity is specified at the Location level, then the Location can only be used for importing balances from this single Accounting Entity.
5.10Configure Data Load Rules
Data Load Rules determine which records (rows) are extracted from the source system, including which balance types are selected (Entered/Functional), whether zero balances are included, and whether currency rates are imported along with the balances (for ERP sources only).
For each Location, one Data Load rule must be configured for each currency bucket for which balances are imported. For example, if Location A contains ledgers from which Entered and Functional currency balances are required to be imported, then two Data Load Rules will exist for this Location: one for importing Entered currency balances, and one for importing Functional currency balances. Which bucket is enabled for each reconciliation is controlled by settings within ARM.
To configure Data Load Rules:
-
Click the link located within the Data Load section on the Tasks navigator.
-
Select a Location by clicking the Search Location icon. After selecting a Location, the Target should display “Account Reconciliation Manager”. Period and Category may contain values; these can be ignored. These are default values that are ignored by ARM when data loads are run.
-
Click the Add button in the Data Rule Summary section to add a Data Load Rule.
5.10.1Configuring Data Load Rules for ERP Sources
If the Location references an ERP source system, perform the following procedures:
-
In the Details section:
-
Name: Provide a Name for the Data Load Rule. In general, it is good practice to include in the Data Load Rule name descriptive information about the source system from which balances are obtained and the currency bucket to be assigned to the balances.
-
Category: Select the currency bucket to be assigned to the balances from the Category selection.
-
Include Adjustment Periods: If Adjustment periods should be included, select Yes. Otherwise, select No.
-
Period Mapping Type: Select Default to use the Application Mapping settings in the Period Mapping configuration. If period Source Mappings were configured for this source system, select Explicit.
5.10.1.1EBS, Fusion, & SAP source systems
If the Source system is EBS, Fusion, or SAP:
-
In the Source Filters section:
-
Amount Type: Select “Monetary”.
-
Include Zero Balance: Select “Yes”.
-
Amount for Balance Sheet Accounts: Select “YTD”.
-
Amount for Income Statement Accounts: Select “YTD”.
-
Currency Type: Select the value that corresponds with the currency bucket to be assigned in this Data Load Rule (per the Category value selected in the Details section).
-
Select “Entered” if Category = Entered (or its equivalent in ARM)
-
Select “Functional” if Category = Functional (or its equivalent in ARM)
-
Select “Translated/Group” if Category = Reporting (or its equivalent in ARM)
-
Currency Code should be left blank, if the objective is to import all balances from the Location. If a value were provided here, it would limit the balances imported to those that contained a matching currency code.
-
Balance Method: Select “Standard”.
-
Exchange Rate Options: Select the same currency rate that is used to revalue period-end balances in the source system.
-
Click the Save button.
5.10.1.2PeopleSoft source system
If the source system is PeopleSoft:
-
In the Source Filters section:
-
Amount Type: Select “Monetary”.
-
Amount for Balance Sheet Accounts: Select “YTD”.
-
Amount for Income Statement Accounts: Select “YTD”.
-
Currency Type: Select the value that corresponds with the currency bucket to be assigned in this Data Load Rule (per the Category value selected in the Details section).
-
If the ledgers associated with this Data Load Rule are the primary (not translated) ledgers, then Entered and Functional currency types are typically mapped to the Entered and Functional currency buckets within ARM:
-
Select “Entered” if Category = Entered (or its equivalent in ARM)
-
Select “Functional” if Category = Functional (or its equivalent in ARM)
-
If the ledgers associated with this Data Load Rule are translated ledgers, then the Entered currency type is not mapped since it was already mapped from the primary ledger. The Functional currency bucket (containing the translated balances) is mapped to the Reporting currency bucket in ARM:
-
Select “Functional” if Category = Reporting (or its equivalent in ARM)
-
Ledger Group: Select the appropriate Ledger Group.
-
Ledger: Select the appropriate Ledger.
-
Exchange Rate Options: Select the same currency rate that is used to revalue period-end balances in the source system.
-
Click the Save button.
5.10.2Configuring Data Load Rules for File-Based Data Loads
If the Location references a file, perform the following procedures:
-
In the Details section:
-
Name: Provide a Name for the Data Load Rule. In general, it is good practice to include in the Data Load Rule name descriptive information about the source system from which balances are obtained and the currency bucket to be assigned to the balances.
-
Category: Select the currency bucket to be assigned to the balances from the Category selection.
-
File Name: Provide the static name of the file (the part of the name that will not change from period to period).
-
File Name Suffix Type: If a suffix will be appended to the file name each period, then choose one of the following two options (refer to the File Naming Convention section for a discussion about using file suffixes):
-
Period Key: If this option is chosen, then the value appended to the file must exactly match the Period Key value associated with the Application Mapping in the Period Mapping configuration.
-
Period Description: If this option is chosen, then the value appended to the file must exactly match the Period Name value associated with the Application Mapping in the Period Mapping configuration.
-
Period Key Date Format: If Period Key is chosen as the File Name Suffix Type, then specify the format for the provided date. Format must be specified using the symbols in the table below. For example, consider the following format variations for July 1, 2012:
-
MM-dd-yyyy (07-01-2012)
-
MMM-d-yy (Jul-1-12)
-
Symbol
|
Meaning
|
Examples
|
M
|
Month
|
M 7
MM 07
MMM Jul
MMMM July
Note the “M” must be capitalized.
|
d
|
Day
|
d 1
dd 01
MMM Jul
Note the “d” must be lower case.
|
y
|
Year
|
yy 12
yyyy 2012
Note the “y” must be lower case.
|
Share with your friends: |
