Zero Copy Connector for ERP - Content Packs Overview

NatashaBanerje · 4 hours ago

WORKFLOW DATA FABRIC

ZCC for ERP Content Packs:
what they are, where to find them, and how to get moving

You have ZCC for ERP installed and a SAP connection ready. The next question is usually the same: where do I actually start? Content packs answer that. They are pre-built collections of ERP models and process extensions, grouped by business process area, so you are not configuring every SAP entity from scratch before you can build anything useful.

What are content packs?

An ERP model defines how ServiceNow connects to a specific SAP entity. It specifies the entity (say, a Purchase Order), the protocol to use (RFC/BAPI or OData V2), and which operations are available: Read, Create, or Update. The model reaches directly into your live SAP system. Nothing needs to be copied or staged in ServiceNow.

A content pack is a curated set of models for a specific business process area. Install from the ServiceNow Store, explore what is included, clone the pieces you need, and build from there.

A note on how content packs work

Models in a content pack are read-only. To use one in a workflow, you clone it into your application scope. That clone is fully editable. The original stays intact as a reference you can always return to.

Four content packs. Four process areas.

Each content pack covers a different area of your SAP landscape. Here is what each one includes and when to reach for it.

Enterprise Data Foundation

Hire to Retire

Quote to Cash

Source to Settle

Enterprise Data Foundation

Master and reference data, SAP-wide

Most SAP-connected workflows need foundational data before they can do anything useful: which cost center? Which plant? Which vendor? This pack covers that layer - the reference and master data objects your flows will call on repeatedly, regardless of which SAP module the workflow touches.

What's inside

Master data models cover Business Partners, Vendors, Materials, Cost Centers, G/L Accounts, and Profit Centers, with Create, Update, and Read operations for most objects.

SAP Foundation models cover the cross-module reference data your other models depend on: plants, payment terms, currencies, purchasing groups, storage locations, and more. Think of these as the SAP lookup layer.

A good starting point if

You are building workflows that span multiple SAP modules, or you need common SAP reference data available across several flows. Most teams install this one first.

View Enterprise Data Foundation on the ServiceNow Store

Hire to Retire

Employee lifecycle data, live from SAP

If your HR system of record is SAP HCM or SuccessFactors, this pack gives your ServiceNow workflows direct access to the employee data they need: positions, org structures, employee records. The data stays in SAP HCM or SuccessFactors. ZCC for ERP can read it in real time, and approved changes can be written back through SAP's own business logic and authorisation checks.

What's inside

Employee data models cover positions, org structure, and employee records from SAP SuccessFactors and SAP HCM, with Read and where applicable Write operations.

A good starting point if

You are building HR Service Delivery workflows in ServiceNow that depend on live SAP employee data, and you want to stop relying on manual lookups or maintaining a sync between the two systems.

View Hire to Retire on the ServiceNow Store

Quote to Cash

Live sales order data in customer-facing workflows

Sales orders, delivery blocks, credit limits, customer invoices: this is the data customer service and order management teams need to act on exceptions and answer questions, but usually cannot get without calling a SAP user or logging in themselves. This pack brings those objects into ServiceNow workflows directly, with Create, Update, and Read operations where available.

What's inside

Sales order models cover Create, Read, and Update, plus search by customer and search by status. Credit Memo Requests, Customer Credit Limits, Customer Invoices, and Outbound Deliveries are also included.

A good starting point if

You are building workflows for customer-facing or order management teams who have no way to view or act on SAP order data without a SAP login.

View Quote to Cash on the ServiceNow Store

Source to Settle

Procurement decisions, running on live SAP data

Procurement approvals stall when approvers have to log into SAP to check PO details. This pack gives approval and exception-handling workflows in ServiceNow direct access to the procurement data they need. Approvers see live SAP data, make the call, and outcomes can be written back to SAP - without anyone needing a SAP login to complete the task.

What's inside

Purchase order models cover item-level detail and full PO lists. Both RFC/BAPI and OData V2 variants are available for some objects, so you can choose the access pattern that fits your SAP environment.

Procurement models also cover Purchase Requisitions and Purchasing Info Records.

A good starting point if

You are building a procurement approval flow and want approvers to see live SAP PO details in ServiceNow. Procurement approvals tend to be one of the faster ZCC for ERP use cases to take from build to production.

View Source to Settle on the ServiceNow Store

Before you install

Each content pack is a separate install from the ServiceNow Store. You can install one or all four depending on which process areas apply to you. Before installing, check that you have:

1. Zero Copy Connector for ERP installed on your ServiceNow instance
2. A linked SAP system configured in ZCC for ERP
3. The sn_erp_integration.erp_admin role assigned to your user

How to use a content pack

Once installed, here is how to start working with it.

STEP 1

Find the models

Go to All > Zero Copy Connector for ERP > Zero Copy Connector for ERP Home and open the ERP Models page. Content pack models are labeled with "CP:" at the start of their name.

STEP 2

Explore before you clone

Select a model to review its entities, field mappings, and available operations. This gives you a clear picture of what the model does before committing to it.

STEP 3

Clone the model

Select Clone now, give the clone a name, confirm the target application scope, and save. The original stays read-only. The clone is yours to adapt.

STEP 4

Adapt if needed

Open the cloned model and select Manage model to review operations and entity mappings. Adjust them to match your SAP environment.

STEP 5

Use it in Flow Designer

Wire the cloned model into your flow using the Use ERP Data action. From this point it works exactly like any other ZCC for ERP model.

One thing to know

Content packs are accelerators for ZCC for ERP. They are not a limit on what the connector can access. You can build custom models for any SAP entity using RFC/BAPI, OData V2, or IDoc through the ERP Model Manager, and they work exactly the same way once configured. No coding required on either side. If a content pack does not cover the exact SAP entity your team uses, a custom model is the next step.

New to ZCC for ERP, or looking to get started?

If this is your first time exploring ZCC for ERP, our Quick Start Guide walks you through what it is, how it works, and how to get your first connection up and running.

Read the Quick Start Guide

Have questions? We'd love to hear from you.

Drop your questions or comments below and someone from our team will get back to you. Whether you are just exploring ZCC for ERP or already working through a specific use case, we are here to help.