SAP Community - SAP S/4HANA Private Cloud

Gregor Wolf

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

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.

SAP Tax and Revenue Management - What is new for the S/4HANA 2025 FPS1 Release

2026-02-23T20:31:25.811000+01:00

Dear readers,

In a previous blog (SAP Tax and Revenue Management - What is new for the S/4HANA 2025 (initial) release I covered the new developments introduced in the S/4HANA 2025 FPS0 release. In this post, I will discuss what’s new in the S/4HANA 2025 FPS1 release:

Enable archiving of form data stored in the business document service (BDS/XML)

For Tax & Revenue Management, the archiving for form bundles was enhanced by the possibility to archive XML form data during the archiving run and delete the XML forms during the deletion run.

Compressed XML forms and alternative XML storage are supported as well.

The existing reload program was enhanced to handle reloading/re-creation of BDS documents for XML forms and restoring the DFMCA_FORM_DATA entries for XML forms.

This development has been downloaded all the way to ECC EhP8 (https://me.sap.com/notes/3648380)

For more information, see:

Help Document: Enable Archiving of Form Data

Disable the creation of new data form versions when updating existing form data

In legacy TRM, every change of formdata of an XML form lead to the creation of a new data version (corresponding to an extra line in dfmca_form_vers and an extra internal XML document). This new development allows the prevention of the creation of new data versions via customizing.

The new development is relevant for all channels processing forms: standard UI processes, API usage (via FMCA_RETURN_UPDATE), or “upload” via Emigall (via FMCA_RETURN_UPDATE).

For more information, see:

Help Document: Disable XML Versioning

Virtual Data Model for Tax and Revenue Management analytics

Virtual data model for analytics in tax and revenue management that provides streamlined and harmonized access to the tax and revenue management data model

Content that includes form bundle headers and form data for tax and revenue management analytics

For more information, see:

Help Document: New CDS Views in Taxpayer Identification and Returns Processing

As usual, stay tuned for more insights in my next post! Until then, thanks for reading, and feel free to share your thoughts or questions in the comments.

Diego Gaudenzi, Tax and Revenue Management Product Manager

"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 😊

Permit to work in SAP Cloud ERP Private: Aligning safety and maintenance in real operations

2026-02-24T16:08:24.639000+01:00

How can maintenance teams stay both safe and efficient while handling increasingly complex assets and processes?

This question opened our latest Expert Talk, where Maria Silipo welcomed SAP experts Jörg Medack and Yakub Shah, from product management, together with guest speaker Marc Janssen from the company Vattenfall. The session focused on how the Permit to Work process in SAP Cloud ERP Private supports operational safety and strengthens maintenance execution.

Watch the full Expert Talk episode below:

As explained by the SAP experts, a permit to work is much more than a formality. It acts as an operational safety barrier, setting clear conditions for safe execution and reducing the likelihood of incidents. SAP has been modernizing this process since 2020, simplifying how planning, preparation, approvals, safety implementation and closure are handled across maintenance activities. When these two worlds come together, plants gain a digital, structured way to guide safe work from start to finish.

Marc then provided the customer perspective. Vattenfall is one of Europe’s largest producers and retailers of electricity and heat, operating wind, biomass, gas, solar and district heating assets across multiple countries. With more than 20,000 employees and approximately 50,000 permits issued each year, the company relies heavily on a consistent and dependable safety process.

According to Marc, since implementing the SAP solution, Vattenfall has seen work becoming safer across the business units using it, measured by a significant drop in safety‑related incidents.

To support their internal policy that every maintenance job requires a permit, Vattenfall added a small extension. If a permit starts from an operation rather than the whole order, operation‑level data is transferred into the permit. Otherwise, the system uses the standard approach and copies information from the order header. This ensures that each permit always reflects the correct operational context.

Yakub then demonstrated how SAP’s integrated process works in practice. One of the design principles is to avoid repetitive work. When a user identifies a maintenance order that requires a permit, they can create it directly.

Example of a maintenance order that requires a work permit

Instead of starting from a blank form, the system encourages the use of templates linked to the technical object. These templates store information such as known hazards, typical mitigation measures, safety precautions, safety gates and required certificates. With this approach, operational data is taken from the order while safety‑critical data comes from the template, helping ensure that important aspects are not overlooked.

Some of the steps in creating and preparing a permit include:

Selecting the relevant permit type based on the job
Applying a template for the equipment or location
Copying operational details from the order
Automatically populating safety‑related details from the template
Defining whether the permit applies to the entire order or specific operations

Work permit overview

Once created, the permit follows a clear approval flow. The solution supports the four‑eye principle through a mix of mandatory and optional approvals. Customers can configure hierarchical approvals as well. For example, a second mandatory approval may only become available after the first one is completed. Every approval, comment and status change is logged, giving full clarity on decisions.

One of the strongest points in the demo was the validation logic before a permit can be issued. The system checks whether required safety precautions have been marked as implemented and whether dependent objects, such as safety certificates, are properly reviewed and approved. If something is missing, the user is blocked from issuing the permit until the gap is resolved.

These checks can be placed before printing or issuing, depending on the organization’s process. In real plant environments, especially when using tablets, each action is logged with date, time and user, enabling a transparent and trustworthy audit trail. For companies with unique validation needs, the extensibility framework introduced in 2023 allows custom rules to be added on top.

Check the complete demo in the video, starting on 03:31: https://youtu.be/N8sD04FwrIc?si=cSrutg_439G4bPz5

Practical operations also require flexibility. Permits may need to be suspended when a shift ends, revalidated after a break in work, or handed over to another technician. SAP supports all of these steps while keeping the full history. To help plant managers keep track, the standard dashboard provides KPIs such as active permits, suspended permits and overdue items. Vattenfall is exploring adding extra tiles to show maintenance orders with open permits, reflecting how their internal processes begin from the order.

Looking ahead, Marc shared two important wishes. First, a deeper integration of Permit to Work within SAP’s nine-phase maintenance model, so the system can prevent execution when a required permit is not approved. Second, the continued evolution of isolation management, which SAP is actively developing. Marc highlighted the need not only for the functional capabilities but also for extensibility, so customers can adapt the solution to their specific safety models.

Yakub and Jörg closed the session by summarizing what SAP has delivered recently and what is coming next. Permit to work is now fully Fiori-based, with extensible objects for work permits and safety certificates. Integration with maintenance orders will be delivered with the 2025 FPS1 release, and isolation management will also be part of that delivery. Additional capabilities, such as shared tagging, adjustments, and mass processing, are on the roadmap. On the maintenance side, SAP is working on making the phase model more flexible, giving customers more control over process insights.

The discussion made it clear that Permit to work in SAP Cloud ERP Private is evolving quickly, driven by customer scenarios and real operational needs. For companies like Vattenfall, the solution already brings measurable improvements in safety, reliability and transparency, and the roadmap promises even more integration and flexibility in the future.

Do you want to learn more? Continue the conversation with professionals in the SAP Community: SAP S/4HANA Asset Management | SAP Community

Check our complete playlist for all SAP Expert Talks and subscribe to SAP's channel on YouTube.

Helpful links

Find all our assets
We at Cloud ERP and SCM Product Success offer a service as versatile as our product itself. Click on the enablement wheel below and check out the numerous offerings our team has created for you:

SAP S/4HANA and SAP S/4HANA Cloud Private Edition 2025 FPS01: Final What's New & Product Assistance

2026-02-24T17:19:42.494000+01:00

With immediate effect, the final version of What's New information and Product Assistance for SAP S/4HANA and SAP S/4HANA Cloud Private Edition 2025 FPS01 is now available:

To access the final version of the Product Assistance on the current SAP Help Portal pages, please use SAP S/4HANA and SAP S/4HANA Cloud Private Edition.
To access the final What’s New information, please use What's New Viewer for SAP S/4HANA or What's New Viewer for SAP S/4HANA Cloud Private Edition.

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

In addition, you have access to further content, for example, the conversion and upgrade guides specifically tailored for SAP S/4HANA and SAP S/4HANA Cloud Private Edition. Please refer to the SAP S/4HANA and SAP S/4HANA Cloud Private Edition pages for more details

The Path to SAP Cloud ERP Private –Technical Assessment

2026-02-25T07:08:34.797000+01:00

With SAP Cloud ERP Private, SAP removes the complexity of designing, building, and operating SAP software for customers by offering a user- or metric-based subscription that bundles software and tooling licenses, infrastructure, and technical managed services—everything needed to run an SAP solution. Read more about this here: Understanding the Distinct Scope of SAP Cloud ERP Private

To ensure a smooth transition to the cloud, SAP collaborates with each customer and partner on all design, build, and operational topics relevant to SAP Cloud ERP Private, assessing the technical feasibility of each customer’s requirements and handing them over to the business unit within SAP that is responsible for designing, building and operating SAP Cloud ERP Private.

Moving to a cloud subscription service either from an on-premise datacenter or indeed from public cloud IaaS is not a trivial task. It requires due diligence to ensure that all technical and operational requirements are met, and where deviations exist, a solution is achieved to deliver the same business outcome.

To support our customers’ transition to the private cloud, SAP offers a safeguarding process which covers all the technical and operational requirements. This process, which we call Technical Assessment, is delivered by a unit within Global Cloud Operations called Cloud Architecture & Advisory (CAA).

This document explains the role and value of the Technical Assessment process in the journey to SAP Cloud ERP Private. It outlines how SAP works with customers and partners to achieve the following:

Advise on suitable private cloud options and high-level architecture choices
Assess technical requirements and align expectations across stakeholders
Transition the agreed outcomes into a clear and feasible target architecture before delivery

By providing an overview of the assessment domains, decision points, and outcomes, this document aims to give stakeholders a clear understanding of how the Technical Assessment helps ensure a secure, scalable, and successful transition to SAP Cloud ERP Private.

Figure1 : Technical Assessment Flywheel

Advise the customer on the private cloud offerings within the SAP GCO portfolio

A key factor to ensure a successful transition to SAP’s Private Cloud is to understand the private cloud offering and the details of each technical domain such as:

Technical Domain	Expected customer’s stakeholder
SAP Cloud ERP Private Overview	All key stakeholders
Cloud Technical Architecture	Infrastructure, application, basis, and network stakeholders
Network and Integration	Infrastructure, network, and security stakeholders
Cybersecurity and Compliance	Security, network, infrastructure, application, and basis stakeholders
Cloud Managed Services and Operating Model	All key stakeholders
Customer Onboarding	Infrastructure, application, basis, and network stakeholders

Table 1: Technical Domains and expected participants

These domains provide a structured lens to assess customer needs and requirements as well as position the right GCO services. Depending on the complexity of the requirements, some topics will require deep‑dive workshops to reach a shared understanding and robust solution options. This collaborative approach enables tailored architectures and operating models that align to the customer’s objectives and proactively address potential challenges during the move to SAP Cloud ERP Private.

Assess the technical feasibility of the customer’s requirements

Figure2: Technical Assessment aspects

Aligning the customer’s current and target (“to‑be”) state is essential to define a clear path for their cloud journey. This assessment ensures both sides share the same expectations on scope, timelines, and responsibilities.

Throughout this process, SAP validates that the customer’s business and operational requirements can be implemented within SAP’s private cloud delivery standards. It also confirms that the solution follows GCO best practices for business continuity, operations, and cybersecurity.

Some aspects to be covered during the assessment are the following:

Aspect	Topics to be discussed	Decisions to be taken
Deployment option, platform, and region	As described in the blog From On-Premise to Cloud: Making the Right SAP ERP Move, SAP offers several deployment options for SAP Cloud ERP Private, such as hyperscaler, SAP data center, customer data center, and premium suppliers – each available on different platforms and in multiple regions. It is the customer’s responsibility to choose the deployment model and select the platform and target regions, with support from the SAP CAA team to align with requirements, synergies, and the customer’s cloud strategy.	Deployment option (hyperscaler, SAP data center, customer data center, premium supplier) Cloud provider or hyperscaler for the deployment Regions (main and disaster recovery)
Network and communication infrastructure	Each platform provides different private and internet-facing connectivity options. Based on the chosen deployment option, platform, region, and performance needs, the customer must decide how to connect to SAP Cloud ERP Private, including any requirements for network segregation and DNS integration that should be clarified during the Technical Assessment.	Connectivity options for private and public access Bandwidth required DNS integration method (zone transfer, conditional forwarding, etc.) Load balancing requirements
Application platform and integrations	It’s crucial to clarify which bill of materials, applications, and solutions are in scope for the private cloud, how they are offered in the GCO portfolio (for example, high availability, disaster recovery, and SLAs), and how they will integrate with SAP and non‑SAP systems.	Bill of material and solution’s versions Business continuity options and SLAs Technical elements required for integration with SAP and non-SAP systems
Solution sizing	Solution sizing from the customer or partner must be translated into cloud technical sizing (for example, database and storage), since accurate sizing is key for a smooth transition and optimal performance.The blog Sizing Your Success: A Guide to SAP Cloud ERP Private is a recommended reference for this activity.	Target sizing of the different solutions and tiers Expected growth during the contract’s runtime
Security and regulatory requirements	As explained in the blog RISE with SAP: Comparing the Security of SAP S/4HANA Cloud, private edition Vs SAP S/4HANA Cloud, public edition, SAP applies a multilayered security strategy and a zero‑trust approach across its cloud services, with controls such as encryption, access control, auditing, compliance, logging, monitoring, and secure operations governed by SAP standards and policies. This underpins the SAP Cloud ERP Private security and regulatory framework. Each organization also has its own security and regulatory needs, and where specific requirements go beyond the standard framework, SAP reviews them and designs appropriate measures.	Confirm that SAP’s security framework meets the customer’s requirement in terms of cybersecurity and regulation. Identify any special requirement and find a solution for it.
Best practices and operational model	SAP Cloud ERP Private provides several operating models and SLA levels to suit different customer sizes and requirements. This includes defining backup expectations and reviewing roles and responsibilities (for example, via a RACI matrix) to identify and close any gaps.	Operational model Availability SLAs for solutions Customer’s specific backup SLA Review of roles and responsibilities RACI matrix to identify potential gaps

Table 2: Technical aspects to be assessed

The outcome of the technical domain sessions and the customer landscape assessment is a clear and accurate “to‑be” picture of the customer environment, including the transformation strategy. This serves as the blueprint to design and build the final landscape in SAP Cloud ERP Private.

Transition the customer’s requirements to GCO for delivery

SAP Cloud ERP Private is a managed private cloud service delivered by Global Cloud Operations (GCO), requiring a structured handover of customer requirements to SAP.

Early transition planning: Although the formal transition begins after the Cloud ERP Private agreement is signed, preparation should start early to avoid deployment delays that could jeopardize the project timeline.

Support process: The Cloud Architect and Advisory (CAA) team guides customers and partners through this process by collecting onboarding information, coordinating milestones, and ensuring smooth delivery to SAP teams.

The following outlines typical onboarding information to be collected:

Type of Input	Input Needed
Operational	Support user (S-user) Type of deployment (greenfield or brownfield) Planned downtime SAP Best Practices activation Financial relevance Customer contact information Regulatory requirements – GxP, HIPPA, data sovereignty Cybersecurity requirements
SAP-specific	System parameters (SIDs, clients, languages, etc.) Target versions
Network and DNS	Connectivity method Connectivity data Private IP addresses ranges DNS information

Table 3: Onboarding information

Outcome of Technical Assessment: baseline and working document

The Technical Assessment process produces the Technical Assessment Report, summarizing all sessions and workshops, the proposed to‑be architecture for SAP Cloud ERP Private, and any assumptions or exceptions from discussions.

This report is shared with the customer for review and sign-off. It serves as the baseline for the commercial contract, delivery onboarding and is a living document throughout the contract lifecycle.

Innovate and grow in SAP Cloud ERP Private

Everything described above represents continuous engagement throughout the entire contract lifecycle, not a one-time effort.

For new customer requirements, the GCO team supports the customer and partner through a renewed technical assessment process. Depending on the requirement, relevant assessment domains and onboarding details will vary, but GCO provides full guidance—advising on goals and value drivers, identifying innovation opportunities, and extending the Cloud ERP Private scope via the change request process.

SAP Extended Warehouse Management for SAP S/4HANA Cloud, Private Edition, 2025 FPS01 – What’s New

2026-02-25T11:15:29.070000+01:00

We have recently released the latest updates for SAP Extended Warehouse Management for SAP S/4HANA Cloud, Private Edition, 2025 FPS01. With this release, we further expand the Predictive Labor Demand Planning capabilities available for SAP EWM, add in more functionalities and scenarios for the Advanced Shipping & Receiving integration, deliver a host of extensibility and user experience improvements, strengthen our Suite Integration capabilities, and much more.

And unlike many of our past product release blog posts, I would like to begin today’s overview with the latest updates to our AI capabilities in Extended Warehouse Management. To find out more technical details and information on each feature (such as Customization steps) I shall link the corresponding “What’s New” viewer from the help portal in the title of the subchapters.

ARTIFICIAL INTELLIGENCE

With our AI strategy for Logistics and warehousing, we aim to address further on the labor and resource shortage in the warehouse execution. We achieve this via machine learning–based predictive analytics to forecast current and future workloads and conduct forecast based on long-term historical data across warehouse operations, as well as via Joule copilot to provide advanced warehouse operation, and proposing insightful solutions to streamline the outbound process. With this feature pack release, we continue to advance towards this goal via the following updates.

Feature enrichment for AI-assisted Predictive Labor Demand Planning

In the previous two product releases, our teams have delivered a solid foundation for Predictive Labor Demand Planning (LDP), through which warehouse operators and shift managers can:

Predict planned workload on Outbound Delivery Order and Warehouse Order/Warehouse Task level based on historical data collected from RF Picking and Packing activities
Use a minimum of 2 weeks of historical data and predicts the short-term labor demand in next days or weeks
Utilize the SAP Smart Business dashboards to gain insights on workload duration, calculated Full-time-equivalents (FTE) and other important aspects such as volume, weight, and number of expected items

With the SAP S/4HANA Cloud Private Edition 2025 FPS01 release, the solution now supports the persistence of aggregated historical workload data and determines planned duration for outbound delivery staging.

Additionally, we have expanded the range of executed picking workload that can be captured – such as the start date and time - to improve LDP reporting, KPI calculation, and historical workload tracking for warehouse task confirmations via the external API. This has been done by integrating and enabling a two-step pick process for historical records and time tracking using an existing remote-enabled ODATA-API: API_WAREHOUSE_ORDER_TASK_2.

Also, on the topic of reporting for Labor Demand Planning, we now directly integrate the pLDP statistics to the Fiori App “Warehouse KPIs”, providing users with a view of workload forecast KPIs directly as configurable cards, alongside seamless navigation to the detailed smart-business drill-down apps.

The user experience is further enhanced through dynamic date functions. The first forecast graph now displays the total forecast value with drill-down to activity areas for deeper insight. Workload forecasts can be analyzed through five KPI measures—Duration, Volume, Weight, Capacity Consumption, and Number of Items—offering a clear and structured view of operational demand.

Joule integration with the EWM Outbound process

In the upcoming releases of Joule monthly schedule, we will release the full capabilities of Joule feature “Talk to your Warehouse Outbound process”, providing users with the possibility not only to retrieve data from EWM backend on Outbound Delivery Orders, but also to trigger next steps and accelerate the outbound fulfillment process. In addition, users can also navigate directly in the Joule conversation to the corresponding FIORI apps.

Get an overview on all available Joule capabilities in SAP S/4HANA Cloud, private edition via our dedicated SAP Help – Joule in SAP S/4HANA Cloud Private Edition - highlighting transactional and informational capabilities to stay up-to-date.

ADVANCED SHIPPING & RECEIVING

Integration between transportation and warehouse logistics is a significant contributor towards logistics efficiency, synchronizing process changes between warehouse and transportation, reducing overall logistics-costs by optimizing and streamlining freight planning with warehouse execution. To further tighten this integration, with this release we provide the following enhancements and updates to Advanced Shipping & Receiving.

Perform ad-hoc loading

In this latest release, we further streamline the loading process by enabling warehouse operators to assign Outbound Delivery Orders to freight orders during the radio frequency (RF) loading process in Advanced Shipping and Receiving. When the first handling unit (HU) is scanned and loaded, the complete Outbound Delivery Order, including the remaining HUs, is assigned to the Freight Order. Ad-hoc loading can be performed in the following RF transactions:

Loading By HU
Loading By Door
Loading By Bill of Lading

This new process helps to simplify loading in a busy warehouse, in such scenarios as when:

There are regular freight orders to a certain plant or region. When the truck arrives, all the HUs in the staging area for this plant or region can be loaded onto it. This procedure is typically used in combination with the immediate loading process.
A truck at the door has some space left that can be further filled. Additional suitable HUs can be loaded onto the truck, and the system automatically assigns the corresponding Outbound Delivery Order to the Freight Order.

To see if an Outbound Delivery Order is relevant for Ad-Hoc Loading, users can check in the Outbound Delivery Orders app (transaction /SCWM/PRDO) and/or the Warehouse Monitor app (transaction /SCWM/MON).

Warehouse-Driven Outbound Delivery Order split

In the shipping process, sometimes companies need to split Handling Units based on actual pick, pack and stage status, according to various exceptions in the outbound process. To increase warehouse and shipping flexibility and allow the adjustment of deliveries according to operational reasons, we provide the option to do a warehouse-driven Outbound Delivery Order split with SAP S/4HANA Cloud, private edition FPS01.

With this feature, warehouse and shipping operators can split Outbound Delivery Orders in the warehouse-driven scenario of Advanced Shipping and Receiving triggered from EWM. For example, for an urgent customer order and in case of stock insufficiency, it is now possible to split the Outbound Delivery Order into available quantity and the remaining quantity. So the available quantity can be sent to the customer as planned, and the remaining quantity can be sent at a late point in time, while the corresponding new split-Freight Unit can be considered for further planning in Transportation Management.

The split of Outbound Delivery Orders can take place up until the status Ready for Shipping is set. The Outbound Delivery Orders can be split in the following ways:

Split Outbound Delivery Order item into a new Outbound Delivery Order – the unpicked (and unpacked) item quantity is split from an Outbound Delivery Order into a new Outbound Delivery Order. For example, there is currently not enough quantity available in the warehouse, but the quantity that has already been picked could be shipped with an available transportation vehicle. The picked quantities stay in the original Outbound Delivery Order, and the unpicked quantities move to a new Outbound Delivery Order, including the corresponding Freight Unit in Transportation Management (TM).
Split handling unit (HU) into new Outbound Delivery Order – one or more selected HUs are split into a new Outbound Delivery Order. For example, an HU is to be delivered on a different date in the future. The HU, which is split, is moved to a new Outbound Delivery Order, while the remaining HUs in the original Outbound Delivery Order are kept in that Outbound Delivery Order. This scenario works in classic Advanced Shipping and Receiving loading as well as Immediate Loading.
Split remaining parts into new Outbound Delivery Order – the HUs in the Outbound Delivery Order that are to be delivered are selected, and the system splits the remaining items or HUs into a new Outbound Delivery Order. The selected HUs are kept in the original Outbound Delivery Order. For example, the HUs for an Outbound Delivery Order which are already fully picked, packed, and loaded to a specific transportation vehicle. However, the remaining parts of the Outbound Delivery Order will not be ready for picking, packing, or loading in time. The remaining parts are split to another Outbound Delivery Order and the loaded HUs are sent to the customer.

The setting for this functionality can be found in Customizing for Extended Warehouse Management under Goods Issue Process > Outbound Delivery > Define Document Types for Outbound Delivery Process. To enable splitting of Outbound Delivery Orders, Outbound Delivery Order Split must be chosen in the Outbound Split setting for the combination of document type and document category.

Harmonized SAP Global Trade Service integration

A final highlight I would like to mention in Advanced Shipping & Receiving is that the integration pattern for ASR and SAP Global Trade Services (SAP GTS) is now available for Extended Warehouse Management embedded in SAP S/4HANA. This integration pattern is harmonized with the integration pattern used in the decentralized setup for the Advanced Shipping and Receiving process (which is available since February 2025 with the SAP S/4HANA 2023 FPS03 release) and features enhance stability and reliability.

To enable the new integration pattern, users must ensure that the status type “DSC - LE Distribution Confirmation” is active in all relevant outbound delivery status profiles, in Customizing for Extended Warehouse Management under Cross-Process Settings > Delivery - Warehouse Request > Status Management > Define Status Profiles.

SUITE INTEGRATION

Integration is a core pillar of our investments, by which we provide a deep and native integration with SAP S/4HANA Private Cloud solution components, along with other SAP cloud solution offerings for seamless integration of comprehensive logistics end-to-end processes incl. production integration, customs processing and more. With SAP S/4HANA Cloud, private edition 2025, FPS1 we deliver the following enhancements.

nJIT Supply-to-Customer (S2C)

Just-in-Time (JIT) processing is a common practice in manufacturing industries for efficient demand-driven production and logistics across supply chains. Just-In-Time Supply to Customer covers JIT processes from the perspective of a supplier. A JIT supply-to-customer(S2C) call is a request of the customer to deliver components to a ship-to location, specifying the requested quantity, date, time, and destination within the ship-to location for each item. The JIT S2C supply starts with the receipt of JIT calls from the customer. These JIT calls are directly relevant for shipping, assuming there is stock available from in-house production or external procurement. The shipping process starts with delivery creation and ends with posting goods issue. After goods issue, the settlement is done from creating the billing document until receiving the payment.

With the current release, we enable production planners, warehouse operators and shipping specialists to work with the S2C process for Just-In-Sequence (JIS) calls when using Extended Warehouse Management (EWM) embedded in SAP S/4HANA in their storage locations. After the production and packing of the sequenced component groups, the system creates outbound deliveries using the Manage Customer JIT Calls by Component Groups app, including handling unit numbers from packing. These deliveries are then transferred to EWM. In EWM, the system creates an Outbound Delivery Order that contains the lowest-level HU details (to be used as pick-HUs) per delivery item. The HU warehouse tasks can be created manually or automatically to pick highest-level HUs and move them to the staging area. If HUs are already staged, the system automatically creates and confirms the corresponding pick tasks, reducing manual steps.

Quantity Correction Process in Advanced Returns Management (ARM)

There are cases when after material inspection is done for received customer returns, there rises a need to correct received quantities, for example when not the entire quantity was returned, or if upon inspection of the goods, some are beyond recovery and must be sent to salvage rather than storage.

With this release we enable logistical follow-up action “0023 - Goods Receipt Quantity Correction” to correct the goods receipt quantity after inspection so that discrepancies between the returned quantity and inspected quantity can be accurately reflected in the system. The outbound delivery is directly sent to Extended Warehouse Management with a corresponding document type and item type. Automatic warehouse task creation and confirmation to a staging zone, including an automatic goods issue posting is performed to enable the stock correction

To run the quantity correction process in Advanced Returns Management, users must activate business configuration set (BC set) Outbound Delivery Process for ARM Quantity Correction (/SCWM/DLV_OUTBOUND_ARM_QC). There is a proposed mapping for Logistics Execution (LE) document and item types to EWM document and item types in the BC set documentation.

Quality Inspections for Products in Outbound Delivery Orders

A final highlight worth spotlighting in the area of Suite Integration is the integration of quality management to outbound warehouse processes. With this integration, warehouse operators and quality inspectors can make sure that specific qualities of a product (for example, paperwork completion) are checked before the relevant Outbound Delivery Order leaves your warehouse. To this end, we introduced a new indicator on the EWM Outbound Delivery Order item – Relevant for Q-Inspection in Outbound.

With this indicator, the system checks the status of the quality inspection at goods issue posting in EWM and prevent successful posting in case quality inspection is not completed. The check prevents goods issue posting for EWM Outbound Delivery Orders with open inspection lots with origin:

10 - Delivery to Customer with Sales Order
11 - Delivery to Customer Without Sales Order
12 - General Delivery

To use this feature, IOT 8 must be activated in Customizing for Extended Warehouse Management under Cross-Process Settings > Quality Management > Basics and Integration > Define and Activate Warehouse-Dependent IOTs.

CONTINUOUS MODERNIZATION & SIMPLIFICATION

Our commitment to modernization and continuous improvements not only enhances functionality but also provides users with a seamless and intuitive interaction, helping businesses drive efficiency, optimize processes, and deliver superior experiences to their stakeholders. To that end, I would like to highlight the following features from this latest release.

Use Stock Transfer Orders with Valuated Stock in Transit (SIT)

Starting with the SAP S/4HANA Cloud, private edition 2025 FPS01 release, we enable the use of EWM-managed storage locations as receiving locations in the stock transfer process with valuated SIT. Valuated SIT can be used in both intra-company processes and processes that move stock between companies.

Quantify changes are not supported in the scenario, besides that an inbound delivery item with valuated SIT can be set to zero in a stock transfer order process, which cancels the delivery. Subsequently, the quantity of an inbound delivery item with valuated SIT cannot be changed to anything other than zero in a stock transfer order process.

The field EWMStockTransferOrderType is now also available in the OData API Warehouse Inbound Delivery - Read, Update (A2X) (API_WHSE_INB_DELIVERY_2). To enable this feature, the Prev. Qty Upd STO checkbox must be selected in Customizing for Extended Warehouse Management under Goods Receipt Process > Inbound Delivery > Define Item Types for Inbound Delivery Process.

Specify Handling Unit Number for Component Consumption

In certain production environments, the Production Supply Areas (PSA) are managed by the Handling Units. Before this release, production warehouse workers had to consume the entire component group HU at the PSA before you can register the consumption in the system. However, there are cases when only select sub-HUs are required from the PSA. In order to keep the physical world and the system in sync, we now allow users to specify which HU the component is to be consumed from. This strengthened integration is supported for synchronous goods movement postings via the Production Order Confirmation API (API_PROD_ORDER_CONFIRMATION_2_SRV), which passes the handling unit (HU) number for component consumption with synchronous goods movements.

CLEAN CORE & EXTENSIBILITY

The Clean Core Extensibility strategy aims to provide a modern and powerful integration option for customers and partners. Alongside supporting this strategy, we continuously adapt solution content to modernize and simplify the user experience. By regularly updating and refining Extended Warehouse Management for SAP S/4HANA Cloud, private edition, we ensure we remain relevant and effective in meeting current needs.

In the SAP S/4HANA 2025 FPS01 release we continue to deliver on this with the following highlights:

Update for the Warehouse Order and Task (A2X) API – We have enhanced the existing ODATA-service Warehouse Order and Task (A2X), with the new ‘Lock/Unlock Warehouse Order’ actions on the Warehouse Order. This was done to enable efficient and lean integration of warehouse automation (e.g. robotics).
Enhancement of Stock List in the Warehouse Task Apps – We enabled warehouse operators to add their own fields to the stock list at warehouse task creation for warehouse request. For this, they can use the Business Add-In (BAdI) Enhancement for Stock List for Warehouse Task Creation (/SCWM/EX_CORE_CR_STOCK_LIST) to add additional fields to the display of stock at warehouse task creation for warehouse requests in the following apps:
- Create Warehouse Tasks - Inbound Delivery
- Create Warehouse Tasks - Outbound Delivery Order
- Create Warehouse Tasks - Posting Change
- Create Warehouse Tasks - Stock Transfer

FIND OUT MORE!

To see more details on the above-mentioned topics as well as see what other enhancements we delivered with this release (such as RF improvement to allow RF receiving of mixed HUs with Serial Numbers, deletion of Inbound Deliveries in the STO scenario, and more) I highly encourage you to explore our latest “SAP Extended Warehouse Management for SAP S/4HANA Cloud 2025, Private Edition, FPS01” slide deck.

You can also find more technical details and documentation on the above listed topic and others we left out via the “What’s New” viewer on the Help Documentation portal.

For more information about SAP Extended Warehouse Management, please follow us on social media, our YouTube channel or our community pages:

SAP EWM Community

SAP YouTube Channel

EWM LinkedIn Community

SAP Extended Warehouse Management Roadmap Explorer

Release information and restrictions of embedded EWM on SAP S/4HANA 2025 and SAP S/4HANA 2025 FPS01

Release information and restrictions of Decentralized EWM on SAP S/4HANA 2025 and SAP S/4HANA 2025 FPS01

For a complete list of Q&A from the EWM community, please access this link:
https://answers.sap.com/tags/01200615320800000705

In case you do not find your specific question there, feel free to post your question via the following form:
https://answers.sap.com/questions/ask.html?primaryTagId=01200615320800000705

What’s New in the SAP Cloud ERP Private 2025 FPS1 release

2026-02-25T11:30:00.017000+01:00

The SAP Cloud ERP Private 2025 FPS1 release brings a new level of intelligence to everyday business work by expanding how AI supports users across various LoBs. At the core of this update is Joule and SAP’s agentic AI framework, where specialized agents and conversational capabilities work together to guide users through tasks, surface the right information, and provide recommendations in the moment of need. Instead of navigating complex transactions or piecing together data from multiple systems, employees can rely on natural‑language interactions to move through their processes faster and with greater confidence. This release also delivers embedded AI features that automate checks, streamline validations, and support operational decisions with real‑time insights. The overview chart below brings together all key innovations delivered with the SAP Cloud ERP Private and SAP Cloud ERP 2025 FPS01 Release, highlighting how AI, Joule capabilities, and embedded intelligence are supporting users across every line of business.

Altogether, these innovations help organizations reduce manual effort, strengthen transparency, and keep their operations running more smoothly, while allowing users to focus on the work that truly drives business outcomes.

Agentic use cases

Finance:

Mastering cash flow with the Cash Management Agent*

The Cash Management Agent supports finance teams by automating tasks that usually drain time, checking bank statement completeness, validating opening balances, and preparing cash‑flow forecasts. Many organizations struggle with fragmented financial data and delayed insights, which makes it difficult to spot potential cash shortages or opportunities to use surpluses effectively. By relying on Joule and Joule Agents to run these daily checks, calculations, and summaries, teams can shift from manual reconciliation to confident, data‑driven decisions. This automation improves accuracy and frees cash managers to focus on strategic liquidity planning instead of routine monitoring. In the end, it strengthens daily cash‑position visibility and helps organizations manage their cash resources more efficiently.

Learn more by accessing the SAP Help Portal.

* This AI offering is currently in Beta and available at no cost. Pricing will be communicated once the AI offering becomes generally available. A separate subscription is required for use or testing. Learn more.

R&D:

Streamlined engineering changes with the change record management*

Engineering teams often lose momentum when a simple product or process change turns into a maze of documentation, reviews, and approvals. Coordinators and engineers must manually create change records and shepherd them through the process, which can delay decisions and slow time‑to‑market. The Change Record Management Agent uses SAP Joule to assist with creating complete and consistent change records and orchestrating the necessary workflow steps. By reducing manual effort and guiding teams through the process, it helps engineering organizations keep changes moving without administrative bottlenecks. This leads to a faster, more efficient change‑management cycle and ultimately supports quicker delivery of updates and innovations.

Use our SAP Help page to learn more.

Joule capabilities

Please note that certain Joule features described in this blog may not yet be available in your system and are planned for release as part of the upcoming Joule release cycle scheduled for March/April 2026.

Finance:

Joule for invoicing specialists to enable more-seamless navigation and transactional actions within billing documents

Invoicing specialists often spend far too much time clicking through multiple screens just to find the right convergent invoicing app or complete a billing‑related task. When workloads are high, even simple actions, like navigating to a billing document or making a small update, can slow the process and impact how quickly customers receive clear and accurate invoices. With expanded Joule capabilities, specialists can move directly to the right SAP Fiori apps and perform transactional actions through natural‑language prompts, without hunting for the correct tile or transaction. This conversational support reduces manual effort and helps teams resolve billing tasks more efficiently, leading to quicker processing and a better customer experience. Over time, this can even help reduce days sales outstanding by keeping billing workflows running smoothly and consistently.

AI-assisted accrual object creation

Preparing manual accruals often requires finance teams to gather fragmented information, apply judgment, and cross‑check historical patterns, all of which can be time‑consuming and inconsistent across entities. When deadlines are tight, variations in how preparers estimate amounts or select accounts can increase the risk of missed accruals or adjustments later in the audit process. With AI‑assisted accrual creation in Joule, users can describe their scenario in natural language and instantly receive a proposed accrual object, including category, amount, life term, and relevant GL accounts. They can refine any attribute, and Joule adapts its suggestions in real time based on the edits, gradually improving proposal quality through continued use. This guided, conversational approach streamlines preparation, increases consistency, and helps finance teams create more accurate accruals with far less effort.

Sales:

Staying ahead with AI-assisted detecting of expiring prices using Joule

Pricing specialists often spend valuable time hunting through condition records to find prices that are about to expire, a task that becomes even more demanding when large volumes of data and tight sales timelines are involved. Missed expirations can lead to outdated pricing in customer quotes, last‑minute firefighting, and unnecessary manual corrections. With Joule detecting expiring prices, displaying relevant condition records, and even supporting validity extensions and mass changes, specialists can handle follow‑up activities with far less effort. This reduces repetitive work, minimizes human error, and keeps pricing information accurate and up to date across the system. Ultimately, it enables teams to manage pricing proactively, saving both time and operational cost.

Use our SAP Help page to learn more.

AI-assisted fetching and listing of open sales documents

Internal sales reps often need to scan through multiple criteria in VA05 just to find the right open sales orders, which can slow down workflows when customers are waiting for updates. Searching by document type, dates, materials, or organizational data requires navigating several fields and filters, making the process repetitive and time‑consuming. With AI‑assisted retrieval in Joule, reps can simply ask for open sales documents, and the system instantly displays orders filtered by attributes such as customer, material, creation date, or sales area. This conversational approach reduces the manual effort needed to locate the right information and helps reps respond faster and more accurately. The result is a more efficient sales process and smoother daily operations for the team.

Consult our SAP Help Page for more information.

AI-assisted sales quotation changes using Joule

Updating sales quotations can be surprisingly time‑consuming, especially when internal sales reps need to adjust quantities, refine pricing, change delivery dates, or capture customer‑specific references across multiple line items. These routine updates often involve navigating several fields in VA22, increasing the chance of small mistakes that can slow down the sales cycle. With AI‑assisted quotation changes in Joule, reps can make these adjustments through simple natural‑language requests, whether they need to update a quantity, modify a price via condition type, set delivery dates, or record reasons for rejection. This conversational flow speeds up the process and reduces manual effort, helping teams respond to customer requests more quickly and accurately. The result is a smoother quotation‑management experience that keeps sales moving with less friction.

Service:

Searching and navigating to service contracts with Joule

Service agents often spend more time searching for the right service contract than actually solving the customer’s issue, especially when navigating by status, dates, or complex contract structures. These delays can disrupt workflows and make it harder to move quickly from one task to the next. With Joule assisting through natural‑language prompts, agents can instantly search for service contracts, open details, complete releases, or jump directly to the relevant SAP Fiori functionality. This reduces unnecessary clicks and helps users focus on completing service‑related tasks instead of trying to find them. As a result, teams can deliver faster responses and manage service contracts with more confidence and less effort.

Joule for transferring in-house service objects

Transferring an in‑house service object between plants or storage locations often requires navigating several steps in the system, from creating the outbound delivery to recording the inbound receipt. These tasks can slow down technicians and coordinators who simply want to keep service operations moving. With Joule guiding the process through conversational prompts, users can initiate the transfer, add the target plant and storage location, and create the necessary deliveries without searching for the right transaction. This reduces friction in daily logistics and helps teams complete handovers more reliably. The conversational flow not only speeds up execution but also makes the transfer process easier for occasional users who don’t perform it every day.

Consult our SAP Help Page for more information.

Supply Chain:

Enabling Joule to drive operational efficiency in outbound processes in SAP Extended Warehouse Management

Warehouse teams often juggle multiple screens just to track outbound deliveries, check warehouse tasks, or confirm the status of orders—slowing down operations in environments where every minute counts. As outbound volumes grow and customer expectations tighten, the effort required to manually search, summarize, and update records can become a real bottleneck. With Joule integrated into SAP EWM, users can search for outbound delivery orders, review warehouse tasks, or even create and confirm warehouse orders simply by asking in natural language. This gives frontline teams instant insights and reduces the time spent navigating complex menus or transactions. The result is faster decision‑making, smoother outbound processing, and a more intuitive experience that helps warehouses keep goods moving efficiently.

To learn more, access our SAP Help Portal.

R&D:

Project assistant capabilities for the Joule copilot: read cost and revenue details of project objects

Project controllers and R&D teams often spend a lot of time gathering cost and revenue details from multiple reports, especially when they need to compare actuals, planned values, commitments, or fiscal‑year breakdowns. Navigating through different project objects, whether a project, WBS element, network, or network activity, can slow decision‑making and make routine checks feel heavier than they need to be. With Joule acting as a project assistant, users can simply ask for the financial picture of any project object and instantly receive details such as actual cost, planned cost, commitments, or revenue, including breakdowns by fiscal year, cost component, or value category. This conversational access removes the need to open complex reports or consolidate information manually, giving teams a clearer view of project performance in seconds. The result is faster insights, easier financial monitoring, and a more intuitive way for project stakeholders to stay on top of their work.

Consult our SAP Help Page for more information.

Streamlining batch master insights and navigation with Joule

Reviewing batch master data often requires users to navigate across multiple fields and apps to check details such as material, plant, batch status, manufacturing date, shelf-life expiry date, or supplier, which can slow decision-making and increase the risk of missed insights under tight timelines. With Joule in SAP S/4HANA Cloud, private edition, users can describe their requirement in natural language and instantly retrieve relevant batch master information, then navigate directly to the Manage Batches object page for deeper analysis, updates, or next actions. This conversational approach streamlines access to batch insights, enhances user experience, and improves operational efficiency through faster, more intuitive interaction.

Embedded AI

Finance:

AI-assisted fixed asset key figures explanation

Fixed asset reporting often raises questions that require deep accounting knowledge, especially when values are influenced by midyear acquisitions, depreciation keys, or complex calculation rules. In many organizations, answering these questions means digging through configuration tables or asking specialists to explain how a specific number was derived. With AI‑assisted explanations in Joule, users can simply request a breakdown of any fixed asset key figure and immediately see where the values come from and how they were calculated. This natural‑language guidance helps preparers and reviewers understand depreciation logic and valuation outcomes without manual analysis, reducing the risk of errors or compliance issues. As a result, teams can resolve fixed‑asset questions more quickly and consistently, with far less effort during period close or audits.

AI-assisted settlement rule proposal for asset capitalization

Creating settlement rules for investment measures can be a painstaking task, especially when projects or internal orders need to settle to fixed assets and no automatic guidance is available. Finance teams often spend time determining the right receivers and percentages, increasing the risk of inconsistencies across measures or late adjustments when assets are capitalized. With AI‑assisted settlement rule proposals in Joule, users receive an initial suggestion for full settlement to fixed assets and can easily refine the proposal by adjusting percentages or selecting different receivers. This conversational support reduces manual effort and helps ensure more accurate asset class determination for final capitalization. The result is a smoother, more reliable settlement process that supports finance teams without adding complexity.

Supply Chain:

AI-assisted goods receipt analysis for bordero documents

Goods receipt processing for bordero documents can be slow and error‑prone, especially when teams need to manually review carrier paperwork, create corresponding freight orders, and verify that all information matches what’s in the system. These manual checks often lead to delays at the gate, longer truck turnaround times, and unnecessary waiting for logistics partners. With SAP Document AI analyzing bordero documents, the system can automatically extract key details, propose a freight order, and highlight discrepancies between the uploaded document and existing freight data. This reduces the time spent on validations, improves accuracy, and helps teams process inbound goods more efficiently. The smoother flow not only enhances operational performance but can also reduce yard congestion by keeping vehicles moving.

Summary

As you look across the innovations in this release, a clear pattern emerges: AI is no longer something users “go to”, it’s something that quietly supports them throughout their day. Whether it’s a cash manager starting the morning with a clear liquidity picture, a service agent navigating directly to the right contract, or a warehouse coordinator checking outbound tasks with a simple question, Joule and embedded AI make these moments feel more connected and intuitive. These capabilities reduce the friction of everyday work, giving teams more room to focus on decisions, collaboration, and the tasks that genuinely move the business forward. And while this release delivers meaningful improvements on its own, it also lays the foundation for even more intelligent assistance, with agents and AI features becoming part of the natural rhythm of how people use SAP Cloud ERP. It’s a step toward a future where systems feel less like tools and more like partners, helping organizations work smarter, not harder.

Thank you for taking the time to explore the latest updates of AI‑driven capabilities in SAP Cloud ERP Private Edition with us. If you’d like to stay informed about upcoming features, deep dives, and enablement content, make sure to follow updates tagged with PSCC_Enablement in the SAP Community. You’re also welcome to connect with me (@Yannick_PTT) both in the community and on LinkedIn for more insights and continuous updates.

For a deeper look into the intelligent capabilities delivered in this release, you can explore the full documentation on the SAP Help Portal.

More information

We at Cloud ERP Product Success offer a service as versatile as our product itself. Check out the numerous offerings our team has created for you below:

Join the Updated SAP Defense & Security Courses – Now Live!

2026-02-25T12:44:05.753000+01:00

Dear learners,

I’m pleased to share that the updated versions of IDS20_2601(61) and IDS30_2601(61) are now live and ready for learners. These new releases include fully corrected and revalidated hands-on exercises on the S4U SAP S/4HANA 2025 demo system, with master data and configuration aligned to the 2025 tenant.

These improvements ensure an even smoother, more reliable learning experience—perfect for anyone working with SAP S/4HANA Defense & Security scenarios.

Why Join These Courses?

Each course has been refined to match real-world Defense & Security processes and provides hands-on, scenario-driven learning. Here's a short overview:

IDS10 – Exploring Fundamentals of SAP S/4HANA Defense & Security

A high-level introduction offering conceptual grounding in SAP Defense & Security, ideal for learners looking to understand core capabilities, system navigation, and foundational processes.
➡️ Great for newcomers and those planning to progress into deeper topics.

IDS20 – Exploring Organizational Flexibility in SAP S/4HANA Defense & Security

Designed for consultants and solution architects, this course dives into capability planning, organizational integration, HR topics, and accounting within the SAP D&S solution—supported by demonstrations and exercises.
➡️ Ideal for those involved in implementing or supporting Defense & Security structures.

IDS30 – Exploring Logistics and Maintenance in SAP S/4HANA Defense & Security

A hands-on course dedicated to logistics, maintenance processes, and operational readiness in Defense & Security environments.
➡️ Perfect for practitioners working with material management, maintenance workflows, or operational logistics.

Start Learning Today!

Access on learning.sap.com (LSC):

Classroom / ILT Registration:

IDS10 – https://training.sap.com/course/ids10
IDS20 – https://training.sap.com/course/ids20
IDS30 – https://training.sap.com/course/ids30

Thanks,
Greg

The SAP Extended Warehouse Management FAQ Series: AI-assisted Predictive Labor Demand Planning

2026-02-25T16:02:41.055000+01:00

As many of our EWM customers are excited to learn what AI capabilities we are working on, with S/4HANA Cloud for EWM, Private Edition, we’ve decided to write this blog to provide an overview on the AI-assisted predictive labor demand planning topic.

We hope it will give you good information on the released features, as well as hands-on information on how to start using it.

Feature scope of AI-assisted Predictive Labor Demand Planning (pLDP):

2023 FPS03 (release date Feb. 2025), we released the backend foundation for the pLDP in which users can get planned workload based on executed workload of RF based Picking and Packing activities in the warehouse outbound processes.
2025 FPS00 (release date Oct. 2026), we introduced the Machine Learning algorithm in the EWM side to learn from the historical executed workload to derive future workload forecast. Meanwhile, we have built up a new UI on the Fiori based SAP Smart Business application to show the workload forecast with drill down capabilities.
2025 FPS01 (release date Feb. 2026), we have just released the following feature enrichments in the pLDP:
- RF-based Staging is also included in the forecast.
- API for picking can be used for executed workload recording.
- An introduction of aggregated historical workload data, to provide long-term forecasts for future releases.
- The forecast cards are directly integrated into the FIORI Warehouse KPI app, with a refined UI

Where can I find more information on the released features?
We have recorded the feature demos for AI-assisted predictive labor demand planning on our IRIS platform:

https://sapvideo.cfapps.eu10-004.hana.ondemand.com/?entry_id=1_c6j2rizz

https://sapvideo.cfapps.eu10-004.hana.ondemand.com/?entry_id=1_pgw47fje

https://sapvideo.cfapps.eu10-004.hana.ondemand.com/?entry_id=1_hjlcr9hf

Additionally, we recommend that you read our SAP Help documentation and Release Information Note for pLDP - SAP Note 3577311

How can I configure the new Predictive Labor Demand Planning?
Great question! Last year, we hosted a Meet the Expert session detailing how to activate the new feature. To view the recording here; please register with your company email.
We've made a simple setup: just activate it in customizing and in the ISLM (Intelligent Scenario Lifecycle Management) FIORI app for your machine learning scenario. The EWM system automatically learns from then on, so no extra data training is required.

Do I need to use Labor Management (LM) to use the new Predictive Labor Demand Planning?
No you do not need to use LM here. In the case that no Labor Management is active in the EWM managed warehouses, you can still use the new pLDP.
Of course, using LM is compatible with the new pLDP. For example, if you maintain the ELS in Labor Management, the ELS will take over here as usually this activity is quite cost-intensive, so you do not want to lose that. But in the activity areas that ELS is not maintained, you can continue to use the new pLDP for the planned workload and workload forecast.

How flexible is the workload forecast?
Well, as usual, we provide our customers with different BADI enhancement possibilities, for you to influence the workload calculation as well as the interpretation of the forecast data. Our goal is that you can use these for workload planning according to the specific conditions that you have in the warehouses. You might want to check the SAP Help documentation for details.

How accurate is the new Predictive Labor Demand Planning?
We use a triple exponential smoothing algorithm in the Predictive Analysis Library to forecast the future workload based on historical workload, and so for data accuracy, data retention of the historical workload plays a key role here. In the future, we would like to provide also a comparison based on historical workload data with past forecasts. As of now, you can check it manually in the EWM system.
Also, for longer-term forecasts other than the next weeks, it depends on the data availability of long term aggregated historical data. We will work on that and carefully choose the right Machine Learning algorithm for upcoming future releases.

Which processes are supported with the new LDP feature? I would like to have the same process coverage in other warehouse processes.
As of now, it is only supported for Outbound processes, for picking, packing and staging activities. You can also use POSC (Process-Oriented-Storage-Control) together with the new pLDP features. We are aware of the customer requirements to expand the workload forecast to other EWM processes, e.g. Inbound, Production Integration, etc. We will address this matter in future releases.
Your feedback as valued customers and partners is greatly appreciated; please feel free to inform us of any ways we can further support your warehouse operations regarding this topic.

How do I know if EWM managed warehouses are eligible for using the new AI-assisted predictive labor demand planning in our EWM managed warehouses?
This is also mentioned in the central SAP Note for pLDP: SAP Note 3577311
Make sure that you fulfil the requirement mentioned in SAP Note 3642983

We are S/4HANA Cloud for EWM Private Edition customer, which releases do I need to be able to use the new LDP feature?
The minimal requirement for the eligible release is S/4HANA Cloud for EWM, Private Edition 2022 FPS0, and later releases. We have downported the 2023 FPS03 release scope already. For 2025 FPS0 release scope, we plan a downport which comes very soon. For the 2025 FPS01 release scope, we will check based on customer requirements to decide for the downport in the future. So, feel free to leave a comment.

I have tried the new LDP feature and would like to provide feedback and future development requirements. How can I reach you?
Thanks! This is exactly what we are looking for!
You are always welcome to leave a comment in this blog post or write to us in private messages. Please leave your contact information and we will contact you shortly to discuss the details.

Further reads on what's new in 2025 FPS01:

https://community.sap.com/t5/supply-chain-management-blog-posts-by-sap/sap-extended-warehouse-management-for-sap-s-4hana-cloud-private-edition/ba-p/14336378

What’s New in Subscription Order Management 2025 FPS01

2026-02-26T08:49:42.080000+01:00

What’s New in Subscription Order Management 2025 FPS01

New Release

PUBLIC

February 2026

🚀 Introducing Subscription Order Management 2025 FPS01

Advancing Agility, Intelligence, and Customer Experience Across the Subscription Lifecycle

We are excited to announce the 2025 FPS01 release for Subscription Order Management (SOM)—a significant upgrade that strengthens end-to-end subscription lifecycle processes, enhances user experience, and unlocks new flexibility for solution extensibility.

This release builds on the foundations of SAP BRIM in S/4HANA, expanding support for recurring services, improving Fiori usability, enabling phased contract management in the UI, and extending key API capabilities. Whether you manage complex subscription bundles, long-term phased contracts, consumption-based products, or recurring physical deliveries—this release elevates how business users and developers interact with SOM.

⭐ Key Innovations in 2025 FPS01

Recurring Delivery Items Now Available in Fiori Apps

Originally introduced in 2025 FPS0, recurring delivery of physical products is now integrated directly into the Subscription Contract Lifecycle Management Fiori apps. Business users can now:

Access delivery plan items via Fiori navigation

Review detailed delivery schedules (delivery plan lines) within contract item views

Manage physical product deliveries alongside digital or service-based subscriptions

This brings a consistent and modern UI for managing hybrid subscription models.

Business Benefits

Unified workspace for hybrid offerings: Bring subscriptions with digital services and recurring physical delivery products together in a single Fiori experience.

Reduced operational complexity: Reduced jumping between SAP GUI and Fiori for delivery management.

Better order accuracy and transparency: Delivery plan details are always available where subscription decisions are made.

For more information, refer to Fiori Enablement of Subscriptions with Recurring Delivery of Physical Products.

Phased Contracts — Now Manageable Directly in the UI

Previously supported only via API, lifecycle management of phased subscription contracts can now be fully handled in the UI.

New capabilities include:

“Add Successor Phase” button at item level on the subscription order user interface

Automatic delimitation of previous phases

Ability to modify attributes (pricing, quantity, durations) per phase

Clear visibility of current vs. future phases in the subscription contract

Implementation of contract changes using standard and customized change processes

This enables business teams to easily model:

Multi-year upgrades

Scheduled migrations

Stepwise expansions or reductions in services

Timesliced price adjustments

Business Benefits

Empowers business agility: Sales and operations teams can model multi-phase deals (e.g., gradual upgrades or scheduled transitions) without IT intervention.

More accurate revenue planning: Contract phases reflect real commercial timing—improving forecasting and billing accuracy.

Reduced implementation cost: Eliminates the need for custom UI extensions or external tooling to manage phase transitions.

For more information, refer to UI Enablement of Phased Contracts .

Fiori UX Enhancements for Subscription Lifecycle Management

FPS01 brings a redesigned user experience to the Manage Subscription Contract Lifecycle Fiori app.

What’s new:

Contract State Hierarchy View
See contract structure across current, planned, and expired states in a single intuitive hierarchy.

Harmonized Navigation Between WebUI and Fiori
All subscription-related navigations now default to Fiori apps and navigation to WebUI is integrated into a single menu, offering seamless transitions and reduced UI fragmentation.

Improved Timeslice Navigation
At the main item level, user navigation is updated for cleaner contract timelines.

These refinements simplify review of complex contracts—especially multi-level bundles and contracts with phases.

Business Benefits

Faster decision making: Clear visibility into contract phases (planned, current, expired) helps business users understand the contract lifecycle status instantly.

Lower training and support cost: Unified WebUI → Fiori navigation reduces confusion and simplifies onboarding.

Improved productivity: Timeslice-based navigation avoids mis-clicks and ensures users land on relevant contract elements.

Maintain Plant and Storage Locations in Subscription Orders

For organizations delivering physical goods alongside service subscriptions, FPS01 introduces plant and storage location fields for:

Subscription items

Sales items

Master agreements

Highlights:

Existing plant determination logic is respected

Plant / storage locations flow to subscription contracts and SD sales orders

Supports scenarios with multiple fulfilment centres

This greatly improves operational accuracy for hybrid subscription models.

Business Benefits

Operational accuracy for hybrid models: Ensures the correct fulfilment location is assigned for physical components of subscription offerings.

Improved logistics coordination: Enables tighter alignment between subscription sales and downstream supply-chain processes.

Minimized errors in follow-on documents: Correct plant/storage values automatically flow into subscription contracts and SD sales orders.

For more information, refer to View and Update the Plant and Storage Location Values While Creating a Subscription Order .

Other Enhancements

➡️Register Payment Cards Directly in Subscription Transactions

A major usability upgrade: Payment cards can now be registered directly on subscription orders or solution quotations.

Key improvements:

No prerequisite to register the card under the business partner

Card token (from Digital Payments Hub) is stored in the transaction

Token is passed automatically to the subscription contract and provider contract

This removes friction in subscription sales scenarios and accelerates order capture.

Business Benefits

Faster checkout and quote-to-contract cycles: Direct card registration removes bottlenecks during order and quotation capture.

Reduced fallout in sales workflows: No need to navigate to business partner master data to register payment details.

Enhanced customer experience: Sales teams and self-service portals can collect payment details more seamlessly.

For more information, refer to Registering Payment Cards at Subscription Transaction Level .

➡️ Manage Sub-Items During Contract Extension via API

The Change Quotation API now allows the following actions on product bundles:

Adding new sub-items

Deleting existing sub-items (with constraints)

Extending selected sub-items during contract renewals

This provides developers a fine-grained control mechanism to adjust complex subscription bundles during contract extension cycles.

Business Benefits

Greater flexibility in contract adjustments: Supports real-world scenarios such as product bundle expansions or optional service removals.

Improved automation for renewals: System-managed sub-item logic eliminates manual adjustments during extension cycles.

Stronger governance: Mandatory bundle rules are enforced, ensuring compliance with product design.

For more information, refer to Enhancements to the Solution Quotation (A2X) OData API .

➡️Recurring Sales Items with Delivery Plans — Now Supported in APIs

The OData APIs API_SUBSCRIPTIONORDER and API_SUBSCRIPTIONCONTRACT now support:

Creation of subscription orders that include recurring sales items with delivery plans

Reading subscription contracts containing recurring sales items

Delivery plan data via 1:n associations

This enables automation and integration for businesses with periodic physical deliveries tied to subscriptions.

Business Benefits

Better integration with external systems: Partners and customers can automate creation of subscription orders with periodic deliveries.

Consistent multi-channel orchestration: API parity ensures front-office systems (CPQ, commerce, custom portals) behave exactly like SAP SOM.

Insightful downstream reporting: Delivery plan data is available programmatically for planning, fulfilment, and analytics.

For more information, refer to Enhancements to the Subscription Order (Version 0002) OData API and Enhancements to the Subscription Contract - Read OData API .

➡️Best Practice Content Enhancements (Scope Item 7WB)

The 7WB - Subscription Order Management – Master Data and Basic Functions scope item has been enhanced so that you can now execute change processes on an existing subscription contract and implement the following.

Enable trigger of change process on an existing contract supporting relevant change processes

Submit the change order to update the subscription contract

Replicate these changes to FICA provider contract

Enable replication of the changes to FICA provider contract, via the order distribution interface

Leverage the subscription contract lifecycle app to display the new subscription contract

The enhancement builds on the previous capability of creating new subscription contracts and accelerates customer onboarding with ready-to-deploy business scenarios.

Business Benefits

Accelerated project timelines: Customers can adopt Subscription Order Management with lower setup complexity.

Reduced implementation risk: Standardized flows minimize the likelihood of design issues during rollout.

Improved cross-team alignment: Consistent best practice processes help cross-functional teams work more cohesively.

For more information, refer to Subscription Order Management – Master Data and Basic Functions (7WB) .

🔍 Additional Resources

Subscription Order Management 2025 FPS01 has been released to customers on Feb 25th, 2026. For more information, check out the following links:

What’s New in Subscription Order Management 2025 FPS01 (Go to Finance > Billing and Revenue Innovation Management > Subscription Order Management)

Product Assistance on the SAP Help Portal

Integration Guide: Integration Guide for S/4HANA BRIM using SOM

Business AI in BRIM:

Joule Help Page

Initial Setup of Joule for BRIM

Questions and Answers for Subscription Order Management in SAP Community

SAP BRIM Customer Influence Portal > Opportunity area “Solution Quotation and BRIM”

💬 Final Thoughts

The Subscription Order Management 2025 FPS01 release represents a major step forward for enterprises managing complex subscription offerings. With improved UX, enriched APIs, expanded delivery plan support, and powerful phased contract capabilities, this release empowers organizations to scale subscriptions with greater agility, control, and customer focus.

SAP S/4HANA 2025 FPS1: What's in it for the Utilities Industry?

2026-02-27T09:10:53.250000+01:00

The first feature pack (FPS1) of the SAP S/4HANA 2025 has just been released to customers. Below is an overview of its key innovations tailored specifically for the utilities industry:

1. Enterprise search for utilities master data
Using the Enterprise Search from Fiori Launchpad, you can now search various utilities-specific master data - such as premise, utility installation, point-of-delivery, device and device information record. Starting from the search results, you can directly access frequently used apps and transactions for each master data entity. This intuitive approach significantly reduces search time and enhances operational efficiency.

2. Graphical display of utilities interval data
A new Fiori app Display Utilities Time Series Values (F8929) is available for SAP S/4HANA Utilities, designed for the Meter Data Specialist (Utilities) role. This app delivered detailed insights into time series values from EDM profiles through a graphical representation that combines the values with related status information.

3. Archiving of utility installations and premises and deletion of unused device information records
New archiving object ISU_EANL is now available to archive utility installations, including their related installation structure and points-of-delivery. Additionally, the archiving object ISU_EVBC enables the archiving of premises. Especially the first one (ISU_EANL) comprises comprehensive validations for dependent data, making sure that all related documents and master data entities are archived beforehand. Furthermore, a new report REG_DEV_INFO_REC_CLEANUP, has been introduced to delete unused device information records.

4. More flexible completeness check for profile values
Based on customer feedback from the SAP Continuous Influence session for SAP S/4HANA Utilities, transaction EEDMPROFVALCHECK (Check Whether Profile Values Are Complete) has been enhanced:

The meter reading unit and service type of the utility installation are now available as additional selection criteria.
Existing BAdI ISU_BI_RTP_STATUS_CHECK method STATUS_CHECK_EXT now provides more precise information regarding the billability of profile values.

5. Additional CDS views for time series data

SAP S/4HANA Utilities now includes multiple CDS views for time series data extraction, supporting various interval lengths, status fields, and related attributes. For details on these new CDS views, refer to the What's New.

6. Enhancements in SAP Market Process Management

The What's New section in the SAP Help Portal outlines several enhancements related to SAP Market Process Management. For full details, please refer to the following link: What's New . You can find utilities-related content in a dedicated section under Industries > Energy & Natural Resources.

Finally - here is a list of previous SAP Community blog posts, beginning with release SAP S/4HANA 2023:

SAP S/4HANA release (and feature pack)	Available since
2023	Oct 2023	SAP S/4HANA 2023: What’s in it for the Utilities Industry?
2023 FPS1	Feb 2024	SAP S/4HANA 2023 FPS1: What’s in it for the Utilities Industry?
2023 FPS2	Oct 2024	SAP S/4HANA 2023 FPS2: What’s in it for the Utilities Industry?
2023 FPS3	Feb 2025	SAP S/4HANA 2023 FPS3: What’s in it for the Utilities Industry?
2025	Oct 2025	SAP S/4HANA 2025: What's in it for the Utilities Industry?

What is new in S/4HANA Manufacturing for Production Engineering & Operations (PEO) in 2025 FPS1

2026-02-27T14:20:17.172000+01:00

With the 2025 FPS1 release of SAP S/4HANA Manufacturing for Production Engineering and Operations (PEO), SAP continues to strengthen its manufacturing capabilities by delivering features that boost engineering efficiency, improve shop floor flexibility, and streamline daily operations.

In this blog, I’ll walk you through the key innovations included in this feature pack – and what they mean for production engineers, supervisors, and manufacturing operations teams.

Production Engineering Efficiency Enhancements

🔁Alternative Sequences of Operations in Shop Floor Routings

PEO now allows production engineers to create alternative and parallel sequences directly within shop floor routings.

This is especially helpful when:

Work can be done on an alternative machine
Different inspection paths exist
Certain steps can be bypassed
Different lot-size specific process flows are required

Supervisors can switch to these sequences at the order level, giving operations more flexibility without modifying the standard routing.

Why it matters:

Greater process and scheduling flexibility → reduced lead time, better resource utilization, and faster response to shop floor contingencies.

🧩 Mass Management of Components in Order-Specific Shop Floor Routings

Engineers can now manage multiple components at once—adding, editing, or replacing them in a single table-based view.

Items marked Not Editable remain protected.

Why it matters:

Huge efficiency gains during order changes and rework scenarios, where batch updates to components are common.

🔄Manage Alternative Components Using Alternative Item Groups (AIGs)

PEO now supports creating and managing alternative item groups for order-specific shop floor routings.

You can:

Add, edit, or remove alternative components
Move components into new/existing AIGs
Create new AIGs for new components

Why it matters:

Allows the shop floor to use valid alternatives without touching master data — a big win for flexibility and compliance.

🔧Flexible Rework Routings

Engineers can now create rework routings with flexible processing, enabling:

Sequence-independent processing
Cross-operation predecessor relationships

This requires the production order’s routing to have flexible processing enabled as well.

Why it matters:

Rework becomes smoother and more adaptable, reducing bottlenecks and manual coordination.

📝 Long Texts for Externally Processed Operations

Long text descriptions can now be authored externally processed operations — and the system automatically transfers this text to:

The production order
The purchase requisition

Why it matters:

Clearer communication with suppliers + fewer manual updates = reduced errors and faster processing.

🎨Custom Text Formats via New BAdI

A new BAdI allows companies to define custom heading formats in the rich text editor used for standard texts and work instructions.

Why it matters:

Guarantees consistent formatting aligned with corporate branding standards, without manual adjustments by engineers.

2. Flexible Production Operations Enhancements

🔀Order Split for Serialized Products with Sequences

PEO now supports splitting shop floor orders even when serialized products use alternative or parallel sequences.

PEO automatically determines which sequences remain feasible for the new order.

Why it matters:

Significant time savings by allowing completed units to progress independently, reducing waiting time and simplifying sequencing.

⏸️ Action Handlers for Hold/Release Operations

Production process specialists can now configure automated or manual actions that trigger when applying or releasing a hold—for example:

Additional quality checks
Automatic follow-on system actions

Why it matters:

More controlled, automated, and auditable hold handling with reduced manual overhead.

🛠️ Additional Code Groups for Defect Recording

Supervisors can now define additional reason code groups for defect recording. Operators can then choose from any of these groups.

Why it matters:

More accurate defect categorization → richer insights and more effective quality improvement initiatives.

Wrapping Up

The 2025 FPS1 updates for SAP S/4HANA PEO focus on one overarching theme:

Empowering production engineers and shop floor teams with flexibility, speed, and clarity.

Whether it’s expanding routing capabilities, streamlining rework, improving communication with suppliers, or making shop floor execution more adaptable, these features help manufacturers operate with greater agility and precision.

If you’re already using PEO, many of these enhancements can immediately simplify daily operations. If you’re planning a transition to S/4HANA Manufacturing, these innovations highlight why PEO continues to be a strong foundation for digital manufacturing.

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.

Demand and Supply Segmentation in SAP S/4 HANA - Segmentation Setup (Blog 1)

2026-03-02T05:51:36.101000+01:00

This blog series provides a fundamental understanding on Segmentation and its end-to-end integration with other capabilities such as Advanced ATP, Planning, Production, Supply Assignment, PPDS, EWM, etc. in SAP S/4 HANA Private Cloud Edition.

In this blog, we will focus on the Segmentation Master Data setup and assigning that to a material.

Background:

Segmentation was a feature available only for Fashion industry and due to its widespread relevancy is now accessible for all other industries too.

Why do we need Segmentation?:

Segmentation can serve both physical and logical needs.
Minimizes the number of products to be created e.g. materials with different quality grades and revisions can be set up as single material with multiple segmentation values.
Flexibility to share the inventory against different segmentation values using ATP Pool Segment setup and ARUN/MRP NM Segmentation setup.
Controls planning, production, fulfillment processes at segment level.

Basic Concepts of Segmentation:

Segmentation Structure
- Defines the structure of Segmentation set up.
- Recommended having different structures for different product categories as the characteristics and rules could be different.
- List all the characteristics to be set up under a segmentation value (e.g. Characteristic 1 – Country of Origin, Characteristic 2 – Quality Grade, etc.).
Segmentation Strategy
- You can define multiple segmentation strategies for a segmentation structure. In a segmentation strategy segmentation strategy you can define the rules to map requirement and stock segment values and much more. This has following sub nodes:
  - ARUN/MRP – Map requirement segments to stock segments (To be discussed in a separate blog later)
  - ATP Pool – Define Pool segment values for ATP (To be discussed in a separate blog later)
  - Dependent Requirements – Used when to determine requirement segments of components based on stock segment of main item (e.g. Planned Order components or Production Order components)
  - Requirement to Stock conversion – Used to determine stock segment of MRP stock proposals
  - Planned Independent Requirements – Used to consume PIR requirement segments for desired SO/STOs requirement segments
- Segmentation Scope: Define if the scope of segmentation is relevant for both demand and supply (Scope 1) or only for demand (Scope 2):
  - Scope 1 Segmentation (Both Requirement and Stock Segments): A typical use of physical segmentation such as Country of Origin, Product Revision, Quality Grades are relevant for both demand and supply segmentation, and the strategy should be set as Scope 1
  - Scope 2 Segmentation (Only Stock Segment): Certain logical segmentation uses cases such as channel based (ECOM, Retail and Wholesale) relevant only from demand side and hence the segmentation strategy is recommended to be set as Scope 2. (Note – Logical Segmentation set as Scope 1 will have downstream impacts in deliveries and warehouse operations and should be evaluated case to case basis)

Below steps demonstrate setting up of basic segmentation strategy and assigning to material master:

Step 1 – Create Segmentation Characteristics

Go to transaction CT04
Enter below details and save the characteristics

Step 2 – Set up Segmentation Structure

Go to transaction ‘SGT_SETUP’ and click on ‘Create’. Enter the structure name and description and save.

Once saved, go to change mode and double click on the structure. Enter the characteristics created in step 1. Once done click save.

Note – If you want to enable blank values for any of the characteristics, ensure that you select ‘Enable blank’ against each characteristic in above grid screen.

Step 3 – Create Segmentation Strategy

Go to change mode of the segmentation strategy and then right click on structure created in step 2 and select ‘Add Segmentation Strategy’ and click on save.

Go to Change mode and then double click on the segmentation strategy. You can manually add the segmentation values or generate them as shown below

Generate Segmentation strategy once above steps are completed.

In above step, system generates 1:1 Segmentation for all notes by default. We will discuss the details of individual nodes later.

Step 4 – Assign Segmentation Strategy to Material Master

Once Segmentation setup is completed, assign the segmentation strategy to the material as shown below.
‘Assign the segmentation strategy’ at Material level in ‘Basic Data 2’ Tab

‘Assign the segmentation strategy’ at Plant level in ‘Plant data/stor.1’ Tab and save the material.

Key points to be noted:

You observe that batch management will be automatically set when segmentation is activated
You can have segmentation relevancy for one plant and not for another plant for the same material
You can have different segmentation strategies for different plants for the same material if they belong to same segmentation structure

Hope this blog helps to provide a basic understanding of “Segmentation” to define appropriate settings to setup and assign to a material.

SAP Help Documentation:

Segmentation

Blog Series:

Demand and Supply Segmentation in S/4 HANA - Segmentation Setup

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.

Introducing SAP Cloud ERP Private, Nonproduction Usage: A Flexible Path to SAP S/4HANA Private Cloud

2026-03-06T04:37:34.288000+01:00

Introduction

Many SAP ERP Central Component (SAP ECC) cloud customers face a necessary upgrade because of upcoming end-of-support deadlines for SAP ERP 6.0 private cloud systems on Enhancement Packages 6-8 (mainstream maintenance ending in 2027 and extended maintenance in 2030).

SAP ECC (SAP ECC 6.0 with Enhancement Package 6 to 8 ) will move to Customer Specific Maintenance starting 1 January 2031. This also means that the SAP ERP, private edition offering will effectively have an end of availability on 31 December 2030. Because of this, many customers will face a time-sensitive transition period. During this time, they may need to run both their existing SAP ERP 6.0 system and the new SAP S/4HANA Private Cloud system in parallel—especially for non-production environments like testing, development, and QA during migration.

Having both environments available can accelerate transformation initiatives, allowing teams to leverage bundled cloud components for innovation, testing, process redesign, and early adoption of new capabilities while the legacy system continues to support ongoing operations.

At the same time, customers seeking a more cost-optimized transition path now have a new option that provides earlier access to a non-production environment without requiring a full parallel subscription. This gives customers greater flexibility to plan and execute their transformation while managing overall subscription costs.

To support this approach, we are introducing SAP Cloud ERP Private, nonproduction usage. This offering enables unlimited non-production use of SAP S/4HANA Private Cloud during the transition period, allowing customers to perform migration and testing activities without incurring the cost of a full production subscription.

How this helps, for example.

Explanation:

Without SAP Cloud ERP Private, nonproduction usage
In Year 2, the SAP ERP, private edition subscription is needed for the production systems, but as non-productive environments are gradually upgraded to the new S/4HANA Private Cloud version, they also need SAP Cloud ERP Private subscription. This overlap leads to simultaneous subscription costs of both SAP ERP, private edition and new SAP Cloud ERP Private systems.
With SAP Cloud ERP Private, nonproduction usage
In Year 2, production continues under the old SAP ERP, private edition subscription, while the non-productive environments are covered by the new SAP Cloud ERP Private, nonproduction usage product. SAP Cloud ERP Private, nonproduction usage can be applied to an unlimited number of non-productive systems, allowing full coverage without triggering a full double subscription. In Year 3, all environments have migrated and can now be covered with the normal SAP Cloud ERP Private subscription.

Benefits of SAP Cloud ERP Private, nonproduction usage

Removes simultaneous subscriptions during the transition phase
Supports testing and validation without the need for exact timing of the switch to a new subscription
Access to the SAP AI portfolio in the nonproduction environment, not available with SAP ECC [SAP ERP 6.0]
You only pay for limited support for the non-productive systems during the migration period
Covers an unlimited number of non-productive systems
Gives customers the flexibility to plan and execute the migration properly
The transition period can be as long as needed, keeping the end of support date in mind.
SAP Cloud ERP Private, nonproduction usage is an addition to the SAP ERP, private edition subscription, extending the product support to S/4HANA Private Cloud in the transition phase.
Helps organizations meet upgrade deadlines without budget overruns

NEW! - Enterprise management layer for SAP S/4HANA - SAP S/4HANA Cloud Private Edition 2025 FSP00

2026-03-06T10:08:16.034000+01:00

On Monday March 2nd, 2026, the enterprise management layer team has just released its latest template system based on SAP S/4HANA Cloud Private Edition 2025 FSP00.

The enterprise management layer is not to be confused with model company for SAP Business Suite.

The focus of the enterprise management layer template is large multinational organizations operating in many countries around the world. It provides the foundation of your SAP S/4HANA Cloud Private Edition by covering all Line of Business. It is by design industry agnostic, so that it can easily be used in all the industries covered by SAP S/4HANA.
Model company for SAP Business Suite focuses on the industry-specific content and is available for Germany and the United States.

Some of the Model company for SAP Business Suite is compatible and can be applied on top of the enterprise management layer.

The new release of the enterprise management layer is based on a selected number of scope items (220+) from SAP Best Practices for SAP S/4HANA Cloud Private Edition and specific content only available in the enterprise management layer. It covers up to 49 countries; 43 available through SAP Best Practices for SAP S/4HANA Cloud Private Edition and 6 only available through the content built by the enterprise management layer team. The system is delivered with 25 languages and is fully Fiori enabled.

The offering is split under in three groups as depicted below:

Standard Scope: activation of SAP Best Practices scope items that do not require a specific SAP license other than the core SAP S/4HANA Cloud Private Edition
Scope Options: activation of SAP Best Practices scope items that require specific SAP license
Service Options: activation of content only available in the enterprise management layer

Compared to the previous versions of the enterprise management layer, besides the fact that the content deployed by the activation of SAP Best Practices for SAP S/4HANA Cloud Private Edition is based on the updated 2025 FPS00 content, the following specifics shall be mentioned.

New scope items:

Treasury and Risk Management (Optional scope):
- TRM12 - Master Data: Treasury Management*
Order and Contract Management (Standard scope)
- 3TD - Internal Commissions Settlement for Sales (replaces OTC30)
Service Operations & Processes (Standard scope)
- 7GB - In-House Service (mainly description change)
Extended Warehouse Management (Embedded) (Optional scope)
- 7VC - Synchronous Goods Receipts in EWM - External Procurement
- 7VD - Material Replenishment with Kanban – Stock Transfer within EWM
- 7GP - Basic TM/EWM – Inbound Advanced Shipping and Receiving
- 7GQ - Basic TM/EWM – Outbound Advanced Shipping and Receiving
- WM05D - Cross-Plant Stock Transfer with EWM in both Plants with Different Serial Number Profiles*
Advanced Shipping & Receiving (Optional scope)
- 7VE - Advanced TM-EWM – Inbound Advanced Shipping and Receiving
- 7VF - Advanced TM-EWM - Outbound Advanced Shipping and Receiving
Advanced Variant Configuration (Optional scope)
- 7KW - Customer Returns for Material with Variant Configuration
Product Compliance (Optional scope)
- 7DO Product Compliance Document Authoring
Embedded Production Planning and Detailed Scheduling (ePP/DS) (Optional scope)
- 7UV Make – to – Stock Production - Discrete Manufacturing
- 7V9 Make – to - Order Production - Discrete Manufacturing

* enterprise management specific

Removed scope items:

Order and Contract Management
- 2QS - Analytics for Sales - Central Stock with Returns
- OTC30 - Internal Commissions Settlement for Sales (replaced by 3TD)*
Extended Warehouse Management (Embedded)
- WM01 - Synchronous Goods Receipts in EWM For External Procurement (replaced by 7VC)*
- WM02 - Synchronous Goods Receipts in EWM for Kanban (replaced by 7VD)*

* enterprise management specific

Updated Localization content:

Country	Feature	Description
AT	Annual Financial Statement	OBSOLETE: Use the Annual Financial Statement App to prepare an XML file that contains the annual financial statements of your company that you submit to the Austrian commercial register. You submit the data using the ERV-JAb data service (version 03.31).
AT	Annual Financial Statement	New report supporting ERV JAb 4.0 is available.
BE	Annual Sales Listing	UPDATED: The Report has been adjusted so that the Representative information is optional and only populated in the XML, if the related Reporting Parameters are maintained.
BE	Payment formats	The following Payment Formats are available BE_CGI_XML_CT_V9 and BE_CGI_XML_DD_V8.
CA	Tax Jurisdiction Codes in Document and Reporting Compliance	It is possible to select more than one Tax Jurisdiction Code as part of the selection criteria of reports Canada QST Return, Canada PST British Columbia Return, Canada PST Saskatchewan Return, and Canada PST Manitoba Return.
CH	Processing Incoming Payments with LSV+ Reference	Referred to the user-exit and solution required to populate the LSV+ Reference if required and how to use it in incoming payment processing.
CH	Cash Flow Statement	You can generate a Cash Flow Statement report using the Indirect Method (also known as C. Tableau des flux de trésorerie).
CL	eBoleta additional fields	The following fields are populated in the XML: • CorreoRecep - refers to the re-ceiver e-mail address • TelefonoRecep - refers to the receiver telephone number • MedioPago - refers to the pay-ment method
CN	Cash Flow Statements	OBSOLETE: Companies in China are required to generate a statement about the changes in their cash and cash equivalents in each period. You can prepare the cash flow statement in the required format as defined by law
CN	Cash Flow Statement	New features are available such as data preview, correction phase and manual adjustments.
CN	Balance Sheet / Income Statement	New features are available such as being able to call the Display G/L Account Balances - Summary/Journal Entry Views app from within.
CN	Splitting Cells with Multiple Values	With this feature, you can split cells with multiple values when exporting to a spreadsheet by choosing the option Split cells with multiple values.
CN	Aging Report (Accounts Receivable/Accounts Payable)	UPDATED: A new selection criterion Reporting Currency is available and allows the user to select between Local Currency, Functional Currency, Global Currency, and First Freely-Defined Currency to display the amounts.
CO	UGPP Reports	The UGPP reports allow you to generate your Trial Balance (report category CO_UGPP_TRIAL_BALANCE) and Auxiliary of Accounts (report category CO_UGPP_AUX_ACCT) and fulfill the statutory reporting requirements from the Unidad de Gestión Pensional y Parafiscales. The output is in a CSV format.
CO	Account Balance Ledger Reporting	The Monthly Ledger (report category CO_ACCT_BAL_LEDGER) report enables you to generate a monthly balance of accounts and subaccounts. The output is in a CSV format.
CO	DIAN 350 Withholding Tax Form	You can generate the DIAN 350 Withholding Tax Report which reports on all types of Withholding Tax and generates the DIAN 350 PDF Form.
DE	E-Bilanz	UPDATED: The E-Bilanz (electronic financial statement for Germany) is the required electronic tax filing in Germany. Updated with latest Taxonomy.
DE	Reduced Rate on User Rights	When processing foreign supplier invoices related to User Rights a lower withholding tax rate should be applied for transactions amounting to up to EUR 10,000 in case there is a Double Tax Agreement between Germany and the country of the supplier
DE	VAT Return Format	UPDATED: A new XSD format starting January 1st, 2026 is available.
ES	EC Sales List Modelo 349 – Credit Memo Referencing	All relevant credit memo must reference an original invoice. To reference credit memo, the Rebate Reprocessing Activity can be used.
ES	Cadastral Reference	Modelo 115 reports on withholding tax related to income from property renting or leasing.
ES	Tax Register Book to SII through SAP Document and Reporting Compliance, Cloud Edition	UPDATED: it is now possible to exchange the electronic documents using SAP Document and Reporting Compliance, Cloud Edition
ES	B2G invoices through SAP Document and Reporting Compliance, Cloud Edition	UPDATED: it is now possible to exchange the B2G electronic invoices using SAP Document and Reporting Compliance, Cloud Edition
ES	VERI*FACTU	You can exchange electronic invoices through the VERI*FACTU system
FR	Payment Formats	New Payment Format FR_CGI_XML_CT_V9 available
GB	Payment Formats	New Payment Formats GB_CGI_XML_CT_V9 and GB_CGI_XML_DD_V8 are available
HR	Fiscalization	Fiscalization refers to a set of measures implemented by companies in Croatia that provide an overview of cash transaction revenues. When a buyer pays the seller by cash, the probability of the seller evading tax by not declaring the cash payments is very high. To prevent this, the tax authority in Croatia, has instructed sellers to declare all their cash transactions.
HR	Overdue Receivable (OPZ-STAT-1)	The Overdue Receivable report can be executed through Document and Reporting Compliance
HR	Withholding Tax Reporting	You can report on suppliers’ transactions subject to Withholding Tax such as: • Dividends and shares • Services of foreign legal entities such as business consultancy, audit, tax consultancy, research markets etc. • Interests other than the pre-scribed exemptions in accord-ance with the provisions of arti-cle 31 of the Corporate Income Tax Act • Payment of copyright and other intellectual property rights • Service of companies in other countries
HR	B2B eInvoicing	From January 1st, 2026, all B2B invoices must be exchanged electronically. The system now generates electronic documents for B2B transactions. You can also generate electronic docu-ments for customer payments.
HU	Monthly VAT Declaration Format (2025)	UPDATED: New chapter about VAT Return Form 2665A version 2, and the latest requirements in terms of Reverse Charge Tax for some specific products
ID	BPPU Withholding Tax Report	The BPPU Withholding Tax Report is known locally as the Bukti Potong Pajak Unifikasi and generates an XML file with the related Withholding Tax levies.
ID	BPNR Withholding Tax Report for Foreign Vendors	The BPNR Withholding Tax Report is known locally as the Bukti Potong Non-Residen and generates an XML file with the related Withholding Tax levies.
ID	VAT OUT (CORETAX)	The VAT OUT (Coretax) report enables you to generate a list of VAT items on sales to customers in an XML file. You can download the generated XML file and upload it to the Coretax system.
KR	Entertainment Expenses Report	Providing additional information about the prerequisites to run the entertainment expense report and the report output.
KR	VAT Report	Providing additional information about the prerequisites for generating a successful VAT Report and the various mandatory/optional outputs supported.
KR	Monthly Submission of Withholding Tax Reports	It is now possible to submit the Withholding Tax reports for Business and Other Income monthly.
LU	SAF-T	Article 70 of the Luxembourg VAT law and Administrative Circular nº 742, published in the Mémorial A-206 (Official Journal of the Grand Duchy of Luxembourg), effectively amending the VAT Law requirements determines that all businesses using electronic accounting systems are required to provide their bookkeeping data in a legible and intelligible electronic format, upon request by the Luxembourg Tax Authorities, in the form of the FAIA file (Fichier d'Audit Informatisé AED). UPDATED: Generation of Periodic VAT Return through Document and Reporting Compliance
LU	New Payment Formats	The following Payment Formats are available LU_CGI_XML_CT_V9 and LU_CGI_XML_DD_V8.
LU	Fixed Assets Appendix of Annual VAT Return	This report enables you to generate an XML file with fixed assets information to be submitted together with the Annual VAT Return report to the tax authorities through the eCDF platform.
MX	Withholding Tax Declaration	OBSOLETE: This report is now obsolete and replaced by the electronic submission of Withholding Tax Certificates (see OSS note 3361404 - Sunset of Mexico Statutory Report for Withholding Tax reporting in DRC)
NL	Financial Audit File	UPDATED: The Financial Audit File is a standard for creating a xml file containing relevant data in Financial Accounting for the Netherlands. The file contains master data, opening balances and transactions that were processed during a certain period. The Financial Audit File is used by the Dutch tax authorities and approved accountants to perform audits of the financial administration of Dutch companies. The file version available is 4.0
NO	General Ledger Account Line Items, Customer Line Items and Supplier Line Items Reports	A new configuration parameter has been introduced to limit the number of line items for the PDF generation to avoid the issues in ADS Server
PL	Reverse Charge VAT Declaration (Form VAT-27 (2))	OBSOLETE: In Poland, certain transactions are subject to reverse charging. This means that the obligation to settle the applicable VAT amount rests with the purchaser and not the ven-dor. The vendor issues an invoice for 0% VAT (in enterprise management layer Tax Codes A6 and A7 are available) and then reports the reverse charge to the tax authorities through a supplement to the standard periodic VAT declaration. This supplement is the Reverse Charge VAT Declaration (form 27) provided to the authorities in XML format.
PL	Official Document Number	You are required by law to number the documents you post to your customers, for example, customer invoices or credit memos, following defined rules defined by the tax authorities. Each invoice successfully submitted to the KSeF (National System of e-Invoices) receives a unique identifier known as the KSeF Invoice ID, which is distinct from the invoice ID (number) issued by the sender.
PL	SAF-T JPK_WB	The SAF-T Bank Statements report (PL_SAFT_WB) enables you to generate the report on bank account transactions in an XML file format.
PL	Withholding Tax	Added a chapter about Withholding Tax requirements and set up in enterprise management layer.
PL	Algorithm for KSeF Reference Numbers	You can use algorithm 805 in your Posting Rules to clear open items based on the KSeF Reference Number
PT	Purchase Account Procedure	UPDATED: If Purchase Account Management is active, which is the case for Portugal, additional postings are carried out during the posting of receipts of goods and invoices.
PT	Asset Classes	UPDATED: Specific Asset Classes relevant to Portugal are available in enterprise management layer.
PT	QR Code	UPDATED: A QR code and additional information such as the ACTUD number are printed on the billing documents generated from Sales and Distribution
PT	Additional Tax Box Structure Types for the Periodic VAT Return and Annexes Report	If your main location is not the continent, but the Azores or Madeira, you can use new parameters to set your Tax Box Structures accordingly
RO	Account Card	Report FIŞĂ DE CONT can now be reported through Document Reporting and Compliance
RO	Document Journal	Report REGISTRUL JURNAL can now be reported through Document Reporting and Compliance
RO	Cash Journal	The Romania Cash Journal report enables you to generate your Cash Journal (local name: REGISTRUL DE CASĂ).
RO	General Ledger with Corresponding Accounts	Report CARTEA MARE can now be reported through Document Reporting and Compliance
SA	Vendor Certificates	UPDATED: Suppliers are required to maintain several certificates that are pre-requisites for doing business in the country. For example, all suppli-ers that have 100,000 Saudi Riyals in capital are legally required to register with the Commercial Register Office and are issued a commercial registration certificate with a Commercial Registration Number (CRN). These certificates are only valid for a limited time and must be re-newed periodically. Added new Business Partner Certificates functionality.
SA	VAT Return Format	UPDATED: The Saudi Arabia VAT Return statutory report has been updated to generate a PDF output that is like the online form provided by GAZT. If you have maintained the International Address Version in Arabic in your Company Code the address is populated in Arabic in the Arabic Output Form
SK	VAT Return	A new VAT Return form is mandatory from July 1st, 2025, following the introduction of the new reverse charge mechanism on imports from outside the EU and new VAT rates.
TH	Branch Code optional for non-VAT registered Business Partners	The Branch Code is now optional for non-VAT registered Business Partners (foreign or natural person)
TR	New Value Mapping UBL_DOC_TYPE	A new value mapping UBL_DOC_TYPE is available for Delivery Notes
XX	Display G/L Account Balances in Country/Region Specific Format	UPDATED: This App displays general ledger account balances for specified fiscal periods and in a format based on country/region -specific accounting practices. From enterprise management layer based on SAP S/4HANA Cloud Private Edition 2025, the App has been renamed.
XX	Local Chart of Accounts	UPDATED: List of Local Chart of Accounts available in enterprise management layer and which Financial Statement Versions is using them
XX	Financial Statement Versions	UPDATED: List of Financial Statement Versions available in enterprise management layer.
XX	Flexible Billing Document Numbering	UPDATED: Reference to Flexible Billing Document Numbering on how to address country specific billing document numbering required in Spain and Portugal
XX	Outgoing Payment Methods	UPDATED: list of outgoing payment methods per country including payment format
XX	Incoming Payment Methods	UPDATED: list of incoming payment methods per country including payment format
XX	Special features in Document Reporting Compliance	Added a note about the need to activate Business Function GLO_DRC to activate the special features or not.
XX	International Address Versions	Referring to the functionality of International Address Versions and how to activate them
XX	Country-specific fields in Manage Journal Entries	Referring to which Country specific fields are available in App Manage Journal Entries
XX	Run Statutory Reports App Updates	Various new features are available in the Run Statutory Reports App
XX	Manage Document and Reporting Compliance App	UPDATED: Update list of Fiori Apps and relevant SAP Business Roles

What’s New in Asset Management in SAP Cloud ERP Private 2025 FPS01

2026-03-06T13:35:08.631000+01:00

SAP Cloud ERP Private 2025 FPS01 release delivers a strong collection of enhancements across Asset Management, with improvements in maintenance execution, safety, planning, technical object management, and extensibility.

SAP S/4HANA Cloud Private Edition (the foundation of SAP Cloud ERP Private) strengthens efficient, data‑driven maintenance in this release while elevating user experience and process consistency across the entire asset lifecycle.

In this blog post, you’ll find a curated overview of the most important innovations, grouped by theme and written for maintenance technicians, planners, reliability engineers, and integration partners who rely on SAP to keep operations running safely and efficiently.

For a broader look at what’s new across other lines of business in the SAP Cloud ERP Private 2025 FPS01 release, don’t miss the blog by Yannick Peterschmitt: What’s New in the SAP Cloud ERP Private 2025 FPS1

Table of content:

Safety, compliance & field execution excellence
- Isolation Management in Permit to Work – Lockout/Tagout (LOTO)
- Associated work permits in Manage Maintenance Orders app
- Inspection checklist enhancements
- After‑job recording for unplanned work
- New capabilities in Perform Maintenance Jobs app
Maintenance request & work pack enhancements
- Improvements in Screen Maintenance Requests app
- Custom logic to add e‑mail recipients for job pack outputs
Planning and strategy enhancements
- Additional functionality in Manage Maintenance Plans and Items apps
- Extended planning bucket capabilities
- Improvements for phase control code and analytics based on phases
Master data and technical object innovations
- Reuse value help app for technical objects
- Hierarchy structure view for reference structures
SAP Asset Performance Management
More information

Safety, compliance & field execution excellence

Isolation Management in Permit to Work – Lockout/Tagout (LOTO)

The 2025 FPS01 release introduces a fully embedded Isolation Management capability that brings the complete Lockout/Tagout (LOTO) lifecycle into SAP S/4HANA Asset Management. Through new configuration options and dedicated Fiori apps, maintenance organizations can structure and govern how isolation activities are defined, prepared, approved, and executed.

A new customizing section enables planning plants to specify isolation certificate behavior, certificate and template types, number ranges, and approval setups. The Manage Isolation Certificate Templates app (F8505) allows users to build reusable templates by adding technical objects, attaching work permit templates, assigning approvers, and adding supporting documents, ensuring consistent and compliant LOTO preparation.

Manage Isolation Certificate Templates app (F8505)

With the Manage Isolation Certificates app (F8504), users can create certificates from scratch or from a predefined template, add and process isolation items, move them through operational cycles such as tagging, testing, and untagging, assign work permits and approvals, and attach relevant documents. Printable outputs for certificates, lists, and tags support on‑site execution.

These innovations strengthen safety compliance and reduce operational risk through modernized digital isolation management, improves coordination between operations and maintenance to boost asset productivity, enhances the handling of technical objects during LOTO procedures, and increases overall usability of the permit‑to‑work process.

Check this Road Map item: Isolation management in permit to work (lockout tagout)

Associated work permits in Manage Maintenance Orders app

Work permits are now seamlessly integrated into the Manage Maintenance Orders (F4604) app, becoming available whenever a Permit‑to‑Work profile is maintained for the planning plant. A dedicated Work Permits section provides immediate visibility of permit details, including approval status, implemented precautions, certificate progress, and handout information.

Users can navigate directly to the related permit or create a new one linked to the order and planning plant. In addition, a Fiori‑based mass creation job enables work permits to be generated for multiple orders at once, using filtering criteria and template determination to streamline preparation and ensure consistent alignment with Work Clearance Management.

Work permits section in Manage Maintenance Orders (F4604) app

Inspection checklist enhancements

Inspection checklist processing receives several refinements that improve configuration, transparency, and usability across maintenance workflows. A new customizing knot centralizes all checklist‑related settings, creating a clearer foundation for managing current and future checklist configurations. Updated output forms now reflect material‑based checklists, covering serial‑number and component information in maintenance orders and work packs, ensuring documents accurately represent checklist content.

Enhancements in the Manage Inspection Checklists app (F6607) introduce richer detail in inspection lots, including quantities, reservation data, component references, serial numbers (if enabled), and new filtering options such as technical object and inspection lot status. Task lists now display a material checklist indicator, and the related API has been expanded to support reading, creating, and updating this field.

Within Manage Maintenance Orders app (F5241), checklist types are visible at operation level, cross‑app navigation to inspection checklists is supported, and actions such as “Generate Checklist” streamline preparation. Authorization checks for checklist types help ensure only permitted users can assign or modify certain checklist categories, providing stronger control over sensitive checklist usage.

Find more in the Road Map: SAP Road Map Explorer

Manage Inspection Checklists and Manage Maintenance Orders apps

After‑job recording for unplanned work

Technicians can now document maintenance activities that were performed immediately during an ad‑hoc repair, even when no prior order or confirmation existed. Using the new Confirmation of Unplanned Work processing context, they record failure data, measurements, consumed components, attachments, and time confirmations after completing the physical repair, ensuring proper traceability without delaying the actual fix.

A dedicated customizing knot controls default behaviors such as notification type, priority, and order type, and determines whether statuses like Work Completed or Job Finished are automatically applied. Authorization checks ensure only permitted users can create or submit unplanned work confirmations. Technicians can start the process either from the Perform Maintenance Jobs (F5104A) app, where the context is preselected, or from Create Maintenance Request (F1511A), where it must be chosen manually.

Once submitted, the system creates the necessary order operation (often directly in the MAIN execution stage) and enables technicians to capture all required details in a structured flow. Additional behavior, such as phase transitions or automatic technical completion, follows plant‑specific customizing settings.

Check more in the Road Map: SAP Road Map Explorer

Confirmation of Unplanned Work

New capabilities in Perform Maintenance Jobs app

The Perform Maintenance Jobs app (F5104A) receives numerous usability and functional enhancements that make job execution, time recording, and material handling more transparent and efficient. Key improvements include:

Configuration & time recording

New customizing knot for clearer setup of all F5104A‑related configuration steps.
Flexible defaulting of employee for time confirmations (logged‑in user, main technician, previous confirmation, or empty).
Introduction of Degree of Progress to capture physical work completion independently from actual work time, with UI slider and defaults based on last confirmation.

Perform Maintenance Jobs app (F5104A)

Job pausing & transparency

New pause codes for documenting why a job is paused, with optional or mandatory entry modes and full history tracking.

Notification processing

Long text templates can be applied during malfunction data capture, supporting guided, structured input and respecting notification type text rules.

Technical object visibility

New overview of object list entries with processing‑indicator editing (if authorized) and cross‑app navigation.

Material handling improvements

Transparency for EWM‑managed materials, automatically disabling Post/Return actions when required.
Better handling for batch‑managed materials, including mandatory batch entry and smart‑link navigation from material numbers.
Enhanced support for serialized materials, including value help and duplicate‑number checks during posting.

List page enhancements

A redesigned list table with more visible results, improved column management, context menu, and richer notification quick info.

Redesigned list table in Perform Maintenance Jobs app

Maintenance request & work pack enhancements

Improvements in Screen Maintenance Requests app

The Screen Maintenance Requests (F4072) Fiori app now adopts a flexible column layout so users can view the request list alongside its details in resizable, side‑by‑side columns, reducing back‑and‑forth navigation and accelerating review.

In addition, a new Change Scheduling action enables mass updates of open notifications for key scheduling fields (Priority, Maintenance Event, Required Start, Required Finish, and Final Due Date) directly from the list page; changes are captured in the History tab for traceability of updates to consequence and likelihood values.

Screen Maintenance Requests (F4072) app

Custom logic to add e‑mail recipients for job pack outputs

A new enhancement makes it easier to distribute job pack and work pack outputs to all relevant stakeholders. Using a dedicated BAdI, planners can now add additional e‑mail recipients to work pack output items, such as pick lists or instructions, through Output Parameter Determination. This logic can be activated for specific output types and e‑mail channels (To, Cc, Bcc), and supports flexible recipient management via custom tables, reusable elements, or SAP distribution lists.

At the same time, work pack creation becomes more versatile. The previous limitation restricting creation to execution or post‑execution phases is removed; planners can now enable work pack creation across the entire maintenance order lifecycle based on work pack type settings. New customizing options allow organizations to manage where restrictions apply for both phase and non‑phase‑enabled orders, increasing control and flexibility.

Custom logic to add e‑mail recipients for job pack outputs

Planning and strategy enhancements

Additional functionality in Manage Maintenance Plans and Items apps

Maintenance planners gain more flexibility and control through several usability improvements in the Manage Maintenance Plan (F5325) and Manage Maintenance Item (F5356) apps. The plan app now allows users to search maintenance plans directly by description, making it easier to identify and retrieve relevant plans.

In the maintenance item app, planners can filter items by maintenance plan status and display the plan status directly in the item list, offering clearer visibility into which items belong to which plan stage.

Manage Maintenance Plan (F5325) and Manage Maintenance Item (F5356) apps

Extended planning bucket capabilities

The planning bucket framework is expanded to give maintenance planners more control over how backlogs are grouped and prepared for execution. With this enhancement, users can define a broader and more flexible range of maintenance backlogs to be included in a reference or event-based planning bucket. This includes the ability to add additional grouping fields, enabling maintenance teams to organize work in ways that reflect real operational structures or business priorities.

For example, planners can now link an improvement project to a planning bucket, allowing all backlogs associated with that project to be bundled into a single, coherent scope. This creates a more holistic view of the work that needs to be scheduled and makes it easier to consolidate activities that naturally belong together.

These enhancements optimize the scope of maintenance backlogs planned within a given period, while giving planners the flexibility to reprioritize and adjust the bucket contents based on available capacity, budget, and strategic initiatives.

Improvements for phase control code and analytics based on phases

This enhancement strengthens the way maintenance organizations use the phase‑based maintenance model by improving both the usability of phase control codes and the analytics available around phase progression.

The definition of phase control codes has been simplified, so the same codes can be reused across different maintenance‑order types. This ensures more consistent behavior across teams and scenarios. The translation of both the phase control code and its description have been streamlined as well, making the codes easier to understand and apply in multi‑language environments.

In addition, new analytics allow planners to analyze the throughput of backlogs based on the average time each backlog item takes to move through the maintenance phases. This enables better visibility of bottlenecks and helps identify root causes behind slowdowns or delays. The result is clearer insights into phase progression and improved control of the maintenance workflow.

Phase control code and analytics based on phases

Master data and technical object innovations

Reuse value help app for technical objects

Finding the right technical object, whether equipment or a functional location, often meant navigating different value help dialogs with varying layouts and search behaviours. To simplify this experience, a new unified value help has been introduced across Asset Management. This enhancement provides a single, consistent, and intuitive way to search for equipment, functional locations, and other technical objects in Fiori apps.

The new Technical Object Reuse Value Help is built on RAP‑based CDS views and delivers a more efficient, flexible search. Users can choose from multiple search templates, each surfacing different fields depending on their task, for example, focusing on labels, maintenance data, sales information, or address details.

This not only speeds up how users find the right object but also brings a more modern and consistent user experience across apps such as Find Technical Object (F2072) Manage Technical Object BOMs (F6070) and Manage Serial Numbers (F7617).

Behind the scenes, the value help objects for equipment, technical objects, and functional locations are fully reusable, so any Fiori app can adopt them without redesign, ensuring a harmonized look and feel across the maintenance process.

Technical Object Reuse Value Help

Hierarchy structure view for reference structures

Managing consistent and scalable asset structures becomes easier with two major innovations: Reference Equipment and Reference Structures. Together, they introduce a more controlled and harmonized approach to defining master data structures across plants and sites.

Reference equipment serves as a master template for creating and governing individual equipment records. It centralizes key information, such as general data, classification, measuring points, partner data, and change history, and provides a consistent basis for downstream equipment creation and updates through the Manage Reference Equipment app (F8304).

Reference structures provide a hierarchical view of reference functional locations and reference equipment, displayed in an intuitive split‑screen layout that combines structure navigation with detailed object information. Using the Manage Reference Structures apps (F8311/F8669), organizations can build and maintain standard structural templates and use them as the master for mass creation of individual structures.

Together, these capabilities help enforce consistent asset modeling across sites, enable mass changes, and reduce manual effort and errors.

Manage Reference Equipment app (F8304)

SAP Asset Performance Management

SAP Asset Performance Management integrates with SAP Cloud ERP Private and empowers asset owners, plant managers, and reliability engineers to optimize maintenance strategies, measure and improve asset performance, and follow through on your sustainability objectives. The 2602 release includes improvements such as smarter notification replication between SAP ERP and APM, expanded industrial system modeling, extensible and time-aware FMEA assessments, and streamlined rule execution. Together, these updates help reduce manual effort while improving data clarity, structural transparency, and lifecycle control. Read the complete blog post by Kate Dowle: What's New in SAP Asset Performance Management 2602.

If you’d like to stay up to date with the latest APM innovations, follow my colleague Kate Dowle who regularly shares updates and new blog posts on the topic.

Summary

With these delivered innovations, SAP S/4HANA Cloud Private Edition FPS01 significantly strengthens Asset Management capabilities, from daily technician execution to long‑term planning and technical object governance. Each enhancement contributes to safer operations, improved data consistency, and more efficient maintenance processes, supporting organizations on their path toward intelligent, connected, and resilient asset performance.

Don’t hesitate to leave a comment and check out our community page to ask your questions and engage with the experts. Also, visit the Asset Management community page. Follow the PSCC_Enablement tag to find our latest blog posts.

Follow me on LinkedIn and stay up-to-date to our latest enablement assets: Fernanda Rodrigues | LinkedIn

More information

We at Cloud ERP Product Success offer a service as versatile as our product itself. Check out the numerous offerings our team has created for you below: