SAP Workflow Error Analysis TCodes

SAP Workflow Error Analysis TCodes: You can use T-code: SWI2_DIAG (Diagnosis of Workflows with Errors) – which is defined as the standard SAP code available within R/3 SAP systems depending on your version and release. You can see the error cause in the workflow diagnosis and also “Restart workflow”

SAP Business Workflows With Errors :

Below are the SAP Workflow error analysis transaction codes to troubleshoot workflow errors.

TcodeDescription
SWF_FOOTPRINTDatabase Footprint Workflow Tables
SWI1Work Item Retrieval
SWI11Where-Used List for Tasks
SWI13Task Profile
SWI14Workflows for Object Type
SWI1_CONDCheck Conditions for Work Items
SWI1_RULEExecute Rules for Work Items
SWI2_ADM1Work Items Without Agents
SWI2_ADM1_CLOUDWork Items Without Agents
SWI2_ADM2Work Items with Deleted Users
SWI2_DEADWork Items with Monitored Deadlines
SWI2_DIAGDiagnosis of Workflows with Errors
SWI2_DURAWork Items by Processing Duration
SWI2_FREQWork Items per Task
SWI3Workflow Outbox
SWI30Unlock Workflows
SWI5Workload Analysis
SWI5NWorkload Analysis
SWI6Workflows for Object
SWIAAdministration Work Items
SWIADM1Display Work Items without Agents
SWIADM2Display Work Items w. deleted Agents
SWIEUnlock Work Item
SWI_ADM_CLOUDWorkflow Administration
SWI_DIA_TASKDialog Tasks Statistics
SWI_HC_CLOUDWorkflows with Issues
SWI_PR_CLOUDWorkflows in Status Error
SWRPDummy for IAC Workflow Status

You can also list top workitems with errors in Workflow. SAP List viewer in ABAP system is used to view the workflow with errors and these are grouped based on error reason. Following are the possible causes of workflow errors −

  • Agent
  • Deadlines
  • Binding from workflow to workitem
  • Other

You can access the processing of workflows with errors navigating to this path: Tools → Business Workflow → Administration → Workflow Runtime → Diagnosis of Workflows with Errors.

You can use T-code: SWI2_DIAG (Diagnosis of Workflows with Errors) – which is defined as the standard SAP code available within R/3 SAP systems depending on your version and release.

Determining Events That Are Triggered By a Workflow Template

Use :

If a process is started with the start application in the Portal, the system triggers an event CL_HRASR00_WF_PROCESS_OBJECT.TRIGGERED in the back-end system to start the workflow. At runtime you can check in the event trace to see which events were triggered and which workflow templates used the event.

Procedure

  1. Choose transaction SWEL (Display Event Trace) , or from the SAP Easy Access screen, choose Tools  Business Workflow   Utilities  Events  Event Trace  Display Event Trace .
  2. Enter CL_HRASR00_WF_PROCESS_OBJECT in the ‘Creator’ Object Type field.
  3. In the Event field, enter TRIGGERED .
  4. Fill additional selection criteria as required.
  5. Set the Only Events with Linkages indicator, or if necessary the With and Without Linkages indicator.
  6. Choose Execute .The system issues a list of the workflow templates that have used the event CL_HRASR00_WF_PROCESS_OBJECT.TRIGGERED.In the output you see when the event was generated for the class of workflow templates that react to the event. The workflow templates that have also processed the event are indicated by a green disk in the Information column. To display detailed information about the entry, double-click the entry.
  7. It is possible that you are missing an entry for a workflow template. If this is the case, check the following:
    • Is the event trace enabled?
    • Are there restrictions in place that define which events the system follows up?In the output list menu, choose Goto  Switch Event Trace On/Off .
  8. Check whether the Event Trace Switched On indicator is set. If so, this cannot be the reason that the entry is missing.
  9. Check whether there are restrictions in place.If the symbol on the Restrictions for Trace pushbutton is gray, there are no restrictions in place. If the symbol is colored, check whether restrictions are in place for the class CL_HRASR00_WF_PROCESS_OBJECT. Remove these restrictions if necessary.For more information, see the SAP Business Workflow documentation, by choosing Reference Documentation  Workflow System Administration  Event Manager Administration .
  • Related Posts

    Attachments for SAP XI/PI – ARIBA Invoices sent via PI to S/4HANA

    Integration with SAP systems has never been more intriguing, especially with Ariba, Workday, Concur, Successfactors, Fieldglass, Hybris, and other satellite cloud solution vendors banging on doors every day. 🙂 I…

    11 Steps to Include a New Field in an Already-Existing SAP LSMW Batch Input Recording

    Alright. Why in the world do we care about LSMW in this paper when S/4HANA migration cockpit should ideally replace it? 🔥🎥 The simple answer is that not all people…

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    You Missed

    SAP XI/PI – Invoice Attachment Transfer from ARIBA to VIM

    • By Varad
    • November 8, 2024
    • 2 views
    SAP XI/PI – Invoice Attachment Transfer from ARIBA to VIM

    11 Steps to Include a New Field in an Already-Existing SAP LSMW Batch Input Recording

    • By Varad
    • November 6, 2024
    • 2 views

    Part 23 of ABAP for SAP HANA. How Can AMDP Be Used to Access Database Schema Dynamically?

    • By Varad
    • November 4, 2024
    • 2 views

    S/4HANA VDM 1 Employing CDS Virtual Data Model for Embedded Analytics

    • By Varad
    • November 1, 2024
    • 5 views