132

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.


 

Category: Planning
STATUS DETAILS
Under Review
Ideas Administrator

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

P

This is a real bottleneck that we are facing, as a work around we have switched off update "Latest purchase price" this makes Buyers to open every purchase order and enter unit price manually. This not only increased work for buyers but we are now having issues with some analytical report as "last purchase Price" is blank . Having a PO in Approved status through MRP gives away control from Purchasing manger .

I think every entity that is going to use MRP will feel the pain without this fix, please get this on your rod map

Category: Planning

P

We achieved this with a customization in a customer project. The idea was that Purchase orders created from a Planned purchase order receive the status "Draft". Thereby, it is possible to use the standard Purchase order workflow.

In the further ongoing of the project, we implemented a Purchasing policy that defines which field of a Purchase order need a re-approval if changed.

Thereby, we were confronted with the following issue: the system does not evaluate Purchase orders created from Planned purchase orders as changed. Therefore, Purchase orders created from Planned purchase orders are automatically approved.

We set up the Purchasing policy in a way that if e.g. the total amount of the Purchase order changes, a re-approval is required. When creating a new Purchase order manually, you enter an item with a price and therefore, the total amount is "changed" - PO runs through the workflow.

But if you create the PO from the Planned PO, the system does not evaluate the amount as changed - therefore, the re-approval rule is not triggered and the Purchase order runs through the automatic approval (depends on the setup of the workflow).

So far, we did not solve this issue - but simply giving the status "Draft" to Purchase orders created from Planned Purchase orders does not fulfill the whole requirement.

Category: Planning

P

Absolute must have, I couldn't believe this behavior when testing a specific scenario.

Category: Planning

P

We would need to have the option to set purchase orders created from a planned purchase order to status draft in order to comply with company rules that all purchase ordes must have been approved from at least one manager before it may be send out to the supplier.

Category: Planning

P

I cannot comprehend why the functionality - or at least the option to kick firm planned POs into approval workflow for those who have absolute confidence planning recommendations - would not be delivered as standard. Just because master-planning generates the recommendations, it certainly does not mean they are automatically correct.

There are many examples for this that I could reel off, but I'll stick to one example. Within the masterplanning parameters (module level) allow you to define to select whether the search criterion is minimum lead time or minimum unit price. The businesses preference might be different for different groups of products.

Having the option for more senior staff member to 'genuinely approve' POs about a certain level of spend would help safeguard the business (and the junior staff processing the POs) against accidental/incorrect POs.

Category: Planning

P

I'd say it is not required. There are already controls in place to authorize purchase requisitions and manual created purchase orders through workflow approval.

From a leading supply chain management practice point of view I'd say controls shall be added prior to the MRP run. Forecast, min / max coverage groups etc. shall be authorized and reviewed.

If there is another control in place to authorize purchase orders that have been created by MRP it leads to bad customer experience and highlights a failure of controls that authorize forecast and coverage groups in the first place.

Category: Planning

P

We have same Issue in our business, I dont know why have missed this issue.

Category: Planning

P

The workflow could be instead on the planned orders themselves, but then as Nicholas Cram said we would need to be able to see the value of a group of selected planned orders.
If a PO is created from master planning it needs to generate inventory transactions, otherwise a subsequent run of the MRP will generate new planned orders.

Category: Planning

P

Hello all,

A PO that has been created by firming a planned order from master planning is always set to a status of Approved, regardless of the change management settings. This is indeed a problem in my organisation where MRP is run by junior staff who's not authorised to approve POs. We definitely need a workflow for firmed planned POs so these can go to relevant senior staff for approval. Ability to approve all kind of POs should be a fundamental feature of any ERP system and should not be dependant on the source of the PO (i.e. purchase agreement/master planning suggestion etc.). For companies where tightly controlled purchase agreements exist, PO auto approval can be made optional in settings for any POs derived from such agreements.

Microsoft, please consider this favourably as soon as possible as I would hate to ask our implementation partner to create customisation to provide this basic functionality.

Thanks,

Amit

Category: Planning

P

We need to make sure this functionality can be controlled by a coverage group setting. Purchase orders that are released for example based on purchase agreements may not need workflow for approval. Other conditions may be purchase that is within budgets of projects or simply parts where the planner has the autorisation to buy.

Category: Planning