Remove check on ‘default mapping’ in SCV Mappings

The ‘default mapping’ check on SCV Mappings has been eliminated in the UI and the template loader. When multiple default mappings exist for one target table, instead of sending an error message, the UI now displays a warning message but continues and saves the mapping definition.

This allows users to load multiple ‘default’ mapping definitions using template without receiving any validation errors. For example, it is now possible to load both base for M3 and base for LN templates on the same SCP instance.

The ‘default mapping’ check is now applied by the transfer program at run time. The transfer program tries to determine a single mapping for each target table. If only one mapping exists, default or non-default, the program uses the existing for the transfer. If the transfer program cannot determine which mapping to use, the program sends an error message. Hence, default mapping is still required when executing a transfer at table or table group level where the target table has multiple enabled mappings.

By default, this feature is enabled. No additional role or privilege is required to access this feature.