An Internal action does not create any rules in Map. The Target ERP system is the source for the number.
NOTE: A mapping with an Internal action cannot be saved unless the fields SOURCE TABLE, SOURCE FIELD, DEFAULT VALUE, and RULE SQL on the Horizontal View are blank and the Target Relationship ID field on the Vertical View is empty on the Field Mappings page.
To create a field mapping using the Internal action on the Field Mappings page:
- Select the field to be mapped.
- Select Internal from the ACTION list box.
- Click Save.
- Click the Submit icon on the Page toolbar.
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 created, 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 Submiticon on the Page toolbar. This updated mapping is sent to the Developer for review on the Mapping Approval page.