Search Results gl_recurring_headers_uk1

Overview

The GL_RECURRING_HEADERS table is a core data object within the Oracle E-Business Suite General Ledger (GL) module. It serves as the master definition table for recurring journal entries and budget formulas. These are standardized journal templates designed to automate the posting of repetitive accounting transactions, such as monthly depreciation, rent, or loan payments, thereby enhancing efficiency and ensuring consistency. The table stores the header-level metadata that defines the template's properties, including its name, frequency, currency, and associated ledger. Each header record is linked to one or more line definitions in the GL_RECURRING_LINES table, which together form a complete, reusable journal entry template.

Key Information Stored

The table's structure is centered on defining the template's identity and execution parameters. Its primary key is RECURRING_HEADER_ID, a unique system-generated identifier. A significant business key is the combination of NAME and RECURRING_BATCH_ID (enforced by the GL_RECURRING_HEADERS_UK1 unique key), ensuring template names are unique within a specific batch. Critical foreign key columns establish vital relationships: LEDGER_ID links to GL_SETS_OF_BOOKS_11I (defining the applicable ledger), RECURRING_BATCH_ID links to GL_RECURRING_BATCHES (for organizational grouping), PERIOD_TYPE links to GL_PERIOD_TYPES (defining the accounting period frequency, e.g., Month), and CURRENCY_CODE links to FND_CURRENCIES. Other essential columns typically include STATUS, ENABLED_FLAG, LAST_UPDATE_DATE, and CREATION_DATE for lifecycle management.

Common Use Cases and Queries

The primary use case is the creation, review, and maintenance of recurring journal templates via the Oracle GL application interface. Technically, common queries involve auditing and integration. For instance, to identify all active recurring templates for a specific ledger, one might query: SELECT name, currency_code, period_type FROM gl_recurring_headers WHERE ledger_id = :ledger_id AND enabled_flag = 'Y';. For troubleshooting, a join with the lines table is frequent: SELECT rh.name, rl.code_combination_id, rl.entered_dr FROM gl_recurring_headers rh, gl_recurring_lines rl WHERE rh.recurring_header_id = rl.recurring_header_id AND rh.name = 'MONTHLY_RENT';. Reporting often focuses on summarizing templates by batch or period type to assess automation coverage.

Related Objects

GL_RECURRING_HEADERS is a central hub with several key dependencies, as indicated by its foreign key relationships. Child objects include GL_RECURRING_LINES, which holds the detailed accounting lines for each template. Parent and reference objects are GL_SETS_OF_BOOKS_11I (ledger), GL_RECURRING_BATCHES, GL_PERIOD_TYPES, and FND_CURRENCIES. Crucially, the table is the source for generating actual journal entries; the GL_JE_HEADERS table references it via the FROM_RECURRING_HEADER_ID column when a recurring template is generated. Similarly, GL_ARCHIVE_HEADERS references it for archival purposes. Understanding these relationships is essential for any data flow analysis or custom extension involving automated journal creation.