CUSTOMER · BUSINESS PARTNER
How does Customer master data work?
The central Business Partner identity becomes a usable customer when roles add company-code and sales-area data.
OBJECT ANATOMY
Separate identity, accounting, selling, and transaction roles
BP identity
Name, address, communication, legal identifiers, tax numbers, relationships, and central bank details describe the party.
Company code
Reconciliation account, payment terms, dunning, correspondence, payment methods, and withholding data support AR.
Sales area
Sales, shipping, pricing, tax, billing, delivery, and partner inputs make the customer executable in O2C.
Transaction roles
Sold-to, ship-to, bill-to, payer, and relationships allocate responsibility through order, delivery, billing, and collection.
VALUABLE SETTINGS
Find the owner, then prove the copied value
Payment terms
Inspect company-code customer data for receivables defaults and sales-area billing data for sales-document defaults. Confirm the value in the sales order, billing document, and AR open item.
Customer VAT
Legal VAT or tax registrations belong to central BP tax-number data; transaction tax classifications and destination inputs commonly sit in the sales-area extension. Prove the resulting tax condition.
Bank and withholding tax
Customer bank details may support incoming-payment identification. Where required, withholding-tax data belongs to the relevant company-code extension and must agree with configured types, codes, and posting treatment.
Customer readiness does not prove credit readiness
The credit design connects the BP credit role, credit profile, credit segments, limits, risk class, check rules, exposure, blocks, release responsibility, and sales-order evidence. Activation, migration, assignments, and authorizations must be proven independently from the ordinary Customer BP roles.
Use O2C controls for operational evidence and O2C 404 for the configured solution boundary.