> For the complete documentation index, see [llms.txt](https://servicenow-lf.gitbook.io/the-workflow-data-fabric-loom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://servicenow-lf.gitbook.io/the-workflow-data-fabric-loom/main-exercises/lab-exercise-zero-copy-connectors.md). # Lab Exercise: Zero Copy Connectors [Take me back to main page](/the-workflow-data-fabric-loom/readme.md) This lab will walk you through integration of data coming from Cloud Data Warehouses and ERP using Zero Copy Connectors (ZCC) for SQL and ERP respectively. ## Lab Sections and Objectives

Step	Who	Description
1	Facilitator	Context Setting: Review the data flow diagram showing how ServiceNow consumes data from Cloud Data Warehouses and ERP systems via Zero Copy Connectors for SQL and ERP.

**Preparation**

Step	Who	Description
2	Student	Platform Configuration: Complete Integration Hub platform configuration if not done. Assign `sn_erp_integration.erp_admin` role to admin user.

**Zero Copy Connector for ERP**

Step	Who	Description
3	Student	ZCC for ERP Workspace: Navigate to Zero Copy Connector for ERP Home. Explore the workspace layout.
4	Student	Clone ERP Data Product: Clone the OOTB DP: Cost Center model. Label it SAP Cost Center. Assign ERP system S4D.
5	Student	ERP BAPI Entity: Review the BAPI_COSTCENTER_GETDETAIL1 entity. Explore Specify Inputs and Choose Outputs configurations.
6	Student	ERP Extraction Tables: Filter and review SAP Cost Center extraction table. Navigate to the target table containing Cost Center Master Data from SAP.

**Zero Copy Connector for SQL**

Step	Who	Description
7	Student	Cloud Data Warehouse Source: Review screenshot of the Snowflake source table used for Zero Copy for SQL (no backend access provided).
8	Student	ZCC Connection Review: Navigate to Workflow Data Fabric Hub. Review the established Snowflake connection details.
9	Student	Configure Column Mappings: Create a data fabric table from the Snowflake data asset. Set Cost Center as a Reference field to the ERP extraction table. Set GL Account as primary key.
10	Student	Open Data Fabric Table: View the data assets created and open the data fabric table contents.

**AI Agent and Finance Operations Workspace**

Step	Who	Description
11	Student	AI Agent Walkthrough: Open AI Agent Studio. Review the Forecast Variance agent: specialty, tools, security controls, trigger (blank), and channel settings. Save and test.
12	Student	Test AI Agent: Enter test prompt to process an expense event. Review planning steps, cost center and vendor extraction, RAG search results, and Finance Case creation.
13	Student	Verify the Finance Case: Navigate to Finance Operations Workspace. Find the case created by the agent.

Step	Who	Description
14	Facilitator	Conclusion: Walk through the complete data flow chain showing how Zero Copy Connectors bring external data into ServiceNow for AI Agent-driven case management.

## Data flow The data flow below shows how ServiceNow consumes data from the local Expense Transaction Event table populated by REST API events. The events processed can be near-real-time or historical (e.g. transaction events after over a period of time). Aside from local tables, ServiceNow will also consume external data from a Cloud Data Warehouse and an ERP system via ZCC for SQL and ERP respectively. The data taken from the external sources will be used by an agent which will also create Finance Cases for Cost Centers which are going over budget. While majority of the workflow is handled deterministically, AI Agents will provide additional context by searching and comparing expenses and cost center histories to enrich the workflow data that will be used by the personnel in charge of the cost centers. **Note**: future versions of this lab will include ServiceNow Enterprise Graph which will provide a universal query functionality that brings together the various internal and external data sources. As of Jan-2026, said feature is not globally available and is hence not yet included in this lab. {% @mermaid/diagram content="graph TB subgraph "User Interaction Layer" Employee((Employee/
Finance Manager)) EC\[Employee Center or
Workspace with Now Assist] end ``` subgraph "External Systems" ERP[(ERP System
OData Endpoint)] CDW[(Cloud Data
Warehouse)] end subgraph "ServiceNow AI Platform" subgraph "Data Integration Layer" ZeroCopySQL[Zero Copy SQL
Connection] ZeroCopyERP[Zero Copy ERP
Connection] end subgraph "Zero Copy Tables - Read Only" ZCCC[(Cost Centre)] ZCCH[(Cost Centre
History)] ZCExp[(Expenses)] end subgraph "ServiceNow Native Tables" ExpenseTable[(Expense Event
Line Items
Scoped Table)] FinCase[(Finance Case
Table)] end subgraph "AI & Automation" Agent1[Agent: Over-Budget
Case Creator
Zero Copy Source] RAG[RAG - Retrieval
Augmented Generation] FlowAction[Flow Action] end end %% Data Flow Connections ERP -->|OData Feed| ZeroCopyERP CDW -->|Data Fabric table| ZeroCopySQL ZeroCopyERP --> ZCCC ZeroCopySQL --> ZCCH ZeroCopySQL --> ZCExp %% Agent 1 Workflow - Zero Copy Source ZCCC -->|Query Over-Budget| Agent1 ZCCH -->|Historical Data| Agent1 ZCExp -->|Expense Details| Agent1 ExpenseTable -->|Search Similar Cases| Agent1 Agent1 -->|Create Case| FinCase Agent1 <-->|Trend Analysis| RAG Agent1 <-->|Flows/Subflows/Actions| FlowAction %% User Interaction Connections Employee -->|Ask Questions
View/Update Cases| EC EC -->|Search & Query| FinCase %% Styling classDef external fill:#2196F3,stroke:#1565C0,stroke-width:2px,color:#fff classDef user fill:#F5F5F5,stroke:#616161,stroke-width:3px,color:#1a1a1a classDef nowassist fill:#FFB300,stroke:#F57F17,stroke-width:2px,color:#1a1a1a classDef platform fill:#4CAF50,stroke:#2E7D32,stroke-width:2px,color:#fff classDef wdf fill:#9C27B0,stroke:#6A1B9A,stroke-width:2px,color:#fff class ERP,CDW external class ZeroCopySQL,ZeroCopyERP wdf class ZCCC,ZCCH,ZCExp wdf class ExpenseTable,FinCase platform class Agent1,RAG nowassist class FlowAction platform class Employee,EC user" %} ``` > **Color Legend:** 🟡 Now Assist | 🟢 Platform | 🟣 Workflow Data Fabric | 🔵 External Systems | ⚪ User Interaction > [📊 View High-Resolution Diagram](https://raw.githubusercontent.com/leojacinto/WorkflowDataFabric-TypeA/main/.gitbook/assets/dataflow_zero_copy_connectors.png) ## Preparation ### Preparation: Platform Configuration Complete Integration Hub platform configuration if not done. Assign `sn_erp_integration.erp_admin` role to admin user. 1. If you have not done [Lab Exercise: Integration Hub](https://servicenow-lf.gitbook.io/the-workflow-data-fabric-loom/lab-exercise-integration-hub) yet, do the needed [Preparation: Platform Configuration](https://servicenow-lf.gitbook.io/the-workflow-data-fabric-loom/lab-exercise-integration-hub#preparation-platform-configuration) steps. 2. Make sure you are logged in as **admin** user. 3. Navigate to **All** > **a.)** type **Users and Groups** > **b.)** click on **Users and Groups > Users**.

4. Search for **a.)** **System Administrator** then hit **Return/Enter ↵** > **b.)** click on **admin**.

