Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 

1.     Introduction


  • SAP has provided a new dimension – E-SOA, with tremendous potential for customers and partners. Trends in SAP like ESOA, ESB, EDA (Event Driven Architecture), BPM have made the integration as backbone for the ideal architecture.


  • A configuration profile comprises a set of technical settings for Web services (bindings). Configuration profiles are created for the specific interdependencies between providers and consumers in a particular system landscape.


  • SOA with Integration scenario is useful when we want to replicate master data from S/4 to more than one external systems (SAP Cloud for Customer(C4C), SAP Fieldglass, BOOMI) using Data Replication Framework (DFROUT). It’s recommended to create logical ports based on Integration scenarios for service groups, rather than creating ports manually in SOAMANGER.


2.     Preparation


  • Within an integration scenario, we can create all connections based on integration scenario definitions. This is done with only a few clicks as the entire integration scenario definition has been well defined during design time.

  • We can also include connections that are based on contracts, service groups or consumer factories.

  • Service bindings can be created if we don’t know which consumer needs to consume the Web service or if we cannot configure the consumer centrally.


2.1 Prerequisites


  • ICF node- /sap/bc/webdynpro/sap/appl_soap_management to be active

  • Assign the administrative role SAP_BC_WEBSERVICE_CONFIGURATOR for the SOA Manager

  • Business functions activation for interfaces. Refer References


3.     Types of SOA Scenarios


  1. SOA Integration Scenario without WSDL

  2. SOA Integration Scenario with WSDL

3.1 SOA Integration Scenario without WSDL


  • Configuring the SOA Manager for Master Data Governance (MDG) in the MDG HUB and the MDG Client system.

  • To configure a scenario, both ABAP systems must use configuration profiles with the same names. If the connected system offers the services required, but they have been configured without a profile or using different profile names, the consumer proxies in the local system cannot automatically.



Execute a SOA Manager Transaction

Step 1: Create a profile for point-to-point communication

  • On the Technical Administrationtab, choose create Profile


  • Define the Profile name and description

  • Click on Next and choose the security settings


  • Click on Next and choose the Transport settings


  • Activate the profile



Step 2: Configure the client setting

  • On the Technical Administrationtab, choose SAP Client Settings, and open the Service Identifier


  • Note the Business Application ID (the field is automatically filled) which will be used at the time of Integration scenario setup



Step 3: Configure a provider system for the Business Scenario Configuration


  • On the Technical Administrationtab, choose Provider Systems, then choose Create. Enter the system ID of the client system as the name, select the profile name defined in step 1, and choose Next.




  • Enter the SLD identifier in the following form w.r.t MDG client: <Client>.SystemName.<ABC>.SystemNumber.<InstallationNumber>.SystemHome.<Host>

  • Enter the Access URL for WSILand Logon Information under WSIL Servicesr.t MDG client as: https://<hostname>:<port>/sap/bc/srt/wsil?sap-client=<client>;

  • Verify that the Use WSIL Usercheckbox is selected.

  • Make a note that the user credentials used for BASIC Authentication must be setup is both MDG HUB and MDG Client systems.





  • Retrieve the Business Applications ID from the right corner option


NOTE: To retrieve the own Business System ID, run transaction SLDCHECK and check the section Calling function LCR_GET_OWN_BUSINESS_SYSTEM. As a prerequisite, SLD needs to be connected to your system as described in Prerequisites section above.




  • Check the connection test



Step 4: Configure a Logon Data Management


  • On the Service Administrationtab, choose Logon Data Management.



  • On the maintenance tab, choose Create, enter your logon data name with description



  • Select an Authentication Method as User/Passwordor 509



  • Enter the username that got created earlier in the backend system and choose Finish to activate the logon data.


Step 5: Create Integration Scenario for Point-To-Point Communication


  • On the Service Administrationtab, choose Local Integration Scenario Configuration.



  • Choose Create, provide a name and a description for the integration scenario, and choose Next.



  • Select service definitions and assign a profile created in STEP 1. Service definitions information will vary from the partners used (as Business, Finance, Master etc.)

  • Here, we’re giving an example of Finance partners.

  • Choose Add to search for the service definition

  • Search for all the required service definition for the given below list and choose OK.


Service Definition (Internal Name) Description
CHARTOFACCOUNTSREPLICATIONCONF Confirmation of Chart of Accounts Replication
FINANCIALREPORTINGSTRUCTUREREP Confirmation of Financial Reporting Structure Replication
GENERALLEDGERACCOUNTMASTERREPL Bulk Confirmation of General Ledger Account Master Replication
COMPANYREPLICATIONBULKCONFIRMA Bulk Confirmation for Company Replication
COSTCENTREREPLICATIONBULKCONFI Bulk Confirmation for Cost Center Replication
PROFITCENTREREPLICATIONBULKCON Bulk Confirmation for Profit Center Replication
COSTCENTREGROUPHIERARCHYREPLIC Confirmation for Cost Center Group Hierarchy Replication
PROFITCENTREGROUPHIERARCHYREPL Confirmation for Profit Center Group Hierarchy Replication
COSTELEMENTREPLICATIONBULKCONF Bulk confirmation for cost element replication
COSTELEMENTGROUPHIERARCHYREPL1 Confirmation for cost element group hierarchy replication
INTERNALORDERBULKREPLICATECONF Bulk confirmation for internal order replication



  • Service definitions for replication to a SEM-BCS system:


Service Definition (Internal Name) Description
CHARTOFACCOUNTSREPLICATIONCONF Confirmation of Chart of Accounts Replication
FINANCIALREPORTINGSTRUCTUREREP Confirmation of Financial Reporting Structure Replication
FINANCIALCONSOLIDATIONELEMENTR Bulk confirmation for replication of Financial Consolidation Element
FINANCIALCONSOLIDATIONSTRUCTUR Confirmation for replication of Financial Consolidation Structure




  • Select all the service definitions from the list, assign profiles and select NEXT.

  • Select all the service groups for the relevant service definitions and assign the provider IBC reference


Service Group (Internal Name) Description
USMD_CHARTOFACCRPLCTNRQ_V1 Chart of Account Replication for Version 1
USMD_FINREPSTRUCTRPLCTNRQ Service Group for Outbound FinancialReportingStructureReplicationRequest
USMD_GENLEDACCMRPLCTNRQ Service Group for Outbound GeneralLedgerAccountMasterReplicationBulkRequest
USMD_COMPANYRPLCTNBRQ Service Group for Outbound CompanyReplicationBulkRequest
USMD_COSTCTRRPLCTNBRQ Service Group for Outbound CostCentreReplicationBulkRequest
USMD_PROFITCTRRPLCTNBRQ Service Group for Outbound ProfitCentreReplicationBulkRequest
USMD_COSTCTRGRPHIRPLCTNRQ Service Group for Outbound CostCentreGroupHierarchyReplicationRequest
USMD_PRFTCTRGRPHIRPLCTNRQ Service Group for Outbound ProfitCentreGroupHierarchyReplicationRequest
USMD_COSTELMTRPLCTNBRQ Service Group for Outbound CostElementReplicationBulkRequest
USMD_COSTELMNTGRPHIRPLCTNRQ Service Group for CostElementGroupHierarchyReplicationRequest
FI_CO_INTERNALORDER_SGRP Service Group for InternalOrderBulkReplicateRequest_Out


  • Service groups for replication to an SEM-BCS system:


Service Group (Internal Name) Description
USMD_CHARTOFACCRPLCTNRQ_V1 Chart of Account Replication for Version 1
USMD_FINREPSTRUCTRPLCTNRQ Service Group for Outbound FinancialReportingStructureReplicationRequest
USMD_FINCNSELMNTRPLCTNBRQ Service Group for Outbound FinancialConsolidationElementReplicationBulkReq
USMD_FINCNSSTRUCTRPLCTNRQ Service Group for Outbound FinancialConsolidationStructureReplicationReq


  • Select all services groups from the list and assign them to the provider IBC reference by choosing Assign IBC Reference and choose finish.






NOTE: Step 1 to Step 5 needs to be performed in both Hub and client environment and then it’s recommended to activate the business scenario.


  • While following up these steps in client environment, step 4 and step 5 will differ, we can follow the SRT_MIF_REL_INTERFACES report to generate specific service definitions and service groups for the given consumer proxy.




3.2 SOA Integration Scenario with WSDL


  • Replicating master data from S/4 to C4C (Cloud for Customer) using DRFOUT approach based on integration scenarios for service groups.


  • The following steps needs to be performed in SOAMANAGER


  1. Prepare and Upload WSDL

  2. Publish WSDL

  3. Verify Published Service Definitions

  4. Create a Profile

  5. Create a Provider System

  6. Create Logon Data

  7. Create Local Integration Scenario

  8. Create Configuration Objects



