What SAP support numbers tell an architecture team after go-live
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 / Product coverage
SAP BTP
Source-linked reporting organized by product, platform, and the topics that connect them.
Latest coverage
SAP's Embodied AI Jam turns master data into a safety question
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.
The five-part test we'd run on SAP's Embodied AI Jam pilots
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.
What a warehouse robot needs from SAP after the Embodied AI Jam
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.
Analysis and architecture
Map the Power Platform and SAP flows before the roadmap
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.
SAP clean core is a budget decision before an architecture one
Keeping SAP S/4HANA modifications out of the core only works when someone funds the BTP extension platform, the rewrites, and the retirements.
Why every modernization plan needs a retirement list
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.
Related guides
Start SAP master data governance with material and vendor master
A full governance program takes years to fund. Material and vendor master ownership is where an S/4HANA team can start this quarter.