Skip to content

Latest commit

 

History

History
62 lines (50 loc) · 2.67 KB

README.md

File metadata and controls

62 lines (50 loc) · 2.67 KB
Raw

Getting Started

Welcome to your new project.

It contains these folders and files, following our recommended project layout:

File or Folder Purpose
app/ content for UI frontends goes here
db/ your domain models and data go here
srv/ your service models and code go here
package.json project metadata and configuration
readme.md this getting started guide

Next Steps

  • Open a new terminal and run cds watch
  • (in VS Code simply choose Terminal > Run Task > cds watch)
  • Start adding content, for example, a db/schema.cds.

Learn More

Learn more at https://cap.cloud.sap/docs/get-started/.

2. Log into your S/4HANA Cloud system and access **Maintain Communication Users**.

3. Click **New** and create a new communication user. Specify a **User Name, Description, and Password**. Click **Create**.

4. Access **Communication Systems**.

5. Click New and specify a **System ID**, **System Name** and click **Create**.

6. Specify a value for **Host Name** to match your S/4Cloud hostname. For eg. **myXXXXX.s4hana.ondemand.com**.

7. Enable OAuth 2.0 Identity Provider by setting the toggle to **ON**.

8. Click **Upload Signing Certificate** and upload the file your downloaded from the BTP subaccount in Step 1.

9. Copy the value after **CN=** and paste it in the **OAuth 2.0 SAML Issuer** text box. Switch the **User ID Mapping Mode** to **User UUID**.

10. Click **+** under Users for Inbound Communication.

12. Select the communication user created earlier and click **OK**.

13. Save your Communication System. 14. Access **Communication Arrangements**.

15. Click **New** and choose the value help icon to open up the list of available communication scenarios.

16. Search for **SAP_COM_0501** and select it. This communication scenario is relevant for Task Center integration.

17. Specify an **Arrangement Name** and click **Create**.

18. Use the value help icon and select the **Communication System** created earlier. The User Name for inbound communication should automatically populate. Confirm the Authentication Method is set to OAuth 2.0 and save your Communication Arrangement.

19. Click **OAuth 2.0 Detail** and make a note of the **Client ID**, **Token Service URL** and **SAML2 Audience**. These fields are required to configure the destination settings in the BTP subaccount.