Receiving Fails with eConnect Error 7922 "Item/Vendor Item Number Does Not Match a Line on the Purchase Order"

Receiving Fails with eConnect Error 7922 "Item/Vendor Item Number Does Not Match a Line on the Purchase Order"

Receiving Fails with eConnect Error 7922 "Item/Vendor Item Number Does Not Match a Line on the Purchase Order"

Receiving a Purchase Order line fails with eConnect error 7922. This is almost always a data-matching issue between the Vendor Item Number on the item/PO and what eConnect expects, not a PanatrackerGP defect. This article covers the usual cause and how to correct it.

Symptom

Submitting a Receiving transaction fails, and the returned eConnect error includes:

Error Number = 7922
Stored Procedure = taPopRcptLineInsert
Error Description = Item Number/Vendor Item number does not match a line on the Purchase Order

Related Error Code Parameters:
  ITEMNMBR = [item number]
  VNDITNUM = [vendor item number]
  VENDORID = [vendor ID]
  PONUMBER = [PO number]

The transaction stays in a failed state on the portal and does not post to GP until it is corrected and resubmitted.

Cause

eConnect's taPopRcptLineInsert stored procedure validates the item being received against the Vendor Item Number (VNDITNUM) on the PO line, and rejects the receipt if it doesn't match exactly. In practice this mismatch is almost always caused by something in the Vendor Item Number that isn't visible at a glance:

  • A stray leading or trailing space in the Vendor Item Number.
  • A special character — most often a forward slash (/) — embedded in the Vendor Item Number.
NOTE: The extra space or character is easy to miss just by looking at the value in GP or on the portal — it typically only shows up once you compare the exact string on the PO line against the item/vendor record.

How to Fix

  1. Note the ITEMNMBR, VNDITNUM, and VENDORID values from the failed transaction's error details on the portal.
  2. Compare the Vendor Item Number character-for-character against the PO line and the vendor's item record in GP, looking specifically for a leading/trailing space or a slash. Correcting the value has been done in different places depending on the setup — on the Purchase Order line itself, on the item's Vendor Item Number record, or (most reliably) in both — so check both if the first correction doesn't resolve it.
  3. Resubmit the failed transaction from the PanatrackerGP portal.

Prevent

Where this has recurred for the same vendor, it has traced back to how that vendor's Vendor Item Numbers get entered. Double-checking new or edited Vendor Item Numbers for stray spaces or slashes before the PO is created can avoid triggering this error on receipt.

Questions? Contact Panatrack Support.

Related articles