Mapping Sets
Mapping sets provide an efficient way to define a segment or account combination value for one or more transaction or reference attribute values. Using such input and output mappings is simpler than using complex conditions on account rules.
Based on the value of the source input, a single segment or a full account is derived.
Examples of source input value types:
-
Transaction attributes
-
Reference attributes
With mapping sets you can:
-
Use up to 10 transaction or reference attributes as inputs into a mapping.
-
Define default output value to use when actual input values don't match the mappings.
-
Use wildcards for multiple input mapping sets to indicate that the value of a particular input should be ignored for certain mappings.
-
Enter the mappings directly on the user interface or use the spreadsheet available in the Export option, and then import.
Export allows:
-
Exporting a template to create mappings.
-
Exporting all mappings created for the mapping set to add or edit the current mappings.
-
Example
Assume a business operates in several regions, including:
-
East
-
South
-
West
The business has a Region segment in their chart of accounts.
The region name can be the input for the mappings to derive the value of the region segment. You can create a mapping set that maps region names to the corresponding region code.
This table contains region names and segment values used in this example.
|
Input Value (Region Name) |
Segment Value |
|---|---|
|
East |
01 |
|
South |
02 |
|
West |
03 |
Additional transaction information, such as transaction type and salesperson name, could also be used as inputs to help derive a different segment value for each combination of the input values.
Constant values that are used in any Conditions region must not contain the following characters:
-
"
-
,
-
& -
|
-
(
-
)
-
'
For example, in the condition "Project Type" = ABC (123), the constant value following the equal sign, ABC (123), contains restricted characters ( ) that enclose 123 and is invalid.