WF problem with different release codes for the same approver

[Former Member]

Hi guys,

we are currently facing this problem.

We have 2 release codes:

1. RE (Requestor)

2. BC (Budget Coordinator)

Email will be sent to BC after RE approved.

It happened that CLKOO is both RE and BC.

Once CLKOO released using RE , system will automatically approved BC also.

(We are not sure if this is supposed to happend as standard feature , can anybody advice ).

In the WF log, i checked that there are 2 active WFs, both sending to CLKOO's SBWP as BC email notification to approve, whereas BC has been approved automatically when RE was released.

CLKOO is curious to see that why 2 notifications are still sitting in her inbox. To her , once she approved , she expected nothing left in the inbox.

How can i prevent this from happening? shall i change the WF logic or is there anyway to settle

[KKilhavn]

> In the WF log, i checked that there are 2 active WFs, both sending to CLKOO's SBWP as BC email notification to approve, whereas BC has been approved automatically when RE was released.

>

> CLKOO is curious to see that why 2 notifications are still sitting in her inbox. To her , once she approved , she expected nothing left in the inbox.

>

A sensible thing to expect, so apparently nothing wrong with your user

In addition to the suggestions you already have received, check SM58 in case the terminating events were created, but not delivered. It has happened before....

[Former Member]

Hello Ester,

an automated approval, such in

<i>> Once CLKOO released using RE , system will

> automatically approved BC also.

> (We are not sure if this is supposed to happend as

> standard feature , can anybody advice ).</i>

is <b>not a standard</b> feature.

However, the user may have set both release codes in one go, using the enjoy release transaction (ME54N for requisitions, ME29N for purchase orders)

For each release code that is currently required, i.e. RE + BC at the same time, there will be one workflow each (if using the standard release workflow here). And yes, after both approvals are set (at the same time or one after another doesn't matter), both release work items have to disappear.

So please check around the event triggering, event coupling, instance coupling for BUS2105.Released / BUS2012.Released + the user exits / BADIs in the release process, what's not part of the standard.

Best regards,

Florin

[Former Member]

Hi Ester,

Just switch on SWEL and check the event which is triggered when you create a PR or PO and check the container to see which release code is passing and make sure only one template gets activated at one time( in case there are more than one template is attached to this triggering event ). If at any time one event gets triggered then you should get only one workitem( Notification) at one time in SBWP.

Do let me know if this problem persists..

Thanks,

Sudhi

[Former Member]

Hi

I think the approver is not manually releasing the PO or PR using Tcode ME29n. If the workflow functionality is like that you cannot restrict it. But if in the Workflow design you are releasing the PO and PR by standard method then the PO and PR will be released depending on the sequence of Release Code. In this case you can restrict the user from Releasing both the release Code. There is probably standard method in the respective Business Object which you can use.

<b>Reward points if useful</b>

[Former Member]

Hi,

this is standared behaviour that if some buddy have both the authorization then why he/she have to approve twices and about notification just check what is the text in notification.

Atul