Name: Business Partner SOAP Services Overview - SAP S/4HANA Technology Topics
Uploaded: 2020-8-25
Duration: 458 s
Description: In this video you will learn about the available interfaces for business partners and business partner relationships

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div>In this video you will learn about the available interfaces for business partners and business partner relationships<br></div></div>

Business Partner SOAP Services Overview - SAP S/4HANA Technology Topics

Hello, and welcome. My name is Pankaj and I work in the business  partner master data team. In this microlearning, I will give you an overview  of different SOAP services from the business partner area. This learning unit is meant for integration  architects, technical and functional consultants who are  concerned with replicating business partner data from S/4HANA systems  to clients and vice versa. There are different interfaces to replicate business partner data and business  partner relationship data. We will cover both in this learning. Using these interfaces, business partner and  business partner relationship, data can be replicated between the S/4HANA  system and client. The client can be another S/4HANA system or any supported non-S/4HANA system, like  ECC, Ariba, C4C, SCP, and so on. Let's get into details of business partner SOAP  interfaces. There are two request interfaces and two  confirmation interfaces. The request interfaces are used to replicate business data between S/4HANA system and  client, and the confirmation interfaces are used to exchange the status of replication. For every request message, a confirmation  message is mandatory. This is because only through the confirmation  message does the sender system get to know the status  of replication. Secondly, the IDs of business partner, customer,  and supplier created in the receiving system may differ from  IDs in the sender system. The sender must know IDs of created objects in  the receiver. This is achieved through the confirmation  message, which carries IDs of created objects back to  sender. Next, when the sender has to update the same  object instance, it knows what ID to pass in payload. Let's explore the request messages in detail. BusinessPartnerSUITEBulkReplicateRequest_O ut is outbound request interface, and  BusinessPartnerSUITEBulkReplicateRequest_In is inbound request interface. The outbound service interface replicates business partner from S/4HANA system to client and the inbound service  interface replicates business partner data from the client system to  S/4HANA system. You can defer to the technical specifications link to know about business data carried by these  interfaces. This can be done by scanning the respective QR code that you see on a screen. If you open any of these links, you will find three important pieces of  information. First, the WSDL of the payload through which  you can explore the interface's structure. Second, 1R0 scope item link, which explains the setup required to send the  SOAP message between two systems. And third, Business Documentation. It contains detailed documentation of segments and fields present in the interface. Coming to confirmation interfaces, BusinessPartnerSUITEBulkReplicateConfirmatio n_Out is the outbound confirmation interface. This SOAP message is sent from S/4HANA system to client in response to the inbound  request message that S/4HANA system received from client. The message lets the client know the status of  replication. In addition, it transfers IDs of objects created in  S/4HANA system to client. BusinessPartnerSUITEBulkReplicateConfirmatio n_In is inbound confirmation interface. S/4HANA system gets this message in response to the outbound request message  sent to client systems. This message lets S/4HANA system know the status of business partner data replication in  client as well as IDs of created objects in client. You can navigate to specifications base to get  more details on confirmation messages structure and detailed  documentation of fields in interface. Let's look into business partner relationships of  interfaces. The concepts behind these interfaces are similar to what we discussed for business  partner interfaces. There are two request interfaces and two  conformation interfaces. BusinessPartnerRelationshipSUITEBulkReplicat eRequest_Out is the outbound request interface and it  replicates relationship data from S/4HANA system to  client. BusinessPartnerRelationshipSUITEBulkReplicat eRequest_In is the inbound interface and it replicates business partner relationship data  from the client system. to SAP S/4HANA system. BusinessPartnerSUITEBulkReplicateConfirmatio n_Out and BusinessPartnerSUITEBulkReplicateConfirmatio n_In are the confirmation interfaces. They exchange the status of replication and IDs of created objects between S/4HANA  and client system. Further details on the interfaces can be found from the technical specification link by  scanning the QR code. So, to wrap up, the key takeaway of the session is that you now  have an overview of business partner and business partner relationship SOAP  interfaces. You also have the links to business documentation, from where you can find more  details about these interfaces. To learn more, check the openSAP platform for upcoming microlearnings on SAP S/4HANA Master Data  Management, The microlearning Replication of Business  Partner Data. will explore business partner SOAP interfaces in  more detail. The microlearning Business Partner  Relationship SOAP Service will focus on relationship SOAP interfaces. Then there will be a microlearning on Reduced  Data Model Handling. It will explain how business partner SOAP  services ensure that payloads coming from non- S/4HANA systems where the data model is different from S/4HANA  don't delete data in S/4HANA. Thank you, and goodbye.