A cluttered Chart of Accounts (CoA) can slow down financial processes, hinder automation, and create compliance risks. Before moving to SAP S/4HANA, optimizing your CoA is the first and most critical step!

In this blog, we introduce the SMART framework—a strategic approach to standardizing, modernizing, and future-proofing your CoA. With real-world use cases, before-and-after examples, AI-powered insights, and a three-step action plan, you’ll discover how to build a scalable, AI-ready CoA for the cloud.

New Release

PUBLIC

February 2025

Dear Convergent Charging and BRIM community,

We are glad to announce another release of the latest SAP Convergent Charging 2023 FPS3, which introduces intuitive features designed to enhance functionality and user experience. This update brings exciting capabilities, including new monitoring metrics for business data growth, streamlined cockpit deployment via SAPInst, enhanced Fiori App and integration capabilities, and an improved, more user-friendly cockpit experience.

Let's dive into these latest product features in detail, highlighting our latest pricing and charging capabilities as part of the SAP Billing and Revenue Innovation Management (BRIM) suite.

New metrics for monitoring business data growth

Managing business data growth is critical for ensuring optimal system performance. The latest enhancement in this release introduces proactive monitoring metrics to track key entities such as Subscriber Account Count, Contract Count, and Mapping Table Row Count. By continuously monitoring data growth, you can identify potential issues early, rather than reacting when performance problems have already occurred. This ensures better system stability and smooth operations, even as solutions evolve and new implementations drive data increases.

With this feature, customers can gain greater control and predictability over the system landscape. With the new standard view that shows the evolution of the growth in the row of the key metrics rows over the months helps detect anomalies before they impact performance, while historical data tracking enables more accurate forecasting and capacity planning. This not only helps prevent unexpected slowdowns but also improves operational efficiency, ensuring a seamless experience with an uninterrupted charging process.

Key Benefits:

• Track Growth of Business Data Objects – Gain real-time insights into expanding business data, helping identify trends and prevent performance bottlenecks.
• Improve User Assistance and Support – Enhance system monitoring, streamline troubleshooting, and provide proactive support to maintain high availability and reliability.

New Introscope metrics are now available for effective monitoring, allowing users to define thresholds and set alerts for these metrics. For more information about this new feature, refer to the Display Usage Metrics topic and details regarding Introscope on the SAP Help Portal.

Facilitation of the deployment of the Cockpit with an installer

With this release, the deployment of SAP CC Cockpit has been simplified by integrating it with SAPInst, aligning its installation process with the Core Server. This ensures a more structured and streamlined setup, reducing complexity and making it easier for businesses to adopt the Cockpit. With this improvement, the , ensuring a more cohesive deployment process within the SAP CC system.

By integrating Cockpit deployment into SAPInst, businesses can experience improved system stability and reduced support incidents related to manual deployment. This new method provides of deployment provides more standardized and efficient approach to installation and gain higher adoption of Cockpit. While the existing option of deploying on Apache Tomcat remains available. 

Feature enablement

• Simplify the deployment of the Cockpit: Easily install and update the Cockpit through SAPInst, reducing manual efforts.
• Minimizes errors and deployment issues and provides flexibility
• Reduce the number of support incidents linked to the deployment of the CC Cockpit

Learn more about this feature from our SAP help page for Installation and Maintenance Guide

Enhancement of the Display Contracts Fiori app to display allowances of a contract

With this release, the Display Contracts Fiori app in Cockpit has been further enhanced to provide a display of associated allowances assigned in a contract. This update enables users to quickly locate and review contract details, including associated contract and its activated allowances, ensuring greater transparency and accuracy in rating and billing processes. With this enhancement, billing specialists can efficiently verify provisioned provider contract data, along with key parameters and counters of the assigned allowances, thus improving overall operational efficiency.

Key Benefits:

• Enhanced Contract Visibility – Easily access and review allowances linked to a contract, ensuring transparency in charging.
• Improved Data Verification – view the activated allowance logic of an allowance including activation date/time & current value of counters.
• Increased Operational Efficiency – Enable billing specialists to quickly verify contract details, enhancing workflow efficiency and accuracy.

Learn more about this feature from SAP Help portal:     Cockpit Apps > Display Contracts

Other Enhancements 

In addition to the features mentioned above, SAP Convergent Charging 2023 FPS03 also introduces other enhancements:

• SAP Note for Minimum Hardware Requirements for an SAP Convergent Charging Development Environment

Our customer has requested an optimal hardware configuration for running a development environment. In response, we have released SAP Note 3568851, which outlines the essential hardware requirements for creating and testing pricing configurations.

