Skip to Content

Approver determination for Fiori Approve Purchase Orders

Hi Experts,

We have set up the standard Fiori Approve Purchase Orders application and are able to access it from the Launchpad.

I have a question pertaining to the approver determination in the Fiori app - in our case the release strategy is not constant and we are determining the approver users from an exit dynamically on the basis of cost center, material group and total amount of PO.

So we cannot maintain the entries in the table in SPRO -> Materials Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders -> Define Release Procedure for Purchase Orders -> Workflow.


With this, how can we make sure that the corresponding workitems are shown for the approver users when they open the Approve PO Fiori app? Currently even though the approver user has some POs pending in the SAP Inbox, the same are not being fetched and shown in the Approve PO Fiori app - the count of workitems in the app tile is shown as 0.

Regards,

Saurabh

approver_ids.png (12.3 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jun 27, 2015 at 03:22 PM

    Saurabh

    Did you do this step?

    Specify the workflow tasks that are relevant for approving purchase orders. You do this in Customizing forMaterials Management under Start of the navigation path Purchasing Next navigation stepPurchase Order Next navigation stepApprove Purchase Orders App Next navigation stepSpecify Workflow Task IDs for Approve Purchase Orders App End of the navigation path. For more information, see the documentation available in Customizing.

    From App Implementation: Approve Purchase Orders - SAP Fiori Apps - SAP Library

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Masa,

      We corrected the trusted RFC connection setup and the RFC destination settings as per the link you provided, and now the issue is resolved. The Approve Purchase Orders app is working perfectly now.

      As always, thanks a lot for your invaluable inputs and support!

      Regards,

      Saurabh