Accpac Error in shipment 1

[vbdbcoder]

We can't ship items in Order Entry screen, even though we have received the items in PO receipt.

The bottom section of the Order Entry screen says the item Quantity on Sale Orders is -2. Only a few sales orders have this problem. Day End could be run without problem.

Has anybody seen this? What is the fix?

Thanks in advance.

 

[ettienne]

Version?
Service packs?
There was a known issue that was fixed in a service pack. You had to run data integrity with the fix option after installing the service pack.

 

[vbdbcoder]

Version 56A

Running data integrity with fixing minor error turned on on OE, PO and IC now. Will find out what the results are.

 

[vbdbcoder]

Data Integrity is still running.

Attached is an image from the query I ran to display the good item (001-010-601) vs. the bad items. from ICILOC table.

What process in Accpac populates the fields of Qtyonorder, Qtyoffset, etc. My OE screen shows I have -1 qty on puchase order. But I have received it...

 

[ettienne]

IC, OE and PO update ICILOC when you post transactions.

 

[vbdbcoder]

Data Integrity with fixing error turned on works. Thanks!!!

What happened was some non-stock items were changed to stock items in both setup and transactions. The change was made using SQL scripts updating tables including ICITEM, ICPRIC, OEORDD, POPORL, PORCPL. The update was successful and good. However, the users did not invoice all the PO receipt lines as they were told, before the system update. Those outstanding non-invoiced PO Receipts somehow messed up ICILOC table's values...

Day End was run before and after the system update without problem.

I know a lot of people do not like the fact that system update using SQL scripts. If I can get by, I would not use this approach either. But with hundreds of transactions needed to be transformed, SQL scripts are the only option left.

 

[Jay Converse]

SQL scripts to update I/C??? That's crazy! You're lucky the system was able to fix those errors.

 

[vbdbcoder]

Just verified that update only happend on ICITEM table to update Account Set and Stockitem fields. No other IC tables were touched.

We did the update on our test data environment and things were tested and tried fine with users.

Once we did it in production, those outstanding items (Received but not invoiced) were having problem in OE screen, and majority of the transactions were brought over with no errors (That alone saves a lot of time for the users.)

 

[Jay Converse]

Oh, that's better. I thought you regularly doing updates, like to quantity fields.

Indeed, switching stock and non-stock flags is touchy, especially the PO module. I make my clients 100% certain there are no outstanding transactions before doing this kind of thing.