---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Extracting and transforming data

# Extracting and transforming ERP data with Zero Copy Connector for ERP extraction tables {#ariaid-title1}

Release version: Brazil  
Updated October 22, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Use ERP extraction tables in Zero Copy Connector for ERP to schedule processes that extract large volumes of ERP data into local tables on the ServiceNow AI Platform. Then the data is transformed with table maps and can be used in ERP models and applications.

## Data in extraction tables {#erp-canvas-extraction-tables__section_vwd_2s4_cyb}

Use extraction tables, which are ETL (extract, transform, and load) data sources, to extract large amounts of data regularly.

For example, you can extract all open purchase orders for the current month from an SAP system into a Glide table once a day at a set time. You can then access that data through ServiceNow AI Platform, such as Source-to-Pay Operations or a PO workspace created in App Engine Studio.

After the extraction process is run, use import sets to map imported data into ServiceNow AI Platform tables. For more information, see [Import sets](https://www.servicenow.com/docs/D6zgromoT3xYW7pLsMx4Ew "Import sets enable administrators to import data from various data sources, and then map that data into ServiceNow tables.").

## Extraction tables use transform table maps {#erp-canvas-extraction-tables__section_ubh_5ml_gyb}

ERP extraction tables save data to a local transform table on the ServiceNow AI Platform. The transform table is a temporary table that holds data during the data integration or transformation process. Transform tables are an intermediary step before data is further processed, cleaned, or loaded into the target destination. For example, after import, the extraction table can run a Glide query on a transform table and save the output to several different target
tables.

If you use a custom transform table, you must first create the table on the ServiceNow AI Platform, and the table must be in the application scope. For more information on creating table transform maps, see [Create a transform map](https://www.servicenow.com/docs/MuV3GRK2YbgAZ1yFS6K_Pg "Every import operation to a production table requires at least one transform map associated with an import set.").

ETL processes in Zero Copy Connector for ERP (Enterprise Resource Planning) are configured in the ServiceNow AI Platform app that needs the data, not Zero Copy Connector for ERP. For example, you can configure an extraction process in a flow in Workflow Studio.

## Automatically available standard extraction tables {#erp-canvas-extraction-tables__section_grc_hs4_cyb}

When you install Zero Copy Connector for ERP, the ServiceNow AI Platform automatically loads a standard set of ERP extraction tables, including sales, delivery, and procurement tables. For a list of standard extraction tables, see [Standard extraction tables for Zero Copy Connector for ERP](https://www.servicenow.com/docs/6t~Ucn36Zk~StO_N~bTA8g "Zero Copy Connector for ERP provides standard extraction tables that you can link to enterprise resource planning (ERP) models.").

If you installed ERP Semantic Mining, that app populates some additional extraction tables, such as ERP application activity, Collector directory data, and Namespace data.  
Important:  
Starting with the Zurich release, ERP Semantic Mining is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported.