Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
23,457

Relevant for SAP S/4HANA Cloud Public Edition 2408. Last update on 29.07.2024.  

Introduction
Invoicing plays a critical role for companies in the consulting industry. Therefore, Project Billing in SAP S/4HANA Cloud Public Edition is a key capability in the professional services scenario. The following article provides more details on the motivation and the included functionalities.

Why Project Billing in SAP S/4HANA Cloud Public Edition?
The former resource-related billing in SAP S/4HANA Cloud Public Edition has been in place for several years, so it was necessary not only to address feedback from customers and partners, but also to solve fundamental requirements in a holistic manner. For example, the underlying source selection and material determination in the DIP profile was not open to customer customization for several reasons. This limited the number of activity types and sales/billing materials that could 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 main benefits of this Project Billing solution are:

  1. Increased usability by using the latest SAP Fiori elements. This makes it possible to use centrally provided functions such as sorting, grouping, and filtering or the use of different variants in viewing the provided data.
  2. Prior preparation of billing data using a push principle. When a posting in ACDOCA/Universal Journal is recognized as billing relevant, it is pushed directly to the new billing tables, which also has the added benefit of improving performance.
  3. Addition of several new features as compared to the previous solution. These include not only the ability to add additional activity types and billing materials through a flexible material determination configuration, but also generic access to Project Billing based on authorizations and enhanced reporting on billing data. 


Delivery and localization
The delivery of the Project Billing functionality is enabled by scope item 4E9 “Project Billing - Project-Based Services”. This solution process is relevant for all standard countries and regions. Further information can be found on the Process Navigator (SAP Best Practices for SAP S/4HANA Cloud Public Edition).
As of the release of SAP S/4HANA Cloud Public Edition 2108, scope item 4E9 is delivered as a standard scope item, which means that it is activated by default in all new customer systems. For existing brownfield landscapes, customers must specifically request its activation. 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 therefore deprecated as of 2108. Please see Note 3072179. The deletion of the deprecated Business Catalog is currently planned for release 2508. Starting from SAP S/4HANA Cloud Public Edition 2111, the Project Billing solution is the default solution for the billing preparation process in the professional services scenario. Since both solutions can coexist without impacting the existing billing process, customers can migrate to the Project Billing solution in a phased approach. This means that customer projects using the old solution can exist next to other ones with new solution, but there is no possibility to change running projects from one solution to the other. There is also an accelerator in place that can be used to extract project plan data in the format of the data migration template and that eases migration efforts.
 
Overview on the main application Manage Project Billing
The main application of our 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 Sales Billing process itself starts. All four contract types (Time and Expenses, Fixed Price, Periodic Service and Usage Based) 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.

Figure 1 - Manage Project Billing Overview Page

During preparation of a bill for a “Time and Expense” or "Usage Based" billing element, 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 old billing solution, this allowed the introduction of certain functionalities (e.g. integration to the central approval framework, accessibility to historic data). 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).

On top of that, a billing specialist or billing team member can add, edit and delete additional items in the project billing request. This helps the users to create additional revenue from heaven or discount. Further details can be found in the documentation on the SAP Help Portal.

Figure 2 - Prepare Billing screen

Once the Project Billing Request is submitted and the approval workflow is not in place, a Billing Document Request is created automatically. In the next step, the Billing Document can be created directly or the Preliminary Billing Document can be used to make further changes to the invoice. There are standard applications for billing clerks to manage Preliminary Billing Documents, or alternatively, the "Manage Preliminary Billing Document - Services" application, which is tailored to the needs of a billing specialist.

Figure 3 - Business process flow for billing

Approval workflow for project billing requests
Configuration experts have the possibility to enable and configure different workflow scenarios for project billing requests with the application “Manage Workflow for Project Billing Requests”. If such an approval workflow is in place, the end-to-end process stops after the submission of the project billing request and no follow-on documents can be created. Only once the project billing request is approved, the billing document request is created automatically. If the project billing request is rejected, the included items get reinstated and they are again available for billing in the Manage Project Billing application.
The automatic creation of a billing document request after approval, for example, is not possible if there is a price change between the submission and approval of the project billing request. Administrators can track such errors in the app “Flexible Workflow Administration” with the Scenario ID WS01800259. Additionally, the project billing specialist or billing team member can use the Manage Project Billing Requests app (see next chapter) to easily filter project billing requests with approval status “Released” but lifecycle status “In Process”. To resolve such a scenario, the repricing job that is explained further below can be used to re-trigger the approval workflow.
The approver can view basic billing data during the approval process in the My Inbox, such as customer, project or aggregated cost and revenue information. If needed, she or he can also navigate from the project billing request number to its details to check written-off and postponed items. The display of this project billing request is also explained in the next chapter. To inform the project billing specialist on the approver’s decision, a notification is sent to the workflow initiator in case of approval, rejection and successful billing document creation.
Generic information on business workflows in SAP S/4HANA Cloud Public Edition can be found on the SAP Help Portal. Specific information on the workflow for project billing requests can be found on the SAP Help Portal, too.

Figure 4 - Approval screen for a project billing request in the My Inbox

Application to manage project billing requests
In contrast to the legacy project billing solution, which did not allow to access released billing proposals from the past, the Project Billing offers the possibility to display submitted project billing requests. The application “Manage Project Billing – Project Billing Request” lists permanent project billing requests, which means that these requests were already submitted from the main Manage Project Billing application.
To access a project billing request in this new application “Manage Project Billing – Project Billing Request”, the business partner of the logged in user needs to be part of any header role in the corresponding customer project. So, if the user is maintained as project manager or any other standard or custom role of a customer project, she or he would see all project billing requests that were created for this specific project.
The main purpose of this application is not only to track the lifecycle and approval status of historical project billing requests, or the decision note entered by the approver during approval/rejection, but also to look at the details of these project billing requests. The UI of a project billing request has the same look and feel as the billing preparation screen with the difference that certain actions are certainly not allowed anymore. The buttons for editing, deleting, and submitting the project billing request as well as for write-off, postponement and date deferral are not visible. Instead, the project billing request can be rejected, or the follow-on billing document request can be triggered. The former is needed to withdraw a project billing request from the approval workflow, the latter is needed in case the automatic billing document request creation failed.
Further details can be found in the documentation on the SAP Help Portal.

Figure 5 - Application to manage project billing requests

Configuration possibilities for flexible material determination in Project Billing
As mentioned above, a central capability of 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. There is no default content or demo data provided in newly provisioned quality or productive tenants, which means that this configuration needs to be added in a one-time activity.

Figure 6: 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 (YBPS_UBBT in Usage Based scenario) 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 ProfileLineMat. dir.Qty/CostsMaterialField Name Set NameValue
CMPRJBL0011 Transfer Costs and QuantityT001GLACCOUNTYBPS_T000 
     ACTIVITYTYPE T001
CMPRJBL0012 Transfer Costs and QuantityT001GLACCOUNTYBPS_T000 
     MATERIAL T001

G/L accounts that are classified as revenue or balance accounts accounts as well as G/L accounts that are used for billing should not be included in the cost element group YBPS_BILL. Doing so could lead to problems such as the incorrect or duplicated inclusion of cost postings in the billing process.
 
Application jobs for automation and repricing
The first application job that is offered in Project Billing is 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. Further details can be found in the documentation on the SAP Help Portal.
The second application job is “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. Further details can be found in the documentation on the SAP Help Portal.

Access and usage of Project Billing
Scope item 4E9 does not only include the business role template “Billing Specialist – Projects” and various business catalogs, but also a switch on the information tab of the Plan Customer Projects app. Starting from SAP S/4HANA Cloud Public Edition 2111 release, the default setting of this flag "Use Project Billing (New)" will be set to Yes which means that the Project Billing solution will be the default solution. If the old billing solution is still needed, the flag can be changed manually. The BAdI “Custom Checks on Project Save” (Business Context: Engagement Project) can be used to ensure that either the legacy solution or Project Billing is used for all newly created customer projects.
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.
In a long-term meaning after the deletion of the old resource-related billing process mentioned above, this Project Billing switch will be deprecated and not shown anymore.

Figure 7: 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 profit centers or cost centers. 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. More information can be found in Note 2971025.

For more information on the Project Billing solution in SAP S/4HANA Cloud Public Edition, check out the following links:

33 Comments
LucaBia
Participant
0 Kudos
Hi Andreas,

very nice blog, the new Project Billing sounds really interesting and we look forward to testing it.

Concerning the new Billing Document Requests, will they be affected by the same modification constraints as DMRs?

The impossibility to edit basic elements such as the Customer Purchase Order Reference currently forces users to perform rather time-consuming and annoying operations to satisfy the requirements of customers in terms of reference information to be output in the printouts and in the XML eInvoices.

Thank you,

-Luca-

 

 
A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Luca,

Thanks a lot for your comment. Your assumption is correct, modifications on Billing Document Requests are not supported. Please leverage on the functionality given in the Preliminary Billing Document, where for example the Header Texts can be added or changed. This document is exactly designed for your described business scenario, in which a customer upfront can receive and agree on a preliminary invoice and changes can be done if needed. Please keep in mind that the Customer Reference from the Sales Order is not changeable in the billing process at all.

Best regards,

Andreas
Feras_Al-Basha
Product and Topic Expert
Product and Topic Expert

Great blog and valuable information. CE 2008 has outstanding innovations for professional services.

Thank you Andreas !

Kind regards,

Feras

Haaroon_Daya
Explorer
0 Kudos
Hi Andreas

Thank you Great Post

WRT your comment below: The BAdI Custom Checks on Project Save (Business ContextEngagement Project) can be used to ensure that either the old or new project billing is used for all newly created customer projects

Does this mean we can default the selection to "NO". If so can i get some guidance on how to set this up via the Custom Checks on Project Save Badi

BR

Haaroon
A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
Hi Haaroon,

Thanks a lot for your question. The default value of "Use Project Billing (New)" cannot be changed and is always set to Yes. The BAdI is rather a security measure to prohibit the existence of customer projects with either the one or other setting.

So if you e.g. want that customer projects are only created/saved with the old process, projects managers need to manually change the flag. If they forget, the BAdI can ensure that projects cannot be saved with this "wrong" setting.

Best regards,

Andreas
aramaisa
Participant
Hi Andreas,

Thank you for your swift response. last week I sat with Haaroon he managed to put the Badi to ensure that the project does not save if the flag is on Yes. Business thought there is another Badi to switch the flag to No with this badi.

kind regards,

Angelina
Haaroon_Daya
Explorer
0 Kudos
Hi Andreas

 

Thank you for your response.

I have added the validation in the badi 🙂

BR

Haaroon
Sean_House
Explorer
0 Kudos
Is there any commitment to when this functionality would be available on premise?  Are we still stuck with DP91 ?
A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
0 Kudos

Thanks a lot for your question. The Project Billing is part of SAP S/4HANA Cloud, Public Edition. There are currently no plans to make this available in SAP S/4HANA, Private Edition.

IMSYadav
Active Participant
0 Kudos
Hello Andreas,

I was working for New Billing Solution and found some conflicts and Questions:

  1. Usage Based Project:


Here we found few discrepancies in SAP documentation, Video, etc. Please check below configuration help maintained.

Here, the U-material provided is a usage-based material that is configured to transfer both costs and quantities. Also, the Material Direct is set to True.

  • Qty/Costs: Transfer Costs and Quantities Only



  • Material: U001



  • Material Direct: True (This is not mandatory, however if we try activating this, system does not create any issue)


To the above material determination, add the following criteria:

  • GLACCOUNT: YBPS_UBBT



  • MATERIAL: U001 (Direct Activity Allocation does not have any Material in posting, so it should be Activity type)


 

  1. Contingent Worker


In case of Contingent worker, SAP has given cost element group as YBPS_S001 under YBPS_T000 and YBPS_S000 as separate. using this we can bill Purchased service and get relevant Material in Billing but In our case we have to Bill as normal (T001-T020) materials with quantity. So we can define these settings as per our requirement. System has flexibility to set as required.

Please check and help us to understand.

thanks

Sunil
A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hello Sunil,

Thanks a lot for your questions. The configuration of the Project Billing Profile for our Usage-Based Billing scenario is very similar to the Time & Expense one. In your referenced video, the material direct flag is not set to true, so I am not sure what you are referring to? For the second part (material U001 is maintained as criteria instead of the activity type) your understanding is correct. If the posting is done through activity allocation, the criteria needs to be maintained with activity type.

The demo configuration for material S001 and cost element group YBPS_S002 is not necessarily meant for the contingent worker scenario, but rather for general purchased services (scope item J13, chapter 4.5). You can maintain the Project Billing Profile for the contingent worker scenario as described in this blog.

Best regards,

Andreas
IMSYadav
Active Participant
0 Kudos
Hi Andreas,

  1. I am referring to configuration help maintained in manage your solution where Material Direct: True is activated  (but This is not mandatory, however if we try activating this, system does not impacts) system works fine in both options.

  2. Material is not being used in "manage/create direct activity allocation" so we are not getting material in this posting so how system will determine Material U001 in billing. this app is using activity type instead of Material while postings so we need to add Activity type in Criteria. in video material is being used in criteria which is wrong.

  3. In contingent worker or Purchased Services, we need config for both separately as per business, In case of contingent work we need T* (where activity type or material are used as criteria) in billing and if we consider purchased service then S* (where material or activity type are not coming as criteria) will be in billing.


please let me know in case you feel anything different.

thanks

Sunil
A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hello Sunil.

  1. The example in the configuration help explains the behavior with a material direct flag: For any cost posting that matches this criteria, the source material defined in the posting is determined. This is because the Material Direct option is selected. However, in the absence of a material in the posting, the material determined is U001. This last sentence explains why there is no difference for you.

  2. Yes, your understanding is correct.

  3. As you correctly stated beforehand the configuration allows such flexibility.


Best regards,

Andreas
Sanne
Explorer
0 Kudos
Hello Andreas,

thank you for your blog. I have a question about screen adaptation. Do you know if it is possible to add a custom field to the "manage project billing app"? We have a customer requirement to show a custom field representing the type of project to this app for filtering reasons.

 

Many thanks,

Sanne van Bruijnsvoort
A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
Hi Sanne,

Thanks a lot for your question.

  • The extensibility scenario under the business context Accounting Coding Block (business scenario: project-based services transfer from time recording to invoice printout) allows you to add the custom field to the item details of a Project Billing Request. Thus, it will be visible in the Prepare Billing UI of our Manage Project Billing application.

  • However, the other extensibility scenario (to which you probably refer) across Sales Order and Billing Document Request does not offer the possibility to add the custom field in our Manage Project Billing application. In case this would be valuable for your business scenario, please submit a new improvement request on our Customer Influence Portal.


Best regards,

Andreas
aramaisa
Participant
0 Kudos
Hi Andreas

hope you are well.

Please advise if there is an option to build reasons for Write-offs that  the billing clerk can use to just select when  executing a write-off on Manage Project Billing. Business will like to have a list of write off reasons that the users processing the write off can select from and then the selected reason be visible for to the approval.

Kind regards,

Angelina
A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
Hi Angelina,

Thank you for your question. The functionality you describe is not available in Project Billing, but please feel free to use our Customer Influence Portal to create a new request.

Best regards,

Andreas
hdita
Explorer
0 Kudos
Hi Andreas,

Thank you very much for the valuable information!

I do have a question please: we know that we can combine multiple billing document requests into one invoice, if some requirements are met. But I have tried to combine two down payment requests created for same client (even for same project actually) into one invoice, in this case down payment invoice, but those couldn't be combined. What is the reason for this?

Best regards,

Horatiu Dita
A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
0 Kudos
Dear Horatiu,

Thank you for your insightful question. During the posting of a down payment request (also known as an FAZ invoice), there is a need to handle each line item separately in Financials due to the special G/L indicator. Therefore, even if two down payment billing plan items under the same sales order item in the same customer project are submitted in Project Billing, you will receive two different project down payment requests and, accordingly, two separate FAZ documents.

Best regards,

Andreas
0 Kudos
Hello,

In projects, how is the estimated actual calculated? I see this in time and expense, but I don't see it in time and material.?

Thanks in advance
A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
0 Kudos
Dear Elif,

Thank you for your question. In most cases, Estimated Actuals = Billed + Unbilled + Billing in Process. This represents the overall actuals that can be estimated at the current point in time. Exceptions can occur in the on-account scenario.

I believe there may be some confusion in your question regarding the terms “time and expense” and “time and material”. Both terms are often used interchangeably and refer in Project Billing to the billing method “Time and Expenses”.

Best regards,

Andreas
0 Kudos
Hello Andreas,

Thank you for answer I understand the calculation logic. I managed to add two items as t001 to my project. I could perform time recording. While one of the items fell under 'estimated actual,' the other did not. Is there anything within these data that could be affecting this?
A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
0 Kudos
Dear Elif,

This requires a closer look at your system, and I am happy to assist here. May I request that you contact me through your SAP representative?

Best regards,

Andreas
Johnny_B_
Active Participant
0 Kudos

Hello @A__Hammerschmid thank you for this post and the video recording.

One question: In consulting services it is common practice to submit a list of time recordings to the customer an get approval (or some records rejected) so that the billing is prepared accordingly.

Does the system support such a process in any way? I am missing an app to export all time recordings on a given project, or some (external) approval workflow.

thank you, Johannes

A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Johannes,

This is possible, please see the sample scenario Timesheet Data Export on the Extensibility Explorer. 

Best regards,

Andreas

Johnny_B_
Active Participant
0 Kudos

Hello @A__Hammerschmid thank you for the quick response.

