---
sourceDocument: Australia Operational Technology Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/operational-technology

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Operational Technology Management

ft:clusterId :

    - optm

bundleId :

    - optm

workflow :

    - Technology


---

# Configure the RTE mapping for ETL

# Configure the RTE mapping for ETL {#ariaid-title1}

Release version: Australia  
Updated September 9, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Configure the Robust Transform Engine (RTE) mapping for the Extract Transform Load (ETL). The ETL process transfers custom column data from the import set to the target Configuration Management Database (CMDB) class.

## Before you begin

* Complete the update for the column mapping script. The custom column must be included in the JSON file exported to the import set before the RTE can map it. For more information, see [Update the column mapping script](https://www.servicenow.com/docs/CAVQYXsxMv2dGu3WgjmmwQ "To transfer the custom column data to the Configuration Management Database (CMDB), update the column mapping script to add the corresponding entry to the importSetColumnsVsStagingColumnsMap object.").
* Role required: admin
{#complete-rte-mapping-etl-sgc-excel__ul_y5l_dhz_qkc}

## About this task

When you select the Trigger CMDB Import UI action, the exported staging records are loaded into the SG-OT Asset Excel Import set and processed through the following RTE entities:

Import
:   The raw field on the import set record (the JSON key produced by importSetColumnsVsStagingColumnsMap).

temp
:   An intermediate staging entity used to hold the value during transformation.

CI class stub
: The target field on the CMDB CI class that stores the value.  
The data is processed from the Import to the temp to the CI class stub. You must define a field for each entity the data passes through and map each pair of entities.  
Warning:  
Use the same column name in the RTE entity fields as the key you used in the importSetColumnsVsStagingColumnsMap object. Using different names results in the RTE not finding the data to transform.

For more information about triggering the CMDB import process, see [Trigger a CMDB import for valid staging records](https://www.servicenow.com/docs/U1Gv9UW1v5_TZMrMfmXWLw "Trigger a Configuration Management Database (CMDB) import for your valid staging records to directly import them into the CMDB").

## Procedure

1. Create a field for the Import entity.
   1. Select All.
   2. In the Filter field, enter <kbd class="ph userinput">sys_rte_eb_field.do</kbd> to open a new record form in the RTE Entity Field (sys_rte_eb_field) table.
   3. In the Name and Field/Path fields, enter the name of your custom column.
   4. Set the Entity field to Import.
   5. Set the Definition field to SG-OT Asset Excel Import.
   6. Select Submit.
   {#complete-rte-mapping-etl-sgc-excel__substeps_khg_kt3_nkc}
2. Create a field for the temp entity.
   1. Select All.
   2. In the Filter field, enter <kbd class="ph userinput">sys_rte_eb_field.do</kbd> to open a new record form in the RTE Entity Field (sys_rte_eb_field) table.
   3. In the Name and Field/Path fields, enter the name of your custom column.
   4. Set the Entity field to temp.
   5. Set the Definition field to SG-OT Asset Excel Import.
   6. Select Submit.
3. **Optional:** Create a field for the configuration item (CI) class entity.  
   Note:  
   Only complete this step if the custom field is being added to the target CMDB CI class.
   1. Select All.
   2. In the Filter field, enter <kbd class="ph userinput">sys_rte_eb_field.do</kbd> to open a new record form in the RTE Entity Field (sys_rte_eb_field) table.
   3. In the Name and Field/Path fields, enter the name of your custom column.
   4. Set the Entity field to the CMDB class stub you want to target.
   5. Set the Definition field to SG-OT Asset Excel Import.
   6. Select Submit.
   {#complete-rte-mapping-etl-sgc-excel__substeps_bwd_4t3_nkc}
4. Create a mapping from Import to temp.
   1. Select All.
   2. In the Filter field, enter <kbd class="ph userinput">sys_rte_eb_field_mapping.do</kbd> to open a new record form in the RTE Entity Field Mapping (sys_rte_eb_field_mapping) table.
   3. Set the Source to the custom column from the Import entity.
   4. Set the Target Field field to the custom column from the temp entity.
   5. In the Order field, enter any value.  
      For example, <kbd class="ph userinput">100</kbd>.
   6. Set the Entity Mapping field to <kbd class="ph userinput">impTotemp</kbd>.
   7. Set the Definition field to SG-OT Asset Excel Import.
   8. Select Submit.
   {#complete-rte-mapping-etl-sgc-excel__substeps_vzq_pt3_nkc}
5. Create a mapping from temp to the CMDB class stub.
   1. Select All.
   2. In the Filter field, enter <kbd class="ph userinput">sys_rte_eb_field_mapping.do</kbd> to open a new record form in the RTE Entity Field Mapping (sys_rte_eb_field_mapping) table.
   3. Set the Source to the custom column from the temp entity.
   4. Set the Target Field field to the matching column from the target CMDB class entity stub.
   5. In the Order field, enter any value.  
      For example, <kbd class="ph userinput">100</kbd>.
   6. Set the Entity Mapping field to <kbd class="ph userinput">tempTo</kbd> followed by the CMDB class you're targeting.
   7. Set the Definition field to SG-OT Asset Excel Import.
   8. Select Submit.

## Result

After you configure these mappings, the custom column data populates correctly in the CMDB when you select the Trigger CMDB Import UI action.