Results for “gl_recurring_headers_pk”

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

Overview

GL_RECURRING_HEADERS is a General Ledger table in the Oracle E-Business Suite (12.1.1 and 12.2.2) that stores the header definitions for recurring journal entries and budget formulas. Each row represents a named recurring template — for example, a monthly accrual, a standing cost allocation, or a recurring budget formula — that General Ledger can generate on demand or on a defined schedule. The table holds the ledger assignment, journal category, currency, period type, effective date range, and enablement controls that govern how and when a recurring definition is processed. The actual debit and credit lines associated with each header reside in GL_RECURRING_LINES.

The ETRM relationship metadata classifies GL_RECURRING_HEADERS as satellite-leaning. In a Data Vault model this suggests treating the table as a satellite attached to a hub keyed on RECURRING_HEADER_ID (or the business key NAME plus RECURRING_BATCH_ID), with descriptive attributes such as LEDGER_ID, JE_CATEGORY_NAME, and ENABLED_FLAG maintained as satellite payload. This is a heuristic suggestion only; the physical table remains a standard GL transactional-setup table.

Key Information Stored

The table contains 30 documented columns. The most operationally significant are:

• RECURRING_HEADER_ID — Surrogate primary key (GL_RECURRING_HEADERS_PK) that uniquely identifies each recurring definition.
• NAME — The user-facing name of the recurring journal or budget formula; combined with RECURRING_BATCH_ID it forms business-key candidate GL_RECURRING_HEADERS_UK1 (and U2).
• LEDGER_ID — Foreign key to GL_SETS_OF_BOOKS_11I identifying the ledger (set of books) in which the recurring entry is generated.
• RECURRING_BATCH_ID — Foreign key to GL_RECURRING_BATCHES, grouping the definition into a recurring batch.
• JE_CATEGORY_NAME — The journal category assigned to generated entries.
• CURRENCY_CODE — Foreign key to FND_CURRENCIES; the currency of the recurring entry.
• CURRENCY_CONVERSION_TYPE — The conversion rate type applied when the entry currency differs from the ledger currency.
• PERIOD_TYPE — Foreign key to GL_PERIOD_TYPES, defining the accounting period frequency.
• ENABLED_FLAG — Controls whether the definition is active for generation.
• ALLOCATION_FLAG — Indicates whether the recurring definition behaves as an allocation.
• START_DATE_ACTIVE / END_DATE_ACTIVE — The effective date window during which the definition may be run.
• LAST_EXECUTED_PERIOD_NAME / LAST_EXECUTED_DATE — Audit fields recording the most recent generation.
• ATTRIBUTE1–ATTRIBUTE10, CONTEXT — Descriptive flexfield columns for client-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical uses include identifying all active recurring definitions for a ledger, auditing which definitions have not yet been executed in the current period, and reconstructing the source of a generated journal entry.

• List enabled recurring journals for a ledger:
  SELECT RECURRING_HEADER_ID, NAME, JE_CATEGORY_NAME, PERIOD_TYPE FROM GL_RECURRING_HEADERS WHERE LEDGER_ID = :ledger AND ENABLED_FLAG = 'Y';
• Find definitions not yet run for a period:
  SELECT NAME, LAST_EXECUTED_PERIOD_NAME FROM GL_RECURRING_HEADERS WHERE LAST_EXECUTED_PERIOD_NAME <> :period_name OR LAST_EXECUTED_PERIOD_NAME IS NULL;
• Trace generated entries back to their definition:
  SELECT j.JE_HEADER_ID, j.NAME, r.NAME FROM GL_JE_HEADERS j JOIN GL_RECURRING_HEADERS r ON j.FROM_RECURRING_HEADER_ID = r.RECURRING_HEADER_ID;
• Drill into the detail lines:
  SELECT * FROM GL_RECURRING_LINES WHERE RECURRING_HEADER_ID = :id;
• Effective-date reporting: filter on START_DATE_ACTIVE/END_DATE_ACTIVE against a target period.

Related Objects

• GL_RECURRING_LINES — Detail lines; joins on RECURRING_LINES.RECURRING_HEADER_ID = RECURRING_HEADERS.RECURRING_HEADER_ID.
• GL_RECURRING_BATCHES — Batch grouping; joins on RECURRING_BATCH_ID.
• GL_SETS_OF_BOOKS_11I — Ledger definition; joins on LEDGER_ID.
• GL_PERIOD_TYPES — Period frequency; joins on PERIOD_TYPE.
• FND_CURRENCIES — Currency validation; joins on CURRENCY_CODE.
• GL_JE_HEADERS — Generated journals; referenced via FROM_RECURRING_HEADER_ID.
• GL_ARCHIVE_HEADERS — Archived journals; referenced via FROM_RECURRING_HEADER_ID.

These relationships make GL_RECURRING_HEADERS the central reference point for defining, executing, and auditing recurring General Ledger activity.