Hi Heather,Our solution isn't perfect, but it has been working for us for about 10 years.We use three dates in the Sales Transaction Entry. Requested Ship Date - This is the date the customer wants the order. This is the date we try to get the order out by. User defined date 1 - We renamed this field to "Est(imated) Ship Date". This is the date we told the customer we could ship by. It usually matches the Requested Ship Date. Our production department determines this date base on the size of the order and other orders in production. We strive to meet the Requested Ship date, but if the order goes out on or before the Estimated Ship Date, we consider the order "on time". User defined date 2 - We renamed this field to "Org(inal) Est(imated) Ship Date)". If we have a production issue and need to adjust our Estimated Ship Date, the field is used to record what we originally promised. This allows us to track the orders we were late on and by how much.Some random notes:1. We drive production based on the Requested Ship Date not based on our Estimated Ship Date. That way, if we gave an Estimated Ship Date later than the Customer's Requested Ship Date and if what ever was causing the order to be delayed goes away, we have a good chance of meeting the Customer's date.2. If the customer changes the Requested Ship Date, we recalculate and reset the Estimated Ship Date and Original Estimated Ship Date base on dates that our planning team says we can ship the product. This is the only time the Original Estimated Ship Date is change.3. You can rename the user defined field from the Sales Order Processing Setup Window -> User-Defined. Just enter a new value for Date Field 1 & Date Field 2.4. This process requires our customer service team to fill out all three dates when they creating an order.5. On "standard" orders when things are running smoothly and when the customer has a reasonable expectation, these dates are all set to the same value.6. We process our orders as one shipment. We rarely do partial shipments. If a customer wants a different delivery date on different line items in the order, GP supports it, but we don't allow it. We would create multiple orders.7. Once an order has become an invoice, we can compare the Actual Ship Date to the Estimated Ship Date to see if the order was on time or late.8. If you need to look at this stuff from the database level, The Requested Ship Date lives in the ReqShipDate column in the SOP10100 (Work) and SOP30200 (History) tables. The User Defined fields are in the USRDAT01 & USRDAT02 columns in the SOP10106 table (for both work and historical orders). The Actual Ship Date is in the ACTLSHIP column in SOP303200 - for us, invoices don't live long in the work tables (they are posted soon after being created) so I just report on historical invoices.I hope this makes sense and is helpful. If you have any questions, please give me a yell!
If you've found this thread useful, dive deeper into User Group community content by role