Edit input and output mapped value name in Zero Copy Connector for ERP

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
  • Manually edit mapped value field names for input and output when managing models in Zero Copy Connector for ERP (Enterprise Resource Planning).

    Before you begin

    Role required: sn_erp_integration.erp_admin

    About this task

    In ERP model manager, the mapped value name in inputs and outputs is system-generated automatically. Edit the value manually as needed. Specify a unique value. You can revert to the system-generated name at any time.

    Let's step through an example. In Zero Copy Connector for ERP, create a model. For more information, see Create a model.

    Procedure

    1. On the new model, select Manage Model and add a read operation.
    2. On the read operation, add a read table entity, for example, on the T005 Countries table.

      Add entity page with T005 entity selected.

      For more information, see Add an entity to a model.

    3. After data is retrieved, select Specify inputs.
    4. Select Select mandatory inputs.
    5. Select Country/Region Key and select OK.

      Mandatory inputs for countries organized into available columns and selected columns.

      The system-generated mapped value is countries_country_region_key. The operation parameter value is set to the same name.

      Specify inputs page with required parameter and mapped value fields highlighted.

    6. Change the mapped value to, for example, country_region_key and select Save.

      The updated mapped value is displayed and the operation parameter value changes to match automatically.

      Updated field with edited mapped value and updated, matching required parameter.

    7. If a new input is added, the mapped value is system-generated but is editable.

      For example, add the Nationality field and edit the name from countries_nationality to country_nationality so it's more consistent with the country_region_key name.

      New field added and mapped value is displayed as editable.

    • If a new child (nested) input is added, the system-generated mapped value doesn't contain the parent name. You can edit the child name for inputs and outputs. For input, the edited name is used in the operational parameter. In this example, the UDAT and BASXML_SUPPORTED fields were added and their system-generated names can be edited to contain or more closely match the parent name.

      Function call displayed with function names parent field and several child fields.

    • If a join is used, the changed name should be available on the join fields as well. For more information about joins, see Add joins between ERP tables.
    • If the same field exists in both input and output, but they have different mapped values, the name of the output field is given precedence and used.
    • If you want to revert to the system-generated name at any time, remove the field and then add it again. Another option is to change the mapping type and then change it back.