Sanity check
In Customer Maintenance, there is a check box for Check for Duplicate PO. It works great to prevent using a customer PO on more than one Sales Order.
BUT it also makes PO a required field, even when Ready to Process is not checked, and our Sales team insists that in E10, this was not required when Ready to Process was unchecked.
Before I roll out a new UD checkbox to bypass base functionality, is this expected behavior? or are we fighting for Kinetic to behave like a customization we might have had on E10?
The idea being that we don’t always know what the Customer PO is when a Sales Order is created…
and they surmised that the behavior before was a bug that was fixed by 10.2.700 (which they used to test). We’ll never know, as we’re not going to push it and just enter a placeholder PO as needed…