Hi there,
I am trying to update the procedure LP_UPDATE_SUB_LINEITEM_STATUS which updates the table LT_SUB_LINEITEM_STATUS. Discovered this was necessary when an updated procedure LP_CONSTITUENCY failed to effectively insert a new Constituency.. I searched LT_SUBLINEITEM_STATUS for this season and there was no data - so here we are.
I turned to update LP_UPDATE_SUB_LINEITEM_STATUS and it would appear in several places that it is not regularly updated every season. I'm sure it was working last season as the Subscriber Constituency was functioning and the Job has been scheduled to run daily.
The parameters are Season String and Start Event Date and are filled into the current procedure as follows:
@season_str AS varchar(255),@start_event_date datetime = '09/01/2009'
The Start Event Date parameter in particular makes me think that there shouldn't need to be any change. I can't find any other typical Subscriber data that might need updating - zone map numbers or season numbers come to mind.
There is a bit of text in the code stating that LT_CUSTOM_PLAN_PRICE_TYPE must include any new Price_Types added into tr_price_type for the Custom Plan Packages for the current season... But when I view that table, I see no changes or rows beyond Seasons 08 and 07.
Any help welcome!! Thank you all!
Frannie
Hi Frannie
That's all custom work, local to your Tess install, not actual Tess objects. (The LP_ and LT_ tags tell you that.)
So it's unlikely anyone on the forums would have specific knowledge about it., unless they were previously involved with your org's customisation.
But it certainly looks as though some custom functionality has been set up, but not maintained properly for the last couple of years. If there's no documentation on how it's supposed to work, maybe you should refer this one to Tess Network for some advice and/or consultancy?
Ken
Thanks Ken! Knew that they were definitely Customized, but was hoping it wasn't too uncommon. I will probably turn to TASC to see if they have advise as you recommend. :)