2790296 - Fields which trigger a re-start of Flexible workflow for Purchase Contracts

You work with Flexible Workflow for Purchase Contract.

Change of purchase contract during approval is not possible. But it is possible to change the released/rejected contract.

In this case there is a logic; checking what was changed in the contract. This is by comparing the changed fields with the fields of a reference structure.

In the App  Manage Purchase Contract, there are 4 relevant fields which are editable, so changes on them will  retrigger the workflow.

S/4HANA Cloud

These are the relevant fields  which  retrigger the workflow based on the document type

Validity end date  -  Quantity & Value Contract 

Material Group    -  Quantity & Value Contract

Target Quantity at item level - Quantity Contract

Target Value        - Value Contract

The other way for the workflow is going to process again is in the LMEOUTP1C include into the me->fill_cekko. 
    
Every field inside of the CEKKO will be checked to compare the old CEKKO and new CEKKO, and If they are different, the workflow will be going to approval again.
    
The Method FILL_CEKKO of Include LMEOUTP1C. Here the system fills the OLD structure and the new structure.

KBA , MM-FIO-PUR-SQ-CON , Fiori UI for Manage Purchase Contracts , Problem