SD / O2Cintermediate

SD Credit Management Part 6: Credit Blocks, Documented Credit Decisions and Release

Key takeaway

What happens after a failed check: credit status on orders and deliveries, documented credit decisions (cases) for analysts, release, rejection and forwarding, effects on deliveries and billing, notifications to sales, and SLAs for credit decisions.

Explanation

📌 KEY POINTS
✅ A failed check sets the document's credit status to blocked; blocked orders are not delivered, blocked deliveries not goods-issued.
✅ SAP Credit Management creates a documented credit decision (case) with exposure, limit and failed steps.
✅ Analysts release, reject or forward the decision; release updates the SD document status.
✅ Later changes (value increase, date change) can trigger a recheck and a new block.
⚠️ Decisions without SLAs leave orders waiting — sales and customers see "system problems".

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 5 defined what is checked. Now handling blocks.

━━━━━━━━━━━━━━━━━━━━
▶ 1. CREDIT STATUS

Order header credit status (e.g. checked OK, blocked, released).
Delivery credit status for delivery/PGI checks.
Lists of blocked documents.

━━━━━━━━━━━━━━━━━━━━
▶ 2. DOCUMENTED CREDIT DECISIONS

Case per blocked document with data for the decision.
Worklist for analysts by segment/risk.

━━━━━━━━━━━━━━━━━━━━
▶ 3. DECISIONS

Release: document continues.
Reject: order items rejected/status set.
Forward: to higher approval level.

━━━━━━━━━━━━━━━━━━━━
▶ 4. RECHECK AFTER RELEASE

Value or date changes can trigger new checks.
Release validity depends on configuration (e.g. deviation tolerance).

━━━━━━━━━━━━━━━━━━━━
▶ 5. COMMUNICATION AND SLAS

Notify sales of blocks and decisions.
SLA per risk class (e.g. 4 hours).
Reports on block volume and decision time.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Create a blocked order.
Process its documented credit decision (release).
Increase the order value and observe recheck.
Reject another blocked order and check item status.

✅ CHECKPOINT: every blocked document has an owner, decision time and documented reason.

Code example

ABAP Code

===== STEP 1: blocked documents =====Order credit status (header) | delivery credit status | lists of blocked SD documentsClassic ECC: VKM1 (blocked SD documents), VKM3/VKM4 ===== STEP 2: documented credit decisions (S/4HANA) =====UKM_CASE / apps for documented credit decisions (names per release): release | reject | forward ===== STEP 3: recheck =====Order change with value increase → new credit check → new block if exposure exceeds limit ===== STEP 4: KPIs =====Blocks per day | median decision time | % released | % rejected

Real project scenario

A distributor's credit team worked through blocked orders by opening VKM1 once a day. Urgent orders waited up to 30 hours, and sales escalated constantly. With S/4HANA documented credit decisions, worklists by risk class, a four-hour SLA for key accounts and automatic notifications to sales, median decision time fell below two hours.

Common mistakes

No SLA for credit decisions.
Sales unaware of blocks.
Releases without documenting reasons.
Ignoring rechecks after changes.
Rejecting orders without informing customers.

Best practices

Use documented credit decisions with worklists.
Define SLAs by risk class.
Notify sales automatically.
Document reasons for releases.
Monitor block and decision KPIs.

Interview angle

Questions: "What happens when an order fails the credit check?", "What is a documented credit decision?", "When is a released order rechecked?"
Strong answer: credit status blocks delivery/PGI, DCD cases for analysts (release/reject/forward), status update, rechecks on value/date changes, notifications and SLAs.

Practice this lesson

Quick check

1. When a sales order fails an automatic credit check and is set to be blocked, what is the immediate system behavior?

2. An order passed at entry but was blocked before delivery. What is a typical explanation?

3. Which transaction releases sales documents blocked for credit?

Interview questions

1. A customer's sales order is blocked for delivery due to a credit hold, but the sales team insists the order must ship today for a strategic account. What steps would you take to resolve this while maintaining credit control integrity?

Answer it in your own words first, then compare.

2. A customer is at their credit limit, but the warehouse has already picked and packed the goods before the credit block is triggered. Post Goods Issue is now blocked. How would you architect a solution to prevent this costly late-stage blocking pattern?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.