Search Results from_subsidiary

Overview

GL_IEA_SEGMENT_RULE_MAP_V is a General Ledger view in Oracle E-Business Suite that exposes the segment mapping rules used by the Intercompany Elimination and Adjustments (IEA) engine. In Oracle EBS 12.1.1 and 12.2.2 the IEA feature supports the automatic creation of balancing and elimination entries between legal entities, subsidiaries, and balancing segments. The mapping rules stored in the underlying GL_IEA_SEGMENT_RULE_MAP table determine how source segment values, transaction types, and subsidiary identifiers are translated into target segment values when intercompany transactions are processed.

The view performs three important functions. First, it resolves surrogate identifiers into descriptive names for transaction types and subsidiaries through outer joins to GL_IEA_TRANSACTION_TYPES and GL_IEA_SUBSIDIARIES. Second, it substitutes the literal "OTHER" wherever a special sentinel value (-1) is stored for transaction type or subsidiary, using GL_LOOKUPS to supply the meaning. Third, it exposes audit columns and fifteen descriptive flexfield attribute columns alongside the core mapping definition. Because the IEA setup is largely reference data, this view is primarily used for reporting, validation, and integration rather than transactional processing. The user's search term "transaction_type" maps directly to the TRANSACTION_TYPE_ID and TRANSACTION_TYPE columns, which are central to how rules are scoped.

Underlying Base Objects

The view is defined over five documented base objects:

• GL_IEA_SEGMENT_RULE_MAP (aliased RUL) — the driving table holding the actual segment mapping rules, including the source and target segment values, transaction type, and subsidiary identifiers.
• GL_IEA_TRANSACTION_TYPES (aliased TYP) — supplies the transaction type name via an outer join on TRANSACTION_TYPE_ID.
• GL_IEA_SUBSIDIARIES (aliased SUB1 and SUB2) — supplies the "to" and "from" subsidiary names via outer joins on TO_SUBSIDIARY_ID and FROM_SUBSIDIARY_ID respectively.
• GL_LOOKUPS (aliased LK) — provides the literal meaning (the string "OTHER") used when the transaction type or subsidiary ID equals -1. The lookup is filtered to LOOKUP_TYPE = 'LITERAL' and a specific lookup code.

All joins to TYP, SUB1, and SUB2 are outer joins, ensuring that rows with the sentinel -1 value or with missing reference data still appear, with their descriptive columns substituted by the GL_LOOKUPS meaning. This design makes the view behave as a denormalized, human-readable representation of the rule map.

Key Columns

• SEGMENT_MAP_ID — primary identifier of the mapping rule; useful for joining back to the base table.
• TRANSACTION_TYPE_ID / TRANSACTION_TYPE — the transaction type that scopes the rule. When the ID is -1, the DECODE returns the literal "OTHER", indicating the rule applies to all other transaction types.
• FROM_SUBSIDIARY_ID / FROM_SUBSIDIARY and TO_SUBSIDIARY_ID / TO_SUBSIDIARY — the source and destination subsidiaries, with the same -1/"OTHER" literal substitution applied.
• FROM_SEG_VALUE and TO_SEG_VALUE — the segment values being mapped from and to, which form the core of the intercompany translation logic.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Who columns for auditing.
• ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — descriptive flexfield columns supporting the IEA segment rule flexfield definition.

Common Use Cases and Queries

A typical reporting requirement is to list all mapping rules for a given transaction type so that setup inconsistencies can be detected:

SELECT transaction_type, from_subsidiary, to_subsidiary, from_seg_value, to_seg_value
FROM gl_iea_segment_rule_map_v
WHERE transaction_type = 'Intercompany Sales';

Because the view resolves IDs to names, an integration or reconciliation report can join it to the IEA transaction tables without repeating the DECODE logic:

SELECT segment_map_id, transaction_type_id, transaction_type,
       from_seg_value, to_seg_value
FROM gl_iea_segment_rule_map_v
ORDER BY transaction_type_id, segment_map_id;

The view also supports validation checks that identify rules mapped to the "OTHER" literal, which represent catch-all rules that may need review:

SELECT * FROM gl_iea_segment_rule_map_v
WHERE from_subsidiary = 'OTHER'
  OR to_subsidiary = 'OTHER';

In 12.2.2 the view metadata notes it is "not implemented in this database" in the sampled dictionary, indicating it exists only where the IEA module has been configured; queries should therefore be validated against the target instance before being embedded in production reporting or integration code.