• Replies 5 replies
  • Subscribers 337 subscribers
  • Views 279 views
  • Users 0 members are here
Related

Open Batches at Post Time

Lee Schlosser
$organization

We are beginning to run into problems of users not holding or closing their batches at the end of the workday, then, having to hold the post until the offending batch can be held/closed.  We were wondering how others deal with this problem.

Parents
  • $organization

    You can run a script to put the batch on hold and then close it (if you don't know the users password you can change it via security, log in and close the batch)....

     

    --- run this query first and then again after the update

    --- statement to check the batch status (asterisks will be the batch no)

    select

     

    * from t_batch where batch_no = ****

    The above will show you the status of the batch before and after you run the update below...

    --- run this to put the batch on hold

    update

     

    t_batch set status = 'H' where batch_no = ****

     

Reply
  • $organization

    You can run a script to put the batch on hold and then close it (if you don't know the users password you can change it via security, log in and close the batch)....

     

    --- run this query first and then again after the update

    --- statement to check the batch status (asterisks will be the batch no)

    select

     

    * from t_batch where batch_no = ****

    The above will show you the status of the batch before and after you run the update below...

    --- run this to put the batch on hold

    update

     

    t_batch set status = 'H' where batch_no = ****

     

Children
  • Former Member
    Former Member $organization in reply to Heather Fails
    That's a slightly dangerous thing to do.
    If you force a batch to Held status in sql like this, and then Close it, but the batch is still actually open on the pc, then the user can come back to their session and continue to use the batch. That can lead to Unfortunate Consequences which are messy to fix. That did happen to us once in the early days. It wasn't pretty.
    We ask people to certify that the pc in question has been re-started before we will Held a batch in the backend like this. We have a local report called Current Open Batches which a manager can use to review the state of play before the shift finishes, and which identifies the PC that a batch is open on.
    A bit excessive possibly, but we certainly don't want to encourage sloppiness by making it too easy.
    Ken McSwain
    +61 (0)418 659 360
    Sent from BlackBerry

    From: Tessitura Technical Forum <forums-technical@tessituranetwork.com>
    To: Ken McSwain
    Sent: Tue Dec 08 08:32:07 2009
    Subject: Re: [Tessitura Technical Forum] Open Batches at Post Time

    You can run a script to put the batch on hold and then close it (if you don't know the users password you can change it via security, log in and close the batch)....

     

    --- run this query first and then again after the update

    --- statement to check the batch status (asterisks will be the batch no)

    select

     

    * from t_batch where batch_no = ****

    The above will show you the status of the batch before and after you run the update below...

    --- run this to put the batch on hold

    update

     

    t_batch set status = 'H' where batch_no = ****

     

    From: Lee Schlosser <bounce-leeschlosser6477@tessituranetwork.com>
    Sent: 12/7/2009 3:10:24 PM

    We are beginning to run into problems of users not holding or closing their batches at the end of the workday, then, having to hold the post until the offending batch can be held/closed.  We were wondering how others deal with this problem.




    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!
    Please consider the environment before printing this email.
=====This message is intended for the addressee(s) named and may contain confidential information.
If you are not the intended recipient, please delete it and notify the sender.
Views expressed in this email are those of the individual sender and are not necessarily the views of the Sydney Opera House Trust=====