[Home] [Help] [Dependency Information]
Object Name: | GL_BC_DUAL |
---|---|
Object Type: | TABLE |
Owner: | GL |
FND Design Data: | SQLGL.GL_BC_DUAL |
Subobject Name: | |
Status: | VALID |
GL_BC_DUAL contains one row which the Funds Checker locks in row share mode right before it begins its SQL statement that checks funds consumed by earlier pending and accepted transactions in the budgetary control queue table. The lock is released after the Funds Checker executes a second SQL statement that checks postedfunds available in GL_BALANCES.
The purpose of this lock is to prevent the case where the Posting process commits its update of GL_BALANCES and delete of GL_BC_PACKETS in between the two separate SQL statements the Funds Checker has to run to check funds availability. Hence funds do not get counted twice.
Posting will perform its update of GL_BALANCES and delete of GL_BC_PACKETS and then attempt to lock GL_BC_DUAL. If successful, Posting will commit its update and delete, and then release its lock. Otherwise Posting waits until all other Funds Checker processes release their locks on GL_BC_DUAL before committing. Posting requests its lock in exclusive mode.
Tablespace: | APPS_TS_SEED |
---|---|
PCT Free: | 10 |
PCT Used: |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
DUMMY | VARCHAR2 | (2) | Single column for locking |
Cut, paste (and edit) the following text to query this object:
SELECT DUMMY
FROM GL.GL_BC_DUAL;
GL.GL_BC_DUAL does not reference any database object
GL.GL_BC_DUAL is referenced by following:
|
|
|