Results for “gl_date_period_map”

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

Overview

GL_DATE_PERIOD_MAP is a General Ledger reference table in the Oracle E-Business Suite GL schema that stores date-to-period mappings. It resolves an individual accounting date into the accounting period that contains it, within the context of a specific accounting calendar (period set) and period type. Because Oracle General Ledger derives the period name for every journal entry, subledger transfer, and report from the accounting date supplied, this table acts as the authoritative lookup that answers the question "which period does this date belong to?" for a given calendar definition.

The table is populated and maintained by the Accounting Calendar definition process. When a calendar is defined or regenerated, General Ledger builds the date-to-period rows across the valid date range of the period set, so that any accounting date can be resolved to exactly one period name without ambiguity. Its presence enables consistent period derivation regardless of whether the caller supplies the period name explicitly or only provides an accounting date.

From a data modeling perspective, the Data Vault classification suggested by the foreign-key structure is link. The table does not hold descriptive attributes about a single business entity; instead it represents an associative relationship that connects a period set, a period type, an accounting date, and the resulting period name. This makes it a resolution bridge between the calendar definitions and the transactional facts that post against them.

Key Information Stored

The documented physical schema contains nine columns, of which the following are the most significant:

• PERIOD_SET_NAME — the accounting calendar (period set) to which the mapping belongs. This is a foreign key to GL_PERIOD_SETS and scopes every mapping row to a single calendar.
• ACCOUNTING_DATE — the individual date being mapped. It represents the effective accounting date supplied on transactions and journal lines.
• PERIOD_NAME — the accounting period into which the accounting date falls. This is the primary resolution output of the table and is part of the unique business-key index.
• PERIOD_TYPE — the period type within the calendar (for example, a monthly, quarterly, or weekly type). This is a foreign key to GL_PERIOD_TYPES and qualifies which set of periods the mapping applies to.
• CREATION_DATE, CREATED_BY — standard WHO audit columns recording when and by whom the mapping row was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording the most recent modification and the login under which it occurred.

The surrogate primary key is defined by the constraint GL_DATE_PERIOD_MAP_PK over (PERIOD_SET_NAME, ACCOUNTING_DATE, PERIOD_TYPE). A separate unique index, GL_DATE_PERIOD_MAP_U1, covers (PERIOD_SET_NAME, PERIOD_TYPE, ACCOUNTING_DATE, PERIOD_NAME) and is the strongest business-key candidate, since it adds the resulting period name and thereby guarantees that a given date maps to only one period name per calendar and period type.

Common Use Cases and Queries

The most common use is period derivation: given an accounting date, a calendar, and a period type, return the corresponding period name. A representative query is:

• SELECT period_name FROM gl_date_period_map WHERE period_set_name = :p_set AND period_type = :p_type AND accounting_date = :acct_date;

Reporting uses include period-to-date and calendar-exception analysis, such as identifying accounting dates that fall into unusual or adjusting periods, and validating subledger transaction dates against the calendar before transfer to General Ledger. A range-based pattern is useful for resolving many dates at once:

• SELECT accounting_date, period_name FROM gl_date_period_map WHERE period_set_name = :p_set AND period_type = :p_type AND accounting_date BETWEEN :start_date AND :end_date ORDER BY accounting_date;

Reconciliation and diagnostics scenarios also benefit from this table — for example, confirming that a calendar was generated across the expected date range, or explaining why a journal posted to a period different from the one a user expected. Because the table is keyed on the exact accounting date, it is well suited to point lookups and to date-range scans filtered first by period set and period type.

Related Objects

• GL_PERIOD_SETS — referenced by GL_DATE_PERIOD_MAP.PERIOD_SET_NAME; defines the accounting calendars that scope each mapping.
• GL_PERIOD_TYPES — referenced by GL_DATE_PERIOD_MAP.PERIOD_TYPE; defines the period type used to qualify mappings.
• GL_PERIODS — holds the period definitions (period name, start and end dates, year) that the mapping resolves dates into.
• GL_JE_HEADERS — journal headers carry an accounting date and period name that must be consistent with the calendar mapping.
• GL_JE_LINES — journal lines inherit the header accounting date and derived period.
• GL_SETS_OF_BOOKS — associates a chart of accounts and calendar (period set) used with these mappings.
• GL_DAILY_CONVERSION_TYPES / GL_CURRENCIES — supporting General Ledger reference objects commonly queried alongside calendar data for period reporting.

Together these objects form the calendar and journal infrastructure that GL_DATE_PERIOD_MAP bridges, making it a small but essential reference table for accurate period determination in Oracle EBS 12.1.1 and 12.2.2.