Search Results gl_iea_segment_rule_map_u1




Overview
Explore in AI Chat

Overview

The GL.GL_IEA_SEGMENT_RULE_MAP table is a General Ledger (GL) reference table that stores the mapping rules governing how source segment values are translated to target segment values during intercompany and intracompany balancing in Oracle E-Business Suite. It is a core configuration object for the Global Intercompany System (GIS) and its Intercompany Accounting (IEA) processing. The table defines, for a given segment map, which source segment value should be posted against which subsidiary pair and for which transaction type, thereby enabling the automatic generation of balancing entries across legal entities and balancing segments.

From a Data Vault modeling perspective, the heuristic classification supplied for this object is satellite-leaning. This reflects its descriptive, attribute-bearing nature: the table records the detailed business attributes (segment values, subsidiary identifiers, transaction type) that qualify the parent rule entity, rather than acting as a pure hub of distinct business keys or a link resolving many-to-many relationships. The primary key GL_IEA_SEGMENT_RULE_MAP_PK is a composite of the rule-defining and mapping-defining columns, and the table carries a dependent foreign key to the GL_IEA_SEGMENT_MAP parent.

Key Information Stored

The table comprises 27 documented columns. The most significant include:

  • SEGMENT_MAP_ID (NUMBER, 15) — The segment map rule defining column. It is a foreign key referencing GL_IEA_SEGMENT_MAP and forms part of both the primary key and the unique index.
  • TRANSACTION_TYPE_ID (NUMBER, 15) — Identifies the GIS transaction type, where the value -1 represents "Other".
  • FROM_SUBSIDIARY_ID (NUMBER, 15) — The source subsidiary; -1 signifies "Other".
  • TO_SUBSIDIARY_ID (NUMBER, 15) — The target subsidiary; -1 signifies "Other".
  • FROM_SEG_VALUE (VARCHAR2, 30) — The source segment value, or a value greater than 25 characters representing "Other".
  • TO_SEG_VALUE (VARCHAR2, 30) — The target segment value that the source value maps to.
  • ATTRIBUTE1 through ATTRIBUTE15 (VARCHAR2, 150 each) — Descriptive flexfield segments available for client-specific extensibility.
  • CONTEXT — The descriptive flexfield context column.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who columns tracking creation and modification audit information.

The surrogate primary key is composed of SEGMENT_MAP_ID, TRANSACTION_TYPE_ID, TO_SUBSIDIARY_ID, FROM_SUBSIDIARY_ID, and FROM_SEG_VALUE. The unique index GL_IEA_SEGMENT_RULE_MAP_U1 — the object the user searched for — shares this identical column set, confirming that it enforces the business-key uniqueness of the mapping definition. It is stored in the APPS_TS_TX_IDX tablespace, while the table data resides in APPS_TS_TX_DATA with a PCT Free of 10.

Common Use Cases and Queries

This table is primarily consumed by intercompany balancing and GIS transaction generation programs. Typical analytical and troubleshooting scenarios include:

  • Auditing which source segment values map to target values for a given subsidiary pair and transaction type.
  • Detecting incomplete or ambiguous mappings (for example, mapping "Other" placeholders).
  • Reporting the effective mapping matrix for a legal entity restructuring project.

A representative query joining to the parent segment map is:

  • SELECT m.segment_map_id, m.name, r.transaction_type_id, r.from_subsidiary_id, r.to_subsidiary_id, r.from_seg_value, r.to_seg_value FROM gl.gl_iea_segment_rule_map r, gl.gl_iea_segment_map m WHERE r.segment_map_id = m.segment_map_id AND r.from_subsidiary_id = :from_sub;

To list all mappings associated with a specific parent rule, query by SEGMENT_MAP_ID; to trace balance generation, correlate FROM_SEG_VALUE and TO_SEG_VALUE against posted GL journal lines.

Related Objects

  • GL.GL_IEA_SEGMENT_MAP — The direct parent object. The join column is GL_IEA_SEGMENT_RULE_MAP.SEGMENT_MAP_ID → GL_IEA_SEGMENT_MAP.SEGMENT_MAP_ID. This is the only documented foreign key relationship for the table.
  • GL.GL_IEA_SEGMENT_RULE_MAP_U1 — The unique index enforcing the business-key candidate columns, essential for tuning queries that filter on the primary-key set.
  • GIS/IEA balancing programs and concurrent processes — Standard Oracle Applications programs that read this table at runtime to derive balancing entries. Direct data access outside supported programs is not permitted, per Oracle guidance.
  • Subsidiary and transaction type reference objects — Referenced indirectly through FROM_SUBSIDIARY_ID, TO_SUBSIDIARY_ID, and TRANSACTION_TYPE_ID, where -1 denotes the "Other" placeholder.

Because Oracle classifies this object as internal, it should be queried only for read-only reporting and analysis, never modified directly outside standard Oracle Applications programs.