Results for “gl_iea_autogen_map_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_IEA_AUTOGEN_MAP_V is a General Ledger view that exposes the configuration mapping between sender and receiver chart of accounts used by the Intercompany and Intracompany Balancing / Intercompany Accounts (IEA) automatic generation engine. The view is defined over the base table GL_IEA_AUTOGEN_MAP, which stores the balancing rule setup that determines how Oracle General Ledger automatically creates intercompany and intracompany balancing lines during journal posting. Rather than presenting raw numeric chart-of-accounts identifiers, the view resolves those identifiers into human-readable chart of accounts names by joining to the FND_ID_FLEX_STRUCTURES_VL view.

In a multi-organization or multi-ledger environment, each legal entity or balancing segment may be associated with its own chart of accounts. The IEA engine requires an explicit mapping that tells it which sender chart of accounts pairs with which receiver chart of accounts, and which clearing and distribution rules apply on each side of the transaction. This view presents that mapping in a single, denormalized result set, making it suitable for reporting, diagnostic queries, and integration extracts. It is a reporting-oriented view rather than a maintenance object; the underlying GL_IEA_AUTOGEN_MAP table is maintained through the standard General Ledger intercompany setup forms.

Underlying Base Objects

The view text references three sources:

• GL_IEA_AUTOGEN_MAP (aliased MAP) — the primary base table holding the sender/receiver chart of accounts IDs, the three rule-usage flags, the standard WHO audit columns, the ATTRIBUTE1–15 descriptive flexfield columns, and the CONTEXT column. The view selects MAP.ROWID as ROW_ID to provide a unique row identifier.
• FND_ID_FLEX_STRUCTURES_VL (aliased FD1) — joined as the sender chart of accounts, restricted by APPLICATION_ID = 101 (Oracle General Ledger), ID_FLEX_CODE = 'GL#', and ID_FLEX_NUM = MAP.SENDER_CHART_OF_ACCT_ID.
• FND_ID_FLEX_STRUCTURES_VL (aliased FD2) — joined as the receiver chart of accounts, using the same application and flexfield code restrictions with ID_FLEX_NUM = MAP.RECEIVER_CHART_OF_ACCT_ID.

Both joins to FND_ID_FLEX_STRUCTURES_VL supply the ID_FLEX_STRUCTURE_NAME, which is the chart of accounts name (the accounting flexfield structure name). This is the direct source of the value returned in the SENDER_CHART_OF_ACCT_NAME and RECEIVER_CHART_OF_ACCT_NAME columns, and it is the reason a search on "id_flex_structure_name" surfaces this view.

Key Columns

• ROW_ID — the ROWID of the underlying GL_IEA_AUTOGEN_MAP row, useful for uniquely identifying a mapping record.
• SENDER_CHART_OF_ACCT_ID / SENDER_CHART_OF_ACCT_NAME — the accounting flexfield structure number and resolved name for the sending chart of accounts.
• RECEIVER_CHART_OF_ACCT_ID / RECEIVER_CHART_OF_ACCT_NAME — the corresponding identifier and name for the receiving chart of accounts.
• USE_SENDER_CLEAR_RULES_FLAG — indicates whether the sender's clearing rules are applied when generating balancing entries.
• USE_RECEIVER_CLEAR_RULES_FLAG — indicates whether the receiver's clearing rules are applied.
• USE_RECEIVER_DIST_RULES_FLAG — indicates whether the receiver's distribution rules are applied.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns inherited from the base table.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — descriptive flexfield segments associated with the mapping record.

Common Use Cases and Queries

Typical uses include auditing intercompany balancing configuration across ledgers, validating that every sender chart of accounts has a matching receiver mapping, and extracting rule-flag settings for reconciliation with legacy intercompany systems.

List all chart of accounts mappings and their rule usage:

• SELECT sender_chart_of_acct_name, receiver_chart_of_acct_name, use_sender_clear_rules_flag, use_receiver_clear_rules_flag, use_receiver_dist_rules_flag FROM gl_iea_autogen_map_v ORDER BY sender_chart_of_acct_name;

Find mappings for a specific sender chart of accounts, which is the query pattern implied by a search on the flexfield structure name:

• SELECT sender_chart_of_acct_name, receiver_chart_of_acct_name FROM gl_iea_autogen_map_v WHERE sender_chart_of_acct_name = :structure_name;

Identify mappings where receiver distribution rules are not applied, to review balancing behavior:

• SELECT receiver_chart_of_acct_name, creation_date, last_update_date FROM gl_iea_autogen_map_v WHERE use_receiver_dist_rules_flag = 'N';