Hi Tommy
Thanks for your suggestion. I tweaked the code a little bit, and changed the positioning of the base.getSession.transactionBegin() and base.getSession.transactionCommit() statements. although I'm still getting plenty of warning messages regarding the same Requisition object being accessed/updated more than once, I have not encountered the exception so far, in the 5-6 runs we did, each with number of records ranging from 150-220.