0 ratings0% found this document useful (0 votes) 371 views2 pagesSAP Workflow Debug
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content,
claim it here.
Available Formats
Download as PDF or read online on Scribd
EID 2197147 - Debugging of background work items.
Version 2 Validity: 06.08.2015 - active Language English
Header Data
Released On 06.082015 07:56:13
Release Status Released for Customer
Component —8C-BMT-WFM-RUN Runtime
Priority Comraction with medium priority
Category Program error
Symptom
Improvement Request
itis po passible to debug methods at are exeste in orto backround werkitams
Request Reason
‘me debugging 's possible ny wih increased configuration efor. System auhonzations are requred forte necessary corigaaton changes
Fatberoe, the system changes are acve ote ee workon rustime system
Other Terms
Workiiow Customer Connect 2015, breakpoint, debugging
Reason and Prerequisites
‘Solution
Improvement
After you import the relevant Support Package, a simple option for debugging a workslow background work item is available. To activate the
debugging, cary out the fllowing steps.
41. Inthe relevant background method, set an external breakpoint
2. Activate the workliow debugging with the new transaction SWW_BREAKPOINT.
‘© The debugging o the workflow runtime system can be activated for a worklow. Ente the relevant top4evel workflow inthe eld "Top
Task" With this configuration, the debugging is activated for allbackground work items started from within the context of the current
user A simple case, for examples the restart of an incorrect workflow.
f Fyoualso want fo debug methods that are startad from within the context of an event, enter the name of he abject type as well. As a
resut, the debugging is activated for all use cases (such as start events, termination events, and s0 on)
«The waikliow breakpoint is active for half an hour
3. ‘After youhave executed the actions described, the workiow debugging is active. After the relovant workflow activity (such as restarting) is
‘exeoaled, the external debugging ofthe ABAP runtime is actvated. Ina new mode, the system displays the debugger in place ofthe source
Code at which you set the exesnal breakpoint.
[Note that he workfiow debugging is activated fora specific server and yau therefore must execute the activation ofthe breakpoint and the
lnggenng ofthe action (such as restating) onthe same application server
‘Technical background informatio
‘The extemal debugging is possible ony for dialog users because the debugging is Inked tothe WWINGUI session Due to this specified general
Condition, the workflow debugging is realized as folows. The destination NONE, which always exsts, is used instead of he standard workiow
destination, This means the background steps or the event receiver are executed in a new IRF context, but under te current user and no longer
Under the workflow system user WF-BATCH
Benefit
‘The testing and verification of methods used in workow is simplified toa large degree. The workflow developer or woriliow support can be
analyzed vary quickiy using the option for debugging problems.
Delvery
‘The deivery can be carried out only ia a Support Package because the development includes some objects that cannot be implemented using
conection instructions
‘Note thatthe setting of an external breakpoint in BOR methods is made possible with SAP Note 2192937. Other Attributes
Tepe Worktiow
rocwstene [Customer Connect 2015
prorat ow [YO
Validity
-FromRel ToRel, And Subsequent
731 | 731 a
740 |740 a
750___|750 a
‘Support Packages & Patches
'SAPK.7500INSAPBASIS
References
This document refers to:
SAP Notes
2192237 Support of external breakpoints in BOR abjacis
