SD Schedule Line Categories Part 1: What Schedule Lines and Their Categories Do
Schedule lines are where the order meets logistics: requested and confirmed dates and quantities, and — through the schedule line category — whether the item is delivery-relevant, checked for availability, passed to MRP, triggers procurement, and which goods movement follows.
What this complete series covers
Learn Schedule Line Categories in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.
- Who it is for
- Best for SAP consultants, developers, and learners who want a practical understanding of Schedule Line Categories.
- Prerequisites
- Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
- Final outcome
- By the end, you should be able to explain Schedule Line Categories clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.
- Part 1: SD Schedule Line Categories Part 1: What Schedule Lines and Their Categories Do
Understand what a schedule line category is, where it sits in the sales document structure, and why it is the control object that decides delivery relevance, availability check, an
- Part 2: SD Schedule Line Categories Part 2: Configuration and Determination (VOV6 / VOV5)
Deep dive into the configuration fields inside a schedule line category, how determination rules are set up and extended, and how these settings drive availability check, transfer
- Part 3: SD Schedule Line Categories Part 3: Movement Types, Availability Check and Transfer of Requirements
Explains how schedule line category settings drive goods movement, ATP checks, and requirement transfer to MRP/production planning during order processing.
- Part 4: SD Schedule Line Categories Part 5: Governing Schedule Line Category Design in Templates
Architectural guidance for designing, governing, and evolving schedule line category strategy across multi-country, multi-deployment S/4HANA templates, balancing standardization wi
- Part 5: SD Schedule Line Categories Part 4: Troubleshooting Determination Failures and Custom Requirements
Covers diagnosing schedule line category determination errors, incompleteness issues, custom copy control routines, and S/4HANA-specific behavior differences.
System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.
Explanation
📌 KEY POINTS
✅ A schedule line holds a date and quantity: requested delivery date/quantity and the confirmed date/quantity from the availability check.
✅ The schedule line category (VOV6) decides: delivery relevance, availability check, transfer of requirements to MRP, movement type, purchase requisition creation and delivery block.
✅ Common categories: CP (standard with MRP), CN (no MRP), CS (third-party), CB (individual PO), DN (returns), BN/AT (quotation/inquiry — no logistics).
✅ Only items whose item category allows schedule lines get them — services and texts do not.
⚠️ An item without a confirmed schedule line is not delivered, no matter how good the order looks.
━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: What schedule lines and their categories do
Part 2: Schedule line category configuration and determination
Part 3: Movement types, availability check and transfer of requirements
Part 4: Troubleshooting determination failures and custom requirements
Part 5: Governing schedule line category design in templates
━━━━━━━━━━━━━━━━━━━━
▶ 1. WHAT A SCHEDULE LINE IS
- Third level of the sales document (VBEP), below the item.
- Requested line: customer wish date and quantity.
- Confirmed line(s): what availability check can promise — may split into several lines.
━━━━━━━━━━━━━━━━━━━━
▶ 2. DATES ON A SCHEDULE LINE
- Material availability date, transportation planning date, loading date, goods issue date, delivery date.
- Calculated backward/forward from the requested date using delivery and transportation scheduling.
━━━━━━━━━━━━━━━━━━━━
▶ 3. WHAT THE CATEGORY CONTROLS
- Relevant for delivery.
- Availability check and transfer of requirements (with requirements type/checking group).
- Movement type for goods issue (601 standard, 651 returns).
- Order type for PR (third-party/individual PO), delivery block.
━━━━━━━━━━━━━━━━━━━━
▶ 4. STANDARD CATEGORIES
- CP: deterministic MRP — ATP and requirements.
- CN: no MRP — delivery without planning.
- CS: third-party — PR, no delivery from our stock.
- CB: individual PO — PR, then delivery.
- DN: returns (movement 651); BN/AT: presales, no logistics.
━━━━━━━━━━━━━━━━━━━━
▶ 5. HOW IT IS FOUND
- Item category + MRP type of the material in the plant (VOV5).
- Details in Part 2.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Create an order for a stocked material with partial availability.
- Open the schedule lines tab — see requested and confirmed lines.
- Check the schedule line category and its dates.
- Compare with a third-party item (CS).
✅ CHECKPOINT: you can explain why an item has two schedule lines and which one the delivery will use first.
Code example
===== STEP 1: schedule line data =====VBEP ETENR schedule line no., ETTYP category, EDATU delivery date, WMENG order qty, BMENG confirmed qty, MBDAT material avail. date, WADAT goods issue date, BANFN PR number ===== STEP 2: standard schedule line categories =====Cat. | Used with | Delivery | ATP | Req. transfer | Movement | PRCP | TAN (MRP) | X | X | X | 601 | –CN | TAN (no MRP) | X | – | – | 601 | –CS | TAS third-party | – | – | – | – | NB (acct. assign.)CB | TAB indiv. PO | X | X | X | 601 | NBDN | REN returns | X | – | – | 651 | –BN | AGN quotation | – | – | – | – | –AT | AFN inquiry | – | – | – | – | – ===== STEP 3: display =====VA03 > item > Schedule lines tab > Details: dates, category, procurementReal project scenario
A spare-parts distributor saw orders that looked complete but never reached the delivery due list. The items had a requested schedule line only — confirmed quantity zero — because stock was unavailable, and users ignored the schedule line tab. The team added a "confirmed quantity" column to the order monitoring report, set up backorder processing for critical customers and trained users to read the schedule line screen before promising dates.
Common mistakes
- Looking only at the item quantity and ignoring confirmed schedule lines.
- Expecting services or text items to have schedule lines.
- Confusing schedule line category with item category.
- Using CN (no MRP) where planning should see the demand.
- Expecting CS items to appear in the delivery due list.
Best practices
- Train users to read requested vs confirmed schedule lines.
- Monitor unconfirmed quantities with backorder reports.
- Keep standard categories where possible; copy to Z only for real differences.
- Document which categories serve which process.
- Test each category through delivery or procurement.
Interview angle
Questions: "What is a schedule line?", "What does the schedule line category control?", "Difference between CP, CN, CS and CB?"
Strong answer: schedule lines hold requested and confirmed dates/quantities; category controls delivery relevance, ATP, transfer of requirements, movement type and PR creation; CP with MRP, CN without, CS third-party PR without our delivery, CB individual PO with delivery; DN returns with 651; presales categories without logistics.
Practice this lesson
Quick check
1. Which schedule line category is normally used for a third-party item (TAS)?
2. What is the difference between the requested and the confirmed schedule line of a sales order item?
3. Why does a quotation item (schedule line category BN) not reserve stock?
Interview questions
1. 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?
Answer it in your own words first, then compare.
2. 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?
Answer it in your own words first, then compare.
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.
More lessons in this topic
- SD Schedule Line Categories Part 2: Configuration and Determination (VOV6 / VOV5)
- SD Schedule Line Categories Part 3: Movement Types, Availability Check and Transfer of Requirements
- SD Schedule Line Categories Part 4: Troubleshooting Determination Failures and Custom Requirements
- SD Schedule Line Categories Part 5: Governing Schedule Line Category Design in Templates