This document explains us about how to create skyvva asynchronous inbound interface in SAP PI/PO with new V3 adapter module
Steps needs to be done in Skyvva
Create Asynchronous Inbound Interface
New V3 works only with Skyvva message type.
Create Metadata Provider:
Create Istructure Repository:
Create Message type:
For Inbound we can use normal message type as shown.
Inbound skyvva Interface –
In this example i am creating the interfaces under “Lalitha_Test_Integration“
Do the mapping as shown below
Download the inbound interface WSDL to import to SAP PO for mapping.
In SAP PI/PO we need to create Asynchronous interface
With respect to SAP its an outbound Interface(SAP to Salesforce)
Import WSDL into ESR
First, we have to create a namespace in ESR like “http://DEBMAS07_to_AccountUpdate”.
Now create an external definition under the namespace like below. Here the WSDL is for Account. So, we can give the name as ED_Ack_IN
Now import the WSDL and Save and activate it.
No need to create Datatype, Messagetype and Service Interface for Sender system SAP as we are using IDOC as a source.
Create service interface
Now click on Save and activate it.
Do the respective mapping and save and activate it.
Operation Mapping for asynchronous inbound interface
Create Operation mapping.
Then save and activate the operation mapping.
Creation of Integrated Configuration Objects
After creating the objects in ESR. We have to configure these objects in the integration directory.
First, we have to create Configuration Scenario.Now enter the name of the scenario, description and choose a folder if you have created then press on create button.
An Integration scenario has the following objects.
- Business System for Sender and Receiver
- Sender and Receiver Communication channel
- Integrated Configuration
These are the objects we should create.
We have to define our business system e.g. for the SAP-Backend. For Salesforce you can use our proposal “Salesforce” as the business system. We have to import these business systems from SLD.
Configuring the Sender Idoc communication channel
Create sender communication channel as shown below.
Since we are using an IDOC as a source. So, here we are using IDoc adapter in the sender channel.
Provide the necessary details. After that save and activate the channel.
10. Configuring the SOAP receiver channel
Configuration for Tab “General”
Specify the parameters as shown in the above screenshot.
Below is the configuration for the “Advanced” Tab.
The value “TserverLocation” has to be entered for the parameter Variable Header (XHeaderName1).
Below are the settings for Tab “Module”. Here, the SKYVVA module containing the logic for session handling and transformation logic must be specified.
Configuration of module parameters are described in detail below
Skyvva Module Parameters
“Skyvva/V3/Integration” to be used with SOAP receiver channels. Module parameters are outlined below
Create integrated configuration objects as shown below.
Enter the required data e.g. the Communication Component, Interface and Namespace and then click on create button to create an ICO.
Now go through the tabs from left to right to configure the relevant objects. In this first tab “Inbound Processing” here we have to specify the sender communication channel.
Here in the “Receiver” tab, we have to specify the receiver business system.
In Receiver interfaces tab specify the operation mapping and also the values of the parameters.
The parameter Account_Update_In is the interface name (on Skyvva side) of the interface Account.
In the “outbound processing” tab, we have to specify the receiver channel.
Testing the interface –
Triggering the data from SAP
Account data transferred to Skyvva