By following these guidelines, customers can significantly reduce infrastructure costs by avoiding oversized hardware configurations. Adhering to these recommendations not only ensures optimal performance but also enhances overall operational efficiency. We strongly encourage our customers to implement these best practices for a cost-effective and high-performing development environment.

Find more details on the hardware configuration required, refer to the SAP Note: 3568851

• Support for additional pricing components in the Cockpit

The latest update introduces two powerful pricing components to enhance flexibility and precision in charge calculations. The "Number Matching" comparator (formerly Interval Switching) allows the pricing specialists to compare numeric properties against specific values or intervals, ensuring more granular control over pricing rules.

Additionally, the "Number Split-Based Addition" aggregator (formerly Numbers Splitter) enables more dynamic pricing in the pricing tree of the charges and in pricing functions.

     Benefits

• Enhance support for more complex pricing scenarios from the Cockpit

Find more details about this feature from the SAP Help portal:

• Comparators > Number Matching
• Aggregators > Number Split-Based Addition

• Renaming of nodes in pricing trees

To improve usability, we’ve introduced a Rename action in the Manage Rate Plans and Manage Pricing Functions apps. Available in both the toolbar and context menu, this feature allows users to rename pricing tree nodes for better business relevance or can even reset node name to the default name computed by the app. Additionally, tooltips now display component names for enhanced clarity. These improvements streamline pricing configuration, making it more intuitive and user-friendly.

Find more detail about this feature from SAP Help portal:

• Configuring the Pricing Tree of a Charge > Renaming a Node
• Configuring the Pricing Tree of a Pricing Function > Renaming a Node

• 3rd party updates

With this release, JCo has been upgraded to version 3.1, ensuring improved connectivity and performance. Additionally, we’ve introduced an optional check for JCo destination in SAPInst, enhancing installation flexibility.

More Information

SAP Convergent Charging 2023 FPS 03 has been released and is generally available to customers from Feb 2025 and is available on the SAP Software Download Center.

For more information on SAP Convergent Charging 2023 FPS 03, check out the following links:

• What’s New in 2023 FPS03
• Delivery and Information Note for SAP Convergent Charging 2023 FPS 3
• Product Page on SAP Help Portal   > Convergent Charging
• Questions and Answers for SAP Convergent Charging in SAP Community

In this blog post we introduce the split payment of VAT mechanism in Contract Accounting (FI-CA). The VAT split in this blog post means that during the payment run, the information of VAT amounts is split from the invoice amounts in the outgoing payment file. That is, there is only one payment, together with the VAT and invoice amount.

Note: If you want to split the VAT payment and the invoice payment and post VAT amount on a separate bank clearing account (In other words, there are two payments in total), you must set up the bank clearing account for posting area 1061. (Transaction: FQC0)

By applying the VAT split function, the VAT-relevant payment becomes more visible and enables the house banks to send this VAT amount directly to the tax authority. This feature improves the transparency and efficiency of processing payments.

Business Scenario

When you apply the VAT split feature, the VAT amount is listed separately in the payment file. When the house bank receives the payment file, it pays the VAT amount directly to the tax authority.

Processing outgoing with VAT split follows the standard payment processing as the picture above.

1. You first create and post contract accounting documents.
2. You execute payment runs. In this step the system carries out several actions, including selecting payment methods and bank details that you have defined in the customizing activity.
3. After the payment runs, a payment file is created. You can download the payment file as a .txt, or .xml file based on the payment format that you have assigned to payment methods for outgoing payments.
   The VAT split is carried out in this step when the payment file is generated. The VAT amount is listed separately. See the example and the line marked in yellow below.
   
   
4. You send the payment file to the payee’s house bank.
5. Payee’s house bank then sends the VAT amount directly to the tax authority. Later on, it sends you back a statement with the payment status.
6. Finally, you upload the received bank statement file.

Prerequisites

Before processing the payment with the VAT split feature, you must complete the configuration steps. In this blog post we introduce the configuration in SAP S/4HANA Cloud Private Edition and SAP S/4HANA Cloud Public Edition.

SAP S/4HANA Cloud Public Edition

The following two activities are standard steps for processing payments.

1. Define Payment Methods (ID: 101952): Define one or more country/region payment methods for outgoing payments.
2. Define Specifications for Paying Company Code (ID: 101251): Select company code used for automatic payment transactions and assign the payment methods.

To apply the VAT split for processing payments, you must complete the settings as follows. In the following print screen, we take Poland as an example.

1. Define Payment Methods for VAT Split in Contract Accounting (ID: 106940): Assign a payment method to the country/region key for VAT split.
   • Enter the country/region key and select Apply.
     
   • Select a payment method and save.
