Error Handling in Odata

4/23/2017 IssuesfacedwithSAPGateway(GWbySE80Method)|SAPBlogs
GetStarted

Solutions Support Training Community Developer Partner About
Community / Blogs Actions
IssuesfacedwithSAPGateway(GWbySE80
Method)
December24,2014 | 1,131Views |
VaibhavDeorukhkar
morebythisauthor
SAPGateway
gatewayerror | gatewayse80 | issueresolutiongateway | problemsingateway | sapgateway | sapnetweavergatewayerror
share
0 share
0 tweet share
0 0
like

Follow
https://blogs.sap.com/2014/12/24/issuesfacedwithsapgatewaygwbyse80method/ 1/23
Helloeveryone,
BelowyouwillfindanillustrationofissuesfacedinSAPNetWeaverGatewaywhilecreatingservices
by the obsolete SE80 method.Although the SE80 method of generating gateway services is no more being
used by projects this document may prove useful to help resolve realtime issues for developers and
customersstillusingthisversion.
ThedocumentdiscussesvariousissuesalreadyfacedduringGoLive/PostGoLivephaseofthe
projectandalsoelaboratesasolu onastohowtheaboveshownGatewayErrorswereresolved.Although
SAP has provided us with the standard SAP Gateway Error Log. The messages are some mes hard to
decipheranddonotindicatetheac onneeded.
Pleasefeelfreetopostyourcomments.Andalso,docorrectmewhereyouthinkImayhavegone
wrong.Reasonbeing,thisisjustthestartandthereisalwaysscopeforimprovement.
Thanks.
VaibhavDeorukhkar
*******************************************************************************************************************************
***********************
IssuesfacedwithSAPNetWeaverGatewayandits
Resolu on(SP05andbelowversions)
Letsstartwithmostbasicandcommonerrorsfaced
SAPNetweaverGatewayhasbeendeactivated
Solution:
TheaboveerroroccurswhenGatewayisdeactivated.Toresolvethisnavigatetotransaction
codeSPRO,andexpandthebelowshownnodestoactivateSAPNetWeaverGateway.
P.S There may also be a case that an SAP System is having multiple clients and Gateway being
activated on another Client. In such a case it is required to maintain the system alias of that client
whilecreatingservicesorthesameerrormightagainpopup.
NoSystemAliasfoundforServiceZxxxxxxx_xxxxanduserXXXXXX
Solu on:
ThisisakindofanerrorwhenserviceisgeneratedaccordingtoSdatastandardinsteadofOdata.
AlthoughSdatas llisatypeofserviceURLbutifthefrontenddeveloperissendingdatainOdataformat;
itsrecipienthastobeinOdataformatonly.Andsinceintheabovescreenshotweconguredasystemalias
for the OData service, the above error has popped up since no system alias corresponding to the Sdata
versionoftheservicewascreated.ServiceswhichcontainOdataintheirURLhavebe ercompa bility
withODatastandardandmightintroducesupportforaddi onalODatacapabili es.TheODataURLofa
serviceisafeaturewhichwasaddedtoGatewaySP3.Sdataiss llavailableforbackwardcompa bility.
Bo omlineis,iftheserviceyouareworkingwithisavailableinOdataURLaswell;usethatinsteadofthe
sdataURL.
Noservicefoundfornamespace/SAP/,nameZ****_P****_I****,versionXXXX.
Solution:
This common error usually occurs when the service is not properly transported. Under
DevelopmentEnvironmentsuchanissueneverarises.Butoncetheservicesaremovedtoanother
environment(sayQuality/Production),itisapossibilitythattheabovemessageisregisteredinthe
errorlog.ToresolvethiswenavigatetoSPROTransactionandexpandtothebelowshownnode.
Next,navigatetotheServiceandselecttransport.
Entertherelevanttransportnumberandclickonsave.InSE10,youwillnowbeabletoseethe
newlyaddedentry.
Value*XXXXXXXXX*violatesfacetinformationmaxlength=10
Solution:
ThiserrorisencounteredwhentheRequestDataattemptstobetransmittedtotheBackend
withadatalengthmorethanwhatissetintheGateway/RFC.Thiscanberesolvedbytwo
methods
a.)Increasingthedatatypelength,sothatitequalsthelengthofthetargetdata,thatis
actuallybeingsentoverthroughthegateway.
b.)SettingtheDataTypelengthasSTRINGintheRFC/Classandappropriateconversionbe
doneintheCodetherebyavoidingthepossibilityofsuchanerrorbeingregisteredintheSAP.
RFCcallwasnotsuccessfulbecauseofsystemfailureUnabletointerpret0,0asa
number.
Solution:
Thiserrorisencounteredintwocases.
a.)WhentheDatabeingpassedoverthegatewayisofadatatypeotherthanthatwhatissetinthe
Backend.
Fore.g.I_QUANTITY,animportparameterissetintheCode/GatewayoftypeQUAN13anddatabeing
passedissay15*000(auserinput).
b.)Whentheuserparametersforaparticularuseraresetinsuchaway(fore.g.,toindicate.In
15,000)thattheGatewayParametersfailtointerpretthesymbol.Thisisbecauseingatewayweset
astaticdatatype.
Wecanmaintaintheuserparametersbynaviga ngtotheSU3Transac onCode.
Invalidformat(returntable):RowNumberX,PropertyNamexxxx_xxx_xx,PropertyValue
XX
Solution:
Thiserrorisencounteredwhenthevaluereturnedbytheserviceisnotinthesameformat
asexpected.
Fore.g.N.Na.NaNainsteadofastandardSAPDate.Thisthrowsanerroratthegatewaylevel.
However,noerrorisloggedinST22orrelevantDumpLogger.
Solution:
ThiserroroccurswhenthedataisstoredinSAPintheaboveshownformat.Thedatacannot
becorrectedbutstepshavetobetakentoensurethatthedatapassedontotheBAPIiscorrect.The
originofsuchgarbagedatacanbeanythingfromtheFrontendcodetotheBackendcode.There
are no explicit steps to handle such data at Gateway Level. However, if the output format of the
returntableismadetobeStringorCharthenprobablywecanatleastpreventfromshowingupan
HTTPrequestfailedontheUI5Frontend.
ErrorwhileparsinganXMLstream
Solution:
ThiserrorisencounteredwhenaspecialcharacterispassedinaREADURL.StandardSAP
Gateway(SE80)versionsupportsonlyupto1specialcharacterintheREADURL,inthiscase:isalready
used,soifitwastryingtopassanotherspecialcharactersuch/,thenitthrowsadumpintheErrorLog
andignorestheotherenteredspecialcharacter.
ActualDatainSAPwas
Thus,aswecansee,the/inN/Aiscaughtasaspecialcharacterandthrowsanerrorlog.
RFCcallwasnotsuccessfulbecauseofsystemfailureUserUK_XXXXXisalready
processingPurchasingdocum.
Solution:
Usuallysuchamessageshouldpopupasanerror/warningmessageontheUI5screen.Butif
thestandardBAPIbeinguseddoesnotfacilitatesendingsuchamessageasanexportparameteron
theUI5Screenandthedocumentisbeingeditedsimultaneouslybymorethanoneperson,thenthe
gatewayerrorlogregisterssuchamessageandshowsanHTTPRequestFailedontheUI5Screen.
Inconsistencyinkeyfieldi_process_order.
Solution:
Akeyfieldshouldneverbepassedblankthroughgateway.Thissettingcanbedoneinthe
RFCagainstwhichthegatewayserviceismade.Ifitisnotnecessaryforthatfieldtoholddataatall
timestheserviceiscalledthenitshouldbemarkedasoptional.Orotherwiseitshouldbemadesure
thatthisfieldalwayscarriessomevalue.
NoauthorizationtoaccessServiceZXXX_XXXXXX_XX_0001.
Solution:
Thisisabasisissuetododealwith.TherearespecificauthorizationstoaccessaGateway
Service.Theremayberequiredtoincorporateseparaterolesfrombasissidetosolvethisissue.
RFCcallwasnotsuccessfulbecauseofsystemfailureNoauthorizationtologonasa
TrustedSystem(L
Solution:
Thisisagainabasisissue.Specicse ngsaredonebythebasisteamtohelpresolve
thisissue.
Invalidkeypredicate
Solution:
ThisisencounteredwhentheURLpassedtocallagatewayserviceisincorrect.By
incorrectitisimpliedthatacertainkeyfieldisnotpassedintheURLwhichisconsideredas
mandatorytocontaindata.
BelowisasampleURLwithanInvalidKeyPredicate.
OperationtypeQdoesnotexistintheDataModel
Solution:
ThisisatypeoferrorwhenaQueryURLiscalledinsteadofaRead.InSAPGatewayifit
isknownthattheoutputcontainsatableofdata,thegatewayserviceatthedevelopmentstageitself
needstosupportQueryOperation.Hereinthecaseshownabove,maybeitwaspreviouslyexpected
thatoutputwillbeintheformatofInputfollowedbysingle/multipleexportparameters.ButtheURL
wascalledwithanexpectationthatatablewillbepassedontothefrontend.
Therecanbetwoscenariosfortheabove
a.)TheURLforQueryiscalledbymistakewhenitwasintendedtocallaReadService.
b.)TheGatewayserviceismadewithoutproperknowledgeoftheexpectedoutput.Atthispointin meit
isabsolutelynecessarytohavepropercoordina onbetweentheGatewayDeveloperandtheABAPer.
DatabaseLockforServiceZ**********couldnotbeset.
Solution:
This situation was encountered when many users are accessing a particular service
continuously. Although it did not seem to hamper any business functionality for the client, it was
deemedasapotentialhiccuptotheUI5applicationasawhole.Henceitwasdecidedtoturnonthe
Metadata Cache within the Gateway and since then the above issue never reoccurred. As a
negativeconsequenceofthesame,itwasneededtoclearthegatewaycacheaftereachcodedrop
intotheproductionenvironment.
Note:Cacheofonlythoseservicesneededtobeclearedthatweretransportedwithaddi onalelds.That
is,onlythosewithchangestotheexis ngones.Asama erofconcern,EachandeveryService
metadatacacheissafetobecleareda eracodedropintoProduc onEnvironment.
RFCcallwasnotsuccessfulbecauseofsystemfailureFillinallrequiredentryfields.
Solution:
Whenamandatoryeld(bymandatoryeld,wemeanthattheeldshouldcontaindata)is
missedoutintheURLthatistriggered,wehavethisentrybeingregisteredintheerrorlog.Toresolvethis,
itisrequiredtochecktheURLagainandthebackendcodeagainandensurethatallthemandatoryelds
containproperdata.
SpecifyPositiveValuesOnly
Solution:
Itisrequiredthataquan tyeldcannotbepassedasnega ve.Itmayalsobethecasethatthe
value that is passed is being derived a er mul ple calcula ons in the front end and eventually the
calcula on results in a nega ve number as a result (scenario might be dierent) and thus leads to
registeringthiserrorintheErrorLog.Thebestsolu ontoallowanega venumber,isdeclaringthedata
type of the eld being set to CHAR and then once the ABAP Code takes control of the parameters, it is
convertedtotherequirednega vevaluewithinthecode.
DereferencingoftheNULLreference
Solution:
ThisissuecroppedupintheProduc onEnvironmentandsomethingwhichwehadnot
expected.Therootcauseofthiswas,achangeintheBackendParameter,achangeintheGatewayService
butthegatewayserviceparametersnotge ngreectedintheproduc onenvironmentevena ermul ple
transports. This was then resolved a er clearing the Gateway Cache by naviga ng to the Transac on
/IWFND/CACHE_CLEANUP
BelowarethestepstoclearGatewayMetadataCache.
1.NavigatetotheTransaction/IWFND/CACHE_CLEANUP.
2.UsetheF4HelpandenterthepartoftheDataModelwhosecacheneedstobecleared.
3.ChoosetheGatewayServicewithtypePS(PublicSolution).
4.NextafterselectingtherequiredDataModelpressF8(Execute).
5.GatewayMetadataCacheclearedsuccessfully.
Toconclude,mostoftheGatewayErrorLogentriesclearlyexplainwhattheerroris;fortheonesthat
donot,wecanrefertothescenariosexplainedaboveandhelpresolvetheissues.Thisdocumentdoesnot
cover all the issues encountered but covers mostly those that posed a hindrance in the Produc on
Environment.Hopethishelps.
VAIBHAVDEORUKHKAR
***********************ENDOFDOCUMENT***********************
AlertModerator
7Comments
SrikanthGajula
January7,2015at10:12am
HelloVaibhav,
Goodstart,hopetoseeyouwriteonSEGWinnearfuture .
Cheers
Sri
VaibhavDeorukhkar Postauthor
ThankyouSrikanthyesiwill!!
EkanshSaxena
HiVaibhav,
Itsreallyagoodblogwhichcompilesthecommonerrorsatoneplace.Itwouldhelpmanywhiletroubleshooting.
IMOthenameoftheblogisbitconfusing. Youhavepostedtheerrorsfacedandthesolutionsbutthenamesuggests
thatitwillleadtotheconstraintsorlimitsofSAPGateway.
Regards,
Ekansh
VaibhavDeorukhkar Postauthor
ThankyouEkansh,
Updatedthetitleaccordingly
PavanGolesar
February1,2016at11:54am
HiVaibhav,
AddingtoEkansh,Goodbundlingoferroralongwithsolutions
Nicetroubleshootingdocument..
SavedandBookmarked.
Regards,
PavanG
UmitCoskunAydinoglu
March29,2016at1:24pm
Hello,
Gooddocument!
IamgettingNoauthorizationtoaccessServiceZXXX_XXXXXX_XX_0001forasevicewhichsdefinitionisonanother
system.Therearealsoanotherservicewhichisdefinitionisonthatsystem.Icheckedbothservicesandcouldntfindany
difference.Doyouhaveanyidea?
KindRegards,
Cokun
UmitCoskunAydinoglu
April21,2016at5:15am
Forauthorizationerrorsyouneedtocreatearoleintheserviceasstatedinthisdocument
AuthorizationsandRolesforTransactionalAppsSAPFioriprincipalappsforSAPERP1.0SAPLibrary
AddComment
Share & Follow Privacy TermsofUse LegalDisclosure Copyright Trademark Sitemap Newsletter

Error Handling in Odata

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Error Handling in Odata

Uploaded by

Copyright:

Available Formats

4/23/2017 IssuesfacedwithSAPGateway(GWbySE80Method)|SAPBlogs

Community / Blogs Actions

gatewayerror | gatewayse80 | issueresolutiongateway | problemsingateway | sapgateway | sapnetweavergatewayerror

Wecanmaintaintheuserparametersbynaviga ngtotheSU3Transac onCode.

You might also like