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

[Kunal-Jaiswal]

• Overview
• Prerequisites
• 1. Creating a Communication User
• 2. Checking the Availability of OData Services
• 3. Configuring the Cloud Connector
• In the Cloud Connector
• 4. Subscribing to SAP Self-Billing Cockpit
• 5. Assigning Role Collections to Users
• 6. Configuring Data Replication (Units of Measurement & Plants)
• 1. Configure Endpoints in SOAMANAGER
• 1.1 Common Procedure
• 1.2 Object-Specific Service Details
• 2. Define Replication Models in DRFIMG
• 2.1 Common Procedure
• 2.2 Object-Specific Outbound Implementation
• 3. Execute Data Replication in DRFOUT
• 3.1 Common Procedure
• 3.2 Important Notes
• 3.3 Save as Variant
• 4. Schedule Data Replication (Optional)
• 7. Configuring the Service for Updating Journal Entries (Automatic Posting Only)
• 1. Create an Inbound Service
• 2. Create an Outbound Service (Logical Port)
• 3. Set Up Mapping Between the Inbound and Outbound Services
• 4. Extract Deployment Scenario
• 8. Configuring the Service for Billing Integration
• 1. Create a Security Profile
• 2. Activate Pending Tasks
• 3. Define a Provider System (for Business Scenario Configuration)
• 4. Create a Technical User and Assign Logon Data
• 5. Create an Integration Scenario
• 6. Run Pending Tasks (to create logical ports)
• 7. Extract Deployment Scenario
• 8. Enable Point-to-Point Asynchronous Communication
• APIs for Billing Integration
• 9. Defining Additional Destination Properties
• Retrieving Service Endpoints for Billing Integration
• 1. Access the SOA Manager
• 2. Retrieve the Endpoint for Updating Journal Entries
• 3. Retrieve Additional Service Endpoints
• 10. Verifying the Integration Setup
• 1. Verify the Web Service Configuration in SOA Manager
• 2. Verify Additional Services
• 3. Verifying OData Services and Destination Using the API
• Summary
• Additional Information
• Blog Post Series for SAP Self-Billing Cockpit

This guide explains how to configure integration between SAP Self-Billing Cockpit and an SAP S/4HANA system. Follow the sections below step by step.

Overview

The complete setup involves the following major tasks:

Create Communication User Check OData Services Configure Cloud Connector Subscribe to Self-Billing Assign Role Collections Data Replication Journal Entry Services Billing Integration Services Destination Properties

Prerequisites

• Your global account and subaccount on SAP BTP are set up.
• You have the Administrator role for the global account.
• You have the Security Administrator role for the subaccount to manage role collections.

1. Creating a Communication User

1. Log on to the SAP GUI in the SAP S/4HANA system.
2. Run transaction SU01.
3. Enter a username and choose Technical User.
4. On the Logon Data tab:
   • Set User Type to Service.
   • Enter a password and record it (used when creating destinations in SAP BTP).
5. On the Roles tab, assign: SAP_ALL/SAP_APP.

2. Checking the Availability of OData Services

1. Log on to the SAP S/4HANA system.
2. Run transaction /IWFND/MAINT_SERVICE (Activate and Maintain Services).
3. For each required OData service, choose SAP Gateway Client → Execute to check status.

If the system returns HTTP 200, the service is working. Otherwise choose Add Service and add the missing service.

External Service Name	Processing Mode	System Aliases	Remarks
API_BUSINESS_PARTNER	Routing-based	required
API_SD_SA_SOLDTOPARTYDETN	Co-deployed only
API_OUTBOUND_DELIVERY_SRV	Routing-based	required	Version: 2
API_BILLING_DOCUMENT_SRV	Co-deployed only
API_SUBSQNT_BILLG_DOC_SBI_SRV	Co-deployed only
API_PRODUCT_SRV	Routing-based	required
API_SALESORGANIZATION_SRV	Co-deployed only
API_SALES_DOCUMENT_REASON_SRV	Routing-based	required
API_COMPANYCODE_SRV	Co-deployed only
API_CREDIT_MEMO_REQUEST_SRV	Co-deployed only		only used for Invoice Creation
API_DEBIT_MEMO_REQUEST_SRV	Co-deployed only		only used for Invoice Creation

