Skip to Content

SAP PI/XI : Content Conversion using Generator mapping functionality of SeeBurger : Part 2.

In Part 1 ( SAP PI/XI : Content conversion using Generator mapping functionality of SeeBurger : Part 1. ), we seen how to use SeeBurger for defining the content conversion for deep XML structure. 

In this blog we will see, step by step procedure for deploying SeeBurger map and calling that maps from SAP PI adapter.

Once mapping have been created in BIC mapping designer, we need to deploy the map on SAP PI.

Step 1: Create   XSD file.

Export XML message as XSD file. This is the xsd file, which we will be importing in PI Repository as External definition and will be used in the message mapping.


Step 2 : Create .sda file using BIC mapping designer.


 Select Generate SDA file option.



SeeBurger creates the .SDA file in specified folder. The name of the file will be Mapping_User.sda.


Do not change the file name. As SeeBurger Runtime engine uses this sda file to find out all the custom maps created.

All the standard EDI maps delivered by SeeBurger will be stored in Mapping_Sys.sda file. 

In future if you want to deploy any new map, that should also be deploy using the same .sda file.


Step 3: Deploy Mapping_User.sda file on your SAP PI server using SDM.


Step 4: Configure SAP PI receiver file adapter for calling the SeeBurger map.

From PI, We will call the module localejbs/CallBicXIRaBean and will pass the mappingName as parameter in module configuration.

Default module CallSapAdapter must be called after the SeeBurger module to pass the control back to the Adapter Engine.



 Step 5: Test the scenario.

Communication channel monitor will log the errors in case of any. SeeBurger trace can also be very useful for further tracing. 

Be the first to leave a comment
You must be Logged on to comment or reply to a post.