Skip to Content
Product Information
Author's profile photo James Erickson

2108 CDS views for Project Profitability Use Cases

Extending SAP S/4HANA Cloud is a key approach to support business priority use cases backlogged from your fit to standard analysis workshops. The Virtual Data Model and CDS Views are an important component in your implementations extensibility approach. This blog will provide some ideas for using CDS Views related to Customer Projects in SAP S/4HANA Cloud to provide quick insight to action on project performance, especially in the area profitability.

You should be aware of the SAP Extensibility Explorer for SAP S/4HANA Cloud. Within this Accelerator is is a great setup guide called “Combined Reporting for Professional Services and Sales Orders”. The solution objective of that guide is to provide an analytical structure and reporting to view and compare Customer Project profitability. This scenario provides reporting that combines both the Project and its ultimate Financial Reporting result including profitability in an easy-to-use analytical query. See an example of this query result showing Billed Revenue – Actual Cost = Recognized Margin.

This blog provides the steps to both add-to and improve your analysis approach to the next depth of the Customer Project – specifically the work item level. The 2108 release of SAP S/4HANA Cloud has several newly released CDS Views that make this possible. Before you begin it is important to have a working knowledge of the Custom CDS View and Custom Analytical Query apps.

In this blog I focus on two of these views:
I_ProjectBillingElementEntrFlw This CDS view contains the details of project billing request and billing document request for each project billing element entry.
I_PrjBlgElmEntrJrnlEntrLink This CDS view provides the link between the project billing element entry and the journal entry postings for work breakdown structure elements.

The following three steps can be used as guidelines for this proof. Also, the use of filters in the CDS Views is encouraged as you prove your report results. Ledger ‘0L’ and Accounting Document type ‘RV’ were used in this example. The field lists and Join conditions given are guidelines as well, and may vary based on your use case.

Step 1
Create CDS View (YY1_bildoctoentryflo) with the following Join conditions between CDS View I_BillingDocumentItem and CDS View I_ProjectBillingElementEntrFlw

Below you will see the elements/fields chosen for the resulting CDS view (YY1_bildoctoentryflo)

This step creates a CDS View combining Project Data with the Billing Document Request created as a result of 4E9 Manage Project Billing app. Be sure to add the field ProjBillgElmntEntrItmUUID to the result field list because is used in the next Join step.

Step 2
Add this data set CDS View (YY1_bildoctoentryflo) to I_PrjBlgElmEntrJrnlEntrLink to create the CDS View (YY1_projflowtoJE)

Below you will see the elements/fields chosen for the CDS view

The result of this step creates a CDS view (YY1_projflowtoJE) that links the project work items to the Journal entry items done as a result of the 4E9 Create Billing Documents app.

Step 3
Now create an CDS View of Scenario type Analytical Cube using YY1_projflowtoJE data and I_GLAccountLineItem with the following Joins

Below you will see the elements/fields chosen for the CDS view

Here is an example of the Analytical report that displays cumulative values at the work item level:

The above report analysis is filtered to depict only the following Journal Entry from the project:

I hope this will help you use these new data sources to deliver a deeper level of understanding to project profitability.
Stay tuned to the 2111 What’s New viewer for additional enhancements in scope item 4E9 that a) allow additional billing items to the Project Billing request, and b) provide an additional contract type for a usage-based billing.

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.