EGL: Lock on INSTALLATION_FS table adding journals concurrently. (Doc ID 608599.1)

Last updated on APRIL 03, 2017

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 8.8 SP1 to 9.2 [Release 8.8 to 9]
Information in this document applies to any platform.
SPECIFIC TO:´┐Ż´┐ŻEnterprise, Financials, General Ledger

This document was previously published as Customer Connection Solution 574534



****Checked for Relevance on 30-OCT-2012****


Symptoms


When adding Journals and chosing to let system assign a journal id,  the following code locks the INSTALLATION_FS table until the save is complete.

In FUNCLIB_GL.JOURNAL_ID.FieldFourmula PeopleCode,

Function get_journal_id(&JOURNAL_ID);
SQLExec("Update ps_installation_fs set journal_num_assign = journal_num_assign + 1");
SQLExec("Select journal_num_assign from ps_installation_fs", JRNL_PANELS_WRK.JOURNAL_NUM_ASSIGN);



An  update to PS_INSTALLATION_FS (1 row table) is made at the beginning of the work and do not commit until all other updates are done. The other updates could take upto 10-30 seconds depending on the machine and network and other performance issues. Since PS_INSTALLATION_FS is a 1 row table, and because it is not committing unitl after the update, it will  hold a lock on that table for the entire duration of the save.  This will prevent other users who are accessing that table. The other user could be another GL user adding Journals or running Journal Generator or an AP or AR user because INSTALLATION_FS is used by all applications.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms