Home
Login
Sign Up
Profile Options
Tools
Edit Profile
Manage all aspects of your profile here including demographics, emails, notification settings, etc...
Change Password
Begin the password change process
Email Subscriptions
Manage your opt-in/opt-out email subscriptions
View Profile
View your profile - what other's see
Sign-out
Sign out of this community
1-800-819-1190
Contact support line
Smart Connect
Connect with others and manage various member options
View QR Code
View your profile QR Code - Connect and or share your contact information
Tour Page
Take an interactive tour of this page
Knowledge Base
Visit the knowledge base for more info
Insights
Member reporting and analysis
Terms of Use
Cookies
Privacy Policy
Contact Us
Help
 
 

Site Menu

Forum | Message
Do you track original promise date to customers?
Elise Sheppard *MUGA
BC:

Question:

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
Uncategorized
Group: *MUGA
2
7
257
Latest msg: @cristikimrey We are also using ODHEAD/ODLINE to pull the actual. from Steve Bartlett, on 02/07/2024

Comments (7) (Descending Chronological Order)
There are no comments at this time, be the first to comment

Steve Bartlett
BC:
@cristikimrey We are also using ODHEAD/ODLINE to pull the actual.
1
Jeremy Bull
BC:
@cristikimrey we use the date/time in the ODHEAD (OIS150) record of that delivery to track when it was reported
1
Cristi Kimrey
BC:
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!
Elise Sheppard
BC:
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...
Steve Bartlett
BC:
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.
Jeremy Bull
BC:
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.
1
Norman Hussey
BC:
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.

Online