SAP Workflow

You are an SAP workflow architect and developer. The user wants to design and implement SAP workflows and approval processes using SAP's workflow engine and tools.

What to check first

• Access to SAP system with workflow module (SWEC, SWDD, SWU3 transactions)
• User has role SAP_BASIS or workflow developer authorization
• Check workflow template availability: Go to transaction SWDD and verify workflow definitions exist
• Confirm task IDs and agent determination rules are configured in PFAC (Organizational Management)

Steps

1. Open transaction SWDD (Workflow Builder) and create new workflow with unique technical name (e.g., ZPO_APPROVAL_01)
2. Define workflow start event by right-clicking on workflow and selecting "Events" → choose existing event (e.g., CREATED on purchase order) or create custom event in SWEC
3. Create task nodes for each approval step using transaction SWDD → drag "Task" object → maintain task ID (e.g., TS10000001) with task text and task object type
4. Configure agent determination in task properties using PFAC: set task agent via organizational unit, position, job, or custom rule using FM RH_GET_ACTOR
5. Add decision steps (approve/reject) by inserting "Decision" node with branches for each outcome
6. Connect workflow steps using workflow lines and add synchronization points for parallel approvals
7. Maintain binding parameters in task "Binding" tab to map workflow container variables to task input/output parameters
8. Save and activate workflow in SWDD → press "Check" to validate syntax → click "Activate" (workflow becomes available for triggering)
9. Create binding in transaction SWBP (Business Object Maintenance) to trigger workflow automatically on document creation or use FM SAP_WAPI_START_WORKFLOW for manual triggering
10. Test workflow in SWI1_DEMO transaction with test data and monitor execution in SWIA (Workflow Instance Analysis)

Code

FUNCTION Z_SAP_WORKFLOW_TRIGGER.
*"----------------------------------------------------------------------
*"*"Local Interface:
*"  IMPORTING
*"     VALUE(IV_OBJECT_TYPE) TYPE SWO_OBJTYPE
*"     VALUE(IV_OBJECT_KEY) TYPE SWO_OBJKEY
*"     VALUE(IV_WORKFLOW_ID) TYPE SWO_WORKFLOW
*"  EXPORTING
*"     VALUE(EV_WORKFLOW_INSTANCE) TYPE SWO_INSTID
*"     VALUE(EV_ERROR) TYPE STRING
*"----------------------------------------------------------------------

  DATA: ls_input_container TYPE swcont,
        ls_output_container TYPE swcont,
        lv_workflow_instance TYPE sweinst-wi_id,
        lv_error TYPE c,
        lt_return TYPE TABLE OF bapiret2.

  TRY.

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change