B2b Edi Inbound 4f2c24

B2B- EDI Inbound -Step by Step Configuration Posted by Rahul Malani in B2B Integration with SAP Process Orchestration on Sep 27, 2012 1:36:14 PM inShare1

I believe readers of this blog aware of new B2B Add-on for SAP PI through available content on B2B integration space. Those who are not aware, it's new offering by SAP for B2B integration in SAP PI space. In this blog I’ll discuss step by step configuration in inbound EDI (EDI from Partner) scenario.

Scenario: Inbound EDI (EDI from Partner)

In this example scenario I have configured file sender to pick EDI Message, instead of AS2 Sender or some other technical adapter. Receiver side, instead of IDoc receiver I am storing IDoc in XML format in file system. Incoming EDI message comprises of following EDI message of ANSI X12 Message format. 810: Invoice Message format: ANSI X12 Version: 4010

850: Orders Message format: ANSI X12 Version: 4010

ESR Objects: To maintain the focus on Configuration using new B2B adapters, I am not going into details of ESR objects here.

Integration Directory: Message Flow: Step 1. EDI message comprising multiple business transactions received in SAP PI by available technical adapters. Step 2. Receiver EDI Separator Adapter split received message into individual business transaction message. Step 3. Individual messages then mapped to target messages in SAP PI.

Step 4. Acknowledgement generated and sent back to sender of EDI message [Only available in case of ANSI X12 messages now]. Step 5. Transformed message then sent to receiver using available technical adapters. To configure this scenario we have to configure two types of Interfaces. Interface 1: From EDI Sender to EDI separator adapter [Step 1 and 2 above]     

Deliver the incoming EDI message [Comprises multiple business transaction] to EDI separator adapter. Split EDI message [Comprises multiple business transaction] into individual business transaction message. No need to create any service interface in ESR. Use dummy interface. No EDI to EDI XML conversion in this interface. No mapping. Interface 2: From EDI Receiver to backend system [Steps 3 and 5 above]

   

Process individual messages separated in interface 1. Interface needs to be configured for each individual message and for each pair of sender and receiver. EDI message converted in EDI XML format. EDI XML message transformed to target message. Interface 1 Configuration: Sender Agreement:

File Sender Communication Channel:

I’ll describe the reason to keep file name as ‘*ANSI*.*’ later in the blog. Receiver determination:

Interface determination: No mapping in this interface.

Receiver Agreement:

EDISeparator Receiver communication channel: Message Protocol is ANSI X12, since in example inbound EDI message contains ANSI X12 messages.

After processed through Separator interface EDI message split into individual EDI message. Here in our example incoming EDI message splitting into two messages - 810 and 850.

Once message separated, adapter start searching sender communication channel for the particular business transaction and partners. In our example it will search for following sender communication channels

 

Transaction 810, Version 4010, Sender ID 1111, Receiver Id 2222 Transaction 850, Version 4010, Sender ID 3333, Receiver Id 4444

It is required to configure two interfaces to process these messages.

Interface 2 Configuration: Here I have configured interface only for Transaction 810, Version 4010, Sender ID 1111, and Receiver Id 2222. Similarly it can be configured for other message. Sender Agreement: In ESR configure service interface using XSD of transaction 810 and Version 4010.

EDI Separator Sender Communication Channel: EDISeparator sender Communication channel configured for Transaction 810, Version 4010, Sender ID 1111, and Receiver Id 2222.

Module X12ConverterModule configured in Module parameter of communication channel to convert EDI into EDI XML.

Receiver determination:

Interface determination: In ESR mapping has to be developed to map EDI XML to Invoice IDoc.

Receiver Agreement:

I have not configured IDoc receiver channel, instead I am using file receiver channel to store invoice xml in file system.

In similar way interface can be configured for other separated message. Please find below the screenshot of the EDISeparator communication channel which I have configured in this scenario.

Execution:

