PO was aproved by strategy workflow: but it is not released.

[Claytoncbj]

Hi!

PO was aproved Nivel 1 e Nivel 2 but the status release is '1 - waiting release'.

The WF has been working for 2 years and it has never had this problem.

What do i do?

Thanks.

[JL23]

Maybe someone changed the strategy

Customizing activities have a change log as well as your purchasing document.

So you could check in both areas what actually happened.

The workflow itself... is for me just a car to get me from A to B.

[Claytoncbj]

I am ABAP and i do not idea what i can do to release this PO.

[JL23]

the customer data tab is your own development and not SAP standard, so whatever it shows is not of any relevance except you or your co-developer did something wrong here and this has a side effect to the release.

Your PO change history does not at all show any evidence for your statement: "PO was aproved Nivel 1 e Nivel 2"

So just execute ME28, enter release code WF and release group 02 and see if this can be released using standard transactions.

Of course you have to have authorization for this release code, otherwise it will not work anyway.

[Claytoncbj]

Hi, Jürgen!

We can not excecute ME28.

I found out that problem occured because the PO was opened when it was approved.

And we can change by BADI the fields in EKKO to relead the PO.

Now, the user wants that it does not allow to approve the WF process if the PO is opened.

Do you konw if it has any configuration for it or i need to change ABAP?

Thank you!

[JL23]

I dont really catch your situation, a situation like "the PO was opened when it was approved" can't actually occur as 2 persons cannot work at the same time in update mode on the same document.

So if user A was in ME22N to change the PO, and user B processed his workitem then user B should actually have received an error message " Document locked by user A" . Your workflow has of course to react on such kind of events, it must know whether the user successfully approved the document, if the approval was rejected or if the user just left the transaction without doing anything because the bell rang for lunchtime.

From your description it has to be assumed that your workflow just goes to end no matter what happened.

[Claytoncbj]

Hi!

I found out that it has a erro in the WF. And we can manually reset the process solving the problem.

Is there a possibilte to show a message error in the inbox of approver?

Thank you!

capture-wf-erro.jpg

[keohanster]

Is this consistently not working? If so, it points to what Juergen said... if it's a one-off, then check for short dumps or other system errors that could have interrupted the process.

It's also helpful to include the product and release... strategies may be different for SRM .vs. ECC....

Sue