Hi All - I hope you agree with me that we'd all benefit from capturing the name of the shopping list on the requisition line when a user adds an item from their list.
Currently, there is no data capture from procurement templates when users add items to their orders from RSS or FSM while shopping from a procurement template (shopping list). We propose adding a field that captures the name of the shopping list if the user selects an item from their shopping list, similar to how contract lines are denoted for pricing. This field would only populate when items are selected from the shopping list page, not when searching the catalog. This is important because an item can exist on multiple templates, and we need to identify when users shop from templates and which templates are being used.
This enhancement would allow us to fine-tune shopping lists, improving the ordering process for end users. Additionally, capturing data on item template usage could serve as a valuable data point in requisition approvals. By aggregating item selections from shopping lists, we can maintain more accurate records, thereby improving item maintenance processes.
We currently have no way of identifying which templates are being used. As a result, shopping lists can grow unchecked, without data to support the addition of new lists or items. This unchecked growth adds clutter, weakening the lists’ intended purpose and driving users to search the catalog instead.
Please go out and vote for this! Even if you don't really see the use in your organization 
I'll return the favor! Thank you.
mingle-portal.us2.prd3.inforcloudsuite.com/.../
