Identifying New Features of Master Data and Organizational Management Objects
Identifying New Features of Service Orders and Service Confirmations
Identifying New Features of In-House Service
Identifying New Features of Recurring Services
Identifying General New Features in Service in Release 2025
Identifying New Features of Master Data and Organizational Management Objects in 2025 FPS1
Identifying New Features of Service Contracts and Recurring Services in 2025 FPS1
Identifying New Features of Service Quotations, Service Orders and Service Confirmations in 2025 FPS1
Identifying New Features of In-House Service in 2025 FPS1
Identifying General New Features in Service in 2025 FPS1

Calculating Planned Costs and Revenue for Unplanned Items

Objective

After completing this lesson, you will be able to calculate planned costs and revenue for unplanned items

Planned Costs and Revenue for Unplanned Items

Improved Percentage of Completion Method Calculation

Comparison table of revenue recognition between ‘0L (Leading ledger)’ and ‘2L (Non‑leading ledger)’. Sections: ‘Plan data’, ‘Time confirmation’, ‘Billing’, and ‘Period‑end closing’. For 0L: planned revenue 200 EUR; planned costs 100 EUR. Time confirmation: actual costs 20 EUR; deferred costs 20 EUR. Billing: billed revenue 20 EUR; revenue‑based POC calculated as actual revenue/planned revenue = 20 EUR/200 EUR = 0.10 (10%); RAC = 1; accrued costs computed as POC × RAC × planned costs = 0.10 × 1 × 100 = 10 EUR. Period‑end closing: RAC calculation ‘actual costs (ledger n)/actual costs (leading ledger)’ gives 1; recognized costs ‘POC × RAC × planned costs’ = 0.10 × 1 × 100 = 10 EUR. For 2L: planned revenue not available; time confirmation: actual costs 30 EUR; deferred costs 30 EUR. Billing: billed revenue 20 EUR; revenue‑based POC is 10% from the leading ledger; accrued costs 10 EUR. Period‑end closing: RAC calculation 30 EUR/20 EUR = 1.5; recognized costs 0.10 × 1.5 × 100 = 15 EUR. Visual cues: blue table, a document icon in the Billing row, an ‘X’ indicating ‘Not available’ for planned revenue in 2L, and arrows showing transfer of the 10% POC and the 10 EUR accrued costs from 0L to 2L.

Here you can see a comparison table of maintained costs and revenue data (for example related to revenue recognition) where a comparison is made between the ‘0L (Leading ledger)’ and the ‘2L (Non‑leading ledger)’ ledgers. What is included here and what the table tries to illustrate is the use of the percentage of completion (POC) method for recognizing revenue and costs over the duration of a long-term project or contract.

Note

See the following video to learn more about planned costs and revenue for unplanned items in a service process and how this influences the percentage of completion (POC) method for recognizing revenue and costs over the duration of a long-term project or contract:

The fact that planned costs and revenue can be calculated for unplanned items in a service order results in a optimized POC calculation if these unplanned items are indeed present in the service order.

An Example

Screenshot of an unplanned service order item that shows the planned cost (360 USD) and revenue (700 USD) data for the ongoing and the baseline data set.

Starting with SAP S/4HANA Cloud Private Edition 2025, the unplanned item in the service order shows the planned cost and revenue data for the ongoing and the baseline data set.

As with other items, the baseline data is written on the first release of the item and can be updated by the Update Baseline button.

Note

Since release 2025, if an unplanned item is added to the service confirmation, saved, and then deleted while the status is Open, it will also be removed from the corresponding service order. This was not supported before release 2025.

Summary

  • Starting with SAP S/4HANA Cloud Private Edition 2025, unplanned items in a service order are pricing-relevant, which means that planned cost and revenue can be calculated for unplanned items in a service order.
  • Because of this, unplanned items are now considered in the POC method.
  • The percentage of completion (POC) method, especially in the context of SAP's Event-Based Revenue Recognition (EBRR), is an accounting technique used to recognize revenue and costs over the duration of a long-term project or contract.