- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2 hours ago - edited 2 hours ago
Onboarding vendors into S/4HANA with Zero Copy Connector for ERP
From request to ready-to-pay: ZCC for ERP runs the whole onboarding on ServiceNow while the Business Partner is created directly in S/4HANA, with no middleware, no data copies, and no manual re-keying.
What is vendor onboarding in SAP?
In S/4HANA the vendor is a Business Partner. The old separate vendor master was folded into the Business Partner model through Customer Vendor Integration, so a supplier is now a Business Partner carrying a supplier role. Creating one that a buyer can actually transact against is not a single field. It is central data (name, address, tax numbers), the supplier role, company code data for accounting, purchasing organisation data, and bank details for payment. Different teams tend to own different parts of that picture, which is exactly why onboarding is slow and why records come out incomplete.
|
6
Onboarding stages
|
1
Business Partner object
|
0
Data copies
|
Six stages. One workflow. One clean vendor record.
Every stage of vendor onboarding today involves a handoff between the person who needs the vendor, the people who approve it, and the team who keys it into SAP. Here is where it breaks, and how ZCC for ERP closes the gap by running the workflow on ServiceNow and writing the result straight into S/4HANA.
A buyer finds a supplier they want to work with and needs it in SAP before a purchase order can go anywhere. Today the request is an email, a half-filled form, or a quick word in a corridor. It lands in a shared mailbox and joins the queue behind everything else.
- Requests arrive in inconsistent formats, so half the information needed to create a usable Business Partner is missing before anyone even looks at it
- There is no single queue or audit trail, so nobody can say where a given request is or who it is waiting on
- A single intake form in ServiceNow captures everything the S/4HANA Business Partner needs in one place, with mandatory fields enforced before the request can be submitted
- ZCC for ERP can validate reference data live against SAP as the form is completed, so company codes, purchasing organisations, and payment terms are chosen from real S/4HANA values rather than typed free-hand
- The request becomes a tracked record with an owner and a status, replacing the shared mailbox with something the requester and the master data team can both see
The fastest way to create a data quality problem is to create a vendor that already exists. Duplicate suppliers split your spend, hide negotiated payment terms, and turn month-end reconciliation into detective work.
- Duplicate checking depends on someone manually searching SAP, which is the first thing that gets skipped under time pressure
- The same supplier ends up created two or three times under slightly different names, fragmenting spend and breaking reporting
- ZCC for ERP can search live S/4HANA Business Partner records for a match on name, tax number, or address before anything is created, and surface likely duplicates to the requester
- The check runs against real SAP data, so a tax number that already belongs to an existing supplier is caught at intake rather than discovered at invoice time
- It happens on every request, because the search is part of the flow instead of a manual step someone has to remember
Before a vendor is created it usually has to clear a set of checks: tax validation, sanctions screening, bank verification, and sign-off from procurement and finance. Today those run over email and shared spreadsheets, in no fixed order.
- Approvals and compliance checks move over email, so there is no enforced sequence and no clean evidence trail when an auditor asks
- The vendor is often keyed into SAP before every check has actually cleared, because the create step and the approval step have nothing connecting them
- The full approval and compliance chain runs in ServiceNow, with tax checks, screening, and procurement and finance sign-off each recorded against the request
- Nothing is written to S/4HANA until every gate has cleared. The create only fires once the workflow reaches an approved state, so an unapproved vendor never reaches the SAP master
- Every decision is captured on the record, giving auditors one complete trail from request to created supplier without anyone trawling inboxes
This is the step that has always been manual. Someone opens the Business Partner transaction and retypes the approved details field by field, hoping not to enter the wrong tax number or miss a mandatory view.
- The approved data is re-keyed into SAP by hand, which is slow and quietly reintroduces the errors the approval process just worked to prevent
- A supplier is not usable until its role and organisational data are all in place, and a missed view leaves a Business Partner that exists but cannot be transacted against
- On approval, ZCC for ERP can create the Business Partner directly in S/4HANA from the approved intake data, so the record the business signed off is the record that lands in SAP
- The supplier role and central data are created in the same flow, so the Business Partner comes into existence ready to use rather than as a shell someone has to finish later
- The create runs in real time under the connection user's SAP authorisation, and SAP's own field validation still applies, so what gets created is a record SAP considers valid
Bank details are the highest-risk field in the whole vendor record. Get them wrong and you pay the wrong account. Let them change without verification and you have opened the door that payment-diversion fraud walks straight through.
- Bank details are entered, and later changed, with little enforced verification, which is exactly the gap fraud exploits
- Payment data is often handled separately from the rest of the vendor, so a supplier can exist without actually being ready to pay
- Bank details are captured and verified inside the ServiceNow workflow before anything is written, so verification is a required step rather than an optional one
- ZCC for ERP can write the verified bank data into the S/4HANA Business Partner as part of the same governed onboarding, keeping payment setup tied to the approval that authorised it
- Later bank changes run through the same verified workflow, so a change of account becomes an approved, auditable event instead of a quiet edit in SAP
Onboarding is not the end of the story. Vendors change address, change bank, change contacts, get blocked, get reactivated. Every one of those changes carries the same drift and audit problems the original onboarding did.
- Vendor changes are made directly in SAP by whoever holds the access, with no consistent approval and no clear record of who changed what or why
- Changes to sensitive fields like bank details or payment terms do not automatically trigger re-verification
- Change requests run through the same ServiceNow workflow as onboarding, with approvals matched to the fields being changed, and ZCC for ERP can write the update back to the S/4HANA Business Partner once approved
- Sensitive changes re-trigger verification automatically, so a new bank account goes through the same check a brand-new vendor would
- The vendor's full history lives in ServiceNow, so you can see every change, who approved it, and when, without reconstructing it from SAP change documents after the fact
How ZCC for ERP connects the two systems
Vendor onboarding is a write-first use case, so the workhorse is the Flow Designer Use ERP data action calling ZCC for ERP Model operations, and both sides of the flow run on OData V2. The read steps (duplicate search, reference-data validation) use Read. The steps that build and maintain the supplier, its central data, the supplier role, and the bank details, use Create and Update. A full onboarding uses more than one OData model rather than a single call, so the flow orchestrates the Business Partner and its segments together.
Because it is OData, ZCC for ERP talks to SAP over its own HTTPS services, and S/4HANA Cloud OData services connect directly with no MID Server. If you want to connect to S/4HANA OnPrem, you can use the same Model with a MID Server. The calls are real time, so the Business Partner is created in SAP the moment the flow runs, with nothing staged or copied into ServiceNow. It all runs on SAP-native OData, which is why there is no middleware and no custom ABAP to maintain.
If you are mapping out how to build this, Models 101 - platform vs ERP models is the right place to start, Model creation using an OData service walks through the Business Partner model end to end, and Building custom models shows how to extend it for the fields your onboarding needs.
How it plays out in the real world
Vendor onboarding looks different depending on how many requests you handle and how much scrutiny each one has to survive. Here are two examples.
Shared services and global procurement
When onboarding is spread across regions and inboxes, the same supplier gets requested in three countries and created three ways. Local teams key vendors in with local habits, master data drifts, and reporting on total spend with a given supplier becomes guesswork. The volume is the problem, and manual process does not scale with it.
| Challenge | With ZCC for ERP |
|---|---|
| The same global supplier is onboarded separately by three regions, creating duplicate Business Partners that split spend and defeat any attempt at consolidated reporting. | ZCC for ERP can check live S/4HANA Business Partner records for an existing match before creating anything, so a supplier already onboarded in one region is surfaced to the next requester instead of duplicated. |
| Every region keys vendors in its own way, so mandatory data is inconsistent and records come out incomplete. | A single ServiceNow intake form enforces the same mandatory fields for everyone, and ZCC for ERP writes the approved record directly into SAP, so what lands in S/4HANA is consistent regardless of who raised it. |
| Nobody can say how many vendor requests are open, where they are stuck, or how long onboarding actually takes. | Every request is a tracked ServiceNow record with an owner and status, giving the shared services team one live view of the whole queue rather than a scattering of email threads. |
Regulated industries
In a regulated business the compliance steps are not optional and the audit trail is not a nicety. Sanctions screening, tax validation, and bank verification all have to happen, in order, with proof that they did. When those checks live in email and the vendor gets created in SAP on trust, the gap between approval and creation is the thing that fails an audit.
| Challenge | With ZCC for ERP |
|---|---|
| Compliance checks run over email, so proving that screening and approvals happened in the right order means reconstructing the story from inboxes months later. | The full compliance chain runs in ServiceNow with each step recorded against the request, so the evidence trail is complete and sits in one place by default. |
| Vendors sometimes get created in SAP before every check has cleared, because the create step is disconnected from the approvals. | Nothing is written to S/4HANA until the workflow reaches an approved state, so an unscreened or unapproved vendor cannot reach the SAP master in the first place. |
| Bank account changes are made directly in SAP with little verification, which is precisely the exposure payment-diversion fraud relies on. | Bank details are verified in the ServiceNow workflow before ZCC for ERP writes them, and later changes run through the same verified, approved, auditable path. |
Ready to onboard vendors without the re-keying?
ZCC for ERP can run vendor onboarding on ServiceNow while the Business Partner is created directly in S/4HANA, using SAP-native OData, with no middleware, no custom development, and no data leaving SAP. Most teams start with the create-on-approval flow for new suppliers, then add live duplicate checking at intake, then extend the same workflow to bank verification and ongoing change management. The quickest wins tend to come from ending the manual re-keying and stopping duplicate suppliers before they are ever created.
Have questions? We would 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 onboarding scenario, we are here to help.
Ask a question below ↓
© 2026 ServiceNow, Inc. All rights reserved.
