In SAP S/4HANA, a customer is represented through the Business Partner model. General data identifies the person or organization, the FI customer role FLCU00 adds Financial Accounting information, and the customer role FLCU01 adds Sales data. A customer may need one or both specific roles depending on the process.
What a customer Business Partner represents
An organization may need to identify the same customer for correspondence, receivables, orders and shipping. SAP S/4HANA uses a shared Business Partner identity and assigns roles for the processes the relationship needs. Maintaining a general Business Partner does not automatically mean the customer is ready for sales-order processing or customer invoice posting.
General Business Partner data is the common layer
General identity holds business-partner-level information such as name, address and communication details. This common record makes it easier to recognize the customer consistently. Duplicate identities, incorrect legal names or unapproved changes can lead to billing confusion and downstream reconciliation issues. Data stewardship and appropriate authorizations are important.
FI customer role FLCU00: accounting by company code
The Financial Accounting customer role is associated with company-code data, including reconciliation-account and payment-related settings. If an enterprise operates multiple legal entities, the same partner may require different accounting settings for each relevant company code. Finance must validate those settings; they cannot be inferred from a sales address or supplier record.
Sales customer role FLCU01: the sales-area view
The sales role contains customer data relevant to sales and distribution activity, including order, shipping and billing contexts. A customer may have accounting data but not yet be extended to a required sales area. Ask which sales organization, distribution channel and division apply in the actual design rather than assuming one sales relationship fits every location.
A practical two-company example
Imagine one external customer buying equipment from one legal entity and services from another. The customer should be identified reliably across the relationship. But payment rules, reconciliation accounts and sales terms may vary by company code or sales area. Teams should verify business-partner roles, organizational extensions and authorization before creating another near-duplicate customer to work around missing data.
Governance questions that prevent trouble
Who may create a customer, approve a new sales-area extension, maintain payment details or block a record? Is there a duplicate check? Are sensitive bank updates independently verified? Are ownership and changes traceable? Good master-data controls protect Accounts Receivable, credit management, sales fulfillment and accurate customer communication.
How CVI and role mapping fit the bigger picture
SAP documents Customer/Vendor Integration (CVI) as the integration between Business Partner and corresponding customer/supplier master data in S/4HANA contexts. Grouping, account-group assignment, number ranges and required fields can affect the process. An implementation team should check the actual landscape and configuration before assuming that a legacy customer number maps automatically to a Business Partner without design decisions.
Consultant thinking: identify the missing scope
When someone reports that a customer exists but cannot be used, ask whether general data is complete, whether FLCU00 or FLCU01 is needed, which company code or sales area is involved, and what error or authorization boundary is visible. The issue may be missing organizational extension, invalid required fields or blocked master data—not a need to create a second identity.
Read next
Compare Supplier Master Data Controls, Document Types in Financial Accounting, Automatic and Manual Clearing and Chart of Accounts Structure. Return to the SAP FI / FICO hub.