Hello! I have inherited a "LP_CUSTOMER_RANK" sproc that no longer performs as desired - it is assigning rankings that give discounts to customers not entitled to said discount. It has been through many changes in developers and business practices, and seems mostly made of band-aids at this point. I want to redo it, but at this point it is hard to tell what the current sproc is even doing. Do any of you fine Tessiturians have a "clean" copy of this stored procedure that you'd be willing to share as an example? Many thanks!
You might put in a TASK ticket and ask support if they can get you a copy of this file. I've got to imagine that the installation teams have these files.
Payce English said:Do any of you fine Tessiturians have a "clean" copy of this stored procedure that you'd be willing to share as an example?
I certainly don't, I'm afraid. I'm sure they'd be happy to send you one if you put in a request in a TASK ticket, however.
We do a lot (too much) in our LP_CUSTOMER_RANK proc, and while it is discouraged by Tessitura, I've broken out different parts of it into separate stored procedures called by LP_CUSTOMER_RANK. I think I have seven? In any event, there is performance overhead to executing a stored procedure, and of course LP_CUSTOMER_RANK is called so often that performance needs to be very, very good. Unfortunately, trying to wrap the code in one procedure would have made maintenance impossible for us.
Is AP_CUSTOMER_RANK the basis for your LP_CUSTOMER_RANK? If so, that should be in your database.
No, that's the main internal Tessitura procedure that calls LP_CUSTOMER_RANK as part of its execution.
We look on LP_CUSTOMER_RANK procedure as programmer hook to put our business logic there. This is very intensive use of it, so it need to be kind of light.
Payce, You can just put a RETURN statement (or un-comment it) before any code is executed. That is the default behavior. Send it over to me, I'm happy to take a look too.
JD
Thanks a million! I have emailed you the sproc.
I think I'm in a similar situation. The full story is that we used to be part of local government with a full IT team. Now the IT team is just me and I have a mighty need to simplify the maintenance of this beast.