--- sourceDocument: Australia Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications Release : - australia ft:locale : - en-US ft:publication_title : - Australia Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Models # Exploring Zero Copy Connector for ERP models {#ariaid-title1} Release version: Australia Updated August 5, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Exploring Zero Copy Connector for ERP models Zero Copy Connector for ERP enables ServiceNow customers to build ERP models that define how to read, update, and create data within connected ERP systems. These models represent the logical structure of ERP data, including tables, fields, operations, and relationships, allowing seamless interaction with ERP data in ServiceNow. Once configured, models serve as reusable data sources for various ServiceNow components such as apps, flows, playbooks, and workspaces. Show full answer Show less ## Key Features * **Model Types:** Supports ERP models that mirror external ERP data structures and platform models that map ERP data into ServiceNow's AI Platform tables for standardized integration. * **Custom and Standard Models:** Includes prebuilt standard models and allows creating custom models from scratch or cloning existing ones. * **Operations:** Each model supports one read, one update, and one create operation using suitable methods like table reads, BAPIs, RFC, OData, IDoc, or REST APIs depending on the ERP capabilities. * **Security and Data Control:** Input and output parameter mapping enables selective field use, excluding sensitive fields from remote or extraction tables before data transmission. * **Integration Flexibility:** Models act as universal integration points usable across Workflow Studio flows, ServiceNow Studio, Workspace Builder, UI Builder, Table Builder, and playbooks, eliminating the need for multiple custom integrations. ## Practical Use Case For example, a developer building a vendor management application can create a single vendor model connected to an SAP system. This model defines operations to read vendor details via RFC/BAPI, update payment terms using OData, and create vendor records with a BAPI. The model then serves as the data source for workflows that automate vendor data retrieval, approval routing, and updates directly back to SAP, reducing manual ERP system access. Build ERP (Enterprise Resource Planning) models in Zero Copy Connector for ERP to create read, update, and create operations and organize mirrored ERP data. In Zero Copy Connector for ERP, a **model** is the foundational building block for accessing and working with ERP data. It represents the logical structure and organization of data coming from the ERP system. A model defines the tables, fields, read/update/create operations, and table join relationships that capture a specific business process or dataset. After you configure a model, you can use it as a data source for building apps, flows, playbooks, workspaces, and more. Zero Copy Connector for ERP supports two types of models: * ERP models follow the data structures defined by the external ERP system itself, accommodating the unique formats of each connected system. * Platform models map ERP input and output fields to existing ServiceNow platform tables, standardizing ERP data into the data structure of the ServiceNow AI Platform for tighter integration. {#exploring-erp-models__ul_e3h_km2_cjc} Zero Copy Connector for ERP includes a standard set of models and supports creating custom models from scratch or cloning existing ones. Each model connects to one ERP system, and each model can have only one read operation, one update operation, and one create operation defined. Operations use one of several underlying methods depending on the type of operation and what the connected ERP system supports. ## Key benefits {#exploring-erp-models__section_ytd_53z_j3c} Models create a consistent, reusable data layer. You can connect the same ERP table to multiple models, and build as many models as needed to represent different business areas. Through input and output parameter mapping, you define which ERP fields are used and what the model sends back to the ERP system on reads, updates, and creates. This means sensitive fields never reach remote or extraction tables. The fields are excluded at the model level before any data flows. Models support a range of underlying connection methods (table reads, BAPIs, RFC, OData, IDoc, and REST APIs). You can match the method to what's available and appropriate for the ERP module and operation type you're working with. After a model is ready and its operations are configured, use it as a data source across Workflow Studio flows, ServiceNow Studio, Workspace Builder, UI Builder, Table Builder, and playbooks. This makes models a universal integration point rather than something custom-built for a single use case. ## Use case {#exploring-erp-models__section_egy_53z_j3c} A developer is building a vendor management application and needs to retrieve vendor data from SAP, enable updates to vendor payment terms, and create vendor records. Instead of building three separate integrations, the developer creates a single vendor model connected to the appropriate SAP system. In the model manager, they add three operations: * A read operation using an RFC/BAPI entity to retrieve vendor details. * An update operation using OData to write payment term changes back to SAP. * A create operation using a BAPI to create vendors. {#exploring-erp-models__ul_lyj_bhg_dkc} The developer uses the model as the data source for a Workflow Studio flow that triggers when a new vendor request is submitted. The flow automatically reads existing vendor data, routes through an approval, and writes the approved changes directly back to the SAP system. No one needs to log in to the SAP system directly.