Perf_Name in T_TICKET_HISTORY

Where does perf_name pull from in T_TICKET_HISTORY? I had assumed T_INVENTORY, but that doesn't appear so...?   Unless I am seriously missing something .. which, let's be real, is a distinct possibility.  :)

I am trying to clean up some remnants in terms of out dated Performance Name standardization was left over from when we were part of a consortium.   Its a mess and my Type A needs it to be fixed.  We do not have any orders from prior to moving from our consortium - only ticket history - so I am hoping that T_ORDER and T_SUB_LINEITEM have nothing to do with it. 

Also, when the TP_UPDATE_TICKET_HISTORY runs, does it overwrite the existing table or just appends for additional historical items? Considering this just in case I am feeling adventurous and want to update T_TICKET_HISTORY manually. O.o

Any insight would be appreciated!

Thanks!

Parents
  • From what I can glean from the TP_UPDATE_TUCKET_HISTORY stored procedure, John is correct.

    The perf_name column of the T_TICKET_HISTORY table gets it's information from the @perf_desc variable; and the @perf_desc variable gets it's information from the short_name column of the T_INVENTORY table. Looks like that is the table that needs to get updated.

    Neil Cole | Customer Service Specialist Principal

    neil.cole@state.mn.us

    o: 952.431.9213 | MNZOO.ORG

    13000 Zoo Boulevard Apple Valley MN 55124

    ________________________________________

Reply
  • From what I can glean from the TP_UPDATE_TUCKET_HISTORY stored procedure, John is correct.

    The perf_name column of the T_TICKET_HISTORY table gets it's information from the @perf_desc variable; and the @perf_desc variable gets it's information from the short_name column of the T_INVENTORY table. Looks like that is the table that needs to get updated.

    Neil Cole | Customer Service Specialist Principal

    neil.cole@state.mn.us

    o: 952.431.9213 | MNZOO.ORG

    13000 Zoo Boulevard Apple Valley MN 55124

    ________________________________________

Children
No Data