Another “feature” of Reqs (which caught us off guard at first… we just kind of stumbled on it)… a part requisitioned referencing a Job will be added as a job material automatically if the requisition is converted to a PO. And this could be a part-on-the-fly.
For example, our final assembly department needs a hose clamp from McMasterCarr… they put in a requisition for a job material. That part (and McMasterCarr P/N) will show up as a material on the job once the PO is created and approved.
That being said, we’ve seen a lot of unexplained behavior with Reqs falling through the cracks in the system (a req with 4 lines… 3 get converted and the other just hangs there like it was never dispatched). You can actually go back into the Req and re-dispatch and then that line comes through. Not sure why that happens, but its difficult to monitor. We always assumed this was probably “a Kinetic thing” (we’ve never used Classic Requisitions). Its hit or miss and hard to reproduce on demand. So, the trust level here for requisition system was in the toilet.
Because the Requisitioner is doing most of the work already… part info, supplier info, demand info… we’ve actually started moving away from Requisitions and started using Tim’s approach in the post below:
“simply create buyers for all employees that make requisitions, and assign those “buyers” a $1 limit. Then have them create their own POs which need to go through the PO approval process, skipping the requisition altogether.”