In this blog post, we explain step by step how to configure SAP S/4HANA and SAP Customer Checkout manager to transfer material master data from SAP S/4HANA to SAP Customer Checkout manager. This blog is part of a series that conveys how the out-of-the-box integration of SAP Customer Checkout manager works for the sync materials, business partners, posting of receipts and the stock check.
In the following, we first configure the SAP Customer Checkout manager to provide an inbound endpoint for material master data synchronization calls, and continue then with SAP S/4HANA.
Configuring SAP Customer Checkout manager
First, we configure a technical user in SAP Customer Checkout manager. For that, open the app Users.
In the users app, click on the “+” button to create a new user. In the create screen, enter the following:
Select a user name, enter the password, leave the role assignment empty, take the “Force password change” flag out and set the “Technical user” flag to true. This is very important for the following. Leave all other fields empty and save the new user.
After saving the user successfully, navigate to the tab “Permissions”, click on Edit and set the permission “Access SAP Customer Checkout manager” to Yes for this user. Save the change.
Go back to the home screen and navigate to the app “Communication systems”. Click on the “+” button to create a new system. Select the scenario “SAP S/4HANA”, enter a name and set the status to “Active”. Save the communication system.
In order to receive material master data from SAP S/4HANA, no further configuration is needed in this app. Go back to the home screen and navigate to the app “Communication arrangements”. Click on the “+” button to create the according communication arrangement.
Click on Save. As next, navigate to the tab “Configuration”. Click on Edit and in the dropdown for “Inbound user”, select the above created technical user for SAP S/4HANA integration.
Save the change and navigate to the tab “Inbound services”. Here you see two entries, one for the business partner master data sync, one for the material master data. Select the entry “ProductMerchandiseViewReplicationBulk”.
In the detail page of the service, click on Edit, set the status of the service to Active and save the change.
Navigate to the tab “Configuration”. Here you can configure the settings of the material inbound call handling for this inbound service.
By setting the inbound service to active, a SOAP endpoint got activated and can be consumed. For that, open a new browser tab and enter “http(s)://<servername>:<port>/ccos/soap”. Here all active SOAP endpoints are listed.
With that, SAP Customer Checkout manager is prepared to receive material master data from SAP S/4HANA. In order to have the most convenience after material sync, two further actions should be taken: Configure the plants as POS groups in SAP Customer Checkout manager and adapt the tax settings.
POS group configuration
During the material sync, SAP Customer Checkout manager will create price lists on the fly for each triple of plant, condition type and currency (e.g. ALE1_VKP0_EUR). If the according POS group is found during the sync, SAP Customer Checkout manager will assign the newly created price list automatically with the POS group.
To create a POS group, navigate back to the SAP Customer Checkout manager home screen and open the app “Organizational structure”. Click on the “+” button and select “POS group” to create a new POS group.
Do not forget to set the Plant ID field by which the explained mechanism works.
Tax rate configuration
Compare the settings in SAP Customer Checkout manager against the configuration in SAP S/4HANA, if the tax codes and rates are aligned. The same has to be done later between SAP Customer Checkout manager and SAP Customer Checkout. In SAP Customer Checkout manager, these are maintained in the app “Tax rates”.
In the following, we configure the outbound call on SAP S/4HANA side.
Configuring SAP S/4HANA POS outbound
In this section, we create a business system, the replication model and configure the outbound implementation. We will then assign sites to a reference site, set up the SOAP endpoint, define the filter criteria and initiate the call to sync materials.
First, we create a business system and define the outbound implementations. Open the transaction DRFIMG.
Select “Define Technical Settings for Business Systems”. Click here on “New Entries”. Enter in the column “Business System” a name for the business system, e.g., “CCOM”. Leave the other fields empty and click on save. Despite the validation marks the empty columns, the business system is created, which is enough for our purposes.
Once saved, click on Exit to navigate back to the main page. Open the entry “Define Replication Model”.
Create here an new replication model, e.g., “CCOM_POS”. Select the newly created replication model and navigate in the dialog structure to “Assign Outbound Implementation”. Select here the outbound implementation “0100” and save the change.
Select the outbound implementation “0100” and open in the Dialog structure the node “Assign Target Systems for Replication”. Assign here the newly created business system “CCOM” and save the change.
Open the node “Assign Outbound Parameter” in the dialog structure. Here, you can set the parameters that influence prices for which validity period will be sent out, the package sizes, etc..
Open the node “Assign Language” to assign languages that shall be supported in outbound calls.
Reference site assignment
Make sure that all changes are stored. As next, we assign the sites to our outbound implementation.
Open the transaction REFSITE.
Click on “Creation” to create a new reference site. In the dialog, set the group type “POS Outbound” and enter the reference site. Once created, you can select sites to assign receiving stores.
The next step is to configure the web service endpoint in the SOA manager. Open the transaction SOAMANAGER. Select here the link “Web Service Configuration”.
For the search criterion “Object Name”, enter “ProductMerchandiseViewReplicationBulkRequest_Out” and click on search. In the list below, you will find an entry with the internal name “CO_WART_PRMRCHV_REPLBLKQ_OUT”. Open the entry by clicking on the link.
In the opened view, click on “Create” and select “WSDL Based Configuration”.
Enter a logical port name and set the logical port as default.
In the WSDL Information section, leave the WSDL base as “Via HTTP Access” and enter the URL for the WSDL access. For that, open the SOAP endpoint page of SAP Customer Checkout manager (e.g. http://localhost:6060/ccos/soap), navigate to the WSDL link and copy the URL from the browser URL address input including the “?wsdl” suffix.
In the section “Binding Selection”, check that one binding is shown as depicted below.
In the section “Customer Security”, enter the user name and password of the technical integration user that we created in the beginning of the blog. All other flags remain as they are.
In the section “HTTPSettings”, no change is needed. Check that the values are set as shown in the screenshot.
In the section “SOAP Protocol”, make sure that as RM Protocol “SAP RM” is selected and as Message ID Protocol “SAP Message ID”. If these two values are not set, the communication to SAP Customer Checkout manager will not work successfully.
In the section “Identifiable Business Context”, leave the sender and receiver fields empty and the Suppress sending of IBC identifier on false. In the last section “Operation Settings”, set the flag in the Transport Binding section to false, if set.
With that, the logical port is finally configured. If not already done, please ensure that the logical port is active and that it is set as default. Otherwise, no call will be sent out.
Use the ping function to check if the connection to your SAP Customer Checkout manager can be established.
Configuring the filter criteria
In the following, we define the filter criteria. Open the transaction DRFF.
Select here the Product Merchandise replication model. Set here the filter criteria according to your needs.
We prepared the SAP S/4HANA POS outbound to send material master data. Let’s initiate a call from SAP S/4HANA to SAP Customer Checkout manager.
Configuring the data replication framework
Open the transaction DRFOUT. Select first our replication model “CCOM_POS”. Then, select the Outbound Implementation “0100”. You can choose between an initial full sync, a delta sync (“Changes”) or a manual selection of articles to be sent out. Select “Initialization” and click on “Execute”.
The initial load might take a while. Once the call is made, the view changes and the logs are displayed.
By clicking on the magnifier in the “Det.” column, you can drill down and gather more information on the payload generation.
Open the transaction SRT_MONI. Configure the filter according to the needs and click on Execute.
Here, you can see the status of the call to SAP Customer Checkout manager on SAP S/4HANA side.
Doubleclick on the entry to open the detail page. Here, you can see the payload sent out and access it as well as XML.
Checking incoming master data calls in SAP Customer Checkout manager
In SAP Customer Checkout manager, you can check if the call has reached and if the payload is processed successfully. For that, you find three apps in the Monitoring section, Inbound call monitoring, Master data queue and Master data results.
In the app “Inbound call monitoring”, we can check if the call from SAP S/4HANA has successfully reached the SAP Customer Checkout manager and at what time precisely. The status is success when the payload of the external system could be mapped and queued properly. The processing itself happens asynchronously.
In the app “Master data queue”, entries can be seen when payloads are not yet or currently in processing. Once the entries are processed, the results can be seen in the “Master data results” app.
When an entry is selected, one can see per material in the payload the processing result. If any error came up, these are shown in the “Error message” column.
After all these steps, the articles are successfully synced to SAP Customer Checkout manager, price lists are created per triple of site, condition type and currency. If the according POS groups have been created before, the price lists are assigned to the POS groups and the articles can be synced to the cash desks. The article groups (material groups) in the payload are created on the fly in SAP Customer Checkout manager and can be brought in hierarchy if desired.
With SAP S/4HANA via the Product merchandise SOAP call, we support the sync of sales sets and generic articles (variants) to SAP Customer Checkout manager as well.