SAP AI access for on-premises customers

Why SAP’s Cloud Terms Could Limit Joule Access for Smaller On-Premises Customers

A manufacturer running its business on one SAP system can use selected Joule AI capabilities before moving that system to the cloud. The harder question is what it must sign while its purchasing, production and finance teams still depend on the old system. SAP ties access to eligible cloud ERP commitments and a supported software release. That can turn a proposal for one AI assistant into a decision about several years of ERP spending. SAP’s explanation of AI activation

That distinction is at the heart of a November 18 report from The Register. Thomas Henzler, chair of DSAG, the SAP user group representing customers in Germany, Austria and Switzerland, warned that smaller businesses with one ERP system have fewer practical ways to meet the terms. SAP told the publication that a single system can qualify and that customers can commit commercially before moving it. The disagreement is about how affordable that sequence is.

What SAP is offering before migration

An on-premises enterprise resource planning (ERP) system holds the records a business uses to buy materials, fulfil orders and close its books. A customer might run SAP ERP Central Component (ECC), an older product, or its successor, SAP S/4HANA. Moving from ECC to S/4HANA changes the software. Choosing who operates it and under which cloud agreement is a separate decision. For a broader look at how deployment affects purchasing and implementation, see a guide to choosing ERP software.

Joule gives users a conversational way to work with supported business applications. Depending on the application and release, a user can ask for information, navigate to a record or carry out a supported task. Joule Studio is the environment for building and extending agents and workflows. Someone who wants purchasing staff to use an existing assistant has a different licensing and implementation question from a developer who wants to build a custom agent.

RISE with SAP is SAP’s guided route for existing ERP customers moving to SAP Cloud ERP Private. Its relevance here is timing. SAP says customers who commit to that route and meet the minimum cloud conditions can activate supported assistants and agents against eligible ECC or S/4HANA installations while their modernisation work continues. A team can therefore ask what it can use this year, even if its production cutover is scheduled much later.

How SAP’s 50% maintenance test works

SAP confirmed a 50% maintenance-spending requirement to CIO in May. Its commercial guidance provides a more precise account of what counts. The calculation depends on when the customer signed its core cloud ERP contract. Both scenarios also require the software release specified for the desired AI feature.

Core cloud ERP contract date Test described in SAP’s guidance
Before October 7, 2024 The average annual contract value of eligible cloud ERP subscriptions must equal at least 50% of the current annual on-premises maintenance fee.
After October 7, 2024 The customer must sign a Cloud Extension Program agreement that converts at least 50% of the current annual on-premises maintenance fee into eligible cloud ERP subscriptions.

The denominator matters. Using total IT spending, the original ERP purchase price or the number of live systems would give procurement the wrong answer. SAP’s slide lists eligible subscriptions by product name. Ask the account team to match each proposed order line to that list, identify the maintenance amount it used and show the calculation. The slide uses “before” and “after” for the cutoff, so a customer whose agreement is dated October 7 itself should get written confirmation of the applicable route. SAP’s commercial guidance

The percentage establishes an eligibility benchmark. It does not give a buyer a subscription quote, a Joule usage allowance or a guaranteed maintenance credit. Two companies with the same maintenance bill could face different cash outlays if one already has qualifying subscriptions and the other must negotiate a conversion.

Why one ERP system changes the business case

A group with several ERP systems might move one subsidiary to cloud ERP, build qualifying subscription value and keep other businesses on premises during the transition. A smaller company that runs everything on one ECC system has no second production system to move first. Henzler’s concern is that, in practice, such a customer may have to convert its entire maintenance arrangement to make the offer work. That is DSAG’s assessment of a possible commercial outcome. SAP’s published percentage remains 50%, and SAP says system count itself does not determine eligibility.

Worked example — one German manufacturer, one ECC system

Consider a fictional components manufacturer paying €120,000 a year in qualifying on-premises maintenance. It has one ECC production system and no existing eligible cloud ERP subscription. Its purchasing team wants help investigating overdue orders. Its next realistic migration window is after the factory’s peak season.

Under the post-cutoff scenario, 50% of the assumed maintenance base is €60,000. That is the amount of maintenance to address in the conversion calculation. It tells the finance director neither the final cloud invoice nor how much support the factory will still need before cutover. The figures are illustrative. SAP would need to price the subscription and specify when any maintenance reduction takes effect.