2. Business partner master data setting:
   
   • Search for the Maintain Business Partner app.
   • Enter the business partner.
   • In the Display in BP Role, select Contract Partner.
   • In the Country-Specific Data (FI-CA), enter a valid time for the VAT split and select 2-Split Enabled as the VAT Payment Type.

SAP S/4HANA Cloud Private Edition

The following two activities are standards steps for processing payments.

1. Define Payment Methods (Transaction: FQP1): Define one or more country/region payment methods for outgoing payments.
2. Define Specifications for Paying Company Code (Transaction: FQP4): Select company code used for automatic payment transactions and assign the payment methods.

To apply the VAT split for processing payments, you must complete the settings as follows. In the following print screen, we take Poland as an example.

1. Define Payment Methods for VAT Split in Contract Accounting: In the transaction SM30 enter the view FKKID_VATSP_PM_V to assign a payment method to the country/region key for VAT split.
2. Enable the VAT Split Option Screen (Transaction BUS6):
   • In the Screen sequences, select the entry BUP001.

   • In the Screen sequences – Screens, enter a screen code and an item number.
     Take Poland sample values as example. In the next setting, you enter events to this item number.

     Item	Screen
     9000005	MKKPL1

     
3. Enter Business Data Toolset Events (Transaction: BUS7)
   • Select for the events based on your business requirements.
   • In the Event -> Function Modules enter the item number and the function module.
     

   • You can refer to the table below to add the item into the events according to your business requirements.

     Event	Item	Function Module	Call	Application
     DCHCK	9000005	FKKPL_BUPA_VATSP_EVENT_DCHCK	X	MKK
     DLVE1	9000005	FKKPL_BUPA_VATSP_EVENT_DLVE1	X	MKK
     DSAVC	9000005	FKKPL_BUPA_VATSP_EVENT_DSAVC	X	MKK
     DSAVE	9000005	FKKPL_BUPA_VATSP_EVENT_DSAVE	X	MKK
     ISDAT	9000005	FKKPL_BUPA_VATSP_EVENT_ISDAT	X	MKK
     ISSTA	9000005	FKKPL_BUPA_VATSP_EVENT_ISSTA	X	MKK
     XCHNG	9000005	FKKPL_BUPA_VATSP_EVENT_XCHNG	X	MKK

      

4. Business partner master data setting (Transaction: BP)
   • Enter the business partner.
   • In the Display in BP Role, select Contract Partner.
   • In the Country-Specific Data (FI-CA), enter a valid time for the VAT split and select 2-Split Enabled as the VAT Payment Type.

SAP Notes

You can refer to the SAP Notes for VAT Splits for localization in Poland.

1. 2653460: VAT split payment format PL_ELIXIR-O and maintenance for MKK partner
2. 2664940: VAT split payment format PL_ELIXIR-O and maintenance for MKK partner, correction #1

Is this blog post useful to you? Leave your comments to let us know your thoughts!

Challenges with the Clearing of Incoming Payments

SAP Billing and Revenue Management (BRIM) is designed to efficiently handle high transactional volumes through process automation. While configuring business rules enables full automation in most areas, such as billing, invoicing, and collections, many companies still struggle with effective payment allocation. This challenge often arises when relying on arbitrary free text remittance information commonly used in bank transfer payments.

FI-CA Clearing Control is effective only to a certain extent and is highly depended on the discipline of customers in providing accurate remittance information. Although system allows for the configuration of complex and flexible allocation rules through standard configuration and custom code enhancements, predefined business rules cannot address scenarios where a  customer does not follow the prescribed remittance format (e.g. omitting an account number or invoice number) or provides incomplete payment details. As a result, such incoming payments end up in the clarification worklist.

Manual clarification is often time consuming , requiring significant effort, as unresolved clarification cases continue to accumulate. This leads to large amounts of cash being booked in suspense accounts for extended periods, negatively impacting key financial metrics such as available cash flow.

 SAP Cash Application

The AI capabilities embedded in the SAP Cash Application Add-on for Contract Accounting reduce the need for manual intervention and enable the assignment of incoming payments as quickly as possible. Running on the SAP Business Technology Platform, the SAP Cash Application leverages Machine Learning (ML) model to analyse data transferred from the S/4HANA system, identifying selection categories and selection values for FI-CA Clearing Control.

The ML model is trained before productive use, learning from historical clearing information. This learning process continues permanently in the production environment, automatically adapting to changing conditions to keep the model up to date. The key advantage of the ML model is its ability to automatically detect data patterns, while its dynamic learning process ensures long-term effectiveness without requiring additional maintenance effort.

 Key Configuration in Contract Accounting (FI-CA)

