PROCURE TO PAY · SUPPLIER
How is a supplier represented in SAP S/4HANA?
SAP S/4HANA uses the Business Partner as the leading identity. Supplier roles then add company-code, purchasing-organization, tax, payment, bank, partner-function, and operational data needed by P2P.
PROCESS ROLE
One identity can carry several process roles
Central BP data identifies the person or organization. Supplier roles extend that identity for Financial Accounting and Purchasing. Organizational segments and partner functions determine where the supplier may transact and who acts as ordering address, goods supplier, invoicing party, or alternative payee.
SUPPLIER MODEL
One identity, three operational layers
Separate identity from organizational extensions and transaction roles so ownership and defects can be located correctly.
Central Business Partner
Name, address, communication, legal and tax identity, relationships, and general status belong to the leading BP object.
Accounting extension
Reconciliation account, payment terms and methods, dunning, withholding tax, payment block, and correspondence support supplier accounting.
Procurement extension
Purchasing organization data carries order currency, incoterms, purchasing blocks, partner schema, planned delivery and buyer-facing defaults.
Partner functions and document use
Ordering address, goods supplier, invoicing party, alternative payee, bank data, source records, and document partners shape individual transactions.
OPERATIONAL FLOW
What happens in SAP
Read the sequence as one connected business event, not as isolated transactions.
Establish the leading identity
Create or govern the Business Partner with the correct category, grouping, number range, addresses, tax identifiers, and duplicate controls.
Add supplier roles
Extend the BP to the required supplier roles, company codes, and purchasing organizations rather than creating disconnected identities.
Apply organizational and partner rules
Account groups, field status, reconciliation account, payment data, partner functions, blocks, and authorization determine allowed use.
Supply purchasing and payment documents
PR sourcing, info records, agreements, POs, invoices, payments, and reporting consume the appropriate supplier segment and retain the BP relationship.
DESIGN & CONTROL
What shapes the result
These controls work together; a locally correct setting can still produce the wrong end-to-end outcome.
Business Partner and CVI governance
In SAP S/4HANA the BP is the leading object. Migration and coexistence require Customer/Supplier Integration mappings, groupings, account groups, number ranges, roles, and synchronization to be explicitly designed.
Organizational completeness
A BP can exist centrally but still be unusable because the company-code or purchasing-organization extension, reconciliation account, tax, payment, or partner data is missing or blocked.
Sensitive and segregated data
Bank accounts, payment methods, alternative payees, tax identifiers, blocks, and changes require stronger access, approval, monitoring, and evidence than ordinary address maintenance.
DIAGNOSTIC EVIDENCE
Diagnose the missing supplier layer
Do not treat every supplier error as a purchasing-document defect.
BP category, grouping, address, tax identity, relationships, duplicate result, central block, and change history.
Company-code and purchasing-organization extensions, account group mapping, reconciliation account, payment and tax data, purchasing block, currency, and incoterms.
Partner functions, ordering and goods-supplier addresses, invoicing party, alternative payee, bank data, source records, and document partner result.
PROJECT MOMENT
The supplier exists but the PO still fails
A BP was created with central data and an FI supplier role, but no purchasing-organization extension. AP can inspect accounting data, yet Purchasing cannot use the supplier in the intended organization until the missing role data and controls are completed.
- Leading identity is unique
- Required roles are extended
- Sensitive data is governed
- Transaction partner result is explainable
See how demand, sourcing, commitment, receipt alternatives, invoice matching, accounting entries, payment, and clearing connect.