Let’s look at the common issues that we may have while setting up Joule with SuccessFactors:

1. SAP BTP Booster | Entitlements Missing
2. SAP BTP Booster | Sync between Joule and SAP Cloud Identity Services System failed
3. SAP BTP Booster | No Registered Systems of type S/4HANA
4. Joule in S/4HANA Cloud | Joule icon missing in S/4HANA Cloud
5. Joule in S/4HANA Cloud | Some Prompts are Not Working
6. Joule in S/4HANA Cloud |  Not Authorised

==================================================================================

So let us take a look at the issue and how to fix them:

1. SAP BTP Booster | Entitlements Missing

While running the booster, we got the error message:

“Some of the entitlements are not available in the selected subaccount <XXXX>. Please either add them or select a subaccount with different provider or region.”

Fix: 

Go to BTP Global Account -> Entity Assignments.

Check if Joule and SAP Build Work Zone, standard edition service are entitled to the subaccount.

If Joule is not available in BTP Global Account -> Procure Joule

 

2. SAP BTP Booster | Sync between Joule and SAP Cloud Identity Services System failed

While running the Joule booster, we got the error message:

 

Fix: Please follow the KBA to setup accordingly: 

3539985 – Synchronization failed between Joule and SAP Cloud Identity Services when using booster fo…

 

3. SAP BTP Booster | No Registered Systems of type S/4HANA

While running the booster, we got the error message:

Cause: S/4HANA system is not registered with BTP global account.

Fix: Double check the steps “Register SAP S/4HANA Cloud Public Edition in BTP Global Account” in the mission.

 

4. Joule in S/4HANA Cloud | Joule icon missing in S/4HANA Cloud

There are several reasons might cause this issue, please follow below to check:

4.1 Double check the step “Update Content Security Policy Settings in S/4HANA Cloud” in mission

Follow the last step to paste the URL of your Joule application into the Trusted Content text box and click Save.

4. 2  Try opening the system in an Incognito window to rule out browser cache issues.
If Joule appears there, clear your browser cache and cookies before accessing it again in normal mode.

4.3 When logging int S/4HANA Public Cloud, check the domain of Cloud Identity Services that is used during login (e.g. ending with ondemand.com or cloud.sap) => in BTP Cockpit -> Joule Subaccount -> Trust Configuration -> Select the Cloud Identity Services used for application logon -> check if the “Domain” is set to the same domain used in S4.

4.4 Check in Cloud Identity Services if the hosting application (S/4Public Cloud) and Joule application are configured in exact same way (IDP/Conditional authentication)

 

5. Joule in S/4HANA Cloud | Some Prompts are Not Working

5.1 Cause: CDM content not synchronised

Fix: In the Channel Manager of Build Workzone, please click on “Report” to check how many apps / roles were actually synchronised.

5. 2 Cause: User lacking role assignments.

Fix:  Check whether the logged in user actually have the required groups assigned.

Check the sample prompts and corresponding roles here.

5. 3 Double check below steps in the mission

• Provision Users and Groups from S/4HANA Cloud to Work Zone
• Update Content Security Policy Settings in S/4HANA Cloud

6. Joule in S/4HANA Cloud |  Not Authorised

Cause: In rare cases the automated integration between Joule and S/4HANA might fail.

Fix: Check if the CN name used in Destination S4HANA_PUB_SSO fits to the CN name maintained in S/4HANA.
In case of mismatch open an incident with CA-JOULE

CN name in above screenshot need to match between BTP Destination and S/4 Communication System (Signing Certificate Issuer in below screenshot).

 

If the issue still persists or any other issues not listed here, open a ticket under component CA-JOULE.