SAP各種場(chǎng)景下的DEBUG方法

資料來(lái)源于網(wǎng)絡(luò)收集及個(gè)人經(jīng)驗(yàn)總結(jié)資料來(lái)源于網(wǎng)絡(luò)收集及個(gè)人經(jīng)驗(yàn)總結(jié)

SAP各種場(chǎng)景下的Debug方法

Contents直接在程序中設(shè)斷點(diǎn) 2BackgroundJob的Debug 2在程序運(yùn)行界面進(jìn)入Debug 3正在運(yùn)行的程序debug 3CallFunctioninUpdateTaske的debug 4SM13ErrorMessageDebug 4RFCDebug 5針對(duì)彈窗的DEBUG 7SE16/SE16N修改表內(nèi)容 8SE16 8SE16N 11修改Debug模式為經(jīng)典/新 11SAPscript的Debug 14使用StepSize 15Debug返回已經(jīng)執(zhí)行過(guò)的語(yǔ)句 15Watchpoint-SLAD 16Smartforms的debug 17DebuggingSmartformsandSAPScriptinABAP 181)DEBUGSmartforms 182)DEBUGSAPScript 21DebuggingtipsforSAPSmartFormsdocuments 22SmartForms 22DebuggingTips 22SmartForms–FunctionModuleNames 22SmartForms-ProgramNames 23WhereSAPstoresyourABAPCodeinSmartForms 23SettingBreakpointsintheABAPDebugger 23Conclusion 24Note: 24SAPscript、Smartform區(qū)別/調(diào)試方法 25DebugIDOC 25HowtodebuganIDOC 28Purpose 28Overview 28Step1-

DisplayIDOCwitherrorintransactionWE02 28Step2-

View

PartnerprofilesintransactionWE20 30Step3-

SetbreakpointonIDOC_INPUT_INVOIC_MRMandotherrelevantfunctionmodules

forissueconcernedviaSE37 33Step

4-UsetransactionBD87todebug

IDOCconcerned. 34修改IDOC并重新傳送 35DebuganOutboundidoc 37

直接在程序中設(shè)斷點(diǎn)這種方式想必大家都知道了，在se38里面打上breakpoint,程序運(yùn)行到該處即進(jìn)入debug模式

BackgroundJob的Debug進(jìn)入SM37查找到自己想要debug的后臺(tái)程序，這里運(yùn)行完畢或者正在運(yùn)行的均可進(jìn)入debug查找到后打中job前面的勾然后在控制框輸入JDBG回車(chē)，即進(jìn)入debug

在程序運(yùn)行界面進(jìn)入Debug在程序的控制框輸入/H并回車(chē)，接著繼續(xù)運(yùn)行程序的時(shí)候就會(huì)進(jìn)入debug

正在運(yùn)行的程序debug進(jìn)入sm50找到需要進(jìn)入debug的process然后點(diǎn)工具欄Program/Mode->program->debuging即可進(jìn)入Debug

CallFunctioninUpdateTaske的debug

我們?cè)趗pdatetask的function里面設(shè)斷點(diǎn)的話(huà)正常是進(jìn)不去debug的我們?cè)赿ebugger里面路徑setting->Display/changedebuggersettings這里面會(huì)有updatedebugging

選上以后我們運(yùn)行到updatetask的function后會(huì)自動(dòng)開(kāi)辟新的session進(jìn)行debug

SM13ErrorMessageDebug

有些時(shí)候我們?cè)诔绦蜻\(yùn)行的時(shí)候會(huì)報(bào)一些update的errormessage

進(jìn)入sm13可以找到相應(yīng)的item就可以進(jìn)行debug雙擊我們需要的debug進(jìn)去有個(gè)debug的按鈕就可以進(jìn)去debug了

RFCDebug

在RFC所在系統(tǒng)用RFC連接所用的用戶(hù)賬號(hào)去設(shè)斷點(diǎn)然后再進(jìn)行debug就可以了

