SAP SD / O2C Schedule Line Categories Interview Questions

Interviewers use schedule line categories to test depth rather than coverage: the follow-up question is almost always "why does the system behave that way?", and that is where prepared answers usually run out.

Schedule Line Categories control the operational execution of a sales document item: whether it is relevant for delivery, whether availability check and transfer of requirements are triggered, which movement type feeds goods issue, and how the item connects to procurement (for third-party or make-to-order flows). This topic covers their purpose, configuration, determination logic via the schedule line category determination table, integration with MM/PP/FI, and the troubleshooting and S/4HANA considerations consultants need to configure and support order fulfillment correctly.

This page carries 21 reviewed SAP SD / O2C schedule line categories interview questions, each with a complete written answer and no sign-in required. The set breaks down into 4 foundational, 4 mid-level and 13 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

If you can handle every question here without hesitating, schedule line categories is unlikely to be what costs you an SAP SD / O2C interview β€” and the same reasoning pattern transfers to the neighbouring topics linked at the bottom of this page.

21 Schedule Line Categories questions with answers

easySchedule Line Categories

1. Do sales contracts (quantity or value contracts) generate schedule lines with ATP checks at header/item level, and how does this affect requirements transfer to MM compared to release orders created against them?

Standard quantity and value contracts are typically not schedule-line relevant and do not carry delivery-relevant item categories, so no ATP check or requirements transfer occurs at contract level. Only when a release order is created (referencing the contract) does the release order item category trigger schedule lines, ATP checking, and TOR to MRP, consuming the contract's target quantity/value. Item category group and item usage in copy control determine this.
easySchedule Line Categories

2. How does the standard Rush Order sales document type (RO) differ from a normal Order (OR), and what role does schedule line category determination play in enabling immediate delivery?

Rush order type RO is configured so the schedule line category (typically CP) triggers automatic delivery creation at order save instead of waiting for a delivery due list run, unlike OR where delivery is scheduled and processed in batch via VL10. Billing remains delivery-related (F2) and happens after goods issue, not at order entry. This is achieved through item category and MRP-type-based schedule line determination that flags 'delivery immediately' in the schedule line category.
easySchedule Line Categories

3. What is the purpose of schedule lines in a sales order, and which key fields do they carry?

Schedule lines exist at the item level and represent the quantities and dates for delivery, carrying confirmed quantity, delivery date, and the movement type used for goods issue. They drive requirements transfer to MM/PP for availability check and MRP, and determine whether the item is relevant for delivery. Schedule line category, controlled by item category and MRP type combination, decides ATP and TOR relevance.
easySchedule Line Categories

4. What role does the schedule line category play in the Cash Sales (BV) order type in enabling immediate delivery and goods issue at the point of sale, and how does its configuration differ from the schedule line category used on a standard order?

Cash sales uses a schedule line category (typically CP-derived) configured for immediate delivery with movement type triggering goods issue posting right after order save, since the delivery is created automatically in the background via the order type's immediate delivery setting. Unlike standard order schedule line categories, it usually has availability check active but requirements transfer often suppressed since stock is consumed instantly, and it's tied to an order type that auto-creates the delivery, unlike OR which requires separate delivery creation.
mediumSchedule Line Categories

5. In a make-to-order integration, how does the schedule line category influence whether a purchase requisition, planned order, or production order is generated when a sales order is saved?

The schedule line category (configured in VOV6) carries a movement type and, critically, an item relevancy indicator alongside the requirements type derived from the material's strategy group. For MTO scenarios, the schedule line category is linked to requirement class settings that determine account assignment category and whether MRP passes demand as a planned order (converted manually or via MRP run) or directly creates a production/process order upon order save, depending on the strategy (e.g., 20 vs 25/26).
mediumSchedule Line Categories

6. In an MTO scenario, an order item's incompletion log flags the requested delivery date as missing even though the sales rep manually entered a date at header level. What is the likely root cause, and how would you resolve it considering how transfer of requirements depends on this field being complete at item/schedule line level?

The header-level requested delivery date (VBAK-VDATU) does not automatically propagate to schedule line dates if the item's schedule line category or item category is configured to require independent date entry, or if the incompletion procedure checks VBEP-EDATU rather than the header field. The fix is either to correct the incompletion procedure to reference the correct field/table (schedule line vs header) or ensure the item category's TOR settings properly copy the header date down to schedule lines during order entry.
mediumSchedule Line Categories

7. A customer's scheduling agreement has multiple open delivery schedule lines, but the JIT delivery run consistently skips several items even though quantities and dates appear correct. How would you use incompletion procedures to diagnose this?

