I've seen that error before and the cause is mostly data related. Let's say one day you created an order with 2 lines. First line is for item X and second line for item Y. A shipment is then created for the order. Later on, you decided that it's time to invoice the shipment but you got this error. From what I've seen with other customers, this error occurs if the original order's line contains a different item than originally shipped. So in this case if the shipment has item Y for line 2 the original order should still have item Y in line 2. This error appears if they don't match (either item Y is missing or replaced by a different item). Some of the known causes of this are data manipulation or a third party application that would modify the OE order details.

That's interesting but I don't think its the case this time. Our error happens to new orders even if we try and generate an invoice immediately so i don't know that its related. For example:

I open Order Entry and create a new order with any item from our inventory, set the order qty to 1, set the price to $0.01, set the ship qty to 1. The click the Create Invoice check box and attempt to post the Order. I get the error i listed above(Description: Incorrect procedure. Shipment cannot be posted. You must manually create the shipment from Shipment Entry.)

But,

If i open Order Entry and create a new order with any item from our inventory, set the order qty to 1, set the price to $0.01, set the ship qty to 0, don't check the create invoice check box(since it doesn't exist with nothing shipped) and post the order posts and generates an order number. I can then take that order number and generate a shipment manually and then generate a invoice.

It only give me the error when i try to create the invoice from the order entry screen.

I see. Is your Sage 300 data activated with 3rd party applications that integrate with OE? If so, try sample data and test the invoicing. If sample data is ok, chances are either the live data has problems or a 3rd party application may be causing the error. If you are still stuck open a ticket with our support team and prepare to run RVSpy on your error.

No 3rd party integration and sample data has the same errors.

Are there other computers with a local install of Sage 300? Do they also get the error? You might end up with a reinstall of OE on that computer. I assume you have PU2. If nothing else works, run RVspy and open a ticket with Sage.

None of the computers have local installs of sage 300, they are all network installs from the server, i get the same errors running AccPac directly on the server. I have not installed update 2 but I am tentative to install an update while we are having problems. I have opened a ticket but have yet to get any response beyond the initial consult.

Hi I have a client that ran into this same error on Wednesday. She is using Sage 300 ERP V2014 on a standalone computer. I brought the data in house and I was able to ship an Order and invoice it without receiving the error. I reinstalled Sage 300 and PU1 on her computer then ran Regacc. This resolved the issue. You could also try renaming the OE60a folder and replacing it instead reinstalling all of Sage 300.

We reviewed the rvspy you sent and it appears that you are missing (or bad) DLL file in your AR. That triggered both errors in OE and customer inquiry. Stand by for a call from our support analyst.