Results for “closing_status”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_PERIOD_STATUSES_V is an APPS-owned database view in the Oracle E-Business Suite General Ledger (GL) module. It is documented in the Oracle ETRM (E-Business Suite Technical Reference Manual) under product GL — General Ledger, with a status of VALID and a description of "10SC ONLY." The view exposes accounting period status information for a ledger, joining the GL_PERIOD_STATUSES table to a lookup-based view (GL_LOOKUPS_PERIOD_STATUSES_V) to translate the stored closing status into a human-readable display value. It presents one row per period per ledger, allowing reporting and integration components to query period open/closed state without recoding the underlying lookup join.

Its principal role is to centralize period-status resolution. Rather than replicating the join between GL_PERIOD_STATUSES and the period-status lookup view, forms, concurrent programs, and custom reports can query this view directly. This ensures consistent rendering of the CLOSING_STATUS value across the application and reduces maintenance when lookup definitions change.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects:

• GL_PERIOD_STATUSES (SYNONYM) — the primary source table, aliased as GPS, holding the raw period status rows per ledger/application and period.
• GL_LOOKUPS_PERIOD_STATUSES_V (VIEW) — a lookup view, aliased as GLPS, supplying SHOW_STATUS.

The view definition joins these objects with the predicate GPS.CLOSING_STATUS = GLPS.STATUS_FLAG, which maps each stored closing status code to its corresponding display status. The view also derives GPS.LEDGER_ID SET_OF_BOOKS_ID, retaining a column named SET_OF_BOOKS_ID for backward compatibility with pre-Release 12 terminology while GL_PERIOD_STATUSES itself stores the value in LEDGER_ID. ROW_ID is passed through from the base table to support the standard "WHO" framework.

Key Columns

• ROW_ID — the ROWID of the underlying GL_PERIOD_STATUSES row.
• APPLICATION_ID — the application owning the accounting period.
• LEDGER_ID / SET_OF_BOOKS_ID — identifies the ledger; SET_OF_BOOKS_ID is an alias of LEDGER_ID.
• PERIOD_NAME — the accounting period identifier (e.g., JAN-24).
• CLOSING_STATUS — the stored status code (e.g., O, C, P).
• SHOW_STATUS — the decoded, displayable status derived from the lookup view.
• START_DATE / END_DATE — the period begin and end dates.
• PERIOD_TYPE, PERIOD_YEAR, PERIOD_NUM, QUARTER_NUM — period classification and sequencing attributes.
• ADJUSTMENT_PERIOD_FLAG — indicates whether the period is an adjustment period.
• WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

A typical use is retrieving the current status of a specific period for a ledger:

SELECT PERIOD_NAME, LEDGER_ID, CLOSING_STATUS, SHOW_STATUS
FROM   APPS.GL_PERIOD_STATUSES_V
WHERE  LEDGER_ID = :ledger_id
AND    PERIOD_NAME = :period_name;

Other scenarios include listing all open periods for a ledger, filtering modules by whether the target period is closed before posting (to prevent invalid journal entries), and joining to GL_JE_BATCHES or GL_JE_HEADERS to reconcile period activity. Because SHOW_STATUS is pre-decoded, reports can display a readable status without additional lookup logic, and integrating systems can use CLOSING_STATUS for programmatic checks. Note the description "10SC ONLY," indicating the view is intended for a specific reference configuration (10SC); confirm applicability against the target instance's patch level before relying on it. For high-volume reporting, DBAs should validate the execution plan, as the join to the lookup view may require appropriate indexing on the underlying GL_PERIOD_STATUSES.