Suggested by Chin Hung Yang – Needs Votes
Looking for a way to designate a parent node in a procurement hierarchy as a parent, and not allow a user to select and use the parent category on a requisition, purchase order, and vendor invoice. Currently, there isn't a direct way to prevent user from selecting a parent node.
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,
Mai Kirknel
PM, Microsoft
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.
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.
Hello,
Has anyone been able to obtain feedback from Microsoft on this idea?
Is it still on the road map or not ?
Thank you in advance for your help !