OTC-04

Control Description

SAP S/4HANA automatically evaluates a customer's total credit exposure against their assigned credit limit during sales order processing, blocking orders that cause the credit exposure to exceed the limit

Risk

Sales orders could be fulfilled and shipped to customers whose total credit exposure exceeds their authorized limit, leading to uncollectible accounts receivable and financial loss.

Implementation Details

1. SPRO Configuration - Credit Control Areas & System Reaction
• SPRO Path: Financial Supply Chain Management > Credit Management > Integration with SD > Define Automatic Credit Control (OVA8)

• For each in-scope Credit Control Area (CCA), configure:
◘ SAP Credit Management Flag (CMPAM) as TICKED (X) - Enables credit checks
◘ Risk Categories (CTLPC) for No/Low/Medium/High/Very High Default Risk
◘ System Reaction (PMREA) for Medium+ Risk "D" (Error/Block) - Prevents order proceeding
◘ Status/Block Flag (PMSET) for Medium+ Risk CHECKED - Order placed on hold

• Evidence: Screenshot T691F export or OVA8 transaction for all in-scope CCAs

2. SPRO Configuration - Map Company Code to CCA
• SPRO Path: Assignment > Financial Accounting > Assign Company Code to Credit Control Area
• Verify: Each in-scope company code assigned to a CCA (table T001, field KKBER)

3. SPRO Configuration - Map Sales Areas to CCA
• SPRO Path: Financial Supply Chain Management > Credit Management > Integration with SD > Assign Sales Area and Credit Control Area
• Verify: Every in-scope Sales Organization (VKORG) mapped to exactly 1 CCA

4. Business Partner (BP) - Credit Management Data Assignment (UKM000)
• Transaction: BP (Business Partner master)
• Role: UKM000 (SAP Credit Management)
• For each in-scope customer, configure Credit Segment sub-screen:
◘ KKD01 (Credit Limit) - Numeric value >= $0
◘Risk Category - One of configured risk classes (No/Low/Medium/High/Very High)

Test Procedures

Test of Design (ToD)

(1) - Credit Control Areas & System Reaction

• SE16n > Table T691F. Filter by in-scope CCAs.
• For each CCA, verify:
• CMPAM = Ticked (X)
• CTLPC Risk Categories configured (No/Low/Medium/High/Very High)
• PMREA for Medium+ risk = "D" (Error/Block)
• PMSET for Medium+ risk = Checked

(2): Verify Company Code to CCA Mapping
• SPRO > Assignment > Financial Accounting > Assign Company Code to Credit Control Area
• Verify each in-scope company code assigned to a CCA
• Alternative: SE16n > Table T001, field KKBER, filter by in-scope company codes

ToD-3: Verify Sales Area to CCA Mapping
• Procedure:
• SPRO > Financial Supply Chain Management > Credit Management > Integration with SD > Assign Sales Area and Credit Control Area
• Verify every in-scope VKORG (Sales Organization) mapped to exactly 1 CCA
• Evidence: SPRO screenshot showing VKORG ↔ CCA mappings

ToD-4: Verify Customer Credit Limits & Risk Classes (BP UKM000)

• SE16n or SQVI > Join tables UKMBP_CMS (Credit Master Data) + BUT000 (BP General Data)
• Filter: Company Code = [in-scope], Customer type = [as defined], exclude inactive customers
• Output fields:
◘Customer ID (BP number)
◘Customer Name (BUT000)
◘Credit Limit (UKMBP_CMS)
◘Risk Category (UKMBP_CMS)

• Query results and identify:
◘Total count of in-scope customers
◘Customers with Credit Limit = NULL or = $0
◘Customers with Risk Category = NULL or blank

Test of Operating Effectiveness (ToE)
Setup
• Prerequisite: Copy of production environment with current master data (BP, AR, open orders)

ToE-1: Create Order Within Credit Limit (Should NOT Block)
• Procedure:
• VA01 > Enter test order for customer
• Order value: Less than available credit (e.g., available credit = $50k, order = $30k)
• Expected result: Order saved successfully (no credit block triggered)
• Verify: VA03 > Order status shows "Confirmed" (not held/blocked)
• Evidence: Screenshot of VA03 showing order confirmed + Header > Credit Management tab showing available credit > order value

ToE-2: Create Order Exceeding Credit Limit (Should Block)
• Procedure:
• VA01 > Enter second test order for SAME customer
• Order value: Exceeds available credit (e.g., available credit = $20k remaining after first order, order = $30k)
• Save order (Ctrl+S)
• Expected result: System triggers credit block (error message or DCD case created)
• Verify in UKM_CASE: DCD case created with reason = "Credit Limit Exceeded" or similar
• Verify in VA03: Order status shows "Held/Blocked" (not confirmed)
• Evidence: Screenshot of error message + UKM_CASE DCD confirmation + VA03 blocked status

ToE-3: Verify Override Process (Release Requires Authorization)
• Procedure:
• UKM_CASE > Find blocked order's DCD case > Release/Override button
• Expected: System requires approval by authorized credit manager (not just anyone)
• Approve override as credit manager user
• Verify: UKM_CASE workflow history shows approval date, approver name, reason
• Verify: VA03 order status now shows "Confirmed" (released from hold)
• Evidence: Screenshots of UKM_CASE approval workflow + VA03 order status change