Symptom
Required Flexible Workflow at Header Level based on Plant Condition
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Create a purchase requisition with many line items.
- Activate flexible workflow for purchase requisitions at item level.
- Observe that multiple approval tasks are created (one per line item).
- Open Manage Workflows for Purchase Requisitions and review available start/step conditions; note that Plant is not available as a condition field.
Cause
By design, plant-based approval determination is not supported: PR workflows do not offer Plant as a condition field, and PO workflows evaluate at header level where Plant is not supported.
Resolution
- Note the standard limitation: plant-wise approval determination for PRs and POs is not supported by flexible workflow in the product.
- If Plant must be evaluated, define a custom pre-condition/step condition by creating a custom condition definition (SWF_WORKFLOW_CONDITION_DEF) so that Plant can be used as a condition.
- Implement and activate the custom condition definition as described in the referenced note.
- In Manage Workflows for the relevant procurement scenario, add the new custom pre-condition/step condition to the workflow definition.
- Test the workflow to confirm approval determination using the Plant condition and adjust as required.
See Also
Keywords
flexible workflow, purchase requisition, pr workflow, header level, plant condition, plant-based approval, manage workflows, pre-condition, step condition, swf_workflow_condition_def, procurement workflow, item-level approvals, approval tasks, s/4hana cloud public edition, missing condition field , KBA , MM-FIO-PUR-REL-2CL , Fiori UI for Purchasing Approval (Public Cloud) , Problem
SAP Knowledge Base Article - Public