Implementation Toolkit Financial Close Management

Download 186.56 Kb.

Page	1/8
Date	21.06.2017
Size	186.56 Kb.
	#21317

1 2 3 4 5 6 7 8

Implementation Toolkit

Financial Close Management

Configuring ERPI for ARM

Author: Heather Lynds

Creation Date: Feb 21, 2012

Last Updated: Apr 18, 2012

Document Version: 1.0

Status: DRAFT

1. Overview 4

1.1 Purpose of this Document 4

2. Data Integration Options 5

2.1 ERP Sources 5

2.2 Open Interface Method 5

2.3 File-Based Data Loads 5

2.3.1 File Naming Convention 5

2.3.2 File Columns 6

2.3.3 Importing Balances Associated with Different Currency Buckets 6

3. Data Load Process 8

4. Planning the ERPI Configuration 9

4.1 Planning Locations 9

4.1.1 Multiple Reconciliation Processes 10

4.1.2 Same Source System Account reconciled in 2 different Profiles in a Single Process 10

5. Configuring ERPI for ARM 11

5.1 Configure System Settings 11

5.2 Register Target Application 12

5.2.1 Configure the Target Application Summary 12

5.2.2 Configure the Dimension Details 12

5.3 Period Mapping 14

5.3.1 Global Mapping 15

5.3.2 Application Mapping 16

5.3.3 Source Mapping 16

5.4 Category Mapping 16

5.4.1 Review ARM Currency Configuration 16

5.4.2 Single Currency Category Mapping 17

5.4.3 Multi-Currency Category Mapping 17

5.5 Register Source Systems 18

5.6 Register Source Adapter 18

5.7 Select Source Accounting Entities 19

5.7.1 Configure Accounting Entities 20

5.7.2 Configure Entity Groups 20

5.8 Configure Import Formats 21

5.8.1 Configure Details 21

5.8.2 Configure Mappings 22

5.9 Configure Locations 26

5.10 Configure Data Load Rules 27

5.10.1 Configuring Data Load Rules for ERP Sources 27

5.10.2 Configuring Data Load Rules for File-Based Data Loads 29

5.11 Configure Data Load Mapping 30

5.11.1 Rules Assigning ARM Profile ID’s 31

5.11.2 Rules Assigning ARM Balance Source Types 33

5.11.3 Import Data Load Mappings 34

6. Appendix 1: Supported Currency Codes 39

Appendix 2: Troubleshooting 42

6.1 ODI Studio Error Message 42

7. Index 43

1.Overview

Integration of account balances is core to the effective functioning of an account reconciliation solution. FCM’s Account Reconciliation Manager (“ARM”) uses Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications (“ERPi”) to load balances from source systems and map the balances to reconciliations.

1.1Purpose of this Document

ERPi is used by many different Oracle applications. The purpose of this document is to facilitate planning for an ARM implementation and to explain how a typical ARM customer would configure ERPi for ARM. This document is intended to supplement the instructions contained in the Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Administrator’s Guide.

2.Data Integration Options

ERPi provides three options for importing balances into ARM.

2.1ERP Sources

ERPi has native support for importing general ledger balances from the following ERP source systems:

Oracle E-Business Suite 11i, 12
Oracle Fusion Financials
PeopleSoft Enterprise Financial Management 9.0, 9.1
SAP ERP Financial 4.7c, ECC 6.0 enhancement pack 4.0+
JD Edwards Enterprise version 9.0

Once connections to these source systems have been configured in ERPi, balances are retrieved from the source system directly upon initiation of a data load (no manual extract from the source system is required).

2.2Open Interface Method

ERPi provides an Open Interface Adapter which enables customers to populate data from any source system into an open interface table in ERPi, where the data is then accessible for import into ARM. This option is useful for importing general ledger balances from ERP’s for which adapters have not been produced, from subledger systems from any ERP platform, from HFM, or from any other system containing balances to be reconciled.

In addition to configuring the Open Interface Adapter in ERPi, customers must also populate the open interface table each month, using a data extraction tool of the customer’s choice. ODI can be used for this purpose, so long as the customer obtains a license to ODI.

2.3File-Based Data Loads

File-based data loads enable customers to import balances from delimited or fixed-width text files. In addition to configuring the file import, customers must also publish the files to be imported to the proper location each period. The location is configurable based on the ERPi application root directory (see Configure System Settings).

2.3.1File Naming Convention

ERPi supports two naming conventions for data load files: Static File Name, or Static File Name plus a Period Suffix. The convention used is based on the Data Load Rule configured for the file.

2.3.1.1Static File Name

For example, if the Static File Name is set to “EBS_Balances”, then when balances are imported for a selected period, ERPi will look for a file titled “EBS_Balances” and will import those balances into the selected period.

2.3.1.2Static File Name plus a Period Suffix

the same from period to period

When choosing the Period Suffix, two options are available: Period Key or Period Name. Both values are configured in the Global Mapping section of the ERPi Period Mapping dialog. The Period Suffix must exactly match the values configured, or the import will fail.

For example, if the Static File Name is set to “EBS_Balances_.txt”, Period Name is used as the suffix, and the Period Name is “January 2012”, then when balances are imported for January, ERPi will look for a file titled “EBS_Balances_January 2012.txt” and will import those balances into the selected period. If the file matching the expected name does not exist, then no balances will be imported.

2.3.2File Columns

Files must include the following columns:

Account Segments: The source system account segments associated with the balance (one segment per column)
Balance: The period-end balance

In addition, if the file contains balances in more than one currency, then an additional column must exist in the file containing the 3 digit ISO currency code associated with each balance. Refer to Appendix 1 for a list of supported currency codes. If the balances pertain to a single currency, then currency code may be omitted from the file and configured at the Location level.

Files do not require a header row. If a header row is included, it must be configured to be ignored in the Import Format definition.

2.3.2.1 Determining which Source System Segments to Include in the File

There are two factors to consider when determining which source system segments to include in the file:

Segments used in balance mappings: Any source system segments that are used to map balances from the source system to Profiles in ARM must exist within the file.
1. For example, if your source system contains segments for Company, Account, Profit Center, Plant, and Intercompany code, yet reconciliations are only ever performed at the Company-Account level, then the file only needs to contain values for the Company and Account segments. The values in these two segments will be used to map balances to the Profile in ARM.
2. If, however, some reconciliations are performed at the Company-Account level, while others are performed at the Company-Account-Plant level, then the file will need to store values from all three segments, so that the mapping rules can be configured properly. Mapping rules for accounts reconciled the Company-Account level will ignore the Plant segment values, while rules for accounts reconciled at the Company-Account-Plant level will use all three.
Segments that need to be visible during drill-back to aid in discovery: When viewers of reconciliations view balances in ARM, they are presented in summary, at the level at which reconciliation is performed. ARM supports drill-back to ERPi for the balance detail. The information displayed on the drill-back landing page is obtained from the values in the file. Therefore, all information that should be visible during drill-back must exist in the file, so that the information will be present during drill-back.

2.3.3Importing Balances Associated with Different Currency Buckets

ARM supports reconciliation of balances in up to 3 currency buckets. The names of buckets are configurable within ARM, but are generally classified like the following:

Entered: The currency in which the transaction occurred
Functional: The currency of the entity that owns the ledger
Reporting: An enterprise-wide reporting currency (typically the consolidation currency)

If the reconciliation process requires reconciliation of balances in more than one currency bucket, then balances must be imported for each bucket and a separate file is required for each set of balances. In this case, the static file name should include the currency bucket name to enable proper configuration of the import files.

Directory: technetwork
technetwork -> Apex 0 Web Services Evaluation Guide