Extracting and transforming data in Zero Copy Connector for ERP

  • Release version: Zurich
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Extracting and transforming data in Zero Copy Connector for ERP

    The Zero Copy Connector for ERP enables ServiceNow customers to extract large volumes of ERP data regularly using extraction tables, which serve as ETL (extract, transform, load) sources. Extracted data is stored temporarily in transform tables on the ServiceNow AI Platform, facilitating data integration and transformation before loading into target tables. This process supports daily data refreshes to power ERP models and applications such as Source-to-Pay Operations and PO workspace in App Engine Studio.

    Show full answer Show less

    Key Features

    • Extraction Tables: Used to hold and extract large datasets like open purchase orders from ERP systems (e.g., SAP) on a scheduled basis. These tables are automatically available upon installing Zero Copy Connector for ERP, including standard ERP data tables for sales, delivery, and procurement.
    • Transform Tables: Temporary staging tables on the ServiceNow AI Platform that hold extracted data during ETL processing. Custom transform tables must be created within the platform’s application scope.
    • Transform Maps: Enable mapping of source fields from extraction tables to target fields in ServiceNow tables to facilitate data processing and integration.
    • Scheduling: Supports scheduling of regular extractions to keep ERP data current within ServiceNow applications.
    • Monitoring: Provides transaction tracking and error logging capabilities to oversee the extraction and transformation workflows.
    • Configuration Location: ETL processes are configured within the ServiceNow AI Platform app requiring the data, not directly in the Zero Copy Connector for ERP. For example, workflows can be created in Workflow Studio.
    • ERP Semantic Mining: Adds additional extraction tables but is being deprecated starting with the Zurich release, remaining supported but hidden in new instances.

    Key Outcomes

    • Enables automated daily extraction of large ERP datasets into ServiceNow for real-time or near-real-time operational use.
    • Facilitates data transformation and cleansing through transform tables and maps before loading into target ERP models or remote tables.
    • Supports customization by allowing adding or removing fields in extraction tables to comply with data privacy or business needs.
    • Improves data reliability and operational insight through monitoring of extraction transactions and error logs.

    ERP (Enterprise Resource Planning) extraction tables enable you to create daily processes that extract large amounts of data. You can then include the extracted data in an ERP model in Zero Copy Connector for ERP.

    Hold large amounts of data in extraction tables

    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 via 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.

    Extraction tables use transform table maps

    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.

    ETL processes in Zero Copy Connector for ERP 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

    When you install Zero Copy Connector for ERP, the ServiceNow AI Platform automatically loads standard ERP extraction tables for you to work with. For example, sales, delivery, and procurement tables. For a list of standard extraction tables, see Standard ERP models and extraction tables for Zero Copy Connector for ERP.

    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.