In the current version of RSS (not LPL) has anyone encountered requester specific errors that cannot be recreated by another requester that follows the same requisition entry process?
We have at least one requester that occasionally has requisitions with multiple lines that could and should all be on a single PO, but instead will create separate POs for each requisition line.
For example, the requisition has 12 lines that all have the same ship to, vendor, buyer, etc. that should create a single PO, but instead it create 12 single line POs.
In V10, we would often find various errors that would be specific to the requester and there was a process to clear requester cookies.
I've opened a few tickets with Infor, and they are focused on trying to recreate the problem.
While I understand that approach generally, I don't think it's addressing the requester specific part of the problem.
I'm curious if anyone else has encountered a similar problem and found a good solution.
Thanks!
Gretchen Tesché
