Specific Mapping File Structure for Jobs Runnable from Packages
When creating a data mapping definition, you can choose if you want to run its corresponding job from within a package, by selecting the Runnable from Packages option.
In this scenario, the system automatically derives source filters from the package's consolidation unit by reversing the mapping rules.
This automatic inversion is necessary because multiple users may run the same job from within their own packages. Without this feature, every user would process the entire dataset and process irrelevant rows at the end based on their package context. This approach would be inefficient and resource-consuming.
Technical Requirements for Rule Inversion
To enable successful rule inversion, your mapping file must adhere to the following requirements:
-
Dedicated Mapping Sheet: you must include a specific sheet that defines the input columns to be filtered and designates the Consolidation Unit as the output column.
-
Flat Hierarchy: Rule hierarchies are not permitted in this sheet; all rules must be set at Level 0.
-
Simplified Syntax: Complex logic cannot be inverted. Only basic mapping syntaxes are supported.
Supported syntaxes:
Unsupported syntaxes:
-
Row 4: Several input columns can't be combined to map the ConsolidationUnit output column.
-
Row 5: The expression for the output column must be reversible for filter generation.
-
Row 6: The filter for the input columns can't be empty.
-
Row 7: Complex regular expressions in input columns are not supported.
Validation and Best Practices
Additional validations are then applied to ensure the mapping file meets these requirements.