This document explains us about how to create skyvva asynchronous outbound interface to send base 64 string file from Skyvva to SAP PO using SFDC2SAPPI Adapter
Steps needs to be done in Skyvva
Create Asynchronous Outbound Interface
Outbound skyvva Interface –
In this example we are creating the interfaces under “Attachment_Test” Integration. Provide the Interface name, Description, Source name, Status, Direction, Interface type, Processing mode, outbound adapter and the SQL statement to query the data.
Provide all the required details and save the interface. After that click on “Open Mapping” to do the mapping.
Do the mapping as shown below
Save the mapping.
Download the outbound interface XSD to import to SAP PO for mapping.
In SAP PI/PO we need to create Asynchronous interface
With respect to SAP its an inbound Interface(Skyvva to SAP)
Import XSD into ESR
First, we have to create a namespace in ESR like “urn:SF2SAP:attachment”.
Now create an external definition under the namespace like below. we can give the name as ED_ContentVersion
Import the XSD and Save and activate it.
We need to create Datatype, Messagetype and Service Interface for target file system
Target Data type
Here we are selecting the base64Binary for the field versionData as shown below. In this field we are going to send file attachment from Skyvva.
Target Message type
Outbound Service Interface
Select the Source message type and save and activate the service interface.
Inbound Service Interface
Create service interface
Select the target message type and save and activate the service interface.
Do the respective mapping and save and activate it.
Operation Mapping for asynchronous inbound interface
Select the outbound and inbound service interface and the message mapping to create operation mapping
Then save and activate it.
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 component e.g. for the file system “BC_File“. For Salesforce you can use our proposal “Salesforce” as the business system. We have to import these business systems from SLD.
Configuring the Sender SOAP communication channel
Create sender communication channel as shown below.
Since we are sending file from Skyvva. So, here we are using SOAP adapter in the sender channel.
Provide the necessary details. After that save and activate the channel.
Configuring the File receiver channel
Configurations for Target tab
Configurations for Processing tab
Configurations for Advanced Tab
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.
In the “outbound processing” tab, we have to specify the receiver channel.
Testing the interface –
Triggering the data from SOAPUI
Message is delivered from SAP PO
Check the message in Skyvva message monitoring.
Click on “related to” to check the transferred data in Skyvva
We are sending the base 64 string from SAP PO to Skyvva as we can see the transferred data below