@willie98 , as far I see, there is another root cause which leads to the same outcome and is fixed in 21.114:

See ‘Known Issues for 2021 R1’ (https://sso.acumatica.com/Main?ScreenId=KI2021R1&PageID=994d89e7-82a1-41eb-8465-9db854ab3c04)

AC-203120: If a sales order was created for a customer on credit hold, then the status of the customer was changed from Credit Hold to Active, and then a user tried to create a shipment for the sales order on the Sales Orders (SO301000) form, the system displayed the following error: “Order does not contain items planned for shipment“.
Workaround: On the Sales Orders form, put the sales order on hold and then assign it the Open status back. To identify documents affected by the issue, please perform the instructions of the knowledge base article. 

Hi @mvolshteyn 

I will have my team update to build 21.114: to make sure, but I am pretty sure we tested with latest Version and Build and it was still happening. This is what we found:

Customer is on CH
User enters a SO, order status is OPEN

While on the order, we use the “pencil” to open Customer screen.

Customer screen comes up, user removes CH, closes Customer screen

Back on SO Screen, user does not refresh, does not save, closes SO- INPLAN error comes up.

We are thinking at this point it’s a cache issue.

Any thoughts?

@willie98 , I did not test this scenario, but it does not look as an obvious issue to me

Obviously, first customer status should be settled, then a sales order lines should be entered

If it is done vice versa, order lines need to be ‘refreshed’ - i.e either have quantity retyped or the order should be put to and removed from hold

We have been doing the workaround suggested above, but it’s getting to be very annoying for my client.

My client has over 200 employees and work in different buildings- AR Dept in one building, SO Dept in another where they cannot be checking with each other every second. Their customer data base has over 4500 customers and most of them have locations, the number is over 30K. Credit Hold rules can change every second on a customer and for sure every 20 minutes because they run an automation to check on this and change status.

We have also instructed the users to save or refresh SO due to what I’ve explained before- Cache issue, that seems to have relieve a bit the situation. 

I’ll keep reporting back if I find anything else.