Skip to content

How to Stop Changing Sales Order with Shipment Tracking (Starship) Note

- I have made the following changes to prevent my users from bringing up a sales order in Change mode once it is has a shipment tracking note.  System will detect the condition and display message "The order has been process by starship already".  Unfortunately, there is one situation where I can still bring up the sales order even though the shipment tracking note is there.  What happened?

(1) In Global Setup -> COP-Func -> Order Header Screen,  I set the flag "27. Allow Change Order w/ Shipment Tracking Note" to "N." See sample screen below.
 


(2) Furthermore, in Password Setup -> Global Security -> User Global Security, I set the flag "8. Allow User to Change COP Order W/Shipment Trx" in Screen 6 to "N."  See sample screen below.



(3) Also, as you can see, I have a shipment tracking note for order# 888505. See sample screen below.


So why is it that when I go to COP -> Order Entry and try to change  order# 888505, the system does not stop me from changing this order?

A - Just to clarify, If one of the flag in global setup flag in (1), or the global user security flag in (2) is set to "N", then user will not be able to change the order in shipment tracking note is found.  Even if both flags are set to "Y", you still will be warned with the condition. The reason you experienced the problem as reported is because Elliott tries to consider the possibility of a tracking note being created for a prior shipment due to partial shipment.  

When you process an order through Shipping Manifest, there will be a shipping tracking note created with a system date.  Naturally, that order will also be selected, invoiced and posted on the same date.  Our control to prevent you from changing the order is only for a short period of time within that same day. So when you bring up the order in Change mode, we try to determine if there’s a shipping note with today’s date. If so, we stop you.  If the date stamp of the shipping note is older, then this is the shipping note left from the prior shipment (back order).  We obviously do not want to stop you from bringing up a back order that was shipped previously.

If you look at order# 888505, the shipping note was created on 6/30/2015. Since that is in the past, our system assumes that the shipping tracking note was created for a prior partial shipment. Therefore, you can bring up that order.  In your customer master file setup, if you answer "N" to field "43. Backorders OK?", then system will assume that you don't have back order with this customer.  In that case, if you have a shipping tracking note for this order, regardless if it is today's date, system will give you warning or stop you from bringing up the order.

As for the setup, you only need to change either (1) or (2) above to "N," and system will stop the user from changing the order with a valid shipment tracking note for today.

The other alternative is you can prevent changing an order after pick ticket is printed. You can do that through the combination of global setup flag -> Cop-Func -> Order header Screen, “7. Alert If Order Chg After Pick Ticket Printed ?” and Global user security flag in screen 3. “6. Change/Del COP Ord After Pick Ticket Printed”

If you have proper control to prevent user from changing order after pick ticket is printed, then you don’t need the control through detecting Starship note.

EMK

Feedback and Knowledge Base