Hello SAP Community!  

As enabling seamless and reliable data exchange becomes more important than ever, SAP Profitability and Performance Management Cloud Standard Model (SAP PaPM Cloud SM) continues to enhance its integration capabilities with SAP S/4HANA Cloud. 

With the introduction of the new SOAP Writer, it is now possible to directly post financial data from SAP Profitability and Performance Management Cloud Standard Model to SAP S/4HANA Public Cloud, making this integration straightforward and smooth. 

In this blog post, you will learn how to configure and use the SOAP Writer for posting data from SAP Profitability and Performance Management Cloud Standard Model to SAP S/4HANA Public Cloud. 

We will go through: 

• Setup in SAP S/4HANA Public Cloud 

• Setup in SAP Profitability and Performance Management Cloud Standard Model 

Prerequisites:  

• You should have an existing SAP Profitability and Performance Management Cloud Standard Model subscription. For more information, refer to Account Setup. 

• You should have an existing SAP S/4 HANA Public Cloud account. 

Setup in SAP S/4 HANA Public Cloud 

1. Configuration of Communication User 

In SAP S/4HANA Public Cloud, a Communication User is required to enable secure system-to-system authentication. 

As shown in the figure below, navigate to the Maintain Communication Users app (1, 2) and create a new Communication User (3). During the creation, provide User Name, Description and generate the Password required for authentication (4).

For more information, refer to How to Create Communication Users. 

2. Configuration of Communication System 

The Communication System represents the external system that will communicate with SAP S/4HANA Public Cloud. 

As shown in the figure below, navigate to the Communication Systems app (1, 2) and create a new Communication System (3). During the creation, maintain the System ID and System Name (4). The Communication System created in this step will later be used when defining the Communication Arrangement for SOAP-based integration. 

In the Users for Inbound Communication section of your Communication System, maintain users for inbound and outbound communication by assigning the previously created Communication User. 

For more information, refer to Create a Communication System with Inbound and Outbound Users. 

3. Configuration of Communication Arrangement 

Communication Arrangement is used to define the exact API services that are enabled for data exchange, including inbound and outbound communication. 

To determine which communication scenario should be used, visit SAP API Business Accelerator Hub and navigate to: Products → SAP S/4HANA Cloud Public Edition. Under the SOAP APIs section, select the required API, for example Journal Entry – Post (Asynchronous), and note the Communication Scenario ID provided for the API. 

As shown in the figure below, create a new Communication Arrangement in the Communication Arrangements app by selecting the corresponding Scenario ID and assigning the previously created Communication System. 

The WSDL file that will be later required in the configuration of SAP Profitability and Performance Management Cloud Standard Model, can be downloaded directly from the Communication Arrangement in the SAP S/4HANA Public Cloud system. 

For more information, refer to Create Communication Arrangement. 

Setup in SAP Profitability and Performance Management Cloud Standard Model 

1. Setup in SAP BTP – Destination Configuration 

A destination in SAP BTP is required to enable efficient communication between SAP Profitability and Performance Management Cloud Standard Model and SAP S/4HANA Public Cloud. 

As shown in the figure below, create an HTTP destination with Basic Authentication in the SAP BTP Destination service. The destination URL points to the SAP S/4HANA Public Cloud SOAP where the SOAP requests will be sent. The destination uses the credentials of the previously created Communication User and serves as the entry point for the SOAP based integration. 

2. Configuration of the SOAP Connection  

As the first step you need to visit Connection Management screen in SAP Profitability and Performance Management Cloud Standard Model solution and create a new connection of the SOAP type. 

 
For this connection, it is essential to choose the right destination name configured previously on the SAP BTP level and to upload the appropriate WSDL or XML file. The file should describe the web service and API to be used and should be the same WSDL that was downloaded earlier from the Communication Arrangement in SAP S/4HANA Cloud. After the file is uploaded and the connection is saved, the file appears in read-only mode on the Connection Management screen.

Optionally, you can select the Overwrite Service URL option to override the default Service URL defined in the WSDL file. This is typically used when the same WSDL is reused across different SAP S/4HANA Cloud systems or environments (for example, test and production systems). 

