Results for “gl_period_statuses”

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

Overview

GL_PERIOD_STATUSES is a General Ledger (GL) reference table in Oracle EBS 12.1.1 and 12.2.2 that stores calendar period statuses for every accounting period across each ledger and application. It is the authoritative source that determines whether a given period is open, closed, or permanently closed, and it drives validation logic throughout the GL, Subledger Accounting, and downstream reporting modules. At period close, General Ledger updates the CLOSING_STATUS column in this table for the relevant ledger and period, and that status governs whether journal entries, transfers, and postings may proceed.

The table is owned by the GL schema and contains 30 documented columns. Based on the foreign key topology provided in the ETRM metadata, its heuristic Data Vault classification is satellite-leaning: it carries descriptive and status attributes keyed by ledger, application, and period, and is referenced by dependent fact-bearing tables such as AX_BALANCES and AX_SLE_HEADERS. This classification should be treated as a modeling suggestion rather than an architectural directive.

Key Information Stored

The primary key is the composite GL_PERIOD_STATUSES_PK, comprising APPLICATION_ID, SET_OF_BOOKS_ID, and PERIOD_NAME. These three columns form the surrogate identity of each period-status record. Several business-key candidates are documented through unique indexes: GL_PERIOD_STATUSES_U1 (APPLICATION_ID, SET_OF_BOOKS_ID, PERIOD_NAME), U2 (APPLICATION_ID, SET_OF_BOOKS_ID, EFFECTIVE_PERIOD_NUM, CLOSING_STATUS), U3 (APPLICATION_ID, LEDGER_ID, PERIOD_NAME), and U4 (APPLICATION_ID, LEDGER_ID, EFFECTIVE_PERIOD_NUM, CLOSING_STATUS). The presence of U3 and U4 reflects the 12.2.x multi-ledger architecture, where LEDGER_ID supplements the legacy SET_OF_BOOKS_ID.

• CLOSING_STATUS — the open/closed state of the period.
• PERIOD_NAME — the human-readable period identifier (for example, JAN-24).
• SET_OF_BOOKS_ID / LEDGER_ID — the ledger context for the status row.
• APPLICATION_ID — the application owning or using the period.
• START_DATE, END_DATE — the calendar boundaries of the period.
• YEAR_START_DATE, QUARTER_START_DATE — the year and quarter start anchors.
• PERIOD_YEAR, PERIOD_NUM, EFFECTIVE_PERIOD_NUM — the chronological ordering attributes.
• QUARTER_NUM, PERIOD_TYPE — quarter and period type designations.
• ADJUSTMENT_PERIOD_FLAG — indicates an adjustment period.
• ELIMINATION_CONFIRMED_FLAG — tracks elimination confirmation for consolidation.
• CHRONOLOGICAL_SEQ_STATUS_CODE, TRACK_BC_YTD_FLAG, MIGRATION_STATUS_CODE — sequencing, balance tracking, and migration indicators.

Common Use Cases and Queries

The predominant use case is determining whether a period is open before posting or transferring journal entries. A typical query checks status for a given ledger and period:

SELECT closing_status FROM gl_period_statuses WHERE ledger_id = :p_ledger AND period_name = :p_period AND application_id = 101;

Reporting queries frequently join this table to balances or subledger headers to restrict results to open or closed periods. Period-close dashboards list all periods by CLOSING_STATUS to track open periods per ledger. Chronological validation logic relies on EFFECTIVE_PERIOD_NUM and CHRONOLOGICAL_SEQ_STATUS_CODE to enforce sequential period opening. Consolidation processes inspect ELIMINATION_CONFIRMED_FLAG when reconciling ledgers.

Related Objects

• GL_PERIOD_TYPES — referenced via PERIOD_TYPE, defining the period-type attributes.
• FND_APPLICATION — referenced via APPLICATION_ID for application validation.
• AX_BALANCES — depends on GL_PERIOD_STATUSES through APPLICATION_ID, SET_OF_BOOKS_ID, and PERIOD_NAME.
• AX_SLE_HEADERS — subledger accounting headers tied via the same composite key.
• GL_JE_BATCHES / GL_JE_HEADERS — journal sources commonly validated against period status.
• GL_LEDGERS — supplies LEDGER_ID and SET_OF_BOOKS_ID context.