SAP AI is not a product — it is a three-layer stack
Separate Joule, AI Core and Generative AI Hub. Istanbul delivery writes the instance list and a clean-core decision matrix.
Read →Istanbul · independent delivery
SAP AI
Joule, AI Foundation and embedded AI are not the same layer. Each English note names the runtime, the copilot shell and where the call lives (S/4 vs BTP).
AI Foundation
Business AI is an umbrella term, not an SKU
Embedded process AI, Joule and AI Foundation under one name. Istanbul discovery records KPI base, feature flags and Business Data Cloud.
Read →AI Core is a runtime, not a chat UI
SAP AI Core on BTP: serving template, resource plan, deployment. Istanbul delivery names the instance and the AI Launchpad connection.
Read →AI Launchpad is an admin surface, not the copilot
Admin UI for AI Core connections, scenario status and user assignment. Separate 401/connection faults from the scenario screen.
Read →Generative AI Hub is a model gateway, not an app
Model access and orchestration on BTP. Grounding, CAP destinations and prompt templates bind on the Hub.
Read →Prompts are artefacts, not chat history
Version, transport, owner. Hub templates belong in the same Git discipline as CAP.
Read →AI Foundation is the runtime family, not Joule
AI Core, Launchpad, Generative AI Hub. Istanbul discovery lists instances, not slogans.
Read →RPT-1 is a tabular model, not a copilot
Where it runs, which table contract, who may call it. Not an S/4 embed.
Read →A personal ChatGPT session is not SAP AI
IAS, business object, grounding, audit. Keys do not live in S/4.
Read →Joule
Joule is a process copilot, not a chat bot
SAP Joule sits in cloud application shells. Studio classic GA Dec 2025, next-gen Q3 2026; IAS trust and Work Zone tile are delivery items.
Read →Joule Studio is an extension channel, not a second copilot
Classic GA Dec 2025, next-gen Q3 2026. Delivery records skill transport, tenant entitlement and an IT review gate.
Read →Joule agents are non-deterministic multi-step runs, not skills
Tool catalogue, human-in-the-loop and audit log. Istanbul delivery keeps write tools behind released APIs.
Read →A Joule skill is a contracted action, not an agent
One OData/action, a test, a transport. Prefer skills when the sequence is known.
Read →Joule in Fiori still needs catalog, role and tile discipline
Launchpad/Work Zone shell, PFCG/XSUAA and intent. Joule does not replace App Finder or S_SERVICE.
Read →S/4 Joule does not put the model in the core
Process context, released APIs, entitlement. Inference stays on BTP; S/4 provides the business object.
Read →ABAP AI in ADT is not Joule in Launchpad
Developer copilot vs process copilot. Different entitlement, different shell.
Read →Joule enablement is a Work Zone setting, not a CAP deploy
IAS, role, tile. Admin Launchpad green does not prove the user shell works.
Read →Agent Builder is a design-time, not a go-live
Tool catalogue, guardrails, tenant. Next-gen timing is a risk note, not a promise.
Read →Applications
CAP calls the Hub; it does not embed an LLM in CDS
Destination, secret, timeout, prompt template. Side-by-side on BTP, S/4 consumed as an API.
Read →Build AI is not Joule Studio
Low-code actions can feed a skill. Governance of Build and Studio stays separate.
Read →CPI is not a prompt playground
iFlow calls the Hub or an API. Payload, retry and audit stay in Integration Suite.
Read →Embedded in S/4 is not the same call as BTP Foundation
Feature flag, process, upgrade. Write the call site before the sprint.
Read →The model URL does not belong in the core
CAP destination, secret store, released API. Modification is last resort.
Read →Istanbul AI work starts with landscape, not a demo
Instance, entitlement, call site, KVKK map. No licence sales, no partnership claim.
Read →Data & RAG
Vector index is not a second S/4 database
HANA Cloud vector + grounding. Authority of the business document stays on S/4.
Read →Grounding is retrieval with a contract, not ‘paste the PDF’
Chunking, ACL, citation, refresh. Istanbul delivery writes which store is authoritative.
Read →A graph is context, not a data warehouse
Object links for prompts and agents. Does not replace CDS or released APIs.
Read →BDC is a data plane, not Joule
Grounding and KPI paths. Feature flags and landscape placement are discovery items.
Read →Security
KVKK is a placement decision, not a checkbox on the model
Where prompts, logs and documents live. Istanbul delivery writes the data map before the first call.
Read →Entitlement is not a tile
Quota, booster, commercial assignment. Discovery lists what the account actually owns.
Read →The destination name is the contract
OAuth, principal propagation, secret store. 401 is identity, not ‘AI is down’.
Read →The user in the prompt must be the user in S/4
IAS, XSUAA, destination. A technical user for AI writes is a SoD finding.
Read →