Search Results sla_accounting_method_code

Overview

GL_SECONDARY_LEDGER_RSHIPS_V is a General Ledger (GL) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The view exposes the set of enabled relationships between primary and secondary ledgers, together with the Subledger Accounting (SLA) attributes associated with each secondary ledger. Its name — "Secondary Ledger Relationships" — reflects its purpose: to enumerate every secondary ledger that is defined and linked to a primary ledger through the GL_LEDGER_RELATIONSHIPS table, while filtering out ledgers that are incomplete or relationships of type 'NONE'.

The view plays an important role in multi-ledger accounting configurations, where an organization maintains one or more secondary ledgers for statutory, management, budgetary, or IFRS reporting alongside a primary ledger. It is routinely referenced by reporting queries, data-integration extracts, and diagnostic scripts that need to resolve which secondary ledger corresponds to a given primary ledger and which SLA accounting method governs that secondary ledger. Because it exposes SLA_ACCOUNTING_METHOD_CODE and SLA_ACCOUNTING_METHOD_TYPE, the view is frequently the object returned when users search for the term "sla_accounting_method_code" in the context of General Ledger ledger setup.

Underlying Base Objects

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

• GL_LEDGERS (SYNONYM) — the GL ledger definition table, which stores ledger identity, chart of accounts, currency, period set, and SLA accounting method attributes.
• GL_LEDGER_RELATIONSHIPS (SYNONYM) — the table that records the primary-to-secondary relationships between ledgers, including mapping identifiers and relationship type codes.

The join is driven from GL_LEDGER_RELATIONSHIPS (aliased RS) to GL_LEDGERS (aliased LG). The WHERE clause restricts the result to rows where LG.LEDGER_CATEGORY_CODE = 'SECONDARY', where the ledger is complete (NVL(LG.COMPLETE_FLAG, 'Y') = 'Y'), where RS.TARGET_LEDGER_ID = LG.LEDGER_ID, where the target ledger category matches the ledger category, where RS.RELATIONSHIP_TYPE_CODE is not 'NONE', and where RS.APPLICATION_ID = 101 (the General Ledger application ID). Consequently, the view returns only the "receiving" secondary ledger side of each enabled relationship.

Key Columns

• PRIMARY_LEDGER_ID — identifies the primary ledger in the relationship (from GL_LEDGER_RELATIONSHIPS).
• LEDGER_ID — the secondary ledger identifier (GL_LEDGERS.LEDGER_ID).
• LEDGER_NAME / LEDGER_SHORT_NAME — the descriptive name and short name of the secondary ledger.
• CHART_OF_ACCOUNTS_ID, CURRENCY_CODE, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE — ledger configuration attributes of the secondary ledger.
• SL_COA_MAPPING_ID — the chart-of-accounts mapping used to translate primary ledger balances into the secondary ledger.
• SLA_ACCOUNTING_METHOD_CODE — the Subledger Accounting method code applied to the secondary ledger.
• SLA_ACCOUNTING_METHOD_TYPE — the SLA accounting method type for the secondary ledger.
• RELATIONSHIP_TYPE_CODE — the type of relationship between the ledgers (for example, balance or journal level).
• RELATIONSHIP_ENABLED_FLAG — indicates whether the relationship is currently enabled.

Common Use Cases and Queries

Typical uses include identifying the SLA accounting method for each secondary ledger, validating multi-ledger setups, and driving integration extracts that must know the source-to-target ledger mapping.

List all secondary ledgers and their SLA methods:

• SELECT primary_ledger_id, ledger_id, ledger_name, sl_coa_mapping_id, sla_accounting_method_code, sla_accounting_method_type FROM gl_secondary_ledger_rships_v;

Retrieve secondary ledgers for a specific primary ledger:

• SELECT ledger_id, ledger_name, sla_accounting_method_code FROM gl_secondary_ledger_rships_v WHERE primary_ledger_id = :p_primary_ledger_id;

Find the SLA method associated with an enabled relationship:

• SELECT ledger_name, sla_accounting_method_code FROM gl_secondary_ledger_rships_v WHERE relationship_enabled_flag = 'Y';

Because the view already filters to complete secondary ledgers and non-'NONE' relationships, these queries avoid additional filtering in most diagnostic and reporting scenarios.