SRM PO Workflow - controlling workflow re-trigger of an approved PO

[former_member635449]

Hi Experts,

Hope you are doing well.

I have been trying to find a solution for a requirement where I need to prevent the workflow retrigger of an approved PO which has been replicated to backend. Based on certain conditions.

So far I what I have been able to achieve is that if the user adds a text or attaches a document to an approved PO it does not trigger the workflow and it shows system approved in the workflow log in portal.

What I have not been able to achieve is when the user reduces the amount of the PO it should not trigger the workflow but no matter what I do it always triggers the workflow.

P.S. I have written the coding in a FM which is attached to the first step in BRF schema.

Help with this is much appreciated. I have tried to find a solution for this online but none of them really worked.

Thanks in advance for your help.

[former_member314400]

Hello! Indeed, every time when a new change version of a document is created, a workflow instance needs to be started. If you don't want to route workitems to "real" approvers just implement your first level with an evaluation where you check if the value entered in the change version is lower or higher than the value of the active version. If this level is True because the the value is lower, then your level should trigger the automatic approval, thus no need for decision from approvers. For further levels just make a check in the evaluation which is checking if there was a first level. If yes, then no action needed and they can be evaluated as false. However if the value was higher than the active version's then these levels are started and actual agents receive workitem tasks.

Best Regards

Zoltán

[former_member635449]

Thanks Zoltan, will try that and let you know.

[former_member635449]

Can you elaborate "For further levels just make a check in the evaluation which is checking if there was a first level." ?

[former_member314400]

Under this I meant, that in case of PC WFL you need to set up the evaluation ID in the process schema configuration. This evaluation ID can be connected to a BRF evaluation, where you can create your own logics or you can connect it also by creating an custom BRF evaluation to a custom Function module, where you check and implement your requirements.

[ramki_maley]

Any change triggers workflow. If you do not want to go through the approval process, you should send the document to an auto approval schema. That means you need to have more than one schema and dynamically assign the appropriate schema.

HTH.

Ramki Maley.