1 of 1 people found this helpful
An out of date exception usually indicates and attempt to update an object which has been committed to the database by a separate process...hence the "Out of Date exception. A common error might be committing the transaciton to early, so make sure you are not inadvertantly doing that. With a series of triggers and an external system involved, it can get more complicated because one of the earlier triggers in the sequence may have already committed the object resulting in your reference to the object being out of date. I think you probably need ot figure out the different processes which are updating the object and you will probably find a conflict somewhere.
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.
This is an interesting way of closing PO's in SAP, can you please explain the high level design of this.