EDI Integration using SAP Net Weaver Process Integration

Contents 1. 1.1. 1.1.1. 1.1.2. 1.1.3. 1.2. 1.3. 1.4. Introduction 3 Seeburger EDI Adapter Overview: 3 Classifier Module: 3 BIC Adapter Module: 3 Splitter Module: 3 Interface Flow in PI 4 Integration Scenario in PI 5 Configuration 6

1.

Introduction

This document describes steps involved in integrating Electronic Data Interchange (EDI) messages with SAP ECC system using Process integration (

PI). This document mainly talks about how to configure the Sender and receiver c hannel in SAP PI for EDI message transformation. For testing purpose consider a scenario Sales Order creation. Sa les orders from different customers are received by PI in the form of EDI messag e format. SAP PI processes these files and for each input file an Idoc is trigger ed to SAP ECC system. 1.1. Seeburger EDI Adapter Overview: Seeburger EDI Adapter leverages SAP Process Integrations (PI) Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also p rovides some built-in EDI layouts and the ability to build your own. Seeburger E DI Adapter is used to transfer the EDI message via HTTP or AS2 protocols 1.1.1. Classifier Module: . See Classifier analyses and classifies the content of a message and adds this information as an XML attachment to the XI message. It is then passed on to the next module in the module chain. This information can be read, e. g. by the SEEB URGER Converter module 1.1.2. BIC Adapter Module: BIC can convert XML format (used in SAP NW PI) to an EDI format (For Example it converts EDI xml invoices to EDI message). The conversion can be executed before the message is transmitted to the business partner. The other way around, once an EDIFACT message has been received from the business partner, it must first be converted to XML format, i.e. the format supported by SAP NetWeaver PI. 1.1.3. Splitter Module: The SEEBURGER message splitter module initiates new XI messages as children of a main (or parent) XI Message. A new child (or split) message will be created for each main messages attachment in the split list. The split list can be provided in 2 ways: The split list can be defined manually as a module parameter. In this case the m essage splitter is running as a standalone module. The split list can be provided by a previous BIC conversion. In this case the me ssage splitter is running integrated with the BIC Module. This option is not cov ered in this guide; please refer to the SEEBURGER Functional Acknowledgement Solu tion for SAP NW Process Integration for a complete description of the approach. The following diagram shows the operation mode of the splitter in 4 steps:

1. An XI Message has been initiated by an adapter (e.g. OFTP, mail ) 2. The Splitter message will be executed as part of the module sequence processi ng of the sender channel. 3. The splitter reads the splitter partner data to known which sender channel sh ould be used for initiating the child messages. 4. Child messages will be initiated. Note the sender channel used to initiate ch ild messages uses a special adapter called Split997 The module in the processing sequence (module sequence) must be entered in the c onfiguration table to configure the Message Splitter. It is located on the modul e tab page of the communication channel. As a perquisite the mapping that is intended for use must already be deployed us

ing the JSPM (Java Support Package Manager). 1.2. Interface Flow in PI

Input message formats used by Customers for sending the order data: 1. EDI X12 (Partner A) 2. EDI EDIFACT (Partner B) EDI Message flow in PI: PI adapter picks the EDI file message; EDI file will have multiple order details which also have multiple segments. See burgers splitter adapter module is used in sender adapter to split the single EDI message into multiple EDI messages; after splitting each EDI message have o ne order detail. Followed by that a seeburger mapping program which converts these EDI messages t o EDI xml messages is called. PI maps these EDI xml file to ORDERS05 IDOC xml message structure. SAP PI sends the EDI Functional Acknowledgement 997 back to Partners, upon accep tance of EDI message format. In receiver file adapter See burger mapping program is called to convert the EDI xml structure to EDI message format. Output essage 1.3. 1.4. messages for the above cases: IDOC Type ORDERS05 Functional Acknowledgement 997 Message stating the acceptance/rejection of the M format. Integration Scenario in PI Configuration

The Message Splitter module must be configured in the SAP NW PI Integration Dire ctory Sender File Adapter Configuration The Message Splitter must be executed in the module sequence of the communicatio n channel, as shown in the screenshot:

The above configuration of a communication channel, which first classifies the c ontent of an XI message, converts it into EDI xml structure and writes it to the file system with the File Adapter. As shown above, there are 3 steps in the module sequence: 1. Execute SeeClassifier by calling the module localejbs/SeeClassifier. 2. Execute the Converter by calling the module localejbs/CallBicXIRaBean. 3. Execute the FileAdapter. The Module Configuration table contains the parameters for the SeeClassifier and the SEEBURGER Converter modules. See Classifier Module: Parameter Entry

destSourceMsg This parameter is used to specify an attachment including the da ta that has to be classified. attID This parameter is used to specify an attachment, in which the informatio n about the classification is attached to the XIMessage.If no attID is set, the default name MessageTypeReport will be used. classifierMappingID An ID can be assigned to each module sequence. This ID i s used to generate the name of the mapping. If this parameter is not set, the ge nerated name of the mapping will start with See_. showInAuditLog If this parameter is set to "true", the information on the class ification is shown in the audit log. Convertor Module: Parameter Entry classifierAttID If the Classifier fy the ID of the attachment where If no attachment name is set, the destTargetMsg This parameter is hould be placed after conversion. module is running before the BIC Module, speci the outputs of the Classifier were stored. default name MessageTypeReport will be used. used to specify where the resulting document s Possible values are:

MainDocument: Main payload of the SAP XI Message (default value if the mapping c onverts to XML value). SeeburgerMain: Attachment with name SeeburgerMain(default value unless the mapping converts to XML format). <attachmentId>: Other attachment with the given ID mappingName Specifies the mapping to be executed. If the name is set to AUTO, it will be automatically generated with help from the Classifier module. For mor e information also see the Classifier documentation. This "AUTO" setting require s explicitly configured execution of the classifier module! split Set this parameter to true, if you want to use the Split option. Split Channel Configuration As already mentioned, child messages are initiated using a split channel. This i s a sender channel which uses the Split997 adapter as in the following screensho t. Note that before to split messages you must: Create a split sender channel Create a sender agreement for the split sender channel Create a splitter partner data entry which selects the correct sender channel

Receiver File Adapter Configuration: SAP PI sends the EDI Functional Acknowledgement 997 back to the Partners, upon a cceptance of EDI message format. The converter is configured on the Module tab p age in the Module Processor of the communication channel. To configure the converter, the module must be entered in the processing sequenc e (module sequence) and the parameters of the module must be entered in the conf iguration table. Both are located on the module tab page of the communication ch annel. In order to run a BIC mapping, the converter must be executed in the module sequ

ence of the communication channel and the mapping that is to be executed is sele cted in the Module Configuration table, by means of the module configuration par ameters: Module Name: localejbs/CallBicXIRaBean. Parameter Meaning mappingName Specifies the mapping to be executed. If the name is set to AUTO, it will be automatically generated with help from the Classifier module. For mor e information also see the Classifier documentation. This "AUTO" setting require s explitly configured execution of the classifier module! destSourceMsg This parameter is used to specify which data has to be converted . Possible values are: MainDocument: Main payload of the SAP XI Message. SeeburgerMain: Attachment with name SeeburgerMain. This is the default value, if t he attachment does not exist, the main document will be used. <attachment Id>: Other attachment with the given ID. destTargetMsg This parameter is used to specify where the resulting document s hould be placed after conversion. Possible values are: MainDocument: Main payload of the SAP XI Message (default value if the mapping c onverts to XML value). SeeburgerMain: Attachment with name SeeburgerMain(default value unless the mapping converts to XML format). <attachmentId>: Other attachment with the given ID newLine True, if the mapping should add a CRLF at the end of each segment/record . After Orders EDI message conversion and splitting the orders message enters into PI Integration engine. PI maps the orders EDI xml structure to ORDERS Idoc xml structure. Finally ORDERS Idoc is successfully posted in SAP ECC system and Para llelly SAP PI sends the EDI Functional Acknowledgement 997 back to the Partners, upon acceptance of EDI message format. References: Seeburger Adapter Installation documents provided by Seeburger