Download - B2B EDI Inbound
-
7/24/2019 B2B EDI Inbound
1/21
B2B- EDI Inbound -Step by Step ConfgurationPosted by Rahul MalaniinB2B Integration with SAP Proess !rhestrationon Sep 2"# 2$%2 %&'(&%) PMinShare%
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
PIspae.In this blog Ill 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 850: Orders
Message format: ANSI X12 Message format: ANSI X12
Version: 4010 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 Director:
Message Flow:
Ste! 1"EDI message comprising multiple business transactions received in SAP PI by available
technical adapters.
Ste! #"Receiver EDI Separator Adapter split received message into individual business transaction
message.
Ste! $"Individual messages then mapped to target messages in SAP PI.
http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/tapan.singhhttp://scn.sap.com/community/b2b-integration/bloghttp://scn.sap.com/community/b2b-integration/bloghttp://scn.sap.com/community/b2b-integrationhttp://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141296/scenario1.pnghttp://scn.sap.com/people/tapan.singhhttp://scn.sap.com/community/b2b-integration/bloghttp://scn.sap.com/community/b2b-integrationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration -
7/24/2019 B2B EDI Inbound
2/21
Ste! %"Acknowledgement generated and sent back to sender of EDI message [Only available in case
of ANSI X12 messages now].
Ste! 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 #: 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 &on'guration:
Sender Agreement:
File Sender Communication Channel:
http://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141300/senderagree.png -
7/24/2019 B2B EDI Inbound
3/21
Ill describe the reason to keep file name as *ANSI*.* later in the blog.
Receiver determination:
Interface determination:
No mapping in this interface.
http://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141305/3.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141301/2.png -
7/24/2019 B2B EDI Inbound
4/21
Receiver Agreement:
EDISeparator Receiver communication channel:
Message Protocol is ANSI X12, since in example inbound EDI message contains ANSI X12 messages.
http://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141307/5.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141306/4.png -
7/24/2019 B2B EDI Inbound
5/21
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
http://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141310/8.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141309/7.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141308/6.png -
7/24/2019 B2B EDI Inbound
6/21
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 # &on'guration:
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.
http://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141312/10.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141311/9.png -
7/24/2019 B2B EDI Inbound
7/21
Module X12ConverterModule configured in Module parameter of communication channel to convert EDI
into EDI XML.
Receiver determination:
http://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141317/12.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141313/11.png -
7/24/2019 B2B EDI Inbound
8/21
Interface determination:
In ESR mapping has to be developed to map EDI XML to Invoice IDoc.
Receiver Agreement:
http://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141319/14.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141318/13.png -
7/24/2019 B2B EDI Inbound
9/21
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.
http://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141324/16.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141323/15.png -
7/24/2019 B2B EDI Inbound
10/21
Eecution:
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 #:
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 [messageformat] 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 thedisussion raised in SDN:
http://scn.sap.com/thread/3233645http://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141330/19.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-72497-141325/17.pnghttp://scn.sap.com/thread/3233645 -
7/24/2019 B2B EDI Inbound
11/21
1)Use dierent communication channels on sender side. he! ma! point to same input
folder "here !ou can provide dierent #le names for EDIFAC and A$SI %ul& messagesrespectivel!.
I have opted this solution in this example for simplicity and to maintain focus on the main objective.
'( )ait for ne" support pac&age for *'* "here SA+ planning to provide this enhancement.
I believe from the planned enhancement there will be no need to configure message format in
EDISeparator receiver.
,( )or&around:a( )rite a custom adapter module -to %e used on sender side( "hich can read incomingmessage and create an /0 message "ith root tag descri%ing the message t!pe -sa!EDIFAC or something( %ased on received %ul& message. 1ou need to add these /0 tagsafter reading the headers of the incoming EDI messages. Add this custom module to !oursender channel.
%( Add t"o dierent receivers to the same scenario. And provide condition %ased on value of/l ags !ou have added during !our module development.c( $o" !our message is routed in the right manner to the respective EDI Seperator receiverchannel. )rite another module -or enhance the same adapter module( "hich can removethese /0 tags and convert the pa!load %ac& to plain EDI %ul& message -"hich !oureceived initiall!( and use this module in EDI Separator receiver channels.
Thanks for reading !!2$*'" +iewsProduts&sap,netweaer,proess,orhestration# sap,netweaer,proess,integration.ags& edi# b2b,add-onAerage /ser Rating0* ratings1
inShare%
') Coents
Ashish Shara!t '# 2$%2 "&2% AM
3reat wor4 Rahul 5 +ery insight6ul blog7
8i4e 0%1
o
Rahul Malani!t '# 2$%2 9&') AM 0in response to Ashish Shara1
.han4s Ashish 558i4e 0$1
o
+en4ata :ageswara Rao BandaruDe 2)# 2$%) %&*" PM 0in response to Ashish Shara1
;i Rahul#
http://scn.sap.com/community/b2b-integration/blog/tags#/?tags=sap_netweaver_process_orchestrationhttp://scn.sap.com/community/b2b-integration/blog/tags#/?tags=sap_netweaver_process_orchestrationhttp://scn.sap.com/community/b2b-integration/blog/tags#/?tags=sap_netweaver_process_integrationhttp://scn.sap.com/community/b2b-integration/blog/tags#/?tags=sap_netweaver_process_integrationhttp://scn.sap.com/community/b2b-integration/blog/tags#/?tags=edihttp://scn.sap.com/community/b2b-integration/blog/tags#/?tags=b2b_add-onhttp://scn.sap.com/community/b2b-integration/blog/tags#/?tags=b2b_add-onhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/ashish.sharma13http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-322825http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/tapan.singhhttp://scn.sap.com/people/tapan.singhhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-322919http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-322825http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/venkat.bandaru2http://scn.sap.com/people/venkat.bandaru2http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-553594http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-322825http://scn.sap.com/people/venkat.bandaru2http://scn.sap.com/people/tapan.singhhttp://scn.sap.com/people/ashish.sharma13http://scn.sap.com/community/b2b-integration/blog/tags#/?tags=sap_netweaver_process_orchestrationhttp://scn.sap.com/community/b2b-integration/blog/tags#/?tags=sap_netweaver_process_integrationhttp://scn.sap.com/community/b2b-integration/blog/tags#/?tags=edihttp://scn.sap.com/community/b2b-integration/blog/tags#/?tags=b2b_add-onhttp://scn.sap.com/community/b2b-integration/blog/tags#/?tags=b2b_add-onhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/ashish.sharma13http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-322825http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/tapan.singhhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-322919http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-322825http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/venkat.bandaru2http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-553594http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-322825 -
7/24/2019 B2B EDI Inbound
12/21
i?e7
.han4s#
+en4at7
8i4e 0$1
Sreeniasulu Soaarapu!t %$# 2$%2 %$&$$ AM
3ood wor4 Rahul7
Do we hae separate onerter odules 6or eah strea li4e [email protected] as li4e as %2
8i4e 0$1
o
Ian osen4o:o %(# 2$%2 %%&*" AM 0in response to Sreeniasulu Soaarapu1
;i#
yes 6or EDI@AC. eists the sae loalebs>[email protected] - but i hae anerror
when try to ipleent the sae senario&
Error during processing local bean: localejbs/EDIFACTConverterModule
while trying to invoe the !ethod java"lang"#tring"e$ualsIgnoreCase%java"lang"#tring& o' an object
loaded 'ro! local variable (status
8i4e 0$1
Piyush 3a4har:o %F# 2$%2 %%&$% AM0in response to Ian osen4o1
;i Ian#
Ges7 It is 4nown issue 6or wrt douentation and is already fed7 EDI@AC. isnot in aps letter7 Gou hae to use Hloalebs>Edi6atConerterModuleH
Regards#
Piyush
8i4e 0$1
Ian osen4o:o %F# 2$%2 %%&'" AM 0in response to Piyush 3a4har1
;i Piyush#
than4 you - its wor4s now 5
Regards#
Ian7
8i4e 0$1
3aura :autiyalDe 29# 2$%2 *&)2 PM
;i Rahul#
http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/sreenivasulu.somavarapuhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-323798http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/ivan.kosenko2http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-328561http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-323798http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/piyush.gakharhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-328862http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-328561http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/ivan.kosenko2http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-328886http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-328862http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/garvnahttp://scn.sap.com/people/garvnahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-334663http://scn.sap.com/people/garvnahttp://scn.sap.com/people/ivan.kosenko2http://scn.sap.com/people/piyush.gakharhttp://scn.sap.com/people/ivan.kosenko2http://scn.sap.com/people/sreenivasulu.somavarapuhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/sreenivasulu.somavarapuhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-323798http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/ivan.kosenko2http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-328561http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-323798http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/piyush.gakharhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-328862http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-328561http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/ivan.kosenko2http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-328886http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-328862http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/garvnahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-334663 -
7/24/2019 B2B EDI Inbound
13/21
Just a =ui4 =uestion will it wor4 the sae way i6 fle ontains two 9*$ 0Inbound purhase
orders1 6or either sae or diKrent partner 7
.han4s#
3aura
8i4e 0$1
o
Rahul MalaniDe 2F# 2$%2 *&$$ AM0in response to 3aura :autiyal1
;i 3aura#
Ges senario will wor4 in sae way7
Regards
Rahul
8i4e 0$1
3aura :autiyalJan F# 2$%' (&)) PM0in response to Rahul Malani1
;i Rahul#I tried to ipleent the sae way 6or EDI@AC. essages but y Sender EDI
separator hannel is 6ailing with reason no Message type 6ound or ouldnot
fnd essaeg type7
Any idea or eaple 6or EDI@AC. inbound proessing or what alues i need to
fll under @ilter or Sender Couniation hannel 6or EDI separator7
Also any idea how to setup outbound essages 6ro SAP to PI to point to two
diKrent inter6aes setup 6or 2 diKrent partners7
.hans4#
3aura
8i4e 0$1
3aura :autiyalJan %$# 2$%' )&$9 AM0in response to Rahul Malani1
I did soething and now able to see soe progress in R
-
7/24/2019 B2B EDI Inbound
14/21
Rahul MalaniJan %$# 2$%' *&%$ AM0in response to 3aura :autiyal1
;i 3aura#
Its loo4 li4e you hae not onfgured Sender EDI Separator hannel
orret7 Proide paraeters alues# whih you hae onfgured in
sender edi separator hannel7
- Rahul
8i4e 0$1
3aura :autiyalJan %$# 2$%' *&'F AM0in response to Rahul Malani1
;i Rahul#I hae setup Sender EDI separator hannle with
details as Message .ype - !RDER# D# F(A# sender ID- %2')#
Code ual- All# Reieer ID- )'2%# C!de ual6 - A887
A I ising any PI seeting needed 6or EDI separator # I read
in douent soe EDI@AC. tables are there do I need to doanything with that7
8i4e 0$1
Rahul MalaniJan %%# 2$%' %&29 PM 0in response to 3aura
:autiyal1
I beliee you are re6erring to EDIM8 to EDI onertor
odule7 .hat is re=uired to onert Business
douent in EDIM8 6orat to EDI and ie ersa7
Please re6er 6ollowing blogand upload [email protected]
tables7
8i4e 0$1
3aura :autiyalJan 29# 2$%' *&'9 PM 0in response
to Rahul Malani1
;i Rahul#
I hae setupped EDI@AC. inbound senario
siilar to yours # but a6ter y EDI essage
is proessed through EDI separator 0whih I
see proessed in M!:I1 y another reeier
hannel 6or EDI separator where I ention
sender ID>ual6 # Reeier ID>ual6 is 6ailing
giing essage H :o ouniation hannel
is 6ound 6or sender ID>ul et77H this error Ian see in ouniation hannel
onitoring7
Please suggest i6 you hae tested EDI@AC.
inbound and its wor4ing# or i6 you hae any
idea o6 issue I a 6aing7
.han4s77
8i4e 0$1
http://scn.sap.com/people/tapan.singhhttp://scn.sap.com/people/tapan.singhhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336173http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336171http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/garvnahttp://scn.sap.com/people/garvnahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336208http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336173http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/tapan.singhhttp://scn.sap.com/people/tapan.singhhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336469http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336208http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336208http://scn.sap.com/community/b2b-integration/blog/2012/06/07/sap-pi-using-the-b2baddon-edixml-convertor-modules--basicshttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/garvnahttp://scn.sap.com/people/garvnahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-338759http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336469http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336469http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/garvnahttp://scn.sap.com/people/tapan.singhhttp://scn.sap.com/people/garvnahttp://scn.sap.com/people/tapan.singhhttp://scn.sap.com/people/tapan.singhhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336173http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336171http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/garvnahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336208http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336173http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/tapan.singhhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336469http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336208http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336208http://scn.sap.com/community/b2b-integration/blog/2012/06/07/sap-pi-using-the-b2baddon-edixml-convertor-modules--basicshttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/garvnahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-338759http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336469http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-336469http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration -
7/24/2019 B2B EDI Inbound
15/21
Diitri Sannen@eb %9# 2$%' 9&%" PM 0in
response to 3aura :autiyal1
;i 3aura#
I also struggling with the inboundEDI senario and I stu4 in y
B2B Integration Co4pit7
I trying to load EDI and M8
essage into it# but without any
suess7
In the eantie# I opened a
thread&http&>>sn7sap7o>thread>''
$F$$"
But no response yet7 8oo4s all 0too1
new to e and no one really tested
it7
ind regards#
Diitri
8i4e 0$1
3aura :autiyal@eb %9# 2$%'
9&*2 PM0in response to Diitri
Sannen1
;i Diitri#
Sorry I didnt updated thread
but I hae atually
suess6ully resoled this7I hae suess6ully
ipleented both EDI@AC.
and %2 0fe inbound
essage types &
!RDERS>!RDC;3>RE!.E>I
:+RP.>S8SRP.1 essages7
8et e 4now i6 you need any
in6o and share yours eail
ID I an send you
sreenshots as how I hae
enabled also I6 I ould be o6
any help# But I hae basedy ipleentation ore or
less on Rahuls thread only
with 6ew twea4s77
.a4e it easy77.han4s
3aura777
8i4e 0$1
http://scn.sap.com/people/dsannenhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341901http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-338759http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-338759http://scn.sap.com/thread/3309007http://scn.sap.com/thread/3309007http://scn.sap.com/thread/3309007http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/garvnahttp://scn.sap.com/people/garvnahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341977http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341977http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341901http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341901http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/dsannenhttp://scn.sap.com/people/garvnahttp://scn.sap.com/people/dsannenhttp://scn.sap.com/people/dsannenhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341901http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-338759http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-338759http://scn.sap.com/thread/3309007http://scn.sap.com/thread/3309007http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/garvnahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341977http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341977http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341901http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341901http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration -
7/24/2019 B2B EDI Inbound
16/21
Diitri SannenMar )# 2$%'
9&*2 AM 0in response to 3aura
:autiyal1
;i 3aura#
Can you send e
sreenshots o6 you B2BIntegration Co4pit Did you
use it
Gou an send it
todiitri7sannenNthealue
hain7be
.han4s a lot7
Diitri
8i4e 0$1
Indrait Sar4ar:o %# 2$%' %$&)* AM
:ie Blog Rahul
8i4e 0$1
+ R:o )# 2$%' %%&'2 AM
;i Rahul#
.han4s 6or the Blog# it is really help6ul7
I would li4e to understand what is the soure struture that we are going to use to ap with
the ido0target essage17
I a not really sure o6 this B2B# but i6 seeburger adapters are installed there will be pre loaded
standard strutures aailable on behal6 o6 EDI tsruture7Can you please let e 4now7
.han4s7
8i4e 0$1
o
Diitri Sannen:o )# 2$%' %%&'" AM 0in response to + R1
;i#
.a4e the EDI ontent anager 0within the B2B Integration Co4pit1 and generate an
SD7 Eport it and use it into your ESR as soure essage7
ind regards#
Diitri
8i4e 0$1
+ R:o )# 2$%' %2&$) PM 0in response to Diitri Sannen1
.han4s 6or the larifation Daitri7
http://scn.sap.com/people/dsannenhttp://scn.sap.com/people/dsannenhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341956http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341956http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341977http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341977mailto:[email protected]:[email protected]://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/indrajit.sarkarhttp://scn.sap.com/people/indrajit.sarkarhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-417034http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/nvenkata.rajahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-417752http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/dsannenhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-417681http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-417752http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/nvenkata.rajahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-417755http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-417681http://scn.sap.com/people/nvenkata.rajahttp://scn.sap.com/people/dsannenhttp://scn.sap.com/people/nvenkata.rajahttp://scn.sap.com/people/indrajit.sarkarhttp://scn.sap.com/people/dsannenhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341956http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341956http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341977http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-341977mailto:[email protected]:[email protected]://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/indrajit.sarkarhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-417034http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/nvenkata.rajahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-417752http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/dsannenhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-417681http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-417752http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/nvenkata.rajahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-417755http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-417681 -
7/24/2019 B2B EDI Inbound
17/21
8i4e 0$1
+ishwanath D:o )# 2$%' *&*' PM
;i Eperts#
A trying a other way senario i7e EDI !utbound& !rders Response ID!C to !RDRSPF(A
Edi6at fle7 in the EDI Separator Reeier hannel 6ro senario - !RDERS$* ID!C to EDI
Separator reeier hannel a getting an error -
/essage could not %e for"arded to the 2CA adapter. Reason: Channel con#guration error:
3alue "ith name rcv.handleplain not availa%le7
I hae as well raised a thread -
http&>>sn7sap7o>thread>'))99$F detailing the issue7
-
7/24/2019 B2B EDI Inbound
18/21
Gou need to assoiate the integrated senario to ontrol 4ey7 @or this frst you hae to
iport the %2 B2B ontent7 .his an be done 6ro the integration
o4pit http&>>Ohost&Oport>b2bi
A6ter the iport is suess6ul you need to go to the Control ey Senario Assoiation
/I and assoiate the run tie senario with the ontrol 4ey7
Add the odule as be6ore and eeute the senario7
.han4s Q regards#
Ruhir
8i4e 0$1
Anana SMar '%# 2$%) "&%) PM 0in response to Ruhir Sinha1
;i Ruhir#
.han4s 6or your help7
I did the ontrol 4ey senario assoiation to the senario# but still getting the
sae error7 :ot sure i6 I issing soething else7
.han4s#
Anana7
8i4e 0$1
Ruhir SinhaApr %# 2$%) *&$F AM0in response to Anana S1
;i Anana#
I6 all the onfgurations are done and you are still getting the error
then I need to see the error trae in order to tell the eat proble7
Also# I would li4e to he4 the input payload whih you are trying to
send7 I6 you dont want to put the payload on SC: then you an sendit to e ia ail 0ruhir7sinhaNsap7o17
Regards#
Ruhir
8i4e 0$1
Ruhir SinhaApr 2# 2$%) "&)( AM0in response to Anana S1
;i Anana#
Could you he4 with the BASIS olleagues whether the B2B fles 6or
%2 are iported properly or not I6 not please as4 the to iportand then defne the senario assoiation7
Regards#
Ruhir
8i4e 0%1
Saurabh ubhareJun F# 2$%) (&$9 PM
http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/anjana.shttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-477340http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-476454http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/ruchir.sinhahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-477294http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-477340mailto:[email protected]://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/ruchir.sinhahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-477843http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-477340http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/saurabhakumbharehttp://scn.sap.com/people/saurabhakumbharehttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-497314http://scn.sap.com/people/saurabhakumbharehttp://scn.sap.com/people/ruchir.sinhahttp://scn.sap.com/people/ruchir.sinhahttp://scn.sap.com/people/anjana.shttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/anjana.shttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-477340http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-476454http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/ruchir.sinhahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-477294http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-477340mailto:[email protected]://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/ruchir.sinhahttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-477843http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-477340http://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configurationhttp://scn.sap.com/people/saurabhakumbharehttp://scn.sap.com/community/b2b-integration/blog/2012/09/27/b2b-edi-inbound-step-by-step-configuration#comment-497314 -
7/24/2019 B2B EDI Inbound
19/21
;ello Eperts#
I a onfguring the senario 0 AS2 to EDISeparator and EDISeparator to ID!C 17
Can you please help e with the error below whih is 6ro the either the EDISeparator
Reeier hannel or the EDISeparator Sender hannle7
$F7$(72$%)%"&*2&%97"$F
In6oration Message is enrypted with %7'7%)7'727" algorith
$F7$(72$%)%"&*2&%97""9
In6oration AS2 Message is signed with S;A% 0%7'7%)7'7272(1 algorith
$F7$(72$%)%"&*2&%97""F
In6oration
AS2 Message essage signature is alidated# signer ID is*$FCertSeletor& Serial :uber& %(2)$('*%( Issuer& C:MendelsonAS2 .ES.#!/Integration#!Mendelson#8Berlin#S./n4nown#C3EathAllSubetAlt:aes ?ag& true T
$F7$(72$%)%"&*2&%97"
9)
In6oratio
n AS2 douent siUe is '*$ Bytes$F7$(72$%)%"&*2&%97"9)
In6oration Payload harset onerted 6ro IS!-99*F-%* to IS!-99*F-%*
$F7$(72$%)%"&*2&%97"9*
In6oration B2B Edi6atConerterModule & EDI 6orat deteted as EA:C!M
$F7$(72$%)%"&*2&%97"9*
In6oration B2B Edi6atConerterModule& Message will be read as IS!-99*F-%7
$F7$(72$%)%"&*2&%97"9*
In6oration MP& proessing loal odule loalebs>Edi6atConerterModule
$F7$(72$%)%"&*2&%97"9*
In6oration
$V& .he odule-parateter Heano7subersion7prefH is not set7 /singde6ault alue H6alseH
$F7$(72$%)%"&*2&%97"9(
In6oration
$V& .he odule-parateter Heano77auditH is not set7 /sing de6aultalue H6alseH
$F7$(72$%)%"&*2&%97"F%
In6oration MP& proessing loal odule loalebs>CallSapAdapter
$F7$(72$%)%"&*2&%97"F%
In6oration
Appliation attepting to send an I essage asynhronously usingonnetion AS2,http&>>sap7o>i>I>AS2
$F7$(72$%)%"&*2&%97"F2
In6oration .rying to put the essage into the send =ueue
$F7$(72$%)%"&*2&%979'%
In6oration Message suess6ully put into the =ueue
$F7$(72$%)%"&*2&%979'%
In6oration
.he appliation sent the essage asynhronously using onnetionAS2,http&>>sap7o>i>I>AS27Returning to appliation
$F7$(72$%)%"&*2&%979
In6oration
MIC 0DeJG/Ius=(aaGRASd;hAoL)J$1 is alulated using S;A%algorith7
http://sap.com/xi/XI/AS2http://sap.com/xi/XI/AS2http://sap.com/xi/XI/AS2http://sap.com/xi/XI/AS2http://sap.com/xi/XI/AS2 -
7/24/2019 B2B EDI Inbound
20/21
'(
$F7$(72$%)%"&*2&%979'9
In6oration .he essage was suess6ully retrieed 6ro the send =ueue
$F7$(72$%)%"&*2&%979
)'
In6oratio
n Message status set to D8:3$F7$(72$%)%"&*2&%979)*
In6oration MD: is suess6ully signed with S;A% 0%7'7%)7'7272(1 algorith
$F7$(72$%)%"&*2&%979*F
In6oration .rying to put the essage into the send =ueue
$F7$(72$%)%"&*2&%97F%2
In6oration Message suess6ully put into the =ueue
$F7$(72$%)%"&*2&%97F
%'
In6oratio
n .he essage was suess6ully retrieed 6ro the send =ueue$F7$(72$%)%"&*2&%97F%9
In6oration Message status set to D8:3
$F7$(72$%)%"&*2&%97F(%
In6oration .rying to put the essage into the send =ueue
$F7$(72$%)%"&*2&%F7$$%
In6oration Message suess6ully put into the =ueue
$F7$(72$%)%"&*2&%F7$$%
In6oration .he essage was suess6ully retrieed 6ro the send =ueue
$F7$(72$%)%"&*2&%F7$$( Error
MP& eeption aught with essage :o onfguration > de6ault adapterspeifed 6or EDISeparator
$F7$(72$%)%"&*2&%F7$$(
In6oration
Deliering to hannel&B2BSE$$$$2,!2C,!RDERS,+A:S,P!, de6aultadapter speifed 6or EDISeparator
$F7$(72$%)%"&*2&%F7$%$
Error .ransitting the essage to endpoint Oloal using onnetionAS2,http&>>sap7o>i>I>AS26ailed# due to&o7sap7engine7inter6aes7essaging7api7eeption7MessagingEeption& aa7lang7Eeption& :o onfguration > de6ault adapter speifed 6or
http://sap.com/xi/XI/AS2http://sap.com/xi/XI/AS2 -
7/24/2019 B2B EDI Inbound
21/21
EDISeparator
$F7$(72$%)%"&*2&%F7$%*
In6oration
.he asynhronous essage was suess6ully sheduled to be delieredat Mon Jun $F %"&*"&%F CES. 2$%)
$F7$(72$%
)%"&*2&%F7$%*
In6oration Message status set to