3. Configuring the Cloud Connector

Download the SAP Cloud Connector from the SAP Tools website and install it on a server that remains continuously available. If the server is shut down, the connection between SAP Self-Billing Cockpit and SAP S/4HANA will break. For details, see Cloud Connector for SAP BTP Connectivity.

In the Cloud Connector

• Add your SAP BTP subaccount and verify the connection is Green (Connected).

  Region	Europe(Frankfurt) – AWS cf.eu10.hana.ondemand.com
  Subaccount	<Your subaccount ID>
  Display Name	By yourself
  Login E-Mail	<Your subaccount user>
  Password	<Your subaccount user password>
  Location ID	Don’t need to maintain
  Description	By yourself

  
• Under Cloud To On-Premise, add a new system mapping. Obtain host and port values in S/4 via SMICM → GOTO → Services.

• SAP S/4HANA ports:Go to the Transaction SMICM. Choose from the menu “GOTO -> Services”.You can find the ports and host information.

  
• Click the check button to check the connection availability
• Add resources (typically / for all resources) or define specific allowed paths.
• For self-billing APIs, add specific URL paths and set the Access Policy to Path and All Sub-Paths.
  API CategoryURL Path

  OData	/sap/opu/odata/sap/API_BILLING_DOCUMENT_SRV
  OData	/sap/opu/odata/sap/API_BUSINESS_PARTNER
  OData	/sap/opu/odata/sap/API_OUTBOUND_DELIVERY_SRV;v=0002
  OData	/sap/opu/odata/sap/API_PRODUCT_SRV
  OData	/sap/opu/odata/sap/API_SALESORGANIZATION_SRV
  OData	/sap/opu/odata/sap/API_SALES_DOCUMENT_REASON_SRV
  OData	/sap/opu/odata/sap/API_SD_SA_SOLDTOPARTYDETN
  OData	/sap/opu/odata/sap/API_SUBSQNT_BILLG_DOC_SBI_SRV
  OData	/sap/opu/odata/sap/API_COMPANYCODE_SRV
  SOAP	The value of the additional property CREATE_BILLING_URL_PATH configured in the destination
  SOAP	The value of the additional property UPDATE_JE_URL_PATH configured in the destination
  SOAP	The value of the additional property UPDATE_BILLING_URL_PATH configured in the destination
  SOAP	The value of the additional property SIMULATE_PRICING_PATH configured in the destination

  
  
  For APIs used in self-billing with invoice creation, specify the URL paths as follows:
  

  
  

  API CategoryURL Path

  OData	/sap/opu/odata/sap/API_BILLING_DOCUMENT_SRV
  OData	/sap/opu/odata/sap/API_BUSINESS_PARTNER
  OData	/sap/opu/odata/sap/API_OUTBOUND_DELIVERY_SRV;v=0002
  OData	/sap/opu/odata/sap/API_PRODUCT_SRV
  OData	/sap/opu/odata/sap/API_SALESORGANIZATION_SRV
  OData	/sap/opu/odata/sap/API_SALES_DOCUMENT_REASON_SRV
  OData	/sap/opu/odata/sap/API_SD_SA_SOLDTOPARTYDETN
  OData	/sap/opu/odata/sap/API_SUBSQNT_BILLG_DOC_SBI_SRV
  OData	/sap/opu/odata/sap/API_CREDIT_MEMO_REQUEST_SRV
  OData	/sap/opu/odata/sap/API_DEBIT_MEMO_REQUEST_SRV
  OData	/sap/opu/odata/sap/API_COMPANYCODE_SRV
  SOAP	The value of the additional property CREATE_BILLING_URL_PATH configured in the destination
  SOAP	The value of the additional property CREATE_INVOICE_URL_PATH configured in the destination
  SOAP	The value of the additional property SIMULATE_PRICING_PATH configured in the destination

  
  Check the cloud connectors in SAP BTP subaccount.
  
  

  
  

