Lesson 5 of 5
Testing credit checks
10 min
A credit check is a threshold, and thresholds are tested at their boundaries. A single order "far below the limit" proves almost nothing: it would pass even if the check were switched off. Good credit tests are designed around the exposure numbers.
Prepare the numbers
Before testing, set up a dedicated test customer, or use Great Lakes Fleet Services in client 100, with a known segment limit and a known exposure. Record both before every test, because every order, delivery and invoice of other testers changes exposure. Display them in Manage Credit Accounts or UKM_BP, and for detail, the credit exposure breakdown by category.
| Test | Starting exposure | Order value | Exposure after | Expected result (limit $250,000) |
|---|---|---|---|---|
| Just below | $237,000.00 | $12,999.99 | $249,999.99 | Passes; no block |
| At the limit | $237,000.00 | $13,000.00 | $250,000.00 | Confirm the design: typically passes, because the limit is not exceeded |
| Just above | $237,000.00 | $13,000.01 | $250,000.01 | Blocked; reason segment limit exceeded |
| Main segment | Segment fine, main segment at its limit | $5,000.00 | Main over limit | Blocked; reason main segment limit exceeded |
Boundary tests for the static limit check. Values are fictional; tax may be included in the checked value, so calculate with the same basis SAP uses.
Beyond the limit
- Overdue items: post an invoice and age it past the oldest-open-item threshold (or use a test invoice with an old due date); a new order should be blocked even under the limit.
- Dunning level: where the check rule includes it, a customer at the highest dunning level should be blocked.
- Expired limit: set a limit validity in the past and confirm the check rule's behavior.
- Checking points: if checks run at delivery or goods issue too, test a change in exposure between order and delivery.
- Release and change: release a blocked order, then increase its value and confirm it is checked again.
- No check: an order type without check type D should never be blocked; confirm that is intended.
Evidence: block status and exposure before and after
- Record exposure$237,000 in segment US alternators; main segment $300,000
- Enter order$13,000.01; message and credit status captured
- Check DCDCase created, assigned to the analyst, reason segment limit
- ReleaseAnalyst releases with note "payment received today"
- Record exposureOpen orders now include the order; total $250,000.01
- DeliverDelivery due list picks up the released order
Exposure itself needs a test, separate from the check. Follow one order through delivery, billing and payment and confirm that each category moves as expected and that total exposure returns to its starting value after payment. If exposure drifts, every later credit check is wrong, so a defect here outranks a defect in any single check step.
What would you do?
Priya's credit test pack has one test: "order $1,000 for a customer with a $250,000 limit: not blocked – PASS." Dan asks if he can sign off. What do you recommend?
- Record limit and exposure before every credit test; other testers change exposure.
- Test just below, at and just above the segment and main segment limits, using the value SAP actually checks.
- Test non-limit steps, releases, rechecks, rejections and authority.
- Evidence: exposure before and after, credit status with reason, and the documented credit decision.
Check your understanding · not graded
Lesson check
1. Which test set best verifies a credit limit?
2. Why record exposure before each credit test?
3. A customer is under its limit but has a 90-day overdue invoice. What should a test with an oldest-open-item step expect?
4. What evidence shows who released a blocked order and why?