ERP data extraction and transformation

  • Release version: Australia
  • Updated June 8, 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 ERP data extraction and transformation

    The ERP data extraction and transformation capabilities in ServiceNow's Zero Copy Connector for ERP enable customers to efficiently extract, transform, and load (ETL) large volumes of ERP data on a regular basis. This data is stored in local transform (staging) tables within the ServiceNow AI Platform, facilitating further processing, cleaning, and integration into ERP models or remote tables. These processes support business functions such as procurement, sales, and delivery by providing timely and accessible ERP data within the ServiceNow environment.

    Show full answer Show less

    Key Features

    • Extraction Tables: Specialized tables designed to hold large data extracts from ERP systems (e.g., SAP) daily, such as open purchase orders for the current month.
    • Transform Tables: Temporary staging tables within the ServiceNow AI Platform that store extracted data before it is processed or mapped to target tables. Custom transform tables must be created within the appropriate application scope.
    • Standard Extraction Tables: Automatically installed with Zero Copy Connector for ERP, covering common ERP domains like sales, delivery, and procurement. Additional extraction tables are available if ERP Semantic Mining is installed, though this app is being deprecated starting in the Zurich release.
    • Configurable ETL Processes: ETL workflows are configured within the ServiceNow AI Platform applications (e.g., via Workflow Studio flows), not directly in the Zero Copy Connector, allowing tailored integration to meet specific business needs.
    • Field Selection: Ability to add or remove fields in extraction tables to customize data extracts and exclude sensitive information as needed.
    • Scheduling: Regular scheduling of data extraction jobs to ensure up-to-date ERP data is consistently available.
    • Monitoring: Tools to track progress and errors in ERP extraction transactions, enhancing operational visibility and troubleshooting.

    Key Outcomes

    • Reliable daily extraction of large ERP datasets enables integration of ERP information into ServiceNow AI Platform applications, enhancing business insights and automation.
    • Temporary transform tables ensure data quality and facilitate complex transformations before data populates target tables.
    • Standard extraction tables provide out-of-the-box data structures for common ERP data domains, speeding deployment.
    • Customizable extraction and transformation configurations allow ServiceNow customers to tailor data flows to their organizational requirements while maintaining data security.
    • Scheduled extraction and monitoring capabilities support consistent data availability and operational oversight.

    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 a standard set of ERP extraction tables, including 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.