The buyer can put the pilot on the same footing as other investments. Suppose 12 buyers each save 20 minutes a week for 48 weeks. At an assumed labour cost of €40 an hour, that releases 192 hours worth €7,680 a year, before training or review time. If the team uses those hours to resolve supplier delays, the operational benefit may be worthwhile. Cash savings depend on what the company actually does with the time.

If a cloud move already has board approval, finance should assess the additional cost of starting Joule early. If the pilot would trigger a cloud commitment the business would otherwise postpone, the approval paper should include that commitment and the months of overlapping costs. The same assistant can support a sound decision in the first case and a poor one in the second.

What will actually work on your system?

Start with one verb. “Show overdue purchase orders” requires access to purchasing records. “Change the delivery date” also requires permission to update a transaction and a way to audit the change. SAP documents purchase-order lookup in a cloud release. A customer seeking the same workflow on ECC should request the capability entry for its own backend, release and region. A demonstration on a current cloud tenant answers a different technical question.

Have the implementation partner demonstrate the task using representative records and ordinary employee permissions. Include an order with a custom field, an order the employee cannot access and an order updated after the initial query. Ask where the assistant gets each answer, how quickly a change appears and who can investigate a failed request. These tests reveal whether the pilot can handle the business process staff use every day.

For Germany, Austria, Switzerland and other markets, establish the service region separately from the billing address. SAP directs customers to its Discovery Center for regional platform availability. Ask which services process the request, which languages the chosen assistant supports and where prompts, results and logs are handled. The November report identifies a concern raised by a German-speaking user group. It does not establish a special DACH spending threshold.

What to budget beyond the cloud commitment

SAP describes an activation service for up to three Joule Assistants on Cloud ERP Private at no additional activation charge. It also says the same activation services apply to qualifying on-premises transitions and describes broader activation support under its Max Success Plan. Ask SAP to identify the service scope and required support plan for your installation. SAP’s own onboarding description calls for checking AI Unit entitlements as well as the software version.

Budget item What finance should request
Contract and overlap A dated schedule showing the cloud subscription, remaining maintenance, credits and charges if migration slips.
Implementation A split between SAP-funded activation and partner or internal work on upgrades, connectivity, identity, testing and training.
Production use The billing metric for each capability, included allowance, overage price and a sample month at expected volume.
Custom development Separate figures for building, testing, running and supporting a Joule Studio agent after any promotion ends.

The last line matters for a pilot launched late in 2026. SAP’s commercial training describes action-based AI Unit consumption for premium agents and a temporary runtime promotion through the end of 2026 for customer-built agents on Joule Studio. A December pilot can therefore give a misleading impression of January operating costs. Ask for a priced production example using the same workload after the promotion expires.

Eligibility checklist and questions to take to SAP

Check Question for SAP or your implementation partner
Contract eligibility Which signed agreement qualifies us, which subscriptions count and what maintenance figure did you use?
Technical readiness Which release, patches, interfaces, identity services and connection components does this particular workflow require?
Available capability Can you show the assistant completing our task on our release, in our language, using our existing approval roles?
Entitlements Which order lines cover activation, end-user access, AI Units, Studio development and production runtime?
Commercial timing When do subscription charges start, when does maintenance fall and what changes if cutover moves back six months?
Operational ownership Who monitors consumption, handles failed actions and supports the connection while the ERP system stays on premises?

Ask for the answers in a single proposal that procurement, IT and the process owner can review together. Give each dependency an owner and a date, especially any prerequisite upgrade that competes for the same testing window as the migration. Teams coordinating that work can use a  guide to project management software.

FAQs

Can a company with only one ECC system qualify for Joule?

Yes. SAP told The Register that a single eligible instance can qualify when the customer meets the commercial and technical conditions. DSAG’s objection concerns the cost and practicality of meeting those conditions with one system.

Must we move half our ERP systems to the cloud?

The published test measures money. Depending on the contract date, SAP measures eligible cloud subscription value or the share of annual maintenance converted through its Cloud Extension Program. The calculation does not count servers, users or production instances. SAP’s commercial guidance

Can we keep our migration date and use Joule earlier?

Potentially. SAP explicitly allows eligible customers to activate supported capabilities while modernisation continues. Check the earliest supported activation date for your specific feature against the start of billing. Those dates determine how much useful time early access buys you.

Final words

For a smaller SAP customer, the decisive question is how much earlier Joule can improve a real workflow and what the business must commit to for that head start. Put the qualifying contract calculation, a demonstration on the installed release and the production price beside the existing migration plan. Together, those give the board a basis for approving early access or keeping the original timetable.

Leave a Comment

Your email address will not be published. Required fields are marked *