{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":36802,"path":"operational-technology/operational-technology-manager/complete-rte-mapping-etl-sgc-excel.md","title":"Configure the RTE mapping for ETL","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure the RTE mapping for ETL\n\nConfigure 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.\n\n## Before you begin\n\n-   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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/operational-technology/operational-technology-manager/update-column-mapping-script-sgc-excel.md).\n-   Role required: admin\n\n## About this task\n\nWhen 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:\n\n-   **Import**\n\n    The raw field on the import set record \\(the JSON key produced by importSetColumnsVsStagingColumnsMap\\).\n\n-   **temp**\n\n    An intermediate staging entity used to hold the value during transformation.\n\n-   **CI class stub**\n\n    The target field on the CMDB CI class that stores the value.\n\n\nThe 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.\n\n**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.\n\nFor more information about triggering the CMDB import process, see [Trigger a CMDB import for valid staging records](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/operational-technology/operational-technology-manager/trigger-cmdb-import.md).\n\n## Procedure\n\n1.  Create a field for the Import entity.\n\n    1.  Select **All**.\n\n    2.  In the **Filter** field, enter `sys_rte_eb_field.do` to open a new record form in the RTE Entity Field \\(sys\\_rte\\_eb\\_field\\) table.\n\n    3.  In the **Name** and **Field/Path** fields, enter the name of your custom column.\n\n    4.  Set the **Entity** field to **Import**.\n\n    5.  Set the **Definition** field to **SG-OT Asset Excel Import**.\n\n    6.  Select **Submit**.\n\n2.  Create a field for the temp entity.\n\n    1.  Select **All**.\n\n    2.  In the **Filter** field, enter `sys_rte_eb_field.do` to open a new record form in the RTE Entity Field \\(sys\\_rte\\_eb\\_field\\) table.\n\n    3.  In the **Name** and **Field/Path** fields, enter the name of your custom column.\n\n    4.  Set the **Entity** field to **temp**.\n\n    5.  Set the **Definition** field to **SG-OT Asset Excel Import**.\n\n    6.  Select **Submit**.\n\n3.  Create a field for the configuration item \\(CI\\) class entity.\n\n    **Note:** Only complete this step if the custom field is being added to the target CMDB CI class.\n\n    1.  Select **All**.\n\n    2.  In the **Filter** field, enter `sys_rte_eb_field.do` to open a new record form in the RTE Entity Field \\(sys\\_rte\\_eb\\_field\\) table.\n\n    3.  In the **Name** and **Field/Path** fields, enter the name of your custom column.\n\n    4.  Set the **Entity** field to the CMDB class stub you want to target.\n\n    5.  Set the **Definition** field to **SG-OT Asset Excel Import**.\n\n    6.  Select **Submit**.\n\n4.  Create a mapping from Import to temp.\n\n    1.  Select **All**.\n\n    2.  In the **Filter** field, enter `sys_rte_eb_field_mapping.do` to open a new record form in the RTE Entity Field Mapping \\(sys\\_rte\\_eb\\_field\\_mapping\\) table.\n\n    3.  Set the **Source** to the custom column from the Import entity.\n\n    4.  Set the **Target Field** field to the custom column from the temp entity.\n\n    5.  In the **Order** field, enter any value.\n\n        For example, `100`.\n\n    6.  Set the **Entity Mapping** field to `impTotemp`.\n\n    7.  Set the **Definition** field to **SG-OT Asset Excel Import**.\n\n    8.  Select **Submit**.\n\n5.  Create a mapping from temp to the CMDB class stub.\n\n    1.  Select **All**.\n\n    2.  In the **Filter** field, enter `sys_rte_eb_field_mapping.do` to open a new record form in the RTE Entity Field Mapping \\(sys\\_rte\\_eb\\_field\\_mapping\\) table.\n\n    3.  Set the **Source** to the custom column from the temp entity.\n\n    4.  Set the **Target Field** field to the matching column from the target CMDB class entity stub.\n\n    5.  In the **Order** field, enter any value.\n\n        For example, `100`.\n\n    6.  Set the **Entity Mapping** field to `tempTo` followed by the CMDB class you're targeting.\n\n    7.  Set the **Definition** field to **SG-OT Asset Excel Import**.\n\n    8.  Select **Submit**.\n\n\n## Result\n\nAfter you configure these mappings, the custom column data populates correctly in the CMDB when you select the **Trigger CMDB Import** UI action.\n\n**Parent Topic:**[Add a custom column to the staging table](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/operational-technology/operational-technology-manager/add-custom-column-staging-table.md)\n\n"}}