Search Results gl_date_period_map

Overview

The GL_DATE_PERIOD_MAP table is a core reference table within the Oracle E-Business Suite General Ledger (GL) module. It serves as a master mapping engine, providing the definitive association between any valid calendar date and its corresponding accounting period within a given financial calendar. This mapping is fundamental to the integrity of all transactional accounting data, as it ensures every financial transaction posted with an accounting date is correctly assigned to the appropriate open or closed period for posting, reporting, and consolidation. Its role is critical for period-end closing procedures, financial reporting accuracy, and the operation of any process that requires date-to-period validation, such as journal import, mass allocations, and currency translation.

Key Information Stored

The table's structure is optimized for its singular mapping purpose. The primary key, enforced by the GL_DATE_PERIOD_MAP_PK constraint, is a composite of three columns: PERIOD_SET_NAME, ACCOUNTING_DATE, and PERIOD_TYPE. This design enforces uniqueness and allows for multiple accounting calendars (Period Sets) and period types (e.g., Month, Quarter) to coexist within the same instance. The ACCOUNTING_DATE column stores the specific calendar date, while the associated period information (like period name, start date, end date, and status) is derived by joining to related period definition tables. The table itself acts as a key lookup, with the actual period details residing in normalized child tables.

Common Use Cases and Queries

A primary use case is validating or determining the accounting period for a given date during data entry or interface processing. For example, a custom invoice interface might use this table to verify that an invoice date falls within an open period before creating journals. Common reporting queries involve joining this table to transactional data like GL_JE_BATCHES or GL_JE_LINES to report on activity by period name rather than raw dates. A fundamental query pattern is:

• SELECT gp.period_name, gp.period_num, gp.period_year FROM gl_date_period_map gdpm, gl_periods gp WHERE gdpm.period_set_name = gp.period_set_name AND gdpm.period_type = gp.period_type AND gdpm.acct_period_id = gp.period_id AND gdpm.accounting_date = :p_date AND gdpm.period_set_name = :p_period_set;

This table is also essential for creating time-based aggregations in financial reports, as it provides the authoritative link between the date dimension and the organizational fiscal calendar.

Related Objects

The GL_DATE_PERIOD_MAP table sits at the center of the financial calendar hierarchy, maintaining documented foreign key relationships to core setup tables. As per the provided metadata, it references the following objects:

• GL_PERIOD_SETS: Joined via the PERIOD_SET_NAME column. This defines the financial calendar (e.g., "Corporate Calendar") to which the date mapping belongs.
• GL_PERIOD_TYPES: Joined via the PERIOD_TYPE column. This defines the type of period (e.g., Month, Quarter) for the mapping.

In practice, to retrieve a full period description, queries typically join through GL_DATE_PERIOD_MAP to GL_PERIODS (using implied relationships like PERIOD_SET_NAME, PERIOD_TYPE, and an internal ACCT_PERIOD_ID), which holds the period name, year, number, and status. This table is referenced by numerous GL transactional tables and public APIs (e.g., GL_DATE_API) that require period validation.