Use the Member Mappings to identify how source dimensions and members should be translated to the target consolidation system. These mappings are referenced during Data Imports.
When importing data, member mappings define relationships between source members from source systems, such as, ERPs and General Ledgers, and target dimension members within the system.
You can create a map with mappings for a specific dimension or alternatively you can create a map with mappings for multiple dimensions.
For example:
In cases where the member names in your import file don't match the member names in the system, you need to create member maps. In the sample data import file:
- The accounts may need to be mapped to account members that exist in the system, for example, 10000 may need to be mapped to a member A10000.
- The entity may need to be mapped to entity codes that are in the system.
- Use SKIP in the Mapped Value to ignore the corresponding source record.
For example, in this Sample Data Import File, USA may need to be mapped to USA100.
| Account | Date | Entity | Currency | Amount |
| 10000 | 202503 | USA | USD | 67000 |
| 11000 | 202503 | USA | USD | 1240000 |
| 13100 | 202503 | USA | USD | 15000 |
| 13200 | 202503 | USA | USD | 10000 |
| 13300 | 202503 | USA | USD | 58222 |
| 13400 | 202503 | USA | USD | 125490 |
There are four types of Member Mappings available:
- Exact: Map a specific source value to a target value.
- Range: A range of source values is mapped to a single target value.
- In: A list of non-sequential source values to be mapped to one target value.
- Wildcard: Use * and ? Wildcard characters to map to one or more target values.
Exact mappings are one-to-one mappings. Range, In, and Wildcard are advanced mapping types that can be used to reduce on-going maintenance when new members are added to source systems.
Order of Precedence
When the mapping engine processes the source values, multiple mappings may apply to a specific source value. The order that the mappings appear in the Map determines the order of precedence. You can drag and drop the mappings using the row selector in the Mapping Editor to change the order of precedence.
The first mapping that matches the source value is the mapping that'll be applied.
Exact Mappings
Use Exact mappings to map a specific source value to a target value. The mapping engine looks for the exact source value and map it to a specific member of the system.
This type of mapping is the simplest of all four types of mappings. This mapping type can be useful in these scenarios:
- You need to specify an explicit mapping.
- Range, In, and Wildcard mappings don't apply.
- The mapping contains spaces and other special characters.
For example:
| Account | Date | Entity | Currency | Amount |
| 1000 | 2022 Jun | San Francisco | USD | 0 |
| A1010 | 2022 Jun | San Francisco | USD | 200 |
| 1300 – Short-term loans | 2022 Jun | San Francisco | USD | 300 |
| 1100 – Subscription Receivables, Other | 2022 Jun | San Francisco | USD | 400 |
| Dimension | Mapping Type | Source Value | Mapped Value |
| Account | Exact | 1000 | 1000 |
| Account | Exact | A1010 | 1010 |
| Account | Exact | 1300 - Short Term Loans | 1300 |
| Account | Exact | 1110 - Subscription Receivables, Other | 1110 |
Range Mappings
Use Range mappings to map a range of source values to a single target value. The range consists of an alphanumeric minimum and maximum separated by a hyphen (-).
You may find this mapping type useful in these scenarios:
- There are a range of source product SKUs to be mapped to a single product within the system.
This example shows a sample source file followed by examples of the corresponding Range Mappings in the Mappings Editor.
| Account | Date | Entity | Currency | Amount |
| 4200 | 2022 Jun | San Francisco | USD | 80000 |
| 4210 | 2022 Jun | San Francisco | USD | 900 |
| A4200 | 2022 Jun | San Francisco | USD | 1000 |
| SKU101 | 2022 Jun | San Francisco | USD | 1101 |
| SKU202 | 2022 Jun | San Francisco | USD | 1202 |
| SKU303 | 2022 Jun | San Francisco | USD | 1303 |
| Dimension | Mapping Type | Source Value | Mapped Value |
| Account | Range | 4200-4299 | 4200 |
| Account | Range | A4200-A4299 | 4200 |
| Product | Range | SKU101-SKU999 | Bikes |
Note: When specifying the Source Value for Range mappings in the Mappings Editor, ensure that the minimum and maximum values are separated by a hyphen (-) and that there are no extra spaces in the range clause.
In Mappings
Use In mappings to map a list of non-sequential source values to one target value. The In clause is a comma-separated list of source items.
This mapping type is useful in these scenarios:
- Several disparate source members need to be mapped to a single member.
- Several source members that may be referred to by slightly different names depending on the import file.
The example shows a sample source file followed by examples of the corresponding In Mappings in the Mappings Editor.
| Account | Date | Entity | Currency | Amount |
| 4100 | 2022 Jun | San Francisco | USD | 500 |
| 4105 | 2022 Jun | San Francisco | USD | 6000 |
| 4110 | 2022 Jun | San Francisco | USD | 700 |
| 4100-00 | 2022 Jun | San Francisco | USD | 800 |
| Dimension | Mapping Type | Source Value | Mapped Value |
| Account | In | 4100,4105,4110,4100-00 | 4200 |
Note: When specifying the Source Value for In mappings in the Mappings Editor, ensure that each item in the list is separated by a comma (,) and that there are no extra spaces in the In clause.
Wildcard Mappings
Use * (asterisk) and ? (question mark) wildcard characters to map to one or more target values.
| Wildcard Character | Description | Example |
| * | Matches any number of characters. You can use the asterisk (*) anywhere in a character string. | ch* finds chat, chill, and chute, but not ache or catch. |
| ? | Matches a single character in a specific position. | f?ll finds fall, fell, fill but not fills or frill. |
The wildcard characters * and ? can be used together and multiple time within the source value, for example, A??100-* maps to A10000.
The wildcard character * can be used in both the source and target values. In this case, the mapped value is the equivalent of the source value after the wildcard characters have been stripped.
For example, the source accounts may contain the prefix A1000, A2000, A3000 and these need to be mapped to the accounts 1,000, 2000, 3000 in the system. You can use these wildcard mapping to achieve this:
| Dimension | Mapping Type | Source Value | Mapped Value |
| Account | Wildcard | A* | * |
This mapping type is useful in these scenarios:
- Several similarly formatted source members need to be mapped to a single member.
- The source members closely match the member names in the system but may contain a prefix or suffix that needs to be stripped.
- The * wildcard can be used to catch any unmapped members.
This example shows a sample source file followed by examples of the corresponding Wildcard Mappings in the Mappings Editor.
| Account | Date | Entity | Currency | Amount |
| 4000 | 2022 Jun | San Francisco | USD | 500000 |
| 4010 | 2022 Jun | San Francisco | USD | 1000 |
| 4020 | 2022 Jun | San Francisco | USD | 1000 |
| 5000-01 | 2022 Jun | San Francisco | USD | 1100 |
| 5000-02 | 2022 Jun | San Francisco | USD | 1200 |
| 5000-03 | 2022 Jun | San Francisco | USD | 13000 |
| 5140-11 | 2022 Jun | San Francisco | USD | 14000 |
| 5120-99 | 2022 Jun | San Francisco | USD | 15000 |
| AAA6001 | 2022 Jun | San Francisco | USD | 2001 |
| AAA6002 | 2022 Jun | San Francisco | USD | 2002 |
| AAA6003 | 2022 Jun | San Francisco | USD | 2003 |
| AAA6004 | 2022 Jun | San Francisco | USD | 2004 |
| AAA6005 | 2022 Jun | San Francisco | USD | 2005 |
| AAA6005 | 2022 Jun | Houston | USD | 2006 |
| AAA6005 | 2022 Jun | Denver | USD | 2007 |
| AAA6005 | 2022 Jun | Chicago | USD | 2008 |
| Dimension | Mapping Type | Source Value | Mapped Value |
| Account | Wildcard | 40* | 4000 |
| Account | Wildcard | 5000-?0 | 5000 |
| Account | Wildcard | 51*-?? | 5100 |
| Account | Wildcard | AAA60* | 60* |
| Entity | Exact | San Francisco | E250 |
| Entity | Exact | Houston | E120 |
| Entity | Wildcard | * | UnmappedEntity |
Note: Wildcard characters cannot match spaces (" ").