SD / O2Carchitect

SD Schedule Line Categories Part 5: Governing Schedule Line Category Design in Templates

Key takeaway

Architect's view of schedule line categories in a global template: a canonical set aligned with planning strategies, controlling VOV5 against new MRP types, dependencies on requirements classes, movement types and account determination, aATP implications in S/4HANA, and migration handling.

Explanation

📌 KEY POINTS
✅ Schedule line categories sit between SD, PP/MRP and MM — design them with supply chain planners, not SD alone.
✅ A canonical set (e.g. ZCP, ZCN, ZCS, ZCB, ZDN) with fixed meaning covers almost every process; local variation belongs in master data (MRP type, checking group).
✅ VOV5 must be governed together with the MRP type catalogue: every new MRP type needs an explicit decision.
✅ Changes ripple into requirements classes, movement types, account determination and aATP settings.
⚠️ A local "quick fix" to a schedule line category can switch off ATP or MRP for a whole country's portfolio.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–4 covered purpose, configuration, integration and troubleshooting. This part is the template view.

━━━━━━━━━━━━━━━━━━━━
▶ 1. CANONICAL SET

One category per logistics pattern: planned stock sale, unplanned sale, third-party, individual PO, returns, presales.
Same key and meaning in every country.

━━━━━━━━━━━━━━━━━━━━
▶ 2. MRP TYPE GOVERNANCE

MRP types owned by supply chain; each new type triggers a VOV5 decision.
Blank-row default documented and protected.

━━━━━━━━━━━━━━━━━━━━
▶ 3. DEPENDENCIES

Requirements types/classes, checking groups, movement types (601/651…), account determination for goods issue.
aATP: product allocation, BOP segments, supply protection depend on correct requirements.

━━━━━━━━━━━━━━━━━━━━
▶ 4. CHANGE CONTROL

Design authority for VOV5/VOV6 changes.
Regression tests: ATP, MRP demand, delivery, GI posting per category.
Configuration comparison across systems/clients.

━━━━━━━━━━━━━━━━━━━━
▶ 5. MIGRATION

Map legacy categories to canonical ones.
Open orders: redetermine or migrate with correct categories; reschedule after load.
Verify MD04 demand after migration.

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

Define the canonical set with supply chain.
Build the VOV5 matrix linked to the MRP type catalogue.
Document dependencies and regression tests.
Set change control and comparisons.

✅ CHECKPOINT: a new MRP type or plant can be onboarded with a documented VOV5 decision and no surprises in ATP or MRP.

Code example

ABAP Code

===== STEP 1: canonical set (example) =====ZCP planned stock sale | ZCN unplanned sale | ZCS third-party | ZCB individual PO | ZDN returns | ZBN presales ===== STEP 2: VOV5 matrix linked to MRP types =====ItCa  | MRP PD | MRP VB | MRP ND | MRP X1 (VMI) | blank (default)ZTAN  | ZCP    | ZCP    | ZCN    | ZCP          | ZCPZTAS  | ZCS    | ZCS    | ZCS    | ZCS          | ZCS ===== STEP 3: change impact checklist =====[ ] requirements class (OVZG)  [ ] checking group/rule (OVZ9)  [ ] movement type / account determination (OBYC)[ ] aATP: product allocation, BOP segments  [ ] regression: ATP, MD04, delivery, GI

Real project scenario

In a 14-country rollout, a country team changed the VOV5 blank-row default from CP to CN to stop ATP for a batch of promotional materials. Because the template shared configuration, every material without a specific MRP-type row in all countries lost ATP and requirements overnight. The design authority reverted the change, introduced a dedicated MRP type for promotional materials with its own VOV5 row, and protected VOV5/VOV6 with change control and automated configuration comparison.

Common mistakes

Designing schedule line categories without planners.
Local changes to shared VOV5 defaults.
Adding MRP types without VOV5 decisions.
Ignoring aATP dependencies in S/4HANA.
Migrating open orders without rescheduling.

Best practices

Co-own schedule line design with supply chain.
Keep a canonical set and a governed VOV5 matrix.
Protect the blank-row default.
Run regression tests across ATP, MRP, delivery and GI.
Reschedule and verify MD04 after migrations.

Interview angle

Questions: "How do you govern schedule line categories in a template?", "What happens when a new MRP type is introduced?", "What are the risks of changing VOV5 defaults?"
Strong answer: canonical set with fixed meanings, VOV5 matrix tied to the MRP type catalogue, protected blank default, dependency management (requirements classes, checking groups, movement types, account determination, aATP), change control and regression tests, plus migration handling with rescheduling.

Practice this lesson

Quick check

1. After migrating open sales orders to S/4HANA, which check confirms schedule lines drive planning correctly?

2. Why should supply chain planners co-own schedule line category design in a template?

3. A country team changes the VOV5 blank-row default in a shared template to stop ATP for promotional materials. What is the main risk?

Interview questions

1. In a two-wave, 14-country template, a country changed a shared schedule line determination and ATP disappeared for many materials in other countries. How do you prevent this in the future?

Answer it in your own words first, then compare.

2. You are architecting product allocation controls for a global rollout spanning standard orders and rush orders across multiple plants, where rush orders must bypass normal delivery lead times but must still respect allocation quotas. How would you design schedule line category determination and product allocation configuration to prevent expedited document types from silently bypassing allocation checks?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.