• Replies 7 replies
  • Subscribers 338 subscribers
  • Views 151 views
  • Users 0 members are here
Related

Batch Posting Report Numbers

David Vivino (Past Member)
$organization

Hello – we’ve noticed our batch posting report numbers skip sequence.  We’ve theorized that it’s related to Web batches.  If a posting contains a Web batch, the posting report number that follows adds 10 to the number.  Example: Dev posting Monday – posting report #14090.  Ticket Office Posting Tuesday containing a Web batch – report #14091.  Dev posting later that day – report #14101 (skips 10). 

I saw another forum entry from 2010 that mentioned if users don’t complete a posting, that could cause unused numbers, and skipping.  But this seems to be consistent with skipping 10 following a Web posting.  Our Finance dept is concerned that something is ‘missing’.  Is this by design?  Anyone know?

Thanks,

…Dave

Parents
  • $organization

    Thanks guys.  Yes, I knew about the situation Ryan explains, but I don’t think that’s the cause.

    Yesterday: 

    A morning box office posting was #14115.

    A report later in the day from our sales dept was #14125.

    It seems unlikely that folks would be canceling the posting window exactly 10 times every day!

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Nick Reilingh
    Sent: Tuesday, May 20, 2014 4:12 PM
    To: Vivino, David
    Subject: Re: [Tessitura Technical Forum] Batch Posting Report Numbers

     

    Ryan explained how this works, but to your point about Finance department concerns, I would make sure they understand that post numbers are not what they should be auditing--they will always be generated in sequence (thought not always used) but postings can be backdated such that your posting numbers may not actually end up in chronological order. One way for Finance to verify they are getting all of the relevant posting numbers is to run a GL Summary Report for the posting date range in question. In Detail mode, there will be a line (for each relevant GL) for every posting number that occurred within that date range.

    From: David Vivino <bounce-davidvivino4732@tessituranetwork.com>
    Sent: 5/20/2014 10:56:30 AM

    Hello – we’ve noticed our batch posting report numbers skip sequence.  We’ve theorized that it’s related to Web batches.  If a posting contains a Web batch, the posting report number that follows adds 10 to the number.  Example: Dev posting Monday – posting report #14090.  Ticket Office Posting Tuesday containing a Web batch – report #14091.  Dev posting later that day – report #14101 (skips 10). 

    I saw another forum entry from 2010 that mentioned if users don’t complete a posting, that could cause unused numbers, and skipping.  But this seems to be consistent with skipping 10 following a Web posting.  Our Finance dept is concerned that something is ‘missing’.  Is this by design?  Anyone know?

    Thanks,

    …Dave




    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!

  • $organization in reply to David Vivino (Past Member)

    The next posting number to be used is stored in T_NEXT_ID -- you can run

    SELECT * FROM T_NEXT_ID WHERE type = 'PO'

    to get that from the database. The next time you step through the posting process, you should log the T_NEXT_ID at each step to figure out exactly when the post ID is "jumping".
Reply Children
No Data