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
Your last post and Nick’s triggered a thought. Do you have a scheduled job running that consistently updates T_NEXT_ID (such as running the upd_next_id script used when converting data)? The reason I ask is that upd_next_id is set to increment T_NEXT_ID to the last-used value of each record type - plus 10.
That’s the only situation I’ve run across where that value is updated by that specific interval.