BestPractice:SAPWorkflowMonitoring

SAP Workflow Monitoring

Best Practice for Solution Management
VersionDate:July2007 ThenewestversionofthisBestPracticecanbe obtainedthroughtheSAPSolutionManager
Contents 1 Introduction .............................................................................................................................3 Applicability,GoalsandRequirement.................................................................................3 PreliminaryInformation......................................................................................................5 2 SAPWorkflowFunctionality.....................................................................................................7 3 SAPWorkflowMonitoringandAnalysis .................................................................................10 3.1 SAPWorkflowlog............................................................................................................10 3.2 MonitoringandAnalysisTools..........................................................................................16 3.2.1 BacklogMonitoringandAnalysis..............................................................................19 3.2.1.1 TransactionSWI1SelectionreportforSAPWorkflows ...................................19 3.2.1.2 TransactionSWI2_FREQ WorkItemsperTask ..............................................23 3.2.1.3 TransactionSWI2_ADM1 WorkItemsWithoutAgents....................................26 3.2.1.4 TransactionSWI6SAPWorkflowsforObject .................................................29 3.2.2 ErrorMonitoringandAnalysis...................................................................................32 3.2.2.1 TransactionSWI2_DIAGDiagnosisofSAPWorkflowswitherrors..................33 3.2.2.2 TransactionSWUDSAPWorkflowDiagnosis.................................................34 3.2.2.3 TransactionSM58tRFCMonitor....................................................................42 3.2.2.4 TransactionSWPRRestartSAPWorkflow.....................................................44 3.2.2.5 TransactionSWPCContinueSAPWorkflow ..................................................44 3.2.2.6 TransactionPFTC GeneralTaskMaintenance ..............................................45 3.2.2.7 TransactionSWDD SAPWorkflowBuilder ....................................................47 3.2.2.8 TransactionSWO1BusinessObjectBuilder..................................................47 3.2.2.9 TransactionSWEQADMEventQueueAdministration ....................................49 3.2.2.10 TransactionSM37SAPWorkflowrelatedJobMonitoring .............................50 3.2.2.11 Errorhandlingroadmap ..................................................................................50 3.2.3 PerformanceMonitoringandAnalysis ......................................................................52 3.2.3.1 TransactionSWI5 Workloadanalysis ............................................................52 3.2.3.2 TransactionST03(ST03N) WorkloadMonitor ................................................56 3.2.3.3 TransactionSTADStatisticalRecords ............................................................57 3.2.3.4 TransactionST12SingleTransactionAnalysis ...............................................58 3.2.4 ResourceMonitoring................................................................................................59 3.2.4.1 TransactionSMQSQoutScheduler ...............................................................59 3.2.5 FurtherInformation ..................................................................................................60 3.2.5.1 Troubleshooting...............................................................................................60 3.2.5.2 Literature.........................................................................................................60 1.1 1.2

BestPractice:SAPWorkflowMonitoring

3.2.5.3 BackgroundInformationandReferences .........................................................60 3.2.5.4 FeedbackandQuestions .................................................................................60 3.2.6 APPENDIX:WorkItemArchiving..............................................................................61 3.2.6.1 TransactionSWW_SARA ................................................................................61

2007SAPAG

BestPractice:SAPWorkflowMonitoring

1 Introduction
1.1 Applicability, Goals and Requirement
ThisBestPracticegivesanoverviewonSAPWorkflow monitoring,themaintoolsandtheirfunctions. ThisenableseachresponsibleteamtomonitorSAPWorkflowsoptimally,accordingtotheir responsibilities. ThisBestPracticedescribestheSAPWorkflow monitoringactivities,whichshouldbecarriedoutina particularproductiveenvironmentandonacontinuous/permanentbasis.Therefore,thisBestPractice willnottakeintoaccountcustomizingactivitiesthatareconsideredalreadycomplete. InordertoensuregoodperformanceoftheentireSAPsystem,youshouldtakeintoconsiderationthat creatingmanySAPWorkflowlogscancausetheSAPWorkflowrelatedtablestogrowsignificantlyin thedatabase.Intheappendixyouwillfindrecommendationsonhowtoarchiveworkitems. ThisBestPracticedocumentconsistsofthefollowingsections:
Section1Introduction
Thissectionexplainsthepurposeofthisdocument.

Section2SAPWorkflowFunctionality
ThissectiongivesyouashortintroductiontoSAPWorkflow.

Section3SAPWorkflowMonitoringandAnalysis
Thisisthemainsection,whichintroducestoyouvarioustoolstomonitorSAPWorkflowand analyzeerrorseffectively: o SAPWorkflow log SAPWorkflow logcontainsalltheimportantdataforadministrationandmonitoringof anSAPWorkflow.TheSAPWorkflowlogisthebesttoolavailableforgettingan overviewofanSAPWorkflow instanceandanalyzingit. Differenttransactionsareexplainedindetailinthesection3.2MonitoringandAnalysisTools. BacklogMonitoringandAnalysis WorkItemMonitoringenablesyoutodisplayWorkItems.Youcanseehowmany WorkItemsareexecutedpertypeortask. o ErrorMonitoringandAnalysis Inthissection,youwillfindvarioustoolstoanalyzeerrorsandalsotorestart erroneousItems. o PerformanceMonitoringandAnalysis ThetransactionsexplainedherewillhelpyoutoevaluateSAPWorkflowperformance andinvestigateaperformancebottleneck. o ResourceMonitoring Withresourcemonitoring,youcanensureifenoughresourcesareavailableto executeSAPWorkflow.

Section4FurtherInformation
Additionalinformationisprovided.

Appendix: WorkItemArchiving
WorkItemArchivingismentionedhere.Manyperformanceissuescanbecausedbythefact thatSAPWorkflowitemsarenotarchived.

GoalofUsingthisService
TheSAPWorkflowanditsfunctionsoftenplayacentralroleintheSAPsystems.Torunanoperation withouterrorsanddelays,itisimportantthatallprocessstepsintheSAPWorkflowaremonitored. SAPWorkflow monitoringensuresthatthebusinessprocessesruninasmoothandreliableway.This

BestPractice:SAPWorkflowMonitoring BestPracticedocumentationsupportstheimplementationofSAPWorkflowmonitoringandthe developmentoftheSAPWorkflow monitoringconcept.

AlternativePractices
YoucanhaveSAPexpertsdeliverthisBestPracticeonsitebyorderingaSolutionManagement Optimization(SMO)serviceforSAPInterfaceManagement.Thisserviceisexclusivelyavailablewithin anSAPSupportEngagement(thatis,SAPMaxAttention,SAPSafeguardingorSAPPremium Support).

StaffandSkillsRequirements
SystemandSAPWorkflowadministratorsandotherpersonsresponsibleforSAPWorkflow managementmakeupthetargetgroupforthisdocument.ItisnecessarytospecifyanSAPWorkflow administrator.ThisadministratormonitorsthebusinessSAPWorkflowsandensuresundisturbed operation.TheresponsibilitiesanddifferenttasksmustbedefinedinanSAPWorkflowmonitoring concept. ToimplementthisBestPractice,yourequirethefollowingteams: ApplicationManagementTeam Thisteamprovidestheinformationonthebusinessbackgroundoftheinterfacesusedandknowsthe businessrequirementsfortheinterfaces: Businessdepartment Solutionsupportorganization(forexampletheBasisSupportortheApplicationSupport) Implementationprojectteam

BusinessProcessOperationsTeam TheBusinessProcessOperationsteamwillberesponsibleforapplyingtheresultingprocedures derivedfromimplementingthisbestpractice.Theyincludethefollowinggroups: Personsdesignatedtoperformbusinessprocessorientedmonitoringandensurethatthe processrunssmoothly(forexample,theBusinessProcessChampionforeachbusiness process) AllpartiesinyourSolutionSupportOrganizationandITdepartmentinvolvedinmonitoring focusedontheapplicationaspects(ApplicationSupport,DevelopmentSupport,Program SchedulingManagement)

SAPTechnologyOperationsTeam AllpartiesinyourSolutionSupportOrganizationandITdepartmentinvolvedinmonitoring focusedonthesystemadministrationside(ProgramSchedulingManagement,Software MonitoringTeam,SystemAdministrationTeamincludingtheSystemAdministrator)

BusinessProcessChampion TheBusinessProcessChampionisthepersoninthebusinessdepartmentthatisresponsible forthesuccessfulexecutionofthebusinessprocess.He/shecoordinatesallactivities necessaryforthebusinessprocess.Therefore,he/sheisusuallyresponsibleforthe escalationpathsincaseofproblems. Thebusinessprocesschampionisoftenasecondlevel intheescalationprocedure,iftheapplicationmonitoringteamneedstoescalateanissue.

NecessaryorUsefulTrainings
q q q q q

BIT600SAPBusinessSAPWorkflow BIT601SAPBusinessSAPWorkflowBuildandUse BIT603SAPBusinessSAPWorkflowandWebScenarios BIT610SAPBusinessSAPWorkflowProgramming ADM105 AdvancedR/3SystemAdministration

2007SAPAG

BestPractice:SAPWorkflowMonitoring
q

ADM315WorkloadAnalysis

SystemRequirements
TheinformationinthisdocumentreferstoreleasesSAPR/3Enterprise4.70andhigher.Forsystem access,usetheSAPGUI.

DurationandTiming
SAPWorkflow monitoringshouldbecarriedoutinallpartsofthebusinessprocesswhichuseSAP Workflow.Monitoringshouldbecarriedoutatleastonceperday,dependingonusageofSAP Workflows.

1.2 Preliminary Information

ThereareseveralwaysofdefiningSAPWorkflows: AnSAPWorkflowistheautomationofabusinessprocess,duringwhichdocuments,informationor tasksarepassedfromoneparticipanttoanotherforactions,accordingtoasetofproceduralrules. SAPWorkflowslinkseparatebusinesstaskstogetherintoabusinessprocess.TheSAPWorkflow suppliestherightinformation,attherighttime,totherightpeople,distributingtheworkaccordingto businessrules. Thefollowingsuppliesanothermorecommondefinition: AnSAPWorkflowisthecomputersupportedmodelingandexecutionofabusinessprocess.AnSAP WorkflowManagementSystemisacomputersystem,whichcandefine,performandmonitorSAP Workflows.ThesedescriptionsarebasedontheSAPWorkflowManagementCoalition(WFMC) definition.TheWFMCisanoncommercialorganization,whichstandardizesandencouragestheuse ofSAPWorkflowsystems.SAPparticipatesintheWFMC. TheuseofSAPWorkflowwithinbusinessprocessesreturnsdifferentbenefits.TheSAPWorkflow ManagementSystemsimprovethecommunicationbetweenprocessorsthroughintegrationina mailingsystem.ThesystemdeterminestheprocessorofanSAP Workflowactivitybyspecifiedrules (competences)andassignseachactivitytotheappropriateprocessor.SAPWorkflowsallow monitoringdeadlinestoensurethateachactivityisperformedwithinitsdeadlineandusestatistical functionstoanalyzeprocessorandgroupworkloadandefficiency. Asasimpleexample,wecoulduseanapprovalprocedureusinganSAP WorkflowManagement Systemforamaterialrequirementrequest.Thefollowingfigureshowsthegraphicalpresentationof thisprocess.ThefollowingexplainstheprocessstepsinvolvedandthepersonsbelongingtothisSAP Workflow.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

Figur e1Approvalprocedureforamaterialrequirementrequest Anemployeecreatesamaterialrequirementrequest,thusstartinganSAP Workflow.Thematerial requirementrequestispresentedelectronicallytotheemployeessuperiorforapproval.Themanager canapproveorrejecttherequest.Shouldapprovalbegiven,theemployeeisinformed.Theremaybe subsequentsteps(forexample,createapurchaseorderandsendittoasupplier). Ifthemanagerrejectedtherequest,theemployeeisinformedandcandecidewhethertoreviseor abandontherequest.Theemployeecanabandontherequest,atwhichpointthematerialrequirement requestisdeletedinthesystemandtheSAPWorkflowends.Iftheemployeedecidestorevisethe request,therequestchangefunctionisofferedinthenextstep,andthechangedmaterialrequirement requestisresubmittedtohisorhermanagerforapproval.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

2 SAP Workflow Functionality

AnSAP Workflowisasequenceofsteps,whichareprocessedeitherbypeopleorbythesystem. SAPWorkflowlinkstogetherseparatebusinesstasksintoabusinessprocess.Itprovidesanactive flowofinformation: Supplytherightinformation,attherighttime,totherightpeople Distributionofworkaccordingtobusinessrules Exceptionhandlinganddeadlinemonitoring

FivequestionsforeverypartofanSAPBusinessSAPWorkflowprocessare: What? When? Inwhatorder? How? Who?

SAPWorkflowsarewidelyusedtoautomatedifferentbusinessprocesses.Forexample,SAP Workflowwasusedtoautomatetheroutineadministrativeprocedureofnewusercreation.Itincludes thecreationofanewuserrequestandchanginguserslogondata. SAPBusinessSAPWorkflowliesonanintegrationlevelabovethetransaction/applicationlevel.It usesexistingapplicationfunctions(forexample,transactions,reportsandfunctionmodules).These functionsarenotchanged,buttheyarelinkedtoeachotheraccordingtotherequirementsofthe businessprocess. SAPWorkflowterminology: ThefollowingtabledescribesSAPWorkflowterminology.Itgivesanoverviewofthetechnicalobjects, theirdefinitionsandgivesanexample. Theexampleusedistheprocessofpurchaserequisitionfororderingaprinterforanoffice.Thisfigure showsagraphicaloverviewoftheSAPWorkflowterminologyandalltechnicalobjectsinvolvedinSAP Workflowprocess.

Figur e2 OverviewofSAPWorkflow terminologyandtechnicalobjects

2007SAPAG

BestPractice:SAPWorkflowMonitoring Terminology SAPWorkflow definition Definition Thesetofruleswhichdefinethe SAPWorkflowpaths(routes).The routesmaybelinear,parallelor circular(loop). UsuallyonlyreferredtoastheSAP Workflow.IsasingleSAPWorkflow execution. Theseactionsareguidedbythe SAPWorkflow.Tasksarecarried outbyusers(dialogtasks)witha definedroleintheSAPWorkflowor byprograms(backgroundtasks). Ataskinstanceprocessedasa singleSAPWorkflowstep. Personprocessesataskviaawork item. Example

SAPWorkflow instance Task

Themethodofprocessingapurchase requisition.Itincludesthewholeprocess, startingwiththequeryandendingwith creationofthepurchaseorder. Theprocessingofapurchaserequisition foranofficeprinter. Doesaprinteralreadyexistintheoffice?

Workitem Processor

Checktheofficeforexistingprinters. Thepersonwiththerequest,themanager approvestherequest,thememberofthe ITdepartmentandmemberofthe purchasingdepartmentorganisethe delivery Requester,Approver

Roles

Thesedefinethefunctionsofthe personsinvolvedintheSAP Workflow. Thisisthedatacollectionusedin theSAPWorkflow. Thesetofrulesdescribeswhich datawillbesenttowhichprocess steps.

Container Dataflow

Aspecifiedoffice,theorderedprinter Inthepurchaserequisitionprocess,the requireddatais:officeroomnumberand informationabouttheofficeequipment. Dataregardingtherequestorscostcenter isnotnecessary.

Object

Created at runtime and the specific instance of a previously defined object type that has been assigned values

Method(Objecttype component) Attribute(Object typecomponent) Event Step

Theoperationthatcanbeexecuted onanobject The property or characteristic of an object Thestatuschangeofanobjectthat ispublishedthroughoutthesystem The elementary module of an SAP Workflowdefinition

2007SAPAG

BestPractice:SAPWorkflowMonitoring

Figur e3 Abusinesspr ocessSAPWor kflowinanSAPsystem

2007SAPAG

BestPractice:SAPWorkflowMonitoring

10

3 SAP Workflow Monitoring and Analysis

Toensurethesmoothandreliableflowofthebusinessprocesses,itisveryimportanttodefine personsinyoursolutionsupportorganizationthattakecareofmanagementandmonitoringtheSAP Workflows.Therearesomeactivitiesthatshouldbecarriedout,inordertocheckiftheprocesses basedonSAPWorkflowshaveruncompletelywithouterrorsand,incaseoferrors,tofigureoutthe causesofthemandtrytosolvethem. Therefore,shouldsomeSAPWorkflowinstancesnotruncorrectly,theresponsibleteamshould analyzethemtofindwhatgeneratedtheincorrectflow.Thisanalysiscanbecarriedoutthankstoa centraltoolcalledtheSAPWorkflowlog.InthechapteronSAPWorkflowMonitoringand Analysis themaintransactionsareillustratedthatcanhelptofindoutwhichSAPWorkflowinstances areaffectedbyproblemsandhowtoanalyzethem.

3.1 SAP Workflow log

TheSAPWorkflowlogcontainsalltheimportantdataforadministrationandmonitoringofanSAP Workflowandactsasanentrypointforfurtheractivities.TheSAPWorkflowlogisthebesttool availableforgettinganoverviewofanSAP Workflowinstanceandanalyzingit.Itisveryimportantto keepinmindthatanSAP WorkflowlogisautomaticallycreatedbythesystemforeverySAPWorkflow instance,sothatyoudonothavetoswitchonorcustomizeanythinginordertoseeit.OnceanSAP Workflowstarts,differentSAPWorkflowlogsarecreated.TheSAPWorkflowlogputstogetherall informationthatiscreatedorusedduringtheexecutionofthebusinessprocessinacentralplace,the latterbeingidentifiedbytheSAPWorkflowinstance.TheselogscanalsobedisplayedwhilstanSAP Workflowisrunninganduntilitiscompleted.Bymeansoftheselogs,youcanseewhichstepshave alreadybeenprocessedandwhichstepsarestilltobeprocessed. TheSAPWorkflowlogcanbeaccessedbytransactionsexplainedinthefollowingchapterofthis documentordirectlyfromtheworkiteminboxandoutbox(transactionSBWP).Inthenextfigure,the inboxforManager1isdisplayed.Ontherightsideofthenextfigure,allworkitemswithstatusready arelisted.ByclickingonthebuttonDisplaySAPWorkflowlogthesystemshowstheSAPWorkflow logfortheselectedworkitem.

Figur e4 Businesswor kplaceofManager 1

2007SAPAG

BestPractice:SAPWorkflowMonitoring

11

AnSAP Workflowlogcanbedisplayedthroughdifferentviews:TechnicalViewandStandardView. Thedifferenceistheinformationdisplayed. Inthelogs,alldetailsregardingtheSAPWorkflowsaresaved,howevertheycanonlybecompletely displayedinthetechnicalview.

