3754728 - Issue with Key Date Functionality in Fiori App – Project Actuals in SAP S/4HANA Cloud Public Edition

• The Key Date functionality in the Fiori App – Project Actuals is not working as expected.
• When the Key Date is set to a past date, the report still displays actual values for postings made after the Key Date.

Example: A MIGO document linked with a WBS element was posted on 11.05.2026. When the Key Date is set to 01.05.2026, the report still shows the actual values.

SAP S/4HANA Cloud Public Edition

1. Open the Fiori App – Project Actuals.
2. Set the input parameters to Fiscal Year: 2026 and Key Date: 11.05.2026.
3. Observe that the report displays the actual values correctly.
4. Change the Key Date to 01.05.2026.
5. Observe that the report still displays the actual values, even though the posting date is later than the Key Date.

The issue arises because the Key Date in CDS-based analytical apps, such as Project – Actuals, is designed to display time-dependent master data attributes as of the specified date. However, it does not filter transactional postings based on their posting date. Consequently, postings with dates later than the Key Date will still appear when running the app within a fiscal year context.

To achieve the desired restriction of excluding postings after a specific date, it is recommended to apply a filter based on the posting date or fiscal period. This approach will allow to exclude postings after the specified date. 

For further details, refer to the following community link: The Key Date in "Project - Actuals" app has no impact on data

The Key Date in "Project - Actuals" app has no impact on data

Project Actuals, Key Date , KBA , CO-FIO-OM-IS-2CL , Reporting (Public Cloud) , Problem