eLearning is available for this topic. Check it out here: HxGN SDx® | Data Validator: MSR and HEX Mappings
Most Data Validator mappings are configured out-of-the-box and help in creating objects such as plants, projects, areas, and so on, that represent your plant configuration. You may need to modify the out-of-the-box mappings sometimes to meet your unique business requirements. Data Validator provides Master (MSR) and Editable (HEX) copies of mappings to ensure that the master mappings are protected from unwanted side effects when you customize the editable copy of your own mappings and to support any upgrade process.
-
Master Data Validator mappings with the prefix MSR cannot be used in the system and are supplied only for reference. However you can copy the MSR mappings. For more information, see Copy Data Validator master mappings.
-
Editable copies of the master Data Validator mappings with the prefix HEX can be used and edited in the system.
-
The main Data Validator mapping elements are target systems, import mappings, export mappings, rules and rule sets, job definitions, job detail objects, and job details item objects.
-
The target systems, import mappings, export mappings, rules and rule sets, and job definitions are available in the Data Validator Administration module whereas the job details objects and job details item objects are available in the Desktop Client.
Data Validator Administration
The master mappings are not displayed by default. You must click Show Master 
in the respective screens in Data Validator Administration to view the following master mappings and their related elements:
-
Master Target Systems
-
Master Import Mappings
-
Master Rule Sets
-
Master Export Mappings
-
Master Job Definitions
Desktop Client
The master and editable copies of job details objects and job details item objects are displayed when you search for these objects in the Desktop Client. However, the master objects cannot be edited and are supplied only for reference.
Master mappings (MSR)
In order that each master mappings (MSR) remains intact and unaffected, the ISPFNonEditableCopy interface definition is instantiated on each master mapping element. The ISPFNonEditableCopy interface is only realized by elements used in the master mappings and prevents those elements from being referenced, edited, updated, deleted, or attached. When the master mapping is selected in the user interface, the edit option is not displayed.
-
You can select an object in the Stage to Target Object Map pane in the Export Mapping screen, and click Edit to view the export mapping details of the selected object. However, you cannot edit any of the details.
-
Master mappings or their related elements must not be used while running a silent job or a normal job using the Data Validator Job Management module or the Web Client.
Editable copy of the mappings (HEX)
The editable copy of the mappings (HEX) is supplied so you can customize the mappings. The editable copy does not contain or reference the elements that realize the ISPFNonEditableCopy interface. This allows you to edit the copy of the mappings to meet your custom mappings needs, such as adding new columns, rule sets, and so on.
In case of existing mappings, only the Master copy (MSR) of a mapping is delivered
in case it has been changed in a new release. The Editable copy (HEX) is not upgraded
to prevent undesirable consequences from the upgrade. For more information on upgrading
HxGN SDx, see Upgrade the Data Validator mappings.
Using MSR or HEX prefix in custom mappings
When you create or edit your own custom mappings, we recommend you do not use the MSR or HEX prefix in the names of the mapping elements. If there are overlapping names and Object UIDs between delivered and custom mappings, they may cause issues in the upgrade process, due to uniqueness constraints. Also, we recommend you do not use the MSR or HEX prefix in any of your custom XML mappings that you load into your system using the Loader.
Custom mapping elements that must not have MSR or HSR prefix
-
Target Systems
-
Import Definitions
-
Job Definitions
-
Validation Rules
-
Validation Rule Sets
-
Staging Schema
-
Job Details
-
Job Details Items
Object weights for delivered mappings
The Object Weight value controls the order of export of the object or error report. The lower the number, the earlier in the process the object is exported or reported. For example, a class can exist without a tag, but a tag cannot exist without a class. Therefore, a class has a higher priority and so a lower object weight.
You can view or edit the object weights in Data Validator Administration module in the Export Mapping page.
You must not use any of the object weights already assigned to the delivered class
definitions of the staging objects.