
SAP extends the Joule promo for Build, not for ABAP AI
SAP extended the free Build features to December 31, but ABAP AI still goes commercial on October 1. Two deadlines now, and SAP's pricing wording conflicts.
SAP / Product coverage
Source-linked reporting organized by product, platform, and the topics that connect them.

SAP extended the free Build features to December 31, but ABAP AI still goes commercial on October 1. Two deadlines now, and SAP's pricing wording conflicts.

SAP's four contributions to the OpenShell agent runtime are containment and operability engineering, and the runtime is free only through October.

An ODP security check has landed in SAP EarlyWatch Alert, putting a June note about unchecked RFC callers in front of people who never read the patch queue.

The no-cost period for Joule for Developers ends September 30 and ABAP AI moves to commercial licensing on October 1. Find out who is using it first.

SAP says Colombina migrated all 16 countries it operates in to S/4HANA Cloud Private Edition at once, skipping the phased waves most programmes plan for.

SAP now plans AI token spend inside its normal finance cycle after employee and agent usage became a triple-digit-million-dollar risk.

Procurement's confidence in working with the rest of the business fell 16 points in a year. A new SAP tool answers a narrower question.

SAP's September 10 services update counts Joule users and success plans. After go-live, the number an architecture team needs is in its own support queue.

SAP put drones and humanoids on Joule at its first Embodied AI Jam. Our read: every use case rests on an equipment or routing record a person keeps accurate.

SAP's Embodied AI Jam sent teams home with use cases and architectural proposals. Here is the five-part test that separates a robot demo from a process.

SAP's Embodied AI Jam listed warehouse automation without naming a system. Here is the task data, write-back, and exception path a floor team needs first.

SAP integration moves business documents, not rows. Which patterns hold up over years, which quietly become somebody's problem, and what to check first.

Winter '27 lands October 12, the Release Planner retires November 15, Brazil is arriving and 2026R2 is already live. Six vendors, one team calendar.

SAP numbers are only correct because of the logic around them. Decide which questions need that logic and which cross systems SAP never sees.

SAP publishes BTP's update cadence but not a platform-wide retirement notice period. The number you can hold SAP to sits in the contract.

Consumption pricing moves cost control from the contract to the code, and BTP spending drifts because nobody told the engineers they were spending it.

S/4HANA support packs arrive on a plan and BTP services do not. How to split the reading, triage notes, and keep a record that lasts.

A framework for deciding what SAP work gets rebuilt clean, what becomes a BTP side-by-side extension, and what temporary fix quietly becomes permanent.

Before a Power Platform or SAP roadmap gets sequenced, list every flow it touches with a source of record, a consumer, and the person who fixes exceptions.

Keeping SAP S/4HANA modifications out of the core only works when someone funds the BTP extension platform, the rewrites, and the retirements.

A modernization program that lists what it will build and never what it will switch off ends up paying for both. Put the retirements in the scope.

SAP BTP is one name over four different things: extension runtimes, integration, data services and AI. Knowing which one you mean is most of the answer.

A reorg breaks employee feeds that were built against last year's org chart. Pick keys and reconciliation that outlive the chart.

Before a three-year SaaS renewal call, pull your own usage data, read the vendor timeline pressure for what it is, and decide what discount is worth the lock-in.

A full governance program takes years to fund. Material and vendor master ownership is where an S/4HANA team can start this quarter.