Search Results gl_iea_segment_map_u2

Overview

GL.GL_IEA_SEGMENT_MAP is an Oracle General Ledger table that defines the intra-enterprise accounting (IEA) segment derivation rules used when the system automatically generates balancing accounts during intercompany processing. In Oracle E-Business Suite 12.1.1 and 12.2.2, this table is the metadata layer that instructs the accounting engine how to derive segment values when generating Sender Clearing, Receiver Clearing, or Receiver Distribution accounts across two chart of accounts contexts (sender and receiver). It is owned by the GL schema, resides in the APPS_TS_TX_DATA tablespace, and carries an Oracle Internal Use Only designation, meaning direct access should normally occur only through standard Applications programs or supported reporting extracts.

Under a Data Vault modeling heuristic, this object is hub-leaning: SEGMENT_MAP_ID functions as the stable surrogate primary key (via GL_IEA_SEGMENT_MAP_PK), while the account-generation attributes behave as descriptive payload. Practically, the combination of chart of accounts and column target described by the unique index GL_IEA_SEGMENT_MAP_U2 operates as the business key, making the physical table closer to a hub-plus-satellite hybrid than a pure transactional fact.

Key Information Stored

The table contains 29 documented columns. The most operationally significant are listed below, distinguishing the surrogate PK from business-key candidates.

• SEGMENT_MAP_ID — NUMBER(15), the surrogate primary key and the column defined by unique index GL_IEA_SEGMENT_MAP_U1. The FK GL_IEA_SEGMENT_RULE_MAP.SEGMENT_MAP_ID points here.
• GENERATE_TYPE_CODE — the account-generation category (Sender Clearing, Receiver Clearing, or Receiver Distribution) that scopes the derivation rule.
• SENDER_CHART_OF_ACCT_ID — key flexfield structure ID for the sender's chart of accounts.
• RECEIVER_CHART_OF_ACCT_ID — key flexfield structure ID for the receiver's chart of accounts.
• TO_APPLICATION_COLUMN_NAME — VARCHAR2(30), the target segment column on the generated chart of accounts. Together with the two chart-of-accounts IDs and GENERATE_TYPE_CODE, it forms the unique index GL_IEA_SEGMENT_MAP_U2 business key.
• FROM_APPLICATION_COLUMN_NAME — VARCHAR2(30), the source segment column from which values are read.
• SEGMENT_MAP_TYPE_CODE — the derivation action applied (for example, Assign Single Value or a mapping-driven derivation).
• SINGLE_VALUE — VARCHAR2(25), the literal segment value used when the map type is Assign Single Value.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Who audit columns.
• ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — descriptive flexfield segments available for customer extensions.

Common Use Cases and Queries

Typical usage centers on auditing which derivation rules exist for a given pair of charts of accounts and diagnosing why generated intercompany entries populate unexpected segment values.

• Listing all segment maps defined for a sender/receiver chart pair: SELECT segment_map_id, generate_type_code, to_application_column_name, segment_map_type_code, single_value FROM gl_iea_segment_map WHERE sender_chart_of_acct_id = :p_sender AND receiver_chart_of_acct_id = :p_receiver;
• Finding rules that assign fixed segment values: filter on segment_map_type_code with a non-null single_value.
• Reporting maps by generation type to reconcile Sender Clearing versus Receiver Clearing/Distribution configurations.
• Resolving a map from a rule: join GL_IEA_SEGMENT_RULE_MAP.SEGMENT_MAP_ID to SEGMENT_MAP_ID to trace an intercompany rule to its constituent segment derivations.
• Change-audit queries using the Who columns to identify modifications made since a given LAST_UPDATE_DATE.

Related Objects

The principal dependency is the child table GL.GL_IEA_SEGMENT_RULE_MAP, which references this table through SEGMENT_MAP_ID. Additional significant related objects include:

• GL.GL_IEA_SEGMENT_RULE_MAP — join on SEGMENT_MAP_ID; the FK that binds rule definitions to segment maps.
• GL.GL_IEA_RULES / intercompany rule headers — parent containers of the rule-and-map hierarchy.
• FND_ID_FLEX_STRUCTURES — resolves SENDER_CHART_OF_ACCT_ID and RECEIVER_CHART_OF_ACCT_ID to chart-of-accounts definitions.
• FND_ID_FLEX_SEGMENTS — resolves the segment column names referenced by FROM_APPLICATION_COLUMN_NAME and TO_APPLICATION_COLUMN_NAME.
• GL.GL_JE_BATCHES / GL_JE_HEADERS / GL_JE_LINES — downstream journal objects populated using the accounts these maps derive.
• FND_DESCR_FLEX_COLUMN_USAGES / FND_DESCR_FLEX_CONTEXTS — describe the descriptive flexfield attributes and CONTEXT.

Because the object is flagged Oracle Internal Use Only, extraction should be performed through supported reporting views or standard IEA accounting programs rather than direct DML.