Lesson 2 of 6
Business partner and SAP Credit Management
9 min
Two simplification items change who your customer is in the system and how much credit they get. Both are mandatory. Both are usually handled by dedicated workstreams (and Academy courses on business partner and credit go deeper), but every sales key user needs to understand the result.
Customers become business partners
In ECC, Great Lakes Fleet Services was a customer master record with general data, company code data and sales area data. In SAP S/4HANA the leading object is the business partner (BP). General data (name, address, tax numbers) sits on the BP once, and roles add the customer views: a role for financial accounting (company code data) and a role for sales (sales area data). Customer-vendor integration (CVI) keeps a customer record in sync behind the BP, so sales orders and the tables underneath still find a customer number.
For users the visible change is the maintenance screen: the classic customer transactions redirect to transaction BP, and the Fiori world uses business partner and customer master apps. For conversion, every customer must be converted to a BP before the technical conversion. That means data cleansing: duplicate customers, missing mandatory fields and inconsistent addresses all surface during CVI synchronization.
From FI-AR-CR to SAP Credit Management
ECC's classic credit management (FI-AR-CR) kept a credit limit per customer per credit control area, maintained in FD32, and checked it in sales documents with credit check types such as static or dynamic checks. In SAP S/4HANA, FI-AR-CR is not available. Its successor is SAP Credit Management (FIN-FSCM-CR), which used to be a separate component.
| Topic | ECC FI-AR-CR | SAP Credit Management |
|---|---|---|
| Where the limit lives | Customer per credit control area | Business partner per credit segment |
| Maintenance | FD32 | UKM_BP and Fiori credit apps |
| Risk class | Per credit control area | Once per business partner, across segments |
| Check in sales document type | Several check types (simple, static, dynamic) | Credit check D (SAP Credit Management) or no check |
| Blocked order handling | Release transactions such as VKM1 | Release still possible; with documented credit decisions, the credit controller decides a case in UKM_MY_DCDS or the related app |
| Scoring and external data | Limited | Scoring rules, limit calculation and external ratings (some features need a licensed edition) |
A credit segment is the unit credit is granted and monitored in. Each credit control area is linked to one credit segment; several credit control areas can share a segment. Contoso keeps it simple: one credit segment for the US business. The credit controller maintains Great Lakes Fleet Services' limit in UKM_BP (the BP in the credit management role), and the Credit Limit Utilization app shows exposure against limit.
- Sales orderMaria enters 400 CMC-ALT-100 alternators for Great Lakes Fleet Services
- Credit checkSales document type has check D; SAP Credit Management evaluates exposure in the credit segment
- Exposure updateOpen orders, deliveries, billing and receivables count toward the limit
- BlockLimit exceeded: the order gets a credit block, so delivery cannot proceed
- DecisionCredit controller reviews and releases or rejects, optionally through a documented credit decision
What conversion does to credit data
SAP provides migration steps for configuration, master data (credit limits become credit segment data on the BP), credit exposure and credit decision data. The settings do not map one to one, so the credit team has to redesign check rules and segments, and then reconcile migrated limits and exposures against ECC. One more point bites testers: sales document types that used credit check types A, B or C in ECC need check D or nothing in SAP S/4HANA. If nobody updates them, orders that blocked in ECC may silently stop blocking.
What would you do?
In the first test cycle on client 100, an order for Great Lakes Fleet Services that exceeds the limit by $40,000 is created without a credit block. In ECC the same order blocked. What is the most likely cause to check first?
- Customers are maintained as business partners with roles; CVI keeps the customer record in sync.
- All customers must be converted to BPs before the technical conversion, which forces data cleansing.
- FI-AR-CR is replaced by SAP Credit Management: limits per BP and credit segment, maintained in UKM_BP.
- Sales document types need credit check D or none; verify blocking behavior in regression.
Check your understanding · not graded
Lesson check
1. In SAP S/4HANA, which object holds the general data of the customer Great Lakes Fleet Services?
2. What keeps the classic customer record in sync with the business partner?
3. Where is a customer's credit limit maintained in SAP Credit Management?
4. Which credit check setting can a sales document type use with SAP Credit Management?