SAP Joule in Supply Chain – Key Insights to be considering for support your start point with Joule
Overview
SAP Joule is rapidly transforming how supply chain professionals interact with enterprise systems. As SAP's generative AI copilot, Joule is embedded across key supply chain applications — from SAP Integrated Business Planning (IBP) and SAP S/4HANA Inventory Management to Extended Warehouse Management (EWM) and Procurement — enabling users to execute tasks, retrieve insights, and navigate applications using natural language.
With Joule now supporting over 50 domain-specific assistants backed by more than 200 specialized agents, and with Joule Studio reaching general availability in Q1 2026, supply chain teams are at a pivotal moment to adopt, configure, and govern Joule effectively. This blog consolidates the most critical OSS Notes and architecture guidance every supply chain consultant and administrator should know.
Agentic AI & AI Agents | SAP Architecture Center
Product Sunset: Joule Embedded Entitlement (OSS Note 3720360)
What is happening?
SAP has announced the product sunset of the Joule Embedded Entitlement (SKU 8018168) in SAP Cloud Test, Demo, and Development (TDD) environments. Subscribers to this entitlement have received — or will receive — an official email notification from SAP confirming that the subscription will not be renewed at the end of the current subscription term.
Successor Offerings
SAP is directing customers and partners to transition to the following successor SKUs, which expand capabilities beyond the retiring entitlement:
SKU | Description |
8020592 | Cloud Test, Demo, and Development for Joule Base |
8019670 | Cloud Test, Demo, and Development for SAP AI Unit |
Impact on Supply Chain Teams
Supply chain teams using TDD environments to prototype or validate Joule-enabled scenarios — such as inventory management automation, procurement workflows, or IBP planning assistants — must take action before their subscription term ends. Critically, existing embedded Joule configurations and entitlements will NOT automatically migrate to the successor offerings. Manual steps are required.
Recommended Actions
- Review your current TDD subscription status on SAP for Me (me.sap.com)
- Identify all active Joule Studio projects, custom skills, and SBPA (SAP Build Process Automation) tenant configurations that need to be exported or backed up before migration
- Procure the successor entitlements (8020592 and/or 8019670) through your SAP account executive
- Plan the manual reconfiguration of Joule Studio components in the new environment
- Reference OSS Note 3720360 on SAP Support Portal for the full migration checklist
🔗 OSS Note: 3720360 – Product Sunset Announcement for Joule Embedded Entitlement (8018168)
Support Component Selection for Joule (OSS Note 3798165)
Why Component Selection Matters
Raising a support ticket under the wrong component is one of the most common causes of delayed resolution for Joule issues. OSS Note 3798165 provides definitive guidance on how to select the correct support component when experiencing Joule conversation or prompt-related issues.
Key Component Values
Based on the guidance aligned with this note and related Joule support documentation, the following component structure applies:
Scenario | Support Component |
Joule capability issues in SAP S/4HANA Cloud Private Edition (navigational/transactional) | CA-FLP-EXT-PCE-JOULE |
Joule provisioning and entitlement issues | CA-JOULE-PRV |
Custom skills built via Joule Studio / SAP Build | CA-BLD-JLE-SKI |
Supply Chain Relevance
For supply chain teams, the most common prompt and conversation issues arise in:
- Inventory Management (goods receipts, stock overview, material documents) component CA-FLP-EXT-PCE-JOULE
- Procurement (purchase requisitions, purchase orders, supplier invoices) same component
- SAP IBP (supply planning, lead time intelligence) verify the IBP-specific Joule component via SAP for Me
Important Distinction: Many Joule issues in supply chain stem from missing OData service activations or incorrect business role assignments, not from product defects. Before raising a ticket, verify OData activation status using SAP Note 3746234 (Role and OData Analyzer).
🔗 OSS Note: 3798165 – How to select the correct support component for Joule conversation/prompt issues
Joule Architecture & Security (OSS Note 3786517 + Reference Architecture)
Architecture Overview
OSS Note 3786517 provides the official Joule architecture and security guide. This is complemented by the SAP Architecture Center reference architecture for Identity and Access Management (IAM) for SAP Joule, available at:
🔗 https://architecture.learning.sap.com/docs/ref-arch/ea5d4f
At its core, the Joule architecture positions the AI copilot at the center of a layered integration model:
Identity and Access Management (IAM) Key Architectural Values
The IAM reference architecture for Joule establishes the following critical integration points:
- SAP Cloud Identity Services – Identity Authentication (IAS): Joule relies on a configured trust relationship between the SAP BTP subaccount and the IAS tenant. This is a mandatory prerequisite for all Joule deployments.
- User Attribute Configuration: User attributes must be configured for Joule from the Identity Directory within IAS. This ensures that Joule inherits the correct user context and entitlements.
- Joule Booster: The Joule Booster on SAP BTP automates the setup of the Joule Formation, including the communication scenario SAP_COM_0882 for S/4HANA Cloud Public Edition integration.
- Role-Based Access Control: Joule inherits the user's existing SAP entitlements — users cannot query data they are not authorized to see. This is enforced at the backend application layer, not within Joule itself.
Joule Extensibility Architecture — Four Capability Patterns
The SAP reference architecture for Integrating and Extending Joule (Ref-Arch 464deb) defines four canonical capability patterns:
Pattern | Description | Supply Chain Example |
Transactional | Natural language triggers direct backend processes | Create goods receipt, post inbound delivery |
Navigational | Guides users to the right Fiori app | “Where can I manage warehouse tasks?” |
Informational | Delivers knowledge via RAG from indexed documents | Query delivery notes from SharePoint |
Analytical | Surfaces business insights on demand | Lead time intelligence in IBP |
Security Considerations for Supply Chain Deployments
- All Joule integrations must route through SAP Cloud Identity Services — direct backend connections without IAS trust are not supported
- For SAP IBP integrations, verify the integration path via the Joule Onboarding Guide to ensure the Joule Formation status displays “Ready”
- For SAP Ariba integrations, an additional entitlement and authorization may be required — consult your account executive
- BTP subaccount setup must include correct Global Account, subaccount, and entitlement configuration before running the Joule Booster
🔗 OSS Note: 3786517 – Joule Architecture and Security Guide 🔗 IAM Reference Architecture: https://architecture.learning.sap.com/docs/ref-arch/ea5d4f
Joule Studio Setup with SAP Build Apps (OSS Note 3733441)
What is Joule Studio?
Joule Studio, available within SAP Build, is a low-code/no-code environment for creating, deploying, monitoring, and managing custom Joule skills and agents. It reached general availability in Q1 2026 and is the primary tool for extending Joule with supply chain-specific capabilities.
Prerequisites for Configuring Joule Studio (OSS Note 3733441)
OSS Note 3733441 covers the prerequisites and setting up scenarios for configuring Joule Studio with SAP Build Apps. Based on the aligned architecture and provisioning guidance, the following prerequisites apply:
BTP Platform Prerequisites:
- Active SAP BTP Global Account with appropriate entitlements
- Joule Base SKU (8020592 for TDD, or the production equivalent 8019544 for SAP Signavio integrations) provisioned to the BTP subaccount
- SAP Build Process Automation (SBPA) tenant active and connected
- Trust configured between BTP subaccount and SAP Cloud Identity Services – IAS tenant
Joule Studio Setup Scenarios Relevant to Supply Chain:
The following building-block packages are SAP-maintained and directly applicable to supply chain use cases:
Package | Version | Supply Chain Use Case |
SharePoint Document Grounding Search | 1.1.0 | AI Core vector search over supply chain documents (delivery notes, SOPs) |
Delivery Note Assistant | 1.1.0 | SBPA action to retrieve and extract delivery note details |
Inbound Delivery (A2X) | 1.1.3 | SBPA action to create inbound deliveries in S/4HANA |
Key Setup Steps:
- Provision the Joule Base entitlement on your BTP subaccount
- Configure IAS trust and user attribute mapping
- Run the Joule Booster to establish Joule Formation
- Access Joule Studio within SAP Build and import the relevant SAP-maintained building-block packages
- Build your Joule Capability Package (Custom Agent) by orchestrating the imported packages with your supply chain-specific logic
- Assign the correct Business Roles and activate the required OData services for each transactional use case
Backup Before Migration: If migrating from the sunset Joule Embedded Entitlement (8018168), export all Joule Studio projects and custom skill components before decommissioning the old TDD tenant.
🔗 OSS Note: 3733441 – Prerequisites and Setup Scenarios for Configuring Joule Studio with SAP Build Apps 🔗 Joule Onboarding Guide: https://help.sap.com/docs/JOULE/6189c8655c484916bb8eb767126a653a/48e8f655470048c29555272578fbc2ce.html?version=CLOUD
Key Takeaways for Supply Chain Teams
# | Action Item | Reference |
1 | Migrate away from SKU 8018168 before subscription term ends — procure 8020592 (Joule Base) and/or 8019670 (SAP AI Unit) | OSS Note 3720360 |
2 | Export and back up all Joule Studio projects, custom skills, and SBPA configurations before TDD tenant decommission | OSS Note 3720360 |
3 | Use component CA-FLP-EXT-PCE-JOULE for supply chain capability issues; use CA-JOULE-PRV for provisioning issues | OSS Note 3798165 |
4 | Verify OData activation using SAP Note 3746234 before raising support tickets for transactional Joule failures | OSS Notes 3798165, 3786517 |
5 | Configure IAS trust and run the Joule Booster as the foundation of every Joule deployment | OSS Note 3786517, IAM Ref-Arch |
6 | Leverage SAP-maintained building blocks in Joule Studio (Delivery Note Assistant, Inbound Delivery A2X) for rapid supply chain skill development | OSS Note 3733441 |
7 | Monitor Joule What's New for supply chain-specific releases — IBP lead time intelligence, Inventory Management goods receipts, and Warehouse Management use cases are actively expanding | SAP Help Portal |
Referenced OSS Notes & Resources
Resource | Link |
OSS Note 3720360 | |
OSS Note 3798165 | |
OSS Note 3786517 | |
OSS Note 3733441 | |
IAM Reference Architecture | |
Joule Help Portal | |
Joule Onboarding Guide |
Hope this helps you!
Thank you and regards.
Rogerio Lima.
Source link