4. Subscribing to SAP Self-Billing Cockpit

1. Log on to the SAP BTP Cockpit (Cloud Foundry).
2. Navigate to Connectivity → Destinations → New Destination.
3. Create a destination with the following values:
   • Name: SELFB_DEST_S4HANA (must match exactly)
   • Type: HTTP
   • URL: Virtual host and port from Cloud Connector
   • Proxy Type: OnPremise
   • Authentication: Basic Authentication
   • User / Password: Communication user created earlier
   • Add additional property can be created with : SAP_CLIENT
4. Use Check Connection to validate.
5. Open Service Marketplace, select SAP Self-Billing Cockpit, and choose Create to subscribe.

5. Assigning Role Collections to Users

Create role collections in SAP BTP and assign the recommended roles:

• Admin – SAP_BR_ADMINISTRATOR
• Billing_Clerk – SAP_SELFB_CLERK
• Confirmation – SAP_SELFB_CR_API
• Transmission – SAP_SELFB_TR_API

Assign these collections to your technical and business users as required.

• Create a technical user in your own IDP service.
• Log on to the SAP BTP cockpit (Cloud Foundry environment) with your registered subaccount.
• Choose Security > Role Collections.
• Create a role collection, enter a name and a description, and save the settings.

6. Configuring Data Replication (Units of Measurement & Plants)

This section covers:

• Setting up SOA endpoints
• Creating replication models via DRFIMG
• Executing and scheduling replication jobs via DRFOUT and SM36

This guide explains how to configure, execute, and optionally schedule master data replication from SAP S/4HANA to SAP Self-Billing Cockpit 

---

1. Configure Endpoints in SOAMANAGER

Follow these steps for each object, using its specific service name and endpoint path.

---

1.1 Common Procedure

1. Log on to SAP S/4HANA and run SOAMANAGER.

2. Navigate to Service Administration → Web Service Configuration.

3. Search for the required service (listed below).

4. Choose Create → Manual Configuration.

5. Enter a logical port name and description.

6. Mark the port as default, then choose Next.

7. Under Consumer Security:

   • Set Authentication: User ID / Password

   • Enter the SAP BTP technical user credentials

   • Click Next

8. Under HTTP Settings → URL Components, configure:

   • Protocol: HTTPS

   • Host: <subdomain>.eu10.selfbilling.cloud.sap

   • Port: 443

   • Path: (see table below)

9. Under SOAP Protocol:

   • RM Protocol: SAP RM

   • Message ID Protocol: SAP Message ID

   • Data Transfer Scope: Minimal Data Transfer

   • Transfer Protocol: Transfer via HTTP header

10. Activate and save the logical port as the default port.

---

1.2 Object-Specific Service Details

Object Service Name Endpoint Path

Units of Measurement	UNITOFMEASUREMENTMASTERDATAREPLICATIONBUNDLEREQUEST_OUT	/api-password/selfbilling-core-service/v1/erpintegration/data/UnitOfMeasurementMasterDataReplicationBundleRequest_In
Plants	PLANTMASTERDATAREPLICATIONBUNDLEREQUEST_OUT	/api-password/selfbilling-core-service/v1/erpintegration/data/plantsSync

Note:
If using a custom identity provider, append:
?login_hint=%7B%22origin%22%3A%22sap.custom%22%7D
to the end of the path.

---

2. Define Replication Models in DRFIMG

Steps below apply to both UoM and Plant models, with only the implementation differing.

---

2.1 Common Procedure

1. Run DRFIMG.

2. Navigate to:
   Data Replication → Define Custom Settings for Data Replication → Define Replication Models

3. Choose New Entries and create:

   • A replication model name (e.g., UOM_999, PLANT_999)

   • A description
     Save the model.

4. Select the model → choose Assign Outbound Implementation.

5. Choose New Entries, assign outbound implementation (see table below).