I have a few comments. First, the proposed side-by-side application looks to me a bit outdated, it is based on NEO and it says you can export the timesheet entries "for the currently logged on user". And it seems to be a manual process to export, send to the customer, retrieve approval or rejection, adjust timesheet etc... this is not a scalable, robust process.

In your presentation you have explaind the process from timesheet posting --> approval --> PBR --> PBD --> BDR --> final BD (billing document).

I see in my daily project life, that billing documents are frequently rejected by the customer, for different reasons (example: booking on wrong WBS). What do we do in this case? I would have to revert (cancel) all steps from BD to BDR to PBR to the initial timesheet posting, the consultant corrects the WBS assignment, and then the process starts again. Is this feasible?

What do I do if a billinng document is rejected and I need to do corrections? The earlier we can identify this, the better. Maybe when creating the preliminary BD I should send this PDF preview to the customer? What do you think - how can the system support this process, which happens all the time?

Thanks, Johannes

A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Johannes,

You are correct that the example scenario is a bit dated, but the overall concept of this side-by-side extensibility scenario remains valid. The Timesheet API can be leveraged to cover such a scenario as there is no standard functionality available. Thus, you also have flexibility in design. Whether it is for the logged-in user or based on other filter criteria is up to you, as is the degree of automation. When the sample scenario was created, the business process was such that a consultant would print his own timesheet so the customer could sign it on-site. Of course, such a process might not be relevant to you.

The timing of customer approval depends on the business process and its needs. Does the customer also approve tax and other information on the invoice? If so, I would use the Preliminary Billing Document (PBD) for such approval. If the customer rejects, you can easily amend or discard the PBD without affecting the normal BD number range. If the customer only approves the timesheets, then I would include such an approval earlier before the BDR creation, especially if you also want to keep the option to move time records to another work package.

I hope this is helpful. I am also willing to discuss directly over a call – please feel free to reach out to me directly if needed.

Best regards, Andreas

Johnny_B_
Active Participant
0 Kudos

Hello @A__Hammerschmid  I have one more question for PFS projects, especially for billing "Time & Expense".

Time is clear to me (based on timesheet entries etc...)

But what is "expense" meant to be?

A standard scenario is that it is agreed with the customer to bill all travel expense, like flight tickets or hotel bookings. These are posted as supplier invoices to the System and are "expenses" for my project.

Can I reference such supplier invoices in the project billing preperation? I did not find this option. I only can add "additional items" but it is manual and I would first have to look for all posted supplier invoices.

Could you please explain, what "Expense" is in this context?

UPDATE: I found out how it works, by mapping the cost elements to expenses accordingly. This is a great solution!

Thanks, Johannes

A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Johannes,

I'm glad you've figured it out. Let me explain further to confirm your understanding.

Expenses can be posted as costs to a WBS Element through multiple channels, such as SAP Concur, the creation of a manual supplier invoice, or journal entries. I agree that in a standard scenario, these costs are billed at a 1:1 ratio to the customer. Project Billing supports this through the configuration "Transfer Costs Only" in the billing profile. In this billing profile (SSCUI 103637), the cost element group (for example, YBPS_E001) and its G/L Accounts need to be correctly mapped to the expense material (for example, E001).

As explained in the above blog, additional items are used in a different scenario, which I refer to as "additional revenue from heaven or discount".

Best regards, Andreas

Johnny_B_
Active Participant
0 Kudos

Hello @A__Hammerschmid one more question: Is there any support in the PFS solution for quotation management? The idea would be that I create a project in planning stage with work packages and expenses, and then I would like to create a customer quotation for this. Any ideas? Or maybe this is on the Roadmap?

Thank you, Johannes

A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Johannes, 

Our Professional Services scenario in S/4HANA Cloud Public Edition is currently not meant for quotation management. Such a capability is also not planned on the roadmap. 

Best regards, Andreas

XAVIER2
Associate
Associate
0 Kudos

Thanks, it is great !
unfortunately in our SAP demo system like E5Z AND EOT , i am not able to test these new recognition method, (P005 is still missing) i am a little bit surprise as these system have migrated in 2408
Could you indicate me a system available in which i would be able to test it ? 
Have a nice day

 

A__Hammerschmid
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi @XAVIER2,

I assume your question refers to this blog on Customer Projects with T&E Billing & PoC-based Revenue Recognition. P005 is only an example and is not delivered by default, so it is at the customer’s discretion and decision to create new contract material if required. Please contact me directly regarding SAP internal demo systems (this blog is published externally).

Best regards,
Andreas