About account data sync

Prev Next

Zilliant CPQ supports synchronization of accounts, known as customers in SAP ERP, to ensure accurate, up-to-date customer information for quoting, pricing, and order management workflows. This includes basic account details, associated sales areas, addresses, and partner functions.

What is synchronized

Zilliant CPQ synchronizes the following account-related data from SAP ERP:

  • Basic account information, such as customer ID and VAT ID

  • Customer addresses

  • Sales area data

  • Partner functions

When CPQ pulls product data from SAP ERP, it assigns a Uniform Resource Identifier (URI) to each account object. These URIs uniquely identify records across systems and maintain data consistency.

URI format:

http://<ERP_host>/<client>/<object_type>#<customer_id>

Where:

  • <ERP_host>—ERP hostname derived from SAP connection settings jco.client.ashost or jco.client.mshost.

  • <client>—Client number derived from jco.client.client.

  • <object_name>—Object type, such as Account.

  • <customer_id>—Customer (account) ID.

SAP BAPIs and function modules used

CPQ uses the following BAPIs to retrieve customer data:

  • BAPI_CUSTOMER_GETDETAIL2—Retrieves general and address data.

  • BAPI_CUSTOMER_GETSALESAREAS—Retrieves sales area data.

  • ISA_CUSTOMER_SALES_READ—Retrieves sales-specific data, such as payment terms.

CPQ maps BAPI output structures to its internal data model. The following table shows example mappings:

CPQ object

CPQ field

BAPI

Structure

Value

Notes

Account

objectName

BAPI_CUSTOMER_GETDETAIL2

CUSTOMERADDRESS

NAME + “ “ + NAME_2 + “ “ + NAME_3 + “ “ + NAME_4

The result is trimmed to remove trailing whitespace.

Account

addressCity

BAPI_CUSTOMER_GETDETAIL2

CUSTOMERADDRESS

CITY

SalesInfo

hasSalesOrg

BAPI_CUSTOMER_GETSALESAREAS

SALESAREAS

SALESORG

SalesInfo

hasPaymentTerms

ISA_CUSTOMER_SALES_READ

CUST_SALES_DATA

ZTERM

All referenced values must exist in CPQ with matching ERP IDs.

Note

CPQ doesn’t use BAPIs to retrieve partner functions. Instead, CPQ reads partner functions directly from the KNVP table in ERP. For details, read Prepare and sync partner functions.