Integration Setup : SAP Self-Billing Cockpit Integration with SAP S/4HANA Cloud - 2025

[Kunal-Jaiswal]

• Prerequisites
• Enabling Communication in SAP S/4HANA Cloud
• Creating a Communication User
• Creating a Communication System
• Creating Communication Arrangements
• Subscribing to SAP Self-Billing Cockpit
• Configuring Destinations
• Assigning Role Collections to Users
• Creating Other Communication Arrangements
• For Scenario SAP_COM_0564
• For Scenario SAP_COM_0002 (SBWAP only)
• For Scenario SAP_COM_0114
• For Scenario SAP_COM_0116
• Verifying the Setup
• Summary
• Additional Information
• Blog Post Series for SAP Self-Billing Cockpit

This guide describes how to set up the integration between the SAP Self-Billing Cockpit and an SAP S/4HANA Cloud system without requiring a cloud connector. It covers both self-billing with automatic posting (SBWAP) and self-billing with invoice creation (SBINV).

Prerequisites

• You have set up your global account and subaccount.
• You are assigned the Administrator role for the global account.
• You are assigned the Security Administrator role for the subaccount to configure authorizations using role collections.

Enabling Communication in SAP S/4HANA Cloud

Creating a Communication User

1. Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system.
2. Open the Maintain Communication Users app: Communication Management > Maintain Communication Users.
3. Choose New.
4. Enter the name, description, and password for the new user.
5. Choose Create.
6. Record the user name and password for future use. These are required when you create communication arrangements and destinations to SAP S/4HANA Cloud via the SAP BTP cockpit.

Creating a Communication System

1. Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system.
2. Launch the Communication Systems app: Communication Management > Communication Systems.
3. Choose New to create a communication system.
4. On the New Communication System screen, specify the system ID and system name.
5. Choose Create.
6. In the Technical Data area, specify:
   • The hostname (the host URL of the self-billing tenant excluding https://, e.g. <subdomain>.eu10.selfbilling.cloud.sap)
   • The logical system name
   • The business system name (your subaccount ID assigned by the SAP BTP cockpit)
   The subdomain is defined when you create a subaccount. Ensure it is identifiable and meaningful for you. You can find your subdomain and subaccount ID in the SAP BTP cockpit.
7. In the Users for Inbound Communication area, add a user:
   • On the New Inbound Communication User screen, enter the communication user name you created earlier, specify the authentication method, and save the settings.
8. In the Users for Outbound Communication area, add a user:
   • On the New Outbound Communication User screen, enter the technical user name you created earlier.
9. Save your settings and record the communication system name for future use.

Creating Communication Arrangements

Create communication arrangements for the following scenarios before you proceed.

• SAP_COM_0367
• SAP_COM_0008
• SAP_COM_0106
• SAP_COM_0120
• SAP_COM_0087
• SAP_COM_0158
• SAP_COM_0159
• SAP_COM_0360

All these scenarios follow the same configuration procedure; this section uses scenario SAP_COM_0367 as an example.

1. Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system.
2. Launch the Communication Arrangements app: Communication Management > Communication Arrangements.
3. Choose New.
4. In New Communication Arrangement, choose SAP_COM_0367 under Scenario, optionally modify the arrangement name, and choose Create.

   

5. In the Common Data section, select the communication system you created earlier in Creating a Communication System. The previously created communication user is automatically added to both Inbound and Outbound sections (if applicable).
6. If there are any other outbound services, deactivate them and save your settings.

Subscribing to SAP Self-Billing Cockpit

Configuring Destinations

1. Log on to the SAP BTP cockpit (Cloud Foundry environment) with your registered subaccount.
2. Navigate to Connectivity > Destinations > New Destination to create a new destination for mobile services.
3. In the Destination Configuration wizard, enter:
   • Name: SELFB_DEST_S4HANA
   • URL: Hostname of the SAP S/4HANA Cloud system
   • Authentication: Basic Authentication
   • User: The communication user created in “Creating a Communication User”
   • Password: The password of the communication user created earlier
4. Save your settings and choose Check Connection to verify the connection.

Navigate to Service Marketplace in the navigation tree, locate the SAP Self-Billing Cockpit tile, and open it. Choose Create.

In the displayed screen, choose an application plan (e.g., default) and proceed as instructed. After the subscription is complete, the status changes to Subscribed.

Assigning Role Collections to Users

You can manage role collections as needed. The following table lists the recommended role collections.

Role Collection Role User Remarks

Admin	SAP_BR_ADMINISTRATOR	A technical user on BTP	This role grants the technical user rights to replicate units of measurement and plants data, to check the integration configuration, and to export data.
Billing_Clerk	SAP_SELFB_CLERK	Billing clerk	This role allows the billing clerk to log in to self-billing apps, make configurations, check document status, and perform processing tasks.
Archiving	SAP_SELFB_ARCHIVING	User to process archiving	This role allows the user to log in to self-billing apps and perform archiving.
Confirmation	SAP_SELFB_CR_API	A technical user on BTP	This role allows the technical user to receive confirmation messages from SAP S/4HANA Cloud.
Transmission	SAP_SELFB_TR_API	A technical user on BTP	This role allows the technical user to send transmissions to SAP Self-Billing Cockpit.

Create a technical user in your own IDP service.

1. Log on to the SAP BTP cockpit (Cloud Foundry environment) with your registered subaccount.
2. Navigate to Security > Role Collections.
3. Create a role collection, enter a name and a description, and save the settings.
4. Select the newly created role collection and edit it by adding the corresponding role.
5. If you want to verify the setup via API, you can assign the Admin role to the technical user and remember its username and password for later use.

Creating Other Communication Arrangements

For Scenario SAP_COM_0564

1. Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system.
2. Open the Communication Arrangements app: Communication Management > Communication Arrangements.
3. Choose New.
4. In New Communication Arrangement, choose SAP_COM_0564 under Scenario, optionally modify the arrangement name, and choose Create.
5. In the Common Data section, select the communication system created earlier in Creating a Communication System. The previously created communication user is automatically added to both Inbound and Outbound sections.
6. In the Outbound Services section, enter the path for the following services:

Service Path Remark

Credit/Debit Memo – Send Confirmation of Creation with Invoice Reference	/api-password/selfbilling-confirmation-service/v1/api/CreditDebitMemoConfirmation_In/V2
Billing Document – Send Confirmation of Fields Updated for Self-Billing	/api-password/selfbilling-confirmation-service/v1/api/BillingDocumentUpdateConfirmation_In	Only for SBWAP
Billing Document - Send Confirmation of Simulated Pricing	/api-password/selfbilling-confirmation-service/v1/api/BdSimulatePricingConfirmation_In
Self-Billing Invoice - Send Creation Confirmation	/api-password/selfbilling-confirmation-service/v1/api/SelfBillingInvoiceCreationConfirmation_In	Only for SBINV

Note: If you use a custom identity service as an alternative to the SAP ID service, append ?login_hint=%7B%22origin%22%3A%22sap.custom%22%7D to the end of the service path.

The service URL is automatically generated based on the tenant host name and the entered path. For example: <Self-Billing Tenant URL>/api-password/selfbilling-confirmation-service/v1/api/CreditDebitMemoConfirmation_In and <Self-Billing Tenant URL>/api-password/selfbilling-confirmation-service/v1/api/BillingDocumentUpdateConfirmation_In.

If there are other outbound services you do not use, deactivate them and save your settings. For example, if you only use SBWAP and no pricing simulation, you can deactivate them as shown below.

For Scenario SAP_COM_0002 (SBWAP only)

1. Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system.
2. Open the Communication Arrangements app: Communication Management > Communication Arrangements.
3. Choose New.
4. In New Communication Arrangement, choose SAP_COM_0002 under Scenario, optionally modify the arrangement name, and choose Create.

   

5. In the Common Data section, select the communication system created earlier in Creating a Communication System. The communication user is automatically added to Inbound and Outbound sections.
6. In the Outbound Services section, enter the path for the “Journal Entry – Change (Asynchronous) Confirmation” service: /api-password/selfbilling-confirmation-service/v1/api/JournalEntryBulkChangeConfirmation_In
   Note: If you use a custom identity service, append the login hint as described above.
7. If there are other outbound services, deactivate them and save your settings.

For Scenario SAP_COM_0114

1. Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Arrangements (Communication Management > Communication Arrangements).
3. Choose New.
4. Select SAP_COM_0114 under Scenario, optionally modify the arrangement name, and choose Create.
5. In Common Data, select the communication system created earlier. The communication user is automatically added to Inbound and Outbound sections.
6. In the Outbound Services section, set the path for the Unit of Measurement – Replicate (A2X) service to: /api-password/selfbilling-core-service/v1/erpintegration/data/UnitOfMeasurementMasterDataReplicationBundleRequest_In
   Note: If you use a custom identity service, append the login hint as described above.
7. Deactivate all other outbound services.
8. Under Additional Properties, define Replication Model and save its value (e.g., SB_UOM) for future use.
9. Navigate to the SAP Fiori Launchpad and launch Replicate by Replication Model. From the dropdown, choose an option beginning with the replication model defined in Step 8 (e.g., SB_UOM_999), then choose Replicate.

For Scenario SAP_COM_0116

1. Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Arrangements (Communication Management > Communication Arrangements).
3. Choose New.
4. Select SAP_COM_0116 under Scenario, optionally modify the arrangement name, and choose Create.
5. In Common Data, select the communication system created earlier. The communication user is automatically added to Inbound and Outbound sections.
6. In the Outbound Services section, set the path for the Plants – Replicate service to: /api-password/selfbilling-core-service/v1/erpintegration/data/plantsSync
   Note: If you use a custom identity service, append the login hint as described above.
7. Deactivate all other outbound services.
8. Under Job Execution Details, define the fields to suit your needs (daily execution is recommended).
9. Under Additional Properties, define Replication Model and save its value (e.g., SB_PLANT) for future use.
10. Navigate to the SAP Fiori Launchpad and launch Replicate by Replication Model. From the dropdown, choose an option beginning with the replication model defined in Step 9 (e.g., SB_PLANT_999), then choose Replicate.

Verifying the Setup

After completing all steps, your billing clerk can access SAP Self-Billing Cockpit:

1. Log on to the SAP BTP cockpit (Cloud Foundry environment) with your registered subaccount.
2. Navigate to your application plan, then choose Go to Application.
3. You can now view the apps in SAP Self-Billing Cockpit.

You can also verify via API:

1. In Postman, create a GET request to: https://<subdomain>/api-password/selfbilling-customizing-service/v1/api/check.
2. Under Authorization, select Basic Auth and enter the username and password of the technical user with the role SAP_BR_ADMINISTRATOR.
3. If all checks in odataCheck are 200 OK and there are no items in Configuration Missing in additionalCheck, the setup is correct.

Summary

To set up integration between SAP Self-Billing Cockpit and an SAP S/4HANA Cloud system, we first need to enable communication in the SAP S/4HANA Cloud system and then subscribe to an application plan of SAP Self-Billing Cockpit via the SAP BTP cockpit.

If you’re interested in similar topics, you can follow its tag and my profile.

Surely, you’re cordially invited to provide your feedback and insights in the comments section.

Additional Information

• SAP Self-Billing Cockpit Product Documentation

• SAP Self-Billing Cockpit on SAP Store

Blog Post Series for SAP Self-Billing Cockpit

• SAP Self-Billing Cockpit
• How to Set Up Integration Between SAP Self-Billing Cockpit and SAP S/4HANA
• How to Set Up Cloud Connector
• How to Set Up a Custom Identity Provider
• Self-Billing with Invoice Creation
• Self-Billing Cockpit Q&A
• [Feature]Automatic Execution of Self-Billing
• [Feature]Comparison of Tax in Self-Billing with Automated Posting
• [Feature]Main reference duplicate checks in self-billing with automatic posting
• [Feature]Support for multiple pricing types in the copying control for billing
• [Feature]Customize self-billing processing
• [Feature]Side-by-side extensiblity to adjust the received transmission(ABAP)
• [Feature]Side-by-side extensiblity to custom the product and customer material mapping logic(ABAP)
• [Feature] Self-Billing Ability to integrate with SAP Analytics Cloud