Implementation Toolkit Financial Close Management
Download 186.56 Kb.
|
- Navigate this page:
- 4.Planning the ERPI Configuration
- 4.1Planning Locations
- 4.1.1Multiple Reconciliation Processes
- 4.1.2Same Source System Account reconciled in 2 different Profiles in a Single Process
3.Data Load ProcessThe ARM data load process encompasses three phases: 
While configuration of data loads has to occur within ERPi, it’s important to note that data loads should be initiated from within ARM. Although ERPi enables data loads to be initiated from within ERPi, doing so will limit execution to the first phase (Staging). The Load and Post-Processing phases will not occur. To execute a complete data load (encompassing all three phases), data loads must be initiated within ARM by an Administrator from the Manage Periods dialog. 4.Planning the ERPI ConfigurationThe main components of an ERPI data load are Locations, Import Formats, Data Load Rules, and Data Load Mapping. 
Location is the level at which a data load is executed in ARM. A Location is associated with one source system, but can import data from multiple ledgers from that system. Each Location is assigned an Import Format, one or more Data Load Rules, and a Data Load Mapping. The Import Format determines which fields (columns) are extracted from the source system and how the data is stored in the ERPi staging table. The 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). The Data Load Mapping determines which ARM Profile ID and balance Source Type is assigned to each balance imported. Source Type refers to the classification of a balance as either a source system balance or a subsystem balance. 4.1Planning LocationsLocation is a key component and requires consideration and planning. One Location is needed for each general ledger and subledger from which balances are imported. For example, if general ledger balances are required to be imported from Oracle EBS, PeopleSoft, and SAP, and subledger balances are imported from the Accounts Payable and Accounts Receivable subledger from each of the 3 source systems, then 9 Locations are required:
If balances are imported from multiple ledgers within a single source system and the ledgers contain different charts of accounts or period configurations, then a separate Location is required for each configuration. 4.1.1Multiple Reconciliation ProcessesBalances within a single Location can only be assigned to a single Profile ID in ARM. Therefore, if the same source system accounts need to be reconciled as part of two different reconciliation processes (for example, as part of the Balance Sheet Reconciliation Process and the Consolidation System Reconciliation Process), then a separate Location must exist for each Process (because in this case, two Profile ID’s will exist in ARM: one for each process). When performing multiple reconciliation processes for the same source system balances, we recommend naming the Locations with a combination of the source system name and the process name. For example:
4.1.2Same Source System Account reconciled in 2 different Profiles in a Single ProcessOn rare occasions, the same source system account may be included in two different reconciliations as part of the same reconciliation process in ARM. Within a single Location in ERPi, a source system balance can only be assigned to a single Profile ID in ARM. Therefore, to accommodate a second assignment, a second Location must be created for the same source system. Only those accounts subject to a second Profile ID assignment are mapped in this Location. The rest of the accounts are ignored. Download 186.56 Kb. Share with your friends:
|