Home
Login
Sign Up
 
 

Forum | Message

Wed, February, 7th 2024
Message Link »
7
View »
Elise Sheppard *MUGA
BC:

Forum Question/Topic:

Article:

Do you track original promise date to customers?

We're in multi-tenant cloud, and trying to track our on-time-complete KPIs. What we really want to compare is date delivered to the ORIGINAL promise date. And by that, we mean the date that was on the order confirmation the first time we sent it.

We're having trouble mapping it, as we don't use status 10 on orders as we enter, and the confirmed delivery date gets changed on lines as we go.

The convoluted path we're trying to follow now is to find the date & time we  Read more...created the first OIS606PF output, compare that to DB variations in OOLINE to find the confirmed delivery date of the latest CO line record just before the print date & time...

We're trying to pull this info from the databases to show in our PowerBI reporting.

Any thoughts are welcome! Show less...
Delivered Read
7
Loring Kaveney, Eric Lopez (WOL) like this.
Norman Hussey
Elise, On-prem had an option to configure change tracking on specific tables. I would build a small pipeline to read the variations from the Data lake and append this computed date field to the Line.
Jeremy Bull
Elise,
Try CRS720 - Log changes of confirmed delivery date, set to 1 or 2. That populates OORESC, which you can either pull from directly or output doc 241 using OIS610.
Steve Bartlett
We are currently using the "Requested date" in OIS101/i (OOLINE/RLDZ) as the initial promise date. Any date change there after is done in the planning (PLDT). All KPIs are pulled based on shipped and requested dates. Of course we have the SOP that any date changes should never be made in Requested.
Elise Sheppard
We've talked to the CSR team about using requested date, but they don't think it's a sustainable answer. I'll check again with them again on that.

One of the reasons we can't just use the changes of confirmed delivery date: some orders come from CPQ, so the first confirmed date is incorrect, and doesn't represent the confirmed date that the customer will see. I wish I could just pick the first conf date! That'd be so much easier!

My other thought: change our order  Read more...types to start in status 10 again, rather than 20; change what they click when they're done to a bookmark that kicks off a workflow/dataflow: confirm CO, then generate confirmation. If we do that, we could grab the first time that a CO line hits status 20, and use THAT confirmed delivery date. Show less...
Cristi Kimrey
Steve, how are you tracking the actual ship date? We are looking for a date in the system that tracks the time the delivery was confirmed for shipment, rather than the route departure date. Thank you!
Jeremy Bull
@cristikimrey we use the date/time in the ODHEAD (OIS150) record of that delivery to track when it was reported
Steve Bartlett
@cristikimrey We are also using ODHEAD/ODLINE to pull the actual.

Online