6. Select the outbound implementation → choose
   Assign Target Systems for Repl. Model / Outb. Impl.

7. Add a new entry with your business system name.

8. (For UoM only) Assign outbound parameters if required.

9. Return and activate the replication model.

---

2.2 Object-Specific Outbound Implementation

Object Outbound Implementation

Units of Measurement	ARIBA_999
Plants	LMDR_PLANT

---

3. Execute Data Replication in DRFOUT

Use this single process for both UoM and Plant models.

---

3.1 Common Procedure

1. Run DRFOUT.

2. Select:

   • The replication model created earlier

   • The corresponding outbound implementation

3. Set Replication Mode = Manual.

4. Execute data replication.

---

3.2 Important Notes

• Ensure the SAP Self-Billing Cockpit subscription is active.

• The SAP BTP technical user must have the role:
  SAP_BR_ADMINISTRATOR

• Trigger manual replication whenever master data is updated before the scheduled job runs.

---

3.3 Save as Variant

1. After executing replication, return to the selection screen.

2. Save the selection as a variant.

3. Enter:

   • Variant name

   • Description

4. Save.

(Repeat once for UoM and once for Plant replication.)

---

4. Schedule Data Replication (Optional)

This procedure is identical for both replication models.

1. Run SM36.

2. Choose Job Wizard.

3. Provide:

   • Job Name

   • ABAP Program: RDRF_MESSAGE_OUT

   • Variant: Select the variant (UoM or Plant)

   • Set scheduling frequency

4. Save and activate the job.

5. Monitor under Own Jobs

The steps are similar for Units of Measurement and Plants; only the specific service names and outbound implementations differ.

7. Configuring the Service for Updating Journal Entries (Automatic Posting Only)

Key tasks:

• Create inbound and outbound SOAP services using SOAMANAGER.
• Configure security, HTTP settings, and logical ports.
• Map logical ports to tenant IDs.
• Run /AIF/CONTENT_EXTRACT to extract deployment scenario SAP_COM_0002.

  1. Create an Inbound Service

  1. Log on to your SAP S/4HANA system and run transaction SOAMANAGER to open the SOA Manager.

  2. Navigate to Service Administration → Web Service Configuration.

  3. Search for the object JOURNALENTRYBULKCHANGEREQUEST_ and select the result.

  4. Choose Create Service to create a binding.

  5. In the Provider Security tab:

     • Set Transport Level Security to SSL (HTTPS).

     • Set Transport Channel Authentication to User ID / Password.

  6. Activate the binding.

  ---

  2. Create an Outbound Service (Logical Port)

  1. Run transaction SOAMANAGER again.

  2. Navigate to Service Administration → Web Service Configuration.

  3. Search for the object CO_FINS_JOURNAL_ENTRY_BULK_CHA and select the result.

  4. Under Create, choose Manual Configuration.

  5. Enter a logical port name and description, mark it as the default logical port, and note the port name for later use.

  6. On the Consumer Security tab:

     • Select User ID / Password as the authentication method.

     • Enter the User Name and Password of the technical user created in SAP BTP.

  7. On the HTTP Settings tab:

     • Protocol: HTTPS

     • Host: <subdomain>.eu10.selfbilling.cloud.sap

     • Port: 443

     • Path: /api-password/selfbilling-confirmation-service/v1/api/JournalEntryBulkChangeConfirmation_In

     • Keep all other fields as default.

     Note:
     If you use a custom identity provider (instead of SAP ID service), append the following to the end of the path:
     ?login_hint=%7B%22origin%22%3A%22sap.custom%22%7D

  8. On the SOAP Protocol tab:

     • RM Protocol: SAP RM

     • Message ID Protocol: Suppress ID Transfer

     • Data Transfer Scope: Minimal Data Transfer

     • Transfer Protocol: Transfer via HTTP Header

  9. Choose Next and complete the configuration.

  ---

  3. Set Up Mapping Between the Inbound and Outbound Services

  1. In SAP S/4HANA, run transaction SPRO.

  2. Navigate to:
     SAP Reference IMG → Financial Accounting → Financial Accounting → Global Settings → API Settings for API Monitoring → Map External System and Logical Port

  3. Choose New Entries and maintain the following:

     • External System ID: Your BTP subaccount tenant ID

     • Logical Port: The outbound logical port created earlier

  ---

  4. Extract Deployment Scenario

  1. Run transaction /AIF/CONTENT_EXTRACT.

  2. Extract deployment scenario SAP_COM_0002.

8. Configuring the Service for Billing Integration

This section includes:

• Creating a security profile in SOAMANAGER.
• Activating pending tasks and rebuilding lists.
• Creating provider systems and uploading WSDL files.
• Assigning service groups and creating integration scenarios.
• Running pending tasks and enabling point-to-point communication for async services.

  1. Create a Security Profile

  1. Log on to your SAP S/4HANA system and run transaction SOAMANAGER to open the SOA Manager.

  2. Navigate to Technical Administration → Profile, then choose Create Profile.

  3. On the General tab, enter a profile name and choose Next.

  4. On the Security tab:

     • Set Transport Level Security to SSL (HTTPS).

     • Set Transport Channel Authentication to User ID / Password.

     • Choose Next, then Finish.

  5. Activate the profile.

  ---

  2. Activate Pending Tasks

  1. In SOAMANAGER, go to Service Administration → Pending Tasks.

  2. Choose Switch to Expert Mode.

  3. Choose Filter by Profile and Version, select the profile you created, and set Version = 1.

  4. Choose Rebuild List to refresh the pending-task list for that profile.

  5. Choose Process List and verify that all tasks were processed successfully.

  ---

  3. Define a Provider System (for Business Scenario Configuration)

  1. In SOAMANAGER, navigate to Technical Administration → Provider Systems.

  2. Choose Create Special → Create Third-Party System.

  3. On the General tab:

     • Enter a system name (use the tenant ID of your BTP subaccount).

     • Select the security profile you created.

     • Choose Next.

  4. On Services Search Settings, enter the SAP S/4HANA credentials that WSIL will use, then choose Check to verify authentication.

  5. Return to the provider systems list, select the provider system you created, and choose Edit.

  6. On the WSDL Assignments tab, choose Upload and upload the outbound WSDL files you downloaded from the API Hub.

     • Important: Before uploading, update any host/subdomain placeholders in the WSDL files to match your environment (<subdomain>.eu10.selfbilling.cloud.sap, or your custom host).

     • If you use a custom identity provider instead of the SAP ID service, append the following to each service path:

       ?login_hint=%7B%22origin%22%3A%22sap.custom%22%7D

  7. Continue through the wizard and activate the provider system.

     

  If you see a connection-check warning when validating the provider system, it is often a transient or expected message depending on your network/WSIL setup — you can ignore it if other checks pass and WSDLs upload successfully.

  ---

  4. Create a Technical User and Assign Logon Data

  1. In SOAMANAGER, go to Service Administration → Logon Data Management.

  2. Create logon data entries with the Authentication Method set to User/Password (or X.509 as required) and store the credentials. Save your changes.

  3. Open the Assignments tab and choose Create.

  4. For Provider IBC Reference, select the provider system you defined earlier. Choose Restrict to Service Group / Consumer Factory and enter the service group:

     SDBIL_SBI_BD_UPD_API_OUT

  5. Choose Next, select the logon data you created, and choose Finish.

  6. Repeat the assignment (steps 3–5) for these service groups:

     • SDBIL_SBI_CDM_API_OUT

     • SDBIL_SBI_SMLTE_API_OUT

     • SDBIL_SBI_BD_CREATE_API_OUT

  ---

  5. Create an Integration Scenario

  1. In SOAMANAGER, go to Service Administration → Local Integration Scenario Configuration and create a new integration scenario.

  2. On the Service Definitions tab, add the inbound services and assign the security profile you created:

     • BD_UPDATE_SBI_REQUEST_IN

     • CREDITDEBITMEMOREQUEST_IN

     • BDSIMULATEPRICINGREQUEST_IN

     • BDCREATESELFBILLINGREQUEST_IN
       Then choose Next.

  3. Add the outbound service groups and set the Provider IBC Reference to the provider system you created:

     • SDBIL_SBI_BD_UPD_API_OUT

     • SDBIL_SBI_CDM_API_OUT

     • SDBIL_SBI_SMLTE_API_OUT

     • SDBIL_SBI_BD_CREATE_API_OUT

  4. For Logon Data, select the logon entry you created earlier.

  5. Confirm and activate the integration scenario.

  ---

  6. Run Pending Tasks (to create logical ports)

  1. In SOAMANAGER → Service Administration → Pending Tasks, switch to Expert Mode.

  2. Choose Filter by Business Scenario, and enter the integration scenario name you created.

  3. Choose Process List — this creates the logical ports and other objects defined by the scenario.

  ---

  7. Extract Deployment Scenario

  Run transaction /AIF/CONTENT_EXTRACT and extract the deployment scenario SAP_COM_0564.

  ---

  8. Enable Point-to-Point Asynchronous Communication

  1. Run transaction SPRO.

  2. Navigate to:

     SAP Reference IMG → Cross-Application Components → Processes and Tools for Enterprise Applications → Enterprise Services → Point-to-Point Enablement for Asynchronous Enterprise Services → Activate Support for Point2Point Communication

  3. Activate support if it is not already enabled.

  ---

  APIs for Billing Integration

  Download the WSDLs for these services from the API Hub and upload them to your provider system. Update host/subdomain placeholders before upload.

  Service Name SBINV SBWAP Remarks

  CreditDebitMemoConfirmation_Out	Yes	Yes	Used in versions earlier than S/4HANA 2020 FPS02
  CreditDebitMemoConfirmation_Out_V2	Yes	Yes	Use for S/4HANA 2020 FPS02 or later
  BD_Update_SBI_Confirmation_Out	No	Yes
  BDSimulatePricingConfirmation_Out	Yes	Yes
  BDCreateSelfBillingConfirmation_Out	Yes	No

  

  • SBINV / SBWAP columns indicate whether each API is present for standard Self-Billing (SBINV) and Self-Billing with Adjustment Processing (SBWAP) scenarios.

9. Defining Additional Destination Properties

Add the following properties to the destination:

• CREATE_BILLING_URL_PATH
• UPDATE_JE_URL_PATH
• UPDATE_BILLING_URL_PATH
• CREATE_INVOICE_URL_PATH
• UI_SALES_ORDER_PATH
• SIMULATE_PRICING_PATH
• UI_* paths (UI_BILLING_PATH, UI_DELIVERY_PATH, etc.)
• SAP_CLIENT

Name	Value	Remark
CREATE_BILLING_URL_PATH	Path of the API for creating credit memos or debit memos in your SAP S/4HANA system
UPDATE_JE_URL_PATH	Path of the API for updating journal entries in your SAP S/4HANA system	Only for SBWAP
UPDATE_BILLING_URL_PATH	Path of the API for updating billing documents in your SAP S/4HANA system	Only for SBWAP
CREATE_INVOICE_URL_PATH	Path of the API for creating invoices in your SAP S/4HANA system	Only for SBINV
SIMULATE_PRICING_PATH	Path of the API for pricing simulation in your SAP S/4HANA system
UI_BILLING_PATH	It is in the format of https://<host>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html#BillingDocument-displayFactSheet&/C_BillingDocumentFs('%s'), where <host> is your host name.
UI_SALES_ORDER_PATH	It is in the format of https://<host>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html#SalesOrder-displayFactSheet&/C_SalesorderFs('%s'), where <host> is your host name.
UI_DELIVERY_PATH	It is in the format of https://<host>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html#OutboundDelivery-displayFactSheet&/C_OutboundDeliveryFs('%s'), where <host> is your host name.
UI_CMR_PATH	It is in the format of https://<host>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=<sap client>#CreditMemoRequest-display?CreditMemoRequest=%s, where <host> is your host name and <sap client> is the client number of your SAP S/4HANA system.
UI_DMR_PATH	It is in the format of https://<host>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=<sap client>#DebitMemoRequest-display?DebitMemoRequest=%s, where <host> is your host name and <sap client> is the client number of your SAP S/4HANA system.
SAP_CLIENT	Client number of your SAP S/4HANA system.

