cancel
Showing results for 
Search instead for 
Did you mean: 

PR Workflow - automatic approval of 3.rd step when the same approver

veronika_skybova
Explorer
371

Hello Experts, I have a question regarding workflow approval process. We would like to know if it is possible to auto approve 3.rd step when the second and third approver is the same person. Can the PR be automatically approved after the second approval (so that the third approval by the second person is not required)?

Currently we have implemented a BADI agent determination and these agents are defined in custom business object UI table.

We have try add empty approver to badi "Determination of Workflow Agents for Purchasing Documents", but it was not working for us, we have got this message: 

veronika_skybova_0-1707983484252.png


We are working in s4hana public cloud environment.

Thank you very much for all your responses and help.

View Entire Topic
MariusSiegel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear @veronika_skybova,

You could make use of the Exclusion of restricted Agents using the BAdI 'MMPUR_WFL_CONTEXT_ENHANCE'.

You can find this info in the SAP Help Portal here:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/0e602d466b99490187fcbb30d1dc897c/2c6e00fd27944d7aa6a2ff12...

 

Caution: After exclusion, if no recipients are determined, the workflow will move to error unless the step is marked optional.  If a workflow step is marked optional and an approver cannot be determined for the step then the step gets skipped, and the workflow automatically moves to the next step or will be approved.

 

best regards,

Marius

 

 

veronika_skybova
Explorer
0 Kudos

Dear Experts, We have a little problem with settings of the PR workflow. We are working in S4/Hana public cloud environment. We followed the steps from the SAP site. We have set the Step Properties as optional and added the option “Exclude Restricted Agents Determined by BADI”.

veronika_skybova_0-1725961432496.png

We created BAdi with ID „MMPUR_WFL_CONTEXT_ENHANCE“. With this setting, we expected it to run automatically in PR process and before setting up approvers or approving, this Badi „MMPUR_WFL_CONTEXT_ENHANCE“ will be called. We also set up a Business Object for BADI but the behavior of the process did not change.
Are we missing something in the workflow settings? Can you please help us?

Trang-To
Discoverer
0 Kudos
Hi Marius, do you have any update for us regarding the problem with the BADl MMPUR_WFL_CONTEXT_ENHANCE as described below?