Search Results recurring_line_num

Overview

The GL_RECURRING_LINE_CALC_RULES table is a core data structure within the Oracle E-Business Suite General Ledger (GL) module, specifically for versions 12.1.1 and 12.2.2. It stores the detailed calculation rules that define the behavior of individual lines within a recurring journal entry or a budget formula. This table is essential for automating the generation of periodic journal entries and budget amounts, enabling consistent and rule-based financial postings. Its primary role is to serve as the child table to GL_RECURRING_LINES, where each line can have one or more associated calculation rules to determine its account, currency, and amount.

Key Information Stored

The table's structure is defined by a composite primary key that uniquely identifies each calculation rule. The key columns are RECURRING_HEADER_ID, which links to the parent recurring batch; RECURRING_LINE_NUM, which identifies the specific line within that batch; and RULE_NUM, which sequences multiple rules for a single line. Other critical columns define the rule's logic and targets. These include ASSIGNED_CODE_COMBINATION, which holds the target accounting flexfield (CCID) for the generated entry, and TEMPLATE_ID, which references a GL_SUMMARY_TEMPLATES for aggregated calculations. Currency-related columns such as ENTERED_CURRENCY, LEDGER_CURRENCY, and the legacy CURRENCY_CODE_11I manage multi-currency transactions. The table also contains columns for specifying calculation formulas, statistical amounts, and rule types that govern how the line is populated during journal generation.

Common Use Cases and Queries

A primary use case is troubleshooting or auditing the setup of complex recurring journals, particularly when a line's generated value is unexpected. Developers and functional consultants often query this table to understand the complete rule set driving automated entries. A common query pattern involves joining to the parent line and header tables to review all rules for a specific recurring journal batch.

• Sample Query to List Calculation Rules: SELECT rule.recurring_header_id, rule.recurring_line_num, rule.rule_num, rule.assigned_code_combination FROM gl_recurring_line_calc_rules rule, gl_recurring_headers header WHERE rule.recurring_header_id = header.recurring_header_id AND header.name = '<BATCH_NAME>' ORDER BY 1,2,3;
• Reporting Use Case: Generating a specification document that maps each recurring journal line to its destination accounts and calculation logic for internal control purposes.
• Data Fix Scenario: Identifying and updating rules that reference an invalid or inactive code combination ID (ASSIGNED_CODE_COMBINATION) by joining to GL_CODE_COMBINATIONS.

Related Objects

The GL_RECURRING_LINE_CALC_RULES table maintains strict referential integrity with several key EBS objects, as documented in its foreign key constraints. Its existence is dependent on a parent recurring line.

• GL_RECURRING_LINES: The direct parent table. Each record in GL_RECURRING_LINE_CALC_RULES is linked via the composite foreign key (RECURRING_HEADER_ID, RECURRING_LINE_NUM).
• GL_CODE_COMBINATIONS: References the ASSIGNED_CODE_COMBINATION column to validate the target account for the calculated amount.
• GL_SUMMARY_TEMPLATES: References the TEMPLATE_ID column for rules that utilize summary account templates in their calculations.
• FND_CURRENCIES: Referenced by three separate columns: CURRENCY_CODE_11I, LEDGER_CURRENCY, and ENTERED_CURRENCY, ensuring valid currency codes are used in monetary rules.