What's New In Asset Management In SAP Cloud ERP Private 2025 FPS02

SAP Cloud ERP Private 2025 FPS02 marks a turning point for asset management. This release goes well beyond incremental improvements. It delivers a fully operational suite of AI agents that fundamentally changes how maintenance professionals work, moving from isolated transaction execution toward guided, end-to-end workflows where intelligent assistance handles the repetitive, high-volume, and error-prone steps. Alongside the autonomous AI story, FPS02 also introduces meaningful refinements in safety, planning, compliance, and extensibility.

SAP S/4HANA Cloud Private Edition (the foundation of SAP Cloud ERP Private) strengthens its position as an integrated, intelligent platform for enterprise asset management in this release.

In this post, you will find a curated overview of the most important innovations, grouped by theme and written for maintenance planners, technicians, reliability engineers, and integration professionals who rely on SAP S/4HANA to keep operations running safely and efficiently.

For a broader look at what's new across all lines of business in the SAP Cloud ERP Private 2025 FPS02 release, don't miss the SAP Cloud ERP Private FPS02 release overview blog.

Table of Contents

Autonomous Asset Management: AI Agents in FPS02

Maintenance Request Initiation Agent
Operational Maintenance Order Planning Agent
Maintenance Event Planning Agent
Maintenance Job Debrief Agent
Equipment Insights Agent
Maintenance Task List Agent

Further updates on FPS02 release

Maintenance notification–based inspection checklist process
Inspection checklist further process adjustments
SAP Dynamic Forms integration across asset management apps
Graphical operation dependencies across maintenance orders
Improved visibility for maintenance backlog and event-based planning
Collaborative maintenance: maintenance order integration with BNAC
Reference Structure: rule framework for change cascading
Refurbishment best practice scope items (85R and 85U)
Linear Asset Management APIs
More information

Autonomous Asset Management: AI Agents in FPS02

The Asset Operations Assistant: six agents, one coherent workflow

The headline story in FPS02 is the Asset Operations Assistant — an AI-powered orchestration layer built on the SAP Joule framework that brings together purpose-built agents covering the full maintenance workflow: from reporting a failure, through order creation, event grouping, and job execution, all the way to technician feedback and knowledge capture.

Each agent operates conversationally, in natural language, and always places the human in the loop. No record is created, no status is changed, and no data is submitted without explicit confirmation from the user. This is a deliberate design choice: the agents are meant to accelerate and improve decision quality, not replace the judgment of maintenance professionals.

All six agents run on the SAP Joule framework and are accessed through Joule in SAP Cloud ERP Private.

*Disclaimer: The Joule Assistants and Agents described in this post are currently available through SAP's Early Adopter Care (EAC) program. General availability is planned to begin in Q4 2026, with rollout continuing into Q1 2027. Not all agents require SAP S/4HANA Cloud Private Edition 2025 FPS2 — minimum system requirements vary by agent, and support for additional releases is being continuously extended through downports. For the latest on which releases support which agents, refer to SAP Note 3789370, which is updated on an ongoing basis, and the SAP Discovery Center. All other innovations covered in this post (embedded AI features, Joule skills, and machine learning scenarios) are generally available with the 2025 FPS2 release unless noted otherwise. This blog is a living document and will be updated as new assistants and agents become available in the coming weeks and months. The information here reflects publicly available SAP product documentation and roadmap materials as of October 2026. All forward-looking statements are subject to change.

Maintenance Request Initiation Agent

Create maintenance notifications with the details that actually matter in seconds.

The Maintenance Request Initiation Agent simplifies one of the most time-consuming daily tasks in asset operations: creating a maintenance notification with all relevant data. A technician in the field can describe an issue in natural language, i.e. a pump seal leaking and the agent takes it from there.

The agent identifies the technical object from a partial description, presents a list of matching equipment so the user selects the correct one, and then enriches the notification with failure codes, damage categories, cause codes, and a matching score where catalog master data supports it. It also checks for duplicate notifications on the same equipment before creating a new one — letting the user cancel or create anyway — which keeps the maintenance backlog cleaner and reduces noise and tracking effort.

For emergency scenarios, the agent creates both the notification and a maintenance order simultaneously, setting the order directly into execution. Notification type, priority, and start/end dates are captured in a single conversational exchange, with a confirmation step before any record is written to the system.

The outcomes are direct: faster reporting regardless of IT experience, significantly higher data quality and completeness, and accelerated resolution by eliminating the manual follow-up that typically accompanies incomplete notifications.

Operational Maintenance Order Planning Agent

Turn a notification into a fully structured maintenance order with reference, readiness checks, and scheduling in one flow.

Once a notification exists, the Operational Maintenance Order Planning Agent takes over the planning step. It creates maintenance orders directly from open notifications or from scratch, and it can retrieve a recommended list of reference orders ranked by match score against equipment, work center, description, and recent history, so planners reuse proven structures rather than starting blank.

The agent executes readiness checks across all order prerequisites: component availability, service lead times, production resources and tools (PRTs), and capacity constraints. It validates dates against lead times, buffers, and resource availability. Status management (ready, in execution, scheduling, locked, tack/untack) is handled.

After order creation, the agent naturally prompts the planner to bundle the order into an existing or new maintenance event, bridging directly into the event planning workflow described below.

Maintenance Event Planning Agent

Group, assign, and coordinate maintenance work across events without manual backlog triage.

The Maintenance Event Planning Agent addresses one of the more labor-intensive aspects of tactical planning: aligning work orders and notifications to the right maintenance event (for example, a planned shutdown). Planners currently spend significant time manually reviewing backlog and assigning items; this agent automates that identification and matching.

The agent creates maintenance events by event type (configurable per system), assigns relevant orders and notifications based on technical object and planning attributes, and provides visibility into assigned work and potential blockers within each event. It also identifies backlog items that fall within the event scope but have not yet been assigned, reducing the risk of leaving relevant work out of a window.

Planners can ask for open events by time range (“show me events from October 1 to October 10”), assign additional orders conversationally, and release the planning bucket, all within the same Joule session.

Maintenance Job Debrief Agent

Capture what actually happened in the field, even from a handwritten note or a photo.

The Maintenance Job Debrief Agent is built for the technician to complete a job. Its purpose is to make job confirmation and knowledge capture fast and natural, regardless of how the technician prefers to document work. A photo of the asset you just worked on, a handwritten note, an informal description: the agent reads all of it and converts it into structured, system-ready confirmation data.

The agent finds the relevant order and operational line items from the provided context, corrects spelling, structures work details, and guides the posting of time and material usage, both planned and unplanned. When multiple jobs need confirmation, the agent handles them in sequence within the same session.

Once confirmation is complete, the agent generates a structured feedback template, available in multiple languages, that the technician can review and send to the relevant planner. Crucially, the agent creates a draft in Outlook but does not send it automatically; the technician retains full control over what is communicated and to whom. This preserves operational knowledge at the point where it is richest: immediately after a job is completed.

Equipment Insights Agent

All equipment information in one view without manual data gathering across systems.

The Equipment Insights Agent brings together fragmented equipment information from across S/4HANA into a single, structured overview. It aggregates equipment master data, installation details, active orders and notifications, measurement documents, and historical maintenance records, and summarizes long texts automatically so users do not have to read a long source to understand an asset's recent history.

Beyond a static summary, the agent analyzes failure patterns, reliability indicators such as MTTR and MTBR (mean time to repair and mean time between repairs), and financial performance, linking cost data to maintenance and operational records. This gives maintenance planners, reliability engineers, and master data specialists a foundation for data-driven maintenance decisions and strategy.

The agent works on one equipment record at a time, presenting status, age, location, maintenance history, last service date, and next scheduled maintenance — a quick, comprehensive briefing on an asset, with recommendations on what to address next.

Maintenance Task List Agent

Build maintenance task lists from instruction manuals automatically and consistently.

The Maintenance Task List Agent automates the creation and maintenance of task lists by reading equipment instruction manuals (uploaded to customer-controlled storage such as SharePoint or S3). It extracts maintenance-relevant content based on the context provided by the planner, determines the appropriate operations and organizational attributes, and presents a draft task list for review and approval before any record is written.

The agent identifies whether an existing task list already exists for the equipment and reuses or updates it where applicable, rather than creating duplicates. It supports equipment task lists, functional location task lists, and general maintenance task lists. When a manual changes, the agent detects the differences and applies targeted updates, enabling consistent, scalable maintenance practices across growing asset fleets.

This capability requires document grounding functionality and a subscription to SAP BTP where the MCP server is deployed.

Further updates on FPS02 release

Maintenance notification-based inspection checklist process

FPS02 introduces an inspection checklist process directly at the maintenance notification level. A new customizing activity lets you enable checklist processing for a specific notification type and planning plant combination, and maintain the relevant checklist types for the planned inspection. Within the notification, a Checklists tab provides the checklist types and the generated checklists.

When the technical object's classification matches an inspection plan, the system can create an inspection lot for the notification and set a corresponding system status: CLGE (Checklist generated) or CLNO (No checklists found). An application log records the details, and control can be applied to the header technical object or to sub objects of the structure. A customizing flag, “Check Usage Decision at Notification completion,” raises an error if a notification is completed while inspection lots remain open, and follow-up actions on the usage decision support process automation.

Inspection checklist further process adjustments

In parallel, FPS02 continues to enhance the broader inspection checklist process across SAP Fiori. Material-based inspection checklist planning is added to the Manage Maintenance Orders app (F5241), and the corresponding material-based inspection checklist information is displayed in the Perform Maintenance Jobs app (F5104A). The Manage Inspection Checklists app (F6607) also receives user experience improvements.

For extensibility, three new BAdIs are provided for the business context “Asset Management: Inspection Checklists,” following the clean-core, low-code approach (via F6957). They enable custom logic for the inspection lot usage decision and for maintenance order object list generation — increasing the usability of checklist management and allowing the process to be adapted without modifying the standard.

SAP Dynamic Forms integration across asset management apps

FPS02 extends selected SAP Fiori apps for asset management to integrate with SAP Dynamic Forms. The following apps are scheduled to be extended with support for SAP Dynamic Forms:

Find Maintenance Notification (F2071)
Find Maintenance Order (F2175)
Find Maintenance Orders and Operations (F2173)
Manage Maintenance Notifications and Orders (F4604)
Perform Maintenance Jobs (F5104A)

Users can filter by forms attached to maintenance notifications, maintenance orders, operations, and suboperations, and navigate directly to those form instances with transparency on their processing status. This enables additional scenarios for dynamic, structured data capture in the field and in planning workflows without building custom solutions.

Graphical operation dependencies across maintenance orders

FPS02 delivers a new graphical workspace, the Manage Maintenance Order Relationship app (F8506), for visualizing and managing dependencies between operations within and across maintenance orders. This is particularly useful for organizations managing complex, multi-order maintenance windows where the sequencing of work directly impacts execution.

From the workspace, planners can create and modify multiple types of operation relationships to define and refine execution sequences, including a default start-finish relationship between operations. The integrated graphical and tabular view enables analysis of relationship networks and scheduling dependencies without leaving the planning environment. Changes to operation relationships are preserved within the planning session.

In the Manage Maintenance Orders app (F5241), these relationships are shown in a tabular view, with the option to navigate to F8506 for the graphical workspace.

Improved visibility for maintenance backlog and event-based planning

The Manage Maintenance Planning Buckets app (new version) adds an Event Relevance Check for execution objects. After building a planning bucket and assigning maintenance orders, planners can trigger a relevance check that runs in the background and evaluates whether each assigned execution object still belongs in the event, flagging changes in scope, dates, technical object status, or notifications that have been closed or marked for deletion.

Results are displayed per execution object using a color-coded indicator — white (not yet checked), green (no issues), blue (information), yellow (warning), and red (error), with the option to expand a popover showing the full list of identified issues for that object. This proactive check reduces the risk of releasing a bucket containing work that is no longer relevant or actionable.

The release also introduces automated mass assignment of maintenance work to events through manual, mass, and API-based assignment, plus intelligent backlog scoping that automatically considers subordinate technical objects in a hierarchy, providing a more complete maintenance backlog.

Collaborative maintenance: maintenance order integration with BNAC

The Manage Maintenance Orders app (F5241) now surfaces collaboration details from SAP Business Network Asset Collaboration (BNAC) directly within the order and operation views, without requiring planners to navigate away from S/4HANA.

Two new filter options — Collaboration Order ID and Collaboration Relevance — allow planners to identify which orders are synchronized to BNAC. At the order header level, the Collaboration Order ID is displayed with a popover showing aggregated progress based on operation-level collaboration statuses.

Within the Operations section, planners can filter between All Operations, Collaborative Operations, and Non-Collaborative Operations, and see the Collaboration Operation ID, Collaboration Status, and Collaboration Partner for each relevant operation. A hyperlink navigates directly to the BNAC work order for full details.

This enhancement closes a visibility gap for organizations coordinating maintenance work across internal teams and external suppliers, giving planners a single view of shared work orders and their collaboration status.

Reference Structure: rule framework for change cascading

FPS02 release builds on the recently introduced reference structure and reference equipment capabilities with a sophisticated rule framework that governs how changes to a reference element cascade to the individual technical objects derived from it. For organizations standardizing reference hierarchies and reference equipment, this closes the loop between defining a standard and keeping the real-world asset structures aligned with it.

The new rule set controls how and when a change to a reference element (a reference hierarchy or reference equipment) is handed over to the individual structures that depend on it. A deployment framework manages the propagation of those changes and their impact on the individual structures, with ongoing enhancements to the handling of validity dates at the reference elements. Based on the rule set configuration, a notification is triggered whenever the reference structure changes.

Using the Manage Reference Structures (F8311) and Manage Reference Equipment (F8304) apps, a comparison check can be run across reference structures, reference equipment, and reference functional locations to identify in-sync and out-of-sync technical objects. Master data specialists receive a notification based on the reference structure change and its release, so they always know when individual structures need to be reconciled.

The result is consistent propagation from the reference structure to individual structures, flexible validity-date handling, and clear visibility into which technical objects are in sync or out of sync with their reference.

Refurbishment best practice scope items (85R and 85U)

FPS02 adds two new best practice scope items to the Asset Management solution bundle, covering the end-to-end refurbishment and repair process:

85R – Internal Refurbishment and Repair of Components supports the full lifecycle of repairing a defective spare part within the organization. A refurbishment order is created to plan and track repair activities and costs; the component is withdrawn from inventory, repaired using internal resources, and returned to available stock for reuse with costs reflected in material valuation.

85U – External Refurbishment and Repair of Components covers the same lifecycle for repairs carried out by an external vendor. The component is sent out via a subcontracting purchase order, received back into stock after repair, and tracked throughout with full cost and lifecycle visibility.

Both scope items complement the existing best practice scope items 4HH and 4HI for asset management, and the associated Signavio business process flows are available for reference.

Linear Asset Management APIs

FPS02 significantly expands the API surface for Linear Asset Management (LAM), enabling programmatic integration of linear asset data with third-party GIS, field service, and asset management systems. The following APIs have been extended to support creating, reading, and updating LAM position data:

Equipment OData API (API_EQUIPMENT)
Functional Location OData API (API_FUNCTIONALLOCATION)
Measuring Point OData V4 API (api_measuringpoint)
Measurement Document OData V4 API (api_measurementdocument)
Maintenance Task List API (API_MAINTENANCETASKLIST) — for Equipment Task Lists (Type E) and Functional Location Task Lists (Type T)
Maintenance Plan OData V2 API (API_MAINTENANCEPLAN)
Maintenance Item OData API (API_MAINTENANCEITEM)
Maintenance Notification OData V2 API (API_MAINTNOTIFICATION)

Key constraints apply: LAM data for Equipment must be included in the creation request and cannot be added to an existing record; delete operations are not supported across most APIs. Full technical details, including field cardinalities and PATCH patterns, are available in the What's New Viewer and SAP Help Portal.

Summary

SAP Cloud ERP Private 2025 FPS02 sets a new baseline for intelligent asset management. The autonomous AI agent suite is the most significant innovation in this release. Not because it replaces the expertise of maintenance professionals, but because it removes the administrative friction that prevents that expertise from being applied where it matters. From the first notification to the final job confirmation, every step of the maintenance workflow now has an AI partner that works in natural language, checks before it acts, and learns from the data your organization already has.

The supporting innovations in safety compliance, planning transparency, collaboration, and APIs continue the steady progress toward a more connected, data-driven maintenance operation.

Don't hesitate to leave a comment and check out our SAP S/4HANA Cloud Private Edition Community page to ask your questions and engage with the experts. Follow the PSCC_Enablement tag to find our latest blog posts.

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

More Information

Source link

What's New in Asset Management in SAP Cloud ERP Private 2025 FPS02