Login to Workspace and launch ERPi:
5.1Configure System Settings -
Click the System Settings link located within the Preferences section on the Tasks navigator.
-
Provide the following values for the system settings options, and then press the Save button:
Option
|
Value
|
ODI Agent URL
|
The host and port should be the same as was configured during ODI installation. For example: http://10.149.101.173:20910/oracleodiagent
|
ODI User Name
|
SUPERVISOR
|
ODI Password
|
SUNOPSIS
|
ODI Execution Repository
|
WORKREP
|
ODI Master Repository Driver
|
WORKREP
|
ODI Master Repository URL
|
Must match the Master Repository schema created during ODI installation
|
ODI Master Repository User
|
Must match the Master Repository schema created during ODI installation
|
ODI Master Repository Password
|
Must match the Master Repository schema created during ODI installation
|
Application Root Directory
|
This is the folder into which import files will be placed when data is imported from file-based sources. This folder must be located on the ODI server, and sharing should be configured so that it is accessible by the server upon which ERPi is installed and from computers responsible for placing files into the folder. The Open_Interface_Adapter.xml file should also be placed into this folder. This xml file can be obtained from:
“\products\FinancialDataQuality\odi\11.1.2.2.00\adapters” folder
|
File Archive Directory
|
This is the folder into which import files are archived. The folder must be created under the Application Root Directory.
|
5.2Register Target Application
In order for ERPi to retrieve data for ARM, ARM must be registered as a Target Application in ERPi.
5.2.1Configure the Target Application Summary -
Click the Target Application link located within the Setup section on the Tasks navigator.
-
Click the Add button.
-
Select Account Reconciliation Manager from the Select Application dialog and click the OK button.
5.2.2Configure the Dimension Details
Configuration of the Target Application Dimension Details enables users to specify how columns in the staging table will be used for storing values from source systems. Only those source system values configured as Dimensions will exist in the staging table.
The staging table contains a fixed definition, including a series of standard fields of pre-determined use by ERPi, and a series of 20 user defined fields (UD1-UD20) that can be used by Target Applications for application-specific purposes. In ARM’s case, UD1 is reserved for storing the balance Source Type (the setting that classifies balances in ARM as either source system or subsystem balances). UD2-UD20 can be used to store other information required to be imported from the source systems.
5.2.2.1Pre-Defined Dimensions
After registering the Target Application, the Dimension Details section will contain the following four rows. These rows are not editable:
-
Period: maps the source system period to the Period column in the staging table
-
Profile: maps the ARM Profile ID to the Account column in the staging table
-
Currency Bucket: maps the ARM currency bucket to the Scenario column in the staging table
-
Source Type: maps the ARM balance type (source system or subsystem) to the UD1 column in the staging table
5.2.2.2LOOKUP Dimensions
In addition to the four pre-defined dimensions, additional dimensions (“LOOKUP Dimensions”) need to be added for additional data required to be imported from the source systems and stored in the staging table. There are two reasons why additional values would need to exist in the staging table:
-
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 staging table.
-
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 staging table 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.
-
If, however, some reconciliations are performed at the Company-Account level, while others are performed at the Company-Account-Plant level, then the staging table 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 staging table. Therefore, all information that should be visible during drill-back must exist either as pre-defined or LOOKUP Dimensions, so that the information will be present in the staging table.
5.2.2.3Configure LOOKUP Dimensions
Perform the following actions to configure LOOKUP Dimensions:
-
Click Add/Edit Lookup Dimension
-
Click the Add icon
-
Assign a Dimension Name and select from the list of User Defined columns in the staging table to store the value in
The purpose for assigning a name to the column is to make it easier to remember what data is being stored in the column when the Dimension is used in subsequent configuration steps. For example, when configuring balance mapping rules, it would be a lot easier to refer to columns titled “Company” and “Account” instead of “UD2” and “UD3”.
Since the same staging table is used to store balances from all source systems, names may need to be assigned more generically if the source systems have very unique charts of accounts. For example, if the staging table will be configured to store 3 segment values, and segment 3 is called “Profit Center” in one source system and Department in another, then the name assigned to the Dimension may need to be generic in order to accommodate both. In cases like this, “Segment 3” may be an appropriate Dimension name. In addition, best practices would dictate using the same segment names in ARM.
It is important to note that LOOKUP Dimension names are only used in ERPi during configuration. They are not visible to users of ARM viewing imported data through drill-back to ERPi. Rather, when drilling back from ARM to ERPi, these users will see labels that are specific to each data source imported.
Share with your friends: |
