VBEP S/4 HANA VS R/3

[antonio_bruno]

Hello,

Could you please indicate me the new features related to the VBEP in S/4 HANA?

In particular, compared to R/3, I've found the fields: DLVQTY_BU, DLVQTY_SU, OCDQTY_BU, OCDQTY_SU, ORDQTY_BU, ORDQTY_SU. What's the differences?

Can I use the ODN_AMOUNT to select the open value referred to the specific schedule line (not to the item)?

If i select the records related to one of the "open quantity" fields with value not equal to zero, the result is equal to VBBE?

Thanks and regards.

[Jeremy_Deo]

Hello dear user,

And thank you for asking your question on the SAP Community blog.

Let's walk through each of your questions step by step to clarify how VBEP has evolved in SAP S/4HANA compared to R/3, especially with regard to open quantities, new fields, and how it compares to VBBE :

1. New Fields in VBEP (S/4HANA)

The fields you mentioned — DLVQTY_BU, DLVQTY_SU, OCDQTY_BU, OCDQTY_SU, ORDQTY_BU, ORDQTY_SU — are part of the data model simplification and enhancement in S/4HANA.

These fields represent quantities in different units of measure (BU = Base Unit, SU = Sales Unit) and are meant to give more granular and real-time visibility into the schedule line status.

Here’s what each means:

Field	Description
DLVQTY_BU	Delivered quantity in Base Unit of Measure (BU)
DLVQTY_SU	Delivered quantity in Sales Unit (SU)
OCDQTY_BU	Open confirmed delivery quantity in Base Unit
OCDQTY_SU	Open confirmed delivery quantity in Sales Unit
ORDQTY_BU	Ordered quantity in Base Unit
ORDQTY_SU	Ordered quantity in Sales Unit

These are redundant fields introduced to improve performance and analytics, avoiding on-the-fly UoM conversions when doing reporting or CDS-based analytics.

These fields are filled in real-time via internal processing (e.g., ATP updates) and are not directly editable via standard transactions.

2. Can I use ODN_AMOUNT to get the open value per schedule line?

Yes — but with some caution.

• ODN_AMOUNT (Open Delivery Net Amount) is calculated at the schedule line level, unlike some traditional values in VBAP or VBAK.
• It provides the net amount value (in document currency) corresponding to the open (undelivered) quantity at the schedule line.
• You can use this field if you want to track open revenue/value for a specific delivery date.

Attention : however, if your pricing includes surcharges, header discounts, or conditions not distributed at the schedule line level, the amount might not match 100% exactly with expectations unless conditions are properly distributed.

3. Is VBEP filtered by open quantity ≠ 0 equivalent to VBBE?

Not quite, although they overlap in use case.

Key differences:

Feature	VBEP with Open Qty ≠ 0	VBBE (Requirements Table)
Source	Schedule line table	ATP (MRP) elements
Includes	All schedule lines (even fulfilled ones if not filtered)	Only open requirements
Use case	Sales schedule details, value tracking	ATP, availability check, MRP planning
Scope	Document-centric	Stock/requirement-centric

So:

• If you filter VBEP by open quantities (e.g., OCDQTY_BU ≠ 0), you're close to what you get in VBBE, but:
• VBEP may show more granular info (multiple lines per item/date)
• VBBE is compiled from VBEP, VBFA, VBKD and other sources during ATP/MRP processes

Best practice : Use VBEP when analyzing document-driven open quantities, and use VBBE for ATP/MRP logic and planning requirements.

I hope my explanation is clear enough and answer your main questions.

Best regards,

Jeremy