As a prerequisite, it is easier if you have an idea on the Seeburger BIC mapper and also about the various EDI structures formats like ANSI X12, EDIFACT etc. In this Seeburger BIC mapper we have the standard mapping which can convert the EDI to XML format and Viceversa. So as per the needs we need to select the different EDI structure which has to be converted from EDI to XML or XML to EDI and move it to the active mappings directory of the BIC mapper. Then we need to generate an .sda file which has the group of all standard mappings that are used for the conversion of the EDI formats and deploy that .sda file in XI server.
Once you have the standard Seeburger BIC mapper or the Seeburger adapter installed in SAP XI, use can import those standard EDI structure to our namespace as an external definition and proceed as we general do for any scenario.
Seeburger BIC mapping tool:
Now that we have the standard EDI ANSI X12 structure(I had considered 850) as a source, we need to create the file format for the receiving end. I had created an xml structure as the target structure as per the needs.
Now we need to proceed with the creating the message interface(for source and target), mapping of the source and the target structures and create the interface mapping.
Create the sender and receiver business service along with the communication channel. I had created the sender and the receiver communication channel using the file adapter with FTP protocol.
Here, the most important point to note is that when creating the sender communication channel we need to call the BIC mapping module which is deployed in the XI server. So we need to configure the module parameters in the communication channel based upon the ANSI X12 message that is used for conversion.
In our scenario, we are using an 850 structure where the EDI message coming in has to be first converted to xml and then passed to XI for further processing. To do this we need to specify the following module parameters for conversion of EDI to XML
Sender Communication Channel with module parameters:
Sender CC with Module parameters
Module Name Module type Module Key
localejbs/CallBicXIRaBean Local Enterprise Bean bic
CallSapAdapter Local Enterprise Bean 0
Module Key Parameter Name Parameter Value
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic mappingName See_E2X_ANSIX12_850_V4010
Once you specify these module parameters in the module tab it will automatically call the BIC mapping program with name See_E2X_ANSIX12_850_V4010 which is already deployed in the XI server.
After the conversion then the normal procedure for creating the interface determination, receiver determination, receiver agreement and the sender agreement follows.
Now lets look into the source and target structure of the files that are used in this scenario.
So I hope now it would be easier to work with the EDI interfaces as well.