Site Transfer Fails with eConnect Error 3353 "Lot Number Does Not Exist"
Site Transfer Fails with eConnect Error 3353 "Lot Number Does Not Exist"
When submitting a Site Transfer transaction in PanatrackerGP, the transaction fails with eConnect error 3353 from the taIVTransferLotInsert stored procedure: “Lot Number Does Not Exist.”
Cause
This error occurs when the selected lot being submitted doesn't exist in GP:
- The lot may have been selected on another transaction after it was selected on this transfer but before submit.
- This error also occurs when the inventory setup Auto-Assign Lot Numbers Based on is set to “Expiration Date.”
How to Fix
- Confirm the lot in GP under Lot Inquiry for the site and bin selected.
- If using Auto-Assign based on Expiration Date, change it to “Receipt Date.”
Questions? Contact Panatrack Support.
Related articles