549

Suggested by Peter Hao Under Review 

After planned purchase orders are firmed, the ‘Approval status’ is default to ‘Approved’ on purchase order screen, which is skipping the purchase order workflow. Suggest to default the ‘Approval status’ to ‘Draft’ while workflow is enabled; or have a parameter like 'require workflow' to control planned purchase orders. Then the workflow process should work the same way as any other manually created purchase orders.

The reason is: the 'approve' and 'firm' on the planned order screen is normally used by the planning / purchasing department, then workflow is still required from purchase authorisation / financial point of view.

 

Status Details

Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.

 

Sincerely,

Roxana Diaconu

PM, Microsoft

Comments (57)
  • Frankly, it's absurd that Microsoft has ignored this topic. As has been suggested dozens (hundreds?) of times, a simple parameter like "Auto-approve firmed orders" solves this issue entirely, and is most likely being implemented via custom code by most customers anyway. I just can't imagine why a company which has chosen to enable Change Management would want their Planning group to approve every purchase order.

  • This should be out of the box functionality, multiple companies are modifying this to ensure all their purchase orders are going through approval workflow.

  • This is a crucial function that many customers require. Please take it into the roadmap asap.

  • Hi All,


    Hope you're doing well!


    Great news! Microsoft has simplified the process. Now, with a simple customization, we can create purchase orders in draft status when firming planned orders.


    For more details about the customization, you can refer to my blog:


    https://d365fandotech.blogspot.com/2024/07/set-purchase-order-workflow-status-as.html

  • Hello MS team,


    could we have an update about the planning of the feature release? did you add this topic to your roadmap ?


    Thank you

  • the problem is, that purchase orders in draft status won´t show up in net requirements.


    In Detail:

    1. Master planning creates a planned purchase order to fulfill demand
    2. buyer firms the planned order into a purchase order
    3. If you have a customization that puts the purchase order into draft status, the purchase order does not show up in net requirements
    4. next master planning run will create another planned purchase order
    5. buyer firms again
    6. and again
    7. and again
    8. happens until the first firmed purchase order is in status "approved".
  • Happy this is under review, I see this request a lot.