SD Schedule Line Categories Part 3: Movement Types, Availability Check and Transfer of Requirements

📌 KEY POINTS
✅ ATP and transfer of requirements run only if the schedule line category allows them AND the requirements class allows them — both must be switched on.
✅ Requirements type is determined from the strategy group or item category + MRP type; it points to a requirements class (OVZG) with ATP, requirements transfer, allocation and assembly settings.
✅ Checking group (material master MTVFP) + checking rule (per transaction) define the scope of the ATP check (OVZ9).
✅ Transferred requirements appear in MD04 as sales order demand (individual or summarized records).
⚠️ Movement type is posted at goods issue of the delivery — a wrong movement type posts to the wrong stock or account.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 configured the categories. Now we follow them into MM and PP.

━━━━━━━━━━━━━━━━━━━━
▶ 1. MOVEMENT TYPES

• 601: goods issue for delivery (standard).
• 651: returns into blocked returns stock; 653 returns to unrestricted.
• 631/633: consignment fill-up/issue via specific categories.
• Movement type defines stock and accounting effect.

━━━━━━━━━━━━━━━━━━━━
▶ 2. REQUIREMENTS TYPE AND CLASS

• Requirements type (e.g. KSL sale from stock, KEL/KE MTO types) from strategy group or item category/MRP type (OVZI).
• Requirements class (OVZG): availability check, requirements transfer, allocation, assembly type.
• Schedule line flag AND class flag must both be active.

━━━━━━━━━━━━━━━━━━━━
▶ 3. AVAILABILITY CHECK

• Checking group (MTVFP) from material, checking rule from transaction (A for orders, B for deliveries).
• Scope in OVZ9: stocks, receipts, issues, replenishment lead time.
• In S/4HANA: advanced ATP (aATP) with product allocation, backorder processing (BOP), alternative-based confirmation.

━━━━━━━━━━━━━━━━━━━━
▶ 4. TRANSFER OF REQUIREMENTS

• Creates sales order requirements visible in MD04.
• Individual or summarized per day/week (checking group setting).
• MTO: requirements to individual customer stock, planned orders.

━━━━━━━━━━━━━━━━━━━━
▶ 5. TROUBLESHOOTING INPUTS

• No ATP: schedule line category flag, requirements class, checking group.
• No MD04 demand: requirements transfer flags, requirements class, MRP type.

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

1. Check the schedule line category flags.
2. Find the requirements type (item > Procurement) and its class in OVZG.
3. Check checking group and checking rule in OVZ9.
4. Create an order and look at MD04 for the demand.

✅ CHECKPOINT: you can explain for any item why it was (or was not) checked and planned.

A consumer goods company found that MTO finished goods never appeared as demand in MD04, although orders confirmed dates. The schedule line category ZCP had "Req./assembly" active, but the requirements type determined for the new MTO strategy group pointed to a requirements class with requirements transfer switched off (copied from a presales class). Orders therefore "confirmed" against replenishment lead time without triggering production. Correcting the requirements class and re-running the requirements for open orders (rescheduling) put the demand into MRP.

• Checking only the schedule line category and ignoring the requirements class.
• Wrong checking group causing ATP to confirm against replenishment lead time only.
• Using 653 where returns should go to blocked stock first.
• Summarized requirements where MTO needs individual records.
• Expecting past orders to change after fixing configuration without rescheduling.

• Check both flags (schedule line category and requirements class) together.
• Document requirements type determination per process.
• Align checking groups with supply chain planners.
• Use aATP features deliberately in S/4HANA (allocation, BOP).
• Reschedule open orders after ATP-relevant configuration changes.

Questions: "How is transfer of requirements controlled?", "What determines the scope of the availability check?", "Which movement types do deliveries and returns use?"
Strong answer: schedule line category flags plus requirements type/class (OVZI, OVZH, OVZG) control ATP and requirements transfer; checking group and checking rule define scope (OVZ9); requirements appear in MD04; movement types 601 for deliveries, 651/653 for returns, 631/633 for consignment.