Implementation Toolkit Financial Close Management



Download 186.56 Kb.
Page5/8
Date21.06.2017
Size186.56 Kb.
#21317
1   2   3   4   5   6   7   8

5.5Register Source Systems


Source systems must be registered for each source system containing balance data to be loaded into ARM. “Source System” in this case refers to:

  • Supported general ledger platforms: Add a source system for each general ledger from which balances will be imported.

  • Files containing balances imported using File-Based Data Loads: If balances will be imported from files, then define a source system of type “File”. Only one should be required, even if files from multiple systems are being imported (they can all use the same Source System of type “File”).

  • Balances imported using the Open Interface method: Balances imported using the Open Interface method require a Source System Type of “Other”.

To configure Source Systems:

  1. Click the Source System link located within the Setup section on the Tasks navigator.



  1. Refer to the ERPi Administrator Guide for instructions on configuring each type of source system, as instructions are type-specific. If detailed logging is desired, set the Log Level to 5.

5.6Register Source Adapter


Registration of the Source Adapter is required when data is to be loaded from file-based sources.

To register the Source Adapter:



  1. Click the Source Adapter link located within the Setup section on the Tasks navigator.

  1. Click the Import button



  1. On the Import dialog, select Open_Interface_Adapter.xml and click the OK button.



  1. On the Source Adapter page, click the Save button.


5.7Select Source Accounting Entities


After Source Systems have defined, then Source Accounting Entities must configured by selecting the ledgers from which balances should be imported from each source. (This step does not apply to source systems of type “File” or “Other”).

To configure Source Accounting Entities:



  1. Click the Source Accounting Entities link located within the Setup section on the Tasks navigator.



  1. Select the Source System Type from the list of types provided.



  1. Select the associated Source System from the list provided, which are derived from Source System configuration.

5.7.1Configure Accounting Entities


  1. On the Entities tab, place a checkmark next to the ledgers (EBS/Fusion) or Business Units (PeopleSoft) from which balances should be imported.

  2. For EBS/Fusion source systems, if drill-back to the general ledger is desired, select a Responsibility Name that has proper system security required for viewing journal summaries and details. If drill-back is not desired, leave Responsibility Name blank.

  1. Press the Save button.

5.7.2Configure Entity Groups


Within the same source system, if multiple accounting entities (ledgers/business units) exist that contain the same chart of accounts and have balances that will be assigned the same currency bucket, then an Entity Group can be created for these entities. When configuring Data Load Rules, a single Rule can be created for the Entity Group, rather than having to create separate rules for each entity.

Consider an example of an EBS general ledger that contains the following individual ledgers (all of which utilize the same chart of accounts):



Ledger A

Contains entered and functional currency balances for all transactions associated with Entity A.

Ledger B

Contains entered and functional currency balances for all transactions associated with Entity B.

Ledger C

Contains entered and functional currency balances for all transactions associated with Entity C.

In this case, an Entity Group could be created for Ledger A, B, & C, since they share the same chart of accounts and currency bucket configuration.

To configure Entity Groups:



  1. Click the Entity Groups tab.

  2. Click the Add button.



  1. Type a Name, and optionally a Description for the Entity Group.



  1. In the Entity Group Entities table, place a checkmark next to each Accounting Entity that should be included in the Entity Group.

  2. Press the Save button.

5.8Configure Import Formats


Import Formats determine which fields (columns) are extracted from the source system and how the data is stored in the ERPi staging table. Import Formats are created for a single Accounting Entity. However, if you are importing data from multiple Accounting Entities that have the same COA, you can define one Import Format using a representative Accounting Entity and then use it for importing data for all Accounting Entities with the same COA.

To configure Import Formats:



  1. Click the Import Format link located within the Setup section on the Tasks navigator.



  1. Click the Add button to add a new Import Format.

5.8.1Configure Details


  1. Provide a Name for the Import Format. In general, it is good practice to include the Source Name and information about the ledger configuration in the Name of the Import Format. This will make it easier to select the proper Import Format when configuring the Location.

  2. Select the Source System

  3. Select a representative Accounting Entity (a ledger that contains the correct chart of accounts configuration). Note that the Import Format can be used to load balances from any Accounting Entity or Entity Group that shares the same chart of accounts. The actual selection of the chart of accounts to use occurs within the Data Load Rule configuration.

  4. Select the Account Reconciliation Manager as the Target Application.

  5. Click the Save button.

5.8.2Configure Mappings


The Mappings section determines how data from the source system is stored in the ERPi staging table. The procedures vary based on the type of source system for which the Import Format is being configured.

5.8.2.1Mapping ERP sources


The values appearing in columns Source Segment 1 through Source Segment 5 are the actual segment values that exist within the source system being confirmed. When configuring ARM, only Source Segment 1 column is used, because only one source segment value is stored in a single staging table column. The other Source Segment columns would be used if source values were concatenated together into a single column in the staging table (which is not a use case expected to apply to ARM).