Step 1: Prepare and Upload WSDL



  • Download the WSDL via SE80 for the customer service and adapt the WSDL by adding Binding and Service elements.





  • In SOAMANAGER, upload the consumer proxies following Tools -> WSDL Upload



  • Click on Create and upload the WSDL files from your local machine





Step 2: Publish WSDL


  • Publish the uploaded WSDL to Service Registry. Navigate to Service Registry à Publication of External WSDL

  • Import the WSDL file in the WSDL wizard


  • Under Service Details tab, provide an internal name


Note: The Port type name and namespace in the external WSDL should match the corresponding names defined n SE80


  • Select the service state as configured


  • In the Bindings tab, click Next


  • Create new Physical system, with system type as Third party making sure the RM protocol is set to SAP RM when the logical ports are created later as asynchronous reliable messaging. This is mandatory to send messages via SAP CPI (Cloud Platform Integration).


  • Perform all the above steps for the other consumer proxies in the service group except for the Physical system. Select the existing system that was already created.


  • Review the service details and click on finish to publish the WSDL to local service registry.



Step 2: Verify Published Service Definitions


  • Verify the published service definitions using the navigation path: Service Registry -> Published Service Definitions


Step 3: Create a profile


  • Navigate: Technical Administration à Profiles


Step 4: Create a provider system


  • Navigate: Technical Administration à Provider Systems


NOTE: The provider system name will be used as business system name in DRFIMG. For C4C, it’s recommended to use the C4C short tenant ID as the provider system.



  • Under the service registry, select local service registry (SR_LOCAL) and then select the Third-Party system created earlier as the SLD Identifier.


  • Maintain the user credentials to access WSDL from service registry and check the Tolerant Search


  • User applications, assign the business application (IBC) created earlier


  • Activate the provider system


Step 5: Create Logon Data


  • Navigate: Service Administration à Logon Data Management. Create Log on Data and activate it.


NOTE: This will be used to log on to the provider system



Step 5: Create a Local Integration Scenario


  • Navigate to Service Administration -> Local Integration Scenario Configuration


  • Service Group entry should suffice, therefore we can skip the service definitions tab



  • In the service group tab, add the Service Group Object


  • Assign the IBC reference created earlier



  • Assign the logon data created previously


  • Finish and activate the Integration Scenario


Step 6: Create Configuration Objects


  • Once the Integration Scenario is activated the system will display a link to configure and activate the consumer proxies using Pending tasks.

  • Navigate to Service Administration -> Pending Tasks -> Process List



  • Rebuild and process the list of Pending tasks:


  • Ensure the task list is executed successfully and as a result logical ports will be created using the service registry



4.     Validation and Post Configuration in IMG


4.1 Validate the Configuration


  • Execute a transaction SOAMANAGER. Navigate to Service Administration -> Web service Configuration



  • In the configuration tab for the service group, verify the logical ports are created



  • Verify the messaging tab, the RM protocol should be set to SAP RM which is required for CPI based connection


4.2 Configuration in IMG


  • On S/4HANA On-Premises system, transaction code DRFOUT is used to replicate the interfaces messages to external systems.

  • DRFOUT uses DRFIMG configuration. To send data to the provider systems, using logical ports created in SOAMANAGER, the following two points must be adapted in the DRFIMG configuration.


  • In DRFIMG, create a business system with the same name as defined in the provider system in SOAMANAGER (For replicating data to C4C, it should use C4C short tenant ID as the business system name)


  • Assign the business system to the replication model


4.3 Test the configuration


  • Trigger a business partner message using DRFOUT and check SRT_UTIL/SRT_MONI message monitor using forward navigation from DRFOUT logs.

  • In the payload the RecipientBusinessSystemID in MessageHeader is populated from the Business system name defined in DRFIMG, which is same as the provider system in SOAMANAGER.

  • For demo purpose, the message was made to fail intentionally, so that we can verify the logical port used by DRFOUT, in Web Service utilities -> Error Log

  • Above the logical port being used, which is same as created in SOAMANAGER for the service group


5.     Appendix


5.1 SAP Component


Component Description
  BC-ESI-WS-ABA-CFG Web Services ABAP Configuration
  CA-MDG-APP-FIN MDG Financials



6.     References

Labels in this area