SD Schedule Line Categories Part 4: Troubleshooting Determination Failures and Custom Requirements

📌 KEY POINTS
✅ Most schedule line problems come from three inputs: item category, MRP type (VOV5) and schedule line category settings (VOV6).
✅ "Schedule line category not defined" = missing VOV5 entry for item category + MRP type (and no blank-row default).
✅ Missing PR for CS/CB: purchasing data in VOV6 or incomplete purchasing data (vendor, purchasing group, source list).
✅ Items missing in VL10: confirmed quantity, dates, delivery relevance, blocks, shipping point selection — before blaming the category.
⚠️ Custom routines to "force" a category hide wrong master data; fix data and configuration first.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–3 covered purpose, configuration and integration. Now the diagnostic method.

━━━━━━━━━━━━━━━━━━━━
▶ 1. NO OR WRONG SCHEDULE LINE CATEGORY

• Check the item category first (VOV4 / item category group).
• Then MRP type of the material in the delivering plant.
• Then VOV5 row for this combination and manual alternatives.

━━━━━━━━━━━━━━━━━━━━
▶ 2. NO PURCHASE REQUISITION (CS/CB)

• VOV6: order type, item category, account assignment category.
• Material: purchasing view, source of supply, purchasing group.
• Incompletion of purchasing data in the order item.

━━━━━━━━━━━━━━━━━━━━
▶ 3. NOT IN DELIVERY DUE LIST

• Confirmed quantity > 0 and material availability date in selection.
• Delivery block on schedule line or header; credit block.
• Category relevant for delivery; VTLA copy control.

━━━━━━━━━━━━━━━━━━━━
▶ 4. ATP OR REQUIREMENTS NOT RUNNING

• Schedule line flags, requirements class, checking group (Part 3).
• Plant-specific data (MRP type ND = no planning).

━━━━━━━━━━━━━━━━━━━━
▶ 5. WHEN CUSTOM LOGIC IS JUSTIFIED

• Genuine business rules configuration cannot express (e.g. choose CS vs CP by customer contract).
• Options: user exit in item/schedule line processing (e.g. MV45AFZZ), BAdI in S/4HANA, copy/requirement routines (VOFM).
• Document, test and keep them minimal — they run for every document.

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

1. Reproduce with the exact material, plant, order type.
2. Walk item category → MRP type → VOV5 → VOV6.
3. Check master data (MRP, purchasing, availability).
4. Fix data/config; only then consider custom logic.

✅ CHECKPOINT: you can explain any wrong schedule line category in under five minutes by walking this chain.

A retail distribution client reported that some order items never appeared in VL10. A developer had already proposed a user exit forcing CP. Walking the chain showed the items had CN because the materials' MRP type in the new DC was ND (no planning) — the DC had been set up by copying a consignment plant. With CN, no ATP ran; the items were delivery-relevant but outside the selection because material availability dates were in the past with zero confirmation. Correcting the MRP type and rescheduling fixed it — no custom code needed.

• Writing code to force a category instead of fixing MRP type or VOV5.
• Checking the category but not the confirmed quantity.
• Ignoring plant-specific MRP data in the delivering plant.
• Missing purchasing data for CS/CB materials.
• Not rescheduling open orders after fixes.

• Always walk item category → MRP type → VOV5 → VOV6.
• Keep a troubleshooting checklist in the support runbook.
• Use custom routines only for real business rules, documented and tested.
• Reschedule open orders after changes.
• Monitor unconfirmed and undelivered items proactively.

Questions: "An item gets no schedule line category — what do you check?", "Why is no PR created for a third-party item?", "When would you use a routine or exit?"
Strong answer: walk item category, MRP type, VOV5 and VOV6; PR issues from VOV6 purchasing data or material purchasing data; VL10 issues from confirmed quantity, dates, blocks and copy control; custom logic only for real business rules, documented and minimal.