Business Partner ConfiguratorEnterprise Data Qualification Platform
Customer and supplier master data

SAP Business One integration for customer and supplier data

Connect SAP Business One through Service Layer. Prepare customer and supplier data, review changes and write approved records back to SAP.

Set up with MicrosoftDiscuss your use case

How does SAP Business One integration work?

The SAP Business One integration reads and writes supported Business Partner fields through Service Layer. Creation, enrichment, data cleansing and duplicate review use the configured company database.

Which SAP data is covered?

Business Partner master data

General data, contacts, addresses and supported bank details retain their SAP record identifiers.

Controlled source updates

Customers and suppliers stay separate. An address used for billing and shipping is mapped to SAP’s separate entries.

Connection checks

A login check tests the connection. A separate permission test needs a designated test record and explicit confirmation.

How it works

  1. 1

    Connect

    Enter the Service Layer address and company database.

  2. 2

    Check

    Test the dedicated SAP login.

  3. 3

    Review

    Review the fields and intended changes.

  4. 4

    Publish

    Submit and inspect the SAP result.

Practical example

Example: SAP Business One

A supplier has two contacts and one address used for both billing and delivery. The reviewed record keeps those roles when sent to SAP.

This is master data integration. Duplicate consolidation does not transfer invoices, balances or transaction history.

Frequently asked questions

What does this process do?
It connects supported Business Partner master data through the SAP Business One API.
Which systems and data are covered?
The scope covers supported company, contact, address and bank fields; other SAP objects need separate mapping.
What access or approval is needed?
A reachable Service Layer and a suitable SAP user are needed. Microsoft sign-in is separate.
What should I check before using it?
Provider permissions and SAP customizations can limit individual fields. A successful login does not prove write access.

Related tasks

Data Validation

A filled field is not necessarily the right field. Use data quality checks to inspect company identity, address roles and proposed changes.

Governance Workflows

Give company administrators control over their connections. Keep setup, record review and automatic-update approval as separate decisions.

Duplicate Prevention

Check for existing partners before adding another record. Names and tax identifiers matter more than a shared email domain alone.

Explore ERP and CRM integrationsOfficial provider documentation

Have a record or connection in mind?

Set up your company workspace, or describe the ERP and master data problem through Contact.

Set up with MicrosoftDiscuss your use case