3. Creation of SOAP Writer in the Modeling screen 

Once the SOAP Connection is successfully created, you can include the posting of your financial data to the S/4 HANA Public Cloud system in your modeling solution.  

First, select the new function type SOAP Writer from the modeling palette and assign the previously created SOAP connection under the Connection Name field. 

Note that after the connection is initially saved, it cannot be modified anymore.  

Model Table SOAP is an underlying function of the SOAP Writer and can only be added within the context of the SOAP Writer itself. Once the SOAP Writer is added to the modeling area, the related Model Table SOAP functions become available in the left‑side modeling palette.  
 

In the next step, define Model Table SOAP functions corresponding to the Model entities and fields that are included in a SOAP request. These functions reflect the exact XML structure expected by the target SOAP API. 
It is important to highlight that Model Table SOAP functions do not only contain mapped data but also define the structure of the SOAP request itself. The SOAP Writer generates the payload strictly based on this structure, which makes the correct entity hierarchy and field definitions essential for successful request processing by the API.  

In our example, using the Journal Entry – Post (Asynchronous) API, each Model Table SOAP represents a specific part of the SOAP payload (XML) for the selected API. Together, these entities form the hierarchical structure of the request that is sent to SAP S/4HANA Cloud. 

• JournalEntryBulkCreateRequest  – The root container of the SOAP payload, grouping the entire request into one message. 

• JournalEntryBulkCreateRequest.MessageHeader – Contains technical message metadata used for message identification and monitoring. 

• JournalEntryBulkCreateRequest.JournalEntryCreateRequest – Represents one Journal Entry posting request within the bulk payload. 

• JournalEntryBulkCreateRequest.JournalEntryCreateRequest.MessageHeader – Request-level message metadata for the specific Journal Entry request. 

• JournalEntryBulkCreateRequest.JournalEntryCreateRequest.JournalEntry – Contains the accounting document header data, such as company code, posting/document dates. 

• JournalEntryBulkCreateRequest.JournalEntryCreateRequest.JournalEntry.Item – Contains the Journal Entry line items, such as G/L account, amounts/currency, and debit/credit indicator. 

• JournalEntryBulkCreateRequest.JournalEntryCreateRequest.JournalEntry.Item.AccountAssignment – Contains additional account assignment information for each item. 

Note: The hierarchy between these entities is maintained using GroupId/ParentGroupId, which ensures that child nodes (for example Items) are correctly assigned to their parent node in the generated SOAP request. 

Business data to be sent to SAP S/4HANA Public Cloud is maintained by uploading customer-specific data into the corresponding Model Table SOAP functions via Data Management screen. 

Additionally, Model Table SOAP functions can be used both as input or output functions of a regular Writer, depending on the modeling scenario. 
This allows the same SOAP‑structured data to be reused or further processed within the modeling flow, beyond the execution of the SOAP Writer itself. 

With all configuration steps in place, we can now proceed to executing the SOAP Writer and validating the posting result in SAP S/4HANA Cloud. 

Posting Validation in SAP S/4 HANA Public Cloud 

After executing the SOAP Writer in SAP Profitability and Performance Management Cloud Standard Model, the execution log confirms that the SOAP request was successfully initiated, sent to the configured SAP S/4HANA Cloud endpoint and assigned a Message ID. 

The posting result can then be validated in SAP S/4HANA Cloud using the Message Monitoring for Administrators application. To locate the corresponding message, users can filter by Recipient Name, which is defined by the used SOAP API and documented in the SAP Help Portal under Message Monitoring and Error Handling. This allows verification of whether the SOAP request was successfully processed or rejected by SAP S/4HANA Cloud. 

Tip: To locate the corresponding message, users can filter by Recipient Name, which is defined by the specific used SOAP API and documented in the SAP Help Portal under Message Monitoring and Error Handling. 
Example: Journal Entry – Post Confirmation (Asynchronous) 

I hope this walkthrough helped clarify how the SOAP Writer can be used to post financial data from SAP Profitability and Performance Management Cloud Standard Model to SAP S/4HANA Public Cloud and how the different configuration pieces fit together from setup to validation. 

Thanks for reading and see you in the next topic!