Search Results gl_period_statuses_pkg




Overview
Explore in AI Chat

Overview

APPS.GL_PERIOD_STATUSES_PKG is a server-side PL/SQL package in the Oracle E-Business Suite General Ledger module. Its purpose is to manage the rows that constitute the accounting period status calendar for every ledger defined in the application. The GL_PERIOD_STATUSES table determines, for each combination of ledger, period, and period type, whether that period is Open, Closed, Permanently Closed, or Never Opened. Because almost every GL and subledger transaction validates the target period against this table, the package is central to period control and to the period-close process in both release 12.1.1 and 12.2.2.

The package supplies the programmatic interface used by the Period Statuses form and by the concurrent programs that populate and extend the period calendar. It also exposes utility functions that other GL packages and external modules call to derive period identifiers, default periods, and relative period offsets. The documented package metadata classifies the object as a general-purpose API (classification OTHER) rather than a public, formally versioned open interface, so its procedures are primarily intended for internal GL use and for controlled extension by oracle-adjacent code.

Key Procedures and Functions

The ETRM metadata documents 24 procedures and functions. They fall into recognizable groups:

Because the package body is marked VALID and is not referenced by any database object, these procedures are invoked as top-level calls rather than through dependencies.

Tables Accessed

Usage Notes

In standard EBS operation, the package is driven by the GL Period Statuses form and by the concurrent programs that open and close periods, including the Period Close and Open Period processes. Administrators creating a new ledger rely on INITIALIZE_PERIOD_STATUSES to seed the calendar, and ongoing close activity uses the update and delete procedures. Custom code and extensions should call the package only where a supported form action cannot accomplish the same result, because direct manipulation of GL_PERIOD_STATUSES can bypass calendar integrity checks. Developers integrating subledgers or external systems typically use the retrieval functions such as GET_NEXT_PERIOD and DEFAULT_ACTUAL_PERIOD to resolve period identifiers, while the DFF update procedure is used when period status descriptive flexfields must be maintained programmatically.