針對(duì)彈窗的DEBUG方法1,可能有時(shí)候我們程序運(yùn)行過(guò)程中會(huì)出現(xiàn)一些彈出窗口沒(méi)有輸入/H的地方，但是我們要debug怎么辦？新建一個(gè)txt文檔內(nèi)容如下，當(dāng)我們需要debug某個(gè)窗口的時(shí)候直接把這個(gè)txt文檔拖入對(duì)應(yīng)窗口即可實(shí)現(xiàn)debug[FUNCTION]Command=/HTitle=DebuggerType=SystemCommand方法2,

保存到桌面

打開(kāi)這個(gè)彈出窗口的界面之后，然后在桌面雙擊剛才保存的，就可以進(jìn)入相應(yīng)的command（剛才的是debug）界面。

SE16/SE16N修改表內(nèi)容

SE16IlearnedthisABAPdebuggingtricktoadd,edit,deleteorupdateatablerecordduringmystayinmypreviouscompany.Thistrickwillworkaslongasyouhavetheauthorizationtoforcevalueintovariablesduringdebugging,which,usuallyanABAPerwillhaveinDevelopmentorQASserver.Let’sgointoSE16.TakeSalesOrdertableVBAKforexample.Doubleclickanylineandgoesintothedetailssinglerecordview,type/handhitentertwice.ThevariableCODEwasoriginallyhavingavalueof‘SHOW’.Youcaneditthevalueofthevariableto‘EDIT’,‘INSR’,‘DELE’and‘ANVO’.Thenameofthevalueisquiteselfexplanatory,ANVOisforeditingtherecordincludingthekeys(whichI’veneverused).HitF8andthere,you’reintheEDITmode.RemembertohittheSavebuttonwhenyou’redonethou.It’susefultousethistrickwhenyou’retryingtomaintainatablewhenyoucan’tuseSM30todoit.ThisisoneofmyfavouriteABAPtrick

原理：LSETBF01在里面的代碼設(shè)定斷點(diǎn)通過(guò)對(duì)SE16debug修改某條數(shù)據(jù)（這個(gè)方法比較靠譜）：（這個(gè)方法和SM30一樣只能修改非key值的字段）查看到對(duì)應(yīng)SO單號(hào)數(shù)據(jù)后，運(yùn)行事務(wù)碼‘/h’進(jìn)去debug狀態(tài)，然后雙擊對(duì)應(yīng)的數(shù)據(jù)行。但是這個(gè)方法我一直都找不到那段代碼，經(jīng)常是每次進(jìn)去哦都市不同的代碼，很難找到對(duì)應(yīng)的代碼。然后我就根據(jù)以往的成功經(jīng)驗(yàn)，找到了對(duì)應(yīng)的程序：

LSETBF01

在里面的代碼設(shè)定斷點(diǎn)。

然后去runse16，但是不是雙擊，是點(diǎn)擊查看：

就可以進(jìn)入代碼部分：

SE16NInSAPECC6.0EHP6,thefunctioncode&SAP_EDIT,whichenablesthechangemodeoftransactionSE16N,isdeactivated(SAPNote1420281)duetosecuritybreachesthatweredetected.Inordertoactivateit(temporarily),followthestepsbelow:GotoSE16N,asusual,andtypethetableforwhichyouwanttomakemodifications.Insteadoftyping&SAP_EDITinthecommandfield,type/Handpress“Enter”keytoactivatedebugging.PressF8keytoenterthedatabrowserfortheabovetable.IfyouareusingEHP6,thenyoumayneedtopressF7forseveraltimestoreachtotheScreen100ofprogramSAPLSE16NWhileindebuggingmode&onceyouareinScreen100,enterthetwovariablesGD-EDITandGD-SAPEDITandpress“Enter”key.Foreachvariable,clickonthechangebutton,changethevaluetoanuppercase“X”andpress“Enter”key.PressF8keytoexitdebuggingandenterthetableinchangemode.HereishowtheEntrytobechangedinthedebugmode.Pleasebecarefulwhileusingthistrick.Cheers,BharatBajaj

修改Debug模式為經(jīng)典/新SE38選擇一個(gè)程序進(jìn)入

經(jīng)典界面

新界面

SAPscript的Debug

Doyoueverfindyourselfworkingontransactioncodesthathavemultipleoutputformsandneedtomakechangestomultipleformssimultaneously?Trythesesuggestions.Onewaytostartthescriptdebuggeris:Se71->utilities->activatedebugger.