I would check the incompletion procedure assigned to the scheduling agreement's sales document type and item category to confirm which fields are flagged as mandatory-for-completeness, since an incomplete item is excluded from delivery-relevant processing even if quantity and date fields look populated. Common culprits are missing shipping point, missing route, or an incomplete schedule line status field that isn't visually obvious. I'd run VA02 incompletion log (Edit > Incompletion Log) on the affected items to identify the specific missing field before rechecking the delivery due list.
mediumSchedule Line Categories

8. How would you configure item category determination for a customer scheduling agreement so that materials produced under a make-to-order strategy correctly trigger production-relevant schedule line categories instead of standard make-to-stock delivery processing?

Item category determination for the scheduling agreement document type must combine with the material's MRP type/strategy (e.g., strategy 20/25) via the requirements class linked to the schedule line category, not just the item category itself. You'd assign an MTO-capable schedule line category (e.g., one triggering individual requirements) in the schedule line category determination table (document type + item category + MRP type), ensuring the requirement class routes demand to production rather than stock. Item category itself often stays similar, but the schedule line category is the real differentiator.
hardSchedule Line Categories

9. You are designing the make-to-order (MTO) architecture for individual customer stock, requiring segregated valuation per sales order. What schedule line determination and requirement class settings must align to support this design?

The design centers on requirements class settings (linked via requirement type from the strategy group, typically strategy 20) that enable individual customer stock through special stock indicator 'E', account assignment category, and valuation via order-related settlement or results analysis. Schedule line category must have both 'transfer of requirements' and 'availability check against individual stock' active, with the item category configured for individual purchase order/individual stock relevant processing. Any mismatch between requirement class account assignment and item category valuation settings causes stock to post to standard valuation rather than segregated order stock.
hardSchedule Line Categories

10. Does creating a sales inquiry trigger an availability check or requirements transfer to MM/PP, and why is this design decision significant for demand planning?

By standard configuration, inquiries are not relevant for availability check or requirements transfer since they are non-binding pre-sales documents; the schedule line category typically has ATP and transfer of requirements switched off. This prevents inquiries from consuming stock or generating planned independent requirements. Some organizations customize schedule line categories to allow informational ATP checks for quoting purposes, but this must be carefully controlled to avoid false demand signals in MRP.
hardSchedule Line Categories

11. Explain the end-to-end mechanics of transfer of requirements (TOR) in SD, including how schedule line determination and requirement class settings drive demand visibility in MRP.

When a sales order schedule line is created, the schedule line category (e.g., CP, CN) determines whether requirements are transferred and whether availability is checked, controlled by indicators in VOV6. The requirement type derived from the requirement class links to a planning strategy, generating an independent or individual requirement record (table VBBE for open requirements) visible to MRP. This drives production or procurement planning, and any change to order quantity/date recalculates the requirement automatically.
hardSchedule Line Categories

12. Design the document flow architecture for a complex make-to-order scenario spanning sales order, production order, delivery, and billing, and explain how schedule line determination ties these documents together across systems.

The sales order item with a make-to-order item category (e.g., TAK/TAB) triggers schedule line category which sets the requirements transfer indicator, generating a planned/production order linked via the sales order account assignment; the document flow (VBFA) links sales order to production order, goods receipt, delivery, and billing document, each update tracked. Schedule line determination assigns the requirement type driving the strategy group in production planning, ensuring the produced quantity is earmarked specifically for that sales order line via special stock indicator E (sales order stock), and delivery is only possible once production confirms stock.
hardSchedule Line Categories

13. Walk through how schedule line category determination controls the third-party sales process from sales order to vendor invoice verification.

Third-party items use item category TAS, which via schedule line category CS triggers automatic purchase requisition creation instead of a delivery. The PR converts to a PO, goods receipt is typically non-valuated (or skipped for services), and vendor invoice is matched via MM invoice verification. Customer billing is based on either the sales order (with billing relevance set to trigger on vendor invoice receipt) or via a separate copy control step depending on configuration.
hardSchedule Line Categories

14. A sales order line item is not generating a schedule line, so no delivery can be created, even though the material and quantity appear correct. As the lead architect, what systematic checks would you perform to isolate whether this is a schedule line category determination issue versus a delivery block or ATP issue?

First check VBEP for the item to see if schedule lines exist at all; if none exist, the issue is schedule line category determination (OVZG) failing due to item category/MRP type combination not being mapped, or the item category itself lacking TOR/availability relevance. If schedule lines exist but show zero confirmed quantity, it points to ATP shortage or a delivery block on the schedule line/header. Also verify the shipping point and route determination succeeded, as failed shipping point determination can suppress schedule line creation entirely in some configurations.
hardSchedule Line Categories