5. In the **Roles** tab, click **Edit**.

6. Search for **a.)** **sn\_erp\_integration.erp\_admin** > **b.)** click on **sn\_erp\_integration.erp\_admin** > **c.)** click on **>** to move the role to the right panel > then **d.)** click **Save**.

7. You will get **a.)** messages such as **Adding Role decision\_table\_reader to admin**, there will be 4 of such messages > **b.)** right-click on the top panel and click **Save**.

8. **IMPORTANT**. Log out and log back in.

## Zero Copy Connector for ERP ### Walkthrough: Explore ZCC for ERP Workspace This provides the steps needed to connect ServiceNow to the ERP system to obtain Cost Center Master data. 1. Navigate to All > **a.)** type **Zero Copy Connector for ERP Home** > **b.)** click **Zero Copy Connector for ERP Home**.

2. The **Zero Copy Connector for ERP Home** is a workspace which has the layout as below.

### Hands-on: Clone ERP Data Product for Cost Center Clone the OOTB DP: Cost Center model. Label it SAP Cost Center. Assign ERP system S4D. 1. Click on **a.)** **Models (database icon)** > **b.)** click **Model Name** > **more (vertical three dots)** > **c.)** type **DP: Cost Center** > **d.)** click **Apply**. We will replicate the structure of this OOTB data model.

2. Click on **DP: Cost Center** with Short Description **Data Product: Cost Center ( Function Call )**.

