Results for “from_le_id”

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

Overview

FUN_INTER_ACCOUNTS_V is a documented Oracle E-Business Suite view owned by the APPS schema, classified under the FND — Application Object Library product. Its status is VALID in both release 12.1.1 and 12.2.2, and its metadata is recorded in the ETRM repository for 12.2.2. The view consolidates intercompany (inter-ledger) account configuration data by exposing the union of two underlying intercompany accounting sources: FUN_INTER_ACCOUNTS and FUN_INTER_ACCOUNTS_ADDL. Rather than storing data itself, it presents a single, standardized projection over the intercompany accounts configuration so that reporting tools, concurrent programs, and integration interfaces can query intercompany account assignments without having to know which of the two base tables actually holds a given row. The name reflects the "FUN" application short name for Financials Common Modules, and the view is functionally aligned with the General Ledger intercompany and intracompany balancing configuration used during accounting and reconciliation processing.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both exposed to the view as SYNONYMs:

• FUN_INTER_ACCOUNTS — the primary intercompany accounts configuration table, holding account assignments for intercompany and intracompany balancing between ledgers.
• FUN_INTER_ACCOUNTS_ADDL — the additional intercompany accounts table, containing supplementary account configuration rows.

The view text is a straight UNION of identically projected column lists drawn from each base object: FROM_LE_ID, LEDGER_ID, TO_LE_ID, CCID, TYPE, TRANS_BSV, and TP_BSV. Because it is a UNION rather than a UNION ALL, duplicate rows appearing in both base tables are collapsed to a single row in the view. The APPS synonyms resolve to the corresponding FUN application tables, so all reads flow through the Financials Common Modules data model and inherit its security and multi-org behavior.

Key Columns

The view exposes seven columns, each significant to intercompany and intracompany balancing:

• FROM_LE_ID — the identifier of the source legal entity or ledger from which the accounting entry originates. This is the column most commonly used to filter the view, which explains why "from_le_id" is a frequent search term for this object.
• LEDGER_ID — the ledger identifier associated with the intercompany account assignment.
• TO_LE_ID — the identifier of the destination legal entity or ledger receiving the balancing entry.
• CCID — the code combination identifier of the intercompany balancing account, referencing the chart of accounts combination.
• TYPE — the classification of the intercompany account assignment (for example, distinguishing balancing account purposes).
• TRANS_BSV — the balancing segment value applied to the transaction side of the intercompany entry.
• TP_BSV — the balancing segment value applied to the trading partner side of the intercompany entry.

Common Use Cases and Queries

Typical scenarios include verifying that intercompany balancing accounts are configured for every source/destination ledger pair, auditing account assignments after a ledger or legal entity setup change, and feeding downstream reports or conversion programs with a single consolidated source of intercompany accounts. Because both base tables are unioned, a query returning rows for a given FROM_LE_ID automatically includes configuration from both FUN_INTER_ACCOUNTS and FUN_INTER_ACCOUNTS_ADDL.

Query all intercompany account assignments for a specific source ledger:

SELECT from_le_id, ledger_id, to_le_id, ccid, type, trans_bsv, tp_bsv
FROM   apps.fun_inter_accounts_v
WHERE  from_le_id = :p_from_le_id;

Query a specific source/destination ledger pair:

SELECT from_le_id, to_le_id, ccid
FROM   apps.fun_inter_accounts_v
WHERE  from_le_id = :p_from_le_id
AND    to_le_id   = :p_to_le_id;

Join to the chart of accounts combinations to return the concatenated account:

SELECT v.from_le_id, v.to_le_id, gcc.concatenated_segments
FROM   apps.fun_inter_accounts_v v, apps.gl_code_combinations_kfv gcc
WHERE  v.ccid = gcc.code_combination_id
AND    v.from_le_id = :p_from_le_id;

These patterns make FUN_INTER_ACCOUNTS_V the practical access point for interrogating intercompany account configuration in both 12.1.1 and 12.2.2.