Configuring Schedule Line Category Control Indicators and Determination Logic

Explanation

Once the basic concept of schedule line categories is clear, the next step for a consultant is understanding the configuration fields that make each category behave differently, and how to safely extend the determination logic for new business scenarios. This configuration is maintained in the IMG path under Sales and Distribution > Sales > Schedule Lines, with two related activities: maintaining the schedule line categories themselves (transaction VOV6) and maintaining the assignment table that determines which category is proposed for a given item category and MRP type combination. Inside VOV6, the most operationally significant fields are: Delivery block, Movement type, Item relevance for delivery, Availability check indicator, and Transfer of requirements (TOR) indicator. The delivery relevance indicator is a simple but critical flag - if unchecked, the schedule line will never generate an outbound delivery no matter what stock situation exists, which is exactly the desired behavior for categories used in third-party processing, service items, or pure planning/display items that should never physically ship. The availability check indicator, when active, tells the system to perform ATP (Available to Promise) checking against the requested delivery date and quantity. This links to the overall availability check configuration (checking group and checking rule at the material and requirement class level), but the schedule line category is the gate that decides whether the check happens at all for this schedule line. If a category has this indicator switched off, the order will accept the quantity without validating stock, which is intentional for categories representing service, third-party, or non-stock scenarios but a serious defect if accidentally switched off for a standard stock item category. The transfer of requirements indicator determines whether the requirement is passed to MRP (visible in transaction MD04 as an independent or dependent requirement) so that planning, production, or procurement can react to the demand. This is separate from the availability check indicator - a schedule line can, in theory, check availability without transferring the requirement, though in most standard delivery-relevant scenarios both are active together (as in CP). Understanding this separation is important when diagnosing why a confirmed sales order quantity is not visible in MRP: it usually means TOR is switched off at the schedule line category or the requirement class further downstream is not passing it through. The movement type field defines which goods movement (like 601 for standard delivery-related goods issue, or 231 for consignment issue) will be defaulted during delivery processing for that schedule line. This connects directly to Materials Management and Finance, since the movement type determines account determination for the goods issue posting. Getting this wrong causes incorrect stock account postings or blocked goods issue due to missing account assignment. The determination table itself (item category + MRP type -> schedule line category, with an optional alternative category) needs careful extension whenever a new item category or new MRP type is introduced, for example when a client adds a new MRP type for a subcontracting or vendor-managed inventory process. Consultants must add explicit combinations rather than relying on a generic fallback, because an unmapped combination results in a hard error at order entry (schedule line category could not be determined), which is one of the most common go-live defects in SD configuration. Requirement class and requirement type also interact with schedule line category settings for more complex scenarios like make-to-order (MTO) or configurable materials, where the schedule line category must be consistent with special stock indicators and assembly processing flags maintained elsewhere, so configuration changes here should always be tested end-to-end against the intended production/procurement process, not just order entry.

Code example

* Illustrative view of schedule line category determination logic (VOV6 / assignment table), not executable code:* Item Category   MRP Type   -> Schedule Line Category   Alternative* TAN             PD          -> CP (deliv-relevant, ATP on, TOR on)   CN* TAN             ND          -> CN (not deliv-relevant, ATP off)      -* TAS (3rd party)  *          -> CS (not deliv-relevant, creates PR)   -* TAB             *           -> CB (individual PO scenario)          -* Config check in VOV6 for category CP:*   Delivery relevance = X*   Availability check  = X (checking group/rule inherited from material + checking rule of sales doc type)*   TOR (Req./Assembly)  = X*   Movement type        = 601

Real project scenario

During a rollout to a new distribution center, a client introduced a new MRP type (X1) for a vendor consignment replenishment process but did not extend the schedule line category determination table. Order entry for affected materials failed with a hard determination error, blocking the entire order creation process for that plant on go-live morning. The fix required an emergency transport adding the missing item category/MRP type combination pointing to the correct consignment-relevant schedule line category, along with regression testing of the standard TAN/PD combination to confirm no unintended overlap.

Common mistakes

• Switching off the availability check indicator on a standard stock-relevant schedule line category without realizing it disables ATP validation entirely for that flow. • Forgetting to extend the schedule line category determination table when a new MRP type or item category is introduced, causing hard order-entry errors. • Changing the movement type on a standard SAP-delivered schedule line category directly instead of copying to a custom category, risking cross-process side effects. • Assuming transfer of requirements and availability check are the same setting when they are independently controlled and can be configured differently. • Not testing schedule line category changes through the full document flow (order, delivery, goods issue, billing) before transport to production.

Best practices

• Copy standard schedule line categories to custom Z-categories before altering indicators for a specific business scenario. • Maintain a change-controlled register of item category/MRP type combinations so new materials or MRP types are proactively mapped before go-live. • Always test schedule line category changes through order, delivery, goods issue, and billing, not order entry alone. • Coordinate movement type changes with the MM/FI team since they affect account determination and inventory postings. • Use transaction MD04 and the sales order's schedule line detail view together to validate that TOR and ATP settings behave as configured.

Interview angle

Candidates are frequently asked to explain the difference between the availability check indicator and the transfer of requirements indicator on a schedule line category, and to describe what happens when a combination is missing from the determination table. Strong answers describe the hard error at order entry, the IMG path used to fix it, and the downstream MM/PP impact of getting movement type or TOR settings wrong, showing integration awareness beyond pure SD configuration.