Users statement is listed below...
"REQ ******* was placed and never populated to a PO for company ****. Now this REQ is closed, but we have no information on why this would of closed. Please review req ******* and inform us why this didn't process"
I have researched the obvious areas, RQ10, RQ44, RQC to recreate the req. in test environment. Does anyone know how a req would be released, never make it to a PO, and then the req get closed?
Is it possible somebody Rejected the req? What value does the field reqheader.status have? 0 = Unreleased 1 = Released 5 = In Process 9 = Processed 8 = Rejected
Sorry I'm not seeing a field within the Header that points to the numbers you posted. What I do see everywhere I Drill Around is below... Requesting Location: 5111 MICROBIOLOGY Transaction Type: Issues Status: Processed Closed Flag: Yes Creation Date: 01/21/2020 Time: 10051300 Operator ID: rquser Released Date: 01/21/2020 Time: 10081600 Operator ID: rquser Processed/Rejected Date: 01/21/2020 Time: 10081600 Operator ID: rquser Return Notes: Approval Type: No approval required Approval Code: Header Source: RQC
Also, we don't utilize an approval process so this req would've shot straight to PO23 - which never happened, and the req closed.
Sorry, I should've stated that this is a special req.
Did they enter a vendor? Not sure if you have this required in RQ04 or not.
Yes a vendor was set in the req. Also rq04 for the requester is flagged to require vendor.
That's a good thought with the PO100.err. We will be looking to see if that still exists from January and if not we're about to throw in the towel. Couple weeks ago I had an Infor ticket open for a similar incident and they threw in the towel after a week and a half.
Lawson version 10.0.9.0