Issue Catalog Summary

In this github, you’ll find a consolidated catalog of documented Joule issues, organized by architecture layer to make navigation as intuitive as possible. For the full picture — including detailed root causes, resolutions, SAP Notes, support components – just git and download the attached Excel file. And we’d love to keep this resource growing: if you have additional issues to contribute, you’re warmly invited to add the valid ones.

[Github] leee03/SAP_Joule_Issue_Catalog

Layer 1: Client / UX

• Frame-ancestors Content Security Policy (CSP) violation
• Joule icon not showing in SAP Fiori Launchpad
• Icon displayed incorrectly (SAPUI5 version)
• Unable to launch Joule via icon (cookies)
• Icon not appearing for specific user (SAP SuccessFactors)
• Blank/greyed-out screen (SAP SuccessFactors)

Layer 2: SAP Cloud Identity Services

• Corporate Identity Provider refused to connect
• Joule not greeting with user's name
• Blank/white IAS login screen
• IPS transformation editing fails
• IAS source system read job failing

Layer 3: SAP Build Work Zone

• Content Manager not visible (foundation plan limitation)
• Content provider sync fails (unauthorized)
• Navigation links not working (proxy type)
• Capabilities limited with foundation vs standard plan
• Joule cannot return transactional/navigational responses
• SuccessFactors navigational use cases not working – profile button missing, deep links not generated

Layer 4: Joule Service

• IAS tenant not found during booster prerequisites
• Cloud Identity system host not found
• IAS system missing from System Landscape
• Build Work Zone not in booster dropdown
• SAP S/4HANA Private Cloud Option missing from booster
• SaaS subscription failed (das-application)
• Formation creation error (IAS not enabled in Work Zone)
• Joule scenario selected but execution fails with empty response/error/timeout

Layer 5: Connectivity

• “I'm having trouble connecting” error
• SAP Cloud Connector cannot connect to subaccount
• “Digital Assistant not found” error
• Runtime destination proxy type incorrectly set causing navigation link failures

Layer 6: Backend System

• Required OData services not activated
• Business roles missing required semantic objects
• Content exposure not configured correctly
• Custom roles not working with Joule – missing semantic objects, App IDs, or wrong CDM exposure

Layer 7: SAP Business Technology Platform

• Joule service not available in subaccount entitlement
• Entitlements not available despite supported data center
• System Landscape menu not visible
• SAP systems not visible in SAP BTP System Landscape
• E2E setup requires high manual effort due to documentation gaps

SAP Support Components Reference

When self-resolution is not possible, raise an SAP incident using the appropriate component:

When raising a ticket, always include:

• SAP S/4HANA system name and release version
• Correlation ID (from Joule traces)
• Downloaded trace .zip file
• Screenshots of the error
• Steps to reproduce

See SAP Note 3666014 – Information required for Joule troubleshooting for the complete list of information SAP Support requires.

Troubleshooting Toolkit: Verify Your Configuration

Here is the troubleshooting toolkit organized by architecture layer:

Layer 1: Client / UX

• Joule Download Traces (Settings > About)
• Correlation ID (last 5-10 messages in trace)
• Transaction /UI2/FLC — SAP Fiori Launchpad content check
• Transaction /UI2/INVALIDATE_GLOBAL_CACHES — Cache clear

Layer 2: SAP Cloud Identity Services

• IAS Admin Console (authentication logs, trust configuration)
• IPS Admin Console (provisioning job status, transformation errors)

Layer 3: SAP Build Work Zone

• SAP Build Work Zone Navigation API

Layer 4: Joule Service

• Joule Booster logs (execution history, error details)
• Formation configuration status in SAP BTP Cockpit

Layer 5: Connectivity

• Transaction SMICM — ICM trace (Principal Propagation)
• SAP Cloud Connector Logs (tunnel/TLS trace)
• SAP BTP Destination — Connection Test

Layer 6: Backend System

• Transaction /n/IWFND/TRACES — HTTP Payload trace
• Transaction /UI2/CDM3_EXP_SCOPE — Content Exposure

Layer 7: SAP Business Technology Platform

• SAP BTP Cockpit UI (entitlements, system landscape, subaccount config)

Health Checks: Validate Your Configuration

Before onboarding business users, perform these quick validation tests or dobule checks after apply fixes:

• Test a transactional capability: Prompt Joule with “Display Sales Order 911” (or a valid order number). If Joule returns actual business data, the end-to-end configuration is working.
• Test Principal Propagation: Use the CDM URL test through SAP Build Work Zone as described in Path E above.
• Test content exposure: Access the CDM URL directly in a browser with the technical user (V1: http://:/sap/bc/ui2/cdm3/entities or V2: http://:/sap/bc/http/ui2/flp_content_exposure/entities)
• Verify user roles in SAP Build Work Zone: SAP Build Work Zone Admin > Settings > Identity Provisioning > Search for user > Confirm roles are listed.
• Check Navigation API: Access the navigation API to verify intent-based navigation targets.
• All the details in SAP Build Work Zone, standard edition and Joule health checks

Key Takeaways

Start Here: Identify the Problem Layer

Before fixing anything, figure out where the issue lives. This saves time and prevents fixing the wrong thing.

Most Common Problem

Joule gives information instead of completing tasks =  This is almost always a role/content exposure/IPS sync issue (Path D).

Quick Checklist (Check These First)

•  Are user roles synced to SAP Build Work Zone?
•  Is the content accessible/exposed?
•  Is Principal Propagation working?

Prevention

• Turn on Cloud Connector alerts
• Schedule regular content sync jobs
• Refresh systems after updates

Before Contacting SAP Support

1. Download Joule traces
2. Save the Correlation ID
3. Send both with your ticket

In short: Troubleshoot systematically, check permissions first, monitor regularly, and collect error details before reaching out for support.

Additional Resources

Acknowledgments

This blog consolidates insights from the SAP S/4HANA Customer Care and Regional Implementation Group, the AI RIG team, and the Joule product teams. Special thanks to colleagues and the broader SAP community who continue to share their experiences.

We will update this blog as new issues and resolutions are identified. If you have questions or feedback, please leave a comment below.

Brought to you by the SAP S/4HANA Customer Care and RIG team