Symptom
Incompatible Change: Enhancements to custom CDS views created based on C-1 released I_ProjectBillingElement view.
Environment
SAP S/4HANA Cloud Public Edition
Cause
- As of SAP S/4HANA Cloud Public Edition 2602 release, we have replaced the previously used _WBSElement association with _EnterpriseProjectElement association in I_ProjectBillingElement DCL. This change improves the performance of the CDS views.
- If you do not adapt your custom CDS views by republishing them or by explicitly adding associations using developer extensibility tools, users will get unrestricted access to the data. Data control will not be applied correctly, and the system will ignore authorizations for users by default.
Resolution
Scenario 1: CDS Views Created Using Key User Extensibility.
(Action required immediately after your Q‑system CE2602 upgrade and before your production upgrade)
- If you have created custom CDS views using key user extensibility, you need to republish the topmost custom CDS view from the list of the CDS views you created based on the I_ProjectBillingElement view.
- For example, if YY1_CDS1 is created based on I_ProjectBillingElement and YY1_CDS2 is created based on YY1_CDS1, then select YY1_CDS2 and perform the further steps. This ensures that all dependent views are updated at once.
- When you republish the topmost custom CDS view based on I_ProjectBillingElement, all associations and Data Control Language (DCLs) are created and exposed as needed.
You need to follow these steps:
-
Log in as Extensibility Specialist.
Ensure you have the necessary authorizations to manage and publish custom CDS views. -
Navigate to the Custom CDS Views app in your SAP S/4HANA Cloud Public Edition system.
-
Filter for high priority tasks. Use the Task Priority filter to display tasks marked as High or Very High.
-
From the list, select the topmost custom CDS view created based on I_ProjectBillingElement and navigate to the detail page of this custom CDS view. This ensures that all dependent views are updated at once.
-
In the Custom CDS Views Details page, click the Tasks tab. You will see the tasks that you need to perform.
-
Click Edit.
-
Click the Publish button at the bottom-right corner of the screen. The custom CDS views will be republished.
Scenario 2: CDS Views Created Using Developer Extensibility Tools.
- If you have created custom CDS views based on I_ProjectBillingElement in a three-system landscape using developer extensibility tools, and if the custom views inherit the DCL from I_ProjectBillingElement DCL, then you need to manually add the association and the key for this association in your custom CDS views.
- This means that you need to explicitly expose the _EnterpriseProjectElement association in every custom CDS view that inherits the DCL from I_ProjectBillingElement DCL. You also need to add the field ProjectElementUUID to extract data from the _EnterpriseProjectElement association.
- In this scenario, you do not need to wait until the 2602 upgrade. Custom CDS views created using developer extensibility tools can be adopted starting from the 2508 release, as the _EnterpriseProjectElement association and the field ProjectElementUUID are already present in the I_ProjectBillingElement view and can be exposed to custom CDS views by means of developer extensibility tools.
- With the corresponding adoption, your custom CDS views will be prepared for the 2602 I_ProjectBillingElement DCL change, and you will avoid day-one impact.
Keywords
I_ProjectBillingElement, DCL, Enhancement to custom CDS view, Custom CDS view, Incompatible change, Project Billing, Billing element, PPM-SCL-BIL, PPM-SCL-BIL-FIO, SAP S/4HANA Cloud Public Edition. , KBA , PPM-SCL-BIL , Project Billing (Public Cloud) , PPM-SCL-BIL-FIO , Fiori UI for Project Billing (Public Cloud) , Problem
SAP Knowledge Base Article - Public