On Time Delivery Reporting - Capturing original promise date to customers?

[Former Member]

We have a business metric that we use to track how well we do based on what we told our customers the delivery date was versus when we actually delivered the product(s). However, because of rescheduling, usually this original date that was "promised" is "lost" because of the new delivery date that is proposed. Therefore, we are unable to report on what we originally told the customer.

Does anybody have any suggestions or experience in this area? How do you report on how well you do in terms of delivering to your customers? How do you measure your "on time" delivery?

Thank you, Paul

[Former Member · Accepted solution]

You can create the report where you can have the promised date and the actual dates(PGI date).

In case of rescheduling the back order means now the customer is also agree on the new dates so their is no relevance of old dates and system will pick the new dates only.

We cannot track the old dates at all.

[Former Member · Accepted solution]

That is true, that the customer has accepted the new date, but in our company, this means that we failed in our "on time to commit" even though the delivery itself is techinically "on time". By capturing what the original commitment date was, we can measure whether or not we need to improve ourselves within the company.

Are there any solutions in BI?

[Former Member]

you will not be in a position to track this data unless & otherwise you had recorded the schedule line details on a timely basis.

Say for an example, if you are scheduling the V_V2 or rescheduling option.

You go for a ztable where u have the VBBE/VBEP table details recorded seperately or you can save the details of this output on a local system (ideally we can have this data collected just before the run of V_V2 or rescheduling) and this can be used for evaluation / comparison on the original proposed date at the order level and the actual GI date recorded at the delivery level.

Regards

Ilango