Search Results target_currency_code

Overview

GL_ALC_LEDGER_RSHIPS_V is a General Ledger (GL) view owned by the APPS schema and defined over the Automatic Ledger Configuration (ALC) ledger relationship model. It exposes the set of accounting ledger relationships that Oracle EBS uses to drive secondary, subledger-level, and journal-level conversion and propagation of accounting entries. The view filters the underlying relationship table to only those target ledgers whose ledger category is 'ALC' and whose relationship type is either 'JOURNAL' or 'SUBLEDGER', and further restricts results to ledgers that are not explicitly marked incomplete (NVL(COMPLETE_FLAG,'Y') = 'Y'). The result is a focused, query-friendly list of the source-to-target ledger mappings that are relevant to ALC processing and reporting.

In both 12.1.1 and 12.2.2, the view is commonly consumed by reporting, reconciliation, and integration logic that needs to resolve which secondary ledger corresponds to a given primary or source ledger. Because it presents relationship metadata alongside the target ledger's descriptive attributes (name, short name, currency, primary ledger, application, org), it eliminates the need for callers to join GL_LEDGER_RELATIONSHIPS and GL_LEDGERS themselves.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in APPS:

• GL_LEDGER_RELATIONSHIPS (aliased REL) — supplies the source ledger, target ledger, relationship type, relationship enabled flag, primary ledger, and default conversion rate type.
• GL_LEDGERS (aliased LGR) — supplies the target ledger's name, short name, currency code, completion flag, application, and org context.

The join condition is LGR.LEDGER_ID = REL.TARGET_LEDGER_ID. Only rows where the target ledger's category code equals 'ALC' and the relationship type is 'JOURNAL' or 'SUBLEDGER' qualify. Records for incomplete ledgers (COMPLETE_FLAG other than 'Y' or NULL) are excluded through the NVL expression. The view projects the target ledger identifier as LEDGER_ID (renamed from TARGET_LEDGER_ID) and the target name as NAME (renamed from TARGET_LEDGER_NAME), so consumers see simplified column names.

Key Columns

• SOURCE_LEDGER_ID — the originating ledger in the relationship.
• LEDGER_ID — the target ALC ledger identifier (aliased from TARGET_LEDGER_ID).
• LEDGER_NAME / LEDGER_SHORT_NAME — descriptive identifiers for the target ledger; note the underlying columns are TARGET_LEDGER_NAME / TARGET_LEDGER_SHORT_NAME.
• CURRENCY_CODE — the target ledger's functional currency.
• RELATIONSHIP_TYPE_CODE — 'JOURNAL' or 'SUBLEDGER'; distinguishes journal-level from subledger-level relationships.
• RELATIONSHIP_ENABLED_FLAG — the enablement status of the relationship. This is the column most frequently searched in this context; a value of 'Y' indicates the relationship is active for ALC processing, while 'N' indicates it is defined but disabled. Callers typically filter on this flag to avoid consuming inactive mappings.
• PRIMARY_LEDGER_ID — the primary ledger associated with the relationship.
• APPLICATION_ID / ORG_ID — application and operating unit context.
• ALC_DEFAULT_CONV_RATE_TYPE — the default conversion rate type applied when converting balances or entries between source and target ledgers.

Common Use Cases and Queries

Typical scenarios include identifying the enabled secondary ledger for a source ledger, validating ALC configuration before period close, and supplying ledger mapping metadata to conversion or reporting integrations.

• List all enabled relationships: SELECT source_ledger_id, ledger_id, ledger_name, relationship_type_code FROM gl_alc_ledger_rshps_v WHERE relationship_enabled_flag = 'Y';
• Find the target ledger for a given source: SELECT ledger_id, ledger_name, currency_code FROM gl_alc_ledger_rshps_v WHERE source_ledger_id = :source_ledger_id AND relationship_enabled_flag = 'Y';
• Audit disabled relationships before re-enabling: SELECT source_ledger_id, ledger_id, relationship_type_code FROM gl_alc_ledger_rshps_v WHERE relationship_enabled_flag = 'N';
• Inspect subledger-only mappings: SELECT * FROM gl_alc_ledger_rshps_v WHERE relationship_type_code = 'SUBLEDGER' AND relationship_enabled_flag = 'Y';

Because the view already restricts results to ALC-category ledgers and complete ledger definitions, queries remain concise and avoid redundant joins to GL_LEDGERS.