3. Note the **a.)** popup that indicates that you are opening an **ERP Data Product** which is delivered as OOTB templates that customers can use to ramp-up creation of ERP models, which means it cannot be edited. Click **b.)** **Clone** to create a copy of this model.

4. Provide the label for the cloned model as **a.)** **SAP Cost Center Lab** and take note of the Target application which should be **b.)** **Forecast Variance**. Click **c.)** Clone this model once done.

5. After cloning the model you will be directed to its configuration screen. Assign the **a.)** ERP system name as S4D then **b.)** click Save. This will set up your model to use an ERP system that the ServiceNow instance is integrated to via Connections & Credentials. Then, **c.)** click **Manage model**.

### Walkthrough: Explore ZCC for ERP BAPI Entity Review the BAPI\_COSTCENTER\_GETDETAIL1 entity. Explore Specify Inputs and Choose Outputs configurations. 1. Click **Read** to use a read-only operation configured in the model. ZCC for ERP models can also perform **Update** and **Create** actions.

2. There is a BAPI already included in the **DP: Cost Center** model you have cloned earlier. The entity **BAPI\_COSTCENTER\_GETDETAIL1** is already configured here so you do not have to do anything. As mentioned earlier, there are other ways to obtain master data from SAP (whether it is Cost Center, Materials, etc.) such as RFC table reads or OData endpoints.

3. Click on **Specify Inputs**. You do not need to do anything in this screen. The intent is to provide an overview of what can be configured as fields for selections when extracting or displaying information from the ERP system. If the table, BAPI, or OData endpoint supports it, this screen can also be left blank which is an equivalent of selecting all rows/records when executing the **Read** action.

4. Click on **Choose outputs**. You do not need to do anything in this screen. The intent is to provide an overview of what can be configured as the output for your selection or extraction. Both **Specify inputs** and **Choose outputs** sections can be intimidating for non-SAP practitioners which led to the creation of the **Data Product** we cloned in **Step 5**. Find out more about [**ERP Data Products here**](https://store.servicenow.com/store/app/9a0ad9f41b19e650396216db234bcba9).

### Walkthrough: Explore ZCC for ERP Extraction Tables Filter and review SAP Cost Center extraction table. Navigate to the target table containing Cost Center Master Data from SAP. 1. Go to **a.)** **Extraction tables (Sankey diagram icon)** and click **b.)** **Name** > **more (vertical three dots)** > **c.)** type **SAP Cost Center** and **d.)** click **Apply**. **Extraction tables** are used as persistence layer for **ERP models**, i.e. data is stored here from Extract Transform Load (ETL) processes as an alternative to reading ERP data via Zero Copy. This is useful especially if the ERP table you are connecting to has millions of rows OR are not frequently updated. In our use case, while cost center master data is relatively small in many customer environments, they do not change frequently.

2. Click on **SAP Cost Center**.

3. There is a notification stating that **a.)** the object is in the **Zero Copy Connector for ERP application**, this is expected. Note that the **b.)** **ERP model** used here is different from what you have created earlier, this uses **SAP Material Transfer Cost Center**, this configuration is expected. This discrepancy is because we are not connected to a live SAP system for this exercise. The tools and configurations you have used are representative of a real SAP integration. Finally, **c.)** click on the **Target table link** which is **sn\_erp\_integration\_cost\_center\_list.do**.

4. This will lead to the extraction table which contains **Cost Center Master Data** from SAP. This exercise uses an extraction scenario where data from SAP is stored in ServiceNow.

5. Congratulations! You have set-up the integration to a Cloud Data Warehouse using Zero Copy Connector for ERP. ### Additional Reading: Direct online read for ZCC for ERP 1. Direct online read is also possible with more details found on the blog post [Zero Copy Connector for ERP guide by Leo Francia in the ServiceNow community](https://www.servicenow.com/community/app-engine-for-erp-blogs/part-1-of-4-intelligent-erp-workflows-get-sap-data-into/ba-p/3192800). ## Zero Copy Connector for SQL ### Reference: Cloud Data Warehouse Source This provides the steps needed to connect ServiceNow to the Cloud Data Warehouse and get summary data needed for workflow context and logic. 1. For reference purposes only, the table which will be used as source for Zero Copy for SQL coming from Snowflake is shown below. No action needs to be done for this step.

