This document explains us about how to create skyvva asynchronous inbound interface in SAP PI/PO with new V3 adapter module to generate the Skyvva External ID and Transaction ID?
We have to understand the 4 fields we have in the message monitoring e.g.
– Business External Id
– System External Id
– Transfer Id
– Transaction Id
System External Id – For every message we have the Id field as the Skyvva system external Id field.
Transfer Id – SAP PO filled automatically the transfer id with the SAP PO message id. It is taken care by SKYVVA java module which is deployed in SAP PO.
Transaction Id – It is generated by skyvva api internally if you don’t set the field for ‘Custom Transaction Id’. we set the path for this field to get the value from source. Such value we can see in the Transaction Id in the SKYVVA message monitor
Business External Id – is the external id which we check the flag in the mapping tool.
In this example System External Id is for example the IDOC Number.
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“
If we want to put the customer number into this field skyvvasolutions__SKYVVA_EXTERNAL_ID__c so that we can search in our monitor by the sap customer number for that we have to specify the path of system external Id and customer transaction Id. which comes from the IDOC source structure but here we have specify only the target skyvva sObject structure path.
If we don’t specify the Customer Transaction Id. Skyvva will generate the default transaction Id.
In this example we are not specifying the path of Custom Transaction Id
Do the mapping as shown below
Download the inbound interface XSD to import to SAP PO for mapping.
We have to create the SKYVVA__SystemExternalId field as Message type field entry from the Account message type related tab.
To create Message type field entry initially we have to create Istructure as shown below.
Click on “New Istructure” to create Istructure
Now specify the Name and Category of the Istructure and then save the Istructure field.
Create the message type field entry from the Account related tab. Click on “New” to create new field entry.
Give the Message type field entry name and Istructure name and then click on Save.
Now the field entry is created as shown below.
Once we create this field in message type field entry. Now we can see this field in the Downloaded XSD.
To download the XSD.
Go to Integration details tab and then click on “Generate Metadata”
Now select the Interface name and choose file format and then click on export to generate the XSD.
Scroll down to see the generated XSD and click on View to download the XSD file.
Import this downloaded XSD to SAP PO for further mapping steps.
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 is the XSD for Account. So, we can give the name as ED_32Demo_new
Now import the XSD and Save and activate it.
No need to create Datatype, Message type and Service Interface for Sender system SAP as we are using IDOC as a source.
Service Interface
Create service interface
Now click on Save and activate it.
Message mapping
Map the DOCNUM with SKYVVA__SystemExternalId to send the IDOC number System external Id to show in SKYVVA monitor.
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
Integrated Configuration
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
We can see the Business External Id as we define the mapping tool, System external Id as IDOC Numberand Transaction Id as a auto generated value from SKYVVA and transfer Id as a SAP PO message Id in the SKYVVA message monitoring.
Account data transferred to Skyvva