Subscription Rollover notices

As I recall I the standard renewal notice/invoice reports from T_CUST_SUBSCRIPTION_SUMMARY, and will pull all of the data for the season in question. For what you want, it sounds like a custom notice/invoice/report will be needed.

We did one here last year, though for layout reasons rather than anything re: your issue. Much like a custom acknowledgement, if you call the standard TP_GET_REN_NOTICES and populate its output into a temp table within your custom sproc, you can do just about whatever you want after that. Sending a notice/etc for some but not all of the new packages would be an interesting challenge for this custom arrangement.

As I recall I the standard renewal notice/invoice reports from T_CUST_SUBSCRIPTION_SUMMARY, and will pull all of the data for the season in question. For what you want, it sounds like a custom notice/invoice/report will be needed.

We did one here last year, though for layout reasons rather than anything re: your issue. Much like a custom acknowledgement, if you call the standard TP_GET_REN_NOTICES and populate its output into a temp table within your custom sproc, you can do just about whatever you want after that. Sending a notice/etc for some but not all of the new packages would be an interesting challenge for this custom arrangement.

As I recall I the standard renewal notice/invoice reports from T_CUST_SUBSCRIPTION_SUMMARY, and will pull all of the data for the season in question. For what you want, it sounds like a custom notice/invoice/report will be needed.

We did one here last year, though for layout reasons rather than anything re: your issue. Much like a custom acknowledgement, if you call the standard TP_GET_REN_NOTICES and populate its output into a temp table within your custom sproc, you can do just about whatever you want after that. Sending a notice/etc for some but not all of the new packages would be an interesting challenge for this custom arrangement.

We have changed the TR_SEASON structure this year to be able to sell flexible packages of performances from different series.  We also print subscription Rollover notices on different pre-defined forms.  The issue we ran into: when a customer has subscriptions to two or more series in the same season (winter for example), even though we can create separate orders for each subscription, a notice for a second subscription package includes information from the first package (and summarizes all the $ amounts).  Tessitura by design accumulates these totals.  Did anybody have a similar issue and/or have some possible solutions/work-around?

Thank you,

Sabina

 

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!