Thanks both for your replies. I know that error description gives the idea of authorization problem, but I activated a trace with ST01 and no authorization error came up.
We have advanced in the analysis and now we have a different approach of the problem. This is what we found.
We believe that the problem is not related to FIORI, but instead with workflow and this is why:
- 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:
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?