Figur e5 SAPWorkflowlog technicalview ThetechnicalviewwasdesignedforthedevelopersandSAPWorkflowadministrators,sinceit containsthehistoryofanSAP Workflowinstancewithallitssteps(includingalltechnicalinformation) andtherefore,itisthemostusefultoolforsearchingforpossibleerrors. AsourpurposeistodescribethemonitoringactivitiesforanSAP Workflowadministrator,wewillnow describejusttheTechnicalViewinmoredetail. ThegeneralinformationabouttheSAPWorkflowinstanceisshownintheupperpartofthescreen: theSAPWorkflowname,theSAPWorkflowinstance,theinstancenumberorworkitemID,thestart dateandtime,startedbyandthecurrentstatus.Inthebodyofthetechnicalview,youfindthe chronologyoftheSAPWorkflowinstance.Itappearsasagraphicaltablewithtwolevelsandshows allthestepsoftheSAPWorkflowinstanceinachronologicalorder. Hereisashortintroductiononhowtointerpretthistable.Thefirstlevelofthegraphicaltable correspondstothefirstheaderlineofthetable.Lineitemswhichbelongtothefirstlevelofthetable aremarkedwitharrowsbinthenextfigure.ThefirstlineitemrepresentsthestartoftheSAP Workflowinstance,thelineitemsthatfollowrepresentitstaskstheymaybestepsofthesameSAP WorkfloworstepsofsubSAPWorkflows.Inordertoseeallofthisinformationitmaybenecessaryto scrollleft/rightonthescreen.Onthefirstlevelofthetable,foreachlineitemthetableshows: Anoverallerrorstatusinthecolumnnamederror.Agreentrafficlightappearsifnoerrors occurredinthestep Astatusindicator(columnstatus)thatshowsthestatusoftheworkitem TheworkitemID(columnID) TheSAPWorkflowstepnumber(columnNodeNumber) Thedescriptionofthesteps(columnTask) Theresultofthetasks(columnResult) Theexecutiondate(columnDate) Theexecutiontime(columnTime) Thecurrentprocessingtime(columnProcessingtime) 2007SAPAG

BestPractice:SAPWorkflowMonitoring

12

Figur e6 SAPWorkflowlogin viewwithtechnicaldetails Thesecondlevelofthegraphicaltablecorrespondstothesecondheaderlineofthetable.Lineitems whichbelongtothissecondlevelofthetablearemarkedwitharrowsbinnextfigure. Thelineitems onthesecondtablelevelareonlyvisibleafterexpandingthesecondlevelbyclickingontheicon inthefirstcolumnofthegraphicaltable.Foreachlineitemonthesecondlevelofthetable, thetableshows: Anoverallerrorstatusinthecolumnnamederror.Agreentrafficlightappearsifnoerrors occurredinthestep Theassignedagent(columnAgent) Theexecutedactionwithinthisstep(columnExecutedAction) Theexecutiondate(columnDate) Theexecutiontime(columnTime) Theprocessedobject(columnObject) Thenameoftheprocessedobject(columnObjectname) Theprocessedobject2(columnObject2) Thenameoftheprocessedobject2(columnObjectname2) Thecorrespondingcontextoftheuser(columnUserContext)

2007SAPAG

BestPractice:SAPWorkflowMonitoring

13

Figur e7 SAPWorkflowloginviewwithtechnicaldetails IfanSAP Workflowhasanerrorstatus,youcanseeinthetechnicalview,inwhichsteptheerror occurredandalltheerrormessagesthatwerecreated.Forthisproperty,thetechnicalviewisthe mostsuitableviewfortheinvestigationoftheSAPWorkflowrun. Thetechnicalviewshowstechnicalknotsandcontrolstructuresandoffersadditionaldatafor example,Containerelements ,Agentsdata ,SAPWorkflowdata andgraphicalSAP Workflowlogs .TheStatus ofthesingleworkitemisalsodisplayed.Todisplaythisadditional data,youmustclickonthesymbolsshownabove.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

14

GraphicalSAPWorkflowlog TheGraphicalSAPWorkflowlogshowsthealreadyprocessedstepswithinthegraphoftheSAP Workflowdefinition.Thisisveryuseful,sinceyoucanseethedirectionofaparticularSAPWorkflow instanceataglance(thesystemshowstheprocessoftheSAPWorkflow instancebymeansofa greenlinepleaserefertonextfigureInprintedversions,theprocesslineisfatterthantheotherlines relatedtotheSAPWorkflowdefinition).

Figur e8 SAPWorkflowlogingr aphic

2007SAPAG

BestPractice:SAPWorkflowMonitoring

15

TherearethreepossibilitiesofviewingthegraphicalSAPWorkflowlogifyouareinthetechnicalview: Byclickingonthebutton Byclickingonthesymbol (markedwitharrowa) directlyinthelog(markedwitharrowb)

ByselectingGOTO>GraphicalSAPWorkflowlog(markedwitharrowc)orpressingF9.

However,youwillgetthehighesthierarchylevelifyouchoosepoint(a)or(b)oftheSAPWorkflow instance.Byclickingonsymbol youwillgetthegraphicallogofthe(sub)SAPWorkflow representedinthestepyouwanttoanalyze.

Figur e9 SAPWorkflowloginviewwithtechnicaldetails Itisimportanttoemphasize,thatyoumustselecttheviewwitherrorindicatorsinthemenu(Path: Views>Otherviews>Viewwitherrorindicators,inordertodisplaytheerrors,whichareindicated inthelogwiththesymbol .

2007SAPAG

BestPractice:SAPWorkflowMonitoring

16

Figur e10 SAPWorkflowloginviewwithtechnicaldetails Byclickingontheerrorsymbol,thesystemdisplaysananalysisoftheerrorwhichmaydescribethe causeoftheerror.Youcanaccesstheinformationcontainedinthisanalysis.

Figur e11 Er r ordiagnosisfor aworkitem Bydoubleclickingonaspecifieditem,youcanviewthefull,moretechnicalerrordescription.Inthis technicaldescription,youfindanerrormessagecode(forexample:Messageno.BBP_WFL052).This messagecodeisusefulforsearchingforSAPNotesinordertomanagetheproblem.

3.2 Monitoring and Analysis Tools

Monitoringcanbedoneusingthestandardreportsthatareavailableinthesystem.Theyalsoprovide thepossibilitytousethegeneralreportfunctions,forexample,sorting,filter,layoutchange,etc. AnotherpossibilityistodefinesearchcriteriatorestrictthelistofSAPWorkflowstobemonitored suitably.Forinstance,youcansearchforSAPWorkflowsthatcontainaparticulartask,componentor forSAPWorkflowsstartedinadefinedperiodoftime(today,lastweek,lastmonth,lastyear,all). Ashortoverviewofthemaintransactionsisprovidedhere.Inthefollowingsubsections,wewill explainthelistedtransactionsneededtoviewtheabovementionedreports inmoredetail.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

17

1.WorkItemMonitoring Transaction code SWI1 Shorttext Searchinganddisplaying WorkItemsofalltypes Searchinganddisplaying WorkItemsperTask Searchinganddisplaying WorkItemswithoutagents Searchinganddisplaying WorkItemswithobjecttype Explanation Youcansearchanddisplayworkitemsof alltypesaccordingtovariouscriteriato checkstatus. Youcansearchanddisplayworkitems groupedpertaskanddisplayworkitems ofthesametask. Youcansearchanddisplayworkitems withoutagentstodeterminenextactions. Youcansearchanddisplayworkitems withspecificBusinessObjectinstances andtoanalyzethestatusofSAP Workflow.

SWI2_FREQ

SWI2_ADM1 SWI6

2.ErrorMonitoring,AnalysisandRestarting Transaction code SWI2_DIAG SWUD Shorttext Explanation

ListingWorkItemswitherrors Youcanlistworkitemsbycauseoferror. anddisplayingerrordiagnosis SAPWorkflowDiagnosis YoucanusethistransactionforSAP WorkflowDiagnosiswhichisveryusefulif youdiscoverthataparticularSAP Workflowisnotworkingcorrectly. Youcanmonitorandrestarthanging WorkitemsinthetRFCqueue. YoucanrestartSAPWorkflowsafter error. YoucancontinueSAPWorkflowsthat hangafterasystemcrash. Youcancheckthedefinitionofatask. Youcantracetheflowandinvestigatea specificstep. Youcandisplayandtestanobjectused inSAPWorkflow. Youcanmonitoreventqueue. YoucanmonitorSWW*jobsscheduled byWFBATCH.

SM58 SWPR SWPC PFTC SWDD SWO1 SWEQADM SM37

tRFCmonitor RestartingSAPWorkflow ContinuingSAPWorkflow GeneralTaskMaintenance SAPWorkflowBuilder BusinessObjectBuilder EventQueueAdministration MonitoringSAPWorkflow relatedjobs

2007SAPAG

BestPractice:SAPWorkflowMonitoring

18

3.PerformanceMonitoringandAnalysis Transaction code SWI5 Shorttext WorkloadAnalysis Explanation Youcanestablishtheworkloadof individualorganizationalobjects(users, positions,jobs,workcentersor organizationalunits),usingtheworkload analysis. Youcandisplayinformationonsystem loadfromvariousviewpointsand timeframe. Youcandisplayastatisticalrecordofa singlestep. Youcananalyzeasinglestepusingthe Integratedperformanceanalysistoolwith ABAP(SE30)andPerformanceTrace (ST05).

ST03(ST03N)

WorkloadMonitor

STAD ST12

Statisticalrecord SingleTransactionAnalysis

4.ResourceMonitoring Transaction code SMQS Shorttext QoutScheduler Explanation Youcanmonitorsystemresourcesfor tRFCwithQoutScheduler

2007SAPAG

BestPractice:SAPWorkflowMonitoring

19

3.2.1
Transaction code SWI1

BacklogMonitoringandAnalysis
Shorttext Searchinganddisplaying WorkItemsofalltypes Searchinganddisplaying WorkItemsperTask Searchinganddisplaying WorkItemswithoutagents Searchinganddisplaying WorkItemswithobjecttype Explanation Youcansearchanddisplayworkitemsof alltypesaccordingtovariouscriteriato checkstatus. Youcansearchanddisplayworkitems groupedpertaskanddisplayworkitems ofthesametask. Youcansearchanddisplayworkitems withoutagentstodeterminenextactions. Youcansearchanddisplayworkitems withspecificBusinessObjectinstances andtoanalyzethestatusofSAP Workflow.

WorkItemmonitoring

SWI2_FREQ

SWI2_ADM1 SWI6

3.2.1.1TransactionSWI1SelectionreportforSAPWorkflows
AusefulstepinmonitoringanSAP Workflowistocheckitsstatus.Thebestreportforcarryingout suchacheckisthereportWorkItemSelectiontransactionSWI1.TransactionSWI1allowsthe selectionandviewofalltypesofworkitemsresultingfromthesearchcriteriathathavebeen defined. ThisreportenablestheselectionandtheviewofallkindsofSAPWorkflowsbymeansofdifferent selectioncriteria.ItisparticularlyhelpfulwhensearchingfornonvisibleWorkItems,sincetheyare neitherinwaitingnorinanySAPWorkflowinbox.Moreover,usingthisreportyoucangetanoverview ofspecialtypesofWorkItems,forinstancebackgroundWorkItems(WorkItemtypeB),tocheckif theywerecompleted.

2007SAPAG

BestPractice:SAPWorkflowMonitoring Figur e12 Tr ansactionSWI1 selectionscr een

20

Ifyouexecutethetransactionwithoutdefinedsearchcriteria,alltheWorkItemsfromthelasthourwill bedisplayedbydefault.IfyouenteraWorkItemIDintheselectionscreen,thesystemwillignorethe othersearchcriteria. Afterexecutingthetransaction,youwillgetalistdependingonthesearchcriteriacontaining informationsuchas WorkItemnumber,statusoftheWorkItem,SAPWorkflowtaskthatcreatedthe WorkItem,andsoon.

Figur e13 Tr ansactionSWI1 wor kitemlist

Thelayoutofthislistcanbechanged,forexamplebyaddingorremovingcolumnsfromthelist.You candefineapersonallayoutbyselectingSettings>layout>changefromthemenu.

Figur e14 Tr ansactionSWI1 Layoutsettingsofthewor kitemlist Youcanselect: Columnstobedisplayed Sortorderoftheworkitemsdisplayed Filterthelist Tospeciallycustomizetheviewanddisplayofthelist

2007SAPAG

BestPractice:SAPWorkflowMonitoring Thenextfiguredisplayshowtomanagethisinthesystem.ClicktheTabColumnsandchoosethe columnsyouwantinordertomodifythelayout.

21

Figur e15 Tr ansactionSWI1 changelayoutoftheworkitemlist TodisplaytheWorkItemdetails,doubleclickontheitem.Thedetailsscreenisdifferentdependingon thetypeoftheworkitem.WewanttoshowtwoexamplesforthetypeFSubSAPWorkflowand typeBBackgroundStep.

Figur e16 Tr ansactionSWI1 Listofworkitems FortypeFSubSAPWorkflowyouwillgetthelogoftheSAPWorkflowparentbydoubleclickingon thecorrespondingitemintheabovefigure.Thiscontainsthehistoryoftheentireprocess,includingall subSAPWorkflows.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

22

Figur e17 Tr ansactionSWI1 SAPWorkflowlog(subSAPWor kflow) ForabackgroundtypeSAPWorkflowstep,theSAPWorkflowadministratorwillgetdetailed informationabouttheworkitembydoubleclickingonthecorrespondingworkitemtypeBackground. TodisplaytheSAPWorkflowlog,doubleclickontheiconLog.

Figur e18 Tr ansactionSWI1 SAPWorkflowlog(Backgr oundjob)

WhenthestatusoftheWorkItemshowsanerror,youshouldlookattheSAPWorkflowlogusingthe menuEdit>DisplaySAPWorkflowlog.Here,youcanseeerrorsthathaveoccurred.TheSAP Workflowlogisdescribedinmoredetailinthecorrespondingsectionofthisdocument.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

23

3.2.1.2TransactionSWI2_FREQWorkItemsperTask
TransactionSWI2_FREQlistsworkitempertaskandallowsdeterminationofSAPWorkflows withinaspecifictimeframeandaspecialworkitemtype.Youcansearchandselectworkitemsby Monitoringperiod,WorkitemtypeandTaskfilter: TheonlyparameterthatneedstobespecifiedisMonitoringperiod.Otherparametersareoptional.

Figur e19 Tr ansactionSWI2_FREQ selectionscreen Itispossibletoselect/listtheworkitembyusingaspecialworkitemtype(forexample,only backgroundtypes)andadditionally,thefilterfunctionalitycanbeused(filterforaspecialapplication component).Inthisscreentheselectionsusedaredialogworkitemstoday. ThefollowingfigureWorkitempertaskshowstheresultsofthisselection.Here,weseealistofwork itemssortedbytasktypes.Thedifferenttasksmaybecarriedoutmorethanoncedependingontask type.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

24

Figur e20 Tr ansactionSWI2_FREQ Wor kitemsper task

Ifyoudoubleclickonaspecialtask,yougetalistofworkitemsthatarerelatedtothechosentask type.Thefollowingfigureshowsthechosentask.

Figur e21 Tr ansactionSWI2_FREQ wor kitemswithaspecifictask TheSAPWorkflowadministratorgetsinformationabouttheagentsinvolved,timeofcreationand statusoftheworkitems. Thefollowingfigureshowsthebasicdataabouttheselectedworkitem.Thescreenliststheworkitem attributessuchasstatus,priority,timeofcreation,timeofprocessing,openrequests.Furthermore,the screengivesinformationaboutthedescriptionandattachments.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

25

Figur e22 Wor kitem workitemdetails ByclickingtheLogbutton,theusergetsthelogfileofthecompleteSAPWorkflowandcanfind informationaboutthisparticularexecution.Analysisandinterpretationoftheinformationinthelisted logfileisdescribedinthesectionSAPWorkflowlogofthisdocument.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

26

3.2.1.3TransactionSWI2_ADM1WorkItemsWithoutAgents
TransactionSWI2_ADM1enablesyoutosearchforworkitemswithinaspecifictimeframe withoutagentassignment.

Figur e23 Tr ansactionSWI2_ADM1 Selectionscr een TheonlyparameterwhichneedstobespecifiedisMonitoringperiod.Inthisexample,weareusing theselectionfordialogworkitemsfromtoday.Otherparametersareoptional.Itispossibleto select/listtheworkitembyusingthetaskfilterfunction(forexample,filterforaspecialapplication component).

2007SAPAG

BestPractice:SAPWorkflowMonitoring Figur e24 Tr ansactionSWI2_ADM1 Listofwor kitemswithoutagent

27

Thenextfiguredisplaystheresultsoftheselectionshowninthefigureabove.Todisplayaworkitem, selecttheitemfromthelist(inthisexample,thefirstone)andclickonthebuttonDisplayworkitem.

Figur e25 Detailsoftheselectedwor kitem Thefigureaboveshowsthedetailsoftheselectedworkitem.Todisplaythelogbelongingtothework itemclickonthebuttonSAPWorkflowlog. ThecorrespondingSAPWorkflowlogisdisplayedinthenextfigure.Analysisandinterpretationofthe informationinthelistedlogfileisdescribedinthesectionSAPWorkflowloginthisdocument.Asno agenthasbeenassigned,youwillgetnoinformationonAgent.However,inthelistofworkitems withoutagent,youcandetermineeithertoexecuteagentrules,toforwardtoanagentortoassign possibleagents.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

28

Figur e26 SAPWorkflowlog

2007SAPAG

BestPractice:SAPWorkflowMonitoring

29

3.2.1.4TransactionSWI6SAPWorkflowsforObject
TransactionSWI6allowsyoutodetermineSAPWorkflowsworkingwithspecificBusiness ObjectinstancesandtoanalyzethestatusofSAPWorkflow.Thistransactionisveryusefulifyou donotknowhowtogettheworkitemIDbutonlyhavethebusinessobjectinformation. TheonlyparameterwhichneedstobespecifiedisObjectType.Otherparametersareoptional.

Figur e27 Tr ansactionSWI6 selectionscr eenobjecttype

IftheKeyparameterisspecific,thenonlySAPWorkflowsusingthisObjectinstancewiththegiven keywillbedisplayedinthenextscreen,otherwiseallObjectinstanceswillbelisted.

Figur e28 Tr ansactionSWI6 selectionscr eenobjectkey 2007SAPAG

BestPractice:SAPWorkflowMonitoring

30

The field Selection variant exists in the entry screen of transaction SWI6. The Selection variant parameterdeterminesthetypeofinstancestobeselected(seearrowinthenextfigure).Thereare4 possibleentriesforthisparameterandtheycouldbechosenfromdropdownlist. AllInstances ActiveInstances(Running,Ready,Committed) FinishedInstances(Completed,Cancelled) ActiveInstances(All)

Figur e29 Tr ansactionSWI6 selectionscr eenselectionvar iant

Thenextfigureshowstheresultofthedisplayedselection.Thereare4SAPWorkflowslisted(1two stepand3onestepapprovalSAPWorkflows).

2007SAPAG

BestPractice:SAPWorkflowMonitoring

31

Figur e30 Tr ansactionSWI6 ListofSAPWorkflowsfor objecttypeRequir ementcover agerequest EC

SelectanitemandclickonDisplaySAPWorkflow logtodisplaythecorrespondinglogoftheSAP Workflow,andthecorrespondinglogoftheSAPWorkflowisshownbelow.

Figur e31 SAPWorkflowlog TheSAPWorkflowlogsandtheiranalysiswillbediscussedinthesectionSAPWorkflowlogofthis document.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

32

3.2.2
Transaction code SWI2_DIAG SWUD

ErrorMonitoringandAnalysis
Shorttext Explanation

ErrorMonitoring,AnalysisandRestarting

ListingWorkItemswitherrors Youcanlistworkitemsbycauseoferror. anddisplayingerrordiagnosis SAPWorkflowDiagnosis YoucanusethistransactionforSAP WorkflowDiagnosiswhichisveryusefulif youdiscoverthataparticularSAP Workflowisnotworkingcorrectly. Youcanmonitorandrestarthanging WorkitemsinthetRFCqueue. YoucanrestartSAPWorkflowsafter error. YoucancontinueSAPWorkflowsthat hangafterasystemcrash. Youcancheckthedefinitionofatask. Youcantracetheflowandinvestigatea specificstep. Youcandisplayandtestanobjectused inSAPWorkflow. Youcanmonitoreventqueue. YoucanmonitorSWW*jobsscheduled byWFBATCH.

SM58 SWPR SWPC PFTC SWDD SWO1 SWEQADM SM37

tRFCmonitor RestartingSAPWorkflow ContinuingSAPWorkflow GeneralTaskMaintenance SAPWorkflowBuilder BusinessObjectBuilder EventQueueAdministration MonitoringSAPWorkflow relatedjobs

2007SAPAG

BestPractice:SAPWorkflowMonitoring

33

3.2.2.1TransactionSWI2_DIAGDiagnosisofSAPWorkflowswith errors
ThetransactionSWI2_DIAGallowsyoutocheckforworkitemscontainingerrors.SWI2_DIAG listsworkitemsbycauseoferrorandallowsthediagnosisoferrorswithinaspecifictimeframe. Optionally,theresultcanbefilteredbyspecifictasks. TheonlyparameterwhichneedstobespecifiedistheMonitoringperiod.

Figur e32 Tr ansactionSWI2_DIAG workitemcontaininger r or s Afterchoosingaspecifictimeframe(inthisexampleToday),checktheexecutionbutton. Thenextfigureshowstheresultsofthisselection. Thisexamplelists2errors,categorizedas Miscellaneous.Inthisview,youfindinformationaboutthedateandtimeofcreation,theworkitem type,theworkitemIDandtheworkitemtext.

Figur e33 Tr ansactionSWI2_DIAG err or list

2007SAPAG

BestPractice:SAPWorkflowMonitoring

34

Formoreinformationonaspecialerror,doubleclickontheitemyouareinterestedin.Thefollowing popupshowsadetailederrorexplanation.

Figur e34 Tr ansactionSWI2_DIAG err or diagnosisfor awor kitem Ifyoudoubleclickonaspecifieditemoftheerror,youcanseeamoretechnicalerrordescription.

Figur e35 Er r ortextofaspecifieditem Inthistechnicaldescription,youwillfindanerrormessagecode(forexample:Messageno.WL821). ThismessagecodeisusefulinsearchingforanSAPNotetohelpmanagetheproblem.

3.2.2.2TransactionSWUDSAPWorkflowDiagnosis
TheSWUDtransactionistheSAPWorkflowDiagnosistransaction,whichcanbeveryuseful shouldyoudiscoverthataparticularSAPWorkflowisnotworkingcorrectly.Itisasortofcheck listthatcontainsthetestsyoucanruninordertofindtheerrorsintheSAPWorkflowyouare analyzing. Thechecklistorderisdetermineddynamicallyaccordingto: a) YourSAPWorkflowdefinition b) Thestatisticsofthemostcommonmistakesmadewhencreating/activatinganSAP Workflow.

2007SAPAG

BestPractice:SAPWorkflowMonitoring WhenyoucallthetransactionSWUD,yougetthescreenshowninthefigurebelow.

35

Figur e36 Tr ansactionSWUD initialscreen

Itissubdividedintothreeareas: 1. ThefirstsectionshowstheSAPWorkflowdefinitioncurrentlybeinganalyzed 2. Inthecenter,alistwiththetestoptionsisdisplayed 3. AtthebottomisalistofthelasttenSAPWorkflowdefinitionswhichwereanalyzed.

AnySAPWorkflowaccessedthroughthistransactionisaddedtothelastusedlist.TheSAPWorkflow canberecalledatalaterdatebyclickingonthereuseicon inthelefthandcolumnofthelastused list(inthefigureabove).

Ascanbeseenintheprevious figure,youhavetoenterthetasktype(Standardtask(TS),Customer task(T),SAPWorkflowtemplate(WS)orSAPWorkflowtask(WF))andthetask(thisistheIDthat identifiestheparticularSAPWorkflowortask)thatyouwanttoanalyze.Youcanalsousethesearch helpforaselectionbasedonstandardsearchcriteria.

Inthefollowingparagraphs,wewillgiveyouanoverviewofthefourtestoptionsofferedinthelistand, inordertoaccustomyoutothistransaction,wewillillustratethetestoptions,bymeansofscreen shots.AsanexampletheSAPWorkflow WS30100051SAPWorkflowsystemverificationisused.For moredetails,refertoSAPNote322526AnalysisforSAPWorkflowproblemsandreadthe documentationbyclickingonthebutton . Testoptions VerifyAutomaticCustomizing Problem:Tasknotstarted Problem:SAPWorkflowishanging Testenvironment

2007SAPAG

BestPractice:SAPWorkflowMonitoring

36

OptionVerifyAutomaticCustomizing
IfanSAPWorkflowwhichhasalreadybeentesteddoesnotworkproperly,thencustomizingsettings should be checked for any changes. If this is the case, the SAP Workflow administrator can check thesesettingsbymeansofthischecktool. ExecutingthistestspringsintothetransactionSWU3AutomaticSAPWorkflowCustomizing.Ifany errorsarefoundhere,readthedocumentationfortheerror.

Figur e37 Tr ansactionSWU3 Initialscr een

2007SAPAG

BestPractice:SAPWorkflowMonitoring

37

OptionProblem:tasknotstarted
ThisfunctionalitycanhelpyoutofindwhytheSAPWorkflowortaskdidnotstartorcouldnotbe found.Bymeansofthisoption,yougetalistofchecksasdisplayedinthenextfigure.

Figur e38 Tr ansactionSWUD OptionPr oblem:tasknotstar ted Inthisscreen,theSAPWorkflowadministratorcanstartdifferentchecks(forexample,Determine instancesfortask).Formorebackgroundinformation,clickontheIconsmarkedwiththearrowinthe figureabove. SuboptionsofProblem:tasknotstarted: Determineinstancesfortask Refreshorganizationalenvironment Eventqueue(tRFClog) Eventtrace Consistencycheckfortasks Simulateevent

Determineinstancesfortask: ThisisusedtocheckwhetherthetaskwasstartedandanSAP Workfloworaworkitem created.Youcanbranchtotheworkitemdisplay.IfyousettheflagInc.component,work itemsarealsodisplayedthatwerecreatedinthestartedSAPWorkflow.Youcanonlyset thisflaginthetestenvironmentafteryouhaveexecutedStarttask. Refreshorganizationalenvironment: AlltheworkitemsthattheuserisassignedtoaredisplayedintheBusinessWorkplace. Thisorganizationalassignmentbetweentaskanduserisreadfromabuffer.Thebufferis onlyupdatedevery24hours.Ifworkitemsthatyouhavebeenassignedtointhelast24 hoursarenotdisplayedintheBusinessWorkplace,choosethisfunction. Caution:Onlyyourownsettingsareupdatedusingthisfunction.Ifaworkitemisnot displayedforanotheruser,thisuserhastorefreshhisorganizationalenvironmenthimself. Forthispurpose,thisfunctionisalsoavailableintheBusinessWorkplace.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

38

Eventqueue(tRFClog): Thisisusedtodisplaytheworkitemqueue(logofthetransactionalRFC TransactionSM58).Iftaskstobestartedarenotgeneratedoraregeneratedwith delay,thisisdisplayedintheworkitemqueue.Ifoneofthereceiverscannotbecalled correctly,subsequentreceiverswillnotbeabletobestartedcorrectlyeither. Eventtrace: ThisisusedtocheckwhethertheeventthatistostarttheSAPWorkflowwascreated correctly.Alleventscreatedcorrectlyareloggedintheeventtraceirrespectiveof whetherpossiblereceiversexist.YoucanalsomonitoritwithTransactionSWEL. Consistencycheckfortasks: AsyntaxcheckoftheSAPWorkflowdefinitionorthetaskdefinitionisperformed.All knownerrorsandwarningsarelisted.

Figur e39 Consistencycheckfor tasks

Simulateevent: Bysimulatinganevent,allthetasksthatwouldpotentiallybestartedbytheeventare displayed.Youcancheckwhetheryourtask,whichistobechecked,wouldbe startedwithouterrors.Anextendederroranalysisisnotpossible.

Figur e40 Simulateevent

2007SAPAG

BestPractice:SAPWorkflowMonitoring

39

OptionProblem:SAPWorkflowishanging
ThisisusedtodeterminewhytheselectedSAPWorkflowdoesnotcontinueandisnotcorrectly terminated.Thisoptionallowsyoutorunthetestsshowninthenextfigure.Formorebackground information,clickontheInformationIcons.

Figur e41 Tr ansactionSWUD OptionPr oblem:SAPWor kflowishanging SuboptionsofProblem:SAPWorkflowishanging: Determineinstancesfortask Workitemqueue(tRFClog) ABAPdumpanalysis Consistencycheckforcomponents

Determineinstancesfortask Workitemqueue(tRFClog) ABAPdumpanalysis: IfthecalledobjectmethodendswithanABAPruntimeerror,thecorrespondingSAP WorkflowterminateswithoutanentryandtheSAPWorkflowlogappears.Thesystem producesashortdumpundertheuserSYUNAMEortheuserthatthelogicaldestination SAPWORKFLOW_LOCALisassignedto.ABAPdumpanalysiscanbecalledby TransactionST22. Consistencycheckforcomponents: YouusethisfunctiontochecknotonlytheSAPWorkflowdefinitionbutalsoallthetask definitionsofthetasksreferencedintheSAPWorkflowdefinition.Ifyousettheflag Includingsubflows,allsubSAPWorkflowsandthetaskscontainedinthemareincluded inthecheck.Allerrorsandwarningsfoundarelisted.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

40

Figur e42 Consistencycheckfor components

OptionTestEnvironment
Thisisusedtotesttheselectedtask(inthenextfigure).Youcanstartthetaskandmonitorfurther processingintheSAPWorkflowlog.Ifyousettheflagstoincludetasktype,thetasksandbusiness objecttypesthatarecomponentsofthetasktobetestedarealsodisplayedinthetest. Tasksthathavearedbackgrounddonothaveanagentassignment.Youcanalsodisplaythetasks andbusinessobjectstypesdirectly.

Figur e43 Tr ansactionSWUD OptionTestEnvir onment

2007SAPAG

BestPractice:SAPWorkflowMonitoring

41

SuboptionsofTestenvironment: Determineinstancesfortask Consistencycheckfortasks Consistencycheckforcomponents Simulateevent Starttask Createevent Testmethod Switchoncontainermonitor DisplaySAPWorkflow Trace Displaytaskinanewsession

Determineinstancesfortask Consistencycheckfortasks Consistencycheckforcomponents Simulateevent Starttask: ThisisusedtoaccessthedialogexecutionoftasksorSAPWorkflows.Afteryouhave enteredtherequiredinputdataanddeadlinedata,youcanstartthetask.Further informationontheprocessflowofthetaskcanbefoundintheSAPWorkflowlog.If yousettheindicatorSAPWorkflowtrace,theprocessisloggedintheSAPWorkflow trace.YouhavetoassignanametotheSAPWorkflowtracetobelogged.TheSAP WorkflowtraceshouldonlybeusedbyexperiencedSAPWorkflowdevelopers. Createevent: Thisisusedtocreateanevent.Aftertheeventhasbeencreated,youcanverifythe eventcreationintheeventtrace.IfyouthenchooseDetermineinstancesfortask, youcancheckwhetherthetaskwasstartedbytheevent.IfyousettheindicatorSAP Workflowtrace,theprocessisloggedintheSAPWorkflowtrace.Youhavetoassign anametotheSAPWorkflowtracetobelogged.TheSAPWorkflowtraceshouldonly beusedbyexperiencedSAPWorkflowdevelopers. Testmethod: Thisisusedtostartthetestofmethodsofabusinessobjecttype.Selectanobject typeandacorrespondingmethodand,ifnecessary,specifyotherparameters. Switchoncontainermonitor: Thisisusedtoswitchoffthecontainermonitor.Whenataskisexecuted,the containercontentisdisplayedinadialogboxwherechangedcontainerelementsare flaggedbyastar.Toswitchthecontainermonitoroff,chooseDebugoffinthe containermonitor.Thedatadisplayedinthecontainermonitorcanalsobefoundin theSAPWorkflowtrace. DisplaySAPWorkflowTrace: ThisdisplaystheSAPWorkflowtrace.ThisfunctioncanbecalledbyTransaction SWU9. Displaytaskinanewsession: Thetaskdefinitionisdisplayedinaseparatesession.Notethatyoucanopena maximumofsixsessionsatthesametime.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

42

Figur e44 Tr ansactionSWUD DisplaySAPWorkflowtemplate

3.2.2.3TransactionSM58tRFCMonitor
SAPWorkflowisstartedwithTransactionRFC.TransactionSM58allowsyoutoviewalistofSAP WorkflowrelatedLUWs(LogicalUnitofWork)thatarebeingprocessedorhangingwitherror. Inordertousethis monitor,itisessentialthatyourefertotheinformationonmaintainingthelogical destinationSAPWORKFLOW_LOCAL_<client>inAutomaticSAPWorkflowCustomizingwith TransactionSWU3. ThenenterSAPWORKFLOW_LOCAL_<client>intheTRFCDestinationfieldintheselectionscreen ofSM58.

Figur e45 Tr ansactionSM58 selectionscreen TheerrorsaredisplayedinredintheStatusText. IfyouseemanyentrieswithStatusTransactionrecorded,itispossiblethatnotenoughresourcesare availableforprocessingSAPWorkflow.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

43

Figur e46 Tr ansactionSM58 LUWsfor RFCdestinationSAPWORKFLOW_LOCAL_001 WhenyoudoubleclicktheTransactionIDdisplayednexttoStatusText,youcandisplaysomedetails ofeachLUW.

Figur e47 Tr ansactionSM58 Er r or textsandtr ansactionalID Iftheyaretemporaryerrors,youcanreprocessthemfromthemenu:EditExecuteLUWs. Then,the selectionscreenofthereportRSARFCEXappears.Whennecessary,youcanrunthisreportina backgroundjobonaregularbasis.

Figur e48 Tr ansactionSM58 ExecutingLUWs RefertoSAPNote888279Regulating/distributingtheSAPWorkflowload,whenalargenumberof SAPWorkflowsarestartedinyoursystem.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

44

3.2.2.4TransactionSWPRRestartSAPWorkflow
WithTransactionSWPR,youcanrestartworkitemswitherroraftertheerroriscorrected.You canfirstbringupalistofallworkitemswitherrors(withoutrestartingimmediately)andthenrestart workitemsonebyone,oryoucanrestartalltheworkitemswitherrorsimmediatelybyselecting Restartimmediatelyoptionintheselectionscreen.

Figur e49 Tr ansactionSWPR Selectionscreen

Figur e50 Tr ansactionSWPR Listupwor kitemswither r or

3.2.2.5TransactionSWPCContinueSAPWorkflow
TransactionSWPCenablesyoutocontinueworkitemsthatarehangingafterasystemcrash,a shutdownorashortdump.Youcaneitherdisplayallworkitemstocontinuefirst,orcontinuethem immediatelybyselectingtheContinueimmediatelyoptionintheselectionscreen.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

45

Figur e51 Tr ansactionSWPC selectionscreen

3.2.2.6TransactionPFTC GeneralTaskMaintenance
TransactionPFTCallowsyoutocheckthedefinitionofataskincludingContainerand Triggeringevents.Youcanselectoneofthefollowingtasktypes. Standardtask(singlesteptask,tasktypeTS) Customertask(singlesteptask,tasktypeT) SAPWorkflowtemplate(multisteptask,tasktypeWS) SAPWorkflowtask(multisteptask,tasktypeWF) Taskgroup(tasktypeTG)

Figur e52 Tr ansactionPFTC initialscreen

2007SAPAG

BestPractice:SAPWorkflowMonitoring

46

Figur e53 Tr ansactionPFTCSAPWorkflowtemplate ByclickingtheSAPWorkflowBuilderbuttonundertheBasicdatatabstrip,youcanlaunchSAP WorkflowBuilder(TransactionSWDDSeenext). UndertheTriggeringeventstabstrip,youfindtheEventsdefinitionwiththecorrespondingobjecttype whichyoucanuseinTransactionSWI6.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

47

3.2.2.7TransactionSWDD SAPWorkflowBuilder
WithTransactionSWPCyoucantracetheflowandseeexactlywheretheproblemexistsand theninvestigatethespecificstep.Forexample,binding,objectmethodandagentassignment, andsoon.

Figur e54 Tr ansactionSWDD SAPWorkflowtemplate79900001

3.2.2.8TransactionSWO1BusinessObjectBuilder
TransactionSWO1allowsyoutodisplayandtestobjecttypesintheBusinessObject Repository.Forinstance,ifaworkitemwasexecutedbyauserbutexecutionfinishedwithanerror. Itisusefultofindoutthebusinessobjectmethodusedintheworkitemandgettheobjectinstancefro theworkitemcontainerandtestthemethodexecutionviaSWO1toseeifthereareanyexceptions etc.

Figur e55 Tr ansactionSW01 initialscr een 2007SAPAG

BestPractice:SAPWorkflowMonitoring

48

Youcandisplaythedefinitionoftheobjectandcorrespondingprograms,parametersandexceptions.

YoucanusetheTestoptiontotesttheobject.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

49

3.2.2.9TransactionSWEQADMEventQueueAdministration
Youcanusetheeventqueuetodelaythestartingofreceiversreactingtoatriggeringevent.To achievethis,thereceiversarestoredinatemporarymemory.Onlythosereceiverswhoselinkages wereactivewhentheeventoccurredcanbestored.Theeventqueuedoesnotallowyoutostorethe eventitselfinordertodeterminetheactivelinkageslater.Thismeansthatthesystemloadcausedby alargenumberofeventsbeingcreatedcanbespreadoveralongertimeperiod(whichcanbesetby theSAPWorkflowsystemadministrator).Thiscombatsthethreatofsystemoverload.Thisisachieved usingthetransactionalRFCsforstartingthereceiversnotbeingcalledimmediately,butafteratime delayandinsmallnumbers.Usingtheeventqueue,therefore,delaysthecallingofthereceivers.The eventqueuecanalsobeusedtostoreeventsthathaveerrorstemporarily.

Figur e56 Tr ansactionSWEQADM initialscr een Tabpage Basicdata Activation Backgroundjob Eventdelivery Function Theadministratorandtheerrorfeedbackbehavioraremaintained here. Youcanactivatetheeventqueueanddefinethelinkagesforwhich theeventqueueistotemporarilystoreeventsandreceivers. Theeventqueueisreadatregularintervalsbyabackgroundjob. Theeventsfoundaredeliveredtotheregisteredeventreceivers. Onthistabpageyoumaintainhowtheeventreceiversaretobe started.Adefinednumberofeventsisdeliveredbythebackground jobineachcycle.Theseeventscanbeprocessedsequentiallyorin parallel(withaRFC).Thereceiverscanbestartedsynchronously (withRFC)orasynchronously(withtRFC).

Linkageswitherrors Ifanerroroccurswithinaneventreceiver,thiserrorcancausethe eventdatatobelostandpreventthereceiverfromstarting.To enabletheeventtobedeliveredagainafteranerror,theeventdata canbeenteredintotheeventqueue.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

50

3.2.2.10 TransactionSM37SAPWorkflowrelatedJob Monitoring

YouneedtomonitorbackgroundjobsscheduledbytheuserWFBATCH.Asmostofthesejobsare scheduledveryfrequently,itisindispensabletosetupautomaticjobmonitoringwithCCMSonSAP SolutionManagertodoimmediateerroranalysisandsolveaproblemincasejobsarecancelled.

Jobname SWWCOND SWWDHEX SWWERRE SWWCLEAR SWFSLSDLEX

Reportname RSWWCOND RSWWDHEX RSWWERRE RSWWCLEAR RSWFSLSDLEX

Explanation Executesinglebackgroundjobforworkitem deadlinemonitoring. Deadlinemonitoringforworkitems. Monitoringfor incorrectorstoppedbackground steps Executeworkitemclearingworkonce.

TriggeringDeadlineMonitoring

Figur e57 Tr ansactionSM37 J oblistwiththeuser WFBATCH

3.2.2.11

Errorhandlingroadmap

ThesectionMonitoringandAnalysisTools describestheprocedureofSAPWorkflow monitoring.It givesanoverviewofthemonitoringtools,theirfunctions,andtheiruse.Foraquickanalysisof problemsandsufficientSAPWorkflow monitoring,itcouldbehelpfultousearoadmap. Thefollowingfigureshowsaroadmap,whichcanbeusedforSAPWorkflowmonitoringinproductive operations.Thisroadmapgivesagraphicaloverviewofhowtoanalyzeandmonitorthemajor problemscorrespondingtoSAPWorkflowprocessing.WhichtooltheSAPWorkflowadministrator usesdependsontheinformationavailableabouttheproblemswhichoccurred.
Forexample,aspecialproblemhasoccurred(oneSAPWorkflow instancedoesnotfunction)andthe SAPWorkflow administratoronlyhasinformationaboutcreationtimeofthebusinesstransaction(for example,Createshoppingcart).Inthiscase,usetransactionSWI2_FREQformonitoringtheproblemand navigatetotheSAPWorkflow logforanalyzingtheissue.FormonitoringofSAPWorkflowsandtheir processesonregularbasis,theSAPWorkflowadministratorshouldusetransactionSWI1.

Error!Objectscannotbecreatedfromeditingfieldcodes. Figur e58 Er r oranalysisr oadmap

2007SAPAG

BestPractice:SAPWorkflowMonitoring

51

3.2.2.12

PerformanceMonitoringandAnalysis

ThissectionwillgiveyousomesuggestionsonhowtomonitoryoursystemsperformanceforSAP Workflow. TheperformanceofSAPWorkflowdependsonmanyfactors(typeofbusinessprocess,numberof messages,activitiesrunningonthedistributedsystems,hardware,andsoon).Itisadvisablethatthe personswhodotheperformancemonitoringoftheSAPWorkflowhaveattendedthe SAPcourse:ADM315WorkloadAnalysis.Asthetechnicalknowledgeforthemonitoringismuch morecomplex,wecanonlygiveanoverviewoftheperformancemonitoringinthisdocument. PerformanceMonitoringandAnalysis Transaction code SWI5 Shorttext WorkloadAnalysis Explanation Youcanestablishtheworkloadof individualorganizationalobjects(users, positions,jobs,workcentersor organizationalunits),usingtheworkload analysis. Youcandisplayinformationonsystem loadfromvariousviewpointsand timeframe Youcandisplayastatisticalrecordofa singlestep. Youcananalyzeasinglestepusingthe Integratedperformanceanalysistoolwith ABAP(SE30)andPerformanceTrace (ST05).

ST03(ST03N)

WorkloadMonitor

STAD ST12

Statisticalrecord SingleTransactionAnalysis

3.2.2.13

TransactionSWI5Workloadanalysis

UsingTransactionSWI5Workloadanalysis,youcanestablishtheworkloadofindividual organizationalobjects(users,positions,jobs,workcentersororganizationalunits).Youcan lookintothepast(completedsince...)andintothefuture(tobeprocessedby...)inordertoestablish workload.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

52

Figur e59 Tr ansactionSWI5 Selectionscr een

Workloadforthepast Theselectionproducesalistofworkitemscompletedbythemembersoftheorganizationalobject beforethespecifieddate. Aworkitemmustmeetthefollowingcriteriatobedisplayedinthislist: Theworkitemmustrepresentataskthatsatisfiestheselectioncriteriaspecifiedasatask filter. Theworkitemmustbeadialogworkitem. Theworkitemmusthavethestatuscompleted. Theactualagentoftheworkitemisauserwhoisassigneddirectlyorindirectlytothe organizationalobjectspecified.

TheresultoftheselectionisdisplayedwiththefollowinginformationinthelistCompletedWorkItems byAgentandTask: Organizationalunitoftheactualagent Agent Numberofthetasksrepresentedbytheworkitem Dateoffinalcompletion Workitemtext Processingduration

Ifyoudoubleclickonanentry,yougototherelevantworkitemdisplay.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

53

Formattingforstatisticalpurposes Theinformationcanbeformattedforstatisticalpurposes.Todothis,positionthecursorononeofthe columnsOrg.unit,Agent,TaskorDate,andselectthefunctionStatistics.Dependingonthecolumn youselected,thefollowinginformationisdisplayed: Organizationalunitandnumberofworkitemscompletedbyanemployeefromthe organizationalunit. Agentandnumberofworkitemscompletedbythisagent. Taskandnumberofworkitemsforthistask,whichwerecompleted. Dateandnumberofworkitemscompletedonthisdate.

Inaddition,thefollowingtimesarecalculated: 10%threshold:For10%oftheworkitems,thedurationofprocessingwasshorterthanthe timespecified. 50%threshold:Forhalfoftheworkitems,thedurationofprocessingwasshorterthanthetime specified. 90%threshold:For90%oftheworkitems,thedurationofprocessingwasshorterthanthe timespecified.

Workloadforthefuture Theselectionproducesalistofworkitemsthatmustbeprocessedbythemembersofthe organizationalobjectbythedateentered.Aworkitemmustmeetthefollowingcriteriatobedisplayed inthislist: Theworkitemmustrepresentataskthatsatisfiestheselectioncriteriaspecifiedasatask filter. Theworkitemmustbeadialogworkitem. Theworkitemmusthaveoneofthefollowingstatuses: o waiting o ready o inprocess o reserved o executed Theactualagentoftheworkitemhastobeauserwhoisassigneddirectlyorindirectlytothe organizationalobjectthatisspecified.Thisonlyappliestoworkitemswiththestatuswaiting, inprocess,reservedorexecuted,sincetherecanonlybeanactualagentinthesecases. Therehastobeatleastoneuserinthepossibleagentsoftheworkitem,whoisassigned directlyorindirectlytothespecifiedorganizationalobject.(Thisonlyappliestoworkitemswith thestatuswaitingorreadysincethesedonotyethaveaactualagent.) Thelatestendforprocessingtheworkitemmustbebeforethedateentered.

TheresultoftheselectionisdisplayedinthelistWorkloadfor....Thelistofworkitemsisgrouped accordingtoactualagentsandtasks.Attheendofthelist,theworkitemsandtasksforwhichno actualuserexistsaredisplayedundertheheaderNotreservedbyanagent.Whennodateis specified,auser'sworkloadcorrespondstothecontentsoftheirSAPWorkflowinbox.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

54

Thresholdvalue Theprocessdurationofallworkitemsforonetaskisdisplayedasstandardwiththresholdvalues (10%threshold,50%threshold,90%threshold).Thethresholdvaluesshouldbeinterpretedas follows:Theprocessdurationforthex%thresholdmeansthatx%ofallworkitemsforthistaskwere processedwithinthisperiodorashorterperiod.Theprocessdurationisthetotalofwaittimeand processtime. Averagevalue Theprocessdurationcanalsobedisplayedasanaveragevalue,differentiatedaccordingtowait time,processtimeandtotaltime.Theaveragevalueiscalculatedfromthesumofthewaittimes,the processtimesandthetotaltimesforallworkitemsofonetask.Youcanswitchbetweenthetwo displaysbyselectingtherelevantmenuoptionintheViewmenu.Doubleclickonanentrytodisplay detailedinformationforindividualworkitems.

AfterselectingTasks,youwilldisplaytheprocessingtimeattherightside.

Figur e60 Tr ansactionSWI5 completedwor kitemsbyagentandtask

ByselectingStatisticsbutton,youwilldisplaythenumberofworkitems,10%,50%and90%

2007SAPAG

BestPractice:SAPWorkflowMonitoring Figur e61 Tr ansactionSWI5 completedwor kitemsbyagentandtask

55

3.2.2.14

TransactionST03(ST03N)WorkloadMonitor

TransactionST03(orST03N)showsyouinformationonthesystemloadfromvariousviewpointsand timeframes.CallthetransactionST03andselectExpertmode. Selectthetargetserverandthetimeframetodisplay. UndertheWorkloadOverview ,youwillseetheresponsetimepertasktype(Dialog,Backgroundor RFC,etc). UnderRFCProfilesRFCServerProfile,youwillfindtheresponsetimeofFunctionmodulesthat werecalledinthesystem. WhenyoudoubleclickaFunctionmodule,youcandisplayalistofusers whocalledthisFunctionmodule.

Figur e62 Tr ansactionST03N Expertmode

IfyoudonotfindRFCProfilesintheleftnavigationframe,theRFCstatisticsarenotselected.Follow thepath:CollectorandPerformanceDB WorkloadCollectorStatisticsToBeCreatedSelect

RFCstatistics

2007SAPAG

BestPractice:SAPWorkflowMonitoring
Figure63TransactionST03NCollectorandperformanceDB

56

RefertothebestpracticedocumentontheWorkloadMonitorintheSAPServiceMarketplacefor furtherdetails:http://service.sap.com/~sapidb/011000358700011662332001E

3.2.2.15

TransactionSTADStatisticalRecords

TransactionSTADshowsyoustatisticalrecordinformation.WhenyoucallthetransactionSTAD,you havetochooseatimeframefortheanalysisandcanspecifytheclient,user,TransactionorProgram tolimittheselecteddata.Onthenextscreenyouseealistingofallthestatisticalrecordsforthe chosentimeframe.YoucanthenchooseanRFCtoanalyzeitfurther.

Figure64TransactionSTAD

Figure65TransactionSTADStepsexecutedbytheuserWFBATCH

WhenyouselectarecordandselectRFC,youwillfindRFCdestination(forexample,SAP WORKFLOW_LOCAL<client>)andthecalledFunctionmodule(forexample, SWW_WI_CREATE_VIA_EVENT_IBF)withthecallingtimeandthetransferreddatasize.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

57

Figure66TransactionSTADRFCrecordRFC

Figure67TransactionSTADRFCserverrecordCalls

3.2.2.16

TransactionST12SingleTransactionAnalysis

TransactionST12wasdevelopedtopromotetheuseofABAPtrace,tointegrateABAPand Performancetraces(SQL,EnqueueandRFCtraceswiththetransactionST05)andtomakethe tracingandanalysisprocessfasterandmoreconvenient.ABAPtracewithST12isthecentralentry pointforperformanceanalysis.Itshouldbeusedtodetect(topdown)anyperformancehotspot,for functionaltimedistributionanalysis,andtooptimizeABAP/CPUboundissues.SQLtraceshouldbe usedforDBboundissues. RefertoSAPNote755977ST12"ABAPTraceforSAPEarlyWatch/GoingLive"

2007SAPAG

BestPractice:SAPWorkflowMonitoring

58

Figure68TransactionST12ABAPTracesortedbynettime

3.2.3

ResourceMonitoring

ThissectionwillgiveyousomesuggestionsonhowtomonitoryourresourcesforSAP Workflow. TheperformanceofSAPWorkflowdependsonmanyfactors(typeofbusinessprocess,numberof messages,activitiesrunningonthedistributedsystems,hardware,andsoon).Itisadvisablethatthe personswhodotheperformancemonitoringoftheSAPWorkflowhaveattendedthe SAPcourse:ADM315WorkloadAnalysis.Asthetechnicalknowledgeforthemonitoringismuch morecomplexwecanonlygiveanoverviewoftheperformancemonitoringinthisdocument. PerformanceMonitoring Transaction code SMQS Shorttext QoutScheduler Explanation Youcanmonitorsystemresourcesfor tRFCwithQoutScheduler

3.2.3.1TransactionSMQSQoutScheduler
TherecommendedandsimplestwaytoregulatetheloadthatisexecutedbyanSAP Workflowona systemistoregistertheSAPWorkflowRFCdestinationSAPWORKFLOW_LOCAL_<client>inthe transactionSMQSQoutScheduler.WhenthestatusoftheRFCDestinationSAP WORKFLOW_LOCAL_<client>showsWAITCONNcontinuously,youmayneedtoincreasethevalue ofMAXCONNofthisdestinationasfarasenoughfreeDialogworkprocessesarestillavailable.The statusWAITCONNmeansthatthenumberofactivatedjobsofLUWsforadestinationhasreached thegivenvalue(MAXCONN)anditwaitsforthecompletionofastartedjob. RefertoSAPNote888279Regulating/distributingtheSAPWorkflowload

Figure69TransactionSMQS

2007SAPAG

BestPractice:SAPWorkflowMonitoring

59

Furtherresourcesthatshouldbemonitoredonaregularbasisare: Workprocesses Queues CPU Memory Buffers Database

3.2.4

FurtherInformation

3.2.4.1Troubleshooting
IfexecutingthisBestPracticedidnotproducethedesiredresults, SearchforrelatedSAPNoteswiththecomponentBCBMT*inSAPServiceMarketplace. OpenanSAPCustomerMessagedescribingyourproblemifyoufindnosolutioninSAP Notes.

3.2.4.2Literature

PracticalSAPWorkflowforSAP(EffectiveBusinessProcessesusingSAPsWebFlow
Engine),AlanRickayzenetal,GalileoPress,2002

3.2.4.3BackgroundInformationandReferences
Thefollowingtablelistssomeoftherelevantnotes forSAPWorkflow monitoring. Description EventcreationforSAPWorkflow Deletingworkitemsnolongerrequired Specialfeaturesindatemonitoring Performance Loaddistribution TransportofSAPWorkflowandPDobjects Viewsandsubstitutions SAPWorkflowinterfaces CollectiverestartofSAPWorkflows AnalysisforSAPWorkflowproblems Createshoppingbasket:ErrorinSAPWorkflow Problemswithstartconditions CCMS SAPNotes 38968 49545 69470 72873,72923,95857,98407 888279 73318,77607 73992,74000 77099 116412 322526 396779 304834 855865

3.2.4.4FeedbackandQuestions
SendanyfeedbackbyopeninganSAPcustomermessagewiththecomponentSVBO.Youcando thisathttp://service.sap.com/message.

2007SAPAG

BestPractice:SAPWorkflowMonitoring

3.2.5

APPENDIX:WorkItemArchiving

Most of the performance problems in Business Workplace are caused by the missing archiving of Workitems.

3.2.5.1TransactionSWW_SARA
Thearchivingprogramreadsworkitemsforarchivingandwritesthemintoanarchive.Thedeletion programRSWWARCDdeletestheseworkitemsfromthedatabase. YoucanspecifywhetherornotthedeletionprogramistobestartedwithinCustomizingforthe archivingobjectWORKITEM. Thearchivingprogramoffersvariousselectionparameterswithwhichyoucanselectwhichworkitems aretobearchived.Theselectionparametersare: WorkitemID TaskID Actualagentofworkitem Creationdateofworkitem Enddateofworkitem

Thearchivingprogramcompilesthelistofworkitemsdefinedwiththeselectioncriteria,andpassesit tothefunctionmoduleSWW_WI_LIST_ARCHIVE.Thelatterthenarchivestheintermediate documentsusingthefunctionmodulesandFORMroutinesfromthefunctiongroupSWWXin conjunctionwiththeFORMroutinesfromtheArchiveDevelopmentKit(ADK). Onlyworkitemswithanendstatus(COMPLETEDorCANCELLED)canbearchived.Inaddition, archivingcanonlybeinitiatedforworkitemsthatarenotdependentonotherworkitems(toplevel workitems).Thisensuresthatworkitemsthatarestillbeingprocessedarenotarchived. Workitemsdependentontheselectedworkitemsarealsoarchivedautomatically(forexamplework itemsthatarepartofanSAP Workflow).ThisrecursionisperformedinternallybytheFORMroutine READ_WORKITEM_DATA_FROM_DB.IfyousettheindicatorOutputworkitemsaslist,the selectedworkitemsareoutputinalist. Fordetailedinformation,refertoDataManagementGuideinSAPServiceMarketplace. http://service.sap.com/ilmDataArchivingMediaLibraryLiteratureandBrochuresData

ManagementGuide(PDFfile)

BestPractice:SAPWorkflowMonitoring Copyright2007SAPAG.Allrightsreserved.
Nopartofthispublicationmaybereproducedortransmittedinanyformorforanypurposewithouttheexpresspermission ofSAPAG.Theinformationcontainedhereinmaybechangedwithoutpriornotice. SomesoftwareproductsmarketedbySAPAGanditsdistributorscontainproprietarysoftwarecomponentsofothersoftware vendors. Microsoft ,WINDOWS ,NT ,EXCEL ,Word ,PowerPoint andSQLServer areregisteredtrademarksof MicrosoftCorporation. IBM ,DB2 ,OS/2 ,DB2/6000 ,ParallelSysplex ,MVS/ESA ,RS/6000 ,AIX ,S/390 ,AS/400 ,OS/390 ,and OS/400 areregisteredtrademarksofIBMCorporation. ORACLE isaregisteredtrademarkofORACLECorporation. TM INFORMIX OnLineforSAPandInformix DynamicServer areregisteredtrademarksofInformixSoftware Incorporated. UNIX ,X/Open ,OSF/1 ,andMotif areregisteredtrademarksoftheOpenGroup. HTML,DHTML,XML,XHTMLaretrademarksorregisteredtrademarksofW3C ,WorldWideWebConsortium, MassachusettsInstituteofTechnology. JAVA isaregisteredtrademarkofSunMicrosystems,Inc.JAVASCRIPT isaregisteredtrademarkofSunMicrosystems, Inc.,usedunderlicensefortechnologyinventedandimplementedbyNetscape. SAP,SAPLogo,R/2,RIVA,R/3,ABAP,SAPArchiveLink,SAPBusinessSAPWorkflow,WebFlow,SAPEarlyWatch, BAPI,SAPPHIRE,ManagementCockpit,mySAP.comLogoandmySAP.comaretrademarksorregisteredtrademarksof SAPAGinGermanyandinseveralothercountriesallovertheworld.Allotherproductsmentionedaretrademarksor registeredtrademarksoftheirrespectivecompanies. Disclaimer : SAPAGassumesnoresponsibilityforerrorsoromissionsinthesematerials.Thesematerialsareprovidedas iswithoutawarrantyofanykind,eitherexpressorimplied,includingbutnotlimitedto,theimpliedwarrantiesof merchantability,fitnessforaparticularpurpose,ornoninfringement. SAPshallnotbeliablefordamagesofanykindincludingwithoutlimitationdirect,special,indirect,orconsequential damagesthatmayresultfromtheuseofthesematerials.SAPdoesnotwarranttheaccuracyorcompletenessofthe information,text,graphics,linksorotheritemscontainedwithinthesematerials.SAPhasnocontrolovertheinformation thatyoumayaccessthroughtheuseofhotlinkscontainedinthesematerialsanddoesnotendorseyouruseofthirdparty Webpagesnor provideanywarrantywhatsoeverrelatingtothirdpartyWebpages.