Hi,
We are attempting to import PO Receipts against open existing Purchase Orders, with a simple CSV file.

We have copied the sample Receipt Default which works on our installed Sample data correctly, and replaced it with our own data to test a single receipt import with several changes (no unit cost) because the Item Unit Cost is coming from the PO.

Hdr - Header Record Type
Hdr - Original PO No
Hdr - Vendor Doc Number
Det - IC Item Header Type
Det - IC Item No
Det - IC Item Line No
Det - IC Item Qty Received

On a copy of our live data, we get an Import Error, as below:

Error 16 returned from Validate, not accounted for.
Would you like to continue showing errors on Screen?

We say yes, and get import complete. No receipts were imported, etc.

We have reviewed the import white paper doc,

We have tested our format layout on sample data and the template works for our import file when we match to PO and items in sample data PO.

Does anyone know what causes Error 16 to display?

We have tried with quotes to encapsulate the data strings without success. We have changed the field lengths of the strings to match our data without success. We always get the same Error 16 message.

Thanks,
Brian

Hello Brian,

We haven't seen this error reported before.

Please send a System Snapshot and the related dataset that shows this error to Technical Support.

Hi,

We have uploaded zip file of related PO data 9.3B and separate file of screen shot of error message and import file.
Thanks for your quick response and your attention to this issue.
Brian

Thank you, Brian!

I have received the data.

Hello Brian,

I can duplicate the error but only with the client data. R&D will need to investigate.

This dataset has a lot of Integrity Errors in PurchaseOrders and Inventory.

Hello Brian,

The Error 16 is being returned instead of a warning regarding the Ledger Fiscal period for the Vendor Document number. The Company Profile option: Validate Closed Periods, is set to Disallow.

In the upcoming Service Pack, there will be a better error message!

Thanks Terry,
This really will help to resolve our testing issues.
Brian