Configure Data Load Mapping

5.11.1Rules Assigning ARM Profile ID’s

To manually create mapping rules to assign ARM Profile ID’s, perform the following procedures (refer to the Import Data Load Mappings for instructions on importing mapping rules):

1. 
   Select “Profile” from the Dimension selection. This means that the mapping rules specified will be used for assigning an ARM Profile ID.
   

3. 
   Click the Multi-Dimension tab.
   

2. 
   Click the Add button to add a mapping rule.
   

3. 
   Target Value: Enter the ARM Profile ID, or click the browse icon to select from the list of Profile IDs.
   
4. 
   Rule Name: We recommend using the ARM Profile ID as the rule name, too.
   
5. 
   Click the Add button to add criteria for determining which source system accounts are assigned this Profile ID. For example, if assigning Profile ID 100-1510 to all accounts where Company Code = 100 and Account = 1510, then two rows should be added to the Multi-Dimension table:
   
   1. 
      The first row contains a condition on the source system Company segment:
      

1. 
   Dimension: Company
   
2. 
   Condition: Explicit (the source segment value must exactly match the value specified in the Value field in order for the Profile ID to be assigned)
   
3. 
   Value: 100
   

2. 
   The second row contains a condition on the source system Account segment:
   
   1. 
      Dimension: Account
      
   2. 
      Condition: Explicit
      
   3. 
      Value: 1510
      

If the criteria needs to accommodate a range of values, consider using the “Between” Condition. Specify the starting and ending range, with a comma in between. For example: 1510, 1520 would select accounts in the range from 1510 to 1520.

If the criteria needs to accommodate a partial value in a source account segment, consider using the “Like” Condition. For example, if Profile ID 100-1510-2XXX should be assigned to all accounts where Company = 100, Account = 1510, and Department starts with 2, then the Condition for Department should be created using the “Like” Condition, using the Asterisk (*) character to behave has a wildcard. For example, “2*” would select all accounts where Department starts with 2. Refer to the ERPi Administrator Guide for information on other special characters.

6. 
   Once finished adding criteria, click the Ok button to close the Multi-Dimension dialog.
   
7. 
   Change Sign: The Change Sign checkbox, when checked, causes ERPi to adjust the signage of the balance. Whether or not the box should be checked depends on the interface method used by the Location for which mapping rules are being configured:
   

1. 
   If the Location is importing balances from a supported ERP source system, then balances are always imported in absolute value:
   
   1. 
      Assets and expenses are positive if the value is a debit and negative if the value is a credit
      
   2. 
      Liabilities, revenue, and equity are positive if the value is a credit and negative if the value is a debit
      
2. 
   If the Location is importing balances from a file using File-Based Data Loads, then the balances will be imported using the signage existing in the file.
   

For File-Based Data Loads, it depends on the structure of the data in the file. If the data conforms to ARM’s requirements (debits are positive and credits are negative), then the box does not need to be checked. If the signage is based on the account type, then the box will need to be checked for liability, revenue, and equity accounts.

5.11.1.1IGNORE Mapping Rules

Some source system accounts may have a legitimate reason for being excluded from mapping rules. For example, when mapping accounts to Profiles in ARM that are part of the Balance Sheet reconciliation process, only balance sheet accounts should be mapped. Income statement accounts are not relevant to this process and should be ignored.

Accounts that should be excluded from mapping must be provided an IGNORE mapping rule, using the procedures outlined below. If this does not occur, these accounts will appear in ARM as “Unmapped Accounts” when data loads are executed. To configure IGNORE mapping rules:

1. 
   Click the Add button to add a row to the Multi-Dimension table.
   
2. 
   In the Rule Name and Target Value, type IGNORE.
   

3. 
   Click the Add button to configure the criteria determining which source system balances should be ignored. For example, if Income Statement accounts should be ignored, and the account number for these accounts start with “3” or “4”, then two rules should be added, both using the Like condition:
   
   1. 
      Accounts starting with a “3”
      

1. 
   Dimension: Account
   
2. 
   Condition: Like
   

1. 
   Value: 3*
   
1. 
   Accounts starting with a “4”
   

3. 
   Dimension: Account
   
4. 
   Condition: Like
   

1. 
   Value: 4*
   

5.11.1.2Conflicting Mapping Rules