15. A scheduling agreement with a customer shows JIT delivery schedules not correctly transferring requirements to MRP, causing production shortages. As the architect, walk through your root-cause diagnosis approach.

First verify the item category and schedule line category on the scheduling agreement have requirements transfer active and are linked to the correct requirements type/class feeding independent requirements in MRP. Check the strategy group on the material master matches the planning strategy expected (e.g., make-to-stock with SA integration), confirm the delivery schedule lines (forecast vs JIT) are correctly categorized since JIT schedules often have different requirement transfer settings than forecast delivery schedules, and check transfer control settings in the scheduling agreement customer master record for delivery tolerances and cumulative quantity handling.
hardSchedule Line Categories

16. An inquiry document created for a strategic customer is not generating schedule lines or ATP results, even though the material is available and the item category appears correct. How would you systematically troubleshoot schedule line determination for this inquiry?

Start by checking whether the inquiry's schedule line category has the requirements/availability check indicator active, since inquiries by default (schedule line category AT) typically do not carry ATP or requirement transfer, unlike quotations or orders. Verify item category to schedule line category determination (VOV5) using MRP type and item usage as keys, confirm the material's strategy group isn't causing a mismatch, and check whether the customer or document type requires a customized schedule line category to enable availability checking for informational purposes.
hardSchedule Line Categories

17. A standard order is showing an unexpected schedule line category that bypasses the availability check, causing delivery creation without confirmed stock. How would you diagnose and resolve the root cause?

Start by checking the item category and MRP type combination in schedule line category determination (VOV4/VOV6) to see which schedule line category was actually assigned versus expected. Verify the MRP type on the material master, since it directly influences determination results. Also check if a manual schedule line category override exists in the order, or if a user exit/BAdI in requirement determination is forcing an incorrect category. Correct the determination table entry or material master data, then reprocess affected open orders.
hardSchedule Line Categories

18. Sales orders pass the incompletion log with no errors, yet requirements are not being transferred to MRP for several materials, causing missed production planning. As the architect, how would you investigate and resolve this?

Since the incompletion log validates only fields configured in the incompletion procedure, it will not flag missing requirements transfer, which is governed separately by the requirements class, checking group in the material master (MRP3 view), schedule line category settings for transfer of requirements, and availability check switch at the plant/checking group combination. I would verify the requirement class linked via the requirement type, confirm 'transfer of requirements' and 'availability check' indicators are active on the schedule line category, and check whether the material's strategy group or MRP type suppresses requirements for those materials.
hardSchedule Line Categories

19. 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?

Product allocation checks are triggered by the item category/schedule line combination flagged as allocation-relevant (via the allocation procedure and characteristics like sales org, plant, material). The risk with rush orders is that a distinct schedule line category (often configured to skip standard ATP delays) may not be assigned the same allocation-relevant checking as the standard order's schedule line category, effectively bypassing the quota. Design must ensure both document types share consistent allocation-relevant checking rules, use the same allocation object/characteristics combination, and that any custom schedule line category for rush orders explicitly inherits allocation checking rather than being copied from a non-allocation-checked template.
hardSchedule Line Categories

20. You are architecting a global template where different regions require distinct schedule line splitting behavior for partial deliveries based on plant-level stock availability. How would you design the sales document type and schedule line configuration to support this without creating excessive custom code?

Leverage standard schedule line category configuration per item category/MRP type combination, using different requirement types tied to region-specific requirement classes to control ATP check rules and confirmation behavior. Configure delivery scheduling and rescheduling rules at plant/shipping point level rather than hardcoding logic, and use document type-specific settings for automatic batch split or backorder processing. Where regional variation is truly needed, isolate via separate sales document types sharing common item categories to keep template governance manageable, only resorting to BAdIs for edge cases not covered by standard determination logic.
hardSchedule Line Categories

21. Sales quotations for a new product line are not generating schedule lines even though the item category and material master settings appear correct. As the architect, how would you diagnose the root cause?

First verify the item category assigned to the quotation item has schedule line allowed flag set (some quotation item categories, like AGN, intentionally suppress schedule lines since quotations are not delivery-relevant). If schedule lines are expected, check schedule line category determination (MRP type, item category, plus strategy group) via the schedule line category determination table, confirm the material's requirements type is valid, and check for missing sales org/plant assignment or an incompletion status blocking schedule line generation. Also verify the document type's requirement class doesn't disable requirements transfer for quotations.

Related lesson

Advanced Troubleshooting: Schedule Line Category Determination Failures and Custom Requirement Routines

Related topics

Next practice step