Lesson 2 of 5
Finding and resolving fulfillment issues
9 min
An order that cannot move forward is a delayed shipment, a delayed invoice and, eventually, delayed cash. Sales order fulfillment monitoring finds those orders and tells you why they are stuck. In SAP Best Practices this is scope item BKK (sales order fulfillment monitoring), and SAP describes a family of apps to analyze issues and resolve them by type.
| Issue type | What it means | Typical resolution | Who resolves |
|---|---|---|---|
| Credit block | Credit check failed; order cannot be delivered | Credit controller releases or rejects | Credit management |
| Delivery block | Order header or schedule line blocked for delivery | Remove the block once the reason is cleared | Sales |
| Billing block | Order or item blocked for billing | Release after price or claim check | Sales or billing |
| Incomplete data | Mandatory fields missing per the incompletion procedure | Complete the data | Sales |
| Not confirmed | Availability check could not confirm quantity or date | Re-plan supply, change date or plant | Sales with supply planning |
| Delayed or missing follow-on document | Delivery or invoice not created when expected | Find why the next step did not run | Shipping or billing |
Fulfillment issue types and how they are resolved.
Using the monitoring apps
The fulfillment issue app is an analytical list page: a chart at the top showing issues by type, and a list of affected orders below. Click a bar (say, credit block) and the list filters to those orders. From an order you navigate to the resolving action: the credit release, the order change, or the incompletion log. SAP also provides apps to track fulfillment status across order, delivery, invoice and accounting, with a process flow per order in which each stage shows whether there is an issue.
- Open the issue appFilter on sales organization 1710 and the requested delivery date range
- Read the chartIssues grouped by type, for example 12 credit blocks, 5 incomplete, 3 not confirmed
- Select a typeThe list shows only orders with that issue
- Navigate to resolveRelease credit, complete data or remove a block in the target app
- Re-checkThe order drops out of the list once the issue is resolved
The SAP GUI equivalents
Many teams still work some issues in SAP GUI, and testers should know both routes. Incomplete sales documents are listed with V.02; documents blocked for billing with V.23; documents blocked by credit management with VKM1; orders due for delivery in VL10 variants; deliveries in the outbound delivery monitor VL06O; and the billing due list in VF04. The Fiori apps add the cross-issue view and the navigation, but the underlying status data is the same.
| Issue | Fiori route | SAP GUI route |
|---|---|---|
| Incomplete documents | Fulfillment issue app → incomplete data; incomplete documents list apps | V.02 |
| Credit block | Fulfillment issue app → credit block; credit management apps | VKM1 |
| Billing block | Fulfillment issue app → billing block | V.23 |
| Not yet delivered | Sales order items due for delivery apps | VL10 variants |
| Not yet billed | Create Billing Documents (billing due list) | VF04 |
Fulfillment monitoring is also a measure of process health. If Contoso routinely has 15% of orders on credit block, the issue is not the individual orders but the credit limits or the credit check settings. If incomplete orders cluster on one field, the order entry screen or an interface needs fixing. Review the issue counts weekly by type, not only order by order, and agree with the process owner what a normal level looks like.
What would you do?
On Monday, Maria's fulfillment issue app shows 40 orders with incomplete data, all created by the same EDI interface since Friday, all missing the customer purchase order date. What is the best response?
- Fulfillment monitoring finds orders blocked, incomplete, unconfirmed or missing a follow-on document.
- The issue app groups orders by issue type and navigates to the resolving action.
- SAP GUI equivalents: V.02, V.23, VKM1, VL10, VL06O, VF04.
- Prioritize by value and urgency; treat block removal as a controlled decision.
- A pattern of identical issues usually points to a systematic cause such as an interface.
Check your understanding · not graded
Lesson check
1. Which issue type means mandatory fields are missing?
2. Which SAP GUI transaction lists sales documents blocked by credit management?
3. Forty orders from one interface show the same missing field. What does this suggest?
4. Why should block removal follow approval rules even in monitoring apps?