Search Results sob_id

Overview

The AP_SRS_ACCTG_CURR_V view is a reporting utility object owned by the APPS schema within the Oracle E-Business Suite Payables (AP) module. Its name indicates its function: it exposes the set of accounting currencies and their associated ledger (set of books) context that Payables reporting processes—particularly those supporting the Subledger Reporting System (SRS) and cross-ledger/MRC reporting—rely upon. The view does not store transaction data. Instead, it presents a consolidated, de-duplicated list of ledger-to-currency relationships so that reporting logic can resolve which reporting currency and ledger identifiers are valid for a given subledger application. It is classified as a VIEW and holds a VALID status in the ETRM metadata, confirming that it compiles against its base objects in both 12.1.1 and 12.2.2 environments. Because the structure spans both the multi-reporting-currency (MRC) relationship model and the general ledger set-of-books model, the view acts as a bridge object that normalizes naming differences between those two sources.

Underlying Base Objects

The view is defined as a UNION over two documented base objects:

• GL_ALC_LEDGER_RSHIPS_V — a Ledger/Accounting Setup Manager view that exposes ledger relationships. The first branch of the UNION filters this source to rows where RELATIONSHIP_TYPE_CODE = 'SUBLEDGER', RELATIONSHIP_ENABLED_FLAG = 'Y', and APPLICATION_ID = 200 (the Payables application identifier). This restricts output to active subledger relationships relevant to Payables.
• GL_SETS_OF_BOOKS — the classic set-of-books view. The second UNION branch selects the currency code, ledger name, and set-of-books ID directly, assigning a constant reporting organization ID of -1.

The UNION combines both branches so that the view returns the union of relationship-derived ledgers and standalone sets of books. DISTINCT is applied to the first branch to suppress duplicate currency/ledger combinations. The reporting organization column is sourced from ORG_ID in the relationship branch, permitting multi-org aware reporting.

Key Columns

• CURR_CODE — the currency code (the searched term "curr_code"). In the relationship branch this is derived from the MRC.CURRENCY_CODE; in the set-of-books branch it is GSOB.CURRENCY_CODE.
• SOB_NAME — the ledger/set-of-books name, exposed via MRC.LEDGER_NAME or GSOB.NAME.
• SOB_ID — the ledger identifier (MRC.LEDGER_ID or GSOB.SET_OF_BOOKS_ID).
• P_SOB_ID — the parent or source ledger identifier (MRC.SOURCE_LEDGER_ID, or the same value as SOB_ID for the set-of-books branch).
• REPORTING_ORG_ID — the operating unit/org context for reporting; -1 is used for the set-of-books branch, denoting no specific org restriction.

Common Use Cases and Queries

Typical scenarios include resolving valid reporting currencies for a Payables report, driving dynamic LOVs for currency/ledger selection, and validating MRC relationship configuration. A representative query to list all enabled subledger accounting currencies is:

SELECT sob_name, sob_id, p_sob_id, curr_code, reporting_org_id FROM apps.ap_srs_acctg_curr_v WHERE curr_code = :curr_code ORDER BY sob_name;

To enumerate every currency/ledger combination exposed by the view: SELECT DISTINCT curr_code FROM apps.ap_srs_acctg_curr_v;. Because the object is a view, it should be queried with the APPS schema context or appropriate synonym and does not require maintenance. Reported values reflect live ledger and relationship configuration, so any changes to ledger setups propagate immediately.