Project Billing for Customer Projects in SAP S/4HANA Cloud
Updated for SAP S/4HANA Cloud 2108
The preparation of a bill plays a vital role in a professional services scenario. Thus, the new Project Billing in SAP S/4HANA Cloud for Professional Services is one of the biggest changes in the professional services scenario since its existence. The following article shall provide further details on motivation, included functionalities and future planning.
Why new solution?
The former resource-related billing in SAP S/4HANA Cloud has been in place for several years, so there was the need to address not only feedback from customers and partners, but also holistically solve fundamental requirements. To give an example, the underlying source selection and material determination in the DIP Profile is not open to customers for customizing due to several reasons. This limits the number of activity types and sales/billing materials that can be used in the professional services scenario to the pre-delivered ones T001-T020, U001-U010 and E001-E040.
To overcome this problem and other restrictions, a completely new architecture for the billing preparation process was built. The key benefits of the new Project Billing solution are the following:
- Increased usability due to the usage of latest SAP Fiori elements.
- Prior preparation of billing data using a push principle. When a posting in ACDOCA/Universal Journal is detected as billing relevant, it is getting directly pushed to the new billing tables which also has an added advantage of performance improvement.
- Addition of several new features as compared to the earlier solution. This does not only include the possibility to add further activity types respective billing materials through a flexible material determination configuration, but also a generic access to Project Billing based on authorizations and an extended reporting on billing data.
Delivery and localization
The delivery of the new Project Billing functionality is enabled through the scope item 4E9 “Project Billing – Project-Based Services”. Next to DE and US, this scope item is relevant for all standard countries or regions except Brazil. Further information can be found on the SAP Best Practices Explorer.
Starting from SAP S/4HANA Cloud 2108, scope item 4E9 is delivered as standard scope item, which means that it is activated by default in all new customer systems. For existing brownfield landscapes, customers need to request for its activation specifically. The old billing solution (Business Catalog SAP_PSP_BC_PRJ_BILLING_PC with the applications Release Billing Proposals, Edit Billing Request and Release Billing Requests) is accordingly deprecated since 2108. However, the old billing solution is by implication still the default solution for the billing preparation process in the professional services scenario. Starting from SAP S/4HANA Cloud 2111, the new Project Billing solution will be the default solution. As both solutions can exist in parallel without impacting the existing billing process, customers can test the new Project Billing solution in a dedicated sandbox tenant or their quality system before moving to the new solution in a phased approach.
Features of new Project Billing in SAP S/4HANA Cloud until 2108
This chapter should give a short overview and some background information on the existing functionalities of our new Project Billing. For further details please also see the documentation on the SAP Help Portal.
The main application of our new Project Billing is the successor of the Release Billing Proposals app called Manage Project Billing. This app gives an overview on different billing data and is the central place for the billing preparation before the SD billing process itself starts. For now, the contract types Time and Expenses, Fixed Price and Periodic Service are supported. Additionally, the prepayments on account (for Time and Expenses billing elements) and down payment (for Time and Expenses and Fixed Price billing elements) can be processed. The contract type Usage Based is not yet supported and according billing elements are not displayed.
Fig 1 – Manage Project Billing Overview Page
When billing for a “Time and Expense” billing element is prepared, one or more postings can be fully or partially written off or postponed to the next billing cycle. Technically, these actions are saved in an own object called “Project Billing Request”. Compared to the existing billing solution, this allows the introduction of certain functionalities in the future (e.g. integration to the central approval framework). Additionally, it is possible to bring back formerly written off items, which means a restoration of written-off items that were part of Billing Document Requests created earlier (see SAP Help Portal).
Fig 2 – Prepare Billing screen
Once the Project Billing Request is submitted, a Billing Document Request is created. This is a difference to the old billing solution, in which a Debit Memo Request was created. Thus, the Billing Request Editor cannot be used anymore. As an alternative the features and functions in the Preliminary Billing Document can be leveraged.
Fig 3 – Comparison of business process flow for billing
As mentioned above, a central capability of our new Project Billing is the possibility to configure a flexible material determination. The new Self Service Configuration User Interface (SSCUI) includes a configuration step for making settings related to maintaining the Project Billing Profile in the “Manage Your Solution” app. That way a configuration expert can define which billing materials are determined for incoming costs or quantities on certain activity types or materials.
Fig 4: SSCUI for flexible material determination
To give an example, the below table shows how activity type T001 (Junior Consultant) is mapped to billing material T001 (Junior Consultant) in a Time and Expense scenario. The Project Billing profile CMPRJBL001 as well as the cost element group YBPS_BILL are fixed. The first line covers the scenario in which the activity type is available from the posting. The second one relates to the contingent worker scenario, for which only the material is given.
|PB Profile||Line||Mat. dir.||Qty/Costs||Material||Field Name||Set Name||Value|
|CMPRJBL001||1||Transfer Costs and Quantity||T001||GLACCOUNT||YBPS_T000|
|CMPRJBL001||2||Transfer Costs and Quantity||T001||GLACCOUNT||YBPS_T000|
The second application that is delivered besides the “Manage Project Billing” app is the application job “Schedule Repricing for Projects”. Due to the architectural change explained above (push instead of pull principle) and the fact that repricing is not run each time the “Manage Project Billing” app is used, the billing data needs to be updated when there is a change of the sales rate or material configuration. Compared to the old DIP run, this application job can be scheduled at the customer’s own discretion. For further details please also see the documentation on the SAP Help Portal.
The third application is again an application job called “Schedule Project Billing Preparation”. It allows customers to automate their billing processes through automatic creation of Billing Document Requests for different billing methods. The process definition can be narrowed based on different criteria. For further details please also see the documentation on the SAP Help Portal.
Access and usage of the new Project Billing
Scope item 4E9 does not only include the business role template “Billing Specialist – Projects” and the business catalog “Project Systems – Project Billing”, but also a switch on the information tab of the Plan Customer Projects app. The default setting of this flag is set to No until SAP S/4HANA Cloud 2108, which means that the old billing solution is used. Starting from 2111 release, the flag will be set to Yes by default which means that the new Project Billing solution will be the default solution.
The flag can be changed for single projects as long as the project is in planning stage. Once the project stage is set to Contract Preparation, this decision can no longer be changed. Additionally, the flag can be removed from the UI using the key user functionality for adapting UIs.
Fig 5: Flag in Plan Customer Projects application
There are in principle two ways how billing elements in the “Manage Project Billing” app are shown. The first one is based on the authorizations maintained on the business role, which means that for example a central billing team can be allowed access to all billing elements in one or more specific service organizations. The second one is based on assignments in the project or rather sales order. This access is designed on the billing item level: If a user is assigned in any partner function on sales order item level, the according billing element would be shown. If the assignment is on sales order header or accordingly project level, all billing elements for that project would be accessible. The filter that uses this logic in the “Manage Project Billing” app is My Billing Elements.
Conclusion and features beyond SAP S/4HANA Cloud 2108
The following features are currently planned as part of our roadmap. This list is not intended to be exhaustive, please see also SAP Road Map Explorer.
- Enablement of contract type Usage-Based Billing.
- Additional Item functionality enabling project billing specialists or billing team members to add a manual item in the Prepare Billing screen, which results in additional credit or revenue.
- Approval workflow for project billing requests.
For more information on the new Project Billing SAP S/4HANA Cloud, check out the following links: