OBJID Table Lock

I ran into this last year and had Lawson create a CTP for it. Let me see if I can find it. =

Thanks John, any help is greatly appreciated.

Mark, I went back and looked this up.

It was actually an issue in a client's custom version of AR560 when interfacing AR invoices as GLTRANS and ACTRANS commitment records, which implicitly requires allocation of an OBJ-ID. This is done by calling a common library routine, which locks the OBJID record associated with the OBJ-ID being requested (e.g. OBJ-TYPE = “ACTRN” or ”GLTRN”) for the duration of the database transaction. This then blocks other (unrelated) users from obtaining OBJ-IDs until the transaction is committed.

In testing, appears to be locking issue on OBJID when acquiring a new object id during requisition release; was taking sometimes 13-15 minutes to find & lock one OBJID record. Looking into the code in RQIF, the code is acquiring an object id when using GL/AC commitments. Turned off those flags on GL01, and releasing was fine. Turned the flags back on, and the releasing was slow again.

In looking further, AP26 and AP126 releases were also slowed.

In the end, I changed the custom AR560 to acquire OBJIDs in blocks of 1000 at a time (big client), rather than one at a time.

That may help point us in the right direction as we have a custom routine running to update pricing for our office supply vendor and releasing the PO's. This rountine was running just before we saw the lock up issue.

We will dig into that more. Thanks for the insight.