Search Results gl_iea_segment_rule_map




Overview
Explore in AI Chat

Overview

GL_IEA_SEGMENT_RULE_MAP is a General Ledger (GL) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores individual segment mapping rules used by the Automatic Account Generation feature of the Global Intercompany System (GIS). When intercompany transactions are created or processed, GIS can derive accounting flexfield segment values automatically rather than requiring users to specify them. This table holds the granular, per-segment mapping definitions that drive that derivation logic, linking a mapping rule set to specific transaction types, subsidiary pairs, and source segment values.

The table resides in the GL schema and is documented as VALID in the ETRM repository. Grounded in the foreign key structure, the heuristic Data Vault classification is satellite-leaning: the table records descriptive rule attributes that depend on and extend a parent mapping definition, rather than acting as a standalone hub of business entities or a pure many-to-many link. Practically, it should be modeled as a detail/satellite table keyed to GL_IEA_SEGMENT_MAP.

Key Information Stored

The documented physical schema contains 27 columns. The most significant are:

  • SEGMENT_MAP_ID — The identifier of the parent mapping rule set. This is a foreign key to GL_IEA_SEGMENT_MAP and forms part of the primary key, tying each row to its owning rule definition.
  • TRANSACTION_TYPE_ID — Identifies the intercompany transaction type to which the segment rule applies, allowing different mappings per transaction category.
  • TO_SUBSIDIARY_ID — The receiving subsidiary in the intercompany relationship for which the mapping is defined.
  • FROM_SUBSIDIARY_ID — The initiating subsidiary in the intercompany relationship.
  • FROM_SEG_VALUE — The source segment value that triggers the mapping rule.
  • TO_SEG_VALUE — The target segment value that Automatic Account Generation assigns when the source conditions match.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns capturing audit and concurrency information.
  • ATTRIBUTE1 through ATTRIBUTE15, CONTEXT — The standard EBS descriptive flexfield (DFF) columns that allow customer-defined extensions to the mapping rule.

The primary key is documented as GL_IEA_SEGMENT_RULE_MAP_PK, comprising SEGMENT_MAP_ID, TRANSACTION_TYPE_ID, TO_SUBSIDIARY_ID, FROM_SUBSIDIARY_ID, and FROM_SEG_VALUE. A unique index, GL_IEA_SEGMENT_RULE_MAP_U1, is defined over the same column set, confirming this composite as the business-key candidate that enforces uniqueness of each rule combination. The sole documented foreign key is SEGMENT_MAP_ID referencing GL_IEA_SEGMENT_MAP.

Common Use Cases and Queries

Typical scenarios include validating automatic account generation configuration, troubleshooting intercompany transactions that fail to derive the expected account segments, and auditing mapping coverage across subsidiaries and transaction types.

SELECT m.SEGMENT_MAP_ID,
       m.TRANSACTION_TYPE_ID,
       m.FROM_SUBSIDIARY_ID,
       m.TO_SUBSIDIARY_ID,
       m.FROM_SEG_VALUE,
       m.TO_SEG_VALUE
FROM   GL_IEA_SEGMENT_RULE_MAP m
WHERE  m.SEGMENT_MAP_ID = :p_segment_map_id
ORDER  BY m.TRANSACTION_TYPE_ID, m.FROM_SUBSIDIARY_ID;

To trace which rule set governs a given subsidiary pair and transaction type, join to the parent GL_IEA_SEGMENT_MAP and filter on the composite key columns. Reporting queries frequently resolve TO_SUBSIDIARY_ID and FROM_SUBSIDIARY_ID through the subsidiary/legal entity tables, and TRANSACTION_TYPE_ID through the intercompany transaction type definition. Auditors leverage the audit columns to identify recently changed mapping rules that may affect period-end intercompany balances.

Related Objects

  • GL_IEA_SEGMENT_MAP — The parent table holding the mapping rule set; joined on GL_IEA_SEGMENT_RULE_MAP.SEGMENT_MAP_ID = GL_IEA_SEGMENT_MAP.SEGMENT_MAP_ID.
  • GL_IEA_SEGMENT_RULE_MAP_PK — The primary key constraint enforcing row uniqueness across the five key columns.
  • GL_IEA_SEGMENT_RULE_MAP_U1 — The unique index over SEGMENT_MAP_ID, TRANSACTION_TYPE_ID, TO_SUBSIDIARY_ID, FROM_SUBSIDIARY_ID, and FROM_SEG_VALUE.
  • Intercompany transaction type and subsidiary reference tables — Referenced logically via TRANSACTION_TYPE_ID, TO_SUBSIDIARY_ID, and FROM_SUBSIDIARY_ID for descriptive resolution.
  • Global Intercompany System (GIS) concurrent programs and APIs — Consume these rules during automatic account generation to populate intercompany accounting entries.