SAP Knowledge Base Article - Public

3781915 - The PO workflow restarted after changing a field irrespective of SSCUI or BADI

Symptom

  •  What is the reason that caused the restart.
  •  How to stop the workflow restart

Environment

SAP S/4HANA Cloud Public Edition

Cause

 For example:

1.The total value of the Purchase Order Changed

2.header text or  item text are changed

3.Tax code is changed

Resolution

  1. Open the Purchase Order, go to  change log and add or resize the “Changed On” column to verify all changes that are either manual or automatic.
  2. Acknowledge that a change to the total value is considered critical and, by default, restarts the flexible workflow.
  3. If re-approval should be avoided for any fields change, configure the restart behavior using SSCUI 103345 or with BAdI MMPUR_PO_WORKFLOW_RESTART to disable workflow restart for the relevant field/change.
  4. Review custom logic in the Custom Logic app to ensure no explicit workflow restart is implemented for this scenario.
  5. After adjusting configuration/logic as required, process the Purchase Order and run the workflow as per governance.

 Note: details are applicable for any document not just PO.

See Also

Keywords

purchase order, flexible workflow, re-approval, restart, custom field change, total value change, approve without workflow, change log, badi mmpur_po_workflow_restart, sscui 103345, po approval status, workflow control, public cloud, operational procurement, po processing , KBA , MM-FIO-PUR-PO-WFL-CL , Purchase Order Workflow (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions