ORDER TO CASH · PARTNERS
Who is the customer in an SAP sales process?
In SAP S/4HANA, the Business Partner is the central object. Customer roles add company-code and sales-area data, while partner determination assigns the sold-to, ship-to, bill-to, and payer responsibilities used by a transaction.
PROCESS ROLE
One identity can carry several organizational and transactional roles
General Business Partner data identifies the organization or person. Customer roles extend that identity for Finance and Sales. Partner functions then tell a specific sales document who orders, receives, is invoiced, and pays.
S/4HANA PARTNER MODEL
Identity, organizational extensions, and transaction roles
These layers are related but not interchangeable. A missing sales-area extension cannot be repaired by changing a partner function in the order.
Business Partner identity
Name, addresses, communication, identification, bank, and central relationship data describe the party.
Customer company-code data
Reconciliation account, payment terms, dunning, correspondence, and withholding data support the customer subledger.
Customer sales-area data
Sales, shipping, billing, pricing, tax, delivery, and partner-determination inputs make the party executable in O2C.
Partner functions
Sold-to, ship-to, bill-to, and payer assign responsibilities in the sales order and its successors.
OPERATIONAL FLOW
What happens in SAP
Read the sequence as one connected business event, not as isolated transactions.
Create or govern the Business Partner
Maintain the legal identity once, apply duplicate controls, and preserve addresses and relationships as governed master data.
Add customer roles and organizational data
Extend the partner to required company codes and sales areas with reconciliation, payment, shipping, pricing, tax, and billing data.
Resolve transaction partners
Partner procedures and master-data relationships propose the sold-to, ship-to, bill-to, payer, and other required roles.
Carry responsibilities through the flow
Copy control and partner rules preserve or redetermine the appropriate partners across delivery, billing, output, and receivables.
DESIGN & CONTROL
What shapes the result
These controls work together; a locally correct setting can still produce the wrong end-to-end outcome.
Central identity
Grouping, number ranges, roles, duplicate checks, addresses, tax identifiers, relationships, and governance protect the Business Partner record.
Organizational readiness
Company-code and sales-area extensions must exist with the required reconciliation, payment, shipping, pricing, tax, and billing attributes.
Partner responsibility
Partner procedures, source relationships, mandatory roles, permitted changes, and copy behavior determine who performs each commercial role.
DIAGNOSTIC EVIDENCE
Separate identity problems from role problems
A document can find the correct Business Partner but still fail because an organizational extension or required partner responsibility is missing.
Business Partner number, grouping, legal name, address, tax identifiers, central status, and duplicate relationship.
Customer roles, company code, sales area, reconciliation account, payment terms, shipping conditions, pricing and tax classifications.
Partner procedure, determined sold-to/ship-to/bill-to/payer, source relationship, manual change, and successor-document partners.
PROJECT MOMENT
One buying group, four operational parties
A regional head office places the order, a branch receives the goods, a shared-service address receives the invoice, and treasury pays. SAP can represent four Business Partners or one party in multiple roles, but each responsibility must remain explicit and testable.
- Sold-to is commercially authorized
- Ship-to drives delivery data
- Bill-to receives the invoice
- Payer owns the receivable
See how these module capabilities connect across fulfilment branches, logistics documents, accounting entries, billing, and clearing.