Knowing our vendors do this as well....I would love a 3rd field of
this sort in the sales order (and job info). I want to use the Need
by date as the date I am promising based on current lead times, the
shipping date as the date it would need to ship by to be delivered
by need by....and then a 3rd date field as Customer Request Date -
so if they are requesting ealier than promised - production tries to
reach that date if possible. I don't want to modify the Need By
date to when they request due to 'late shipments' if not met.
Anyone have any ideas here????
this sort in the sales order (and job info). I want to use the Need
by date as the date I am promising based on current lead times, the
shipping date as the date it would need to ship by to be delivered
by need by....and then a 3rd date field as Customer Request Date -
so if they are requesting ealier than promised - production tries to
reach that date if possible. I don't want to modify the Need By
date to when they request due to 'late shipments' if not met.
Anyone have any ideas here????
>do....
> I couldn't agree more with this process. It is exactly what we
>no
>
>
>
>
>
>
> "Promise Date is purely for vendor performance measurement. It has
> impact on planning whatsoever.confirmed
>
> Your Promise Dates should reflect the best date your vendor
> they COULD do (and, on initial PO creation, should be the same asthe
> Due Date).planning
>
> As time passes and you get updates from the vendor that the date is
> either improving or slipping, re-adjust your Due Dates so the
> system (and your people) are working with accurate info.based
>
> If you re-request an changed date, the Promise Date can be changed
> on the vendor's new (re)Promise commitment.accurate
>
> Following this paradigm gives your planning system & people
> info - and still leaves you with the ability to measure vendor on-time
> performance (to Promise Date).
>
> Rob Brown"
>
>
>
>
>
>
>
> -Ben Belzer
>
>
>
> [Non-text portions of this message have been removed]
>