Thismaybeatime-consumingprocess.Instead,openasessionandexecutetheprogramRSTXDBUG.Evenifyoufollowtheabovemenupathtoactivatethescript,itwillinternallyexecutetheprogramRSTXDBUG.Soyouaresavingsometimeingoingthroughalloftheaboveprocesses.Anotheradvantageofusingthisprogram:whenadeveloperworksinthesupportenvironmentandtheclientrequeststomakessomechangestoaform,butdoesn'tknowwhichform,hecanjustshowtheformoutputandrequestforchanges.Example:TransactionCodeHRBEN0001.Thiscontainsaconfirmationform,benefitsformandothers.Inthisscenario,justopentheothersessionandruntheprogramRSTXDBUGprogram,clickapushbuttononthetransactioncodeandifaformisassociatedwiththatbuttonitisautomaticallyopenedindebugmode.Oncetheformisindebugmodeyoucanfindtheformnamethenopenonemoresessionandmakethechangestotheformwhiledebuggingit.

使用StepSize條件斷點(diǎn)，例如在一個(gè)內(nèi)表數(shù)據(jù)非常大的時(shí)候，而我需要的數(shù)據(jù)是1000條里面的第670條，在loop里面就可以設(shè)置一個(gè)條件斷點(diǎn)：

然后直接F8就進(jìn)入第18條數(shù)據(jù)。Debug返回已經(jīng)執(zhí)行過(guò)的語(yǔ)句debug過(guò)程中，當(dāng)手快跳過(guò)了某條語(yǔ)句，可以直接返回到之前的語(yǔ)句：

Watchpoint-SLAD設(shè)置watchpoint，就是前面說(shuō)的，watchpoint只有對(duì)當(dāng)前程序的變量才可以設(shè)置，不可以對(duì)call的function里面的變量進(jìn)行設(shè)watchpoint。但是我們可以利用SLAD實(shí)現(xiàn)這個(gè)功能。

Smartforms的debug可以通過(guò)FM：SSF_FUNCTION_MODULE_NAME設(shè)斷點(diǎn)，然后通過(guò)打印預(yù)覽進(jìn)入之后可以準(zhǔn)確的查看到使用的是那個(gè)smartforms（有時(shí)通過(guò)nace查看的不一定就是打印使用的form）

DebuggingSmartformsandSAPScriptinABAP

Itisoftenrequiredtodebugthemassprintingforms,tochecktoaccuracyorlocate/correcttheerror.BothSAPScriptandSmartformshavedifferentwaysfordebugging.Letslookatthestepsforeachdebeggingoptions.1)DEBUGSmartformsa)UseT-CodeSFTRACE–UsingtheSmartFormtrace,youcantracehowaSmartFormwasprocessedduringprinting.Youcanthensee,forexample,thesequenceinwhichthenodeswererunorthepointatwhichprocessingterminatedduetoanerror.b)HardcodetheBREAK-POINT:WejusthavetoputtheBREAK-POINTstatementwhereeverwewanttostopthecodeandlookinsideinDebugger.c)BreakpointusingBREAKuser-name:Wecanputthebreakpointusingthestatmentusernameadditiontothebreakcommand,forexampleBREAKNAVEEN.ThesebreakpointswouldnotstopanyotheruserswhowouldrunthisSmartform.d)Breakpointonthefly:Toputabreakpointonthefly,wecanfollowthesesimplestepstoputabreakpointasrequired.Step1:OpenyourSmartformandCopythetextaswhichyouwanttoputabreakpointandpresstheTestButton.ItwillbringyoutheFunctionBuilder.SAPScriptDebuggingstep1Step2:Pressthedisplaybuttontoopenthecodeofthefunction.SAPScriptDebuggingstep2Step3:PresstheFind(control+F)button.SAPScriptDebuggingstep3Step4:Inthefindscreen,pastethecopiedtext(control+V)intheText.Selecttheoption“InmainProgram”P(pán)ressEnterSAPScriptDebuggingstep4Step5:Fromthehitlist,gotothesourcecodebydoingdoubleclickonthesearchresults.Now,putaCursoronthelineandpressthe“SetBreakpoint”button.SAPScriptDebuggingstep5That’sit.So,whenyouruntheapplicationitwillstoptothisbreakpoint.SAPScriptDebuggingstep6

