Information Systems:Cannot Close Period

A period cannot be closed if there are outstanding transactions that have not yet been posted. If an update does not complete properly, sometimes orphaned transactions are left behind.

Use QUERY to look at files SROBTR (Accounting transactions created in ASW-DIS) and SROOVF (G/L Input transactions).

For example, we have a custom system to receive transactions from the bank and post them to the store’s accounts receivable (see Bank EDI). Sometimes this leaves transactions in SROOVF. We can’t do anything but manually delete them, and do a journal entry.

• I can see only one place where this could be happening, but I haven’t figured out why. BERUP075 (BED -- Post A/R payment G/L corrections to ASW) calls GCFC851 (Interface accounting transfer), which calls GCFR851 (Interface accounting transaction transfer). If field &GRIW is returned as blank, FMC050 (G/L update transactions and balances) is not run.

• Nancy seems to have found the problem and a solution. We have changed the job queue QBATCH to run two jobs at a time. If Nancy waits until one card type (Visa, Master Card, etc) completes before starting the next, the problem doesn’t seem to happen.