FI / FICOintermediate

FICO Credit Management Part 2: Automatic Credit Checks, Risk Classes and Blocking

Key takeaway

Configure credit checks: risk classes and scoring, check rules and check steps (static, dynamic with credit horizon, maximum document value, oldest open item), assignment to sales document types, blocking behavior and release process with documented credit decisions.

Explanation

📌 KEY POINTS
✅ Check rules bundle check steps: static limit, dynamic (with credit horizon), maximum document value, oldest open item, and more.
✅ Risk classes (from scores) drive default limits and check rules.
✅ SD settings decide which document types and item categories run credit checks and at which point (order, delivery).
✅ Blocks create documented credit decisions for analysts to release or reject.
⚠️ Too many check steps create unnecessary blocks and slow order processing.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 explained the basics. Now configuration.

━━━━━━━━━━━━━━━━━━━━
▶ 1. RISK CLASSES AND SCORES

Score → risk class → default limits/rules.

━━━━━━━━━━━━━━━━━━━━
▶ 2. CHECK RULES AND STEPS

Static, dynamic (horizon), max document value, oldest item.

━━━━━━━━━━━━━━━━━━━━
▶ 3. SD INTEGRATION

Credit check per sales document type/item category; reaction (warning, error, block).

━━━━━━━━━━━━━━━━━━━━
▶ 4. RELEASE PROCESS

Documented credit decisions; responsibilities.

━━━━━━━━━━━━━━━━━━━━
▶ 5. TUNING

Monitor block rates; adjust rules.

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

Define check rule with static + dynamic steps.
Assign to risk class and customers.
Test orders and review blocks.

✅ CHECKPOINT: blocks occur only where risk justifies them.

Code example

ABAP Code

===== CONFIG MAP (SPRO > Financial Supply Chain Management > Credit Management) =====Credit risk monitoring: risk classes, scoring rules, check rules & check stepsCredit segments and assignment to credit control areaSD: activate credit management/credit check per sales document type & item category ===== CHECK STEPS (examples) =====Static limit | dynamic with credit horizon (e.g. 3 months) | max document value | oldest open item (days overdue)

Real project scenario

A company activated a dynamic check with a 12-month horizon; future scheduled orders consumed the limit and blocked urgent orders. Reducing the horizon to 2 months and adding a max document value check balanced control and speed.

Common mistakes

Long credit horizon.
Too many steps.
No release ownership.
Checks on irrelevant document types.
No monitoring.

Best practices

Start simple.
Tune horizon.
Assign analysts.
Scope document types.
Monitor block rates.

Interview angle

Questions: "Static vs dynamic check?", "What is the credit horizon?", "How do blocks get released?"
Strong answer: check rules and steps, risk classes, SD integration, release, tuning.

Practice this lesson

Quick check

1. Which type of automatic credit check compares a customer's exposure using only open items (receivables), without considering future-oriented values like open sales orders or deliveries?

2. What does the 'credit horizon' setting control in automatic credit control configuration?

3. In SAP FI/SD integration, what is the primary purpose of the credit control area?

Interview questions

1. Sales complains that too many orders are credit-blocked. How do you review the credit check configuration?

Answer it in your own words first, then compare.

2. How would you apply Credit Management in a real SAP project? Walk through the design or implementation approach.