Search Results gl_iea_segment_map




Overview
Explore in AI Chat

Overview

GL_IEA_SEGMENT_MAP is a General Ledger table in the Oracle E-Business Suite (12.1.1 and 12.2.2) that stores the automatic account generation segment mapping rules for the Global Intercompany System (GIS). The table belongs to the GL schema and is classified as VALID in the ETRM repository. Its purpose is to define, at the segment level, how individual account segments are derived or mapped when intercompany transactions are processed and accounting entries are generated automatically by the Global Intercompany System.

Because the Global Intercompany System must produce balanced, valid account combinations across multiple ledgers and balancing segments, GL_IEA_SEGMENT_MAP provides the rule definitions that translate a source segment into a destination segment based on configuration. The table is therefore a configuration and setup object, populated during implementation and maintained through the GIS setup flows rather than by day-to-day transactional activity.

From a Data Vault modeling perspective (a heuristic classification mined from the foreign-key structure), this table is hub-leaning. It acts as a reference and distribution point for segment mapping identifiers that are consumed downstream, particularly by GL_IEA_SEGMENT_RULE_MAP, which carries a foreign key back to this table.

Key Information Stored

The table contains 29 documented columns. The most significant are summarized below.

The second unique index, GL_IEA_SEGMENT_MAP_U2, is defined over GENERATE_TYPE_CODE, SENDER_CHART_OF_ACCT_ID, RECEIVER_CHART_OF_ACCT_ID, and TO_APPLICATION_COLUMN_NAME, establishing the compound business key that guarantees one mapping rule per generate type and chart-of-accounts combination.

Common Use Cases and Queries

Typical use cases include setup verification, troubleshooting intercompany account generation, and reporting on segment mapping configuration.

  • Listing all mapping rules for a given generate type and ledger pairing:
SELECT segment_map_id, generate_type_code, sender_chart_of_acct_id,
       receiver_chart_of_acct_id, from_application_column_name,
       to_application_column_name, segment_map_type_code, single_value
FROM   gl_iea_segment_map
WHERE  generate_type_code = :p_generate_type;
  • Joining to the rule map to see how segments are grouped into rules:
SELECT m.segment_map_id, r.segment_rule_map_id, m.to_application_column_name
FROM   gl_iea_segment_map m,
       gl_iea_segment_rule_map r
WHERE  m.segment_map_id = r.segment_map_id;
  • Validating the compound business key by checking for duplicate combinations of generate type, sender chart, receiver chart, and target column.
  • Reporting on flexible attribute configuration (ATTRIBUTE1..15) where customers have extended the mapping behavior.

Related Objects

  • GL_IEA_SEGMENT_RULE_MAP — The principal dependent table; its SEGMENT_MAP_ID column is a foreign key referencing GL_IEA_SEGMENT_MAP.SEGMENT_MAP_ID. This is the key join path for rule-level reporting.
  • GL_IEA_SEGMENT_MAP_PK / _U1 / _U2 — Primary and unique indexes enforcing row identity and the compound business key.

Additional related configuration objects in the same GIS family include the intercompany account generation rule and definition tables that consume the generated segment mappings, along with the GL intercompany APIs used to maintain this setup programmatically. Because the documented metadata identifies only GL_IEA_SEGMENT_RULE_MAP as the direct dependent object, that relationship should be treated as the primary integration point when building queries or extensions around GL_IEA_SEGMENT_MAP.