1. Activate Cash Application for the Company Code   

SPRO -> Organizational Units → Set Up Company Codes for Contract Accounts Receivable and Payable

1. Define Conditions for Using the ML Proposal Based on the Confidence Level Rating

SPRO -> Business Transactions → Payments → Processing Incoming and Outgoing Payments → Incoming Payment Clarification with Machine Learning → Make Settings for SAP Cash Application for Contract Accounting

The configuration determines how the clarification case will be processed in FI-CA based on the confidence rating returned to S/4HANA from the Cash Application. The configuration allows different follow-up processes to be set up:

• A clearing document will be generated for a matching proposal above the auto-clearing accuracy threshold.
• Matching proposals under the auto-clearing threshold are shown and displayed for validation.
• Proposals below the minimum threshold are skipped and not displayed at all.

In this instance (as per the configuration), the payment will be automatically cleared only if the confidence level is very high (greater than 95%). If the confidence level is between 80% and 95%, the system displays the proposal and requires manual post-processing. Below 80%, the system ignores the proposal completely.

Use Case – Payment Clarification with Cash Application

Let’s demonstrate the capabilities of Cash Application for Contract Accouting with a simple use case (note: the screenshots are taken from SAP S/4HANA Cloud Public Edition).

In this scenario, a payer has two ongoing service subscription contracts and is paying both invoices at once. The provided note to payee information is: “Payment for Feb 25 subscriptions West Corp” This presents the following challenges for payment allocation:

• No invoice reference number or account number is provided.
• The payer name (“West Corp”) may or may not match a Business Partner (BP) ID in the system.

Payment lots are created from the electronic bank statements, and the remittance information provided with the payment will be captured in the note to payee segment of the lot. However, the predefined interpretation rules and configured clearing rules will fail to translate the remittance information into selection categories and values, resulting in the creation of a clarification case.

In a system with the Cash Application Add-on activated, manual processing of clarification cases is blocked until the machine learning (ML) analysis is complete. The system will raise an error message if the user attempts to process the clarification case before the data are sent for analysis.

Next, the clarification case is sent to Cash Application for analysis. This is done through job scheduling using the job template “FI-CA: Transfer Clarification Cases”. In a productive environment, this job should be scheduled immediately after the creation and posting of payment lots to FI-CA.

The ML model applies the logic to find a suitable matching proposal, which is then returned to the S/4HANA system. This process is also done through job scheduling, using the job template “FI-CA: Process Returned and Reversed Clarification Cases”.

The ML model provides matching criteria with a confidence level for each clarification case. Proposals with a confidence level meeting the minimum auto-clearing threshold will trigger the posting of FI-CA document.

Availability

As of now, the Add-On is available for SAP S/4HANA BRIM, SAP S/4HANA Cloud Public Edition for Contract Accounting, and other industry-specific FI-CA variants, including PSCD for Public Services, FS-CD for Insurance Companies, and IS-U for the Utilities sector.

 Further SAP Help references

Cash Application integration for Contract Accounting for Cloud

SAP Cash Application for Contract Accounting: Product information

Hi there!  

We are back again for another What’s New for SAP Profitability and Performance Management Cloud Standard Model (SAP PaPM Cloud SM). This month’s What’s New will focus on the enhancements in the Environment screen and the consolidation of Show and Analyze Screen.  

In case you missed it, you can always catch up on the latest developments and releases about SAP PaPM Cloud SM following the relevant tag: PaPMCloudWhatsNew 

Let’s start! 

Environments Screen Enhancements 

SAP PaPM Cloud Standard Model has enhanced the Environments screen by replacing inline editing and drag-and-drop interactions with modal dialogs. This update streamlines actions like adding, editing, moving, and deleting environments, providing a more consistent and user-friendly experience. Additionally, automatic saving eliminates the need for manual save, undo, and redo actions. 

More details about the Environments screen enhancements can be found in the SAP PaPM Cloud blog post: SAP PaPM Cloud SM: Enhancements on the Environments Screen or visit our Application Help portal Environments screen. 

Consolidation of Show and Analyze Screen 

Two of the most frequently used screens in SAP PAPM Cloud Standard Model application, Show and Analyze screens, have been consolidated into one unique screen. Displaying and maintaining data in tabular view in Show screen and manipulating data in aggregated view in Analyze screen is now merged into single Data maintenance screen.  
For your reference, please visit Show screen and Analyze data sections in the Application Help portal. 

Access to the Consolidated Show & Analyze Screen 

Previously, authorized users could access and maintain data in the Show and Analyze screens through two different buttons.

With the new implementation, Show and Analyze screens are merged into one screen, which can be accessed via the Manage Data button.  