To obtain the correct paths, use SOAMANAGER → Web Service Configuration and check the Calculated Access URL for each service binding.

Retrieving Service Endpoints for Billing Integration

Follow the steps below to obtain the endpoint paths required for configuring billing-related services in your SAP S/4HANA system.

1. Access the SOA Manager

1. Log on to your SAP S/4HANA system and run transaction SOAMANAGER to open the SOA Manager.

2. In the Service Administration section, choose Web Service Configuration.

---

2. Retrieve the Endpoint for Updating Journal Entries

1. Search for the object named JOURNALENTRYBULKCHANGEREQUEST_ and open the result.

2. Select the service that you created for updating journal entries and display its Binding.

3. Choose Transport Settings and note the value in Calculated Access URL.
   This represents the API endpoint for updating journal entries.
   → Assign this value to the property UPDATE_JE_URL_PATH.

---

3. Retrieve Additional Service Endpoints

Repeat Steps 1–3 above for each of the following services, and assign the extracted Calculated Access URL to the corresponding property name.

Purpose Property Name Object Name in SOA Manager

Service for updating billing documents	UPDATE_BILLING_URL_PATH	BD_UPDATE_SBI_REQUEST_IN
Service for creating billing documents	CREATE_BILLING_URL_PATH	CREDITDEBITMEMOREQUEST_IN
Service for simulating pricing	SIMULATE_PRICING_PATH	BDSIMULATEPRICINGREQUEST_IN
Service for invoice creation	CREATE_INVOICE_URL_PATH	BDCREATESELFBILLINGREQUEST_IN

10. Verifying the Integration Setup

This section explains how to validate your integration configuration. The example below uses the service for updating journal entries, but the same approach applies to other related services.

1. Verify the Web Service Configuration in SOA Manager

1. Log on to your SAP S/4HANA system and run transaction SOAMANAGER to open the SOA Manager.

2. Under Service Administration, choose Web Service Configuration.

3. Search for the object CO_FINS_JOURNAL_ENTRY_BULK_CHA and open the result.

4. Select the service you created for updating journal entries and choose Ping Web Service.

   

5. If the response shows HTTP 405, the integration setup is correct.

   

2. Verify Additional Services

Repeat the steps above to ping and validate the following services in your SAP S/4HANA system:

Purpose	Object Name
Service for updating billing documents	SDBIL_SBI_BD_UPD_API_OUT
Service for creating billing documents	SDBIL_SBI_CDM_API_OUT
Service for simulating prices	SDBIL_SBI_SMLTE_API_OUT
Service for invoice creation	SDBIL_SBI_BD_CREATE_API_OUT

3. Verifying OData Services and Destination Using the API

You can further validate the configuration of OData services and the destination by performing a check through the API.

Steps:

1. Open Postman and create a GET request.

2. Enter the following URL:  https://<subdomain>/api-password/selfbilling-customizing-service/v1/api/check

   Replace <subdomain> with the subdomain of your BTP subaccount.

3. Go to Authorization, set Type = Basic Auth, and enter the username and password of the technical user assigned with the SAP_BR_ADMINISTRATOR role.

4. Execute the request.

Expected Result:

• All items under odataCheck return “200 OK”

• Configuration Missing under additionalCheck is empty

If both conditions are satisfied, your integration setup is correct.👌

Summary

1. Configure communication and OData in the S/4HANA system.
2. Set up Cloud Connector and create the OnPremise destination in SAP BTP.
3. Subscribe to Self-Billing Cockpit and assign required role collections.
4. Configure replication models, SOAP services, and billing integration scenarios.
5. Complete destination properties and verify all services.

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 Cloud
• 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)