3740941 - Requirement Date in Capacity Scheduling Table differs depending on dynamic pegging and app filter context

In the Capacity Scheduling Table app, the Requirement Date displayed for a component or product may appear inconsistent, even when purchase orders or receipts have been created with identical dates.

In some cases, the same production order can show different Requirement Date values depending on the filter criteria used in the app, such as when loading the app with or without a specific product filter.

This behavior can lead to the impression that the Requirement Date is incorrect or not clearly derived.

SAP S/4HANA Cloud Public Edition

The Requirement Date shown in the Capacity Scheduling Table is calculated based on dynamic pegging.

Dynamic pegging forms the relationship between receipts and requirements at runtime according to the current planning situation. Because of this, the Requirement Date is not necessarily copied from the manually maintained purchase order date or from a fixed source document date.

When multiple receipts exist on the same day, the system may dynamically determine different pegging relationships between receipts and requirements. As a result, the Requirement Date can vary depending on which receipt is used first to cover a given requirement.

Since the pegging relationship is recalculated in the current application context, the displayed Requirement Date may also differ depending on the filters used in the app.

Additionally, according to the standard definition of the field, the Requirement Date is:

• The date at which the requested component or product is due, for example, for production or shipment. It is calculated based on dynamic pegging and displayed in the column.

It is also possible for orders to exist without a Requirement Date.

This behavior is consistent with the current standard design.

The Requirement Date in the Capacity Scheduling Table should be understood as a dynamic planning result based on pegging logic, and not as a fixed date directly copied from the order or other manually maintained receipt date.

Therefore:

• The displayed Requirement Date can change depending on the dynamic receipt-requirement assignment.
• The displayed Requirement Date can also vary depending on the app filter context, since pegging is recalculated accordingly.

SAP Help Portal - Capacity Scheduling Table

requirement date, capacity scheduling, scheduling table, dynamic pegging, purchase order, po date, date mismatch, misalignment, inconsistent dates, capacity planning, production planning, production scheduling, public cloud, s/4hana cloud, PP-CFS-SCH , KBA , PP-CFS-SCH-2CL , Capacity Scheduling (Public Cloud) , Problem