12/6/2014

QuickOverviewB2BScenario(End2End)withSe...|SCN

GettingStarted Newsletters

Hi,Guest

LogOn

JoinUs

Store

SearchtheCommunity

Products

Services&Support

AboutSCN

Downloads

Industries

Training&Education

Partnership

DeveloperCenter

Activity

LinesofBusiness

UniversityAlliances

Events&Webinars

Innovation

Browse

Communications

Actions

ProcessIntegration(PI)&SOAMiddleware

QuickOverviewB2BScenario(End2End)with
SeeburgerEDIAdapter
PostedbyStefanHilppinProcessIntegration(PI)&SOAMiddlewareon13Jan201323:59:29
Share

Tweet

Like

InmyblogabouttheSeeburgerEDIAdaptersforSAPPII( http://scn.sap.com/blogs/seeburger_edi),Ihavebeen
askedforsometutorialtoconfigureasimpleendtoendB2BScenariowithSeeburgerandSAPPI.Althoughthisisnot
anewtopic,Idecidedtosetupascenarioona7.3.1environmentwithDualStack(usingtheStandardConfiguration)
sincetheremightstillbesomeconsultantsthatarerelativelynewtothetopic.

Ihavetriednotjusttoprovideherealotofscreenshotswithoutanyexplanation,butalsotoexplainthebasicconcept
behindthescenarioandthehandlingofEDIfiles.Thismakesthispostverylong,butIhopeithelpstogetagood
understanding.

The"Repositorysettings"canbefoundattheendoftheblog"butitisrecommendedtosetuptheseobjectsfirstasthey
willbeneededtodotheDirectoryConfiguration.

ScenarioDescription:

Inthisscenario,thereare4Parties/Entitiesinvolved

2CustomersthatsendediordersintheformatANSIX12_850_V4010,called"ElectronicWorld"and
"GlobalElectronics"

1ServiceProvidercalled"RetailHub"whichsendsdataforbothcustomersthroughoneAS2Connection

1Supplier,called"Seeburger"thatreceivestheordersfrombothpartnersandprocessestheseordersintheSAP
Backend.

Inaddition,IhavesetupaFilePort,usingthesameparametersintheModuleChainliketheAS2Channel,which
allowsforamanualreprocessingofanyreceivedfile.TherefortheModuleChainalsoincludesaparametertosavethe
OriginalEDIFile.

Ingeneralallreceivingscenariosfollowa2Stepapproach

Step1:TechnicalSetuptoreceivefile
ReceivingthefilesviaAS2orFilePort
Analyzingthefiles(Classifier,BIC,Splitter)andforwardingeachsinglemessagetothecorresponding
businesspartner(accordingtothe
SenderIDintheISASegment)

Step2:Processingthedataaccordingtopartner/messagetypeinformation
foreachbusinesspartner,anownpartyisexistingwithaSplitChannelforeachmessagetype.

http://scn.sap.com/community/piandsoamiddleware/blog/2013/01/13/quicksetup

1/6

12/6/2014

QuickOverviewB2BScenario(End2End)withSe...|SCN

DirectorySetup:

ForStep1(receivingthedata),thefollowingobjectsareused:

TheobjectEDI_SP_Seeburgerisonlyusedas"ReceiverParty"intheAS2SenderAgreementandcontainstheown
AS2ID

(theobjectEDI_SP_RetailHubhasincludeditsAS2IDinthesamearea)

EDI_SP_RetailHubandEDI_SP_ManualRestartbothincludeaSenderCommunicationChannelwithallstepsneeded
fortheanalyzingandsplittingofthereceiveddata.

=>Thissetupwillclassifytheincomingdata(toseeifitisEDIFACT,ANSIX12,TRADACOM,XML,FLATFILE...)and
afterwardsdynamicallydetectwhichConversionRule(e.g.fromANSIX12totheequivalentANSIXMLstructure)
needstobeused.
TheSplitterwillthencreateonesingleXMLFile(MainDocument)foreachmessage(inANSIX2foreachSTLoop...in
EDIFACTforeachUNH...)

AccordingtotheSenderIDintheANSIX12message,themessagesarethenforwardedtothedifferentbusiness

http://scn.sap.com/community/piandsoamiddleware/blog/2013/01/13/quicksetup

2/6

12/6/2014

QuickOverviewB2BScenario(End2End)withSe...|SCN

partners/entities

TheSenderAgreementslooklikefollowing:

(Nosignature/encryptionisusedinthisexample,asthefocusislyingontheEDIhandlingandnotonthisspecific
AS2feature...butifrequested,itcanbeaddedtothisscenarioeasily)

ForStep2(assigningeachpartner/messagetypetothecorrespondingbusinessparty)thefollowing2Parties
(Customers)havebeensetupinIntegrationDirectory:

Thefollowingconventionhasbeenusedinthisscenario
Party:realnameofthecustomer(withPrefixEDI_BP...)
Component:SenderIDofISASegment

Inthescreenshot,the2businesspartners/customerscanbeseenandaninboundchannelhasbeencreated(using
theSplit997Adapter).TheseSplitChannelsalwaysprocessthe"splitted"messagesfromthepreviousstep.

InthefollowingScreenshots,thenextstepsforprocessingthesefilecanbeseen

http://scn.sap.com/community/piandsoamiddleware/blog/2013/01/13/quicksetup

3/6

12/6/2014

QuickOverviewB2BScenario(End2End)withSe...|SCN

ConnectionbetweenStep1andStep2.

ToconnecttheoutputoftheMessageSplitterwiththecorrectInboundChannels"fromSplit",anentryneedstobe
existingintheSeeburgerWorkbenchforthispartner/messagecombination:

Keysare:
Sender=>ISASenderID
MappingName=>detectedmessagetypeandversion

SIncetheSenderAgreementforthe2BusinessPartnershavebeencreatedinpreviousstep,theycanjustbeselected
inthisareabyfirstselectingthe"SenderParty",thenclickon"SearchServices"togetalistofallservicesforthis
Party...andthenselecttheproperChannel"fromSplit_850_V4010".

Aftersettingupbothpartners,theMessageSplitterareaintheWorkbenchincludesthefollowing2lines

http://scn.sap.com/community/piandsoamiddleware/blog/2013/01/13/quicksetup

4/6

12/6/2014

QuickOverviewB2BScenario(End2End)withSe...|SCN

ImportantFeature:
Byusingthe"State"field(acceptedorpartlyaccepted)itcanbedecidedhowtohandlelargefileswithmultiple
messages(ST/UNHsegments),ifsomeofthesemessagesarenotcorrect
=>eitherthecompletefilecanbestopped,orthecorrectmesagesareprocessedanywayandthepartnerisinformed
via997whichofthemessagesneedtobecorrectedandtransmittedagain.

TosetupthecompleteEnd2EndScenariotherearealsosomeobjectsneededintheRepositorywhicharementioned
inthefollowingsection.

RepositorySetup

ThefollowingobjectsareneededintheRepository
Interface/ExternalDefinitionfortheANSIX12850processing
Interface/ExternalDefinitionfortheFunctionalAcknowledgement(usedtocreate997messagesinadditionalsteps)
ImportedIDoc
MessageMappingandOperationsMapping

TheseobjectsareavailableastemplateswithmostoftheIndustryPackages.

Runtime:

Inthissection,Iwillsoonprovideadditionalscreenshotfromtheprocessflowandthemonitoringofthisscenario.

Additionallysomescreenshotsregardingthe997handlingwillbeprovided,

Testdata:

HereIwillalsoprovidesome850Testdatathatcanbeusedtosetup/testthisscenario

Feedback:

Anyfeedbackisappreciatedtoenhancethispostinfutureandaddadditionaldescriptions/features.

3244Views

Topics:process_integration,b2b_integrationTags:adapter,b2b,seeburger,edi,sap_netweaver_pi

AverageUserRating
(5ratings)

http://scn.sap.com/community/piandsoamiddleware/blog/2013/01/13/quicksetup

5/6

12/6/2014

QuickOverviewB2BScenario(End2End)withSe...|SCN
0

Share

Tweet

Like

6Comments
ChristophGerber15Jan201312:50

Verydetailedandinteresting.ShowshowflexibletheSeeburgerSAPPIadapterscanbeusedfor
anykindofEDI/B2Binterface.
Like(1)

StefanHilpp16Jan201323:32(inresponsetoChristophGerber)

Thankyou,
letmeknowifthereisanythingyouaremissingorwouldliketohaveadditionalinformation
Stefan
Like(0)

CarlosOcampos06Feb201315:20

VerygoodJobStefan!
Stepbystep,goodexplanations,screenshotstounderstandandveryeasytofollow.

Congratulationforthisblog!!
Like(1)

StefanHilpp06Feb201319:05(inresponsetoCarlosOcampos)

ThankyouCarlos,
Iamgladyoulikeit.
Stefan
Like(0)

KanchamSreenivasulu18Feb201307:16

HiStefan,
LooksgoodbutlookingforwardformorescreenswithPi7.31versionBolog.

Regards,
Sreeni.
Like(1)

StefanHilpp25Jul201310:24(inresponsetoKanchamSreenivasulu)

HiSreeni,

ittookawhilebutfinallyIfoundsometimetocreatea7.31versionofthisblog.
(mainlyfocusingontheIntegratedConfigurationSteps)

Checkitoutandletmeknowifthisitwhatyouhadinmind:
http://scn.sap.com/community/piandsoamiddleware/blog/2013/07/24/quickoverview
b2bscenariowithseeburgerediadapterusingintegratedconfiguration

Regards
Stefan
Like(0)

SiteIndex
Privacy

ContactUs
TermsofUse

SAPHelpPortal
LegalDisclosure

Copyright

http://scn.sap.com/community/piandsoamiddleware/blog/2013/01/13/quicksetup

FollowSCN

6/6