Search Results gl_recurring_lines




Overview
Explore in AI Chat

Overview

The GL_RECURRING_LINES table is a core data structure within the Oracle E-Business Suite General Ledger (GL) module. It serves as the detailed repository for the line-level information of both recurring journal entries and recurring budget formulas. A recurring journal entry is a template for a standard journal that is processed periodically (e.g., monthly rent expense), while a recurring budget formula is used to generate budget amounts based on calculations. This table stores the target account and amount details for each line of these recurring definitions, which the system uses to generate the actual journal or budget lines during the posting or budgeting process. Its existence is critical for automating and standardizing repetitive financial transactions, ensuring consistency and efficiency in period-end closing and budgeting activities.

Key Information Stored

The table's structure is defined by its primary key, which is a composite of RECURRING_HEADER_ID and RECURRING_LINE_NUM, linking each line unambiguously to its parent definition in the GL_RECURRING_HEADERS table. Key columns include CODE_COMBINATION_ID, which stores the target accounting flexfield (account) for the line, and ENTERED_CURRENCY_CODE, which defines the transaction currency. The table holds the monetary amounts for the line, typically in columns such as ENTERED_DR for entered debit amounts and ENTERED_CR for entered credit amounts. Other columns manage descriptive information like the line description, statistical amounts, and references. The foreign key relationships enforce data integrity, ensuring that every line references a valid recurring header, a valid code combination, and a valid currency.

Common Use Cases and Queries

A primary use case is auditing and troubleshooting the setup of recurring journals. For instance, to review all lines for a specific recurring journal batch, a query would join GL_RECURRING_LINES to GL_RECURRING_HEADERS. Another common scenario is identifying recurring entries that post to a specific account, which is useful for impact analysis before changing an account's status. A sample query pattern is:

  • SELECT rhl.recurring_header_id, rhl.recurring_line_num, rhl.code_combination_id, rhl.entered_dr, rhl.entered_cr, rh.name
  • FROM gl_recurring_lines rhl
  • JOIN gl_recurring_headers rh ON rhl.recurring_header_id = rh.recurring_header_id
  • WHERE rhl.code_combination_id = :target_ccid;

Reporting use cases include generating a catalog of all active recurring templates for process documentation or analyzing the distribution of recurring amounts across different natural account segments.

Related Objects

GL_RECURRING_LINES has integral relationships with several other GL objects. Its most direct parent is the GL_RECURRING_HEADERS table, which stores the header-level information like name, description, and period type. It references the GL_CODE_COMBINATIONS table to validate the target account and the FND_CURRENCIES table for the currency. A critical child object is the GL_RECURRING_LINE_CALC_RULES table, which stores the detailed calculation rules (source lines and formulas) used to derive amounts for budget formulas. When a recurring journal is generated, the data from this table, combined with its header, is used to create actual journal lines in the GL_JE_LINES table.