Search Results gl_period_statuses




Overview
Explore in AI Chat

Overview

The GL_PERIOD_STATUSES table is a core data object within the Oracle E-Business Suite General Ledger (GL) module. It serves as the central repository for managing and tracking the status of accounting periods for a given ledger (represented by SET_OF_BOOKS_ID). This table is fundamental to the period close process, enforcing financial control by defining which periods are open, closed, future-enterable, or permanently closed for transaction posting, journal entry, and consolidation activities. Its status values directly control the operational workflow within the GL and interfacing subledgers, ensuring data integrity and chronological accuracy in financial reporting.

Key Information Stored

The table's structure is designed to uniquely identify a period and its state within a specific application and ledger context. Its primary and unique keys highlight the critical columns. The APPLICATION_ID links to FND_APPLICATION, typically holding a value for the General Ledger application. The SET_OF_BOOKS_ID identifies the specific ledger. The PERIOD_NAME (e.g., JAN-2024) and the combination of PERIOD_YEAR and PERIOD_NUM provide two methods of period identification. The PERIOD_TYPE column, a foreign key to GL_PERIOD_TYPES, classifies the period (e.g., Month, Quarter). The most operationally significant columns are the status flags: CLOSING_STATUS, which indicates if the period is Open, Closed, or Permanently Closed; and the OPEN_FLAG, which is typically derived from the closing status. Additional columns may track the last update date and the user who changed the status.

Common Use Cases and Queries

The primary use case is validating period availability during transaction processing. A common query is to check if a period is open for a given ledger and date, often executed by APIs like GL_DATE_API. For reporting and audit, analysts query the period close history. Administrators use the table to programmatically open or close periods via standard APIs or, with caution, direct SQL during maintenance. Sample SQL to find all open periods for a ledger includes:

  • SELECT period_name, period_type
  • FROM gl_period_statuses
  • WHERE set_of_books_id = 1001
  • AND application_id = 101
  • AND closing_status = 'O';

Another frequent pattern is joining to GL_PERIODS to get date ranges for statuses or to FND_APPLICATION for descriptive application names.

Related Objects

As per the provided metadata, GL_PERIOD_STATUSES has integral relationships with several key objects. It references GL_PERIOD_TYPES via PERIOD_TYPE and FND_APPLICATION via APPLICATION_ID. Crucially, it is referenced by transactional tables like AX_BALANCES and AX_SLE_HEADERS (AutoInvoice tables), enforcing period validity for subledger entries. The SET_OF_BOOKS_ID foreign key points back to its own table, reflecting a hierarchical relationship for consolidation ledgers. The table is also central to standard Oracle APIs such as GL_PERIOD_STATUS_PKG and is the underlying source for key views like GL_PERIOD_STATUSES_V, which may join descriptive flexfield data for reporting purposes.