You can see in the above screenshot, first message belong to the interface which split the messages and other two messages belongs to the 810 and 850 message processing. Scenario 2: In real-time scenarios it may possible that same EDI partner sends different formats of messages, say ANSI and EDIFACT. In that case we have to configure separate EDISeprator receiver communication channel in Interface 1 for EDIFACT message Foramt. Route the message based on content [message format] to the different receiver [EDIFACT or ANSI]. Since in interface1 EDI to EDI XML conversion not occurred, so inbound payload remains in raw EDI format [not in EDI XML], so it is not possible to add condition using XPATH in receiver determination. Possible solution from the discussion raised in SDN:

1) Use different communication channels on sender side. They may point to same input folder where you can provide different file names for EDIFACT and ANSI bulk messages respectively. I have opted this solution in this example for simplicity and to maintain focus on the main objective. 2) Wait for new package for B2B where SAP planning to provide this enhancement. I believe from the planned enhancement there will be no need to configure message format in EDISeparator receiver. 3) Workaround: a) Write a custom adapter module (to be used on sender side) which can read incoming message and create an XML message with root tag describing the message type (say EDIFACT or something) based on received bulk message. You need to add these XML tags after reading the headers of the incoming EDI messages. Add this custom module to your sender channel. b) Add two different receivers to the same scenario. And provide condition based on value of XMl Tags you have added during your module development. c) Now your message is routed in the right manner to the respective EDI Seperator receiver channel. Write another module (or enhance the same adapter module) which can remove these XML tags and convert the payload back to plain EDI bulk message (which you received initially) and use this module in EDI Separator receiver channels. Thanks for reading !! 20537 Views Products: sap_netweaver_process_orchestration, sap_netweaver_process_integration Tags: edi, b2b_ad d-on

Average Rating (5 ratings) inShare1

34 Comments

 

Ashish Sharma Oct 3, 2012 7:21 AM

Great work Rahul ! Very insightful blog. Like (1)

o Rahul Malani Oct 3, 2012 8:34 AM (in response to Ashish Sharma)

Thanks Ashish !! Like (0)

o Venkata Nageswara Rao Bandaru Dec 24, 2014 1:57 PM (in response to Ashish Sharma)

Hi Rahul,

Would request you to send ESR and ID part step by step please send us step by step documents edi to idoc/ifle. Thanks, Venkat. Like (0)

 Sreenivasulu Somavarapu Oct 10, 2012 10:00 AM

Good work Rahul. Do we have separate converter modules for each stream like EDIFACT..etc as like as X12? Like (0)

o Ivan Kosenko Nov 16, 2012 11:57 AM (in response to Sreenivasulu Somavarapu)

Hi, yes for EDIFACT exists the same localejbs/EDIFACTConverterModule - but i have an error when try to implement the same scenario: Error during processing local bean: localejbs/EDIFACTConverterModule while trying to invoke the method java.lang.String.equalsIgnoreCase(java.lang.String) of an object loaded from local variable 'status Like (0)

 Piyush Gakhar Nov 19, 2012 11:01 AM (in response to Ivan Kosenko)

Hi Ivan, Yes. It is known issue for wrt documentation and is already fixed. EDIFACT is not in caps letter. You have to use "localejbs/EdifactConverterModule" Regards, Piyush Like (0)

 Ivan Kosenko Nov 19, 2012 11:37 AM (in response to Piyush Gakhar)

Hi Piyush, thank you - it's works now ! Regards, Ivan. Like (0)

 Gaurav Nautiyal Dec 28, 2012 5:42 PM

Hi Rahul,

Just a quick question will it work the same way if file contains two 850 (Inbound purchase orders) for either same or diffrent partner . Thanks, Gaurav Like (0)

o Rahul Malani Dec 29, 2012 5:00 AM (in response to Gaurav Nautiyal)

Hi Gaurav, Yes scenario will work in same way. Regards Rahul Like (0)

 Gaurav Nautiyal Jan 9, 2013 6:44 PM (in response to Rahul Malani)

Hi Rahul, I tried to implement the same way for EDIFACT messages but my Sender EDI separator channel is failing with reason no Message type found or couldnot find messaeg type. Any idea or example for EDIFACT inbound processing or what values i need to fill under Filter or Sender Communication channel for EDI separator. Also any idea how to setup outbound messages from SAP to PI to point to two diffrent interfaces setup for 2 diffrent partners. Thansk, Gaurav Like (0)

 Gaurav Nautiyal Jan 10, 2013 4:08 AM (in response to Rahul Malani)

I did something and now able to see some progress in RWB , but now I am getting error "Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: No senderchannel matches the Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification 1234, Interchange sender identification code qualifier , Interchange recipient identification 4321, Interchange recipient identification code qualifier" I am usinng below EDI header UNB+UNOA:2+1234+4321+100302:0402+1342++++1+EANCOM' UNH+1+ORDERS:D:96A:UN' BGM+220+P8218007+9' DTM+137:20100802:102' And have setup this in Sender EDI separator channel . Any idea , Please Help.. Like (0)

 Rahul Malani Jan 10, 2013 5:10 AM (in response to Gaurav Nautiyal)

Hi Gaurav, It's look like you have not configured Sender EDI Separator channel correct. Provide parameters values, which you have configured in sender edi separator channel. - Rahul Like (0)

 Gaurav Nautiyal Jan 10, 2013 5:39 AM (in response to Rahul Malani)

Hi Rahul,I have setup Sender EDI separator channle with details as Message Type - ORDER, D, 96A, sender ID- 1234, Code Qual- All, Reciever ID- 4321, COde Qualf - ALL. Am I mising any PI seeting needed for EDI separator , I read in document some EDIFACT tables are there do I need to do anything with that. Like (0)

 Rahul Malani Jan 11, 2013 1:28 PM (in response to Gaurav Nautiyal)

I believe you are referring to EDIXML to EDI convertor module. That is required to convert Business document in EDIXML format to EDI and vice versa. Please refer following blog and EDIFACT's tables. Like (0)

 Gaurav Nautiyal Jan 28, 2013 5:38 PM (in response to Rahul Malani)

Hi Rahul, I have setupped EDIFACT inbound scenario similar to yours , but after my EDI message is processed through EDI separator (which I see processed in MONI) my another receiver channel for EDI separator where I mention sender ID/Qualf , Receiver ID/Qualf is failing giving message " No communication channel is found for sender ID/Qul etc.." this error I can see in communication channel monitoring. Please suggest if you have tested EDIFACT inbound and its working, or if you have any idea of issue I am facing. Thanks.. Like (0)

 Dimitri Sannen Feb 18, 2013 8:17 PM (in response to Gaurav Nautiyal)

Hi Gaurav, I'm also struggling with the inbound EDI scenario and I'm stuck in my B2B Integration Cockpit. I'm trying to load EDI and XML message into it, but without any success. In the meantime, I opened a thread:http://scn.sap.com/thread/33 09007 But no response yet. Looks all (too) new to me and no one really tested it. Kind regards, Dimitri Like (0)

 Gaurav Nautiyal Feb 18, 2013 8:52 PM (in response to Dimitri Sannen)

Hi Dimitri, Sorry I didn't updated thread but I have actually successfully resolved this. I have sucessfully implemented both EDIFACT and X12 (five inbound message types : ORDERS/ORDCHG/REQOTE/I NVRPT/SLSRPT) messages. Let me know if you need any info and share yours email ID I can send you screenshots as how I have enabled also If I could be of any help, But I have based my implementation more or less on Rahul's thread only with few tweaks.. Take it easy..Thanks Gaurav... Like (0)



Dimitri Sannen Mar 4, 2013 8:52 AM (in response to Gaurav Nautiyal)

Hi Gaurav, Can you send me screenshots of you B2B Integration Cockpit? Did you use it? You can send it todimitri.sannen@thevaluec hain.be Thanks a lot. Dimitri Like (0)

 Indrajit Sarkar Nov 1, 2013 10:45 AM

Nice Blog Rahul Like (0)

 V R Nov 4, 2013 11:32 AM

Hi Rahul, Thanks for the Blog, it is really helpful. I would like to understand what is the source structure that we are going to use to map with the idoc(target message). I am not really sure of this B2B, but if seeburger adapters are installed there will be pre loaded standard structures available on behalf of EDI ctsructure. Can you please let me know. Thanks. Like (0)

o Dimitri Sannen Nov 4, 2013 11:37 AM (in response to V R)

