Hi
I've recently started working at the Young Vic as their Database Manager and have discovered that they haven't posted any batches since 2012.
Can anyone offer advice as to the best way of dealing with this? What will be the impact if I bulk posted all batches at the same time; as in over a period of a couple of day in lots? Should I backdated them to the actual date they were closed?
Any advice would be much appreciated.
Very many thanks
Lee-Anne
Hi Lee-Anne
One of our consortium partners has just gone through the exercise of posting maybe 6,000 closed batches, having not done it from when they started using Tess in 2006 until about 2012, I think. They need to be all posted for the upgrade to v12. They did it in chunks of about a month's worth at a time, with the oldest just posted to the current date, and the newer ones posted back to the end of the relevant month, by the look of it, without causing any distress, AFAIK.
I guess my comment about the need to be careful is that you obviously don't have any business processes currently in place that depend on the integrity of batch posting records, so it's probably pretty safe. If someone wants to use the transactions by posting report or something similar in the future, they'd need to be aware of the unreliability of data back from now, but if that hasn't caused a problem to date, it's not likely to be critical.
Ken
Thanks all, there is some very good advice here. I am particularly pleased to see that someone else (Ken) has gone through exactly the same experience.
But, yes, there is no G/L structure and the new financial year has not been set-up. So I have a task ahead of me to sort out the financial structure on Tessitura for the company.