Getting Gett ing Start Started ed Newslet Newsletters ters Stor Store e
Hi, Guest
Log On
Join Joi n Us
Search the Community
Products
Services & Support
About SCN
Downloads
Industries
Traini ng & Education
Partnership
Developer Center
Lines of Busi ness
University All iances
Events & Webinars
Innovation
Process Integration (PI) & SOA Middleware
Quick Overview - B2B Scenario (End2End) with Seeburger EDI-Adapter Posted by Stefan Hilpp in Hilpp in Process Integration (PI) & SOA Middleware Middleware on 13-Jan-2013 23:59:29 Share
0
Tweet
0
In my blog about the Seeburger EDI-Adapters for SAP PI I (
Like
3
http://scn.sap.com/blogs/seeburger_edi ) , I have been
asked for some tutorial to configure a simple end to end B2B Scenario with Seeburger and SAP PI. Although this is not a new topic, I decided to setup a scenario on a 7.3.1 environment with Dual Stack (using the Standard Configuration) since there might still be some consultants that are relatively new to the topic. I have tried not just to provide here a lot of screenshots without any explanation, but also to explain the basic concept behind the scenario and the handling of EDI-files. This makes this post very long, but I hope it helps to get a good understanding. The "Repository settings" can be found at the end of the blog" but it is recommended to setup these objects first as they will be needed to do the Directory-Co Directory-Configuration. nfiguration.
Scenar io-Description: io-Description: In this this sce scenario, there are 4 Parties/Entities involved 2 Customers Customers that send edi-orders edi-orde rs in the format ANSIX12_850_V401 ANSIX12_850_V4 010, 0, called "ElectronicWorld" and "GlobalElectronics" 1 ServiceProvider called "RetailHub" which sends data for both customers throu gh one on e AS2-Connection 1 Supplier, called "Seeburger" that receives the orders from b oth partners and processe rocesses s these or ders ders in the SAP Backend. Ba ckend.
In addition, I have setup a FilePort, using the same parameters in the ModuleChain like the AS2-Channel, which allows for a manual reprocessing of any received file. Therefor the ModuleChain also includes a parameter to save the OriginalEDI-File. In general all receiving scenarios follow a 2 Step approach Step 1: Technical Setup to receive file - Receivi ng the files via AS2 or FilePort - Analyzing the files (Classifier, BIC, Splitter) and forwarding each single message to the correspondin g business partner (according to the SenderID in the ISA-Segment) Step 2: Processing the data according to partner/ messagetype - information - for each businesspa rtner, an own party is existing with a Split-Chann el for each messagetype.
Activity Browse
Commun Com munications ications
Actions
Directory Setup: For Step 1 (receiving the data) , the following objects are used:
The object EDI_SP_Seeburger is only used as "Receiver Party" in the AS2-Sender Agreement and contains the own AS2-ID
(the object EDI_SP_RetailHub has included its AS2-ID in the same area) EDI_SP_RetailHub and EDI_SP_ManualRestart both include a SenderCommunicationChannel with all steps needed for the analyzing and splitting of the received data.
=> This setup will classify the incoming data (to see if it is EDIFACT, ANSIX12, TRADACOM, XML, FLATFILE...) and afterwards dynamically detect which Conversion-Rule (e.g. from ANSI X12 to the equivalent ANSI XML-structure) needs to be used. The Splitter will then create one single XML-File (MainDocument) for each message (in ANSI X2 for each ST-Loop...in EDIFACT for each UNH...)
partners/entities The SenderAgreements look like following:
(No signature/encryption is used in this example, as the focus is lying on the EDI-handling and not on this specific AS2-feature...but if requested, it can be a dded to this scenario easily) For Step 2 (assigning each partner/messagetype to the corresponding business party) the following 2 Parties (Customers) have been setup in Integration Directory: The following convention has been used in this scenario Party:
real name of the customer (with Prefix EDI_BP...)
Component: SenderID of ISA-Segment In the screenshot, the 2 business partners/customers can be seen and an inbound-channel has been created (using the Split-997-Adapter). These Split Channels always process the "splitted" messages from the previous step.
In the following Screenshots, the next steps for processing these file can be seen
Connection between Step 1 and Step 2. To connect the output of the MessageSplitter with the correct Inbound Channels "from Split", an entry needs to be existing in the SeeburgerWorkbench for this partner/message combination:
Keys are : Sender => MappingN ame =>
ISA-Sender ID detected messagetype and version
SInce the Sender Agreement for the 2 BusinessPartners have been created in previous step, they can just be selected in this area by first selecting the "Sender-Party", then click on "Search Services" to get a list of all services for this Party...and then select the proper Channel "fromSplit_850_V4010". After setting up both p artners, the Messag eSplitter a rea in the Workbench include s the followin g 2 lines
Important Feature:
By using the "State" field (accepted or partly accepted) it can be decided how to handle large files with multiple messages (ST / UNH segments), if some of these messages are not correct => either the complete file can be stopped, or the correct mesages are processed anyway and the partner is informed via 997 which of the messages need to be corrected and transmitted again. To setup the complete End2End-Scenario there are also some objects needed in the Repository which are mentioned in the following section.
Repository Setup The following objects are needed in the Repository - Interface / External Definition for the ANSIX12 850 processing - Interface / External Definition for the FunctionalAcknowledgement (used to create 997 messages in additional steps) - Imported IDoc - Message Mapping and OperationsMapping
These objects are available as templates with most of the Industry-Packages.
Runtime: In this section, I will soon provide additional screenshot from the process flow and the monitoring of this scenario. Additional ly some screenshots reg arding the 997 handli ng w ill be p rovided, Testdata: Here I will also provide some 850-Testdata that can be used to setup/test this scenario Feedback: Any feedb ack is appreciated to enh ance thi s post in future and add additiona l d escriptions/features.
3244 Views
Topics: process_integration, b2b_integration Tags: adapter , b2b, seeburger , edi, sap_netweaver_pi
Average User Rating (5 ratings)
Share
0
Tweet
0
Like
3
6 Comments Christoph Gerber 15-Jan-2013 12:50
Very detailed and interesting. Shows how flexible the Seeburger SAP PI adapters can be used for any kind of EDI / B2B interface. Like (1)
Stefan Hilpp 16-Jan-2013 23:32 (in response to Christoph Gerber)
Thank you, let me know if there is anything you are missing or would like to have additional information Stefan Like (0)
Carlos Ocampos 06-Feb-2013 15:20
Very good Job Stefan! Step by step, good explanations, screenshots to understand and very easy to follow. Congratulation for this blog!! Like (1)
Stefan Hilpp 06-Feb-2013 19:05 (in response to Carlos Ocampos)
Thank you Carlos, I am glad you like it. Stefan Like (0)
Kancham Sreenivasulu 18-Feb-2013 07:16
Hi Stefan, Looks good but looking forward for more screens with Pi 7.31 version Bolog. Regards, Sreeni. Like (1)
Stefan Hilpp 25-Jul-2013 10:24 (in response to Kancham Sreenivasulu)
Hi Sreeni, it took a while but finally I found some time to create a 7.31 version of this blog. (mainly focusing on the Integrated Configuration Steps) Check it out and let me know if this it what you had in mind: http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/07/24/quick-overview-b2b-scenario-with-seeburger-edi-adapter-using-integrated-configuration Regards Stefan Like (0)
Site Index Privacy
Contact Us T erms of Use
SAP Help Portal Legal Disclosur e
Copyr ight
Follow SCN