Hi, Take the EDI content manager (within the B2B Integration Cockpit) and generate an XSD. Export it and use it into your ESR as source message. Kind regards, Dimitri Like (0)

 V R Nov 4, 2013 12:04 PM (in response to Dimitri Sannen)

Thanks for the clarification Damitri.

Like (0)

 Vishwanath D Nov 4, 2013 5:53 PM

Hi Experts, Am trying a other way scenario i.e EDI Outbound: Orders Response IDOC to ORDRSP96A Edifact file. in the EDI Separator Receiver channel from scenario - ORDERS05 IDOC to EDI Separator receiver channel am getting an error Message could not be forwarded to the JCA adapter. Reason: Channel configuration error: Value with name rcv.handleplain not available. I have as well raised a thread http://scn.sap.com/thread/3448809 detailing the issue. Wanted to check in this forum if any one have encountered such issue. I understand my question is not related to above thread but wanted to ask this here. Apologies for the inconvenience. Regards, Vish. Like (0)

 Amol Bhutada Mar 1, 2014 8:56 PM

Hi, Nice blog, helped me in configuring Inbound EDI interface. We have a requirement to send 997 back. Please help me how to go about it. Thanks, Amol Like (0)

 Anjana S Mar 27, 2014 11:41 PM

Hi Rahul, Thanks so much for this blog. Very detailed and easy to follow. I tried creating the inbound EDI to IDoc scenario just like you described here.In the sender EDISeparator channel I added the X12ConverterModule. I m getting the error saying the configuration is missing for sender service EDI_Separator. But I have the integrated configuration activated for the same. 1 thing I noticed is if I take out the converter module from the sender ediseparator channel, this error is gone, and the message reaches the mapping, but fails in mapping since the XML conversion did not happen. Any ideas on why this is happening? Are we missing something in the B2B Addon install? Thanks a lot in advance! Anjana. Like (0)

o Ruchir Sinha Mar 28, 2014 3:12 AM (in response to Anjana S)

Hi Anjana,

You need to associate the integrated scenario to control key. For this first you have to import the X12 B2B content. This can be done from the integration cockpit http:// :<port>/b2bic After the import is successful you need to go to the Control Key Scenario Association UI and associate the run time scenario with the control key. Add the module as before and execute the scenario.

Thanks & regards, Ruchir Like (0)

 Anjana S Mar 31, 2014 7:14 PM (in response to Ruchir Sinha)

Hi Ruchir, Thanks for your help. I did the control key scenario association to the scenario, but still getting the same error. Not sure if I m missing something else. Thanks, Anjana. Like (0)

 Ruchir Sinha Apr 1, 2014 5:09 AM (in response to Anjana S)

Hi Anjana, If all the configurations are done and you are still getting the error then I need to see the error trace in order to tell the exact problem. Also, I would like to check the input payload which you are trying to send. If you don't want to put the payload on SCN then you can send it to me via mail ( [email protected]). Regards, Ruchir Like (0)

 Ruchir Sinha Apr 2, 2014 7:46 AM (in response to Anjana S)

Hi Anjana, Could you check with the BASIS colleagues whether the B2B files for X12 are imported properly or not? If not please ask them to import and then define the scenario association. Regards, Ruchir Like (1)

 Saurabh Kumbhare Jun 9, 2014 6:08 PM

Hello Experts, I am configuring the scenario ( AS2 to EDISeparator and EDISeparator to IDOC ). Can you please help me with the error below which is from the either the EDISeparator Receiver channel or the EDISeparator Sender channle.

09.06.2014 17:52:18.7 09 09.06.2014 17:52:18.7 78

Informatio n Message is encrypted with 1.3.14.3.2.7 algorithm

Informatio n AS2 Message is signed with SHA1 (1.3.14.3.2.26) algorithm AS2 Message message signature is validated, signer ID is 09.06.2014 X509CertSelector: [ Serial Number: 1624063516 Issuer: CN=Mendelson 17:52:18.7 Informatio AS2 TEST,OU=Integration,O=Mendelson,L=Berlin,ST=Unknown,C=GE 79 n matchAllSubjectAltNames flag: true ] 09.06.2014 17:52:18.7 84 09.06.2014 17:52:18.7 84 09.06.2014 17:52:18.7 85 09.06.2014 17:52:18.7 85 09.06.2014 17:52:18.7 85 09.06.2014 17:52:18.7 85 09.06.2014 17:52:18.7 86 09.06.2014 17:52:18.7 91 09.06.2014 17:52:18.7 91 09.06.2014 17:52:18.7 92 09.06.2014 17:52:18.8 31 09.06.2014 17:52:18.8 31 09.06.2014 17:52:18.8

Informatio n AS2 document size is 350 Bytes Informatio n Payload charset converted from ISO-8859-15 to ISO-8859-15 Informatio n B2B EdifactConverterModule : EDI format detected as EANCOM Informatio n B2B EdifactConverterModule: Message will be read as ISO-8859-1. Informatio n MP: processing local module localejbs/EdifactConverterModule Informatio 0}: The module-paramteter "eancom.subversion.prefix" is not set. Using n default value "false" Informatio 0}: The module-paramteter "eancom..audit" is not set. Using default n value "false" Informatio n MP: processing local module localejbs/CallSapAdapter Informatio Application attempting to send an XI message asynchronously using n connection AS2_http://sap.com/xi/XI/AS2 Informatio n Trying to put the message into the send queue Informatio n Message successfully put into the queue Informatio n Informatio n

The application sent the message asynchronously using connection AS2_http://sap.com/xi/XI/AS2. Returning to application MIC (DeJYUIusqQj6aaYRASdHhAo+4J0=) is calculated using SHA1 algorithm.

36 09.06.2014 17:52:18.8 38 09.06.2014 17:52:18.8 43 09.06.2014 17:52:18.8 45 09.06.2014 17:52:18.8 59 09.06.201 4 17:52:18.9 12 09.06.201 4 17:52:18.9 13 09.06.201 4 17:52:18.9 18 09.06.201 4 17:52:18.9 61 09.06.201 4 17:52:19.0 01 09.06.201 4 17:52:19.0 01 09.06.201 4 17:52:19.0 06 09.06.201 4 17:52:19.0 06 09.06.201 4 17:52:19.0 06 09.06.201 4 17:52:19.0 09 09.06.201 4 17:52:19.0 10

Informatio n The message was successfully retrieved from the send queue Informatio n Message status set to DLNG Informatio n MDN is succcessfully signed with SHA1 (1.3.14.3.2.26) algorithm Informatio n Trying to put the message into the send queue

Informatio n Message successfully put into the queue

Informatio n The message was successfully retrieved from the send queue

Informatio n Message status set to DLNG

Informatio n Trying to put the message into the send queue

Informatio n Message successfully put into the queue

Informatio n The message was successfully retrieved from the send queue

Error

MP: exception caught with message No configuration / default adapter specified for EDISeparator

Informatio Delivering to channel: n B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator

Informatio n Message status set to DLNG

Error Error

Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator Transmitting the message to endpoint using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException : java.lang.Exception: No configuration / default adapter specified for

EDISeparator 09.06.201 4 17:52:19.0 15 09.06.201 4 17:52:19.0 15

Informatio The asynchronous message was successfully scheduled to be delivered n at Mon Jun 09 17:57:19 CEST 2014

Informatio n Message status set to WAIT

Like (0)

o Dimitri Sannen Jun 10, 2014 8:32 AM (in response to Saurabh Kumbhare)

Dear, Please open a separate thread with your question. The space here is getting too narrow. Also, other people facing the same issue can find back the answer easily. Thank you. Dimitri Like (0)

 Saurabh Kumbhare Jun 10, 2014 11:32 AM (in response to Dimitri Sannen)

Hi Dimitri, Moved it to another forum. Thanks Saurabh. Like (0)

 sudeep singh Jun 22, 2015 1:24 AM

Hi Rahul,, having a quick question since we are not doing EDI to XML conversion in Adapter, so how we translate the data to Idoc, do we do using PI graphical mapping(if yes how?) or and other addon mapping? Thanks, Sud.. Like (0)

 Pradeep Bawlia Jul 31, 2015 3:33 PM

Really a good blog, thanks