10

After Workflow PO approval, changes to any PO field automatically requires Workflow, even if automatically approved. Would prefer option on selected fields to be excluded from Workflow, upon changing after PO approval. These fields should not impact PO pricing and may not be know prior to original PO approval. Examples include:

  • Confirmed delivery date @ PO header & line level
  • External part# - PO Line details > General > Reference > External - PurchLine_ExternaItemId
  • Text Item description - PO Line details > General > Text - PurchLine_Name

With complex Workflows and volume of POs being processed, this would improve process efficiency and avoid timing delays within Workflow, even with automatic approval.

STATUS DETAILS
Needs Votes
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.

Comments

D

There is a purchase directive that allows evaluating the fields in the flow, it does not solve the problem 100% but it can be an alternative, in my case the only thing I needed was not to require approval again when rescheduling delivery, but it did not help me the directive, since when it opens in 2 lines it considers it a change

https://docs.microsoft.com/es-es/dynamics365/supply-chain/procurement/purchase-policies


Category: Procurement and Sourcing