### Walkthrough: Navigation and Review of ZCC Connection Navigate to Workflow Data Fabric Hub. Review the established Snowflake connection details. 1. **If you are on Zurich:** In the ServiceNow navigation, go to All > **a.)** type **Workflow Data Fabric Hub** > **b.)** go to **Workflow Data Fabric Hub**.

2. **If you are on Australia:** In the ServiceNow navigation, go to All > **a.)** type **Workflow Data Fabric Hub** > **b.)** go to **Workflow Data Fabric > Connect Hub**.

3. In the landing page, go to **Established connections** > **Snowflake Connection (S)**. **Note:** this established connection is configured specifically for instances used in ServiceNow-led labs.

4. In the **Connection details** tab of the screen that immediately follows, the established connection is configured as shown in the screenshot below. No action needs to be done for this step. You might also get a notification stating **This connection is read-only in the 'Forecast Variance' application scope...** which can be ignored.

### Hands-on: Configure Column Mappings Create a data fabric table from the Snowflake data asset. Set Cost Center as a Reference field to the ERP extraction table. Set GL Account as primary key. 1. Go to **a.)** Data assets > **b.)** beside **u\_lab\_cc\_summary** click **Create data fabric table**. This screen shows the data assets available for the **Database** and **Warehouse** you configured in the previous screen. In this example, only two tables exist in the database **WDF\_DEMOHUB**.

2. Provide the information needed for **a.)** the **Label** e.g. **cc\_summ\_\** and the **b.)** **Name** which will automatically provided. **Note:** keep the name length not more than 35 characters such as what is listed below, e.g. **x\_snc\_forecast\_v\_0\_df\_cc\_summ\_lfr**. Click **c.)** **Continue** once done. This will create the data fabric table (hence the df prefix) which will contain only the field and mapping information to the Snowflake table, it will not store the data from Snowflake into ServiceNow. While the intent of setting this up is mainly to show Zero Copy capability, this has multiple advantages such as ensuring cost center summary data from source is up to date as well as avoiding offline copies of the same information (e.g. via managed file transfer) which can result into data breaches.

3. In the screen that immediate follows, click on the tick box beside **Name** and this will include all the fields from the Snowflake data asset to the data fabric table being configured. Customers also have the option to select only the columns needed to speed up loading of data fabric tables.

4. Look for **Cost center** column > change the data type from **String** to **a.)** **Reference** and click **b.)** **Reference** to set the table from which **Cost center** column will refer to. A **Reference** field points to a record in an existing table, so users select from a controlled set instead of typing freehand. This keeps your data consistent and traceable, which matters most when the field drives downstream process logic.

5. In the modal pop-up that appears, select the table **sn\_erp\_integration\_cost\_center** which you have set-up in the ZCC for ERP lab exercise.

6. In the same modal pop-up, select **Cost Center**.

7. Once completed, click **Set Reference**. This will create the reference to the cost center details from SAP.

8. Finally, set GL account as the **Primary** key as shown in the **a.)** toggle below. Click **b.)** **Finish** once done.

9. A pop-up dialog indicating that a primary key has been defined. Click **Confirm**. A primary key lets you distinguish unique records from the source data warehouse, which becomes important in complex analysis.

### Walkthrough: Open Data Fabric Table View the data assets created and open the data fabric table contents. 1. This will lead you to a screen showing the data assets created. In the same screen, click on the **a.)** three vertical dots then **b.)** **Open list** to see the contents of the table.

2. This will lead you to the data fabric table.

3. Congratulations! You have set-up the integration to a Cloud Data Warehouse using Zero Copy Connector for SQL. ## AI Agent and Finance Operations Workspace ### Walkthrough: Custom Forecast Variance AI Agent This is a walk through of how an AI Agent equipped with both deterministic and probabilistic capabilities can automate research and validation of cost center history and expenses as well as creation of Finance Cases should cost centers be above their budget allocations. **Note:** this is a custom AI agent pre-configured in the lab instance provided in ServiceNow-led lab sessions; this is not a pre-built agent. 1. Go to All > type **x\_snc\_forecast\_v\_0\_expense\_transaction\_event.list** and hit **Return/Enter ↵**.

2. This will lead to the screen below. Note that this is the table created in [Lab Exercise: Fundamentals](/the-workflow-data-fabric-loom/main-exercises/lab-exercise-fundamentals.md) and populated with the data from [Lab Exercise: Integration Hub](/the-workflow-data-fabric-loom/main-exercises/lab-exercise-integration-hub.md).

3. After reviewing the table, navigate to All > **a.)** type **AI Agent Studio** > **b.)** click on **Create and Manage**.

4. This will go to the list of workflows and agents. Go to **AI agents** tab > **a.)** click **search (magnifying glass)** > **b.)** type **Forecast Variance** and hit **Return/Enter ↵**.

5. You might get multiple results so only get the one which says **Forecast Variance** only.

6. Click on **Define the specialty**. This shows all the instructions for this AI Agent created in plain English. The **List of steps** describes the sequence, purpose, and nuances of the tools configured, which are shown in the next section. No further action is required in this section.

7. Next, click on **Add tools and information**. This is a collection of **Search retrievals** and **Subflows** that are used by the agent. The purpose and sequence of these tools are also described in the section **Define the specialty**. No further action is required in this section but feel free to explore the configurations of each of the tools.

8. Under **Define security controls** > **a.)** click **Define data access** > **b.)** select **Dynamic user** from the drop down then > **c.)** add **admin** user as the approved role. For this exercise we are using permissive authorisations but this is where you can tighten authorisations for your agents allowing mechanisms such as inheriting the authorisations of logged in user (Dynamic identity type) or a predefined set of access (AI User identity type).

9. Next, click on **Define trigger**, which is kept blank. You can add the triggers for the AI Agent here but for the exercise, the AI Agent will be triggered manually to be able to show the detail chat responses and debugging. No further action is required in this section.

10. Finally, click on **a.)** **Select channels and status**. This configures the availability of the AI Agent. In this case, it is enabled and can be accessed using **b.)**** Now Assist panel** toggled on as well as via **c.)**** Now Assist in Virtual Agent** added as chat assistant. Click **d.)**** Save and test**. **Note:** if Chat Assistants (step **10.c.**) does not give you options, check and execute the steps in [Lab Exercise: Integration Hub > Platform Configuration](https://servicenow-lf.gitbook.io/the-workflow-data-fabric-loom/main-exercises/lab-exercise-integration-hub#preparation-platform-configuration) > Steps 9 to 18; esp. if you are doing this lab standalone or have skipped the [Lab Exercise: Integration Hub](https://servicenow-lf.gitbook.io/the-workflow-data-fabric-loom/main-exercises/lab-exercise-integration-hub) portion.

### Hands-on: Test and review Custom AI Agent Enter test prompt to process an expense event. Review planning steps, cost center and vendor extraction, RAG search results, and Finance Case creation. 1. You will be directed to the Test AI reasoning tab. To proceed with testing, **a.)** type **Help me process EXP-2025-IT-002-1007-01** and **b.)** click **Continue to Test Chat Response**.

2. Wait for the test to complete which is indicated by an **End** with a check mark. Once that is completed, you can explore the following sections. These automations help assess and review cost centers which are exceeding budget proactively instead of waiting at the end of reporting cycles. **a.)** Expand **Planning the next steps** to see the tools used. **b.)** Note the **cost\_center** and **vendor** extracted from the expense event. **c.)** You can access the result of the **Retrieval-augmented Generation (RAG) search** and click on the links if you wish. This step helps you check relevant entries for the cost center associated with the expense event so you can do further investigation if needed. **d.)** You can also access the **RAG search** results for the vendors associated with the expense event. **e.)** Finally, if the expense event will lead to the associated cost center being over budget, the total cost center expense and the **Finance Case** created for exceeding the budget for further review and action is listed. In this case it is FINC0010003.

3. The right panel of the same screen shows the **AI agent decision logs** for debugging purposes.

### Completion: Verify Finance Case Navigate to Finance Operations Workspace. Find the case created by the agent. 1. Navigate to Workspaces > **a.)** type **Finance Operations Workspace** and click on the **b.)** workspace with the same name.

2. For this exercise, we are not impersonating a persona so you remain as the System user.

3. Go to **a.)** **list (list icon)** > **b.)** **Lists** > **c.)** sort by **Number** descending/ascending > **d.)** or look for the Finance case created by the AI Agent, FINC0010003 in the example above.

## Conclusion Congratulations! You have created the **Workflow Data Fabric** integrations that powers the **Financial Forecast Variance Agent** allowing proactive creation of cases based on multiple data sources in a complex landscape to allow proactive management of budgets. ## Next step Let us continue building the data foundations for AI Agents to use. The next suggested exercise is the creation of the External Content Connector to SharePoint. [Take me back to main page](/the-workflow-data-fabric-loom/readme.md)