3793452 - Debugging Flexible workflows the Badi breakpoints not hit

• The debugger does not stop at breakpoints in BAdI implementations for example  SWF_WORKFLOW_CONDITION_DEF and SWF_WORKFLOW_CONDITION_EVAL, although the implementation is active.
• No error messages are displayed.

SAP S/4HANA Cloud Public Edition

1. Set breakpoints in the above BAdI implementations and reproduce the issue.
2. Observe that the debugger does not stop at the breakpoints.

• The wrong debugger user was used. Workflow processing runs in the backend under user SAP_WFRT, so breakpoints set for a different user are not reached.

1. Set external breakpoints in the BAdI implementations SWF_WORKFLOW_CONDITION_DEF and SWF_WORKFLOW_CONDITION_EVAL specifically for user SAP_WFRT.
2. Reproduce the scenario by creating or changing a purchase requisition that meets the configured  conditions.
3. Debugger now stops at the breakpoints and proceed with analyzing the custom condition logic.

3190538 - Custom Logic Tracing for Workflow BAdis Purchase Orders and Purchase Requisitions - SAP for Me

flexible workflow, purchase requisition, PR workflow not starting, BAdI, SWF_WORKFLOW_CONDITION_DEF, SWF_WORKFLOW_CONDITION_EVAL, breakpoints not hit, SAP_WFRT, background user, workflow debug, condition evaluation, plant condition, document type condition, external breakpoint, s/4hana cloud , KBA , MM-FIO-PUR-REL-2CL , Fiori UI for Purchasing Approval (Public Cloud) , Problem