This business logic implies that while a put away exists the users cannot post production journal lines for subsequent operations to the last operation until the put away is posted or deleted. In the real world there are always some tasks that lag behind the completion of the put-away, for example recording of run time, setup time, output quantity for prior operations is not always the same day. This additional check only fuels frustrating for end users in high volume environments.

Is it feasible to remove the check or add it to only the last operation?

Thanks
Ashok Sundaram