SAP Community - SAP S/4HANA Public Cloud

Regression testing recommendations for SAP Screen Personas flavors in SAP S/4HANA

2025-05-12T18:50:42.282000+02:00

I recently received an email from a colleague on behalf of a customer they are helping in an SAP S/4HANA Cloud migration project.

How much regression testing do you recommend to customers, both in the case of an SAP S/4HANA upgrade and the implementation of service packs for SAP Screen Personas? Since SAP S/4HANA Cloud Public Edition is frequently upgraded, do customers regularly conduct regression testing for all of the adapted screens?

In this post, I’ll discuss our recommendations for regression testing of SAP Screen Personas flavors in the context of SAP S/4HANA upgrades.

TLDR; Test everything before going live with any changes. Leave enough time to do this.

Regression testing ensures that software works after upgrades

According to GitHub, “Regression testing is a process that ensures that software still performs as expected, even after a change.” In the context of the question above, the changes we are talking about include upgrades to SAP S/4HANA or new SAP Screen Personas service packs. Both represent changes to the IT environment.

When I worked on IT infrastructure management tools in a previous company, the first question we asked customers when they reported that something was broken was “what did you change?” Most problems we encountered were self-inflicted, the result of changes to something in their production environment. The key to catching these issues before they cause an impact on the business is thorough testing of any changes to software, hardware, configurations, or anything.

We recommend regression testing on SAP Screen Personas flavors

If you are performing any upgrade to your business-critical ERP system, we recommend regression testing for *everything* that changes. Ideally, your development or quality assurance (QA) system mirrors your production system, so you can perform the update on your dev system, test that everything works, then implement the same upgrade on your QA and production systems. By verifying that all the individual systems work in a low-risk setting (dev and QA), you will avoid any surprises in the production system.

Regression testing takes time. Do not wait until the last minute. You want to make sure you have enough time before you go live to fix any issues that you find.

Playwright is a common tool for testing web apps, including SAP Screen Personas. You can run a series of tests to ensure that what worked before also works after your upgrade. One key to success here is maintaining the tests that you create. Testing can be manual and/or automated.

SAP S/4HANA Cloud upgrades don’t break SAP Screen Personas flavors

For SAP S/4HANA Cloud Public Edition, we make upgrades approximately every six months (2408, 2502, 2508, etc.). Generally, this does not cause any problems for SAP Screen Personas flavors. The exception would be if a control ID in the transaction changed and a script or other change in the system pointed to that now obsolete object. This is not common.

In SAP S/4HANA Cloud Private Edition, we release feature packs (FPS0, FPS1, etc.) approximately every six months. Customers can consume them at their own pace, allowing them time to test any parts that have changed since their last update. In this case too, we do not expect any issues with SAP Screen Personas flavors. The only time something would break in a flavor is if a control ID in the transaction changed and a script or other change in the flavor pointed to that now obsolete object. Here too, this is not common.

We engineer SAP Screen Personas upgrades to be non-disruptive

For SAP S/4HANA Cloud Public Edition, the SAP Screen Personas functionality is built in as Adapt UI for Classic Apps. You access it through the same user menu as Adapt UI (for SAP Fiori apps built with SAPUI5). Since the user does not need to update anything on their own, we test the Adapt UI capabilities before we include them in the larger ERP upgrade. We are part of the “release train” for all the semi-annual releases.

Since we don’t know how you have built your flavors, we strongly recommend that you test your SAP Screen Personas flavors to ensure that everything works with each system upgrade. There are no SAP Screen Personas service packs with SAP S/4HANA Cloud Public Edition. Any new functionality simply appears in your system. This is the beauty of the cloud.

I cannot remember a time when we introduced new functionality that broke any flavors that customers built. There have been many occasions where we introduced easier ways to do things (adaptive flavors, viewports, scripting). In some cases, this might warrant rebuilding flavors to improve performance or streamline your maintenance. Of course, if you choose to keep things as they are, they will still work.

For SAP S/4HANA Cloud Private Edition, we release SAP Screen Personas service packs around once per year. You can choose to install them or not. In our release announcement and documentation, we clearly explain what’s new and why it matters to you. If you choose to install the latest SAP Screen Personas service pack, we encourage you to perform regression testing on the flavors that you use in production.

Our own service pack upgrades typically do not cause any problems for SAP Screen Personas flavors. We aim not to introduce changes into the product that break existing functionality. It is possible that you might have implemented something in a script or applet that uses an older version of SAPUI5 that we moved up to the current version. It would be very rare that this would disrupt your script, as the SAPUI5 team takes extreme care not to deprecate functionality.

We usually release new SAP Screen Personas innovations every year

If you want to plan your upgrades and testing cycles, here is a graphic that shows our release schedule and support commitment for SAP Screen Personas.

Moving flavors from SAP S/4HANA Cloud Private Edition to SAP S/4HANA Cloud Public Edition is possible

As many customers are moving forward on their RISE with SAP journeys, we are starting to hear questions about migrating flavors from an SAP S/4HANA Cloud Private Edition environment to SAP S/4HANA Cloud Public Edition. For some organizations, their ultimate goal is to run everything on public cloud; private cloud is a temporary transition.

There is no direct path to transport flavors from a private cloud system to a public cloud system. This is obvious, since they are completely disconnected environments. It is possible to use the export – import flavor capability to move your flavors to SAP S/4HANA Cloud Public Edition, then adjust them if necessary.

Some features in private cloud, such as theming, RFC support, or Slipstream Engine-specific functionality, are not supported in public cloud, so please plan accordingly.

If you are moving your flavors from SAP S/4HANA Cloud Private Edition to SAP S/4HANA Cloud Public Edition, there are likely many other IT changes that are happening at the same time. We recommend you take this opportunity to review your flavors, update the documentation so any new team members can maintain them, and only move those that are actively used.

Subcontracting with ATP check for MRP Area requirement

2025-05-13T07:53:13.882000+02:00

This document records the steps for configuration set up, master data change and end-to-end business process.

It covers five topics.

Purpose
Configuration Change
Preliminary steps.
Master data and organization data
Detail process steps

1: Purpose

When creating outbound deliveries to subcontractors based on reservation, availability check is performed.

A subcontract purchase order is manually created by a requestor. Then a subcontract reservation can be generated via the Material Requirements Planning (MRP) process. The outbound delivery is created based on the reservation with ATP check, and the goods are picked and shipped to the subcontractor. With the supply of the finished material, the goods receipt is created. The consumption of the sent components is recorded upon the receipt of the value-added finished material. Subsequently, the invoicing process is triggered.

2: Configuration Change

To allow ATP check during creating outbound delivery for item category LBR, we need to complete configuration set up in the backend S/4HANA Cloud system.

The configuration change includes the following 4 parts.

Define Requirement Class SC1
Define Requirement type SC1
Assign Schedule Line Categories
Determine Requirement Type by Item Category and MRP Type

2.1 Define Requirement Class SC1

Transaction Code: S_ALR_87006831

Choose New Entries to create a new requirement class and enter following values, choose Save.

2.2 Define Requirement type SC1

Transaction Code: S_ALR_87006834

Choose New Entries to create a new requirement type and enter following values, choose Save.

2.3 Assign Schedule Line Categories

Transaction Code: S_ALR_87007127

Choose New Entries, add the data like below, choose Save.

2.4 Determine Requirement Type by Item Category and MRP Type

Transaction Code: S_ALR_87006836

Assign SC1 to LBR like below, choose Save.

3: Preliminary Steps

This section summarizes the preliminary steps for conducting the process in terms of systems.

The preliminary steps include the following 3 parts.

Define MRP Areas for Subcontractors
Assign MRP Area to Components
Assign Shipping Point
Define Item Category Determination in Deliveries

Roles

Name (Role Template)	ID (Role Template)	Name (Launchpad Space)	ID (Launchpad Space)	Log On
Configuration Expert - Business Process Configuration	SAP_BR_BPC_EXPERT	Business Process Configuration	Configuration Expert - Business Process Configuration
Master Data Specialist - Product Data	SAP_BR_PRODMASTER_SPECIALIST	Product Master Specialist	Master Data Specialist - Product Data
Master Data Specialist - Business Partner Data	SAP_BR_BUPA_MASTER_SPECIALIST	Master Data - Business Partners / Business Partner Governance / Business Partner Governance	SAP_BR_BUPA_MASTER_SPECIALIST / SAP_CA_SPT_MDG_BP_GOV_PC /

3.1 Define MRP Areas for Subcontractors

SAP Central Business Configuration:

Test Step #	Test Step Name	Instruction	Expected Result
1	Log On	Log on to the project experience in SAP Central Business Configuration.	The SAP Fiori Launchpad is displayed.
2	Access App	Go to the Business Processes Configuration app. To locate the activity in the tree view, search for the following activity: 103069 (Define MRP Areas for Subcontractors). Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.	The Define MRP Areas for Subcontractors: Change: Details screen is displayed.
4	Add MRP Area	On the Define MRP Areas for Subcontractors: Change: Details screen, click the New Entries and make the following entries: MRP Area: for example, 1010SUB057 MRP Area Type: 3 Supplier Plant: 1010	Add the MRP Area 1010SUB057.
5	Save your data	Choose Save.
6	Add Subcontractor	Choose Subcontractor (one entry per MRP area), choose New Entries and mke the following entries: Subcontr: for example, 10300007 Choose Save.	Subcontractor for MRP Area is saved.

3.2 Assign MRP area to components

Test Step #	Test Step Name	Instruction	Expected Result
1.	Log onto SAP Fiori Launchpad	Log on to the SAP Fiori launchpad as a Master Data Specialist - Product Data.
2.	Access the App	Open Change Material.	The Change Material (Initial Screen) screen displays.
3	Enter Material Basic Data	On the Change Material (Initial Screen) make the follow entries: Material: RM13 Material Type: Raw materials Select View(s) dialog box displays. Select the following entries and choose Continue (Enter): Sales: Sales Org.Data 1 Sales: Sales Org.Data 2 Sales: General/Plant Data Purchasing MRP 1 MRP 2 MRP 3 MRP 4 General Plant Data / Storage 1 General Plant Data / Storage 2 Accounting 1 Accounting 2 Maintain following data and choose Continue: In the Organizational levels subarea: Plant: for example, 1010 Storage location: for example, 101C Change Material screen displays. Make the following data or actions and choose Save. Sales: Sales Org. 1 tab Delivering Plant: for example, 1010 Sales: Sales Org. 2 tab All fields unchanged Sales: General/Plant tab LoadingGrp: for example, 0001 Purchasing tab All fields unchanged MRP 1 tab Choose MRP Areas under section MRP Areas, choose Insert Row, make the follow entries, MRP Area: for example, 1010SUB057 Double clicks this entry, In MRP 1 tab, MRP Type: PD MRP Controller: 002 Lot Sizing Procedure: X In MRP 2 tab, Special Procurement: 45 Choose Adopt. MRP 2 tab All fields unchanged MRP 3 tab All fields unchanged MRP 4 tab All fields unchanged Plant data / Stor. 1 tab All fields unchanged Plant data / Stor. 2 tab All fields unchanged Accounting 1 tab : Standard Price: Change if needed Per Unit Price: Change if needed Accounting 2 tab: All fields unchanged Note Add MRP Area 1010SUB057 to material RM14 by following above steps.

3.3 Assign Shipping Point

To create the outbound delivery successfully, make sure the relevant shipping point is assigned.

SAP Central Business Configuration:

Test Step #	Test Step Name	Instruction	Expected Result
1	Log On	Log on to the project experience in SAP Central Business Configuration.	The SAP Fiori Launchpad is displayed.
2	Access App	Go to the Business Processes Configuration app. To locate the activity in the tree view, search for the following activity: 102126 (Assign Shipping Points). Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.	The Assign Shipping Points: Change screen is displayed.
4	Add Shipping Points	On the Assign Shipping Points: Change screen, make sure the following entry is there, otherwise add a new entry via choose New Entries: Shipping Condition: for example, 01 Loading Group: for example, 0001 Plant: 1010 Proposed Shipping Point: 1010 Choose Save.	The shipping point is there.

3.4 Define Item Category Determination in Deliveries

To create the outbound delivery successfully, make sure item category determination in deliveries is defined.

SAP Central Business Configuration:

Test Step #	Test Step Name	Instruction	Expected Result
1	Log On	Log on to the project experience in SAP Central Business Configuration.	The SAP Fiori Launchpad is displayed.
2	Access App	Go to the Business Processes Configuration app. To locate the activity in the tree view, search for the following activity: 105417 (Define Item Category Determination in Deliveries). Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.	The Assign Shipping Points: Change screen is displayed.
4	Add Shipping Points	On the Assign Shipping Points: Change screen, make sure the following entry is there, otherwise add a new entry via choose New Entries: DlvT: LB ItCG: NORM Uage: LRES Default item Catg.: LBR Choose Save.	The shipping point is there.

3: Organizational Data, Supplier Data and Master Data

The organizational structure and master data of your company have been created in your system during implementation. The organizational structure reflects the structure of your company. The master data represents materials, customers, and suppliers, for example, depending on the operational focus of your company.

Use your own master data or the following sample data to go through the test procedure:

Organization Data:

Country	Purchase Org.	Plant	Company Code
DE (Germany)	1010	1010 (DE)	1010

Supplier Data:

Country	Supplier		Supplier Name	Purchase Org.	Company Code
DE (Germany)	10300007		Inland-Lohnbearbeiter A, DE	1010 (DE)	1010

Customer Data:

Country	Customer		Customer Name	Sales Org.	Company Code
DE (Germany)	10100007		Inland-Lohnbearbeiter A , DE	1010 (DE)	1010

Material Master Data:

Material	Plant	Storage Location	Comment
SG23	1010	101B
RM13	1010	101C
RM14	1010	101C

4: Procedure Steps

Process Overview Table

Process Step	Business Role	Transaction/App	Expected Results
Create Purchase Order	Purchaser	Create Purchase Order (ME21N)	The Create Purchase Order screen is displayed.
Run MRP at MRP Area level	Production Planner	Monitor Material Coverage - Net and Individual Segments (F2101A)	The Monitor Material Coverage - Net and Individual Segments screen is displayed.
Create Delivery	Inventory Manager	Subcontracting Cockpit(F2948)	The Subcontracting Cockpit screen is displayed.
Pick and Post Goods Issue	Shipping Specialist	Change Outbound Delivery (VL02N)	The Change Outbound Delivery screen is displayed.
Post Goods Receipt	Warehouse Clerk	Post Goods Receipt for Purchasing Document (F0843)	The Post Goods Receipt for Purchasing Document screen is displayed.
Create Supplier Invoice	Accounts Payable Accountant	Create Supplier Invoice (F0859)	The Create Supplier Invoices screen is displayed.

4.1 Create Purchase Order

Procedure

Test Step #	Test Step Name	Instruction	Expected Result
1	Log On	Log on to the SAP Fiori Launchpad as a Purchaser.
2	Access the App	Open Manage Purchase Orders (F0842A).	The Create Purchase Order screen is displayed with a list of existing Purchasing Document Items.
3	Start Purchase Order creation	Without making any selection, choose Create.	The Purchase Order Screen is shown.
4	Create Purchase Order data	Enter the following data and choose Enter: Supplier :10300007 Purchasing Org: 1010 Purchasing Group: 001 Company Code: 1010 Currency: EUR In the Items section, choose Create: Item Category: Subcontracting Material (Original): SG23 Quantity: x PC Net. Price: x EUR Plant: 1010 Storage Location: 101B Choose Details on the right of your item and go to Purchase Order Item screen. Choose Apply.
5	Save Purchase Order	Choose Save and when the purchase order number is displayed, write it down for further use.	A Purchase Order is created.

4.2 Material Requirements Planning at MRP Area Level

Purpose

The aim of material requirements planning is to tailor available capacities and receipts on time to suit requirements quantities. You can use MRP or consumption-based planning for this purpose. Single-item multilevel requirement planning is performed for MRP Area 1010SUB057.

Prerequisite

The raw material is planned at MRP Area level. There is now a requirement for the raw material RM13 and RM14.

Procedure

Test Step #	Test Step Name	Instruction	Expected Result
1	Log On	Log on to the SAP Fiori Launchpad as a Production Planner.	The SAP Fiori Launchpad displays.
2	Access the App	Open Monitor Material Coverage - Net and Individual Segment.	The Application Jobs (Original) screen displays.
3	Search by the raw material	Make below entries and choose Go. Material: for example, RM13
3	Create Stock Transfer Reservation	Select one item, choose Manage Material. Select the MRP Area 1010SUB027 from dropdown list, then choose Go. Select one item. Choose Start MRP Run.	A stock transfer reservation is created.

4.3 Create Outbound Delivery

Procedure

Test Step #	Test Step Name	Instruction	Expected Result
1	Log On	Log on to the SAP Fiori launchpad as an Inventory Manager.	The Fiori Launch Pad is displayed.
2	Access the App	Open Subcontracting Cockpit (F2948).	The Subcontracting Cockpit (Original) screen is displayed.
3	Search for Component or Assembly	Set values to some filters to search Components: Subcontractor: 10300007 Plant: 1010 Choose GO.	The search results show the details with the respective filter Criteria. Following columns must contain relevant data: Component Plant Subcontractor Stock Balance
4	Display Stock Transfer Reservation Item for a component	● Choose small Arrow next to Component to expand the details.	All stock transfer reservation with items number corresponding to the component must be displayed.
5	Create Delivery	Choose a stock transfer reservation Item and then choose Create Delivery.
6	Enter Detail Data	Make the following entries: Material (Original): RM13/RM14 Storage Location: 101C Shipping Point: 1010 Note Please make sure the RM13/RM14 have stock in the storage location. If no sufficient stock, partial outbound delivery will be created.	6
7	Item OK	Verify if the processing status is Valid.
8	Post	Choose Create Delivery.	The system displays the message Delivery 00xxxxxxxx has been saved.

4.4 Pick and Post Goods Issue

Procedure

Test Step #	Test Step Name	Instruction	Expected Result
1	Log on	Log on to the SAP Fiori launchpad as a Shipping Specialist.	The SAP Fiori launchpad displays.
2	Access App	Open Change Outbound Delivery (VL02N).	The app name screen displays.
3	Change Outbound Delivery	Enter the following data: Outbound Delivery: <your delivery> Choose Continue.
4	Picking	Choose Picking tab. Enter picked quantity equal to the delivery quantity. ● Choose Save.
5	Post Goods Issue (Original)	On the Change Outbound Delivery screen, choose Post Goods Issue.	The system displays the message ' Delivery for Subcon. xxx saved, material document xxx created.

4.5 Receive Goods from Subcontracting PO

Purpose

In this step, you post the goods receipt for the material against the subcontracting PO.

Procedure

Test Step #	Test Step Name	Instruction	Expected Result
1	Log on	Log on to the SAP Fiori launchpad as a Warehouse Clerk.	The Fiori Launch Pad is displayed.
2	Open Post Goods Movement tile	Open Post Goods Receipt for Purchasing Document (F0843).	The Post Goods Receipt for Purchasing Document screen is displayed.
3	Select Goods Receipt Order screen	Enter your PO number or search your subcontracting purchase order.	The items of the selected Purchase Order display.
4	Select Item	Select the item for which a goods receipt is to be posted.
5	Post	Choose Post.	The system displays the message 1 document(s) created: Material document 5000000XX 20XX.

4.6 Create Supplier Invoice

Purpose

In this activity, you perform the invoice verification.

Procedure

Test Step #	Test Step Name	Instruction	Expected Result
1	Log on	Open the SAP Fiori launchpad with the Accounts Payable Accountant role.	The SAP Fiori launchpad is displayed.
2	Access the App	Open Create Supplier Invoice (F0859).	The Create Supplier Invoices screen is displayed.
3	Enter General Data	In case of purchase orders created with local currency in your system, make the following entries. Transaction: Invoice Company Code: 1010 Reference: <xxx> (reference invoice number from invoicing party) Gross Invoice Amount : <XXX> Currency: EUR Invoice Date: <Today> Posting Date: <Today> Invoice Party: 10300007	The Create Supplier Invoices screen displays.
4	Enter Purchase Order References	In Purchasing Document References, make the following entries (use a PO you created previously) and choose Enter. Make the following entries (use a PO you created previously). Reference Document Category: Purchase Order/ Scheduling Agreement Purchase Order/Scheduling Agreement: <PO number>	The Purchase Document References screen displays.
5	Select Purchase Order Items	Check the selection of the Purchase Order Items. Confirm the warning messages.	All items of the selected Purchase Order are added to the Purchase Order Item table. You should see material items which refer to the entered purchase order document.
6	Check the Invoice Items data	Check the Amount, the Quantity, the Tax Code (there may already be a tax code that was copied from the purchase order).	The Purchase Order Item's table displays.
7	Check Tax Date	In case the time dependent tax is activated, in the section Tax, the Tax Date indicates the tax calculation date according to the tax rates settings in the prerequisites. Make the following entries. Tax Reporting Date: <Today> Tax Date: <Today> Note The Tax Date is the key date for calculating tax, please maintain it carefully according to your financial business requirements.
8	Check Tax code	In the section Tax check if there is tax code information.	In the Tax tab, you should see the same tax codes as in the items. If there is no tax, specify the tax code V0.
9	Check the balance	Calculate the tax amount from the item amount multiplied by the tax value.	The balance should be zero (or within the defined tolerance).
10	Simulate Supplier Invoice and Check Messages	Choose Simulate. If there are no differences (or if the value is within the defined tolerance), a new screen Simulation appears. You can check the simulation results in Simulation Overview and Simulation Details area. The Supplier Invoice is complete to post. Check the Gross Invoice Amount against the items plus tax amount (if tax code is,V0 you do not have any tax amount)	The supplier invoice is complete to post.
11	Post Invoice	Choose Post.	The invoice is posted.

5: Appendix

Manage Special Stocks

https://help.sap.com/doc/0065bd534f22b44ce10000000a174cb4/2.6/en-US/frameset.htm

Material Requirements Planning

https://help.sap.com/docs/SAP_ERP/85d3fce10e264972a0155c8b46ecf93b/a084b853dcfcb44ce10000000a174cb4.html?version=6.18.latest&q=subcontracting+MRP+area+

How to Prepare for the SAP BTP Solution Architect Certification (with Sample Questions)

2025-05-13T13:31:39.715000+02:00

In this blog, I’ll share practical tips to help you to prepare and be able to pass the SAP BTP Solution Architect certification (P_BTPA_2408). While the post is especially helpful for those aiming to get certified, it also provides useful insights for SAP developers, architects, project managers, and anyone daily involved in SAP BTP projects or operations.

You often start preparing for a certification and end up confused ,what are the right resources, and how deep should you go?

As a Microsoft Certified Trainer and an SAP certified, I always tell my learners: preparing for a certification is like learning English as a second language—you want to be able to use it effectively in your day-to-day work, not become Shakespeare!
Here, I share the exact resources I use in my day-to-day role as an SAP Architect—drawing on over 20 years of hands-on experience in the SAP space. I’ve also included the key materials that can help you confidently prepare for the SAP BTP Solution Architect certification.

Being a successful SAP Solution Architect or Enterprise Architect requires a deep understanding of both on-premises and hyperscaler technologies, combined with hands-on experience from real customer projects. On top of that, strong expertise in SAP solutions is essential. Earning the SAP Solution Architect certification is just the beginning of this journey.

In these blog series, I’ll share practical insights to help you prepare and succeed to achieve this as a goal.

🎓 Why Get SAP Certified? Real-World Benefits:

Being certified earns immediate credibility customers, partners, and hiring managers are more likely to trust your knowledge and decisions.
SAP certification improves your chances of landing your desired role.
Certified professionals often qualify for higher rates, promotions, and leadership roles in SAP projects.
In some cases (e.g., security reviews, migration, SOC documentation), certification adds weight to your approval or sign-off.
The annual certification renewal process ensures your knowledge stays current, especially with cloud solutions and SAP's evolving product roadmap.
Certification validates your hands-on skills and prepares you to deliver better results in real SAP implementations.
Certified professionals are more likely to be chosen for challenging or high-impact projects.
Certification gives you recognition within the broader SAP ecosystem.

Exam Topics and Focus Areas

To pass the certification you’ll need a score of 68% or higher, SAP outlines the following key areas:

Understanding the Intelligent Enterprise and SAP’s reference architecture
Familiarity with SAP BTP services, account models, capabilities (including AI), suite qualities, extensibility types, clean core, and migration strategies (greenfield, brownfield)
SAP Methodologies: Integration Solution Advisory Methodology (ISA-M), Application Extension Methodology, and Data & Analytics Methodology
Identity and access management types, CAP (Cloud Application Programming Model), RAP (ABAP RESTful Application Programming Model), and runtime environments
DevOps principles, SAP BTP commercial models, and master data replication
Recommending solution designs based on requirements and compliance

Key Areas of Study

To gain the knowledge required, focus on the following areas:

Enterprise Architect vs. Solution Architect roles
SAP BTP Framework and Reference Architectures
SAP Discovery Centre, Business Accelerator Hub, and Trust Centre
SAP BTP account model (global accounts, directories, subaccounts)
BTP Identity and Access Management (IAM)
BTP Connectivity and SAP Cloud Connector
S/4HANA implementation types: Greenfield, Brownfield, Bluefield
Application development frameworks and extensibility
Clean Core principles and extensibility models
SAP BTP Data and Analytics (SAP Datasphere, SAP Analytics Cloud)
SAP Business Data Cloud
SAP Data and Analytics advisory Methodology
SAP Integration Solution Advisory Methodology (ISA-M)
SAP Integration solution Capabilities and Services
SAP Build Process Automation, and Signavio
SAP AI tools like Joule, and Generative AI Hub
SAP BTP Commercial Models and BTP estimating costs

Deep Dive: ISA-M in Practice

ISA-M is central to BTP solution architecture and used throughout the integration lifecycle:

Phase 1: Assess your integration strategy (e.g., cloud-to-cloud, on-premise-to-cloud)
Phase 2: Design the hybrid integration platform by mapping use case patterns to technology
Phase 3: Define best practices, blueprints, and guidelines
Phase 4: Establish organizational and operational models for enterprise integration

If you study the Learning journey (FREE) courses listed below, you'll gain the core knowledge needed for this exam.
For deeper insight into areas you may not work with daily, make sure to check out the advanced learning links shared below as well.
The exam time is sufficient , you will not face any challenges there , and by practicing with the BTP trial environment or your organization’s non-production BTP landscape, you’ll be well prepared to pass the exam surely.

Recommended (Free) Learning Courses

Important Reference Links

Advanced Learning and Practice

I've put together 15 sample questions to help you prepare for the exam. These questions are a bit more challenging than the ones you'll typically see on the actual test.

1. Which statement is true about SAP trail account in BTP?
a. A BTP trial account includes only 6 GB of memory for applications
b. You are able to move your Proof of Concept from BTP trail to Pay-As-You-Go account
c. A trial account will be removed when a user not logged on after 90 days
d. You need to manually restart of your solution like HANA DB every day

2. Which SAP licensing model In SAP BTP supports: "The total monthly cost would be deducted from the cloud credits balance monthly"?
a. SAP BTPEA
b. Pay-As-You-Go for SAP BTP
c. Subscription
d. SAP Full User Equivalent (FUE)

3. In which level of BTP account you can add or modify your Identity Authentication Service was assigned?
a. Global account
b. Subaccount
c. Directory
d. All answers above

4. In SAP Road Map, SAP decided to have the traditional Early Watch Report in which solution or platform?
a. SAP Solution Manager
b. SAP Cloud ALM
c. SAP Early Watch alert Workspace
d. DVM in SAP For Me launchpad

5. According to the SAP Integration Solution Advisory Methodology, the Enterprise Architect is responsible for which of the following activities?
a. Definition of integration standards and technology selection guidelines (cross-vendor, hybrid integration platform)
b. Definition of technical integration architectures with a focus on specific integration technologies
c. Definition and communication of patterns, templates, and best practices
d. All of above
Reference:
Link page 51

6. A customer has BOBJ and BODS in their existing SAP on premises landscape, when they are going to migrate to S/4 HANA private edition which solution they can pick to support a similar functionality? Make sure the solution required to be aligned with SAP latest future road map.
a. HANA Cloud, Datasphere
b. SAP Analytic Cloud (SAC), SAP S/4 HANA
c. SAP Intelligent Suite, SAP BW cloud
d. SAP Analytic Cloud (SAC), Datasphere

7. Which statement about SAP Clean Core concept is NOT correct?
a. Deploying a new custom code cannot be on core system (by stack).
b. The clean core strategy advocates for separating custom extensions from the core SAP application.
c. Use "Key User Extensibility" functions of S/4HANA for simple extensions.
d. In classic Extensibility: Applicable primarily to on-premises editions, this tier includes traditional customization methods.

8. Your company has S/4 HANA provisioned in National Security Services (NS2) in Azure, for the entry point of external users you as Solution Architect recommending BTP work Zone as an option.
Which answer respectively meets the requirements (as a cost-effective option) for number 1, 2 descriptions in the diagram below:

a. SAP Build Work Zone advanced edition, SAP Connectivity Service
b. SAP Build Work Zone standard edition, SAP Connectivity Service
c. SAP Build Work Zone advanced edition, Cloud Connector
d. SAP Build Work Zone standard edition, Cloud Connector

9. You are acting as a Solution Architect guiding a migration team that is transitioning from an on-premises SAP PI/PO system to the SAP BTP Integration Suite.
Which of the following tools or services should you recommend to the team, in their appropriate sequence, to support this migration effectively?
a.
SAP BTP Migration Assessment
SAP BTP Integration Assessment
SAP Readiness Check
b.
SAP Readiness Check
SAP BTP Migration Assessment
SAP BTP Integration Assessment
c.
SAP Readiness Check
SAP BTP Integration Assessment
SAP BTP Migration Assessment
d.
SAP BTP Integration Assessment
SAP Readiness Check
SAP BTP Migration Assessment

10. Which of the following SAP BTP services are required or typically used by SAP Cloud ALM?
Select all correct answers (3):
a. SAP Alert Notification Service
b. SAP Automation Pilot
c. SAP Cloud Transport Management
d. SAP Build Work Zone
e. SAP Analytic Cloud
f. SAP Conversational AI

11. Which service can provide a rough rate cost for any service you are going to purchase for BTP solution:
a. SAP For Me Legal & cost
b. SAP Cloud estimator
c. SAP BTP Service Catalog
d. SAP BTP Service Estimator

12. A customer is planning to implement Change Request Management (ChaRM) in the cloud after migrating to SAP S/4HANA Private Cloud Edition on a hyperscaler (e.g., Azure).
Which two main tools or technologies can they use to manage change and transport processes in this cloud-based environment?
a. SAP Solution Manager, CTS
b. Cloud Transport Management System (cTMS), SAP Cloud ALM
c. SAP BTP Cloud Foundry, SAP Cloud ALM
d. SAP Solution Manager, Cloud Transport Management System (cTMS)

13. During the Explore phase of an SAP S/4HANA implementation using SAP Activate methodology, a customer aims to validate fit-to-standard processes and ensure alignment with future-state operations.
They also want to establish a monitoring and task management structure early to prepare for efficient project execution and operations.
Which of the following combinations of tools and capabilities are best aligned to support these objectives? (Choose two.)
a. SAP Signavio Process Insights – to compare legacy KPIs against SAP standard benchmarks and identify transformation opportunities
b. SAP Cloud ALM – to import and manage business process models, simulate variants, and execute fit-to-standard workshops
c. SAP Signavio Process Manager – to model target processes and support fit-to-standard workshops using process content from SAP Best Practices
d. SAP Cloud ALM – to orchestrate project tasks, manage requirements, and support test case management from the Explore phase onward
e. SAP Solution Manager – to configure business roles and monitor production incidents during the Explore phase

14. In the context of SAP Event Mesh and SAP BTP, which of the following are required to establish secure communication between publishers and subscribers? (Choose two)
a. XSUAA service for OAuth authentication
b. Connectivity service with destination type = HTTP
c. Application router for handling protocol mapping
d. Event Mesh instance bound to each application with service keys
e. Transport Layer Security (TLS) tunnelling via Cloud Connector

15. What are benefits of using the Cloud Foundry environment in SAP BTP for event-driven extensions? (Choose two)
a. Native ABAP integration without additional runtimes
b. Horizontal scalability for stateless microservices
c. Event handling with built-in webhook configuration
d. Support for event consumers written in various languages (e.g., Node.js, Java)
e. Built-in support for SAP GUI transactions

Answer Keys:
1-Answer: d; 2.Answer: a; 3.Answer: b; 4.Answer: d; 5.Answer: a; 6.Answer: d; 7.Answer: a;
8.Answer: d;9.Answer: b; 10.Answer: a, b, c; 11.Answer: d; 12.Answer: b; 13.Answer: c, d; 14.Answer: a, d;
15.Answer: b, d

To purchase exam attempts if you don’t have SAP Learning Hub license, you can check the link below:
https://training.sap.com/content/purchase-certification-attempts

Schedule exam for BTP Solution Architect(P_BTPA_2408)

Share with others and Connect with us!

Please leave your comment if you have anything to add!
If you would like to ask questions, please use the community Q&A.
Give us a like and share on social media if you feel it was useful!
You can follow me in People SAP @Amin_Omidy
Thanks!

User Experience Overviews at SAP Sapphire Orlando & Madrid

2025-05-13T18:29:01.995000+02:00

Join us in Orlando May 20-21 or Madrid May 27-28 to get an overview of the latest user experience innovations along with an outlook on what is planned.

Figure 1: Alt Text: Image of Arin Bhowmick, Chief Design Officer, SAP, with the title and ID of his talk, along with date and location for Orlando.

Listen to Arin Bhowmick, our Chief Design Officer:

Title: SAP's user-experience strategy to achieve better outcomes

Orlando: PUX2821, May 20, 2025 3:30 – 3:50 PM EDT

Madrid: PUX1497, May 27, 2025, 1:30 – 1:50 PM CEST

Abstract: Understand how SAP is leading the way to help business users get work done easily and with better outcomes. Our strategy provides a consistent and integrated suite-first experience, infuses AI nearly everywhere, makes it easier for our customers and partners to design and build great UX, and leverages our user research framework to meet your needs.

Figure 2: Alt Text: Image of Thomas Reiss, VP of SAP User Experience Product Management, with the title and ID of his talk, along with date and location for Orlando.

Join me for my road map talk:

Title: User experience innovations in our products: For today and tomorrow

Orlando: PUX2826, May 20, 2025 4:30 – 4:50 PM EDT

Madrid: PUX1498, May 28, 2025, 9:00 – 9:20 AM CEST

Abstract: Have a look at the latest UX innovations across our suite of applications, along with cool innovations coming soon. Examine SAP S/4HANA Cloud and SAP S/4HANA, as well as cloud products such as SAP SuccessFactors and SAP Ariba solutions. Also, check out selected highlights from UI technologies.

Orlando: Further UX Talks

Let me call out these additional UX specific talks:

Suite-first experience: Seamless, consistent, and integrated
PUX2825 Tuesday, 1:00 pm
Creating a great UX for your own applications with SAP Design System PUX2827 Tuesday, 1:30 pm
AI on the go: Run your business with SAP Mobile Start and Joule
PUX2818 Tuesday, 2:00 pm
From insights to impact: Elevating product success through your feedback PUX2822 Tuesday, 3:00 pm
AI-first user experience: What's in it for you?
PUX2824 Wednesday, 11:00 am
An overview of our AI-fueled mobile products across SAP Business Suite PUX2819 Wednesday, 11:30 am
Our mobile experiences empowering today’s and tomorrow’s business users PUX3224 Wednesday, 1:00 pm

Find out more in the session catalog for Sapphire Orlando, May 19-21: Product and User Experience Track.

Beyond that, there are a number of interesting UX-related talks in other tracks, have a look here for a nice summary by Peter Spielvogel:

UX, AI, SAP S/4HANA transformation sessions at SAP Sapphire and ASUG Annual Conference 2025.

Madrid: Further UX Talks

Creating a great UX for your own applications with SAP Design System PUX1499 Wednesday, 11:30 pm
From insights to impact: Elevating product success through your feedback PUX1495 Tuesday, 11:00 am
An overview of our AI-fueled mobile products across SAP Business Suite PUX1494 Wednesday, 3:30 pm

Find out more in the session catalog for Sapphire Madrid, May 26-28: Product and User Experience Track (6 talks).

More Information

I hope to see you either in Orlando or Madrid – feel free to approach me and ask questions!

In case you missed my recent series of blog posts about our recent UX innovations, do have a look, it starts with this one, which contains links to all the other six posts in the series:

SAP User Experience Q1/2025 Update – Part 1: Many New Innovations Available (AI, Joule and More).

🔄 Mapping Pricing Conditions from SAP CPS to SAP CPQ and Back to S/4HANA Sales Documents

2025-05-13T20:42:58.062000+02:00

This blog explores how to map pricing conditions from CPS to CPQ, and how to pass them back to S/4HANA Sales Order, Solution Quotation, or Solution Order—ensuring consistency, accuracy, and automation.

Note : Ensure you have Document Pricing is enabled in your SAP CPQ tenant

Understand the difference between Stalesless Pricing vs Document Pricing from the ground level.

In the evolving SAP ecosystem, integrating pricing logic across systems like SAP CPS (Configuration & Pricing Services), SAP CPQ (Configure Price Quote), and S/4HANA is critical for delivering a seamless quote-to-cash process.

How to set Pricing Procedures to populate the Prices coming from CPS to CPQ and CPQ to backend S/4 HANA

How to map CPS Pricing Condition Types to the SAP CPQ Quote Line Items Fields

🧩 Why Map Pricing Conditions to SAP CPQ Line Items?

SAP CPQ acts as the central quoting engine in many enterprise sales processes. However, pricing logic often resides in Variant Pricing (VP) and Pricing Procedures defined in S/4HANA or CPS. Mapping these conditions to CPQ line items is essential because:

Consistency: Ensures pricing in CPQ matches backend systems.
Automation: Reduces manual intervention and errors.
Transparency: Sales reps see the same pricing logic as backend users.
Integration: Enables seamless handover of quotes to S/4HANA for order processing.

🔧Key Components Involved

CPS (Configuration & Pricing Services),– Hosts the pricing logic and variant configuration model (LO-VC and AVC)
SAP CPQ – Front-end for sales reps to configure, receives pricing from backend and quote, negotiate with customer.
S/4HANA – Backend system for order processing and fulfillment.
Pricing Procedure – Defines how pricing is calculated using condition types.
Condition Types – Represent discounts, surcharges, taxes, etc.
Variant Configuration (VC) – Drives product configuration and stateless pricing logic.
Standard Integrations - SAP provides standard integration packages to connect backend for Master data, and placing a order to S/4 HANA Public, Private Cloud and Onprem

🛠️ Steps to Map Pricing Conditions from CPS to CPQ

1. Define Pricing Conditions in S/4HANA

Create or reuse condition types (e.g., PR00, K004, RA01, RB00, EK01).
Assign them to a pricing procedure.
Ensure access sequences are defined for condition records.

2. Expose Pricing Logic via CPS

CPS acts as a middleware to expose S/4HANA pricing logic.
Use APIs or integration flows to expose condition types and pricing results.

3. Configure SAP CPQ to Consume CPS Pricing

Enable SAP Variant Configuration & Pricing (CPS) integration in CPQ.
Ensure you have Document Pricing enabled in your CPQ for interaction (interactive Sales Pricing)
Map CPS pricing outputs to CPQ line item fields via Setup - Pricing - Pricing Procedures.
For custom business requirement, Use scripting or custom logic to parse CPS response and populate CPQ QICF.

4. Map Condition Types to CPQ Line Items

Use Standard Quote Item fields or Create Quote Item custom fields in CPQ to hold condition values (e.g., base price, discounts, customer price, Rebates, Surcharges, Free Item.... etc).
Use mapping logic to assign CPS condition types to these fields.
Ensure the mapping supports multiple condition types per line item.

5. Pass Pricing Back to S/4HANA via Standard Integration Packages

When quote is accepted by customer, CPQ sends the configuration and pricing data back via Integration Iflow.
Iflow is mapped with all Pricing conditions set in CPQ ( Pricing Procedure Mapping)
Iflow will use standard APIs to create:
- Sales Orders
- Solution Quotation
- Solution Order
Ensure pricing conditions are passed as part of the payload or re-determined in S/4HANA using the same pricing procedure.

Below is the Integration mapped from SAP CPQ Quote Item fields to SAP S/4 HANA Public Cloud - Solution Order

Below is the Integration mapped from SAP CPQ Quote Item fields to SAP S/4 HANA Private Cloud - Solution Quotation

🔄Round-Trip Pricing Flow

✅Best Practices

Use consistent condition types across systems.
Test pricing logic in CPS thoroughly before exposing to CPQ.
Use version control for pricing procedures and VC models.
Log and monitor CPS calls for performance and accuracy.
Train sales teams on how pricing is derived in CPQ.

📌Conclusion

Mapping pricing conditions from CPS to CPQ and back to S/4HANA is a foundational step in achieving a unified and automated sales process. By aligning pricing logic across systems, businesses can ensure accuracy, reduce errors, and accelerate the quote-to-cash cycle.

Revolutionizing Order Management with AI: SAP’s CAS AI/ML Powered Order Management Service

2025-05-15T03:06:41.818000+02:00

In today’s fast-paced business environment, efficiency and customer satisfaction are paramount. With the availability of SAP Cloud Application Services (CAS) AI/ML Powered Order Management Service, a comprehensive managed service designed to transform how businesses handle sales orders, streamline operations, and elevate customer experiences.

The AI Disruption in Order Management

Artificial Intelligence (AI) and Machine Learning (ML) are no longer just buzzwords—they are driving a seismic shift in how businesses operate. The CAS AI/ML Powered Order Management Service is at the forefront of this disruption, embedding advanced AI and ML capabilities to deliver unprecedented levels of efficiency and effectiveness in the order management process.

What is the CAS AI/ML Powered Order Management Service?

This end-to-end, AI-driven service automates and optimizes the entire sales order process, leveraging the power of SAP Business AI, Machine Learning (ML), and Large Language Models (LLMs). Here’s how it works:

Automated Order Extraction: The service intelligently parses emails and extracts attachments (PDFs, TIFFs, JPEGs, etc.) to create new orders automatically.
Real-Time Master Data Validation: It validates customer and product data in real-time against the S/4HANA system, ensuring accuracy and compliance.
AI-Powered Email Responses: Using natural language processing (NLP), the service generates real-time, tailored email responses (in multiple languages) to customers, enhancing communication and satisfaction
Dynamic Order Modifications: Businesses can make real-time updates to orders, adapting to changing customer needs with ease.
24/7 Operational Efficiency: The service operates round-the-clock, eliminating delays and ensuring seamless order processing even during peak demand periods.

How AI and ML Drive Efficiency and Effectiveness

The integration of AI and ML into the order management process brings a new level of precision and speed:

Intelligent Automation: By automating repetitive tasks such as order entry, data validation, and email responses, the service reduces manual effort and minimizes errors.
Real-Time Decision Making: AI-powered business rules ensure that decisions are made instantly, based on predefined criteria, reducing processing time and improving accuracy.
Scalability: The service can handle large volume orders effortlessly, making it ideal for businesses experiencing seasonal surges or rapid growth.

Why Does This Matter?

The CAS AI/ML Powered Order Management Service addresses critical challenges faced by businesses today:

High Operational Costs: Reducing the need for manual intervention and staffing during peak seasons.
Delayed Customer Responses: Ensuring real-time communication to maintain customer trust and loyalty.
Inefficient Sales Processes: Automating repetitive tasks to free up sales teams for value-added activities.
Global Reach: Supporting over 40 languages, making it ideal for multinational corporations.

Key Benefits for Businesses

Scalability: Handle large volumes of orders effortlessly, even during seasonal surges.
Cost Efficiency: Significantly reduce operational costs associated with order processing.
Enhanced Customer Satisfaction: Faster order processing and real-time updates lead to happier customers.
Error Reduction: Real-time data validation minimizes errors and improves accuracy.

A Managed Service with Immediate Impact

Unlike standalone AI services that require manual setup and configuration, the CAS AI/ML Powered Order Management Service is a fully managed solution. This means businesses can adopt it immediately without the need for complex implementation. It integrates seamlessly with SAP S/4HANA and SAP BTP, offering a fixed-scope service that delivers value from day one.

Driving AI Adoption Across Industries

This service not only enhances operational efficiency but also encourages the adoption of SAP’s AI Business Services. By leveraging SAP’s Generative AI Hub, businesses can unlock new opportunities for innovation and growth.

Join the Future of Order Management

The CAS AI/ML Powered Order Management Service is more than just a tool—it’s a game-changer for businesses looking to stay ahead in a competitive market. Whether you’re a multinational corporation or a growing enterprise, this service is designed to meet your needs and exceed your expectations.

SAP Business AI , SAP S/4HANA,

Import Sales Documents - Part 2: How to upload numbers with different separators

2025-05-15T12:11:43.174000+02:00

Dears,

I am glad to introduce you how to upload numbers with different decimal/thousands separators in “Import Sales Documents” apps.

Decimal/Thousands Separator Setting in Excel

Basically, the decimal and thousands separator in excel are using the system separators by default (Path: File/Options/Advanced/Use system separators).

If you want to display the numbers with different separator, you can also uncheck the ‘Use system separators’ option and define your own. For example, you set decimal separator to comma, thousands separator to dot. You will see the number as following in excel (2.38 -> 2,38, 3,456.45 -> 3.456,45).

Notes: Please make sure that the cell format is type of number. The default format is Text.

Limitations in Different Cell Format

There are some limitations due to the design of this app.

Number Value with Number Format

No matter what decimal separator you are using in the excel and in the launch pad user setting, you will preview the number value in the app with dot decimal separator only.

But please be confident that the value will be correctly assigned to the sales document.

Number Value with Text Format

In case you are using the default Text format, currently, we only support dot decimal separator without any thousands separator. For example, if you have a condition value 3,456.45, you must place it in excel cell as 3456.45. Otherwise, you probability will receive ‘Invalid Format’ error after uploading.

Related Information

The Link Collection for Import Sales Documents | SAP Blogs

Import Sales Documents - SAP Help Portal

SAP S/4HANA Cloud Public Edition 2502.3: Final What's New & Product Assistance available

2025-05-15T13:56:18.318000+02:00

With immediate effect, the final What's New information for SAP S/4HANA Cloud Public Edition 2502.3 is now available.

To access the final What’s New information, please use the What’s New Viewer.

In addition, the final Product Assistance (aka Application Help) for SAP S/4HANA Cloud Public Edition 2502.3 is available. Please use the SAP S/4HANA Cloud Public Edition Help Portal page to access it.

For you as a customer, we recommend to also use the Release Assessment and Scope Dependency (RASD) tool.

The Release Assessment and Scope Dependency (RASD) tool provides you with a personalized and tailored view on What’s New information based on the activated and used scope within your system. The information for SAP S/4HANA Cloud Public Edition 2502.3 will be available in RASD within the next few days. A valid Customer S-user ID is required for login. We recommend to use RASD to prepare for upgrades and updates of your system and to focus on the new and changed features that are relevant for you as a customer.

You can use the commenting feature for What’s New. With this feature, authors can evaluate your feedback and incorporate it into the documentation, if needed. We hope that by opening this channel of communication, we can learn how to further improve our What’s New content for you. To use this feature, you need to be logged into the Help Portal. The feature will only be available in the English version of the documents. To learn more about how the feedback process works in SAP Help Portal, see Giving Documentation Feedback.

SAP S/4HANA Public Cloud – Network Performance Guidelines

2025-05-16T09:30:31.274000+02:00

Understanding Network Performance Requirements for SAP S/4HANA Cloud Public Edition

Latency Requirements for Front-End User Access

Latency plays a significant role in the user experience. For SAP S/4HANA Cloud Public Edition, the recommended latency for front-end user access is 200ms or better. This ensures that users experience minimal delays when interacting with the system, leading to a smoother and more responsive interface.

Bandwidth Requirements for Integration and Access

Bandwidth is another critical factor that affects the performance of SAP S/4HANA Cloud Public Edition. Here are the key bandwidth requirements based on the number of users:

Small, trial: 1 Mbps
Medium, 50 users: 2 Mbps
Large, 100 users: 4 Mbps
Extra large, 250 users: 10 Mbps
XXL, 500 users: 20 Mbps minimum

Additionally, the minimum upstream and downstream bandwidth requirements are both 1 Mbps.

Accessing the System across Geo Locations

Accessing SAP S/4HANA Cloud Public Edition from a different geo-region than the backend system datacenter location is generally not an issue anymore. The E2E response time depends on the latency between both locations, but also on the Internet Service Provider quality. Additionally, the E2E response time also depends on the amount of Fiori application roundtrips (some do have the need to sequential calls).

Here is an external example of a global latency matrix.

Connectivity and Integration

The service is designed to support cross-region integration, ensuring that services from various locations can integrate with the S/4HANA Cloud Public Edition. For example, if a customer in Australia is consuming a BTP service deployed in AWS Sydney and later decides to deploy SAP S/4HANA Public Cloud service for its subsidiary in EMEA, the integration into the IAS service in AWS Sydney can be managed seamlessly.

It must be considered that the maintenance windows per service follow geo-region time-windows. Distributing a service across geo-regions has the disadvantage of unsynchronized maintenance windows.

For more detailed information on network requirements and performance guidelines, you can refer to the following SAP notes:

2240690- Front-end Network Bandwidth Sizing for SAP Fiori Apps and SAP S/4HANA
2916959- Fiori Performance Troubleshooting
1100926- FAQ: Network performance

By adhering to these guidelines, you can ensure that your SAP S/4HANA Cloud Public Edition deployment runs smoothly, providing excellent user experience and efficient integration.

Ensuring Optimal Performance

To ensure optimal performance, it's essential for SAP Cloud Delivery teams to monitor and adjust the system resources dynamically. The customer system is constantly monitored, and system quota adjustments happen accordingly. This proactive approach helps in maintaining the required performance levels without any customer interaction for application server adjustments.

If the customer sees the need to adjust the database size, he can create a support ticket for the delivery team to upsize the database (on additional costs) within the next maintenance window downtime.

Q/A Section:

Q: Sizing and capacity management: How do we address the seasonality in a customer’s business, for example retail around Black Friday in the US at Thanksgiving.

A: S/4HANA Public Cloud is being offered as a SaaS solution with rich extension capabilities. Our operations team ensures monitoring and a proper performance.

At the same time customers influence the performance by utilizing customer extensions and APIs as well as how the end user is using the system.

The production system will be sized based on the number of acquired FUEs/the different packages. In addition, available resources will be adapted dynamically. In case a project wants to verify the sizing, they can execute a quick sizer project. Depending on the result, it would be recommended to contact SAP.

Further information:

Benchmark | Sizing | SAP -> Tab Quick Sizer -> HANA-based Cloud Quick Sizer

The customer system is constantly monitored and certain checks/thresholds indicate whether a system need to be enhanced. System quota adjustment happen.

No customer interaction is required for application server adjustments.

Customer can raise a service request ticket, if he can foresee the need for enhancement too (e.g. because of peak-season). They can raise a ticket for database enhancement too (additional costs)

2. Q: Because customers share resources in the Public Cloud, how do we ensure one customer does not take all the resources from the other customers?

A: On Database level, resources are assigned per customer and constantly being monitored and can be adjusted to the growth required by customer. On Application Server level, dedicated application servers are assigned per customer. They are as well being monitored and can be adjusted according to the needs and growth.

3. Q: What are the customer frontend system and browser requirements / technical prerequisites? Which network bandwidth is needed?

A: Some SAP notes on frontend and network pre-requisites:

2240690 - Front-end Network Bandwidth Sizing for SAP Fiori Apps and SAP S/4HANA - SAP ONE Support Launchpad

2916959 - Fiori Performance Troubleshooting - SAP ONE Support Launchpad -> see recommendations in the Network section

Front-End Network Requirements for SAP Business Solutions -> the guide includes a formular to calculate network requirements (chapter 4)

1100926 - FAQ: Network performance - SAP ONE Support Launchpad

Helpful info from ByD

Network Requirements by number of users

Small, trial: 1 mbps

Medium, 50 users: 2 mbps

Large, 100 users: 4 mbps

Extra large, 250 users: 10 mbps

XXL, 500 users: 20 mbps minimum

Minimum requirements

Upstream: 1 mbps

Downstream: 1 mbps

Latency: 200ms or better

4. Q: Performance and load testing: Are these tests performed and if so, how often? - Are they performed for the entire platform or are they also performed on a per module basis? - When was the last set of tests conducted? - What were the results?

A: Performance tests are performed as per the product standard, e.g. before a new version of the application is released.

Performance tests are conducted on a modular level.

Performance tests results for S/4HANA Cloud Public Edition are not publicly available.

For On Premise customers there is an example available in sizing guide.

无启用采购订单工作流审批功能，却报审批工作流错误

2025-05-16T09:30:43.894000+02:00

大家好：

相信会有很多客户启用了采购订单工作流审批的功能，但也会有部分客户没有启用这个功能，如果有客户没有启用该功能，但是发现创建的采购订单报错如下：

这时首先需要检查APP：管理工作流-采购订单中是否有激活的工作流，如果没有并且确定不需要启用该功能请检查APP:输出参数设定中采购订单---渠道

检查分派时间是否有值，如果有请删除后再创建采购订单。这样上述错误就会消失，采购订单会正常创建。

具体原因请见SAP Note:https://me.sap.com/notes/3572781/E

Become a Certified SAP S/4HANA Cloud Public Edition Project Manager

2025-05-16T16:16:17.716000+02:00

In the dynamic world of digital transformation, where businesses are constantly evolving to stay competitive, project management is more crucial than ever. Central to this landscape is the role of professionals equipped to manage complex cloud projects. With the newly launched SAP Certification for Managing SAP S/4HANA Cloud Public Edition Projects (C_S4PM), you can now become a certified project manager and take charge of leading transformative initiatives.

Designed for Project Managers, Consultants, and Technical Leads, this certification empowers you to excel in managing SAP S/4HANA Cloud Public Edition implementations, positioning you as a key player in your organization's digital transformation projects with strategic guidance and expert integration.

How can you prepare for this certification?

You can prepare for the exam in your own pace, by completing the "Managing SAP S/4HANA Cloud Public Edition Projects" learning journey, designed to provide comprehensive insight into SAP S/4HANA Cloud project management. With free access to the learning journey, you can deepen your expertise of managing SAP S/4HANA Cloud Public Edition implementations, specifically focusing on SAP tools, methodologies, and SAP Business Suite portfolio.

Additionally, SAP Community blog posts provide some supporting information to deepen your understanding and preparation:

You can also explore more insights about SAP Activate for SAP S/4HANA Cloud Public Edition on SAP for Me and taking a look at the release notes.

As a prerequisite, candidates should possess project management experience, preferred in ERP implementation, especially SAP Cloud-related projects. Additionally, hands-on experience with SAP S/4HANA Cloud Public Edition solutions and experience with managing cloud-based SAP projects is beneficial.

Kickstart your journey today

By becoming a certified project manager for SAP S/4HANA Cloud Public Edition, you will be able to position yourself as a key contributor to your organization's growth and innovation. You can demonstrate a high level of competency in orchestrating SAP S/4HANA Cloud Public Edition projects, showcasing expertise and leadership in cloud initiatives that are aligned with business objectives.

Certified learners need to continuously keep their skills up-to-date and certifications valid by completing mandatory assessments before their certification expires. With an SAP Learning Hub subscription, you can prepare for and take the stay certified assessments at any time during the validity period of your certification. If you want to know more on how to get and stay certified, you can read this blog post.

Open new professional opportunities for you with new learning and a sought-after certification. Build the skills you need on the SAP Learning site and get inspired by reading learner stories on SAP Community, ask questions and connect with fellow learners. When you’re ready, take your certification exam and start shaping your industry's future!

Cloud to Cloud的数据直连集成：产品主数据

2025-05-19T08:47:35.526000+02:00

随着越来越多的客户选择Cloud的产品，尤其有的客户有多个SAP S/4HANA Cloud Public Edition的系统。由于业务需要，这些Public Cloud系统之间也需要有数据的集成。客户为了简化流程，会希望这些Cloud系统之间能够实现业务数据的直接的集成。这篇文章就会来介绍一下如何使用SAP标准的方案来快速地实现数据的集成。在这一篇文章中，我们首先聚焦在产品（Product）主数据的集成。

1. 产品主数据的集成：

产品主数据的集成我们所参考的是标准的scope item 1RO（Master Data Integration）。

1.1 发送系统的设置（Sender System）：

1.1.1 创建通信系统

输入自定义的System ID、System Name，Host Name为接收系统（receiver system）的地址，维护字段Logical System和Business System。

另外，需要在通信系统中维护通信的inbound user和outbound user。

这里需要特别注意的是，发送系统的outbound user与之后维护的接收系统的inbound user需要一致。

1.1.2 创建通信安排

产品主数据的集成借助了通信场景SAP_COM_0009，创建基于该通信场景的通信安排，选中之前创建的通信系统：

具体使用到的接口信息如下，选择激活该SOAP接口，并且维护Replication Model， Replication Mode， Output Mode。

1.2 接收系统的设置（Receiver System）

1.2.1 通信系统的设置

不同于发送系统中创建的通信系统需要选择接收系统，在接收系统中创建的通信系统是选择其本身，因为在这个通信场景里，它是一个被动接收的角色。

同样，在该通信系统中，需要维护inbound user和outbound user。 inbound user需要特别注意，与之前发送系统的outbound user维护成一致。

1.2.2 创建通信安排

接收端的通信安排不需要激活outbound services，使用的是下面的这个inbound service。因此，不需要特别的设置。

1.3 设置消息的监控

为了测试中能够看到SOAP接口的消息，打开应用Assign Recipients to Users，给测试的用户分配以下条目：

1.4 测试

1.4.1 单个产品主数据集成同步测试

打开应用Replicate by Object Selection， Business Object Type选择Product，填入需要同步的产品主数据编码，点击Replicate即可。

1.4.2 根据Replication Model进行批量的集成同步

打开应用Replicate by Replication Model，选择之前在通信安排中维护的Replication Model，点击Replicate，即可进行全量产品主数据的集成同步。

1.5 查看消息日志

在发送系统中打开应用Message Dashboard，查看产品同步的消息PRDREQ_OUT/00001 Product Replication to Client via Service，可以看到产品主数据已同步：

2. 参考文档

如文章开头所说，实现Cloud to cloud的产品主数据的集成，参考的是标准scope item 1RO，如想了解详细内容，可参考以下链接：

1RO（Master Data Integration）的set-up Guide

通过该标准流程，亦可实现产品主数据在cloud系统之间通过后台作业的方式实现数据的同步。

感谢阅读！

Empowering Business Users: Unleashing the Power of Key User Extensibility in S/4HANA Public Cloud

2025-05-19T11:28:45.400000+02:00

What Is Key User Extensibility?

It is the suite of browser‑based tools built into SAP S/4HANA Public Cloud that lets designated “key users” personalize and extend standard applications, data structures, and business rules—completely code‑free. All extensions are upgrade‑safe, maintainable, and governed by role‑based authorizations.

Simplifying the Business User Experience

UI Adaptation at Runtime

Key users enter Adaptation mode directly within the Fiori launchpad to hide, rename, reposition, or add fields and UI elements on standard apps—no ABAP or UI5 coding required. Once saved, changes persist through quarterly upgrades, keeping the interface aligned with user needs.

Custom Fields & Logic

The Custom Fields app allows users to introduce new fields (for example, adding “StockOwner” to the Warehouse Stock report), then publish these across UIs, reports, analytics, and APIs instantly. In parallel, the Custom Logic app (powered by BRFplus) lets users define simple rules—defaults, validations, derivations—without writing code.

Custom Business Objects

When unique data entities are needed—such as “CycleCountSchedule” for non‑standard count plans—key users define Custom Business Objects. The tool automatically generates database tables, OData services, Fiori list/object pages, and API endpoints, making custom masters behave like standard ones.

In‑App Business Rules Framework

For conditional logic or simple automations (e.g., “If |PostedQty – PickedQty| > 5, set TransferOrderStatus to ‘Review’”), the in‑app BRFplus interface enables rule creation, testing, and assignment within the Custom Logic app—keeping business logic close to the process.

Use Cases (Warehouse‑Focused Scenarios)

I am providing below warehouse specific use cases but similar use cases can be extended to other LoBs as well.

Temperature‑Sensitive Handling Units
A cold‑chain operator adds a “Temperature Range” field to the Handling Unit context, making it visible in packing UIs and IoT integrations for real‑time monitoring.
Tailored Warehouse Monitor Views
The control‑tower team hides unnecessary columns and reorders critical fields (SKU, Available Qty, Storage Type, Quality Status) via UI Adaptation, then saves a “Quality Check” variant—streamlining exception handling.
Custom Cycle Count Schedule Object
Inventory leads create a CBO named “CycleCountSchedule,” automatically generating a Fiori app and APIs that mobile workers use to pull active count plans and report results via handheld scanners.
Auto‑Block Transfers on Quantity Mismatch
A rule in BRFplus blocks any transfer order when the posted vs. picked quantity delta exceeds five units, flagging it for review and preventing inventory inconsistencies.
Enhanced Warehouse‑Stock Report
The team adds “StockOwner” via Custom Fields and includes it in the embedded analytics query—enabling stock‑by‑owner analysis (in‑house vs. 3PL) directly in Fiori dashboards.

Governance & Security

All extensibility tools are controlled by role‑based authorizations, ensuring only users assigned the Key User Extensibility role can access Adapt UI, Custom Fields, Custom Business Objects, or Custom Logic apps—maintaining strict change management and audit trails.

Upgrade Safety & Integration

SAP’s cloud‑native extensibility framework preserves all in‑app modifications across quarterly releases, eliminating upgrade rework. Standard SAP code remains untouched through a clear separation of core and extensions via published APIs and extension points.

Business Impact

Faster Time‑to‑Market: Key users implement changes in days, not weeks.
Reduced IT Backlog: Frees developers for strategic initiatives.
Higher User Adoption & Satisfaction: Personalized UIs and processes.
Continuous Innovation: Rapid experimentation without technical debt.

Who Benefits?

Business Users craving tailored experiences
Consultants empowering clients for self‑sufficiency
Decision‑Makers driving agility and cost efficiency

Next Steps

Open the Custom Fields app to add a sample field.
Launch Adapt UI in your Fiori Launchpad and save a variant.
Explore Custom Business Objects in the Extensibility Library.

SAP Help Portal Links

Adapt UI at Runtime: https://help.sap.com/docs/SAP_S4HANA_CLOUD/4fc8d03390c342da8a60f8ee387bca1a/5c424437bf794f809087fdce391149f2.html
Custom Fields & Logic: https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/57909455bf7c4fdd8bcf48d76c1eae33.html
Creating Custom Fields: https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/3a713139e548434e8a50800e7a7c8172.html
Custom Business Objects: https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/b45696ca0d9143cba040797e9c71aa44.html
Create Custom Business Object (Extensibility Explorer): https://help.sap.com/docs/SAP_EXTENSIBILITY_EXPLORER/b0e8d558ba2f47f5b02a3fc0ac9edc34/6bd534db33694eba9ddde788ef717dfd.html
Business Rule Framework plus: https://help.sap.com/docs/SAP_S4HANA_CLOUD/8b78ae42ec1c4b75937806fcd4fd7d1c/9a6b67ce7c26446483af079719edf679.html
Enabling UI Adaptation at Runtime (Admin): https://help.sap.com/docs/ABAP_PLATFORM_BW4HANA/a7b390faab1140c087b8926571e942b7/402b392585834dd38dd381d8f04b2616.html
Adapting the UI of an SAP Fiori App at Runtime: https://help.sap.com/docs/UI_ADD-ON_FOR_SAP_NETWEAVER_20/17ae0e97e0fc424a9c368f350c0ba6bd/5c424437bf794f809087fdce391149f2.html
Custom Logic App: https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/3aa57e5b9a9f46218ef8cc38d703c8f4.html
Custom Fields & Logic App (NetWeaver): https://help.sap.com/docs/SAP_NETWEAVER_AS_ABAP_751_IP/b4367b1cec3243c4989f0ff3d727c4ab/57909455bf7c4fdd8bcf48d76c1eae33.html
BRFplus Enhancements: https://help.sap.com/docs/SAP_S4HANA_CLOUD/ee9ee0ca4c3942068ea584d2f929b5b1/2fa59f4a0ec249b0aa07aafc7c1ea4c4.html

Two-Year Race To Implement IT Transformation Across 40 Countries: The Story of Accelleron

2025-05-19T14:45:04.751000+02:00

In the complex world of business, undergoing a company-wide digital transformation can be a daunting task. Depending on its scope and impact, such a project requires careful planning, efficient implementation, and versatile thinking to mitigate potential risks and maximize outcomes. Accelleron, a global leader in turbocharging, fuel injection and digital solutions, has embarked on such a journey, implementing SAP S/4HANA Cloud Public Edition across 40 countries. This blog explores their challenging yet rewarding journey, outlining the role localization played in their success.

Accelleron: IT Transformation to a Unified Global Service Organization

Accelleron is at the forefront of large turbocharger manufacturing and servicing, primarily serving the marine and power plant sectors. Originally the turbocharging division of ABB Limited, Accelleron became an independent company when a deal to spin out Accelleron from parent ABB Limited was approved, a transition service agreement (TSA) of 24 months was put in place to complete the divestiture. This separation was an opportunity to transform their IT landscape, allowing them to streamline processes and optimize operations.

The main challenge was consolidating their round-the-clock service business, previously managed across more than 40 countries with 21 different ERP systems. This fragmented IT infrastructure posed challenges to the efficiency and coordination of their already established unified global service organization, impacting their ability to operate seamlessly across global platforms. By adopting SAP S/4HANA Cloud Public Edition, Accelleron successfully streamlined these disparate ERP systems into a single platform with ready-to-run best practices for over 40 countries.

Opportunities on the Road to Transformation

Implementing a global ERP application is a significant and exciting undertaking – particularly under a tight deadline and the goal to adhere to the regulations in over 40 countries. The ability to cover the majority of these countries with SAP delivered local version and the flexibility of custom solutions for the remaining countries proven to be invaluable.

Transitioning to a global platform provided a chance to drive a positive cultural shift within the organization. Accelleron ensured a smooth adoption by engaging their entire organization and securing strong executive sponsorship in this transformative journey.

Since Accelleron's IT ecosystem extends beyond their ERP software, they leveraged the capabilities of public cloud APIs to integrate with existing Customer Relationship Management (CRM), Human Resources (HR), and Finance applications and thus ensured end-to-end processes across applications.

Streamlining Global IT Operations with Effective Localization Strategies

Accelleron's decision to implement SAP S/4HANA Cloud Public Edition has significantly streamlined operations, leveraging effective localization strategies to enhance their already robust global operational capabilities. This targeted approach has optimized the company's response strategy, ensuring continued efficiency in delivering expedited maintenance support and spare parts anywhere in the world within a 48-hour timeframe - a capability they have successfully maintained for years. The cornerstone of their success in streamlining global IT operations was the emphasis on effective localization strategies tailored to the needs of over 40 countries.

By prioritizing compliance with local regulations and addressing country-specific business needs enabled by SAP S/4HANA Cloud Public Edition, Accelleron achieved several key benefits:

Strategic Global and Local Integration: The strategic decision to leverage SAP S/4HANA Cloud Public Edition facilitated the harmonization of global processes with local adaptations, enabling Accelleron to balance coherence and flexibility, streamline operations, and improve onboarding by reducing errors and confusion.
Compliance-Driven Scalability: The localization capabilities ensured that Accelleron could adapt swiftly to local regulatory requirements, maintaining compliance while unlocking broader business opportunities through scalable and flexible operational frameworks.
Rapid Implementation Efficiency: Leveraging localization capabilities, Accelleron achieved swift implementation across 40 countries, minimizing business disruption and maximizing efficiency, showcasing how targeted solutions can expedite complex IT transformations.

These achievements highlight Accelleron's strategic approach to optimizing global operations by leveraging SAP S/4HANA Cloud Public Edition with effective localization, demonstrating how it drives both efficiency and growth.

Keeping Pace with Regulatory Changes across the Globe

In a rapidly changing regulatory landscape, implementing a robust ERP is just the beginning. Accelleron understands that staying compliant with evolving requirements and maintaining an adaptive system is crucial for future-readiness. Gathering timely and accurate information is key to this endeavor. Accelleron’s strategy involves multiple sources, with business colleagues and strategic partnerships playing a vital role in collecting insights. Additionally, they leverage SAP's regulatory change manager to get timely information on upcoming regulatory changes that affect SAP products, to stay ahead of compliance needs.

Prompt analysis of new regulatory mandates allows Accelleron to align swiftly with SAP’s roadmap. In countries with SAP-delivered local versions, customers such as Accelleron rely on SAP to keep these updated.

A particular focus area is e-invoicing, where regulatory demands vary significantly by country and transaction type. For instance, European countries are progressively adopting e-invoicing, causing constant updates to SAP software.

Summary

Accelleron's remarkable journey showcases the transformative power of a well-orchestrated SAP S/4HANA Cloud Public Edition implementation, particularly in a global context. By embracing standardization, prioritizing localization, and fostering strong partnerships, Accelleron successfully navigated the complexities of a large-scale ERP rollout in a notably short time. Their story serves as a valuable example for other organizations looking to achieve similar IT transformations on a global scale.

Learn about Localization Today:

Accelleron shares their experience with localized SAP S/4HANA Cloud Public Edition

Accelleron: Turbocharging a divestiture and resolving data fragmentation challenges with advanced ERP in the cloud

Localization Capabilities on sap.com

Accelerate Global Business Readiness with Localized SAP S/4HANA - SAPinsider

SAP Community for SAP Document and Reporting Compliance

SAP Community for Localization

Regulatory Change Manager: Your Solution to Navigate Regulatory Changes with Ease

Calling Public APIs within Embedded Steampunk: A Practical Guide

2025-05-20T16:08:54.714000+02:00

What is Embedded Steampunk?

Embedded Steampunk is SAP's strategic ABAP Cloud development model available on S/4HANA Public Cloud (and Private Cloud/on-premise with specific releases). It allows developers to build cloud-ready extensions directly on the S/4HANA application server using a restricted, cloud-optimized ABAP language and a defined set of released APIs and extension points.

Key characteristics include:

Cloud-Optimized ABAP: A subset of ABAP focused on cloud principles.
Released APIs: Interaction with SAP functionalities is done exclusively through released APIs (like Business APIs on SAP Business Accelerator Hub) or released extension points.
DevOps Ready: Designed for agile development and integration into DevOps pipelines.
On-Stack: Development happens directly within the S/4HANA system instance.

Example: The Business Partner API (API_BUSINESS_PARTNER)

The Business Partner API is a fundamental public API in S/4HANA, allowing external systems or extensions to create, read, update, and delete Business Partner data (including Customers and Suppliers). It is available as an OData service.

You can find detailed information and the service definition on the SAP Business Accelerator Hub:

SAP S/4HANA Cloud - Business Partner (A2X)

This is your primary reference for the API's structure, entity sets (like A_BusinessPartner), properties, and available operations.

Communication Setup in S/4HANA Public Cloud

To call any external or internal API from your on-stack ABAP code in Embedded Steampunk, you must configure the communication using the standard framework involving:

Communication User: Represents the technical user making the call.
Communication System: Represents the remote system or endpoint being called.
Communication Arrangement: Links a Communication Scenario (defining a set of services) to a Communication System and specifies the technical details like authentication method and service URLs.
Communication Scenario: A pre-defined template grouping related inbound and/or outbound services (e.g., SAP_COM_0008 for Business Partner Integration).

For calling a public API within the same S/4HANA tenant, the Communication System will logically represent your own system's API endpoint.

Steps for Configuration

All communication configuration is done in your Customizing Starter tenant using Fiori apps.

Step 1: Create a Communication User

This user will be used for authenticating the outbound call your ABAP code makes.

Open the "Maintain Communication Users" app.
Click "New".
Enter a User Name (e.g., BP_API_CALLER).
Enter a Description.
Provide a Password and confirm it. Note this password down securely.
Click "Create".

Step 2: Create a Communication System

This system logically represents your own S/4HANA tenant's API endpoint from the perspective of your outbound call.

Open the "Communication Systems" app.
Click "New".
Enter a System ID (e.g., MY_S4_TENANT_API).
Enter a System Name.
Under "General Settings", ensure the Host Name is the API endpoint hostname of your S/4HANA tenant (e.g., myXXXXXX-api.s4hana.cloud.sap).
Under "Users for Outbound Communication", click "+".
Select "Authentication Method" as "User ID and Password".
Enter the User Name of the Communication User you created in Step 1.
Enter the Password for this user.
Click "Create".
Click "Save".

Step 3: Create Communication Arrangements (Two are Needed!)

This is the crucial part for calling an API within the same system. You need two arrangements based on SAP_COM_0008:

One to define how external systems (or your system acting as an external caller) can call inbound to the API.
One to define how your system is configured to call outbound to the API endpoint.

Arrangement 1: Inbound Configuration (Defines how to call IN)

This arrangement is necessary for the API endpoint to be active and reachable, and it defines the user and authentication for incoming calls.

Open the "Communication Arrangements" app.
Click "New".
Select the Communication Scenario: SAP_COM_0008 (Business Partner, Customer, and Supplier Integration).
Enter an Arrangement Name (e.g., SAP_COM_0008_INBOUND).
Click "Create".
In the arrangement details:
- Under "Communication System", select the Communication System you created in Step 2 (e.g., MY_S4_TENANT_API).
- Under "Inbound Communication":
  - Ensure the User Name is the Communication User you created in Step 1.
  - Set the Authentication Method to "User ID and Password".
  - Review the Inbound Services list. You should see the "Business Partner (A2X)" OData service listed with its Service URL and Service ID (API_BUSINESS_PARTNER).
- Under "Outbound Communication": This section is less critical for this specific arrangement's purpose.
Click "Save".
Ensure the Status is "Active".

Arrangement 2: Outbound Configuration (Defines how to call OUT)

This arrangement defines the specific configuration used by cl_http_destination_provider=>create_by_comm_arrangement in your ABAP code to make an outbound call to the API.

Open the "Communication Arrangements" app again.
Click "New".
Choose Newly created Communication Scenario ( note : Create New Communication Scenario: ZZZXXXXYY and provide the Business Partner API as Outbound Service over there ).
Enter a different Arrangement Name (e.g., SAP_COM_0008_OUTBOUND).
Click "Create".
In the arrangement details:
- Under "Communication System", select the same Communication System you used for the first arrangement (e.g., MY_S4_TENANT_API).
- Under "Inbound Communication": This section is not the primary focus here.
- Under "Outbound Communication":
  - Ensure the User Name is the same Communication User you created in Step 1.
  - Set the Authentication Method to "User ID and Password".
  - Crucially, find the entry for the Service ID API_BUSINESS_PARTNER. This entry must exist and be configured with the correct URL (which should be automatically populated based on the scenario and system) and the authentication method.
Click "Save".
Ensure the Status is "Active".

Why the Same Username and Password are Crucial for Basic Authentication:

When your ABAP code initiates the outbound call using the second Communication Arrangement, the system uses the Communication User and password configured in that arrangement's Outbound Communication section for the specified service ID. This user and password are sent as basic authentication credentials to the target endpoint.

Since the target endpoint is the same S/4HANA tenant's API, and that endpoint is configured to accept inbound calls using the first Communication Arrangement, the credentials sent by the outbound call are validated against the user configured for inbound calls in the first arrangement.

Therefore, for basic authentication to succeed in this "calling within the same system" scenario, the Communication User and password configured for Outbound Communication in the second arrangement must match the Communication User and password configured for Inbound Communication in the first arrangement. If they differ, the inbound authentication check will fail, leading to errors (like the SAML redirection ).

ABAP Code to Call the API

Once the Communication Arrangements are set up, your ABAP code in Embedded Steampunk can use the standard OData client proxy or HTTP client framework to call the API.

You would typically use cl_http_destination_provider=>create_by_comm_arrangement with the details of your outbound-focused Communication Arrangement (SAP_COM_0008, MY_S4_TENANT_API, API_BUSINESS_PARTNER) to get the HTTP destination and then create an HTTP client or OData client proxy.

DATA: lo_http_client TYPE REF TO if_web_http_client,
        lo_req         TYPE REF TO if_web_http_request,
        lo_resp        TYPE REF TO if_web_http_response,
        lv_status      TYPE i,
        lv_response    TYPE string.

  TRY.
      "1. Create an HTTP destination using your communication arrangement.
      DATA(lo_destination) = cl_http_destination_provider=>create_by_comm_arrangement(
           comm_scenario  = ' '   " The communication scenario defined in the system
           comm_system_id = ' '                    " For same S/4HANA Public Cloud system
           service_id     = ' ' ).  " Service ID as configured (Outbound Service Name )

      "2. Create the HTTP client – basic auth is handled by the arrangement.
      lo_http_client = cl_web_http_client_manager=>create_by_http_destination( lo_destination ).

      "3. Prepare HTTP headers.
      lo_req = lo_http_client->get_http_request( ).
      lo_req->set_header_fields( VALUE #(
           ( name = 'Accept'      value = 'application/json' )
           ( name = 'Content-Type' value = 'application/json' ) ) ).

lo_req->set_uri_path( '/A_BusinessPartner(''0010000000'')' ).

      "6. Execute the GET request using the client, passing the method.
      lo_resp = lo_http_client->execute(
                  i_method = if_web_http_client=>get ).
  
      data(lv_status1) = lo_resp->get_status( ).
      lv_response = lo_resp->get_text( ).

      IF lv_status = 200.
      ELSE.
      ENDIF.

    CATCH cx_root INTO DATA(lx_root).

  ENDTRY.

  IF lo_http_client IS BOUND.
    lo_http_client->close( ).
  ENDIF.

Conclusion

Calling public APIs within Embedded Steampunk requires careful configuration of Communication Arrangements and Communication Systems. While the concept is similar to calling external APIs, calling an API hosted within the same tenant necessitates understanding the interplay between inbound and outbound configurations. By creating two Communication Arrangements based on the same scenario and system, and ensuring the same Communication User with basic authentication is configured for both inbound and outbound communication for the relevant service, you can successfully enable your on-stack ABAP extensions to interact with public APIs like the Business Partner API. This setup ensures that the system correctly resolves the destination and authenticates the call using the configured basic authentication credentials.

How to Configure and Apply Custom Themes Using UI Theme Designer in SAP S/4HANA Public Cloud via BTP

2025-05-20T16:13:34.160000+02:00

Overview:

This guide provides a clear, step-by-step walkthrough on how to create and apply a custom UI theme for your SAP Fiori Launchpad using the UI Theme Designer in SAP Business Technology Platform (BTP). It covers the full configuration process—from setting up services and assigning roles, to designing a theme in SAP Build Work Zone and integrating it with your SAP S/4HANA Public Cloud system. By the end, you'll be able to deliver a consistent, branded user experience across your SAP applications.

Step 1: Configuration in Btp cockpit

In Btp cockpit go to the subaccount.
Go to services à service marketplace and under application development and automation you will have UI theme designer.
Click on UI theme designer and create new instance.
Select the space and give the Instance name and create it.

Then Assign the UI theme designer specific roles for user.
Goto security, role collections and create new collection for UI theme designer.
Create and assign the CustomCssEditor, Editor, Publisher, Viewer roles to the collection.
Now assign the user Id to the role collection.

To Create a new custom theme design, we need a site and that can be used from the SAP Build Work Zone.
Now Go to services à service marketplace and under application development and automation you will find SAP Build Work Zone.
Click on it and create by choosing the plan standard under the subscriptions.
Click on create and the application will be created.
Now go to the instance and subscriptions and will find the applications and instances created.

Now assign roles to the user for workzone.
Go to security à user and click on the user and assign the specific role collection to it.
Assign the roles Launchpad_Admin, Launchpad_Advanced_Theming and Launchpad_External_User to user.

Step 2: Create new UI theme

Go to the instance and subscription tab and click on the SAP Build Work Zone.
In the workzone, create an site to work on the designer.
Enter the site name and create it.

Now open the created site and click on the user profile in the top right.

In that click on the theme designer.
In that you will find the list of themes available and at the bottom will be an option to open the launch theme designer. Click and open it.

UI theme designer will open and click on create a new theme at top to create new.

Now select a theme that you want to customize and click on create theme.

Then after customizing the changes and click on the theme on left top and click on save & publish.

After that it will ask the theme id and save it and publish it.

After that the theme will be available in the site. You can verify it by opening the theme designer in the site.

Step 3 : Add theme in the public cloud system

Go to the instance and subscription in the btp subaccount.
You will find the UI theme designer instance, click on it and create the service key.

Enter the service key name and click on create.

Then click on the service key and copy the Credentials in the json format.

Now open the public cloud system that you want to add the theme.
In the system open the communication arrangements app.
Click on create to create a new communication arrangement.
Use the scenario id as SAP_COM_0623 as this is for the UI theme designer integration.
And now paste the copied service key credentials and click on create.

Now edit the created arrangement and add the theme id in the Additional theme ids and save.

Open the Manage Content Security Policy app and go to trusted sites and open the UI_RESOURSES_FONTS and just enable the options for managed by customers by clicking on add.

Then click on the user icon and go to settings, in the appearance tab you can find the added custom theme.

Click on it and save it and verify the theme.

The theme is applied successfully.
When some changes is done in the designer, save and publish it in designer and in the system refresh the communication arrangement by saving it.

Conclusion:

Customizing the SAP Fiori Launchpad with your own UI theme is a powerful way to align your enterprise applications with your organization's branding and improve the overall user experience. By following this step-by-step guide, you've learned how to configure the UI Theme Designer in SAP BTP, create and manage themes using SAP Build Work Zone, and successfully integrate those themes into your SAP S/4HANA Public Cloud system. With the theme applied, your users can enjoy a consistent, visually appealing interface. For any future changes, simply update and publish the theme in the designer, then refresh the communication arrangement in the system to reflect the updates instantly.

Data Migration Cockpit in SAP S/4HANA public cloud.

2025-05-22T10:35:12.861000+02:00

The SAP S/4HANA Migration Cockpit provides a user-friendly interface to migrate master and transactional data, such as initial stock, into an SAP S/4HANA system. This document outlines the step-by-step process to upload initial stock using the Migration Cockpit with the "Staging Table" approach.

Prerequisite:

Scope ID to be activate: 2Q2 - Data Migration to SAP S/4HANA from Staging

Business role activation: SAP_BR_BPC_EXPERT- Configuration Expert - Business Process Configuration.

Create a Project
- Navigate to App: Migrate Your Data. App ID: F3473

- Click on Create to start a new project and select Migrate data using staging table.

- Enter the project name (e.g., Initial_Stock_Upload).

Enter the project name, and mass transfer ID is system generated ID for each project and it is used to differentiate the projects across the system. When working on the extension template, fill in the mass transfer ID in the run ID column for identification.

In the database connection, select the local SAP S/4HANA database since this is not a remote migration. Click on this and proceed to step 2. Select the relevant template based on your project activity. Here, you need to pick the material inventory balance template for Initial Stack Upload project.

On the left side, you will see a list of available templates. Choose the template you want and move it to the right side. Then, click on review and create the project.

The project has been created, but it hasn't started yet. When you start the project, the status changes to in progress. After you finish the project, you mark it as finished and choose how long to keep the data. Once this period ends, the project disappears from the list. However, the data you uploaded will still be available in the system.

After you create the project, there are some important details to know before starting.

First, there are stage-wise data validations. In this migration object how many tables are involving and how many instances going to create in the system.

Next mapping tasks table you can get the information during mapping task process, like errors and successful same you will get during simulation and migration.

Download the template
Upload the prepared (data filled) template
Prepare the data
Mapping tasks
Simulation
Migration
Correction file

The above the steps involved in the migration process. If you completed the each process next process with move automatically you need to just execute the process. Incase any error in the current process it won't proceed to next process you need to resolve the error and move to next process. Correction file will not generate for all the process. Incase migration completed with error you need to generate correction file and in that file only failed line items are available. You should correct it and reupload and reprocess the steps again.

Download & Upload.

Download the Template in XML format, file the relevant data, and upload the template.

Prepare.

The staging tables need to be prepared before they can be used to transfer data to SAP S/4HANA.

You can also run a consistency check for the data in the staging tables. All records need to be associated with records at a higher level in the hierarchy of staging tables. The consistency check checks whether these associations exist.

Note that if you have transferred data to the staging tables using template files, the system has already performed the consistency check.

However, if you have transferred data to the staging tables using your preferred tools, we recommend performing the consistency check now.
Mapping Task.

Mapping tasks are essential for ensuring accurate data transfer by specifying how source fields in a legacy system are related to target fields in the SAP system.

Mapping tasks help the system understand how to connect the values in your upload file with the values already defined in SAP.

For example, in your file, you might write the full state name like "Karnataka", but SAP uses a short code like "KA". Instead of changing all values in the file, you can simply create a mapping that tells SAP:

"Whenever you see Karnataka, use KA."

This is important for fields like:

Document Type (e.g., "Standard" → "NB")

Country (e.g., "India" → "IN")

Region (e.g., "Tamil Nadu" → "TN")

These values are fixed in SAP and can’t be overwritten. Mapping helps make sure your data fits SAP’s format without changing your original template.

Simulation.

Run Simulation to validate consistency and completeness.
Check logs for errors or warnings.
Migration.
After a successful simulation, start the Migration.
SAP creates Material Documents using movement type 561.
Migration Result.
Review Log Files for confirmation.
Verify stocks using Display Material Document, Stock Overview (MMBE), or Monitor Material Stocks.
If errors occur, refer to the logs, create the correction file and correct the data, then reprocess.
This completes the initial stock upload using the SAP S/4HANA Migration Cockpit in public cloud.

Note: upload file template should be below 100MB

And this activity is only for material stock upload. There is no option to maintain posting period in the migration template. For this use “Define Settings for Legacy Data Transfer” and maintain the posting period and keep the status as ongoing once activity completed switch to in preparation or completed. SAP Note: 2914088 - Migration Error: Posting period &1 YYYY is not open. - SAP for Me

SAP User Experience in SAP S/4HANA Cloud Public Edition 2502

2025-05-22T20:02:49.565000+02:00

January 24 marked the general availability of the SAP S/4HANA Cloud Public Edition 2502 release. As a cornerstone of modern enterprise, SAP Business Suite empowers organizations to scale, innovate, and adapt faster than ever. SAP cloud ERP applications, SAP Business AI, and SAP Business Data Cloud come together to deliver exceptional business value. But even the most robust cloud ERP wouldn't reach its full potential without a smooth user experience. That’s why we’re committed to evolving our product, listening to your feedback, and pushing the boundaries to deliver a user experience that matches the pace of today's dynamic work environment. Let me show you just how we achieve this in this release. Honorary mention: Generative AI is giving main character energy in this release.

Check out my video below to get a first glimpse into what’s coming in the area of SAP User Experience in SAP S/4HANA Cloud Public Edition 2502:

Joule, the AI Copilot

Following a successful early adoption phase, Joule is generally available and fully integrated in SAP S/4HANA Cloud Public Edition. This AI copilot utilizes generative AI to help users complete tasks more efficiently by using natural language to express their business needs. It offers quick navigation to applications, instant insights into key business data like purchase orders, and concise user enablement content to speed up tasks. Joule also simplifies personalization of the My Home section, allowing users to create cards with critical data for immediate insights. Its capabilities include recommending relevant applications, providing insightful information on business situations without needing to open the application, and offering brief summaries of help content. Users can directly create and add preview cards to the Insights section of My Home.

AI-Assisted Smart Summarization

AI-assisted smart summarization allows you to summarize object pages of SAP Fiori elements-based applications with the power of generative AI. The summarization can be reviewed and modified in a rich text editor and easily copied into productivity tools, such as email or chat, for follow-ups with co-workers and customers. The tool also facilitates efficient sharing through seamless copy-to-clipboard functionality for quick follow-ups. Additionally, users have the option to provide feedback on their experience with the feature, contributing to its continual improvement and adaptation to user needs.

AI-Assisted Easy Filter

The AI-assisted easy filter leverages state-of-the-art generative AI to redefine how users approach filtering within SAP Fiori elements-based list reports. Rather than setting filter values manually through type-ahead inputs and value helps, you can simply type your search query into the filter field. This approach not only enhances the user experience but also provides easy access to recent and favorite filter queries. The AI results are reliable, offering an intuitive and click-efficient experience, which is particularly beneficial for new users navigating the system.

Currently in Beta Testing: AI-Assisted Easy Enterprise Search

The AI-assisted easy enterprise search leverages generative AI to enable natural language querying for business objects throughout the solution. By simply typing your search query into the search field of the SAP Fiori launchpad, users can quickly access the information they need. This feature is especially valuable for its time-saving capabilities when searching with known criteria, providing reliable AI results and offering an intuitive, click-efficient experience that benefits new users in particular.

Currently in Beta Testing: AI-Assisted Smart Personalization of My Home

The AI-assisted smart personalization of My Home allows you to use natural language through the power of generative AI to add insights cards to your My Home experience. This feature streamlines the process by enabling you to add insights cards directly from My Home with just two clicks, including a preview step for the end-user to review the AI-generated result. This tool offers several benefits, such as saving time when adding insights cards, providing better insights into business data, and delivering reliable AI results. It is designed to be intuitive and click-efficient, making it especially valuable for new users.

Currently in Beta Testing: AI-Assisted Error Explanation

AI-assisted error explanation supports in understanding errors in SAP Fiori elements-based applications better and provides first recommendations on how to solve the errors by leveraging the power of generative AI. This innovative feature is seamlessly integrated into the current error visualization, enabling users to generate explanations on demand, which significantly saves time and improves workflow efficiency. By offering intuitive navigation, it delivers both the explanatory insight and recommended solutions within a single, click-efficient action. The process includes well-structured results that clarify the nature of the error and suggest practical resolutions.

Interested in all things AI? Read this blog posts by my colleagues Yannick Peterschmitt and Sang Dao:

To-Dos in Microsoft Teams Integration

The integration of To-Dos in Microsoft Teams allows users to seamlessly access their workflow items from SAP S/4HANA Cloud Public Edition directly through the SAP S/4HANA Cloud for Microsoft Teams app. When you receive a workflow item in SAP S/4HANA Cloud, it triggers a notification in Microsoft Teams. This integration enables you to open the My Inbox application from Microsoft Teams to view details of the workflow items and to take immediate action. It also supports mobile approvals, ensuring flexibility in managing workflows on the go.

Smart Heads-Up of Situations in To Dos

Smart heads-up in To Dos ensure that you're always up to speed on situations requiring your attention, allowing you to manage all critical matters efficiently. This feature provides immediate insight and actionability through an intuitive interface, ensuring that nothing important slip through the cracks. By staying informed about and addressing potential issues early on, it significantly boosts productivity. Additionally, it offers support in prioritizing actions effectively. Users can get an overview of situations on both the standard and extended frameworks directly in the To-Dos section. With just one click, they can access detailed information by navigating to the My Situations and My Situations – Extended apps, depending on their needs.

As you can see, SAP S/4HANA Cloud Public Edition 2502 not only promises a transformed user experience but also enhances organizational productivity and strategic decision-making, bringing you closer to achieving seamless operational excellence, rooted in innovative technology.

Find out more about SAP User Experience in the numerous blog posts by my colleagues Thomas Reiss and Conrad Bernal.

The next release is just around the corner! See you in a bit. 😊

_____________________

The Future of Business, Today: Get Your Access to AI-Assisted Features Thanks to this Limited Promotion Now!

The SAP S/4HANA Cloud Public Edition 2502 update is a strategic investment that combines advanced AI with powerful enterprise management tools. Whether scaling your business, enhancing productivity, or building sustainable operations, its capabilities help support a more agile and resilient future.

Sign up for following features through the limited Promotion for AI-assisted Features in SAP S/4HANA Cloud Public Edition (for all countries, customers, and partners):

The easy filter and smart summarization features in SAP Fiori allow for efficient, natural language filtering of business data and seamless summarization capabilities, enabling users to quickly extract relevant information and jump-start subsequent collaboration.
Facilitate easier understanding and interpretation of financial data with insights from cost center reviews and explanations of fixed-asset depreciation keys.

Don’t hesitate to leave a comment and check out our community page to ask your questions and engage with the experts. Follow the PSCC_Enablement tag to stay up to date with our latest blog posts.

Feel free to follow me on SAP Community and on LinkedIn to not miss any updates.

📽️ Watch the Replays of Our SAP S/4HANA Cloud Public Edition 2502 Early Release Series!

From January 21 to January 24, we hosted a series of 21 compelling live sessions to highlight the exciting innovations shipped with the SAP S/4HANA Cloud Public Edition 2502 release. Missed the live sessions? We've got you covered! Take advantage of the entire series or pick and choose the sessions most relevant to you. You will find a 43-minute-long recording and a presentation for SAP User Experience as well as 20 other topics of interest. Don't miss this chance and watch them on demand–anywhere, anytime.

🔎Find All Our Assets

GROW with SAP is a comprehensive package designed to help businesses of all sizes to successfully adopt cloud ERP, anchored by SAP S/4HANA Cloud Public Edition for optimized processes and intelligent, sustainable operations. We at Cloud ERP Product Success and Cloud Co-Innovation offer a service as versatile as our product itself. Check out the numerous offerings our team has created for you below:

Resolving Carrier Mismatch Errors When planning Freight Units within SAP Transportation Management

2025-05-23T11:01:52.065000+02:00

Transportation is a complex process, often requiring careful coordination of Transportation planners and various supply chain partners. This may require the Transportation planners to replan / reassign the demand (Freight Units) to the capacity (Freight order / Trucks). At times, one issue that can arise is a carrier mismatch error when trying to reassign Freight Units (FUs) to Freight Orders (FOs) after they have been unplanned. In this blog, we will explore this issue and offer some possible options to avoid this issue.

Let’s first look at the details of this issue.

When Freight Units are unplanned from an existing Freight Order, they become visible as unplanned in the SAP Transportation Management cockpit. However, attempting to reschedule them into a different freight order can result (under certain conditions) in a carrier mismatch error. This issue arises when the carrier for the freight units is "derived from predecessor documents," creating a discrepancy if the new Freight Order has a different carrier.

Here is a typical process that leads to this error:

1. Create a Sales order and a Freight Unit (FU) and, using the transportation cockpit, create a Road Freight Order (FO) based on the FU.
2. Open the FO and assign a carrier to it. Save your changes.
3. Delete the FO using the appropriate option within the Transportation Cockpit.
4. Next, create a new, empty FO with a different carrier and attempt to assign the initial FU to the newly created FO by selecting both and clicking "Assign Selected Items.”
5. Save the assignment process and encounter no error at this point.

However, the process can also take place when you have a Delivery created. Here the Freight unit is planned on the FO and the carrier may be assigned either to the delivery or to the Freight Order. Now, when the associated FU is unplanned from the FO, the carrier information remains attached to both the FU and the delivery. As you can see in the below screenshot it mentions “Derived from Predecessor Documents”.

At this point if an assignment is planned to a new FO with a different carrier it leads to the system giving an error “Freight unit xxxx cannot be assigned to Freight Order yyyy, carrier doesn't match”.

The system's retention of the carrier information can be due to various scenarios, such as the carrier being inherent in the delivery and thus needing to be retained despite the unplanning of Freight Order and Freight Unit. There can also be a scenario where the transportation planner may only be changing the Freight Order / Truck and continuing with the existing carrier.

To overcome this challenge, one might consider the following strategies

When Carrier was assigned within Freight order
1. Remove the Carrier from FO1 Before Unplanning / Deletion: By clearing the carrier assignment before unplanning / deleting the FO, you ensure that the FU / delivery has no carrier association and can be reassigned freely.
2. Assign Carrier After Planning: Once you have unplanned the FU and need to reassign it, place it on a FO without a carrier and then assign the carrier to FO post-planning.
When Carrier was assigned within Delivery
1. Delete Carrier from Delivery: Ensure that after FO Unplanning / deletion, the FU and delivery have no carrier specified. This allows reassignment to another FO without issues.

While carrier mismatch is a standard behavior that can occur due to multiple scenarios (some of which are mentioned above), understanding the underlying system logic and utilizing these strategies can facilitate smoother freight unit planning and assignment processes. Kindly note that there can be other options also that can be explored.

Should these solutions not address all nuances of your case, consider submitting a feature request on the [SAP Customer Influence Portal] (https://me.sap.com/notes/0002963059).

Change Process in CPQ – BRIM S/4 Solution Quotation Integration

2025-05-23T11:10:00.035000+02:00

Change is the only constant thing is a common knowledge, so how can business documents be an exception to this? It is not! We live in constantly evolving dynamic times, where business strategies, negotiations and deals are also being adapted and changed based on multitude of influencing factors. So, with every change, how the change is managed and how we execute and plan for change especially when it comes to contractual documents like Subscription contract is the topic for this blog.

The CPQ – BRIM integration enables SAP customers to have the best of on cloud CPQ for quoting process and on-prem BRIM for follow-on contract document creation to further proceed with the quote to cash scenario for revenue generation. As part of contract lifecycle management, for subscription products, this process further extends to support changes to existing subscription contracts. These changes can be made to existing contracts or new contracts can be created for the changes triggered from an existing contract.

Changes like contract extension, renewal, cancellation, change in quantity/ price/configuration adding new products, swapping existing product with new products etc. are possible. Only specific change processes are available based on the state of the contract, e.g. cancelled contract cannot be extended or renewed.

Apart from BRIM prerequisites and configurations, administrators need to enable access rights for the Assets Table Management and Change Processes sections as explained in Assign Access Rights for Setup Sections and Entities , else the sections won’t be visible in the Setup.

How subscription contract change-process works?

The term Change Process here refers to a singular change that can be executed on a subscription contract document. These Change Processes when group together based on business need and flexibility required form a group of processes called Change Process Groups. A single Change Process can belong to multiple change process groups. Example we have change process groups like Change Quantity and Price, where Change Quantity and Change Price are grouped together. Change Process Group column is synced from S/4 HANA, it can be renamed as per required. This column is reflected in the Assets section of the quote page. Kindly note not all change process in S/4 HANA are supported in this integration. Depending on the change process/group selected in the Asset Section, the subsequent fields in the product section become editable. The editability of the fields can be controlled from the Set-up section. From the above example, the quantity and price can be set to editable.

Special change process features like New Contract, Co-Term and Swap, must be additionally set for specific change process groups to further control the and align the behaviour to organization needs. New contract enables the sales rep to either create a new contract from the existing contracts or merge all contracts into one. On placing the order, the new contract is created in SAP S/4 HANA. The old contracts are cancelled, and the references are available in SAP S/4 HANA subscription contract document.

To change a particular Subscription contract or to be more specific the items of a subscription contract, we must add it to the quote via the Add Assets “+” icon. These items are termed as Assets and added to the Asset section of the quote. This Asset section can also be personalised via the set-up. The subscription contracts tied to the selected Involved Party in Quotes page are available to be added to quote as Assets.

After adding Assets to the quote page, if the toggle in the quote header section is turned ON to create a new subscription contract, the subsequent changes to the assets selected from one or more contracts will be transferred to a new contract starting on the day of initiating the changes and the existing contracts will be discontinued.

Mostly every change process has direct impact price or value of the quote. Contract Change Activation Date is the reference taken for adjusting all quote relevant price calculations so that prices are always in line with the changes and applicable from the date changes are implemented.

To conclude, for subscription products the SAP CPQ – BRIM integration offers great flexibility to change the already created subscription contracts with feasibility to group multiple changes, change multiple contracts at the same time create new contracts, merge contracts, cancel contracts etc. to enabling smooth management of the contract lifecycle.

Summary Settings for change process

SAP CPQ Set-Up	SAP CPI (Cloud Platform Integration/iflows)	Solution Quotation in S/4 HANA BRIM
Quote Layout : Add Asset Section	Read Change Process Groups for Quote from SAP BRIM	Subscription Contracts
Quotes -Assets Table Management : Configure the view of Asset Table	Read Change Process for Quote from SAP BRIM	Change Processes
Workflow: Preparing – Preparing: Action – Add Asset to Quote and other actions	Read allowed Change Process Groups for Subscription Contract Item from SAP BRIM	Change Process Group
Quotes- Change Processes – Add Change Process, group and give relevant names to the group. Additional settings can be maintained	Read Subscription contract header from BRIM
	Read Subscription contract items from BRIM
	Replicate Change Contract Processing Status from SAP S4HANA

Most used Change Process Capabilities

Sno	Change Processes/ Capabilities	Description	Additional Info
1	New Contract	Enables to renew or change the existing subscription contract and create a new contract with reference to it.	On placing the order, the new/merged contract is created in SAP S/4 HANA. The old contracts are cancelled, and the references are available in SAP S/4 HANA subscription contract document.
2	Merge	Enables consolidation of multiple contracts into one contract.
3	Product Change/Swap	Enables the change/replacement of an existing subscription product in a contract.	In Set up -Quote -Change Processes -Change Process Group Tab, for the selected change process group, you must select the values for additional settings to Swap.
4	Co-Term	Enables user to co-term – adjust to the same contract duration for different items in a contact.
5	Cancellation	Enables users to cancel a contract item.	Cancellation process needs to be set-up.
6	Contract Extension	Enables the extension of the contact term as set-up in product master data).
7	Change Item Quantity	Enables users to change the item quantity for products in a contract.
8	Change Configuration	Enables users to modify the variant configuration-based characteristics for the configurable products in a contract.
9	Change Price	Enables users to change the price of the products in the contract
10	Add Sub-item	Enables the addition of sub-items during change processes

Disclaimer: Given the dynamic nature of technology and features, and the potential limits to the author's knowledge, please consider the contents of this blog as an attempt to simplify the subject matter and disseminate further information about it. Therefore, it is recommended to verify the details from official sources or conduct further research to ensure complete accuracy and up-to-date information. The insights provided are meant to foster learning and discussion, not to serve as definitive guidance.