It is possible to define conflicting mapping rules (rules that attempt to assign a different Profile ID to the same source system account. If this occurs, the rule that appears first in the list “wins”. Subsequent rules affecting the same source system account will be ignored.

5.11.2Rules Assigning ARM Balance Source Types

Balance Source Types enable ARM to classify a balance as either a source system balance or a subsystem balance.

Consider the following examples:

• 
  A reconciliation is performed as part of the Balance Sheet reconciliation process in ARM, comparing a general ledger balance to the corresponding AP Subledger balance. The objective of the reconciliation is to verify that the general ledger balance is correct. In this case, the general ledger balance should be assigned a Source Type of “source system”, and the AP subledger balance should be assigned a Source Type of “sub-system”.
  
• 
  A reconciliation is performed as part of the Consolidation System reconciliation process in ARM, comparing balances in HFM to the general ledger balances. The objective of the reconciliation is to verify that the HFM balance is correct. In this case, the HFM balance should be assigned a Source Type of “source system”, and the general ledger balances should be assigned a Source Type of “sub-system”.
  

The key point to remember is that Source Type “source system” should be assigned to the balance to be reconciled, whereas the Source Type “sub-system” should be assigned to balances used for comparison purposes.

Mapping rules to assign balance Source Types are expected to be configured using the Like method, which enables Source Types to be assigned to source system accounts based on a single “wildcard” criteria.

To configure mapping rules to assign Source Types, perform the following procedures:

1. 
   Select “Source Type” from the Dimension selection. This means that the mapping rules specified will be used for assigning an ARM balance Source Type.
   

2. 
   Click the Like tab
   

3. 
   Click the Add button to add a mapping rule, using the following configuration:
   

4. 
   Source Value: Enter “*” to select all source values, since all source values will be assigned the same Target Value.
   
5. 
   Target Value: Click the browse icon and select the appropriate value (source system or sub-system) from the list provided.
   
6. 
   Rule Name: We recommend using the Target Value as the Rule Name, for simplicity.
   

Note that an IGNORE mapping rule is not required for the Source Type dimension. The IGNORE rule configured for the Profile dimension will cause the same accounts to be ignored for the Source Type dimension.

5.11.3Import Data Load Mappings

Customers using ERPi to import balances to ARM will have at least one mapping rule for every reconciliation performed in ARM. For many companies, thousands of mapping rules will exist. Therefore, importation of mapping rules is a feature expected to be used widely, as it offers a far more efficient method for configuring mapping rules than entering each rule manually. We recommend turning off the validate option when importing large numbers of mappings. Invalid mappings will be detected during data import, and can be corrected at that time.

5.11.3.1Import File Format

Mappings can be imported from .txt and .csv files. The file format depends on which dimensions are used when specifying mapping criteria and how these dimensions were mapped to the staging table in the Import Format configuration. In general, the import file contains the following four columns, in the order listed (from left to right):

• 
  Mapping criteria
  
• 
  Target Account
  
• 
  Rule Name
  
• 
  Description
  

Columns in the import file may be separated by any of the following characters:

• 
  ,
  
• 
  ;
  
• 
  |
  

Consider the following example where source system segments Company and Account are used as mapping criteria. These segments were configured as LOOKUP Dimensions and mapped in the Import Format to the UD2 and UD3 staging table columns, respectively:

Source System Segments	Mapped to Staging Table Column
Company	UD2
Account	UD3

In this example, the import file would appear as follows:

Note the file does not contain a header row. Column A contains the mapping criteria, column B contains the Target Account, column C contains the rule name, and column D contains a description of the rule (description is optional, so this column may be blank).

The mapping criteria column is prefixed with “#MULTIDIM”, which identifies to ERPi that Multi-Dimension mapping is being used. Following this prefix, the mapping criteria column contains a concatenation of all of the criteria required to assign a Profile ID to a source system account. Row 1, for example, will assign Profile ID 100-1500 to any source system account where Company (UD2) equals 100 and Account (UD3) equals 1510.

Since mapping rules are generally related to ARM profile segment values, once the structure of the mapping file is understood, the concatenate function in spreadsheet programs should provide a handy mechanism for creating import files based on ARM Profile Segment values.

To use the concatenate function, split the text from Column A into the following component columns, leaving empty columns for the segment values:

Then, copy the ARM Profile Segment values into the empty columns:

Add a concatenate function to column F that concatenates the values from columns A-E:

Add a concatenate function to column G to create the Target Account value:

To create the Rule Name column, add a formula to column H to set the value equal to column G:

Copy the formulas in columns F, G, & H to each row to be imported. Then, when you are ready to finalize the import file, copy the columns F-H, and “paste special” to paste the values. Then delete columns A-E, and your import file should be ready:

5.11.3.2Checking the Change Sign checkbox for Imported Mappings

The Change Sign setting is incorporated into the Target Account column. If Change Sign should be checked for a given rule, then the Target Account value should be preceded by a hyphen. For example, if the Target Account value should be “100-1500”, then to cause the Change Sign checkbox to be checked for this rule, the value appearing in the Target Account column should be “-100-1500”:

5.11.3.3Create a Template to Import Data Load Mappings

An easy method for determining the proper Import Format is to first create a mapping rule manually using the procedures described above, and then using the Export feature to export the mapping rule. The resulting file will contain the proper format that should be used for importing rules.

To create a template to import Data Load Mappings:

1. 
   Click the link located within the Data Load section on the Tasks navigator
   

2. 
   Select the Location for which mappings are being configured.
   

3. 
   Click the Multi-Dimension tab.
   

4. 
   Select the Dimension for which mapping rules are being created (either Profile or Source Type), click the Export button, and choose the Current Dimension option.
   

5. 
   In the Specify file location dialog, provide a file name, and click the Ok button. Once the import is complete, click on the name of the file in the file list and choose to save the file to your computer. Once saved, you can edit the file.
   

5.11.3.4Re-Importing Mapping Rules

Mapping rules can be imported multiple times to either replace existing mapping rules, or to update mapping rules (using the merge option) so they match the configuration in the latest file. The merge option uses the Rule Name to identify records to be updated. If this option is selected, then any record in ERPi with a Rule Name that matches a Rule Name in the file will be updated.

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

Download 186.56 Kb.

Share with your friends: