Comments
This issue is needed as we are also having requestors select the procurement headings in error when populating PR lines. This causes a distribution error message which prevents the user from submitting the PR.
Once the heading is selected as a procurement category, the user is not able to change it. Instead they need to delete the line and enter it again.
As the headings are not linked to any GL account etc, the system should not allow a user to select them as a procurement category.
Please include this fix in your roadmap if possible.
Category: Procurement and Sourcing
Procurement categories tree structures are used to default data on higher levels. But for reporting and financial purposes more specific categories are needed. We can't assume the user to know on which levels they may and may not purchase goods/services. Also it is not possible for the purchase department to change the procurement category or item on a PR line afterwards so this is also not helpfull.
Please reconsider this for your roadmap.
Category: Procurement and Sourcing
This is needed because the form doesn't give the user an error message when they select the parent node. The order will go through the process until receipt where it will error and then the order goes back to be fixed and approved again. Too many steps and time waster that can be avoided if the user is not allowed to pick the parent node to begin with or at the very least receive an error message.
Category: Procurement and Sourcing
Administrator on 9/30/2020 12:44:27 PM
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,
Mai Kirknel
PM, Microsoft