Sie sind auf Seite 1von 6

GettingStarted Newsletters

Hi,Guest

LogOn

JoinUs

Products

Services&Support

AboutSCN

Downloads

Industries

Training&Education

Partnership

DeveloperCenter

Activity

LinesofBusiness

UniversityAlliances

Events&Webinars

Innovation

Browse

ProcessIntegration(PI)&SOAMiddleware

HCI/HCPIS:IDocAdapterDecipheredPart1
TriggerIDocfromSAPERPtoHCIUsingBasic
Authentication
PostedbyBhaveshKantilalinProcessIntegration(PI)&SOAMiddlewareon09Aug201614:15:43
0

Share

Tweet

Like 0

Background
HanaCloudIntegration/HanaCloudPlatformIntegrationServicesprovidesaIDocadapterthatenablesyouto
IntegratewithyourbackendSAPERPsystemusingIDocAdapters.Thisblogseriesisadetailedstartupguideforthe
setuptweaksrequiredtoIntegrateHCIandERPusingIDocs.InthismultipartserieswewilllookatsendingIDoc's
fromSAPERPtoHCIandviceversa.

TherealreadyexistsafewblogsonSCNthatcoversthevariousindividualpiecesofthispuzzlebuttheintentofthis
seriesistocollatethisinfofromaPIDeveloper'sperspective.WhererequiredIwillalsopointtoadditionallinks/
referencesthathadhelpedmeinmyjourney!Duecredittothosecontentaswell.

In Part1(thisblog),wewilllookatstepstotriggeranIDocfromSAPERPtoHCIfromthescratchusingBasic
Authentication.
InPart2(linkwillbeupdatedoncepublished),wewilllookatusingIDocNumbertosearchforIDocsinHCI
InPart3(linkwillbeupdatedoncepublished),wewillthenextendthistouseClientAuthentication.
InPart4(linkwillbeupdatedoncepublished),wewilllookatthestepstotriggeranIDocfromHCItoSAPERPusing
BasicAuthentication.

HCIConfiguration
Description

ScreenShot

HCIIntegrationFlow
Configuration
PointtoPointIntegration
FlowwithNoMapping.
SenderIDocAdapter
andaReceiverSFTP
Adapter
MakesureRoleBased
Authenticationis

selected.

SenderIDocAdapter
Configuration
SelectAdapterType
IDOC
NotetheMessage
Protocolusedbythe
IDocadapterisIDoc
SOAP
Provideaendpoint
addresstowhichthe
ERPsystemshould
triggertheIDoctoin
thiscase:/orders05.
ReceiverSFTPConfiguration

Store

SearchtheCommunity

Communications

Actions

islikeanyotherSFTP
configurationandisnot
describedhere.
GettheEndPointURLfor
yourIntegrationFlow
GotoyourRuntime
Node(IFLMAP)>
Properties>Services
CopyEndPointURL

SAPERPConfiguration
Description
Transaction:BD54
DefineLogicalSystemName
Youcanprovideanylogical
systemnameyoudeemfit.
Inourcasewehavecalled
theLogicalSystemName
"HCI"
DownloadHCISSLCertificate
GotoyourHCIURL,View
Certificate(frompadlock)
>Details>CopytoFile>
SelectDefaultOptions
Savethecertificatetoyour
localdesktop

Transaction:STRUST
GotoviewSSLClientSSL
Client(Anonymous)
ImportyourHCISSL
Certificatehere.
ClickonImport
Certificate
Selectyourcertificate
frompreviousstep
ClickonAddto
CertificateList
Thisisrequiredtoestablish
aSSLconnectionbetween
yourSAPERPandSAPHCI.

Transaction:SM59
InPIyouwouldcreatea
TRFCDestination,inthe
caseofHCIasthe
communicationhappens

ScreenShot

usingSOAPoverHTTPyou
createaConnectionTypeG
ConnectionType:G(HTTP
ConnectionstoExternal
Server)
TargetHost:<HostNamefrom
theEndpointURLcopied
fromHCI>
ServiceNo:443
PathPrefix:/cxf/<Pathin
AddressFieldofIDoc
Adapter>(Inourcasethe

IdocadapterhadOrders05
andhence,/cxf/Orders05
ProxySettingsisany
LogOn&Security
BasicAuthentication
ProvideyourHCIUser
&Password
SecurityOptions,
SSLActive
SSLCertificate
AnonymSSL
Client(
Anonymous)
Theviewwhere
theHCISSL
Certificatewas
loadedinprevious
stepsinSTRUST

TransactionSM59
PerformaTestConnection
IfeverythingisGood,
YoushouldgetaHTTP
500Response
ResponseBodyshould
containthetext
referringtocheckHCI
MonitoringforMore

details
InHCIMonitoringyou
shouldseeamessage
witherror""
Iftheusername/password
iswrong
YoushouldgetaHTTP
401UnAuthorized
Error
IftheHCISSLCertificate
hasnotbeenloaded
correctlyinSTRUST
Keystore,
Youwillgeterror
ICM_HTTP_SSL_Error
TransactionWE21
InPI,youcreateaTRFC
Port.InHCI,youcreatea
XMLHTTPPortasthe
connectionhappensusing
SOAPOverHTTP
PortType:XMLHTTP
RFCDestination:HTTP
DestinationTypeGfrom

PreviousStep
ContentTypeDefault
SettingText/XML
SOAPProtocolSelected
AsHCIisexpectingthe
IDocasaSOAPover
HTTP,doensurethat
SOAPProtocolis
selectedhere.Thiswill
makesurethatthe
messagethatgoesout
fromERPisaSOAP
message.

Transaction:WE20
Addanoutboundentryfor
yourLogicalSystemasper
theIDocbeingused.
Inourcaseweareusing
ORDERS.ORDERS05IDoc
andhencetheoutbound
entrywillcontainthe
ORDERS.ORDERS05
details
ThePortwillbetheport
createdinPreviousStep.

TestYourFlow
Youaredone!TriggertheIDocusingeitheryourstandardtransactionorusingWe19.TheIDocshouldnowbesentto
HCIandprocessedbyHCI.

TestCase#1:HCIIntegrationFlowExecutesSuccessfully
IDoctriggeredusingWE19


HCIIntegrationFlowStatus

IDocStatusinWE02

TestCase#2HCIIntegrationFlowFails
MakeHCIIntegrationFlowFails(InmycaseSFTPAdapterisupdatedtohaveainvalidUserName)
HCIreturnsastatusHTTP500backtoSAPERP
IDocinWE02willgointostatus02(Failure)
AstheIntegrationhappensusingSOAPOverHTTPthisistechnicallyaSynchronousIntegrationandifaHTTP
202/200isnotreceivedbackfromHCI,SAPwillmarktheIDocstatusasfailed.

TestCase#3IDoctriggeredinWE19withNoofIDocstoberepeatedas2
SingleMessagereceivedatHCI.
IDocXMLwillcontain2IDoctags1forEachIDoc

Summary
HCI'sIDocadapterusesSOAPoverHTTPandhencethisendsupbecomingaSynchronousFlow.
InSAPERP,
MakesureyourPortinWE21isoftypeXMLHTTP&hasSOAPProtocolEnabled.
MakesureyourRFCDestinationinofTypeG
ThestatusofyourIDocinWE02willbe03/02dependingonthestatusofyourIntegrationFlowinHCI.
IfHCIIntegrationFlowsuccessful,Status=03

IfHCIIntegrationFlowfails,Status=02

Categories:SAPHANACloudIntegration(HCI),ProcessOrchestration,ProcessIntegration
129Views
Tags:idoc,soap,idocs,hci,idocaae,outboundidoc,idocoutbound

AverageUserRating
(0ratings)

Share

Tweet

Like 0

0Comments
Therearenocommentsonthispost

SiteIndex
Privacy

ContactUs
TermsofUse

SAPHelpPortal
LegalDisclosure

Copyright

FollowSCN

Das könnte Ihnen auch gefallen