9.04.507A SQL
Trying to make sure I cover all the bases. We have several cases where various things not being completed should prevent a packing slip from being created (Job not complete for example, or Job Ship Qty greater than Job Completed Qty).
As it turns out, I need 3 different BPMs for each case.
First on CustShip.GetQtyInfo, for when our shipping department enters the shipment quantity directly on the Lines screen. This raises an exception message with an explanation and appropriate Job/Order information.
Second on CustShip.MarkShipmentLines, for when our shipping department uses the "Ship All" button. This raises a similar exception.
And third a Data Directive on the ShipDtl table... those exception don't actually stop the process, so the Data Directive kicks in if they try to just bull their way through.
I haven't found any other processes quite so convoluted... am I missing something that would make it a little less inelegant?
Ernie Lowell
Diba Industries
Trying to make sure I cover all the bases. We have several cases where various things not being completed should prevent a packing slip from being created (Job not complete for example, or Job Ship Qty greater than Job Completed Qty).
As it turns out, I need 3 different BPMs for each case.
First on CustShip.GetQtyInfo, for when our shipping department enters the shipment quantity directly on the Lines screen. This raises an exception message with an explanation and appropriate Job/Order information.
Second on CustShip.MarkShipmentLines, for when our shipping department uses the "Ship All" button. This raises a similar exception.
And third a Data Directive on the ShipDtl table... those exception don't actually stop the process, so the Data Directive kicks in if they try to just bull their way through.
I haven't found any other processes quite so convoluted... am I missing something that would make it a little less inelegant?
Ernie Lowell
Diba Industries