Mapping Members

When you map members, the system converts the Chart of Accounts values from the Oracle General Ledger to the Oracle Enterprise Performance Management Cloud dimension members during the transfer. This allows Data Integration to categorize Oracle General Ledger balances.

In the following example, based on the Chart of Accounts segment, the Oracle General Ledger breaks down administrative expenses as a range of accounts from 4001-4003.

In Planning, budgeting for administrative expenses is done for dimension value 410, Administrative Expenses.

The example shows how Oracle General Ledger accounts in the range 4001-4003 actual amounts are mapped to 410 administrative expenses in Planning.

Differences in Planning dimension values and Oracle General Ledger Chart of Accounts values may occur. Additionally, segments of the Chart of Accounts may not be used when budgeting.

For example, you can map zero values (such as "0000" for sub-account) for the Chart of Accounts segments that are not used for budgeting.

Note:

When there is no update to the Oracle General Ledger value prior to the load, it is still necessary to create the member mapping for the dimensions to instruct Data Integration to create the target values.

To define map members:

1. From the Data Integration home page, click to the right of the integration, and then select Map Members.

2. On the Map Members page, from the Dimensions drop-down, select the dimension that you want to map.

   At a minimum, map values for the "Account" and "Entity" dimensions since those are transferred from Oracle General Ledger.

   If you are transferring additional chart segments you must provide a mapping for each destination dimension.

3. Select the member mapping type from the Mapping Type drop down, and then specify the source value.

   Types of member mappings:

   Type of Mapping	Description	See Also
   	Match and replace the source value exactly with the target value. Explicit mappings are one to one mappings, for example, source value "ABC" is replaced with target value "123."	Using Explicit Mappings
   	Replace a continuous range of source values with a single target value. For example, a range from "001" to "010" is replaced as one value. In another example, you may need to map accounts 300000 through 3001999 to Retained Earnings, but accounts 310000 might be Capital contributions or dividends.	Using Between Mappings
   	List non-sequential (non-continuous) source values to be mapped to one target value. In this case, multiple values are mapped to one value within one mapping, eliminating the need to create multiple rules (as is required for an Explicit map). For example, you could have source accounts 1503, 1510, and 1515 map to the target account 15000010.	Using In Mappings
   	Use special characters to match a string in the source value and map it to a target value. Like mappings use wildcard characters: asterisks (*) and question marks (?). Asterisks are placeholders for any number of characters. For example, 1190* maps the accounts 1190, 1190100, and 1190-200 to the Cash target account. Question marks are placeholders for one character. For example, the source account of 119? maps only to source accounts that contain four characters and that begin with 119.	Using Like Mappings
   	Multi-dimension mapping enables you to assign a target value for a specific combination of source column values. This functionality provides you with the ability to load data into dimensions unavailable in the target application. For example, the mapping for the Account dimension can be based on source values of Entity, Product, and Project. In addition, Lookup dimensions added in the target application registration can be selected. These dimensions contain source dimensions that do not exist in the target application. They provide even more flexibility in creating multi-dimension filters. It is a way to facilitate conditional data loading.	Using Multi-Dimensional Mappings

   Note:

   When processing the source values for transformations, multiple mappings may apply to a specific source value. The order of precedence is Explicit, Between, In, Multi-Dimensional, and Like. Within Between and Like types mappings can overlap.

4. Click to add a new member mapping.

   You can also just edit existing mappings as needed without adding a new mapping by selecting a mapping and clicking the Edit icon .

5. From Add Member Mapping page, then Source, select the source dimension member to map to the target dimension member.

   Enter the values from the Oracle General Ledger. Enter the values directly.

   To map all members to then EPM Cloud business process "as is" without any modification, in Source, enter: *, and in Target, enter: *.

6. In Target, enter the value for the accounting scenario to use to load the budget information.

   Enter the values that should be used in the EPM Cloud business process to store the Oracle General Ledger actual balances that are transferred.

7. In Processing Order, specify the order of the mapping.

   The processing order determines the level of precedence within a mapping type. Mappings are processed in alphabetical order by the name within a mapping type. Numbers may also be used to help with ordering. For example, if you use Number for processing, note that the processing order is in an alphanumeric sort order. If have 10, 20, 30, 100 as the order, the processing order will be 10, 100, 20, 30. When using numbers for the processing order, use the same number of digits for all maps.

8. In Description, enter a description of the member mapping.

   For example, enter a description such as "Map to the General Ledger".

9. In Change Sign, select to reverse the sign of the target account specified.

   The Change Sign option is often used with Oracle General Ledger source data when the trial balance has negative signs for Revenue and Liability/Equity source accounts. In EPM Cloud applications, positive numbers are often loaded as credits and all negative numbers are loaded as debits. Consequently, you can reverse the sign.

10. Optional: From the Apply To drop-down, select the name of the integration to which to apply the member mapping.

11. On the Add Member Mapping page, click OK.

12. On the Member Mapping page, click Save.