For each source segment appearing in the Source Segment 1 column that should be imported from the source system and stored in the staging table, perform the following procedures:



  1. In the Dimensions column, locate the row that contains the corresponding staging table column name (the staging table columns were configured in the LOOKUP Dimensions section of Register Target Application).

  2. Assign the appropriate source segment column in the Source Segment 1 column on the same row.

Then, assign the Account source segment to the Profile dimension. The Source Type dimension should not be mapped.

Click the Save button once all mappings have been configured.



In the example above:



  • the Account segment from the source system will be stored in the Account column of the ERPi staging table

  • the Account segment is also mapped to the Profile dimension, which is a requirement for the data to load properly

  • the Company segment will be stored in the Company column of the ERPi staging table

  • the Department segment will be stored in the Dept column of the ERPi staging table

Note that the word “Dimension” is synonymous with “ERPi staging table column”.

5.8.2.2Mapping File-Based sources


When configuring mappings for file-based sources, the procedures are similar, but slightly different. Every column that exists in the source file has to be mapped to a Target, which refers to a column in the ERPi staging table.
5.8.2.2.1Configuration of Delimited Files

Consider the following sample comma-delimited file:

The file contains 5 columns:



  1. Company

  2. Account

  3. Department

  4. Amount

  5. Currency Code

For each column in the file, perform the following procedures:

  1. In the Target column, locate the row that contains the staging table column name associated with the column in the file (the staging table columns were configured in the LOOKUP Dimensions section of Register Target Application).

  2. Assign the appropriate file column in the Source column on the same row. The actual text typed into Source Column is used for display purposes in ERP only. The text does not need to match a column heading in the file (in fact the file is not required to even include a header row).

  3. Field Number: Provide the column number of the field in the file. This value is important, as it used by ERPi to locate the data in the file that should be stored in the staging table column specified in the Target column. In the example above, Company would have a value of “1”, since it is the first column in the file. Department would have a value of “3”.

  4. Number of Fields: The total number of fields in the file. In the example above, the value would be “5”, since 5 columns exist in the file.

  5. Expression: If values in the file require manipulation or conversion, Expressions may be used. One expression that is key for file-based sources is NZP, which ensures that zero balances are imported. To import zero balances (a typical account reconciliation requirement), type “NZP” (without the quotes) into the expression column for the Amount field. If this expression is omitted, zero balances will not be imported. Refer to the ERPi Administrator’s Guide for details on other expressions.

Then, map the Account column to the Profile Target.

If the file contains a Currency Code column, this column must also be mapped to the staging table. By default, the Target column does not include the currency staging table column. To add the Currency staging table column to the Target column, perform the following procedures:



  1. Click the Add button

  2. Select Currency Row



  1. Map the column in the file containing the Currency Code to the Currency Target.

The following image demonstrates how the sample file, once configured, would appear in ERPi.


5.8.2.2.2Configuration of Fixed Width Files

Configuration of fixed width files varies from delimited files in one way: instead of Field Number and Number of fields, Start and Length are required.

  • Start: Identifies the starting position within the row of the value to be imported. For example, if configuring the mapping for Currency Code, and Currency Code begins in position 65 of each row, then enter 65 in the Start field.

  • Length: Identifies the length of the data field. For example, since Currency Codes are always 3 digits in length, enter 3 in the Length field.
5.8.2.2.3Configuration of Skip Rows

Data files may include rows that need to be ignored. ERPi includes a robust feature set for configuring rows that should be skipped, or ignored, during import. To add Skip Rows, perform the following procedures:

  1. Click the Add button

  2. Select Skip Row

  3. Configure the Skip Row, using the following example as guidance.

The first 5 rows in the file should be skipped, since it contains heading information. In addition, the rows containing the column headers and the heading underlines should also be skipped. Since these rows repeat on each page, they’ll need to be skipped every time they appear. The following image demonstrates how ERPi was configured to ignore these rows.



When the value appearing in the Expression column appears in the range identified by the Start Position and Length, then the row should be skipped. For example, consider the Source Column “Skip 3” in the image above. Any time the word “Account” appears in positions 1-7 of the file, the entire row will be skipped. This will cause the row marked with the arrow below to be skipped:




5.8.2.3Regenerate ODI Scenario


    Each time an Import Format is added or updated for data sources other than EBS, PeopleSoft, or Fusion, then a Regenerate ODI Scenario message will appear, requiring the Regenerate ODI Scenario button to be pressed. Failure to perform this action will cause the import to fail. See Appendix 2 for a typical ODI Studio Error Message resulting from failure to Regenerate ODI Scenario. Note that in version 11.1.2.2, Import Formats requiring regeneration of an ODI Scenario cannot contain spaces in the Import Format name. Including a space will cause the Regenerate ODI Scenario action to fail.


Download 186.56 Kb.

Share with your friends:
1   2   3   4   5   6   7   8



The database is protected by copyright ©ininet.org 2024
send message
    Main page
effective functioning
instructions contained
information displayed