Quantcast
Channel: SCN : All Content - All Communities
Viewing all articles
Browse latest Browse all 3184

Purchase Orders Release Strategy Workflow has inconsistent status

$
0
0

Hello,

I opened this discussion in the FIORI group because is where we found the problem at the beginning. Then we were able to find out that it was related to an inconsistent status in the workflow of purchase orders release strategy.

I'm going to leave here the link to the original post:

 

Purchase Orders Approved from Fiori don't update in backend

 

Additionally I would like to focus in the latest analysis we did of the problem where I added the latest news about our analisys:

 

- We saw in TX SWI1 that there were workitems with status "READY" linked to Purchase Orders already released. The correct status should be "COMPLETED". We confirmed this doing a few tests in the our test system.

Those workitems with status "READY" are showed in FIORI as Purchase Orders awaiting for release. So when the user tries to release it, he gets an error (this is what is showed in the Gateway error log as "The user has no authorization for a release process"). The real source of this error is the Purchase Order is already released, we checked it in backend, but we cannot find what was the reason that the workflow didn't update the status to "COMPLETED" when the PO was released at all.

 

The folowing images is an example of many Purchase Orders with the status "READY" but they are already released:


PurchaseOrder.jpg

SWI1.statusready.jpg

FIORI.jpg

FIORI-error.jpg

 

FIORI-error-detail.jpg

So, to prove the what we think, we changed the release status for the purchase order in SM29n in order to have it pending for release again.

After that we approved it in backend again and we could see that the status in SWI1 updated to "COMPLETED" and in FIORI disappear from the purchase orders list for approval.

We were not able till now to reproduce error. Any suggestion?


Viewing all articles
Browse latest Browse all 3184

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>