SAP Community - SAP S/4HANA Public Cloud

How SAP ESM + Document AI + S/4HANA Work Together to Automate Invoice Processing End‑to‑End

2026-02-20T18:58:48.723000+01:00

One of the most powerful capabilities in SAP Enterprise Service Management (ESM) is its ability to automate invoice processing the moment a customer or vendor sends an email. With SAP Document Information Extraction (Document AI) integrated into ESM, the journey from a raw invoice PDF to a validated posting in SAP S/4HANA Private or Public Edition becomes almost fully automated.

Click on Image to view High Quality

Step 1: The User Sends an Email with an Invoice

A customer or vendor sends an email to the SAP ESM dedicated email address configured for automatic case creation.

The invoice may be:

Attached as a PDF, JPEG, PNG, or
Embedded in the email body itself

SAP ESM picks up both.

Step 2: SAP ESM Automatically Creates a Case

Once the email reaches the ESM mailbox:

A new case is created automatically
The email body and all attachments are stored within the case
The attachments (PDFs, images) trigger SAP Document AI processing immediately

This eliminates manual case creation entirely.

Step 3: SAP Document AI Processes the Invoice

SAP Document AI retrieves the attachment from the case and begins extraction using OCR and machine learning.

It identifies:

Invoice number
Customer or vendor name
Address
Line items
Totals & taxes
Payment terms
Contract or PO references

Document AI also calculates a confidence score for each extracted field.
These scores help determine whether the data is reliable enough to auto‑post or requires user intervention.

Step 4: Validation Using Business Rules & Customer Framework

Once extraction is complete, SAP ESM applies:

Business rules
Customer validation frameworks
Mapping logic
Master data checks

These validations are essential before communicating with S/4HANA.

Examples:

Is the customer known in S/4?
Is the invoice number valid and not duplicated?
Does the PO exist?
Do line item totals match?

Only when the validations pass does ESM proceed to the next step.

Step 5: Invoice Number & Customer Auto‑Identification

If Document AI finds the invoice number, SAP ESM updates the line items and case fields:

invoiceNumber → updated
customerNumber → auto‑identified
isClearing → set according to logic (e.g., invoice found, ready to post)

This gives the ESM user immediate visibility:

Has the system recognized the invoice?
Has the customer been identified?
Is the invoice ready for posting?

Step 6: ESM Sends the Validated Invoice to S/4HANA via OData APIs

Once the case has all mandatory and validated data, the ESM user can trigger the next action:

“Post Invoice to S/4”

At this point:

ESM calls S/4HANA OData APIs
A draft or final FI invoice is created
Additional steps like clearing, matching, or workflow approvals occur inside S/4

This hands-off process ensures:

No manual entry in S/4
No data inconsistencies
Full auditability from source → document → posting

Step 7: ESM User Monitors and Completes the Process

Inside the ESM case, the user can now see:

Status of the posting
Document number returned from S/4
Any errors (e.g., master data inconsistencies)
New actions available for follow-up

They can then:

Update the customer
Add missing reference information
Re-trigger the posting
Close the case once processing is complete

Result: A Fully Streamlined, AI‑Driven Invoice Workflow

By integrating SAP ESM, Document AI, and S/4HANA, organizations benefit from:

✔ Zero manual invoice entry

✔ Auto-identification of customers and invoice data

✔ Early error detection using business rules

✔ Faster posting to S/4HANA

✔ End-to-end transparency in one central case

✔ Higher accuracy and reduced effort

This modernizes invoice handling from a traditionally manual process into an intelligent, automated workflow.

Learning Journey : Business Documents in ESM

Budget Management in SAP S/4HANA Public Cloud

2026-02-21T11:52:00.377000+01:00

Hello SAP Folks,

In SAP S/4HANA Public Cloud, Budget Management (known as Funds Management in SAP S/4HANA Private Cloud) has been revamped and its structure has been changed. Following is a brief introduction to Budget Management in SAP S/4HANA Public Cloud.

Introduction to Budget Management in SAP S/4HANA Public Cloud:

Budget management supports budgeting-based management of funds at public sector institutions where revenue and expenditure are budgeted according to legislative criteria, such as payment in kind, area of responsibility, program/function and source of funds. All the financial transactions which leads to eventual outflow of cash are monitored strictly via an allocated budget and revenues planning and monitoring is also done. Planning, posting, maintenance of budget, monitoring is all possible if we have Budget Management in place .

The business benefits of using Budget Management are as follows:

Maintain and monitor the allocation, distribution, or changes of approved budgets
Plan, standardize, schedule, and monitor financial and budget close activities
Automate and streamline budget processes, and reduce manual effort
Optimize closing of open commitments and financial and managerial accounting
Immediate budget availability checking to ensure regulatory compliance
Real-time reporting to aid in time-sensitive managerial decision

A helpful link is given below which has helped me a lot to demystify the Budget management and its underlying concepts in SAP S/4HANA Public Cloud, I am still learning it and will keep you posted if I found something new.

Describing SAP S/4HANA Cloud Public Edition, Public Sector

Scope Item for PSM-Budget Management:

Following scope item was automatically activated when I selected the Public Sector Management.

PSM Bundle Activated

When we activate Public Sector Management in SAP S/4HANA Public Cloud , it automatically setup and configure SAP Budget Management (known as PSM-Funds Management in SAP S/4HANA Private Cloud) , SAP Grants Management and Fund Accounting.

Budget Management in SAP S/4HANA Public Cloud:

In this knowledge article, I will shed some light on my experience with execution and setting up Budget Management in Public cloud. There are lot things which have been set to work differently in SAP Budget Management. If the public sector budget management solution is activated, transactions impacting the budget require budget-relevant account assignments. Often the budget-relevant account assignments are not manually entered, they are derived by the system.

Key Differences between SAP S/4HANA Private and Public Cloud from Budgeting Perspective:

Budget management reuses the master data from other SAP components in combination with PSM-specific master data as account assignments for budget-relevant transaction postings. I will illustrate this statement with below table.

I also could not see any option to post payment and commitment budget separately in Budget Management, if anyone has come across such functionality in SAP S/4HANA Public Cloud then please do let me know.

SAP S/4HANA Private Cloud	SAP S/4HANA Public Cloud
In SAP S/4HANA Private Cloud or even in ECC, for Funds Management system to work, two FM account assignments were mandatory namely Commitment Items and Fund Center	In SAP S/4HANA Public Cloud, Budget management works with a mandatory combination of Fund , Budget Period, Cost Center & Account Number
In SAP S/4HANA Private cloud, there could be one to one, one to many or many to one relationship between Commitment Item to General Ledger, you could automatically derive Commitment item if there was 1:1 relationship .	In SAP S/4HANA Public cloud is has flipped altogether. You can only have 1:1 relationship between your General ledger and Budget Account . The same concept is applicable for cost center.
In SAP S/4HANA Private Cloud, the department for which budget was posted was known as Fund Center.	In SAP S/4HANA Public Cloud, Fund center has been replaced with Cost Center as it has reused the cost accounting assignment.
In SAP S/4HANA Private Cloud, the budget head for which budget was posted in combination with Fund center was known as Commitment item.	In SAP S/4HANA Public Cloud, the G/L account is used as master data for the budget account.
Use of Fund was not mandatory.	Use of Fund is mandatory for posting the budget, the type of fund external or internal plays a critical role here.
Budget period was optional in PSM-FM and you had to activate it to be used.	Budget period is mandatory in SAP S/4HANA Public Cloud
WBS never existed in PSM-FM	We can optionally use WBS element in Budget management to post Budget.
Use of grant account assignment was only needed in PSM-FM Budgeting workbench when SAP GM-GTE was activated.	Use of Grant account assignment is mandatory in Budget Management.
Funded Program was available in PSM-FM budgeting and derivation rule.	Funded Program does not exist in Budget management.

Important Master Data Object in Budget Management:

Following are the important master data objects in Budget management with their pictorial overview.

Fund Master Data:

Fund master data is an important master data object in budget management without which Budget can not be posted. It is maintained by app SAP Fiori Apps Reference Library

Budget Account Master Data:

FIORI App which is used to create budget account which is nothing but a General Ledger Account is SAP Fiori Apps Reference Library

Budget Period:

Budget Period master data is managed via FIORI App Manage Budget period. The budget period master data is pre-delivered in SAP S/4HANA Public Cloud , Budget periods have been maintained for the entire FY e.g. FY 2026 is represented by one budget period, you may create your own master data for Budget period, if you want to maintain and post budget month wise.

I will not go into the details of other master data objects in PSM-Budget Management like Cost Center and WBS as they are self explanatory .

Derivation Rule in S/4HANA Public Cloud:

In SAP S/4HANA Public Cloud, derivation rules are maintained very differently unlike Private Cloud where we had FMDERIVER/FMDERIVE to maintain derivation rules, we have a dedicated FIORI App to Maintain Substitution/Validation Rules for Public Sector as shown below.

Posting Budget in SAP S/4HANA Public Cloud:

Budgeting is a holistic process and it follows many critical steps like preparing, planning, consumption monitoring, returns and supplements etc. It has been described in below flow diagram which has been taken from SAP help library.

In Budget management, budget is posted via following app.

There are lot of functionalities within above app and it would require me to write a separate blog on the future and processes available within Budget posting app. For now, please just bear in that the original budget, supplement, transfers or return etc. happens using this app.

Budget Management Integration with SAP Analytical Cloud (SAC):

The SAP_COM_0761 communication scenario offers the integration of Public Sector Management (PSM) on SAP SAP S/4HANA Cloud as a data provider with SAP Analytics Cloud (SAC).

This scenario offers OData services for the following:

Fund and hierarchy
Grant and hierarchy
Budget period and hierarchy
Actuals and Commitment

The following figure provides an overview of how to do the following:

The master data, budget, and actuals and commitment are transferred between SAP Analytics Cloud and SAP S/4HANA Cloud
The budget is prepared in SAP Analytics Cloud

Recording Commitments/Actuals:

In public sector organisations, no business activity that will result in a future payment can be approved without an available budget. Therefore, it is crucial to reserve budget funds as early as possible to ensure proper financial planning. When governments anticipate future payments, typically due to an operational commitment document, they must formally set aside the required budget. This reservation process, known as "commitment updating," is documented via a financial budget consumption record and is subject to active availability checks.

In some instances, a formal commitment document may not exist, meaning the actual expenditure directly consumes the budget. Both scenarios – whether the spending is linked to a prior commitment or directly consumes the budget – are referred to as "actual updating." The combination of commitment and actual postings constitutes the total budget consumption.

Public Sector Management (PSM)-specific information for both commitment and actual transactions is recorded in the universal journal (table ACDOCA). This involves adding the relevant PSM account assignments, master data, and budgetary attributes to the universal journal entries when documents are posted. Specifically, commitment postings (such as purchase requisitions, purchase orders, or earmarked funds) update ledger 0E, while actual expenditure documents update ledger 0L.

You can learn a lot more about updating commitment/actuals using below link
Recording Commitments and Actuals

Recording Commitments:

We will create a PO to record commitment of 5000 USD on budget dimensions for which I have posted budget. Commitment update logic that I have observed in SAP S/4HANA Public Cloud PSM conforms to PBET (Period Based Encumbrance Tracking) . If you want to learn more about it then please read my blog on PBET
Period Based Encumbrance Tracking in PSM-FM - SAP Community

Recording Actuals:

Posting invoices, expense JVs , GRNs impacts the actuals and converts commitments into actual postings. I have posted a GRN of 60% of PO value which was 5000 USD. I have posted 3000 USD as GRN and now we will see effect of recording actuals on reporting and commitments which were already recorded.

Manage AVC Exceptions:

There is a FIORI app to make exceptions for cost center or budget account if you want to exclude them from budget check. You can do it for a specific user and control address for a given date range and assign a tolerance profile which does not check budget etc.

Budget Management Integration:

You can learn about budget management integration with other components within SAP S/4HANA Public Cloud system using below link. The link offers deep dive into integration of budget management with Finance, SuccessFactors, Procurement, Concur, Plant maintenance etc.

Describing Finance Integration

Limitations in SAP S/4HANA Public Cloud Budget Management:

During my exploration of Budget Management functionality , I came across following limitations in Budget Management Module.

1. No segregation of payment and commitment budgets
2. Budget structure functionality has not been offered in Budget Management
3. I didn’t see multi-year budget functionality in Budget Management
4. AVC is not as highly configurable as it is in Private cloud
5. Budget commitment does not happen when you park or save as complete an Invoice or a JV

Finishing Lines:

In summary, while both SAP Budget Management in the Public Cloud and SAP Funds Management are powerful tools for financial control, they cater to distinct strategic imperatives. The former offers a modern, cloud-native approach aligned with future-proof digital transformation, while the latter provides established, comprehensive functionalities. Understanding these differences is paramount for organisations navigating their journey in the SAP ecosystem. Please let me know if there are improvements or corrections needed 😊.

SAP S/4HANA Public Cloud Edition – All Communication Scenarios in One Place (Bookmark)

2026-02-22T22:46:31.615000+01:00

Make sure to bookmark this blog so you can easily revisit all communication scenarios in one place. Share it with your friends and colleagues—it’s a handy resource when searching across different SAP portals.

What is a Communication Scenario ?

A Communication Scenario in SAP S/4HANA Public Cloud is a predefined, packaged set of:

Inbound/Outbound APIs (OData, SOAP)
Business events (for event-based integration)
Message types
Authorizations

These scenarios act as the integration between SAP S/4HANA Public Cloud and other SAP Products or external systems.

Think of a communication scenario as a “bundle” :

These are the APIs and permissions this external system is allowed to use, and here’s how the communication should happen.

Each Communication Scenario is delivered by SAP S/4HANA Public Product Release and cannot be modified—but you can activate and use them.

Key Components of a Communication Scenario

A typical scenario includes:

1. Communication User

A technical user used for authentication.
Supports:

Basic Authentication
OAuth 2.0 (strongly recommended)

2. Communication System

Represents the external (non‑SAP) or SAP system you are integrating with.
Defines:

Hostname / Token URLs
Outbound target URLs
Authentication method

3. Communication Arrangement

This is where everything comes together.

You assign:

The Communication Scenario
The Communication System
The Communication User
Any specific parameters (e.g., service URLs, outbound destinations)

If you think of it simply:

Scenario = Template
Arrangement = Active Configuration

Why Are Communication Scenarios Important?

In S/4HANA Public Cloud, customers cannot create custom communication scenarios like in on‑premise or Private Cloud. This strict governance ensures:

Security and compliance
System stability
Standardized integration patterns
Ease of lifecycle management during upgrades

So instead of customizing scenarios, you configure and connect the right SAP‑delivered scenarios.

APIs usually come with a predefined communication scenario. To use the APIs, you first need to create a communication arrangement based on the communication scenario.

How to Configure a Communication Scenario: Step-by-Step

Step 1: Create a Communication User

SAP Fiori App: Maintain Communication Users

Create user → assign password → store securely
Or create an OAuth technical user (preferred)

Step 2: Create a Communication System

SAP Fiori App: Communication Systems

Here you:

Assign the communication user
Maintain authentication method
Provide target host details
Configure OAuth token endpoint (if applicable)

Step 3: Create Communication Arrangement

SAP Fiori App: Communication Arrangements

Steps:

Select the communication scenario (e.g., SAP_COM_0008)
Assign the communication system
Review/activate inbound and outbound services
Copy Service URLs for external system use

Once activated, the APIs are ready for use.

Testing Your Scenario

You can test APIs using tools like:

SAP Business Accelerator Hub (API Hub)
SAP Integration Suite (CPI)
SAP API Management
SAP BTP (Destinations, Side by Side Extensions, Extensibility Development)
Custom integrations

Check which communication scenario fits to your purposes best.

The following list gives you an overview of the most important communication scenarios available today

Communication Scenario ID	Description
SAP_COM_0227	(Deprecated) Marketing - Campaign Execution - Twitter Integration
SAP_COM_0346	(Deprecated) Product Lifecycle Management - Product Structure Integration
SAP_COM_0901	ABAP Test Cockpit - ATC Run Integration
SAP_COM_0942	Advanced Backorder Processing Integration
SAP_COM_0438	Advanced Compliance Reporting Integration using SLHACR
SAP_COM_0A49	AI-Assisted Situation Handling Integration
SAP_COM_0454	Application Monitoring Integration (Obsolete)
SAP_COM_0508	Ariba Network - Buyer Integration via CIG Integration
SAP_COM_0081	Ariba Network - Supplier Integration
SAP_COM_0032	Ariba Network Integration
SAP_COM_0244	Asset Central Foundation for Maintenance Execution Integration
SAP_COM_0262	Asset Intelligence Network for Product Information Integration
SAP_COM_0395	Asset Management Master Data Integration
SAP_COM_0927	Assignment Status for Project Demands Integration
SAP_COM_0790	Assortment Module Integration
SAP_COM_0935	Available-to-Promise (ATP) Check Integration
SAP_COM_0379	Bank - Bank Integration
SAP_COM_0141	Batch Management - Batch IDoc/RFC Inbound Integration
SAP_COM_0337	Batch Management - Batch OData Inbound Integration
SAP_COM_0774	Batch Management - Batch SOAP Inbound Integration
SAP_COM_0855	Batch Management - Batch SOAP Outbound Integration
SAP_COM_0120	Billing Integration
SAP_COM_0745	Block Intercompany Postings Integration
SAP_COM_0349	Buffer Profile Integration
SAP_COM_0359	Buffer Sizing Integration
SAP_COM_0888	Business Data Orchestration - UI Integration
SAP_COM_0594	Business Data Orchestration Integration
SAP_COM_0121	Business Event Handling Integration (Obsolete)
SAP_COM_0A54	Business Event Log - SQL Read Integration
SAP_COM_0943	Business Object Cost Center Integration
SAP_COM_0A91	Business Object Project Settlement Rules Integration
SAP_COM_0091	Business Partner, Customer and Supplier Blocking Integration
SAP_COM_0008	Business Partner, Customer and Supplier Integration
SAP_COM_0394	Business Place Integration
SAP_COM_0698	Business Process Intelligence Integration
SAP_COM_0523	Business Process Monitoring Push Integration
SAP_COM_0366	Business Role Change Document Integration
SAP_COM_0A04	Business Role Read Integration
SAP_COM_0345	Business Situation Integration
SAP_COM_0376	Business Situation Master Data Integration
SAP_COM_0706	Business Solution Order Integration
SAP_COM_0327	Business User Change Document Integration
SAP_COM_0889	Business User Logon Details Read Integration
SAP_COM_0083	Central Finance Subsidiary Integration
SAP_COM_0A94	Central Payment Repository - Requested Payment Integration
SAP_COM_0A13	Certificate Read Integration
SAP_COM_0160	Classification Systems Integration
SAP_COM_0163	Classification Systems OData/SOAP Integration
SAP_COM_0A31	Cloud Integration Automation Integration
SAP_COM_0430	CMIS Repository Synchronization Integration
SAP_COM_0054	Commercial Project Integration
SAP_COM_0A07	Communication Arrangement Read Integration
SAP_COM_0400	Communication Management - HTTP Inbound Test Integration
SAP_COM_0401	Communication Management - HTTP Outbound Test Integration
SAP_COM_0A48	Communication Management Integration
YY1_GLACCOUNTLINEITEM	Communication Scenario for GLAccountLineItem
YY1_GLACCOUNTLINEITEM_V2	Communication Scenario for GLACCOUNTLINEITEM_V2
YY1_I_GLACCLINEITEM	Communication Scenarion for I_GLAccountLineItem
SAP_COM_0A06	Communication System Read Integration
SAP_COM_0A05	Communication User Read Integration
SAP_COM_0946	Complaint Handling Integration
SAP_COM_0070	Concur Integration
SAP_COM_0536	Concur POC Integration
SAP_COM_0A08	Content Security Policy Read Integration
SAP_COM_0682	Contract Accounting - Payment Information Integration
SAP_COM_0298	Contract Proposal Integration (Deprecated)
SAP_COM_0165	Convergent Invoicing Integration
SAP_COM_0158	Credit Memo Request Integration
SAP_COM_0722	CSN Exposure Integration
SAP_COM_0464	Custom Code Migration Integration
SAP_COM_0449	Custom Services for Citizen Integration
SAP_COM_0589	Customer Data Return Integration
SAP_COM_0134	Customer Material Info Record Integration
SAP_COM_0459	Customer Return Bulk Integration
SAP_COM_0497	Customer Return Bulk Replication Integration
SAP_COM_0157	Customer Return Integration
SAP_COM_0730	Customer Type Integration
SAP_COM_0080	Data Quality Management Integration
SAP_COM_0209	Data Warehouse - ODP Data Extraction Integration
SAP_COM_0159	Debit Memo Request Integration
SAP_COM_0570	Delivery Insights Integration (Obsolete)
SAP_COM_0571	Delivery Insights Replication App Integration (Obsolete)
SAP_COM_0106	Delivery Processing Integration
SAP_COM_0557	Digital Manufacturing for Network wth Quality Info Record Integration (Obsolete)
SAP_COM_0693	Digital Vehicle Integration
SAP_COM_0426	Direct Material Sourcing With Blockchain Integration
SAP_COM_0077	Distributed Manufacturing Integration (Deprecated)
SAP_COM_0854	Document and Reporting Compliance Cloud Edition Integration
SAP_COM_0703	Document Compliance - Electronic Document File Integration
SAP_COM_0626	Document Compliance Localization Extension Integration (Obsolete)
SAP_COM_0529	Document Compliance PEPPOL Integration
SAP_COM_0A82	Document Information Extraction Integration
SAP_COM_0872	DRC - External reporting system integration
SAP_COM_0548	E-Mail - Outbound Integration
SAP_COM_0A52	EBPP Payment Request Integration
SAP_COM_0448	eDocument - Argentina eInvoice Integration
SAP_COM_0669	eDocument - Chile eInvoice and Delivery Note Integration
SAP_COM_0670	eDocument - Colombia eInvoice and Incoming eInvoice Integration
SAP_COM_0255	eDocument - eInvoice and ePayment for Mexico Integration
SAP_COM_0689	eDocument - Greece electronic Tax register books Integration
SAP_COM_0417	eDocument - Hungary Invoice Registration Integration
SAP_COM_0629	eDocument - India eInvoice Solution Integration.
SAP_COM_0429	eDocument - India eWay Bill Solution Integration
SAP_COM_0418	eDocument - Italy eInvoice and Incoming eInvoice Integration
SAP_COM_0873	eDocument - Peru eInvoice and Delivery Note Integration
SAP_COM_0856	eDocument - Poland eInvoice Integration
SAP_COM_0631	eDocument - Portugal eInvoice Integration
SAP_COM_0494	eDocument - Portugal Transport Registration Integration
SAP_COM_0859	eDocument - Romania eInvoice Integration
SAP_COM_0898	eDocument - Saudi Arabia eInvoicing Integration
SAP_COM_0A19	eDocument - Serbia eInvoice Integration
SAP_COM_0877	eDocument - Slovakia eInvoice Integration
SAP_COM_0468	eDocument - South Korea eInvoice Integration
SAP_COM_0419	eDocument - Spain Invoice Registration Integration
SAP_COM_0846	eDocument - Switzerland eInvoice and Incoming eInvoice Integration
SAP_COM_0851	eDocument - Thailand eInvoice Integration
SAP_COM_0421	eDocument - Turkey eDelivery Note and Incoming eDelivery Note Integration
SAP_COM_0422	eDocument - Turkey eInvoice and Incoming eInvoice Integration
SAP_COM_0225	eDocument - VAT Register Books for Spain Integration
SAP_COM_0688	EHS - Authority Servers with E-Waste Documents Integration
SAP_COM_0857	Electronic Document - Egypt Electronic Invoice Integration
SAP_COM_0056	Employee Central Cost Center Integration
SAP_COM_0441	Employee Central Financial Master Data Integration
SAP_COM_0028	Employee Central Payroll Integration
SAP_COM_0535	Employee Central via SAP CPI Integration
SAP_COM_0001	Employee Integration
SAP_COM_0518	Enterprise Contract Management - DocuSign Integration
SAP_COM_0521	Enterprise Contract Management - External Linked Objects Integration
SAP_COM_0809	Enterprise Contract Management - Hub System Integration
SAP_COM_0868	Enterprise Contract Management - Icertis Integration
SAP_COM_0869	Enterprise Contract Management - Icertis Operational Integration
SAP_COM_0890	Enterprise Contract Management - Icertis UI Integration
SAP_COM_0823	Enterprise Contract Management - Microsoft Teams Integration
SAP_COM_0824	Enterprise Contract Management - Microsoft Teams Operational Integration
SAP_COM_0437	Enterprise Contract Management and Assembly Integration
SAP_COM_0A23	Enterprise Event Enablement - Direct Event Inbound Integration
SAP_COM_0A22	Enterprise Event Enablement - Direct Event Outbound Integration
SAP_COM_0092	Enterprise Eventing Integration
SAP_COM_0963	Enterprise Project - Blockable Function Integration
SAP_COM_0470	Enterprise Project - Central Finance Integration
SAP_COM_0250	Enterprise Project - Collaboration Integration
SAP_COM_0252	Enterprise Project - Collaboration UI Integration
SAP_COM_0656	Enterprise Project - Collaborative Project Integration
SAP_COM_0723	Enterprise Project - Internal Project Type Integration
SAP_COM_0726	Enterprise Project - Project Priority Integration
SAP_COM_0725	Enterprise Project - Project Processing Status Integration
SAP_COM_0724	Enterprise Project - Project Profile Integration
SAP_COM_0917	Enterprise Project Element - Deliverable Type Integration
SAP_COM_0308	Enterprise Project Integration
SAP_COM_0945	Enterprise Project Service Organization Integration
SAP_COM_0369	Environment, Health and Safety - Incident Reporting Integration
SAP_COM_0671	Environment, Health and Safety - Workers' Compensation Associations Integration
SAP_COM_0747	Environment, Health, and Safety - Automatic Data Collection Integration
SAP_COM_0A71	Environment, Health, and Safety - SAP SuccessFactors Learning Integration
SAP_COM_0602	Event Consumption Model Inbound Test Integration
SAP_COM_0634	Excise Tax EMCS Integration
SAP_COM_0568	Excise Tax Integration
SAP_COM_0694	Extensibility UI Text Translation Adaptation Integration
SAP_COM_0176	External Billing Document Request Integration
SAP_COM_0301	External HR Workforce Integration
SAP_COM_0177	External Sales and Use Tax Calculation Integration
SAP_COM_0326	External Scheduler - Application Job Administration Integration
SAP_COM_0064	External Scheduler - Application Job Scheduling Integration (Deprecated)
SAP_COM_0944	Factory Calendar - Pull Inbound Integration
SAP_COM_0732	Field Logistics - Manage Supplier Item Integration
SAP_COM_0752	Field Logistics - Pack Container Integration
SAP_COM_0753	Field Logistics - Shipment Voyage Integration
SAP_COM_0952	Field Logistics Shipment Container Integration
SAP_COM_0679	Field Logistics Supplier Item to Fieldglass Integration
SAP_COM_0074	Fieldglass Integration
SAP_COM_0321	Finance - Account Payable Configuration Integration
SAP_COM_0313	Finance - Account Payable Payment Advice Integration
SAP_COM_0251	Finance - Account Payable Positive Pay Integration
SAP_COM_0316	Finance - Account Receivable Bank Statement Integration
SAP_COM_0314	Finance - Account Receivable Payment Advice Integration
SAP_COM_0303	Finance - Accounting Analytics Integration
SAP_COM_0338	Finance - Accounting Correspondence Integration
SAP_COM_0277	Finance - Accounting Document Integration
SAP_COM_0179	Finance - Accounting Master Data Integration
SAP_COM_0590	Finance - Accounts Payable Discount Management Integration
SAP_COM_0759	Finance - Accounts Receivable Lockbox Integration
SAP_COM_0719	Finance - Accounts Receivable SEPA Mandate Integration
SAP_COM_0775	Finance - ACR Services for Partner Enablement Integration
SAP_COM_0129	Finance - Activity Type Integration
SAP_COM_0649	Finance - Advanced Payment Management - Watch List Screening Hits Integration
SAP_COM_0648	Finance - Advanced Payment Management - Watch List Screening Integration
SAP_COM_0315	Finance - Allocation Posting Integration
SAP_COM_0278	Finance - Bank Account Inbound Integration
SAP_COM_0279	Finance - Bank Account Outbound Integration
SAP_COM_0256	Finance - Bank Connectivity Integration
SAP_COM_0127	Finance - Bank Integration
SAP_COM_0388	Finance - Bank Reconciliation Integration
SAP_COM_0733	Finance - Brazilian ACR Reports Integration
SAP_COM_0284	Finance - Cash Management Inbound Integration
SAP_COM_0285	Finance - Cash Management Outbound Integration
SAP_COM_0126	Finance - Central Entity Integration
SAP_COM_0674	Finance - Central Finance SEPA Mandates Integration (Obsolete)
SAP_COM_0727	Finance - China Payment Requisition Integration
SAP_COM_0241	Finance - Cloud Consolidation Data Collection Integration
SAP_COM_0336	Finance - Cloud Consolidation Master Data for Group Reporting Integration
SAP_COM_0903	Finance - Cloud Consolidation Task for Group Reporting Integration
SAP_COM_0348	Finance - Cloud Consolidation Transaction Data for Group Reporting Integration
SAP_COM_0A83	Finance - Collections and Dispute Automation - Dispute Integration
SAP_COM_0639	Finance - Contract Accounting Collection Agency Integration
SAP_COM_0638	Finance - Contract Accounting External Cash Desk Integration
SAP_COM_0663	Finance - Contract Accounting Factoring Integration
SAP_COM_0696	Finance - Contract Accounting General Ledger Hub Integration
SAP_COM_0731	Finance - Contract Accounting Integration
SAP_COM_0511	Finance - Contract Accounting Integration for SAP Cash Application
SAP_COM_0167	Finance - Contract Accounting Master Data Integration
SAP_COM_0361	Finance - Contract Accounting Open Item Management Integration
SAP_COM_0716	Finance - Contract Accounting Promise to Pay Integration
SAP_COM_0380	Finance - Contract Accounting Security Deposits Integration
SAP_COM_0458	Finance - Contract Accounting SEPA Mandate Integration
SAP_COM_0579	Finance - Contract Accounting: Disconnection and Reconnection of Services
SAP_COM_0357	Finance - Cost Center Activity Type Integration
SAP_COM_0133	Finance - Cost Center Integration
SAP_COM_0173	Finance - Credit Management Integration
SAP_COM_0740	Finance - Credit Management Master Data Integration
SAP_COM_0B18	Finance - Currency Exchange Rates Integration
SAP_COM_0B17	Finance - Direct Debit Mandate Integration
SAP_COM_0705	Finance - EBRR Manual Accruals Integration
SAP_COM_0645	Finance - ELSTER Integration
SAP_COM_0543	Finance - EU VAT Registration Number Validation Integration
SAP_COM_0312	Finance - Event-Based Revenue Recognition Integration
SAP_COM_0563	Finance - Fixed Asset Integration
SAP_COM_0A93	Finance - Fixed Asset Master Data Integration
SAP_COM_0A95	Finance - Fixed Asset Posting Integration
SAP_COM_0A97	Finance - Fixed Asset Revaluation Index Integration
SAP_COM_0A96	Finance - Fixed Asset Usage Object for UoP Depreciation Integration
SAP_COM_0362	Finance - Freeze Period Integration
SAP_COM_0370	Finance - Group Reporting Planning Integration
SAP_COM_0248	Finance - Group Reporting Reported Financial Data Integration
SAP_COM_0377	Finance - Intercompany Matching Item Integration
SAP_COM_0125	Finance - Internal Order Integration
SAP_COM_0559	Finance - Master Data Integration for Cost Center Integration (Obsolete)
SAP_COM_0585	Finance - Master Data Service for Account Assignment Elements Integration
SAP_COM_0A62	Finance - Memo Records 2.0 Integration
SAP_COM_0654	Finance - One Time Password Integration
SAP_COM_0331	Finance - Payment Advice Integration
SAP_COM_0711	Finance - Payment Approval Integration
SAP_COM_0132	Finance - Payment Request Integration
SAP_COM_0002	Finance - Posting Integration
SAP_COM_0131	Finance - Profit Center Integration
SAP_COM_0368	Finance - Profit Center OData Integration
SAP_COM_0754	Finance - Reassign Costs and Revenues Integration
SAP_COM_0852	Finance - SAP SuccessFactors Payroll - Journal Entry Integration
SAP_COM_0844	Finance - Slovakia Bank Accounts Register Integration
SAP_COM_0130	Finance - Statistical Key Figure Integration
SAP_COM_0B07	Finance - Statistical Key Figure OData Integration
SAP_COM_0554	Finance - Third-party's Communication Client Integration
SAP_COM_0794	Finance - Transaction Data - Write - for Group Reporting Integration
SAP_COM_0923	Finance - Treasury Financial Transaction NPV Integration
SAP_COM_0A85	Finance - Treasury FX Exposure Management Integration
SAP_COM_0442	Finance - Treasury Payment Request Integration
SAP_COM_0332	Finance - Treasury Position Flow Integration
SAP_COM_0333	Finance - Treasury Posting Journal Integration
SAP_COM_0853	Finance – SAP SuccessFactors Payroll – UI Integration
SAP_COM_0580	Finance Employee Central Account Assignment Derivation Validation Integration
SAP_COM_0B00	Finance-Contract Accounting Accounts Receivable/Accounts Payable Integration
SAP_COM_0416	Financial Closing Integration
SAP_COM_0566	Financial Tasklist Integration
SAP_COM_0096	Financials - SAP Customer Engagement Center Integration
SAP_COM_0114	Foundation Master Data Integration
SAP_COM_0782	Goods Receipt Confirmation Integration
SAP_COM_0230	GRC - Process Control and Risk Management Integration
SAP_COM_0734	GRC - SAP Risk and Assurance Management Integration
SAP_COM_0391	GRC SAP Privacy Governance Integration
SAP_COM_0364	Handling Unit Integration
SAP_COM_0932	IC Configure - Variant Configuration Bundle Model Integration
SAP_COM_0093	Identity Management Integration
SAP_COM_0193	Identity Provisioning Integration
SAP_COM_0431	Image Based Ordering for S/4H Procurement ML Integration (Deprecated)
SAP_COM_0A42	Incident Management - OSHA Reporting Integration
SAP_COM_0546	Incoming China VAT Invoice Integration
SAP_COM_0110	Inspection Master Data Integration
SAP_COM_0810	Integration of Enterprise Contract Management - Connected System
SAP_COM_0446	Intelligent Accruals Recommendation Integration
SAP_COM_0718	Intelligent Product Proposal Integration
SAP_COM_0572	Intelligent Product Selection Consumption Integration
SAP_COM_0538	Intelligent Product Selection Integration
SAP_COM_0280	International Trade Content - Commodity Codes Integration
SAP_COM_0281	International Trade Content - Control Classes Integration
SAP_COM_0282	International Trade Content - Customs Tariff Numbers Integration
SAP_COM_0240	Invoice Process Integration
SAP_COM_0B08	Invoice Summary Output Integration
SAP_COM_1238	Invoice Summary Output Integration (Deprecated)
SAP_COM_0383	Joint Venture Accounting API Integration
SAP_COM_0381	Joint Venture Partner Billing Files Integration
SAP_COM_0882	Joule Integration
SAP_COM_0330	Kanban Control Cycle Integration
SAP_COM_0520	Kanban Summarized JIT Call Outbound Integration
SAP_COM_0540	Key Mapping Client Integration
SAP_COM_0539	Key Mapping Hub Integration
SAP_COM_0647	Launchpad Content Exposure to SAP BTP Integration
SAP_COM_0791	Legal Context Integration
SAP_COM_0178	Legal Document Integration
SAP_COM_0140	Legal Transaction Integration
SAP_COM_0396	Maintenance Planning Integration
SAP_COM_0397	Maintenance Processing Integration
SAP_COM_0B27	Manage External Tax Items Integration
SAP_COM_0765	Manage User-Defined Criteria Integration
SAP_COM_0667	Manufacturing - MRP Change Request Integration
SAP_COM_0522	Manufacturing Execution - Order and Confirmation Integration
SAP_COM_0156	Manufacturing Execution Integration
SAP_COM_0135	Marketing - Campaigns Integration (Obsolete)
SAP_COM_0371	Marketing - Event Inbound Integration
SAP_COM_1095	Marketing - Kubernetes Dialog Scaler Integration
SAP_COM_0022	Marketing - Reporting Integration
SAP_COM_0780	Master Data - Location Substitution Integration
SAP_COM_0708	Master Data - Product Exclusion Integration
SAP_COM_0779	Master Data - Product Substitution Control Integration
SAP_COM_0778	Master Data - Product Substitution Group Integration
SAP_COM_0707	Master Data - Product Substitution Integration
SAP_COM_0581	Master Data Service for Proj Control Object Integate (Deprecated)\| (Obsolete)
SAP_COM_0108	Material Document Integration
SAP_COM_0263	Material Document Outbound Notification Integration
SAP_COM_0147	Material Price Changes and Inventory Values Integration
SAP_COM_0164	Material Stock Integration
SAP_COM_0447	Material Stock Quantity Replication Integration
SAP_COM_0A79	MDG - Cloud Integration - Business Partner Pull Integration
SAP_COM_0477	Message Monitoring - Error Propagation Integration
SAP_COM_0569	Message Monitoring - Outbound Integration of Error Propagation
SAP_COM_0578	Message Monitoring - SAP Alert Notification service for SAP BTP - Integration
SAP_COM_0947	Migration Cockpit API Integration
SAP_COM_0816	Migration Cockpit Direct Transfer Integration
SAP_COM_0259	Migration Cockpit Integration
SAP_COM_0678	Migration Cockpit Integration
SAP_COM_0181	OData Metadata Integration
SAP_COM_0B06	Omnichannel Promotion Pricing Services Integration
SAP_COM_0046	Open Catalog Integration
SAP_COM_0007	OpenText Business Event Integration
SAP_COM_0577	Outgoing China VAT Invoice Integration
SAP_COM_0881	Output Management - Output Queue Integration
SAP_COM_0399	Packing Instruction Integration
SAP_COM_0896	Packing Instruction Replication with Ariba Network Integration
SAP_COM_0A38	Payables and Receivables Financing with Taulia
SAP_COM_0644	Photo Replication for Workforce Integration
SAP_COM_0107	Physical Inventory Document Integration
SAP_COM_0A15	Planon Real Estate Management for SAP UI Integration
SAP_COM_0398	Plant Maintenance Execution Integration
SAP_COM_0319	Plant Maintenance Master Data Integration
SAP_COM_0322	Plant Maintenance Notification Integration
SAP_COM_0344	Plant Maintenance Order Integration
SAP_COM_0814	Portugal Series Validation Code Registration Integration
SAP_COM_0257	Portuguese Tax Authority Integration
SAP_COM_0920	PRA Accounting Data Integration
SAP_COM_0815	PRA Funds Notification Integration
SAP_COM_0919	PRA Production Data Integration
SAP_COM_0921	PRA Valuation Data Integration
SAP_COM_0940	PRA Well Completion Daily Pressure Integration
SAP_COM_0939	PRA Well Completion Downtime Integration
SAP_COM_0938	PRA WellTest Integration
SAP_COM_0806	PRA XI Inbound Integration
SAP_COM_0373	Predictive Journal Entry Data Integration
SAP_COM_0739	Predictive MRP Masterdata Integration
SAP_COM_0911	Preferred Supplier List Integration (Deprecated)
SAP_COM_0953	Preliminary Billing Document Integration
SAP_COM_0861	Price Calculation - UI Integration
SAP_COM_0294	Pricing Data Integration
SAP_COM_0295	Pricing Data Replication Integration
SAP_COM_0467	Printing - Notification Integration
SAP_COM_0A86	Printing - Print Queue Administration Integration
SAP_COM_0466	Printing - Pull Integration
SAP_COM_0524	Procurement - Ariba Contract Management Integration
SAP_COM_0450	Procurement - Ariba Sourcing Integration
SAP_COM_0451	Procurement - External Sourcing Integration
SAP_COM_0324	Procurement - Operational Supplier Evaluation Score Integration
SAP_COM_0760	Procurement - Supplier Quotation Management Integration (Deprecated)
SAP_COM_0526	Procurement – Ariba Supplier Risk Integration
SAP_COM_0633	Procurement Central Sourcing - Ariba Sourcing Integration
SAP_COM_0116	Procurement Master Data Integration
SAP_COM_0152	Product Allocation Object Integration
SAP_COM_0161	Product Allocation Sequence Integration
SAP_COM_0792	Product Assignment to Distribution Center Integration
SAP_COM_0115	Product Availability Information Integration
SAP_COM_0309	Product Classification Integration
SAP_COM_0797	Product Compliance - Integration
SAP_COM_0666	Product Compliance - Integration of Third-Party Regulatory Content
SAP_COM_0772	Product Compliance - Label Template Authoring Integration
SAP_COM_0A60	Product Compliance - Logistics Inbound Integration
SAP_COM_0786	Product Compliance - Regulatory Documentation Reference Service Integration
SAP_COM_0514	Product Compliance - Regulatory Documentation Service Integration
SAP_COM_0748	Product Compliance - Substance Volume Tracking Integration
SAP_COM_0009	Product Integration
SAP_COM_0339	Product Lifecycle Management - Change Record Integration
SAP_COM_0150	Product Lifecycle Management - Core Master Data Integration
SAP_COM_0151	Product Lifecycle Management - Engineering Change Management IDOC Integration
SAP_COM_0937	Product Lifecycle Management - EPD Integration
SAP_COM_0290	Product Lifecycle Management - Intelligent Product Design BOM Integration
SAP_COM_0214	Product Lifecycle Management - Intelligent Product Design DMS Integration
SAP_COM_0215	Product Lifecycle Management - Intelligent Product Design EADesigner Integration
SAP_COM_0291	Product Lifecycle Management - Intelligent Product Design RD Integration
SAP_COM_0428	Product Lifecycle Management - IPD Collaboration Change Record Integration
SAP_COM_0105	Product Lifecycle Management - Master Data Integration
SAP_COM_0254	Product Lifecycle Management - ML for Document Classification Integration
SAP_COM_0866	Product Lifecycle Management - PLM System Inbound Integration
SAP_COM_0867	Product Lifecycle Management - PLM System Outbound Integration
SAP_COM_0136	Product Lifecycle Management - Recipe Development Integration
SAP_COM_0A47	Product Lifecycle Management - UI Integration
SAP_COM_0149	Product Lifecycle Management - Variant Configuration Integration
SAP_COM_0751	Product Lifecycle Management - Variant Configuration Integration
SAP_COM_0910	Product Sourcing Integration (Deprecated)
SAP_COM_0104	Production Planning Integration
SAP_COM_0519	Production Planning Master Data Integration
SAP_COM_0328	Production Supply Area Integration
SAP_COM_0704	Production Volume Management Integration (Deprecated)
SAP_COM_0909	Project Billing Integration
SAP_COM_0111	Project Control Integration
SAP_COM_0925	Project Demand Category and Type Integration
SAP_COM_0783	Project Demand Integration
SAP_COM_0926	Project Demand Status Integration
SAP_COM_0843	Project Management in SAP Project and Resource Management - UI Integration
SAP_COM_0A09	Protection Allowlists Read Integration
SAP_COM_0761	Public Sector API Integration
SAP_COM_0101	Purchase Contract Integration
SAP_COM_0A29	Purchase Order Accruals Review Integration
SAP_COM_0053	Purchase Order Integration
SAP_COM_0238	Purchase Order Process Integration
SAP_COM_0113	Purchase Request for Quotation Integration
SAP_COM_0102	Purchase Requisition Integration
SAP_COM_0239	Purchase Requisition Process Integration
SAP_COM_0103	Purchase Scheduling Agreement Integration
SAP_COM_0123	Purchasing Category Integration
SAP_COM_0145	Purchasing Info Record Integration
SAP_COM_0166	Purchasing Quota Arrangement Integration
SAP_COM_0162	Purchasing Source Integration
SAP_COM_0588	Quality Certificate Exchange Integration
SAP_COM_0389	Quality Certificate Inbound Integration
SAP_COM_0358	Quality Info Record Integration
SAP_COM_0124	Quality Inspection Process (with BAPI) Integration
SAP_COM_0318	Quality Inspection Process Integration
SAP_COM_0153	Quality Notification and Defect Processing Integration
SAP_COM_0915	Read Access Log Integration
YY1_READWORKFORCEPERSON	Read workforce person
SAP_COM_0402	Remote Function Call - RFC Inbound Test Integration
SAP_COM_0636	Remote Function Call - RFC Metadata Integration
SAP_COM_0403	Remote Function Call - RFC Outbound Test Integration
SAP_COM_0404	Remote Function Call - WebSocket RFC Inbound Test Integration
SAP_COM_0405	Remote Function Call - Websocket RFC Outbound Test Integration
SAP_COM_0902	Renegotiation Integration
SAP_COM_0112	Reservation Integration
SAP_COM_0928	Resource Assignment Source for Project Demands Integration
SAP_COM_0A11	Resource Management in SAP Project and Resource Management - API Integration
SAP_COM_0840	Resource Management in SAP Project and Resource Management - UI Integration
SAP_COM_0560	Responsibility Management Team Integration
SAP_COM_0640	Retail Merchandise Management - Point of sale Master data Integration
SAP_COM_0652	Retail Merchandise Management - Point Of Sale Transaction Data Integration
SAP_COM_0795	Returns Inspection OData v4 Integration
SAP_COM_0701	Revenue Accounting Integration
YY1_RM_SCENARIO	RM api call
SAP_COM_0A33	S/4H Document and Reporting Compliance - SAP CIM Integration
SAP_COM_0228	S/4HANA Activate New Features - Innovation Discovery System Integration
SAP_COM_0837	S/4HANA QM/NCM - Quality Issue Resolution Integration
SAP_COM_0641	Sales - Document Information Extraction Service Integration
SAP_COM_0427	Sales Area Replication Integration
SAP_COM_0A10	Sales Contract Bulk Replication Integration
SAP_COM_0119	Sales Contract Integration
SAP_COM_0325	Sales Credit Management Integration
SAP_COM_0829	Sales Credit Management Outbound Integration
SAP_COM_0117	Sales Inquiry Integration
SAP_COM_0746	Sales Master Data Integration
SAP_COM_0B03	Sales Material Determination Record Integration
SAP_COM_0288	Sales Order Bulk Integration
SAP_COM_0287	Sales Order Bulk Replication Integration
SAP_COM_0109	Sales Order Integration
SAP_COM_0334	Sales Order Without Charge Integration
SAP_COM_0702	Sales Price Integration
SAP_COM_0A12	Sales Quotation Bulk Replication Integration
SAP_COM_0118	Sales Quotation Integration
SAP_COM_0382	Sales Scheduling Agreements Consignment Issue Integration
SAP_COM_0360	Sales Scheduling Agreements Integration
SAP_COM_0444	Sales Scheduling Agreements With Buyers Integration
SAP_COM_0223	Sales with Buyers Integration
SAP_COM_0848	Sales with SAP Business Network Integration
SAP_COM_0A69	SAP AI Core - GenAI - Customer Outbound Integration
SAP_COM_0443	SAP Analytics Cloud for Liquidity Planning Integration
SAP_COM_0087	SAP Analytics Cloud for Planning Integration
SAP_COM_0065	SAP Analytics Cloud Integration
SAP_COM_0545	SAP Ariba Buying Integration
SAP_COM_0A00	SAP Ariba Buying UI Integration
SAP_COM_0574	SAP BTP Connectivity Service - On Premise Integration
SAP_COM_0A34	SAP Build - Extensibility Integration
SAP_COM_0A61	SAP Build Process Automation - Master Data Governance Process Integration
SAP_COM_0743	SAP Business Accelerator Hub - Open Resource Discovery Integration
SAP_COM_0A84	SAP Business Network - Supplier Search UI Integration
SAP_COM_0042	SAP Business Warehouse Integration
SAP_COM_0A20	SAP Cash Application for ISLM Integration
SAP_COM_0650	SAP Cash Application Integration
SAP_COM_0897	SAP Central Invoice Management - UI Integration
SAP_COM_0690	SAP Cloud ALM - Change and Deployment Management Integration
SAP_COM_0527	SAP Cloud ALM for operations - Application Monitoring Push Integration
SAP_COM_0A43	SAP Cloud Application Event Hub - UI Integration
SAP_COM_0892	SAP Cloud Application Event Hub Integration
SAP_COM_0200	SAP Cloud Connector Integration (Obsolete)
SAP_COM_0838	SAP Cloud for Real Estate - UI Integration
SAP_COM_0213	SAP Cloud for Real Estate Contract Management Integration
SAP_COM_0066	SAP Cloud Identity Access Governance Integration
SAP_COM_0180	SAP Cloud Platform - Financials Integration
SAP_COM_0434	SAP Cloud Platform ABAP Environment - CRP Usage Integration
SAP_COM_0510	SAP Cloud Platform ABAP Environment - Software Component Test Integration
SAP_COM_0235	SAP Cloud Platform Business Rules - Inbound Integration
SAP_COM_0236	SAP Cloud Platform Business Rules - Outbound Integration
SAP_COM_0528	SAP Cloud Platform Master Data for Workforce Integration(obsolete)
SAP_COM_0575	SAP Cloud Platform Master Data Service for Workforce Integration (Obsolete)
SAP_COM_0835	SAP Collaboration Manager Integration
SAP_COM_0676	SAP Conversational AI Integration
SAP_COM_0683	SAP CP Notification Service Integration
SAP_COM_0576	SAP Data Intelligence - Metadata Explorer Integration
SAP_COM_0531	SAP Datasphere - ABAP CDS Extraction - OData Integration (Deprecated)
SAP_COM_0532	SAP Datasphere - ABAP CDS Extraction - WebSocket Integration
SAP_COM_0216	SAP Digital Payments Add-On Integration
SAP_COM_0653	SAP Digital Payments Add-On Integration
SAP_COM_0A67	SAP Document AI - UI Integration
SAP_COM_0597	SAP Document Management Service - Attachments Integration
SAP_COM_0194	SAP Document Management Service - Notification Inbound Integration
SAP_COM_0191	SAP Document Management Service - OAuth2.0 mTLS Outbound Integration
SAP_COM_0668	SAP Document Management Service - Outbound Integration
SAP_COM_0190	SAP Document Management Service - SAML Bearer Outbound Integration
SAP_COM_0A66	SAP Dynamic Forms Integration
SAP_COM_0011	SAP Enable Now Integration
SAP_COM_0B10	SAP FSM - Plant Maintenance - CPI Based Integration
SAP_COM_0B12	SAP FSM - Plant Maintenance - Direct Integration (P2P)
SAP_COM_0084	SAP Global Trade Services Integration
SAP_COM_0246	SAP GR/IR Account Reconciliation Status Proposals Integration (Obsolete)
SAP_COM_0A98	SAP Green Ledger - UI Integration
SAP_COM_0573	SAP HANA Spatial Services Integration
SAP_COM_0492	SAP Integration Suite, Advanced Event Mesh Integration
SAP_COM_0493	SAP Integration Suite, Advanced Event Mesh Integration, Validation Service
SAP_COM_0275	SAP Localization Hub - eDocuments - DCS Integration
SAP_COM_0047	SAP Localization Hub - eDocuments Integration
SAP_COM_0249	SAP Localization Hub - External Tax Calculation Engine Integration
SAP_COM_0549	SAP Maintenance Assistant Integration
SAP_COM_0841	SAP Market Rates Management - UI Integration
SAP_COM_0659	SAP Master Data Integration - Outbound Integration
SAP_COM_0060	SAP Order Management Integration
SAP_COM_0863	SAP Process Automation Integration
SAP_COM_0A63	SAP Real Estate - Finance Interface Integration
SAP_COM_0393	SAP Real Estate Contract API Integration
SAP_COM_0918	SAP Real Estate Master Data Event Integration
SAP_COM_0697	SAP Real Estate Master Data Integration
SAP_COM_0657	SAP Remittance Advices Integration
SAP_COM_0098	SAP S/4 HANA Extensibility Cockpit – Best Practices Explorer Integration
SAP_COM_0793	SAP S/4HANA Cloud for Credit Integration - Data Integration
SAP_COM_0826	SAP S/4HANA Cloud for Credit Integration - UI Integration
SAP_COM_0076	SAP S/4HANA Finance Cloud for Customer Payments Integration
SAP_COM_0887	SAP S/4HANA for Microsoft Teams - Contact Integration
SAP_COM_0A17	SAP S/4HANA for Microsoft Teams - Situation Notification Integration
SAP_COM_0A32	SAP S/4HANA for Microsoft Teams - Task Notification Integration
SAP_COM_0860	SAP S/4HANA for Microsoft Teams - UI Integration
SAP_COM_0930	SAP S/4HANA Migration Cockpit - Data Migration to BTP Integration
SAP_COM_0525	SAP S/4HANA Procurement Hub - Ariba Central Contract Management Integration
SAP_COM_0292	SAP S/4HANA Procurement Hub - Ariba GB - Hub to Ariba GB Integration
SAP_COM_0293	SAP S/4HANA Procurement Hub - Ariba GB - Hub to Subsidiary Integration
SAP_COM_0420	SAP S/4HANA Procurement Hub - Ariba GB - Subsidiary to Hub Integration
SAP_COM_0243	SAP S/4HANA Procurement Hub - Central Contract Management Integration
SAP_COM_0515	SAP S/4HANA Procurement Hub - Central Invoice Hub Integration (Obsolete)
SAP_COM_0516	SAP S/4HANA Procurement Hub - Central Invoice Satellite Integration
SAP_COM_0266	SAP S/4HANA Procurement Hub - Central Purchasing Inbound Integration
SAP_COM_0267	SAP S/4HANA Procurement Hub - Central Purchasing Outbound Integration.
SAP_COM_0736	SAP S/4HANA Procurement Hub - Central Request For Quotation Integration
SAP_COM_0512	SAP S/4HANA Procurement Hub - Central Sourcing Hub Integration
SAP_COM_0513	SAP S/4HANA Procurement Hub - Central Sourcing Satellite Integration
SAP_COM_0737	SAP S/4HANA Procurement Hub - Central Supplier Quotation Integration
SAP_COM_0673	SAP S/4HANA Procurement Hub - Centrally Managed PO with Supplier Integration
SAP_COM_0587	SAP S/4HANA Procurement Hub - Foundation Layer Hub Integration
SAP_COM_0586	SAP S/4HANA Procurement Hub - Foundation Layer Satellite Integration
SAP_COM_0090	SAP S/4HANA Procurement Hub Integration
SAP_COM_0672	SAP S/4HANA Procurement Hub-Central Purchase Contract with Supplier Integration
SAP_COM_0564	SAP Self-Billing Cockpit Integration
SAP_COM_0642	SAP Subscription Billing - API Integration
SAP_COM_0884	SAP Subscription Billing - Event Consumption Integration
SAP_COM_0845	SAP Subscription Billing - UI Integration
SAP_COM_0095	SAP Subscription Billing with Sales Billing Integration
SAP_COM_0686	SAP SuccessFactors Employee Central - UI Integration
SAP_COM_0A76	SAP Task Center - Task Consumption Integration
SAP_COM_0501	SAP Task Center Integration
SAP_COM_0922	SAP Treasury Management - Financial Transaction Integration
SAP_COM_0B26	SAP Treasury Management - Financial Transaction Integration
SAP_COM_0839	SAP Treasury Management - SAP Trading Platform Integration
SAP_COM_0226	SAP Treasury Management - SAP Trading Platform Integration (Deprecated)
SAP_COM_0954	SAP Treasury Management - Securities Master Data Integration
SAP_COM_0203	SAP Treasury Market Rate Integration
SAP_COM_0222	SAP Watch List Screening - Screening Hits Integration
SAP_COM_0219	SAP Watch List Screening - Screening Integration
SAP_COM_0013	SAP Web IDE Integration (Obsolete)
SAP_COM_0637	SAP Workflow Management Process Visibility Capability Integration
SAP_COM_0542	SAP Workflow Management Workflow Capability Integration
SAP_COM_0750	Security Audit Log Integration
SAP_COM_0961	Serial Number Management Integration
SAP_COM_0802	Service - Field Service Management UI Integration
SAP_COM_0717	Service - In-House Repair OData Integration
SAP_COM_0764	Service - Master Data Integration
SAP_COM_0933	Service - Repair Confirmation Integration
SAP_COM_0858	Service - Repair Confirmation SOAP Integration
SAP_COM_0742	Service - Repair Order Integration
SAP_COM_0677	Service - Repair Order SOAP Integration
SAP_COM_0744	Service - Repair Quotation Integration
SAP_COM_0687	Service - SAP Field Service Management - Direct Integration (P2P)
SAP_COM_0A50	Service - SAP FSM -CPI Based Integration
SAP_COM_0352	Service Confirmation OData Integration
SAP_COM_0423	Service Confirmation SOAP Integration
SAP_COM_0558	Service Contract OData Integration
SAP_COM_0789	Service Contract OData V4 Integration
SAP_COM_0436	Service Contract SOAP Integration
SAP_COM_0788	Service Contract Template Integration
SAP_COM_0A92	Service Document Settlement Rules Integration
SAP_COM_0146	Service Entry Sheet Integration
SAP_COM_0237	Service Entry Sheet Process Integration
SAP_COM_0350	Service Order OData Integration
SAP_COM_0424	Service Order SOAP Integration
SAP_COM_0715	Service Order Template Integration
SAP_COM_0355	Service Quotation Integration
SAP_COM_0530	Service Quotation Integration
SAP_COM_0831	SLT - CDS View Extraction Integration
SAP_COM_0026	Social Collaboration Integration
SAP_COM_0582	Software Assembly Integration
SAP_COM_0948	Software Component Management Integration
SAP_COM_0367	Sold-to Party Assignment of Sales Scheduling Agreement Integration
SAP_COM_0445	Sourcing and Procurement Scheduling Agreements With Suppliers Integration
SAP_COM_0224	Sourcing and Procurement with Suppliers Integration
SAP_COM_0A80	Stock Transport Order Integration
SAP_COM_0700	SuccessFactors Payment Options Check Integration
SAP_COM_0137	Supplier Activity Integration
SAP_COM_0138	Supplier Activity Task Integration
SAP_COM_0904	Supplier Confirmation Integration
SAP_COM_0827	Supplier Confirmation Process Integration
SAP_COM_0828	Supplier Confirmation Third-party Integration
SAP_COM_0139	Supplier Evaluation Response Integration
SAP_COM_0122	Supplier Evaluation Scorecard Integration
SAP_COM_0057	Supplier Invoice Integration
SAP_COM_0384	Supply Availability Protection Plan Integration
SAP_COM_0347	Support User Request Log Read Integration
SAP_COM_0664	Sustainability - Product Footprint Management Integration
SAP_COM_0883	Sustainability Data Exchange Integration
SAP_COM_0465	System for Cross-domain Identity Management Integration
YY1_TASK_CENTER_TEST	Task Center Test
SAP_COM_0620	Test Automation - Cloud ALM Integration
YY1_TESTCOMMUSER	Test for CFO Dashboard
SAP_COM_0253	Text Analysis - Purchasing (Deprecated)
SAP_COM_0850	Transportation Management - Advanced Shipping Notification Integration
SAP_COM_0756	Transportation Management - Freight Agreement Integration
SAP_COM_0906	Transportation Management - Freight Booking Integration
SAP_COM_0905	Transportation Management - Freight Order Integration
SAP_COM_0908	Transportation Management - Freight Unit Integration
SAP_COM_0813	Transportation Management - LSP Freight Booking Integration
SAP_COM_0534	Transportation Management - LSP Freight Order Integration
SAP_COM_0414	Transportation Management - Order-Based Transportation Consolidation Integration
SAP_COM_0767	Transportation Management - Rate Table Integration
SAP_COM_0660	UI Text Translation Adaptation Integration
SAP_COM_0086	UI Theme Designer Integration
SAP_COM_0623	UI Theme Designer Integration
SAP_COM_0929	Update Source for Project Demands Integration
SAP_COM_0537	Variant Configuration and Pricing Integration
SAP_COM_0323	Visual Business - GeoJSON Inbound Integration
SAP_COM_0A78	WalkMe Digital Adoption Platform - Outbound Integration
SAP_COM_0A65	Warehouse Management Control Cycle Integration
SAP_COM_0386	Warehousing - Attachment Service Integration
SAP_COM_0875	Warehousing - ERP Integration
SAP_COM_0385	Warehousing - Inbound Delivery Integration
SAP_COM_0374	Warehousing - Master Data Integration
SAP_COM_0378	Warehousing - Physical Inventory Integration
SAP_COM_0356	Warehousing - Process Outbound Delivery Order Integration
SAP_COM_0353	Warehousing - Process Warehouse Task Integration
SAP_COM_0755	Warehousing - Stock Integration
SAP_COM_0766	Warranty Claim Management Integration
SAP_COM_0632	Web Dynpro ABAP ALV for PDF Signing Integration (SAP_COM_0632)
SAP_COM_0914	Workforce Availability Integration
SAP_COM_0A35	Workforce Person OData Integration
SAP_COM_0027	Workforce Timesheet Integration
SAP_COM_0242	WSIL Integration

Gregor Wolf

2026-02-23T18:24:58.182000+01:00

About Gregor

Germany | SAP Mentor since 2007 | Follow Gregor on LinkedIn

I am an independent SAP solution architect, developer and SAP Mentor. I focus on SAP Business Technology Platform, SAP Cloud Application Programming Model (CAP), Node.JS, SAP Fiori Elements and Security. I've supported several customers during their SAP Cloud ERP Private Edition (S/4HANA On Premise) implementation. Since the end of 2024 I support the technical topics at an SAP Cloud ERP Public Edition Customer.

Topics of interest: SAP Business Technology Platform, SAP Cloud Application Programming Model (CAP), SAP Cloud ERP public and private, SAPUI5, OpenUI5, SAP Fiori, SAP HANA Cloud

Gregor, what inspired you to become an SAP Mentor?

A key influence early in my SAP Community journey was Mark Finnern. He is the father of the SAP Community. Mark encouraged me to move beyond answering questions and start sharing detailed technical how-to's but also event reports in blog posts. In 2007 Mark also founded the SAP Mentors program which gave me the opportunity to provide structured, experience-based feedback to SAP product teams and help bridge the gap between product vision and real-world implementation.

What advice would like to share with other SAP community members?

My advice to other SAP Community members is simple: contribute consistently and think long-term.

Start by answering questions and helping others solve real problems - but don’t stop there. Document your lessons learned, share architectural insights, and write about what worked and what didn’t. That’s how collective expertise grows. And you will be amazed how often you research years later and find your own answers and blog posts to solve a problem you're just facing. Despite all the new stuff SAP has quite a long tail that doesn't change quickly.

Engage constructively, challenge respectfully, and focus on signal over noise. The community is not just a support forum - it’s an ecosystem where practitioners can influence product direction, elevate standards, and shape the future of SAP together.

Communication Arrangements in SAP S/4 HANA Public Cloud

2026-02-24T07:04:51.057000+01:00

Communication Arrangements

Communication Arrangements is one of the Key User Extensibility Tools.

With Communication Arrangements App,

Communication Arrangements details can be viewed.
Custom Communication Arrangements can be created with standard communication or custom communication scenarios using Communication Arrangements App.

Finding the Standard Communication Scenarios in SAP Business Accelerator Hub

Navigate to SAP Business Accelerator Hub

Choose the Product

SAP S/4 HANA Cloud Public Edition

Navigate to APIs -> ODATA V2 / ODATA V4.

Search Required API

List of results for Purchase Order.

Purchase Order API Overview

API Resources

Navigate to API Resources -> Attributes -> Communication Scenario

API Specifications

Authentication Methods for API

Configuration Details for API

Extensibility

Custom Fields can be added to the API using below Business Contexts - Header and Items in Custom Fields App with Key User Extensibility.

API Reference

List of Entity Sets Available in the APIs.

Communication Scenarios

Navigate to Display Communication Scenarios,

All these are Standard Communication Scenarios.

Standard Communication Scenarios of Purchase Order - SAP_COM_0053

Steps to Create Communication Arrangements

Maintain Communication Users

Navigate to Maintain Communication Users App.

Maintain Communication Users is to create Communication Users for the API Access.

Choose New button to create Communication User

Add User Name and Password.

Propose Password can be chosen to generate password by system.

Save the Communication User.

If communication User is added to any Communication system or communication Arrangements, here it shows those details.

Communication System

Navigate to Communication System App.

Communication System is to maintain communication system with host name and communication User.

Provide Communication System ID and Name.

Add the Host Name

Add necessary details

Choose Add button to add Inbound Communication User.

Available Authentication Methods

Required details for SSL Client Certificate.

Required details for OAuth 2.0

Choose the Authentication Method, and choose User Name/Client ID.

Click on Ok after choosing Communication User.

Communication User is added.

Communication System is saved.

Communication Arrangements

Navigate to Communication Arrangements app.

Communication Arrangements is to generate Inbound Service URLs by adding Communication System and Communication User.

Choose New Option to create Custom Communication Arrangements.

Standard or Custom Communication Scenarios is required to create Custom Communication Arrangements.

Search for the Standard or Custom Communication Scenario

‘SAP_COM_0053’ is the Standard Communication Scenario for the Purchase Order API.

Arrangement appears automatically based on Communication Scenario and it can be changed.

Click on Create button to create Communication Arrangement.

List of Inbound Services available for that Communication Scenario.

WSDL/Service Metadata will be generated once Saved the Communication Arrangement.

Communication System and Communication User is required to create Communication Arrangements.

WSDL/Service Metadata is generated.

Service Metadata

Service URL is available in Communication Arrangement.

Access the Service URLs through the Communication User details.

Conclusion

standard communication or custom communication scenarios are used to create Communication Arrangements.

In Communication Arrangements, OData URLs are generated based on inbound Service.

References

"Getting Started: Maximizing Your Potential from the Start"

2026-02-24T14:30:26.950000+01:00

Overview of the three main content areas and how they support your development.

Discussions – Learn Together
Connect with peers to ask questions, share knowledge, and collaborate on learning. Our experts are available to provide guidance and answers if needed.
Blog – Stay Informed and Inspired
Stay informed on product developments, features, and certification paths with regular updates to enhance your skills.
Knowledge Base – Official Learning Updates
Central source for official announcements related to learning content, including new or updated Learning Journeys, certification changes, new course releases, and invitations to live sessions or expert-led trainings.

Tour the SAP Community - Explore the various features, functionality, and aspects of the SAP Community, familiarize yourself with community guidelines, and discover how to get the most out of your membership.

START Learning based on your proficiency level

Start with the Basics
Positioning SAP Business Suite - Begin with a general overview to understand the positioning and value of SAP Business Suite. This will give you a solid foundation before moving into specific topics.
Choose Your Line of Business
Next, focus on the area that interests you most. This helps you understand the solutions and processes within your chosen domain. For example:
- Positioning SAP Financial Management Solutions
- Positioning SAP Supply Chain Management Solutions
Deepen Your Knowledge
Continue with a specific Line of Business and deepen your expertise. For example:
Become an Expert
If you want to move towards implementation, explore product-focused learning offering such as:
- SAP Certified Associate - Implementation Consultant - SAP S/4HANA Cloud Public Edition
- SAP Certified Specialist - Implementation Consultant - SAP S/4HANA Cloud Private Edition

Recommended Communities

We invite you to become a member and subscribe to the communities below for in-depth discussions on Finance and Supply Chain Management::

Happy Learning 😊

Resolving Key Mapping Missing Issues while sending Freight Unit from Cloud ERP to On Premise system

2026-02-26T04:36:24.910000+01:00

Introduction

The process for Scope Item 6W1 for External Transportation Planning enables transportation requests created in SAP S/4HANA Cloud ERP to be planned within an SAP On Premise system. In this case, Freight units generated in SAP S/4HANA Cloud ERP can be transferred to the On Premise system (with SAP TM) for detailed transportation planning.

Once planning is completed, the results are sent back and integrated into SAP S/4HANA Cloud ERP in the form of freight orders. Upon transfer, transportation charges for these freight orders are calculated automatically. Based on the finalized freight orders, outbound deliveries can then be initiated.

This post covers the scenario where an error is received and the possible workaround for the error.

Kindly note that below steps are a workaround and steps must be taken to resolve error by undertaking the master data replication as per the set up guide.

Process Details

Complete the set up for the scenario including the set up of communication scenario and Data replication. The process requires the Purchase order be created within the SAP S/4HANA Cloud ERP. Ensure that the Purchase group is selected as "006" External TM Planning (refer below screenshot).

Based on settings a Transportation Management Freight unit is created. The same can be seen within the Purchase order app under the tab "TM Status"

As the Process needs the Freight Unit planning within the external TM system the scope items 6W1 in SAP S/4HANA Cloud ERP should be activated. Once done the Freight Unit from Public Cloud system is replicated to the On Premise system.

This replication message should create a Freight Unit within the On Premise / Decentralized TM system.

Challenge

In case of Failure of the FU replication, check the message within the SAP Message Monitor to identify the type of error. One of the error that can occur may relate to Invalid data. As you can see in the below screenshot the error related to invalid data.

This blog covers on the process to be followed to resolve this issue.

To resolve the issue, as you can see the below warnings need to be removed to resolve the error. These warning relate to incorrect / missing key mapping for different Master Data Objects like Location / Business Partner / Product between the Public Cloud and the On Premise system. This can happen in case the replication was not performed correctly.

Resolution

To resolve the issue, key mapping needs to be maintained in both the Public Cloud and the On Premise system.

You can follow the following steps for the same.

Use the Tcode MDG_KM_MAINTAIN within the On Premise SAP system. Manage Key Mapping UI opens.

For each of the impacted Business Object Type (as per the error) select the Object Type (example Business Partner in above screenshot) and Object Type ID, Business System and the Master Data ID (example Business partner ID).
Click on Add Row to add the entries as below. Fill in the details such that there are 2 rows each of Public cloud and On Premise system
1. Row 1 with Public Cloud System ID and BP number and Row 2 for BP UUID in the standard format: 8-4-4-4-12 (hexadecimal groupings). Example – If location UUID is 355F4B6A67ED1EEE9297A3E7521BF064 it should be mentioned as 355F4B6A-67ED-1EEE-9297-A3E7521BF064
2. Repeat the same for the On Premise system with corresponding details added in row 3 & 4.

Save
Repeat the same process from steps 1 to 4 for all other Master data objects as per the error.
Repeat the same process from steps 1 to 5 within the Public Cloud system using the app „Manage Key Mapping“.

Rerun the process of FU replication and mapping error should be resolved now.

Automated Invoice and Credit Memo Processing Using ERS in SAP S/4HANA Public Cloud

2026-02-26T08:37:53.774000+01:00

Automated Invoice and Credit Memo Processing Using ERS in SAP S/4HANA Public Cloud

Introduction

In a standard procurement process, materials are procured from a supplier through purchase order creation, goods receipt posting, invoice processing, and vendor payment. When Evaluated Receipt Settlement (ERS) is activated, the system automatically creates the supplier invoice based on the goods receipt, eliminating the need for manual invoice posting.

During one of the SAP S/4HANA Public Cloud implementations, a requirement came up to handle supplier return scenarios using ERS. In cases where materials were found defective after receipt and payment, the business expected the system to automatically generate a credit memo once the returned goods were posted. This blog explains the end-to-end process that was configured and tested in SAP S/4HANA Public Cloud to achieve this automation.

Step 1: Maintain Business Partner Master Data

Use the Manage Business Partner Master Data app.

Ensure the following fields are enabled for the Supplier in the Purchasing tab:

Automatic Evaluated Receipt Settlement
Evaluated Receipt Settlement
Goods Receipt-Based Invoice Verification

These settings allow the system to generate invoices and credit memos automatically without manual invoice posting.

Step 1: Image 1

Step 2: Schedule ERS Background Job

Use the app: Schedule Supplier Invoice Jobs – Advanced

Step 2: Image 1

Select the job template: Evaluated Receipt Settlement

This job automatically:

Creates Supplier Invoices for GR
Creates Credit Memos for Returns

I have created scheduled background jobs for ERS using this app.

Step 2: Image 2

Step 2: Image 3

Step 2: Image 4

Step 2: Image 5

Step 3: Create Standard Purchase Order (ERS Enabled)

Create a standard PO.

Ensure:

ERS checkbox is automatically enabled in the Invoice tab.

Step 3: Image 1

Post Goods Receipt (GRN).

Once the scheduled ERS job runs: System automatically generates the Supplier Invoice document. The below image shows the PO history reflecting the automatically created invoice document.

Step 3: Image 2

In the Schedule Supplier Invoice Jobs – Advanced app, the below image shows the scheduled job that automatically generated the supplier invoice based on the ERS configuration.

Step 3: Image 3

Step 3: Image 4

Note: In SAP S/4HANA Cloud (Public Edition), the classic GUI transaction MRRL used for Evaluated Receipt Settlement is not available. Instead, ERS processing is executed through the Schedule Supplier Invoice Jobs - Advanced app.

Step 4: Vendor Payment

Based on the automatically generated invoice:

Vendor payment is processed and cleared using standard payment process.

Return Process Using ERS

Step 5: Create Return Purchase Order

When defective material needs to be returned:

Create PO with Return Indicator
Ensure ERS is enabled in the PO

Step 5: Image 1

Step 6: Post Return Goods Receipt

Post Goods Receipt for the Return PO.

Once the scheduled ERS job runs:

System automatically generates a Credit Memo
No manual invoice posting required
Liability is adjusted automatically

Step 6: Image 1

In the Schedule Supplier Invoice Jobs – Advanced app, the below image shows the scheduled job that automatically generated the credit memo for the supplier return process based on the ERS configuration.

Step 6: Image 2

Step 6: Image 3

Conclusion

In my experience, ERS in SAP S/4HANA Public Cloud works smoothly not only for regular procurement but also for supplier return scenarios, provided the configuration is done correctly. Once the supplier master is properly maintained and the background job is scheduled, the system automatically takes care of invoice generation for goods receipts and credit memo creation for returns.

The key is to ensure that ERS is consistently enabled in both the standard and return purchase orders. When everything is aligned, the process runs without manual intervention, reducing effort for the finance team and avoiding posting errors. This makes the overall P2P cycle more controlled and efficient.

S/4HANA Public Cloud: How to Retrieve Print Queue PDFs via OData API

2026-02-26T08:47:18.937000+01:00

Introduction

When building side-by-side extensions or integrating external applications with SAP S/4HANA Cloud Public Edition, a common requirement is to retrieve generated PDF documents (like Invoices or Purchase Orders) programmatically.SAP provides a dedicated standard pattern: The Print Queue API (SAP_COM_0466).
Overview | Print Queue Item - Read (A2X) | SAP Business Accelerator Hub

Step 1: Communication Setup

First, you need to expose the API through a Communication Arrangement.

Create a Communication User: Set up a technical user and password in the Maintain Communication Users app.

ex. SHU_TEST_UESR
Activate the Arrangement: Create a new arrangement for scenario SAP_COM_0466 (Printing - Pull Integration).

Important: Ensure the arrangement is saved and its status is Active. API permissions will not trigger if it remains in "Draft" mode.

Step 2: Print Queue Configuration (The Secret Sauce)

This is where most developers get stuck. Even with an active API, the service will return empty results unless the Print Queue is explicitly configured to allow your technical user.

Open the Maintain Print Queues app.
Create a New Queue: Do not use the DEFAULT queue, as it often has restricted permissions. Create a custom one (e.g., Z_PULL_TEST).
Assign the User: Inside the queue settings, navigate to the Assigned Users section and add your Communication User.

Without this assignment, the API will return a 200 OK but with zero data, as the user doesn't have "permission to see" the contents of that specific vault.

Step 3: Retrieving the PDF via API

The service API_CLOUD_PRINT_PULL_SRV uses Function Imports. You must follow a specific sequence of calls using Basic Authentication.

1. Verify Connectivity

Check which queues your user can access:

GET

.../sap/opu/odata/sap/API_CLOUD_PRINT_PULL_SRV/Get_PrintQueuesOfUser

2. Fetch the Item ID

Retrieve the ID for the next available document in the queue:

GET

.../RetrieveNextQueueItem?Qname='Z_EXTERNAL_PULL'&Language='EN'

Copy the item_id from the XML response (e.g., FA163ECE...).

3. Download the PDF Content

Use the Item ID to pull the Base64 encoded binary data:

GET

.../Get_QItem_Document?attachments=false&main_doc=true&item_id='YOUR_ITEM_ID'&qname='Z_EXTERNAL_PULL'

Step 4: Handling the Result

The response will contain a <d:Blob> tag. This is a Base64 encoded string of the PDF. To view the content, you simply need to decode this string in your application logic (or use a tool like Postman’s Visualizer).

<d:Blob>JVBERi0xLj... (Long Base64 String)</d:Blob>

Pro Tip: Once downloaded, it is best practice to call the Set_QItem_Status function to mark the document as "Printed" or "Successful" so it is removed from the pending pull list.

Conclusion

By shifting from the internal Output Management service to the Print Queue Pull API (SAP_COM_0466), you can reliably and securely automate document retrieval from S/4HANA Cloud. The key takeaways are ensuring the Active status of your Communication Arrangement and the explicit Assignment of the User to the custom Print Queue.

Happy coding!
Shusei Sekiya

Workflow for Sales quotations and Sales Orders triggered when the end user changes the Item Price

2026-02-26T09:20:13.530000+01:00

This requirement is to be implemented in the SAP S/4HANA Public Cloud system.

To trigger a workflow in the Sales Quotation and Sales Order applications, a condition must be checked for the item price. The workflow should be triggered only if the item price has been changed by the end user. To achieve this, a sales quotation or sales order simulation needs to be executed to determine the system-calculated item price. This value must then be compared with the price entered or modified by the user. If a difference is identified, the workflow should be triggered accordingly.

The main challenge is retrieving the item price within the custom logic. However, this can be addressed by calling the Sales Order Simulation API, which provides the calculated item price for comparison.

Pre-requisties :

Required Business Roles must be assigned to the user.
Workflows for Sales Orders must be configured and activated in the system. Refer SAP Help on flexible workflow setup. https://help.sap.com/docs/SAP_S4HANA_CLOUD/a376cd9ea00d476b96f18dea1247e6a5/5a5f3f686c06490893a588c99b36adca.html

Solution:

When sales quotation and sales order created/changed in S/4 system then the Business Add-In (BAdI) SD_APM_SET_APPROVAL_REASON is provided to specify whether a sales document is relevant for approvals or not. Refer below documentation for this BADI. https://api.sap.com/badi/SD_APM_SET_APPROVAL_REASON

In this Blog, Sales order is used for reference to explain the use case.

Communication Setup:

In order to execute API for simulation of the creation of sales order inside Cloud Badi implementation (SD_APM_SET_APPROVAL_REASON), required communcation arrangement to be setup for the Communication Scenario SAP_COM_0109 (Sales Order Integration) to technically enable and activate the Sales Order simulation API - 'API_SALESORDERSIMULATION'. Refer API Hub for detail : https://api.sap.com/api/sap-s4-CE_SALESORDERSIMULATION_0001-v1/overview
Refer SAP Help for guidance on setting up the communication arrangement, system and communication user. https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/2e84a10c430645a88bdbfaaa23ac9ff7.html
After setup of communication arrangement, we will have the Sales Order Simulation API endpoint to be used inside Custom BADI.
Since, the Sales order simulation API to be called within the S/4 system itself, so custom communcation scenario to be setup to enable the call of inbound APIs inside Cloud Badi. In custom communcation scenario, generic outbound service for REST type to be added. Communication arrangement to be created for this custom communication scenario to activate HTTP service with same outbound user as was used in step 1(setup of standard communcation scenrio). Refer SAP Help document for additional details. https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/8d5d71252edd449982083cb5a3b8c8c4-182.html
After completing the above steps, custom communication scenario, outbound service and Sales order simulation API is ready to be used inside implementaton of cloud BADI SD_APM_SET_APPROVAL_REASON."

Cloud BADI implementation

Create Implementation of Cloud BADI 'SD_APM_SET_APPROVAL_REASON' via Custom Logic app (Key User Extensibility).
Add required checks based on importing parameters - SALESDOCUMENT(Sales Document for Approvals) and SALESDOCUMENTITEM (Sales Document Item Table for Approvals). For instance : type of order, sales origanzation, sales document categoty.
Configuration check of communication arrangment, service activation and API Call request-response.

Check if outbound service exists in the communication scenario.

CHECK cl_ble_http_client=>is_service_available(
communication_scenario = 'YY1_COMM_SCENARIO'
outbound_service = 'YY1_COMM_OUTBOUND_REST'
) = abap_true.

Creation of the HTTP client to access the outbound service
DATA(lo_client) = cl_ble_http_client=>create(
communication_scenario = 'YY1_COMM_SCENARIO'
outbound_service = 'YY1_COMM_OUTBOUND_REST'
).
Creation of service request and set properties
*method used for service call
lo_request = cl_ble_http_request=>create( ).
lo_request->set_header_parameter( EXPORTING name = 'x-csrf-token' value = lv_csrf ).
lo_request->set_content_type( 'application/json' ).

* Post method to execute Sales Order Simulation API. URL here is endpoint ('/api_salesordersimulation/srvd_a2x/sap/salesordersimulation/0001/SalesOrder' )
lo_request->set_method( 'POST' )->set_resource_extension( lv_url ).

* Payload in JSON to be created for passing Sales order header data from SALESDOCUMENT and item data from SALESDOCUMENTITEM.

Sample Payload :

{

"SalesOrderType": "TA",

"SalesOrganization": "XXXX",

"DistributionChannel": "10",

"OrganizationDivision": "10",

"SoldToParty": "XXXXXXXXX",

"_Item": [

{

"Product": "XXXX",

"RequestedQuantity": 1,

"RequestedQuantityISOUnit" : "PCE"

{

"Product": "XXXX",

"RequestedQuantity": 2,

"RequestedQuantityISOUnit" : "PCE"}

] }

Call the request by passing Payload created and get the response.
lo_request->set_body( lv_payload ).
* ***Send API request
lo_response = lo_client->send( lo_request ).
***Getting response body from response received
DATA(lv_body) = lo_response->get_body( ).
From the API response, the value of 'TotalNetAmount' needs to be retrieved.
The standard class method /ui2/cl_json=>deserialize should be used by passing the response body as input and extracting the value of 'TotalNetAmount' from the resulting structure.

Note: The custom wrapper class is created in ADT(Developer extensbility) to be called inside Cloud logic. This customer class used standard method /ui2/cl_json->deserialize_json to extract the attribute value of 'TotalNetAmount'.

/ui2/cl_json->deserialize_json(EXPORTING
im_payload = lv_body
IMPORTING
ex_total_val = DATA(lv_field_amt) ).

Compare the TotalNetAmount entered by the user during Sales Order creation (importing parameter: salesdocument-totalnetamount) with the Total Net Amount retrieved from the API response. If there is a difference, set the changing parameter SALESDOCAPPROVALREASON accordingly.

Conclusion : Additional specific complex conditions can be determined inside custom logic to check if Sales order workflow to be triggered or not. For instance, POST operation(simlulation mode) for released API's can be called to validate conditions inside Custom Logic(Key user extensibility) in S/4 HANA Public Cloud System.

Preliminary What’s New Information for SAP S/4HANA Cloud Public Edition 2602.1

2026-02-26T12:04:44.115000+01:00

Preliminary version of What’s New information and of the Product Assistance are now available for customers and partners to get a preview on the upcoming new and changed features of SAP S/4HANA Cloud Public Edition 2602.1.

You can find this preview on the current SAP Help Portal page SAP S/4HANA Cloud Public Edition (see What’s New section “Preview of SAP S/4HANA Cloud Public Edition 2602.1”). To access the Preliminary What’s New information, please use the What’s New Viewer or the Release Assessment and Scope Dependency (RASD) tool.

The 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 preliminary information for SAP S/4HANA Cloud Public Edition 2602.1 will be available in RASD within the next few days. We recommend using RASD to prepare for upgrades and updates of your system and to focus on the new and changed features that are relevant for you. A valid S-User ID is needed to use the RASD tool and to view all the preliminary content stated above.

For any feedback you may have, try the Commenting Feature for What's New documentation in this release. See this blog for more information.

ABAP Cloud Learning Map

2026-02-27T15:38:25.525000+01:00

The ABAP Cloud development model (ABAP Cloud) is the foundation of ABAP-based development at SAP, its partners, and customers, designed from the ground up to adhere to clean core principles. It brings together evolving technologies and methodologies into a sustainable, long-lasting programming model.

The ABAP Cloud development model encompasses all aspects of modern cloud-ready software development, resulting in a wide range of topics that need to be understood. Therefore, clear guidance is helpful for getting started with and navigating ABAP Cloud.

Discover the ABAP Cloud Learning Map🗺️ – your guide to mastering the ABAP Cloud development model. It provides an overview of essential topics and skills, along with a curated collection of links to key resources covering the technologies, tools, approaches, and practices that drive cloud-ready, upgrade-stable ABAP development. 📚Whether you’re starting out or filling knowledge gaps, the learning map helps you navigate modern ABAP Cloud development at your own pace.

🔗Access it here: ABAP Cloud Learning Map↗

Where ORD Is Used in SAP Datasphere, SAP Business Data Cloud & SAP Databricks

2026-03-01T15:42:55.629000+01:00

SAP Open Resource Discovery (ORD) is becoming a foundational standard across the SAP ecosystem because it provides a consistent, self‑describing metadata layer for APIs, events, business objects, and data products. This metadata standardization is what enables smooth interoperability across SAP’s modern data and integration platforms.

Below are the key places where ORD is used today — and how it empowers seamless integration, especially with SAP Datasphere, SAP Business Data Cloud, and SAP Databricks.

1. SAP Business Accelerator Hub (api.sap.com)

SAP Business Accelerator Hub uses ORD as one of the primary mechanisms for publishing APIs and events. Any API showing an ORD ID on its overview page is officially ORD-enabled, meaning it exposes standardized metadata that can be consumed by SAP tools and data platforms.

This ensures:

Consistent API descriptions
Discoverability by SAP’s central aggregators
Compatibility with downstream systems like SAP Business Data Cloud

This is the first indicator that an API can participate in the broader data product ecosystem.

2. SAP Business Technology Platform (BTP)

SAP uses ORD internally to improve SAP-to-SAP integration and provide a unified metadata layer that development tools (like SAP Business Application Studio) can consume for enhanced API discovery and automation.

Each Product Owner from SAP Products LoB will be develop, design ORD to make it available in SAP Business Accelerator Hub (api.sap.com) and Data Products Marketplace for you..

3. SAP Business Data Cloud (BDC)

SAP Business Data Cloud actively uses ORD to describe Data Products and make them discoverable to consumers across the SAP ecosystem, including SAP Datasphere. ORD helps BDC deliver a unified catalog with:

Descriptions of datasets
Relationships
Capabilities
Higher-level metadata structures like data products and business entities

In addition, third‑party systems such as SAP Databricks are required to describe data products using ORD before publishing them into SAP Business Data Cloud.

This ensures smooth catalog integration and consistent metadata across SAP and non-SAP data sources.

4. SAP Datasphere

SAP Datasphere consumes data products published to SAP Business Data Cloud — and because BDC requires ORD‑based metadata, Datasphere gains:

Automatically discoverable data products
Standardized metadata for modeling
Compatibility with external data such as Databricks Delta Lake

Datasphere uses ORD indirectly because it relies on BDC’s ORD-driven catalog for understanding and federating data assets.

Additionally, SAP’s hybrid integration patterns show that Datasphere can integrate with Databricks using JDBC or federated models — and ORD ensures data products between these systems are consistently described.

5. SAP Databricks (Enterprise Databricks Integration)

SAP Databricks integrates deeply with SAP Business Data Cloud using BDC Connect, enabling bi-directional sharing of data products. To publish a data product from SAP Databricks to SAP Business Data Cloud:

The metadata must be described using ORD and CSN (Core Schema Notation)
The data product becomes discoverable to SAP systems (e.g., Datasphere) via BDC

Furthermore, Databricks–SAP integration uses Delta Share, JDBC, and federated models, but ORD plays the critical role of standardizing data product metadata.

This creates a smooth, unified integration path:

SAP applications → ORD-based metadata → Business Data Cloud → Datasphere & Databricks

SAP Architecture Center also confirms this hybrid pattern where business data from SAP and non‑SAP (Databricks) is harmonized through Business Data Cloud and Datasphere, enabling interoperable AI/ML and analytics scenarios.

Refer my SAP blog

6. Data Products Across the SAP Ecosystem

ORD also provides standardized metadata for:

Entity Types / Business Objects
APIs and Events
Data Products

This consistency is the key enabler for cross‑platform interoperability — especially as Data Products become central to the SAP ecosystem via Business Data Cloud and Datasphere.

Summary: How ORD Enables Smooth Integration Across SAP & Databricks

With ORD in place:

APIs with an ORD ID on api.sap.com can be safely consumed to build data products in SAP Business Data Cloud.
Business Data Cloud uses ORD metadata to catalog and serve data products to SAP Datasphere and SAP Databricks.
SAP Databricks uses ORD when publishing its own data products back into Business Data Cloud.
SAP Datasphere leverages ORD-driven metadata to discover, model, and federate data products seamlessly.

ORD is the metadata “glue” that ensures smooth integration across:

SAP BTP → Business Accelerator Hub → Business Data Cloud → Datasphere → Databricks

And the more SAP and partner solutions adopt ORD, the smoother, more automated, and more scalable integrations become across the SAP landscape.

Maintain Form Templates in SAP S/4 HANA Public Cloud

2026-03-02T07:37:53.587000+01:00

Introduction

Maintain Form Templates can be used to create Custom Form Templates using standard templates in SAP S.4 HANA Public Cloud with Key User Extensibility.

Maintain Form Templates is a tile to create new Custom Form Templates in SAP S/4 HANA Public Cloud.

Maintain Form Templates in SAP S/4 HANA Public Cloud

Maintain Form Templates App views a list of all available form templates and filter the templates by their assigned languages or countries
With this, create a new custom form template with one original language and the option to translate it to different target languages
Copy an SAP-predelivered template to custom form templates for the next editing and reuse
Delete custom form templates that are no longer needed
Access older versions of the custom template, download them and compare two versions at object level
Custom fields can also be added to the Custom form templates and values can be mapped using custom logic.

Navigate to Maintain Form Templates App

Predelivered Templates

Choose filters to filter the templates with required templates.

This is the Predelivered template of Purchase Order

Choose Download to edit this template in Adobe Life Cycle Designer

These are the files of the form template.

Custom Templates

For the development of custom form templates, the form template file (XDP) can be downloaded to edit it with the Adobe LiveCycle Designer and upload it as custom template in the original language.

Choose New to create custom template.

Provide the Custom Template name, choose the downloaded file as template file,

choose Dats Source same as Purchase Order template Data Source and

Form Type as Content.

Custom form Template

Save the Custom Form Template

Download the Custom Form Template file to make the necessary changes and re-upload it.

Downloaded files of the Custom Form template.

Adobe LifeCycle Designer for SAP Solutions

Open Adobe LifeCycle Designer to edit the custom form

Choose the form

This is the standard form template, and this can be changeable.

Re upload the custom form after making necessary changes.

Choose Custom Form Template

Custom Form Template has been uploaded.

Assign Form Templates

Assign the custom form templates

Navigate to Assign Form Templates

Maintain an entry for the Custom Form Templates

Maintain the entry for the custom Form Templates as same as standard templates.

Choose new entries.

Custom form template has been maintained.

Output Parameter Determination

Maintain custom form template in output parameter determination

Navigate to Output Parameter Determination

Choose Purchase Order

Choose Form Template as determination

Add a entry or edit the existing entries for custom form templates.

Choose Output type as Purchase Order

Choose Channel as Print

Choose Sender as IN

Add custom form template name in form template

Check and activate the changes.

Testing Form Templates

Navigate to create purchase order and check the forms generated.

Custom form template is triggered.

This is the custom form template

Conclusion

In SAP S/4 HANA Public Cloud, Custom Form templates with specific document types can be created using standard form templates in Maintain form Template app.

Those Custom Form template can be download and modify the form design in Adobe Life Cycle designer and same can be uploaded to that form.

These Custom Form Template can be configured in Output Parameter determination for respective business process.

References

On-Stack Partner Reference App: A Guide to Clean-Core Extensions in SAP S/4HANA Cloud Public Edition

2026-03-02T14:06:51.614000+01:00

As SAP partners and customers continue to innovate in the SAP cloud ERP space, one principle remains non-negotiable: keep the core clean. While SAP’s extensibility guidelines often favor side-by-side builds on the SAP Business Technology Platform (SAP BTP), some scenarios require tighter, real-time integration with core processes. For these tightly coupled cases, on-stack extensibility within SAP S/4HANA Cloud Public Edition provides the essential solution. It offers a powerful way to enhance standard business processes—without modifying SAP-delivered code—enabling end users to innovate securely and at scale.

To bridge theory and practice, the On-Stack Partner Reference Application provides a practical blueprint for building these clean-core extensions. Using modern ABAP and RAP principles, it demonstrates how to extend standard SAP applications in a secure, upgrade-stable, and scalable way, fully aligned with SAP guidelines.

When to Choose On-Stack Extensibility

While a side-by-side architecture on SAP Business Technology Platform is a powerful approach, it isn’t the ideal fit for every business need. Sometimes, an extension must be tightly woven into the main system to deliver the best results. On-stack extensibility is the recommended path for these tightly coupled scenarios, especially when your solution requires:

Deep integration with standard business processes
Seamless navigation across SAP Fiori applications
A harmonized user experience
Enhancements that are upgrade-safe within the same system

On-stack extensibility allows developers and organizations to achieve these goals by building directly within the SAP S/4HANA Cloud stack. This approach preserves the clean-core architecture, ensuring the system remains stable and maintainable. The Partner Reference Application demonstrates the recommended “golden path” for achieving this perfect balance.

The Reference Scenario: Loyalty Hub

When on-stack extensibility is the right approach, the On-Stack Partner Reference Application provides a hands-on example that demonstrates how to extend standard SAP processes securely and efficiently. It goes beyond theory to present a full end-to-end scenario that partners can explore, adapt, and use as a practical blueprint.

The scenario uses a Loyalty Hub application integrated with the standard Manage Sales Orders – Version 2 SAP Fiori application. Its goal is to help organizations manage customer loyalty programs directly within sales operations, while preserving seamless navigation between standard SAP functionality and the custom extension.

To make the scenario concrete, we demonstrate the application using two personas:

Aarti, the loyalty administrator, manages memberships, awards loyalty points, and issues gift cards
Julia, the sold-to party or customer, earns points, redeems rewards, and applies gift cards during sales transactions

This approach highlights both administrative and customer perspectives, showing how Loyalty Hub supports real-world workflows and interactions. Here’s how the Loyalty Hub works from both the administrative and customer perspectives:

Key Capabilities

The application delivers comprehensive loyalty management:

Handles memberships, tiers, and related transactions
Tracks and awards loyalty points automatically in response to sales order events
Issues and redeems gift cards tied to customer orders
Sends automated notifications for points updates and tier changes
Supports both administrator workflows and end-user interactions

Technical and Operational Design

Built with ABAP RAP and custom business objects in the Z namespace
Data modeled using CDS, ensuring separation from standard SAP objects and upgrade stability
User interfaces designed with SAP Fiori elements, supporting flexible extensions and semantic navigation
SAP-standard authentication and role-based authorization for secure access
Operational readiness includes scheduled jobs for membership evaluation, number range handling for controlled object creation, and application logging/messaging for monitoring and troubleshooting

This scenario illustrates how partners can innovate within the SAP S/4HANA Cloud stack, extending functionality while preserving clean-core principles, upgrade safety, and a consistent SAP user experience — all while reflecting both administrative and customer perspectives.

Key Business Value

The reference application helps your organization accelerate development while staying fully compliant with clean-core principles. By using it as a guide, your teams can:

Gain a reference architecture aligned with SAP standards.
Use proven patterns to integrate with standard applications.
Learn to build reusable and deployable solutions.
Accelerate the delivery of robust and upgrade-safe extensions.

The Loyalty Hub demonstrates that innovation and compliance can coexist—adding real business value without compromising the SAP clean core. The best way to understand the power of this approach is to see it in action.

You can get started and try the Loyalty Hub example by accessing the complete reference application on GitHub. By following this framework, you can confidently deliver the innovative, compliant, and upgrade-safe solutions your business requires.

On Stack Partner Reference Extension for SAP S/4HANA Cloud Public Edition

Explore Other Reference Applications

Depending on your extensibility strategy, you can also explore:

Together, these resources guide developers and architects across on-stack, side-by-side, and cross-stack extension patterns—helping them choose the right architecture while staying aligned with SAP’s clean-core and cloud-first principles.

SAP Fiori for SAP S/4HANA Cloud：增强版 New User Experience Switch 全面解析

2026-03-03T07:45:30.472000+01:00

在 SAP S/4HANA Cloud Public Edition 中，SAP 持续推进用户体验（UX）的革新，其中 New User Experience Switch（新版用户体验切换功能） 是帮助企业顺利完成应用替换的重要机制。最新版本（2602）对该功能进行了进一步增强，让业务用户与管理员更容易适应新旧应用的切换进程。

本文将带你了解这个增强功能的核心设计、工作方式，以及企业在实际使用中可以获得的价值。

一、为什么需要 New User Experience Switch？

SAP S/4HANA Cloud Public Edition 每 6 个月发布一次新版本，其中会逐步引入新应用（phase-in），同时也可能逐步淘汰旧应用（phase-out）。通常，业务用户有 至少 12 个月 的窗口期来适应新的替代应用，但在实际项目中，这段时间可能转瞬即逝。

为避免用户错过迁移时机，SAP 引入 New User Experience Switch，通过界面提示与切换选项来“温和推动”用户尝试并过渡到新应用。

二、New User Experience Switch 的三种提示阶段

切换功能在应用生命周期的不同阶段会呈现不同的提示样式：

1. Information 信息阶段

告诉用户有新的应用版本正在被引入
展示新应用的优势
鼓励用户尝试
用户可以随时切回旧应用

这是“最温和”的阶段，旨在减少用户对改变的抵触情绪。

2. Warning 警告阶段

当旧应用已经被标记为 deprecated（即将淘汰） 时，切换功能会显示黄色的警告信息：

告知旧应用将在未来版本中不再提供
提醒用户尽快完成迁移

3. Alert 紧急阶段

这是旧应用被移除前的最后一个版本，切换功能会以更醒目的方式提示：

强调迁移的紧迫性
显示明确的移除时间点

在这个阶段，如果用户仍然停留在旧应用上，会面临无法继续使用的风险。

三、切换功能如何呈现？

SAP 在 2502 版本引入 New User Experience Switch，在 2508 与 2602 的版本中进一步增强：

旧应用启动时出现提示 popover（气泡提示）
Shell Bar（顶端工具栏）中出现 切换按钮
用户可在新旧应用之间自由切换（取决于阶段）

这些交互方式让用户无需离开当前体验即可了解版本状态并快速做出选择。

四、对业务用户意味着什么？

✔ 更轻松的学习曲线

不再需要由管理员单独告知新旧应用替代关系，系统会自动提示。

✔ 提前感知变化

避免新版本发布后突然发现旧应用“消失”，有效减少工作中断。

✔ 自主试用新应用

在 phase-in 阶段，用户可以自由在新旧体验中切换，加速熟悉度提升。

五、对管理员意味着什么？

管理员可以利用此功能：

提前规划应用替换节奏
知道哪些用户仍在使用旧应用
在企业层面推动统一迁移

这让应用治理更加可控，也能减少升级周期带来的沟通成本。

六、为什么说这个功能“让改变更容易”？

New User Experience Switch 正是帮助企业完成改变的机制：

让改变更加可见
让迁移更加自主
让用户更有掌控感

对于每一个正在推进数字化、云化的企业来说，这种设计都能有效降低内部阻力。

结语：更智慧、更温和的用户体验演进机制

New User Experience Switch 的增强不仅让用户更轻松地迈向 SAP Fiori 的现代化体验，也让管理员和企业能够更从容、可控地管理应用生命周期。

随着 SAP 持续对 UX 的改进（例如 2602 版本中的 AI 辅助、增强的 Launchpad、手机端优化等），未来企业的 SAP 使用体验将更加智能、一致、顺滑。

如果你正在规划 S/4HANA Cloud 的上云旅程或准备迎接新版本，这项功能值得你重点关注。

参考文档：SAP Fiori for SAP S/4HANA Cloud – New User Experie... - SAP Community

SAP Enterprise Support Academy Newsletter March 2026

2026-03-03T11:40:05.538000+01:00

Dear customers,
Find here a preview of the SAP Enterprise Support Academy monthly newsletter on latest news, training courses, upcoming sessions, and further educational offerings.
The SAP Enterprise Support Academy provides expert guidance and high impact knowledge transfer services that enable you to innovate and be successful with your SAP solutions.

Subscribe to regularly receive latest news and stay informed about the wide range of educational offerings provided by the SAP Enterprise Support Academy that help you to build the digital skills tailored to your needs.

Getting Started with the New SAP Concur Travel for business users

Discover how the new SAP Concur Travel makes planning and booking work trips easier while helping you stay aligned with your company’s travel program. In just a short read, see what’s changing, how it supports your travelers, and how to get enabled along the way.

Full blog

Ready to Upgrade SAP S/4HANA Cloud Private Edition?

Don’t let myths hold you back! Many teams hesitate to upgrade SAP S/4HANA Cloud Private Edition due to common misconceptions—like being "too many releases behind" or fearing major disruptions. But what if upgrades could be seamless, strategic, and even empower your business?

Learn more

Meet our experts from SAP Enterprise Support to get updates

Join our session on March 25 to meet our experts from SAP Enterprise Support Academy and SAP Enterprise Support Advisory program. Get latest insights about the move to learning.sap.com and learning highlights and hear which workstream the ESAC innovation program offers in Q1.

Stay tuned and join on You Tube

See how SAP is transforming Ariba into an AI‑native source‑to‑pay platform

SAP is reimagining Ariba as an AI‑native, modern source‑to‑pay platform designed to simplify daily work, improve decision-making, and streamline procurement-to-pay processes. Read the blog to see practical examples, product highlights, and what these changes mean for faster cycle times, stronger cost control, and lower risk across your organization.

Read the full blog

New SAP for Me Services & Support dashboard-now live

We’ve launched a redesigned, user‑centric Services & Support overview tab to make support faster and easier. Enjoy a prominent search, actionable cards for Manage Cases, Quick Access (CIC), service requests and recommendations, unified case management, and simplified navigation — all designed to speed resolutions, boost self‑service, and improve outcomes.

Explore the new dashboard and share your feedback

Heads up for the intelligent front door-one digital experience in SAP for Me

SAP’s new unified entry point in SAP for Me will bring conversational and agentic AI to your fingertips. Discover how effortless navigation, advanced self-service, personalized guidance, and lightning-fast task execution will simplify daily workflows and speed decision-making across your SAP landscape.

Stay tuned for the launch in May. More details: Intelligent Front Door - Info sheet

Introducing CQC Security Optimization for SAP SuccessFactors-Now in pilot!

Protecting the security and availability of your SAP SuccessFactors environment is vital to keeping your business running smoothly. With the CQC Security Optimization service, you gain proactive analysis and insights to help prevent critical issues before they arise.

Learn more

Your starting point for practical SAP enablement

SAP Enterprise Support Academy is now on learning.sap.com, bringing together hands-on learning, expert guidance, practical resources, and expert-led live sessions that sessions that support you, so you can move from planning to action more quickly.

Learn more here

ALM Summit NA - April 14-16 in Newtown Square-March

The landscape of Application Lifecycle Management is transforming, and you can witness this evolution firsthand at the SAP ALM Summit North America 2026.

Dates: April 14–16, 2026
Location: SAP US Headquarters, Newtown Square, PA

Customer Success Through Trusted Partner Support Expertise

SAP Cloud customers rely on implementation and operations services from SAP’s partner ecosystem, where an effective support collaboration between partner and SAP is essential for Customer Success. To unlock incremental value, such as faster issue resolution and risk mitigation, customers are encouraged to select and manage partners also based on support quality.

Read the article and learn more

Embedded Launch Activities: Expanding the Customer Onboarding Journey

2026-03-03T15:58:30.138000+01:00

Embedded Launch Activities: Expanding the Customer Onboarding Journey

From March 2 onwards, SAP expands Embedded Launch Activities with an enhanced onboarding experience designed to accelerate time to value from contract start and enable implementation teams to engage hands-on with the system at the earliest possible stage.

This expanded framework supports all customers subscribing to any SAP S/4HANA Cloud, public edition bundle and provides a structured onboarding journey through 1:1 sessions, quarterly 1:m live sessions, and self-service resources. As SAP solutions continue to evolve, so does the Embedded Launch Activities framework — continuously expanding in scope, depth, and relevance.

The Customer Onboarding Journey

1:1 Onboarding Sessions

We engage directly with every customer, always involving implementation partners who bring deep expertise in SAP solutions, industry context, and customer business processes.

These sessions establish a shared understanding across all stakeholders, covering:

Project scope and key milestones
System architecture and provisioning foundations
Commercial entitlements included in the subscription
An introduction to artificial intelligence capabilities embedded in the product
An overview of SAP Support and engagement models

This early alignment lays the groundwork for a confident and well-structured implementation.

1:1 Entitlement Deep-Dive Sessions

As part of the current commercial bundles, customers have access to additional solutions across treasury, expense reporting, sustainability, and extensibility through SAP Build.

To help implementation teams understand both the value and the implementation path of these solutions, dedicated specialist 1:1 sessions are available, including:

SAP Build
SAP Taulia
SAP Concur
SAP Multi-Bank Connectivity
Sustainability solutions within Supply Chain Premium

These sessions ensure that entitlements translate into practical adoption and measurable business outcomes.

Quality Gates with SAP Cloud ALM

A core element of the expanded framework is guided enablement in setting up quality gates within SAP Cloud ALM.

Through shared-screen sessions, customers are guided to:

Define critical checkpoints across the project lifecycle
Assess readiness and quality of deliverables
Validate compliance with requirements
Confirm that key tasks and documentation meet expected standards

Quality gates provide structured decision points that support informed go/no-go decisions and reduce delivery risk.

Alignment Through the Onboarding Plan

The onboarding journey concludes with a dedicated 1:1 session focused on alignment around the Onboarding Plan, ensuring clarity on next steps and ongoing support.

Customers are also encouraged to participate in 1:m live sessions (with recordings available), covering topics such as:

Project methodology and implementation best practices
End-to-end system architecture
SAP product roadmaps
Influence SAP and SAP Communities
Upgrade cycles and continuous innovation
Tools that support sustained value from ERP, including ongoing AI innovations

Guided Enablement and Continuous Learning

As part of the Embedded Launch Activities framework, customers also gain access to Guided Enablement, a structured learning program for SAP S/4HANA Cloud Public Edition onboarding.

This program helps implementation teams track progress and build capability throughout the project lifecycle. The learning content is continuously updated to reflect product evolution and emerging best practices.

The Digital Baseline

The Onboarding Resource Center serves as the digital baseline for the onboarding journey. Customers are introduced through a welcome email and subsequently contacted by an Onboarding Advisor to initiate the journey and guide them through each phase.

Embedded Launch Activities provide a consistent, scalable, and evolving onboarding experience — designed to support customers from day one and grow alongside their SAP landscape.

How Do I Activate a Situation Type in the Extended Framework?

2026-03-04T11:20:40.372000+01:00

Situation Handling notifies users about issues requiring their attention. You may choose SAP delivered situation templates or design your own use cases. For the extended framework for Situation Handling, we often discussed how you can create custom situation templates. The framework comes also with SAP delivered use cases that you can easily activate.

This blog post explains how you can activate situation types from SAP delivered situation templates with the extended framework for Situation Handling. It has been available since SAP S/4HANA Cloud 2202 and SAP S/4HANA 2021 FPS02.

SAP Delivered Use Cases

Looking for Situation Handling use cases? Visit SAP Help and navigate to Situation Handling, then choose Use Cases. You can narrow your results by filtering for Situation Template Type (either extended object-based or message-based), area, and topic. To learn more about a specific use case, simply check the link in the Situation Template column for a detailed description.

Use Case

For illustration purposes we use the situation template Expiration of Purchase Contracts (PROC_ABOUT_TO_EXPIRE_CTR). Purchasers get a heads-up for purchase contracts that are about to expire.

Activation Overview for 2SL and 3SL

Before discussing the activation steps in detail, let me point out the differences between system landscapes and their specific transport paths.

In the extended framework for Situation Handling, you create a situation type from a situation template. Situation templates are only visible in the quality system of a 2-system landscape (2SL) and the development system of a 3-system-landscape (3SL). The situation type needs to be transported to the production system. The transport paths differ between 2SL and 3SL.

Transport the Situation Type in 2SL

In a 2-system-landscape, you transport the situation type from the quality system to the production system.

In the quality system you
- Create a situation type from a situation template
- Test if the configuration alerts the right users about the situation
- Export the well-defined situation type

In the production system you
- Import the situation type
- Since the data usually differs between quality and production system you need to enter the appropriate values for the condition filters
- Enable the situation type

Transports in 2-System-Landscape

Transport the Situation Type in 3SL

In a 3-system-landscape, transports are required from the development system to both the test and production system. In a 3SL environment you may also have different tenants for development, customizing, and parallel customizing that need to be considered as well.

On the customizing tenant in the development system you
- Create a situation type from a situation template
- Export the situation type

On the test tenant in the test system you
- Import the situation type
- Since the data usually differs between systems you need to enter the appropriate values for the condition filters
- Test if the configuration alerts the right users about the situation
- Forward the well-defined situation type

On the production tenant in the production system you
- Import the forwarded situation type
- Enter the appropriate values for the condition filters
- Enable the situation type

Transports in 3-System-Landscape

Detailed Activation of a Situation Type in 3SL

Now let’s check the detailed steps for a sample use case in a 3-system-landscape as it is more comprehensive. In 2SL the export / import mechanism resembles the one from development system to test system in 3SL.

Depending on your system setting, the transports may also be processed automatically. For optimal clarity, the blog post discusses the transport steps through manual triggers.

Development System

Create a Situation Type from a Situation Template

Log-in as business process configuration expert on the customizing tenant in the development system. Open the Manage Situation Types – Extended app where you see a list of SAP delivered templates. Use the search option to find the template for our use case Expiration of Purchase Contracts (PROC_ABOUT_TO_EXPIRE_CTR). Select the template and an object page opens. In the header, select Create Situation Type.

Create situation type from situation template

A new page opens with the situation type that contains all information from the situation template. You just need to enter an ID, Name and Description. The type is configured and ready to use. Depending on your requirements you could adapt the settings, for example, by adding filter values for the conditions, changing texts or rescheduling the batch job.

I recommend monitoring the instances to see how situations are handled.

Monitor situations

Let’s check the relevant settings and understand how the configuration works.

There are two Situation Triggers that detect situations and cover different usage scenarios. While the batch-based trigger checks for situations in the background, the event-based trigger reacts on every active change of the contract.

Situation triggers

The situation triggers cover the following cases:

The Event-Based Trigger checks the conditions whenever you create or update a purchase contract.
- Condition 1 checks if the validity period of a purchase contract expires within the next 30 days and triggers a situation. The information displayed to the user is defined in Situation Display number 1.
- Condition 2 is only executed if condition 1 did not match. That is, the validity period is not within the next 30 days, for instance when the contract got extended, and the situation is closed. As nobody will be informed about the closure, the texts are empty (Situation Display number 2).

Event-based trigger

In addition to the events, the Batch-Based Trigger regularly checks the validity end date according to the batch schedule.
- Condition 1 checks if the validity period of a purchase contract expires within the next 30 days and triggers a situation.

Batch-based trigger

The configuration for the Batch Job Scheduling specifies that the contract dates are verified every 3 hours throughout the day, beginning at 6:00 a.m.

Batch job scheduling

Export the Situation Type

Log-in as administrator on the customizing tenant in the development system. Open the Export Software Collection app.

On top of the table choose Create Software Collection and a new page opens
Choose Add Items and select the situation type you created
On the header select Check and wait until the check is processed successfully
Then choose Export and wait until the export is finished successfully

Test System

Import the Situation Type

Log-in as administrator on the test tenant in the test system. Open the Import Collection app.

Choose your software collection and a new page opens
On the header select Manual Import and wait until the check is processed successfully
Then choose Import on the bottom and wait until the import is finished successfully

Test the Situation Type

As business process specialist you can test the situation type on the corresponding tenant.

Make sure that the situation type is enabled.

Activate the situation type

Then maintain the conditions. The filter values are not transported since they may differ in the various systems and tenants.

Select the Event-Based Trigger and a new page opens
- Condition 1 select Edit and enter the filter values
  - Ext. Reference ID: enter Empty, using the value help
  - Validity Period End: enter Next30Days, using the value help
- Condition 2 select Edit and enter the filter values
  - Ext. Reference ID: enter Empty, using the value help
- Go back to the main page

Event-based trigger

Select the Batch-Based Trigger and a new page opens
- Condition 1 select Edit and enter the filter values
  - Ext. Reference ID: enter Empty, using the value help
  - Validity Period End: enter Next30Days, using the value help
- Go back to the main page

Batch-based trigger

With the situation triggers, you defined when a situation is detected. Now, you need to define who should be informed about situations. Maintain the team(s) in the Manage Teams and Responsibilities app and ensure that at least one team is enabled. The filter settings work the same way as with the standard framework for Situation Handling.

Situation recipients

Now you can test the situation type in your business area with the corresponding application data. You can check if there are purchase contracts that match the conditions by choosing Trigger Batch and Manage Instances.

Test the type with trigger batch

If no situations were detected you can log-in as purchaser and create or manipulate a purchasing contract. Add an end date within the next 30 days and the save event will trigger a situation.

When you log-in as a team member of the recipients team you can also check, if you were alerted about the situation.

After the successful test you push the situation type to the production system.

Forward the Situation Type

Log-in as administrator and open the Import Collection app.

Select your software collection and a new page opens
On the header select Forward and wait until the validation is processed successfully
Then choose Forward on the bottom and wait until the export is finished successfully

Production System

Import Collection to Production System

As administrator open the Import Collection app on the production tenant in the production system.

Choose your software collection and a new page opens
On the header select Manual Import and wait until the check is processed successfully
Then choose Import on the bottom and wait until the import is finished successfully

Activate the Situation Type

Log-in as business process specialist and open the Manage Situation Types – Extended app. Like in the test system, you need to maintain the situation type.

Enable the situation type
Add the filter values for the trigger conditions
Ensure that at least one recipient team is enabled

Now you are all set.

Further Information

You find many more blog posts in the Best Practices section of Intelligent Situation Handling in the SAP Community. And you can visit SAP Help Portal for further guidance on Situation Handling.

Converting to the 3-System Landscape – Part 5: Microlearning Videos

2026-03-04T19:17:08.607000+01:00

Co-Author: Dennis Leslie, Kate Wilson

Are you considering a move to the SAP Central Business Configuration–based SAP S/4HANA Cloud Public Edition, 3‑system landscape – but still unsure what to expect or how to get oriented? Good news: the following microlearning videos are available at no cost to guide you through the essentials.

Managing Transports in SAP S/4HANA Cloud 3-System Landscape
Microlearning video

This video explains how different types of data are transported from the development system to the test and production systems. It outlines a structured and streamlined transport process designed to minimize risk within the 3‑system landscape.
Exploring the Test Automation Tool in SAP S/4HANA Cloud 3-System Landscape
Microlearning video
This video highlights the features of the test automation tool for SAP S/4HANA Cloud Public Edition. The tool simplifies business process testing after release upgrades and is most effective in the 3-system landscape.
Navigating Parallel Line in SAP S/4HANA Cloud 3-System Landscape
Microlearning video
This video explains the parallel line feature. A parallel line is created as a copy of your main line and provides an additional SAP Central Business Configuration workspace, along with an extra development and test tenant for various use cases. This no‑cost feature is exclusive to the 3‑system landscape.
Exploring Developer Extensibility in SAP S/4HANA Cloud 3-System Landscape
Microlearning video
This video highlights the three types of extensibility – key user, developer, and side‑by‑side. While key user and side‑by‑side extensibility are available in both 2‑ and 3‑system landscapes, developer extensibility is exclusive to the 3‑system landscape. Developer extensibility allows you to create customer‑specific extensions to released SAP objects using ABAP, enabling a deeper level of customization.
Using the Configuration Localization Tool in SAP S/4HANA Cloud 3-System Landscape
Microlearning video
This video explains the features of the Configuration Localization Tool, which enables the creation of customer‑specific countries by localizing business configuration and is available exclusively in the 3‑system landscape.

Explore the power of the 3-system landscape today! To learn more, check out the SAP S/4HANA Cloud Public Edition, 3-System Landscape page on SAP Community.

If you liked this blog, please leave us a thumbs up at the top. Also, make sure to follow the SAP Central Business Configuration tag or follow this dedicated blog collection to stay up to date with the latest blog posts.