2)DEBUGSAPScriptTheyaretwowaystodebugtheSAPScript.a).UseTools–>WordProcessing–>LayoutSet(SE71).EnternameoflayoutsetandthenUtilities–>ActivateDebugger.ActivateSAPScriptDebuggerItisofnoconsequencewhichlayoutsetyouenterwhenselectingtheSAPscriptdebugger.(Menupath:Tools–>Wordprocessing–>Forms,Utilities–>ActivateDebugger)Thenextlayoutsetcalledwillinvokethedebugger.b).AnotherwaytosettheSAPScriptdebuggeristorunprogramRSTXDBUG.WhenyoudebugPrintprogramitissameasyoudebuganyotherABAPprogram.WhilewhenyoudebugSAPScript,youactuallydebugthecode(scripting)youhavewrittenSAPScriptForm.

DebuggingtipsforSAPSmartFormsdocuments

IfyouarenotfamiliarwiththeABAPdebuggerorifyouarejustgettingstartedusingit,thenyoumightfinditchallengingtolocatetheABAPcodethatyouhavewritteninyourSmartFormsdocuments.

ThepurposeofthisarticleistoprovidesomeinformationandafewtipsonusingthedebuggertohelptroubleshootproblemsintheABAPcodeinSmartFormsdocuments.

SmartForms

TherearemanyadvantagestousingSmartFormsovertraditionalSAPScriptsforyourSAPdocuments.Whiletheinterfacemakesiteasiertodesignandimplementtheoveralllayoutofthedocument,youalsohavetheabilitytoincorporateABAPcodeatstrategicplacesrightintheSmartFormwithouthavingtomodifytheprintprogram.

However,therearetimeswhenyouneedtodebugtheABAPcodethatyouhavewrittenwithinyourSmartFormsdocument.

DebuggingTips

ThosewhohaveusedtheABAPdebuggerknowthatitcansometimesbedifficulttofindthespecificlinesofcodethatyouarelookingfor.Infact,itcansometimesbelikelookingforaneedleinahaystack.Attheveryleast,youcanspendasignificantamountoftimesteppingthroughlayerafterlayerofprograms,includesandfunctionmodules.

However,byknowingafewsimpletipsyoucanstopdocumentprintingatjusttherightlocationsothatyoucanfindanddebugtheABAPcodethatyouhavewritteninyourSmartFormsdocument.

SmartForms–FunctionModuleNames

Firstofall,itisimportanttorealizethatallSmartFormsdocumentsarecompiledintotheirfinalrun-timeprogramswhentheyareactivated.SAPdynamicallycreatesauniqueprogramnamewithassociatedincludesandfunctionmoduleswhentheSmartFormisactivated.

WhileinyourSmartFormsdocumentgotothemenuoptionEnvironment–>FunctionModuleName.ThereyouwillfindthefunctionmodulenamethatSAPcreatedforyourSmartFormsdocument.Thenameofthefunctionmodulewilllooksomethinglike:/1BCDWB/SF00000015.

SmartForms-ProgramNames

ThenextstepistofindthenameoftheSmartFormsprogramnamewhichcanbedonebyusingtransactioncodeSE37–FunctionBuilderandenteringtheFunctionModuleNamethatyoufoundinthepreviousstep.

GototheAttributesTabandthereyouwillfindtheprogramnamewhichlookssomethinglikethis:/1BCDWB/SAPLSF00000015.NoticethatthewordSAPhasbeenaddedtotheFunctionModuleNametocreatetheProgramName.

WhereSAPstoresyourABAPCodeinSmartForms

TofindtheABAPcodethatyouhavewritteninsideyourSmartFormsdocumentsimplydouble-clickontheprogramnamewhichwilltakeyouinsidetheprogram.Thereyouwillseeseveralincludestatementsintwodifferentsections:1.System-definedInclude-files/1BCDWB/LSF00000015TOP"GlobalData/1BCDWB/LSF00000015UXX"FunctionModules2.User-definedInclude-files/1BCDWB/LSF00000015F01"UserCode

YourABAPcodewillbefoundwithinaFORMwithneartheendoftheUser-definedInclude-files/1BCDWB/LSF00000015F01.AdifferentFORMisgeneratedforeachsectionofcodethatyouhavewrittenintheSmartFormsdocument.EachFORMnameisgeneratedwiththeformat%C##.ForexampleyourABAPcodewillbelocatedinaFORMthatisnamed%C01,%C02,C03andsoforth.

SettingBreakpointsintheABAPDebugger

NowthatyouknowwheretofindyourABAPcodeintheSmartFormsgeneratedprogramsyouarereadytogetstartedusingtheABAPDebugger.YoucanstartbycreatinganoutputforyourSmartFormsdocument.Atthispointjustbeforesavingthedocumentwiththenewoutput,simplyenter/handpressexecute.Thiswillactivatethedebuggerwhichwillpop-upaftersavingthedocument.

Note:IfyouhappentoactivatethedebuggerbeforethedocumentissavedthenthedebuggerwillstartplacingyouintheABAPcodebeforethedocumentsavecodebeginsandnotwherethedocumentprintingbegins.IfthishappensthensimplypresstheContinuebuttonsothatitwilljumppastthedocumentsavecodeandstopagainwherethedocumentprintcodebegins.Ifthedocumentprintswithoutthedebuggerstoppingatthedocumentprintcodethenyouwillhavetobeginagain.

OncethedebuggerstartsyoucanquicklysetabreakpointusingtheProgramNameandtheUser-IncludefilesothatthedebuggerwillstopexactlyatthepointwhereyourABAPcodeislocatedintheSmartFormsdocument.

UsethemenupathBreakpoints–>Breakpointat–>SourceCodeandentertheProgramNameandIncludefilenameyoufoundearlier.YouwillalsoneedtoentertheprogramlineintheRowfieldinordertospecifytheexactlocationwhereyouwantthedebuggertostop.ProgramName:/1BCDWB/SAPLSF00000015Include:/1BCDWB/LSF00000015F01Row:####-"Linenumberofyourcodewhereitappearsintheincludefile

Onceyouhavethebreakpointset,presstheContinuebutton.ThiswillstoptheSmartFormexecutionattheexactpointwhereyouwanttostartdebuggingyouABAPcode.Atthispointyoucancheckvaluesofvariables,lookattablecontentsandstepthroughyourABAPcodetofindoutwhereproblemsexist.

Conclusion

WithoutknowingafewbasictipsabouthowtofindyourABAPcodeinaSmartFormsdocument,youcanspendalotoftimesteppingthroughstandardABAPcodeinSAP.Whileobjectorientedcodehaschangedtheworldofprogramming,itcanalsopresentchallengeswhenyoudon’tknowwheretolooktofindthespecificcodethatyouwanttotroubleshoot.

Note:TheProgramNameandtheIncludeFilenamesofyourSmartFormsdocumentwillbedifferentineachsysteminyourSAPlandscapesincetheywillbedynamicallyrecreatedwhentheyaretransportedtoeachsystem.Therefore,ifyouwanttousethedebuggeronthesameSmartFormsdocumentbutinadifferentSAPsystem,youwillhavetolookuptheProgramNameandIncludefilesnamesinthatsystem.

SAPscript、Smartform區(qū)別/調(diào)試方法

1,smartform在激活的時(shí)候會(huì)自動(dòng)地創(chuàng)建一個(gè)功能模塊,而SAPscript則不會(huì);2,smartform可以直接書(shū)寫(xiě)子程序,使用"ProgramLine"節(jié)點(diǎn),而SAPscript則只能使用控制命令語(yǔ)句PERFORM調(diào)用subroutine;3,SAPscript是基于client的,而smartform不區(qū)分在任何client;4,smartform的字體可以應(yīng)用color,而SAPscript則不能;5,SAPscript的每個(gè)page都只能統(tǒng)一按照橫向和豎向頁(yè)面格式,而smartform則可以不統(tǒng)一格式;

下面我講一下，它們的DEBUG，這個(gè)屬于沒(méi)用的時(shí)候很沒(méi)用，有用的時(shí)候很有用的東西。SAPScript:T-codese71->Utilities->ActivateDebugger這樣就可以DebugForm，如果在出問(wèn)題的字段‘WRITEFORM’加上斷點(diǎn)，效率會(huì)更高。SMARTFORM:T-codeSMARTFORMS如果你在SMARTFORM中加了代碼，編輯器是不會(huì)允許你設(shè)置斷點(diǎn)的。一種方法就是，你在代碼中加入斷點(diǎn)語(yǔ)句，缺點(diǎn)是，每想設(shè)一個(gè)斷點(diǎn)，就需要寫(xiě)一段代碼。所以，我要說(shuō)一下，后一種方法。

你自己加的CODE，都會(huì)自帶出一個(gè)名字的比如‘%code14’。Environment->FunctionModuleName，Thefunctionthatgeneratedforthissmartformsis‘/1BCDWB/SF00000227’（自動(dòng)生成的SMARTFORM程序名）T-codese37->/1BCDWB/SF00000227->Goto->MainProgram最后一個(gè)INCLUDE是對(duì)DEBUG最有用的，雙擊進(jìn)入用‘FIND’去找你要Debug的代碼，F(xiàn)ind中的關(guān)鍵字是‘%code14’

DebugIDOCWE02查看MessageTypeWE20找到MessageType

雙擊MessageType雙擊ProcessCode

找到對(duì)應(yīng)的Functionmodule：IDOC_INPUT_ORDRSPSE37調(diào)試（或者直接雙擊functionmodule），添加斷點(diǎn)/watchpoint等調(diào)試

HowtodebuganIDOCPurposeThiswikiprovidesademonstration

ofhowtodebuganIDOC.OverviewThe

IDOC

giveninthis

exampleisbasedon

invoiceinmaterialsmanagement

onatestsystem.Step1-

DisplayIDOCwitherrorintransactionWE02DoubleclickontheControlRecord.ViewinformationontabTypinfo:

SelecttabPartner.

ForinboundprocessingchecktheSenderinformation..Step2-

View

PartnerprofilesintransactionWE20Usingtheinformationfromstep1:PartnertypeLI,PartnerNumberCP-CP01,MessagetypeINVOIC,MessageVariantMMIntransactionWE20Openfolderfor

PartnerTypeLIDoubleclickonpartnernumberCP-CP01

Intheinboundparameters,doubleclickonMessagetypeINVOIC(MessagevariantMM)Double

clickonProcesscode

Hereyoufindthefunctioncodeidentification,inthisinstanceIDOC_INPUT_INVOIC_MRMStep3-

SetbreakpointonIDOC_INPUT_INVOIC_MRMandotherrelevantfunctionmodules

forissueconcernedviaSE37

Step

4-UsetransactionBD87todebug

IDOCconcerned.IntransactionBD87enterconcernedIDOCandexecute.

SelectButtonProcess(F8).Yhisexampleon

functionmoduleIDOC_INPUT_INVOIC_MRM

UseF8

togototheother

relevantBreakpointsyouhaveset.

修改IDOC并重新傳送WE02查找出錯(cuò)的IDOC雙擊文本圖標(biāo)

修改后保存，然后BD87重新傳送

DebuganOutboundidocManytimeswegets

issuesfordebuggingof

IdocwhichusedtobeinerrorstateThisdocumentwillhelpyouinunderstandthesteps

indebuggingofOutboundidocDebuggingofOutboundidocTheoutboundidocistheonewhichweusetosendfromonesystemtoanothersystemanditbecomesinboundidocforthetargetsystem

fromour

sendersystem.Wheneveryougetsanyidocwitherror,gotoWE02andentertheidocnumber.bydefaultsystemgivescurrentdatesremovecreationdate,systemwillidentifyidocbyjustidocnumberonexecutingit,youwillgetthedetailsofidoc

likethreesections.1.Firstoneiscontrolrecordwhich

containtheinformationofcreatorofidoc,whoisthesender,whoisreceiverlikealltheseidocadministrationdetails.2.SecondsectionisDhis,therewillbesomanysegmentslikeE1EDK01,E1EDP01

etc.Thefirstdatarecordcontainsthedocumentnumberwhoseinformationcameandappearingindifferentdifferentsegments.3.Thirdsectionwillbestatusrecrdanditwillcontainsallthestatuslikeidocprocessedsuccessfully(53status,s