Results for “gl_intercompany_acc_sets”

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

Overview

GL_INTERCOMPANY_ACC_SETS is a General Ledger configuration table in the GL schema that stores intercompany transaction processing rules. It defines, per ledger and per journal source/category combination, how Oracle EBS should handle intercompany balancing — including which balancing segment to use, whether transactions must always balance, and the rule codes that govern segment balancing behavior. In Oracle EBS 12.1.1 and 12.2.2, this table is consulted by the intercompany balancing engine whenever a journal entry crosses balancing segments within a ledger.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. The table's grain is defined by its primary key rather than by an independent surrogate identity, and its non-key attributes (rule codes and flags) describe the balancing behavior attached to that business key. It therefore behaves less like a hub and more like a descriptive satellite keyed on ledger, source, and category. The primary key, GL_INTERCOMPANY_ACC_SETS_PK, comprises LEDGER_ID, JE_SOURCE_NAME, and JE_CATEGORY_NAME, which also forms the unique index GL_INTERCOMPANY_ACC_SETS_U1.

Key Information Stored

The table contains 28 documented columns. The most significant are:

• LEDGER_ID — foreign key to GL_LEDGERS; identifies the ledger to which the intercompany rule applies.
• JE_SOURCE_NAME and JE_CATEGORY_NAME — the journal source and category combination that scopes the rule.
• BALANCE_BY_CODE — the code controlling how the balancing segment is determined for intercompany journals.
• BAL_SEG_RULE_CODE — the balancing segment rule that determines which segment value is used for the balancing line.
• ALWAYS_BALANCE_FLAG — indicates whether intercompany transactions must always be balanced (for example, by generating automatic balancing lines).
• DEFAULT_BAL_SEG_VALUE — the default balancing segment value applied when no rule resolves a value.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns, providing extensibility without schema change.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

The primary key (LEDGER_ID, JE_SOURCE_NAME, JE_CATEGORY_NAME) is the business-key candidate surfaced by the unique index. There is no separate generated surrogate key beyond this composite; the FK relationship to GL_LEDGERS (on LEDGER_ID) is the sole documented foreign key.

Common Use Cases and Queries

Typical uses include auditing which ledgers have intercompany balancing configured, verifying source/category coverage, and extracting rule definitions for reporting or migration. A common pattern joins the rule to its parent ledger:

• List all intercompany rule sets for a ledger: SELECT JE_SOURCE_NAME, JE_CATEGORY_NAME, BALANCE_BY_CODE, BAL_SEG_RULE_CODE, ALWAYS_BALANCE_FLAG FROM GL.GL_INTERCOMPANY_ACC_SETS WHERE LEDGER_ID = :ledger_id;
• Join to GL_LEDGERS to retrieve ledger names/currencies: SELECT s.*, l.NAME FROM GL.GL_INTERCOMPANY_ACC_SETS s JOIN GL.GL_LEDGERS l ON s.LEDGER_ID = l.LEDGER_ID;
• Identify ledgers lacking a rule for a given source/category by outer-joining the table to a source/category list.
• Extract DFF context and attribute values for downstream ETL or reconciliation.

Related Objects

• GL_LEDGERS — parent table; joined on GL_INTERCOMPANY_ACC_SETS.LEDGER_ID = GL_LEDGERS.LEDGER_ID.
• GL_JE_SOURCES — validates the JE_SOURCE_NAME value.
• GL_JE_CATEGORIES — validates the JE_CATEGORY_NAME value.
• GL_JE_BATCHES and GL_JE_HEADERS — journal entries subject to these balancing rules.
• GL_JE_LINES — balancing lines generated for intercompany journals.
• GL_INTERCOMPANY_ACCOUNTS — related intercompany account mapping configuration.
• The GL Journal Import and Posting concurrent programs, plus the GL_JOURNAL_ENTRY_API, which consult this configuration during processing.