NOTE: The Rule XRef action requires a check table to be defined for the field. If a check table is not already defined for the field, update the System Type for this field to add a check table. Refer to Add Check Tables in the Common documentation.
NOTE: The RuleXref action must be used with a lookup table that has multiple key fields. This will allow missing values in the Target table to be inserted into the Value Mapping table. The Xref action can only be used with a lookup table that has a single key field. If the Target Lookup table is a multiple key table, the Value Mapping process will concatenate Target values from the multiple key fields into a single field. To map fields on a multiple key lookup table, use the RuleXref action for the field to be mapped on the Field Mappings page. RuleXref concatenates Source values and is the recommended Migration Solution process to load the values correctly into the Value Mapping process.
NOTE: When mapping fields on a multiple key lookup table, concatenate the fields with a ":" separator, for example, field1:field 2.
NOTE: The Source table and Source field for the check table for the Rule Xref action are not automatically set. They must be entered on the Vertical View of the Legacy Value (Source Table Fields) page.
NOTE: A lookup table is registered as a Source table with a status of Documentation and a rule priority offset of 50000 so that it is sorted last. Documentation Sources are not processed but are a reference item to see all the sources of data.
To create a field mapping using the RuleXref action on the Field Mappings page:
- Select the field to be mapped.
- Select RuleXref from the ACTION list box.
Select the table that stores the field to be converted and then value mapped from the SOURCE TABLE list box.
NOTE: This table may or may not be a check table.
NOTE: When mapping a Source, this field displays the Add Row and Update Row Sources for the Add Row Source only. When mapping a Target, the field displays any Target in the Wave and Process Area.
- Select the field to be converted and then value mapped from the SOURCE FIELD list box.
- Click Save; a confirmation message displays.
NOTE: A user must create the SQL to convert the value and store it in the Rule SQL field on the Vertical View for the selected field mapping.
- Click the Vertical View icon.
- Click Edit.
- Enter the SQL to convert the value in the Rule SQL field.
- Click Save.
- Close the Vertical View.
- Click Submit on the Page toolbar.
NOTE: If the Auto Gen Level on the Automation page’s Vertical View is set to Off for the Target, this rule is not built in SQL. If the Auto Gen Level is set to ON but the Auto Generate Rule check box on the Automation SQL Field Mappings page’s Vertical View is unchecked, then the rule is not built.
The mapping must be approved by a Developer on the Mapping Approval page for documentation purposes and to help track progress of the data migration project. Refer to Approve or Reject Mappings and Assign Developers to a Target or Source for more information.
Once the mapping has been submitted, the Action, Source Table, Source Field and Default Value fields do not allow updates until one of the following events occurs:
- The Developer clicks Reject on the Mapping Approval page.
- The Mapper clicks Reset on the Field Mappings page.
NOTE: When a user clicks Reset, Mapping By, Submitted By, Created By and Approved By field will be reset to NULL values. The Rejected By field does not update and contains the user ID of the Developer who rejected the mapping on the Mapping Approval page. The Mapper can contact the Developer with any questions.
Once the fields allow update, edit them, click Save, and click the Submit icon on the Page toolbar. This updated mapping is sent to the Developer for review on the Mapping Approval page.
Refer to Perform Value Mapping for more information on mapping using a RuleXref Action.