We have a local view called LV_TKT_HIST_REPORT which is based off VS_TCK_HIST, however it looks like we have customized the later some time ago and consequently when it’s altered in the v11 migration script, we get a ton of errors.
Initially, I fixed this by simply not allowing it to be altered in the script (I know…very bad). So now I’m thinking that we should create our own version of VS_TCK_HIST and base LV_TKT_HIST_REPORT off that instead, or just incorporate everything into LV_TKT_HIST_REPORT.
There is only one problem….because we have customized it I’m not 100% sure what it was originally supposed to look like! Can someone share with me the code from within the design for this standard view? V11.0.3 or V10?
I thought about just running the section of the migration script that alters it, but wasn’t sure if all the changes would be covered by that alone.
Also…I have looked at the dependencies of VS_TCK_HIST and only see the trigger and our custom view. Is there anywhere else I should look before changing it?
Thanks for any help and please forgive me for this technical faux pas..…
Hi Natasha
I think this is something you should put in a support ticket for.
Best to get that sort of thing (repairing original Tess code) straight from the horse's mouth, as it were.They can guarantee that the replacement is correct.
And since you already have your own local view, I think your second option makes more sense for the fix . ie " just incorporate everything into LV_TKT_HIST_REPORT." - including securing it by joining to VRS_SEASON, in the same way that VS_TCK_HIST does it.
Ken
Yeah, good point. Thanks Ken, will do.