Upon accessing the Show screen of any function, the URL part isPivotModeOn states if the pivoted mode is enabled. In case authorized users wish to view and maintain data in tabular view they can keep the Pivot toggle disabled.

Once users wish to change the data representation from tabular to aggregated view, they can enable the Pivot toggle. 

Layouts for different pivot modes are separated, which means that the user can save different set of layouts for two different pivot modes: enabled and disabled.  

In case user makes any changes in the Show screen with disabled pivot mode , an asterisk indicator (*) will show up besides the current layout. Upon trying to enable the Pivot toggle, the user will get a warning message that unsaved changes for current mode will be discarded in case user chooses to leave the view. 

The same behavior will be applicable if the user tries to disable the Pivot toggle while they are in pivot mode with unsaved layout changes. 

That’s it for now! 
Stay tuned for more enhancements and exciting release in the next months’ What’s New. 
Until next time and see you next month! 

This blog provides an overview of select enhancements in SAP Risk and Assurance Management from Q4 2024 to Q1 2025. 

Including: 

• New risk analysis methods
• Integration with SAP Signavio for Controls and Risks version 2.0
• Automatic Issue Owner Determination, Notification, and Assignment
• GRC Data Consolidation Service

Before we dive into one details of SAP CPQ 2502 release I wanted to remind you that registration for CWG Spring 2025 Conference in Milwaukee, Wisconsin, United States is open and that you can benefit from early bird registration in next two weeks!SAP CPQ 2502 brings:

• New REST API for Managing Products
• Editability of Cost in Quote 2.0 
• VCPS Integration Improvements 
• Business Partner Standard Fields UX improvements
• Quote Custom Sections
• Alternative & Variant Item Types
• Multilevel Products Change Processes (BRIM)
• Add SubItem Improvement 
• Quote Fields and Calculations Page

...and much more! So let's dig in!

New REST API for Managing Products 

Starting 2502 CPQ admins can synchronize products using the new REST API with improved performance and a new bulk endpoint. The ProductIntegration REST API supports all that was supported in previous SOAP versions and much more. 
 
Check out swagger for this API. Documentation is published in help as well. 
 

Editability of Cost in Quote 2.0 

We recognize how critical it is for our customers to manage standard cost values dynamically. With this release, the cost column in Quote 2.0 can now be scripted, unlocking new opportunities for advanced integration scenarios. 

VCPS Integration Improvements 

Backend characteristics that have dynamic domain are now represented in CPQ I na more intuitive way as their original data type persisted.  
 
Knowledge base synchronization process is enchased to allow deleting obsolete KB data and corresponding product and product versions in CPQ.  
 

Business Partner Standard Fields UX improvements 

While it was possible to define editability and visibility for business partner custom fields all standard fields were both visible and editable. Business partners area covered with responsive templates recently, but still overall idea is to move towards configurations rather than customizations. 
 
Under Setup ->   Business Partners -> Business Partner Fields, CPQ admins now can: 

• Define which fields are visible for different user types and/or permission groups 

• Define which fields are editable for different user types and/or permission groups 

Read more on this in help page for Business Partners. 
  

Quote Custom Sections 

Admins can now create sections on Quote tabs in Quote 2.0 to logically group custom fields and quote tables based on business needs. Rather than customizing templates CPQ admin can leverage out of the box capability to configure sections in quote, decide on which tab to show that section and assign quote custom fields and quote tables to them. 
 
Just navigate to Setup   Quotes  Fields, Calculations, Layout   Custom Sections and select Add New option to get to this page: 
 

 
At any point in time content of the section can be reordered using drag and drop. 

 
What is still not possible is to move standard fields to custom sections and vice versa but if this is something you would appreciate, please do not hesitate to let us know in the comments.  
 
More details can be found in this help page, 
 

Alternative & Variant Item Types 

In Quote 2.0 since a while have base and optional item types but to ease migration of existing Quote 1.0 customers where we also had additional item types in this release, we are bringing to the new quoting engine: 

• Alternative Item type 

• Variant Item type 

Item types can be set on root items and are properly handled not to contribute to quote totals. Read here how to enable new item types in SAP CPQ. 

Multilevel Products Change Processes (BRIM) 

Customers selling multilevel solutions using SAP CPQ and SAP Billing and Revenue Innovation Management. 
 
Supported scenarios: 

Add SubItem Improvement 

The Add SubItem action allows users to include sub-items under a parent product within the quote. This feature is useful when managing complex configurations or bundles that require hierarchical structures. 

Check out detailed documentation how to enable this awesome functionality. 

Quote Fields and Calculations Page 

Management of quote item custom fields is now moved to Quote 2.0 specific section in setup “Fields, Calculation, Layout”  

 
In case you observed that implementing some feature is missing please share your request with us using SAP Customer Influence portal

New Release

PUBLIC

February 2025

We’re thrilled to announce that from February 26th 2025, the Subscription Order Management 2023 FPS03 release is now generally available for our customers. The latest release introduces a suite of user-friendly features, enriched mass run enhancements, and advanced integration capabilities that are designed to significantly elevate your user experience and optimize system performance.

Let's dive into the latest product features, which include an enhanced integration with SAP Global Trade Services (GTS) that now extends to subscription contracts, repricing capabilities during mass changes, and the ability to reactivate cancelled subscription contracts. Additionally, we have enhanced our APIs to handle adhoc and periodic billing schedules, enhanced mass runs so that you can now provide customized attributes and define up to five technical resources at an order-level while creating a large number of subscription orders along with numerous other functional enhancements. Let’s delve deeper into these features in detail.

GTS Integration with Subscription Contracts

In today’s interconnected global economy, adhering to international trade regulations is not only a legal requirement but also a crucial factor in maintaining your company’s global reputation and avoiding costly fines. When your business works with long term subscription contracts that span multiple countries, business partners, and products, compliance with trade regulations can become a complex and resource-intensive process. With this release, we have now extended our integration with SAP Global Trade Services (SAP GTS) to include GTS checks and processes on subscription contracts to enhance a powerful solution to streamline trade compliance.

With this integration, SAP GTS ensures that your business is compliant with international trade regulations by conducting a series of checks, like the Embargo Check, Sanctioned Party List Screening, and Product License (Legal Control) Check on subscription contracts. Your compliance manager will be able to manage the blocked contracts and take the necessary steps directly in the GTS system. This enhancement will enable you to manage the complexity of compliance checks for existing contracts and change orders, allowed change processes on blocked contracts, and many other critical business processes as part of the standard offering.

Figure 1: GTS Block During Contract Creation

Some of the critical business benefits of the Subscription Order Management integration with SAP GTS are as follows:

• Prevent subscription activities with embargoed countries
• Check legal control for relevant change processes on blocked subscription contracts
• Resolve legal control issues with blocked subscription contracts
• Compliance with trade regulations throughout the contract lifecycle
• Screen business partner addresses against denied party lists

For more information about this new feature, refer to GTS Integration with Subscription Contracts topic on the SAP Help Portal.

For more information about the overall integration between Subscription Order Management and SAP GTS, you can check What’s New in Subscription Order Management 2023 FPS02.

Mass Changes of Subscriptions – Reprice

Let’s consider a scenario where 100 subscription contracts have been made for product A. At the time of contract creation, the product price for $10. However, the product price has increased and is now $12. Changing the price for each of the active subscription contracts is a monumental task and that’s where Subscription Order Management steps in to facilitate your task by providing the Update Price change process. You use this change process while creating a mass processing run on the Mass Change of Subscriptions or Manage Mass Processing of Subscriptions Fiori apps.

Figure 2: Update Price in a Mass Processing

Additionally, with this release, Subscription Order Management also delivers the Price Relevant Change flag for the Change Price change process which enables you to set a manual price on multiple subscription contracts while creating a mass processing run.

Figure 3: Change Manual Price in a Mass Processing

Some of the critical business benefits of this feature are as follows:

• Automate the re-pricing process for multiple subscription contracts, eliminating the need for manual updates and significantly reducing operational overhead.
• Enables scalability and enhanced capability in mass processing through the Mass Changes of Subscriptions and Manage Mass Processing of Subscriptions Fiori apps to update across hundreds of active customer contracts
• Ensures all subscription contracts are updated in accordance with new pricing policies and ensure transparency
• Enables rapid implementation of new pricing structures

For more information about this new feature, refer to Manage Mass Processing of Subscriptions, App Details: Manage Mass Processing of Subscriptions, and Update Price on the SAP Help Portal.

Reactivate Cancelled Subscription Contracts

Have you ever cancelled a subscription by accident or cancelled a subscription, simply changed your mind, and wanted to continue using the subscription? With this release, you can now reactivate a cancelled subscription contract as long as you are within the contract grace period.

Figure 4: Reactivate change process on a cancelled subscription contract

Some of the critical business benefits of this feature are as follows:

• The reactivation feature enhances flexibility and customer experience by allowing contract data retrieval, unlike before, when cancellation meant permanent data loss​
• A new change process ‘Reactivate’ is now available for execution during grace period​
• Reduces churn by allowing customers to reverse accidental cancellations or reconsider their decision
• Recovers lost revenue from customers who reactivate their subscriptions

For more information about this new feature, refer to Reactivate on the SAP Help Portal.

Enhanced Mass Run Capabilities for Creating Subscription Orders

With Subscription Order Management you are already able to create multiple, similar subscription orders with ease and efficiency. With this release, you can now customize each line item (subscription order) when using a mass run to create multiple subscription orders so that, in addition to inheriting attributes from the header, each order also has specific order-level attributes. This means that while you create the mass processing, you can customize an individual start date for each order and provide up to five technical resources at an individual order level. If you are creating subscription orders from a specific master agreement, you can also maintain individual master agreement IDs at individual order level.

Specific attributes maintained at individual order level

Figure 5: Specific attributes maintained at individual order level

For more information about this new feature, refer to Mass Creation of Subscription Orders and Mass Creation of Subscription Orders with Master Agreement on the SAP Help Portal.

Adding Subitems in a Change Order from a Master Agreement

Let’s look at a scenario where you work in an organization that has an agreement with a service provider that provides a subscription to an operating system on purchase of a new laptop. Since there are a large number of licensed users, there is a special agreement between your organization and the service provider where purchasing the subscription to the operating system further provides the option to choose two other software products, one being an AI assistant and the other a suite of tools for standard business operations. At the time of buying the subscription, you choose only the suite of standard business tools for your new laptop. However, 6 months later, you decide to also add the AI assistant to your subscription.

This is where Subscription Order Management steps in with the feature that enables you to add subitems from a master agreement in a change order. When you use the Add Subitem button in the change order, you are provided with a list of only those subitems that are available in the associated master agreement. Furthermore, you can also remove any of the copied subitems from the call-off document as long as they are optional in the product bundle or have been added manually in the master agreement. 

Figure 6: Adding and deleting subitems from a master agreement

Some of the critical business benefits of this feature are as follows:

• Allow customers to add new subitems from the pre-negotiated list of products in the master agreement
• Enable smooth upselling and cross-selling by allowing customers to add pre-negotiated subitems from the master agreement at any time

For more information about this new feature, refer to Creating Call-Offs with Reference to Master Agreements on the SAP Help Portal.

Billing Schedules via API

With Subscription Order Management you are already able to create and update subscription orders and solution quotations with either an adhoc or periodic billing schedule from the UI. With this release, this functionality has been enabled for the Subscription Order (Version 0002) and Solution Quotation (A2X) OData APIs.

With the Subscription Order (Version 0002) OData API, you can create and update subscription orders with periodic billing schedule lines, and you can create, update, and delete subscription orders with adhoc billing schedule lines.

With the Solution Quotation (A2X) OData API, you can create and update solution quotations with adhoc or periodic billing schedule lines.

Some of the critical business benefits of this feature are as follows:

• Provides flexibility for customers, making it financially easier to adopt​ the feature
• Enhance the user experience​
• Increasing customer acquisition and satisfaction​
• Provide transparency to the involved stakeholders
• Reduce back-office operations with standard functionality

For more information about this new feature, refer to Subscription Order (Version 0002) and Solution Quotation (A2X)  on the SAP Help Portal.

Other Enhancements

In addition to the features mentioned above, Subscription Order Management 2023 FPS03 also introduces the following enhancements:

RAR Integration Based on CI Billing Plan – Transaction Price and Standalone Selling Price

With this release, you can now do the following:

• Calculate the transaction price based on the RAR transfer record using the Set RAR Transfer Record for Provider Contract Item Based on CI Billing Plan flag.
• Calculate the standalone selling price based on the CI billing plan item using the Create CI Billing Plan Item for Standalone Selling Price flag.

Long texts in Subscription Order and Master Agreement OData APIs

W ith Subscription Order Management, you can maintain long texts at a header and item level on the UI. With this release, you can now maintain the long texts at a header and item level using the Subscription Order (Version 0002) and Master Agreement OData APIs.

Additional BRFplus Functions for Mapping SAP Convergent Charging Parameters

The SAP app Manage Subscription Product-Specific Data uses BRFplus functions in the cross-catalog mapping version to map item-specific data to SAP Convergent Charging charge plans. Additional BRFplus functions have now been added to the standard delivery for mapping CC numeric parameters, CC string parameters, and mapping to technical resources.

Failover mechanism for Web Service Calls from SAP Convergent Charging

With this release, you can now maintain multiple logical ports for the same SAP Convergent Charging web service. This ensures that if one port fails, an alternate port is available for use.

More Information

Subscription Order Management 2023 FPS03 has been released to customers on February 26th 2025. For more information about Subscription Order Management 2023 FPS03, check out the following links:

• What's New in SAP S/4HANA and SAP S/4HANA Cloud Private Edition 2023 FPS03 (Go to Finance > Billing and Revenue Innovation Management > Subscription Order Management)

• Product Page on SAP Help Portal
• Questions and Answers for Subscription Order Management in SAP Community

Hello SAP Community members! 

I’m excited to share the improvements made to the Environment Screen in SAP Profitability and Performance Management Cloud Standard Model (SAP PaPM Cloud SM). In this blog we will explore the new design, which makes working with Environments easier and more intuitive. Actions like adding, editing, moving, and deleting are now clearer, with a structured and consistent flow. There’s no need to worry about accidental deletions or remembering to save—every change is confirmed and applied instantly. The interface is cleaner, and the process feels smoother, allowing users to focus on their work without unnecessary steps. With these improvements, managing Environments is now simpler, faster, and more reliable.

Adding, Copying, and Editing in Environments Screen

Before: 

Previously, adding, copying, or editing nodes and environments was done directly within the table through inline editing. Selecting “Add Node” or “Add Environment” activated an editable row where users could input the ID, version, and description. Copying through “Environment From” pre-filled these fields with data from the selected environment, allowing further change. Editing was accessed via a pencil icon on the right side of the row, enabling users to update only the description while the ID and version remained locked. 

After: 

In the new implementation, actions such as adding, copying, and editing nodes and environments are now performed through pop-up dialogs instead of inline editing. Each dialog is labeled according to the selected action.  

Choosing “Add Node” or “Add Environment” opens a dialog where users can enter the ID, version, and description.  

Editing is now initiated from the header section, and the pop-up allows changes to the description while ID and version remain greyed out. 

Copying via “Environment From” opens a similar pop-up with pre-filled data for editing. 

Moving of Nodes and Environments

Before: 

Users can select the node or environment they wish to move, drag it, and drop it onto the available node on the screen. For instance, as illustrated in the image below, they can move the environment to one of two nodes in the same folder or to the parent node of its current location. To move it to a different node, they must first drag and drop it to a node that allows further movement to a child Node. For example, they can place it in the main folder and then continue the drag-and-drop process to reach the intended node. This method can be labor-intensive due to the manual selection of the target folder without a clear hierarchy, which may take some time.  

When the user moves to the target node, they must save the change by clicking the “Save” icon. If they make a mistake, they have “Undo” and “Redo” buttons to correct it.   

After: 

In the updated Environment Screen, once users select their desired node or environment for moving, they need to click the “Move” option in the header. This action triggers a pop-up window, allowing the user to choose their preferred node either from the dropdown menu or from the node picker.  

The default value is set to Main (Root Node). Display between the main target field and the Node Picker hierarchy is synchronized. This feature is handy for users who don’t remember the exact name of the target node but know its parent. Choosing the parent node from the dropdown will highlight it in the node picker. After that, the user can select the child node where they want to move the selected node or environment.  

After clicking the “Move” button, the node or environment will be moved to the target node, which will be opened on the Environment Screen. This action will be saved automatically.  

Deleting of Nodes and Environments

Before: 

To delete a chosen node or environment, users should click the “Delete” button located in the header. This action will instantly remove the node or environment from the user interface, but users can undo or redo the change if they wish to revert it. Finally, they must click the “Save” button to confirm their changes. After saving, the undo and redo options will no longer be available.

After: 

In the new implementation, after selecting the node or environment they want to remove, users need to click on the “Delete” button in the header. However, this time, the node or environment will not be deleted immediately. Instead, a confirmation pop-up window will appear that shows how many nodes or environments will be deleted, and users need to confirm that they really want to delete them.  

After confirmation, users will receive an information blue message toast indicating that the process has started in the backend. Then, after it’s done, they will receive a successful green message toast. These messages provide clear feedback on the process and improve user experience. 

Conclusion 

The enhancement of the Environment Screen has made it more intuitive, efficient, and consistent. By replacing inline editing and drag-and-drop with pop-up dialogs, users now have a clearer workflow that aligns with other parts of the system. 

Key changes include: 

• Automatic saving, eliminating the need for Save, Undo, and Redo buttons 

• Edit and Move actions relocated to the header for better accessibility 

• Deletion confirmation dialogs, preventing unintended data loss 

• A move option with node picker, replacing manual drag-and-drop for environment movement 

These updates reduce complexity, minimize errors, and improve navigation, making interactions more intuitive and ensuring a more efficient workflow for users.  

I hope you find these updates helpful! If you have any questions or comments, feel free to post them in the comment section.

Stay tuned for the latest updates and insights on the next one. Thank you!