Movement Types, Availability Check, and Transfer of Requirements in Schedule Line Categories
Explains how schedule line category settings drive goods movement, ATP checks, and requirement transfer to MRP/production planning during order processing.
Explanation
Schedule line categories carry three configuration fields that materially affect logistics execution and cross-module integration: the movement type, the availability check indicator, and the transfer of requirements (TOR) indicator. Understanding how these interact is essential for anyone configuring or supporting order-to-cash flows that touch inventory management, MRP, or production planning. The movement type assigned to a schedule line category (commonly 601 for standard outbound delivery, or other types for returns, free goods, or special stock movements) determines which goods movement posts automatically when the delivery is goods-issued. This movement type is not independent; it must align with the item category's special stock indicator and the material's valuation setup. If a schedule line category configured for a stock item is used on a line intended to be non-stock or third-party, the goods movement will either fail or post incorrectly, creating downstream FI/CO reconciliation issues because the movement type also determines G/L account postings via automatic account determination. The availability check indicator on the schedule line category is a switch, not the configuration itself; the actual ATP logic (checking rule, scope of check, storage location relevance) lives in the availability check configuration linked via the sales document's checking group and checking rule. However, if the schedule line category itself has the availability check switched off, no ATP check runs for that line regardless of material or plant settings. This is intentionally used for schedule line categories tied to items like free-of-charge samples, non-stock items, or service lines where checking availability is meaningless. Consultants must verify this switch matches business intent because a mismatched setting can either force unnecessary confirmations delays on non-stock lines or silently skip checks on lines that should be checked, leading to confirmed quantities that cannot actually be fulfilled. Transfer of requirements (TOR) is the mechanism that passes sales order demand into MRP as independent or dependent requirements, enabling make-to-order or make-to-stock planning to react to sales demand. The schedule line category's TOR indicator, combined with the requirements class (derived from the strategy group or item category), determines whether and how demand is passed. If TOR is deactivated on the schedule line category, the sales order will not generate a planning-relevant requirement, meaning MRP will not consider this demand at all. This is correct for schedule lines representing already-available stock transfers or certain intercompany scenarios, but a configuration error here on a standard make-to-order line can cause production to never receive signal to produce, resulting in stockouts and order fulfillment failures that are difficult to trace because the sales order itself may show a valid confirmed date. In practice, these three settings must be evaluated together against the underlying business process: standard stock sales typically use CP or similar categories with TOR active, availability check active, and movement type 601; third-party or individual purchase order scenarios use categories like CS with TOR off (since procurement, not MRP, handles demand) and availability check off; and free goods or text items often disable both checks entirely. Any deviation from these expected combinations should be flagged during configuration review or production support triage as a likely root cause of fulfillment or planning anomalies.
Real project scenario
A consumer goods company reported that certain make-to-order finished goods were never appearing in the production planning table despite confirmed sales orders. Investigation traced the issue to a custom schedule line category copied from CP but with the TOR indicator inadvertently left blank during a rushed configuration change for a promotional item category. Sales orders processed normally, ATP even confirmed dates using existing stock, but no requirement was passed to MRP for replenishment, so once the initial stock depleted, no production was triggered. The fix required correcting the TOR indicator and manually triggering an update to recreate requirements for open orders.
Common mistakes
• Assuming the availability check indicator on the schedule line category is the full ATP configuration rather than a switch controlling whether checking group logic runs at all • Copying a schedule line category for a new item category without validating that TOR and availability check settings match the new process (e.g., third-party vs. standard stock) • Leaving TOR active on schedule line categories used for scenarios where MRP should not see demand, causing phantom planning requirements • Failing to align the movement type with the special stock indicator and valuation class, causing goods issue postings to fail or hit incorrect G/L accounts • Not testing requirement transfer end-to-end (order to MD04/planning table) after changing schedule line category settings, only checking the sales order screen
Best practices
• Always verify schedule line category settings against the requirements class and strategy group to ensure MRP integration behaves as intended • Use transaction-level requirement list review (e.g., stock/requirements list) after any schedule line category change to confirm demand is flowing correctly • Document the intended movement type, ATP, and TOR combination for each schedule line category in a configuration matrix during design workshops • Test goods issue postings in a sandbox after altering movement types to confirm account determination behaves as expected • Coordinate schedule line category changes with MM/PP teams since TOR changes directly affect planning volumes
Interview angle
Interviewers assess whether candidates understand that ATP and TOR indicators on the schedule line category are enabling switches, not the full configuration, and expect candidates to trace a fulfillment failure back through checking rule, requirements class, and strategy group rather than stopping at the sales order screen.