Different strategies for mapping line variations in documents using the Configuration Studio tool.
Use these three methods to help you accurately interpret and map data across various line configurations for one trading partner. Those methods are: Split Mapping, Line Section Mapping, and Business Logic rules.
Split Mapping
Use Split Mapping to identify and isolate specific segments within a value, allowing you to focus on the parts of a term that are essential for accurate mapping.
The Split Mapping tool allows you to set a custom separator to guide Configuration Studio in splitting terms. You can define rules that ignore characters before or after this separator to isolate the key information you need. For more details on Split Mapping, see this article.
Note: Split Mapping will only function correctly if the separator is consistently present in the data. If the separator is missing, the system may fail to process the line as expected since it relies on the presence of the defined separator to execute the mapping. For example, if a part number always appears preceded by a "#" ( “#1234”) you can set “#” as the separator so the system ignores it and only maps the part “1234.”
Line Section Mapping
Use different line sections to map lines with repeating or similar content across different lines, while handling variations within these lines effectively.
This allows you to remap sections so that each unique section is treated as a line. Similar lines can be grouped and mapped collectively, while lines with different values are mapped separately but according to their shared attributes.
For example, if you have a document with several line items, where one set of lines has similar attributes (e.g., all are products with specific part numbers and quantities), while another set varies in attributes (e.g., lines for notes only). Mapping different line sections enables you to map each set accurately according to its specific attributes. In the screenshot below you can see two sections created to cover the two line variations. For more details on how to create and modify sections, see this article.
 |
Example of line section mapping
Business Logic
Business Logic Mapping allows you to implement conditional logic (e.g., “if,” “then,” “always” rules) to guide the Configuration Studio system in mapping lines according to specific terms or data presence, ensuring greater control over when and how fields are mapped.
By setting up conditional rules, you can direct Configuration Studio to map or skip mapping a line based on the presence of certain values. For example, create a logic statement to always set the Unit of Measure (UOM) to "EA" if it is missing. For more details on how to set up Business Logic in Configuration Studio, see this article.
Each mapping strategy can be implemented individually or in combination based on your document structure and mapping needs. Following these steps will help ensure accuracy in handling line variations for consistent and efficient data processing in Configuration Studio.