Exceptions rule
This rule is used to create a separate version value tag for each difference in routing
without merging into a single routing. This rule is applicable when differences are identified
between input items, output items, routing effective from quantities, routing versions,
routing types, or routing alternative codes between routings that have the same routing item,
routing location, and effective from date.
This new routing uses this ID format and the version value:
- Id format: "SCP+" + <routing_item_id> + <routing_location_id> + <effective_from_date> + <new version value>
- Version value: <new version value>
Where <new version value> = Concatenate <version value tag> from exceptions using SZ_ROUTING_VERSION_MAP.version_value_separator as separator.
Note: Each enabled exception check generates at least one tag and, at the end, current generated routings must have all tags from enabled comparisons.
These are the various types of exceptions: