Identifying New Features of Service Contracts and Recurring Services in Release 2025 FPS1

In this unit you learn about …

• … multilevel categorization for service contracts.
• … the creation of a maintenance plan out of a service contract.
• … Joule for service contracts.
• … the SAP BDC data product for service contracts.
• … additional enhancements for service contracts.
• … new BAdIs for recurring services.

Service contracts are part of the lead to cash process. They are part of the plan/configure/price/quote and sell phase of this process. Sub-steps that are part of this process are (for example) creating and releasing a service contract, service contract determination, contract billing and invoicing, etc.

In a broader sense, the next process steps in the lead to cash process are steps in the area of service planning and execution, return and repair, and maintenance service and onsite service. A specific follow-up step after the creation of a service contract, could be its inclusion in a recurring service process.

When you analyze Service Contract Management in its context, you can find documents like a service contract template and/or a billing plan template. Other topics in the context of Service Contract Management are item-based accounting, event-based revenue recognition (EBRR), and contract renewals and extensions. Other related topics include price adoption, contract cancellations, and the various item categories that are supported.

A maintenance plan can be created during the release of a service contract (item) if a maintenance plan template is assigned to the item. A maintenance plan template can be assigned to a contract template item, which will be copied to a service contract item during creation. You can also directly assign a maintenance plan template to a contract item. Only time-based single cycle maintenance plans are supported in this scenario. The service order template can be defaulted from a reference maintenance plan item, or (as stated) it can be updated in a service contract item.

In the screenshot you can see a service contract item with a maintenance plan assigned to it.

SAP combines applications, data, and AI in one unified system, embedded across the enterprise. SAP’s AI is built on a 50-year business intelligence foundation, which is grounded in a company’s business data, and connected across every critical business function.

The SAP Business Suite works like a flywheel across an enterprise. Better processes generate better data, which trains smarter AI agents that continuously improve operations. This in turn results in even better data.

This all works together to make a business smarter with every cycle.

SAP combines applications, data, and AI in a unified system, brought to life by the SAP Suite, and deeply integrated:

• Point solutions can offer useful AI features, but since they can only see a small slice of a business, their impact is usually small. Limited access means limited value.
• Hyperscalers can connect AI to data, but without business applications or process knowledge, they can’t bring intelligence into business processes. AI without context can’t grow a business.

SAP combines AI with applications and data in a unified way, so everything works as one:

• Joule is SAP’s most fundamental AI interface. It’s context-aware, proactive, and seamlessly woven into enterprise applications (from Supply Chain, to HR to Finance and everything in between. This is where a user interacts most frequently with Business AI. •
• A user’s interactions with Joule will inform AI assistants, which learn about a business and role, then execute multi-step tasks on their behalf.
• To do this, they leverage powerful Joule agents. These are autonomous, intelligent actors that can complete complex tasks on their own while referencing a vast library of skills and capabilities.
• The AI Foundation is what powers all of this; it is the core AI operating system, grounded in business data and embedded into every business function.
• Strategic AI Partnerships: SAP collaborates with leading AI companies to bring the most innovative and cutting-edge technologies in a safe, enterprise-complaint way or building and orchestrating custom AI solutions.

Joule extends human capability with AI built in. Embedded directly into the flow of work across SAP and non-SAP systems, Joule transforms transactional tasks into intelligent, connected workflows that inform sharper decisions and accelerate business processes. Grounded in SAP’s harmonized data and trusted architecture, Joule delivers unmatched contextual performance without compromising on compliance, security, or scale. With Joule, people act with clarity, teams collaborate without silos, and business-critical processes are streamlined to drive enterprise-wide impact.

Joule also tailors AI with role-specific assistants. Simplifying employee access to teams of agents who collaborate on end-to-end processes to accomplish complex tasks in minutes versus hours:

• With AI assistants in Joule, SAP introduces personalized AI partners that adapt to individual needs and empower users to confidently navigate complex business landscapes.
• Each AI assistant is purpose-built to support a specific role in an organization, whether it’s Financial Planning, HR Operations, or beyond.
• Behind every assistant is a powerful combination: multiple Joule Agents working together, alongside custom agents if needed. All unified within a seamless experience that’s intuitive and designed to get work done faster and smarter.

The Receivables Assistant is a dedicated AI partner, purpose-built for Accounts Receivable Managers. This assistant brings together specialized Joule agents, each designed to streamline and simplify key receivables processes.

With the Collections Agent, Working Capital Agent, Dispute Resolution Agent, Invoicing Processing Agent, Payment Scheduling Agent, and Fraud Detection Agent, targeted support is available for every challenge in receivables management. Plus, custom agents can be added, creating a solution that fits an organization’s unique needs.

The result is a seamless, intuitive experience that helps Accounts Receivable Managers act faster, reduce risk, and stay on top of every transaction with confidence.

AI-powered breakthroughs aren’t limited to one function or industry. They are improving business processes across the organization and delivering everywhere. These aren’t just point solutions, but systemic improvements that change what’s possible for every leader in an organization. This transformation doesn’t happen in isolation. What truly sets SAP Business AI apart is the scale and diversity of innovation available through an open ecosystem of strategic partnerships.

This open ecosystem of AI partnerships allows a company to get the best out of AI because it provides choice. SAP partners with leading AI providers (data solution providers, hyperscalers, etc.) to provide the most innovative and cutting-edge technologies in a safe, enterprise complaint way.

Additionally, the SAP landscape supports many LLMs and regularly adds in new models. This robust network includes leaders like Anthropic, Cohere, Google Gemini, Meta, Microsoft, Mistral Al, Perplexity and more.

Service contract information can be fetched through Joule by using the sold-to-party, contract person, service contract id and/or the status.

Profitable service contracts can also be fetched using parameters like sold-to-party, contract person and currency. When fetching details for a specific service contract, Joule retrieves information such as the description, the net amount, the responsible employee, and the start and end date. For more details, a user can navigate to the service contract in the app.

For more information, see: https://help.sap.com/docs/joule/capabilities-guide/fetch-service-contract-information.

The SAP Joule AI assistant can be used to update the status of a service contract to Released or Completed. In case the status is not updated, Joule will respond with relevant messages. In case a service contract is already in status Completed, a release is no longer possible. You can navigate to the Manage Service Contracts app by choosing Open and doing the necessary corrections.

For more information, see: https://help.sap.com/docs/joule/capabilities-guide/update-service-contract-status.

SAP’s product strategy is shown: Unparalleled applications, unmatched data, and unrivaled AI together are at the heart of SAP's product strategy.

SAP Business Data Cloud (SAP BDC) provides a single, fully managed cloud SaaS platform for all of a company’s data and analytics . It brings together all SAP data, integrates third-party sources, and offers powerful governance. SAP Business Data Cloud delivers enriched data products, advanced analytics, cross-analytics, benchmarking data, and AI-powered intelligent applications. It empowers SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private Edition, and line-of-business applications (such as HCM, ISBN, etc.) with actionable insights to drive more impactful decisions. It offers business-specific data packages with data products, and supports BI, ML, AI services, Joule, a knowledge graph, and planning functionalities.

A service contract is available as a data product in SAP BDC.

See https://hub.sap.com/api/sap-s4com-ServiceContract-v1/overview.

More enhancements for service contracts in release 2025 FPS1:

• Rejection Reason: The rejection process has been enhanced. In addition to header-level rejection, items can now be rejected individually. This is done by selecting a rejection reason for a specific item in the Item Details list.

  Concerning the difference between rejecting and cancelling a contract:

  • Timing:

    Rejection: Happens at the offer stage. Rejecting is saying No to an offer before a contract exists. If you reject an offer (or let it lapse), no contract is formed.

    Cancellation: Happens after formation of an agreement. An existing agreement is terminated.

  • Legal effect:

    Rejection: No duties, rights, or liabilities because there was never a contract.

    Cancellation: Stops future performance, but rights and obligations already accrued may remain. Depending on the agreement, a cancellation fee might be owed, a payment for work already done, or damages may be faced for breach (if cancelled without a contractual right).

  • Related concepts:

    Termination: Often used interchangeably with cancellation; typically means ending a contract going forward, with accrued rights preserved.

    Rescission: Unwinds the contract as if it never existed (returns parties to their pre-contract position), which is different from simple cancellation.

  • Examples:

    Rejection: You receive a service proposal and decline it. No contract is formed.

    Cancellation: You signed a gym membership and later cancel under the contract’s cancellation clause. You may owe notice or a fee, and past dues remain payable.

  The exact consequences depend on the contract language and applicable law, so it’s important to read the termination/cancellation provisions.

• Reopen Business and Archiving:

  Service contracts can only be archived when they have the status Business Completed. If a specific service contract serves as the root in a financial hierarchy, and any follow-up transaction (service order, confirmation, maintenance order) has been archived, reopening the document again by changing its status is no longer possible, and further changes/settlement is then not allowed.

• Service contracts are now also included in the Customer 360° app (version 2).

• The Financial Attributes assignment block is available for service contracts.

The purpose of this BAdI is to enable a customer to add custom validations at the time of scheduling to prevent the generation of a call object.

The BAdI is applicable for solution process Recurring Services (7GA) (call type 5) and solution process Preventive Service with Advanced Execution (6F1) (call type 6).

In Customizing, go to SAP Reference IMG→Service→Transactions→Settings for Recurring Service→Business Add-Ins→BAdI: Maintenance Plan Scheduling.

The purpose of this BAdI is to allow adding a new service item generated from a maintenance plan item to an existing service transaction if all the preconditions are met.

The BAdI is applicable for solution process Recurring Services (7GA) (call type 5).

In Customizing, go to SAP Reference IMG→Service→Transactions→Settings for Recurring Service→Business Add-Ins→BAdI: Reuse Service Transaction in Recurring Service.

The purpose of this BAdI is to allow the enabling of the standard service contract determination for service transaction items.

The BAdI is applicable for solution process Recurring Services (7GA) (call type 5).

In Customizing, go to SAP Reference IMG→Service→Transactions→Settings for Recurring Service→Business Add-Ins→BAdI: Contract Determination in Recurring Service.

• The idea behind multilevel categorization is to enable scalable, automated, and compliant service operations by standardizing taxonomies across SAP Service processes. It provides a flexible taxonomy framework for service contracts, and it contains an "auto complete" feature for a service contract, based on categorization. A category can be maintained as a hierarchy in the application Manage Categorization Schema and a service contract template can be assigned for auto complete. Using the UI, you can maintain categorization up to level 4.
• Service contract information can be fetched through the SAP Joule AI assistant by using the sold-to-party, contract person, service contract id and/or the status.
• The SAP Joule AI assistant can be used to update the status of a service contract to Released or Completed.
• A service contract is available as a data product in SAP Business Data Cloud (SAP BDC).
• Three BAdIs have been introduced for recurring services: BAdI: Maintenance Plan Scheduling, BAdI: Reuse Service Transaction in Recurring Service, and BAdI: Contract Determination in Recurring Service.