# Credit-Blocked Sales Orders by Value and Age Report

> A custom ALV report that groups credit-blocked sales orders per credit account and shows the blocked order value, the age of the oldest block, the credit limit and the limit utilization on the same line. Credit managers can prioritize the customers whose release unlocks the most revenue.

- Type: Report, Custom development, ALV report
- Module: SD
- Estimated effort: M (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/credit-blocked-sales-orders-by-value-report/


## Why is the standard not enough?

VKM1 lists blocked documents one by one so they can be released; it does not show the total blocked value per customer, how many days the oldest block has been waiting, or rank customers by that value. FD32 shows the credit limit and utilization for one customer at a time. Before credit meetings, teams merge the two screens in Excel. The custom report brings blocked orders and credit data together in one list.

### Closest standard alternatives

- VKM1: Lists blocked documents for release; no total blocked value per customer and no age of the block.
- FD32: Shows the credit limit and utilization of one customer; does not list blocked orders.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| VBUK | Credit check status in the document header (driving table in ECC) | Read | - | ECC only |
| VBAK | Credit control area, credit account, creation date and currency; in S/4HANA also the credit status | Read | VBAK-VBELN = VBUK-VBELN | ECC + S/4 |
| VBAP | Net value of the items | Read | VBAP-VBELN = VBAK-VBELN | ECC + S/4 |
| VBUP | Item delivery status; fully delivered items are not counted in the blocked value | Read | VBUP-VBELN = VBAP-VBELN AND VBUP-POSNR = VBAP-POSNR | ECC + S/4 |
| KNKK | Credit limit, receivables, sales value and risk category | Read | KNKK-KUNNR = VBAK-KNKLI AND KNKK-KKBER = VBAK-KKBER | ECC only |
| UKMBP_CMS | Risk class and credit profile of the business partner in S/4HANA SAP Credit Management | Read | PARTNER = iş ortağı (VBAK-KNKLI'den) | S/4HANA only |
| KNA1 | Name of the credit account | Read | KNA1-KUNNR = VBAK-KNKLI | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_KKBER | Credit control area | Range / multiple | VBAK-KKBER | Yes |
| S_VKORG | Sales organization | Range / multiple | VBAK-VKORG | No |
| S_KNKLI | Credit account | Range / multiple | VBAK-KNKLI | No |
| S_CTLPC | Risk category | Range / multiple | KNKK-CTLPC | No |
| S_ERDAT | Order creation date | Range / multiple | VBAK-ERDAT | No |
| P_KEYDT | Key date (default: today) | Single value | SY-DATUM | Yes |
| P_MINVAL | Minimum blocked value | Single value | VBAK-NETWR | No |
| R_SUMM | Summary per credit account | Radio button | - | No |
| R_DETL | Order detail | Radio button | - | No |

## Output columns

| Column | Source |
|---|---|
| Credit account | VBAK-KNKLI |
| Customer name | KNA1-NAME1 |
| Risk category | KNKK-CTLPC |
| Credit limit | KNKK-KLIMK |
| Receivables | KNKK-SKFOR |
| Sales value | KNKK-SAUFT |
| Limit utilization % | Calculated: (KNKK-SKFOR + KNKK-SSOBL + KNKK-SAUFT) ÷ KNKK-KLIMK × 100 |
| Blocked orders | Calculated: Number of orders with credit status B or C |
| Blocked value | Calculated: Sum of VBAP-NETWR of open items, in credit control area currency |
| Currency | Calculated: Currency of the credit control area |
| Oldest blocked order | VBAK-VBELN |
| Created on | VBAK-ERDAT |
| Days blocked | Calculated: Key date − VBAK-ERDAT of the oldest blocked order |

## How does the report work?

1. Sales documents with credit status B (check not OK) or C (partially released) are selected from VBUK-CMGST. In S/4HANA this status is in VBAK-CMGST.
2. Credit control area (KKBER), credit account (KNKLI), creation date and currency are read from VBAK; the sales organization and date range from the selection screen are applied.
3. Blocked value = sum of VBAP-NETWR of items without a reason for rejection and not fully delivered (VBUP-LFSTA ≠ C), converted to the credit control area currency if needed.
4. Credit limit (KLIMK), receivables (SKFOR), special liabilities (SSOBL), sales value (SAUFT) and risk category (CTLPC) are added from KNKK. Utilization % = (SKFOR + SSOBL + SAUFT) ÷ KLIMK × 100. In S/4HANA the credit data is read from SAP Credit Management (UKMBP_CMS and the credit segment).
5. Days blocked = key date − VBAK-ERDAT of the oldest blocked order. The summary view shows one line per credit account, the detail view one line per order; the list is sorted by blocked value in descending order.

## Authorization objects

- V_VBAK_VKO: Sales document display authorization by sales area
- F_KNKA_KKB: Credit data display authorization by credit control area (ECC)
- F_UKM_SGMT: Credit management authorization by credit segment (S/4HANA)

## Frequently asked questions

### Which orders count as blocked?

Orders with credit check status B (check not OK) or C (partially released). Documents without a credit check or already released (D) are not listed.

### Does it work on S/4HANA?

Yes, but the credit data is read from SAP Credit Management instead of KNKK, and the credit status is in VBAK-CMGST. The program is written to pick the right source for the system release.

### Can orders be released from the report?

The report only reads. For the selected lines VKM1 is called, so the release is done on the standard screen with the standard authorization check.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=sd-credit-blocked-orders-by-value
