Search Results set_of_books_type_code

Overview

APPS.PA_GL_SET_OF_BOOKS_V is a reporting view in Oracle E-Business Suite Projects (PA) that exposes the set of books (ledgers) available to a Projects implementation, distinguishing between the primary set of books and any reporting (secondary) sets of books associated through the Multiple Reporting Currencies (MRC) mechanism. The view is consumed by Projects forms, concurrent programs, and reporting logic that need to resolve the correct set of books context for a given operating unit without requiring the caller to query the General Ledger and Projects implementation objects directly.

The view is particularly significant because it derives its business meaning from the MRC_SOB_TYPE lookup type. The two branches of the UNION ALL correspond to the lookup codes P (Primary) and R (Reporting). This is the origin of the mrc_sob_type naming convention familiar to EBS developers working with multi-currency ledger configurations.

Underlying Base Objects

The view is defined over four documented objects:

• GL_SETS_OF_BOOKS (VIEW) — supplies the ledger name and functional currency. In the primary branch it is joined directly to PA_IMPLEMENTATIONS on SET_OF_BOOKS_ID; in the reporting branch it is joined via GL_ALC_LEDGER_RSHIPS_V.
• PA_IMPLEMENTATIONS (SYNONYM) — provides the implementation context, contributing SET_OF_BOOKS_ID and ORG_ID (operating unit). It anchors the view to a specific Projects implementation.
• GL_LOOKUPS (VIEW) — supplies the decoded meaning and lookup code for the MRC_SOB_TYPE lookup, filtered to codes P and R respectively in the two branches.
• GL_ALC_LEDGER_RSHIPS_V (VIEW) — the MRC ledger relationship view, used only in the second branch to identify reporting ledgers. It is constrained by RELATIONSHIP_ENABLED_FLAG = 'Y', APPLICATION_ID = 275 (the Projects application), and an ORG_ID test permitting either the global value -99 or the implementation's own ORG_ID.

Because three of the four referenced objects are themselves views, the effective execution path ultimately resolves to General Ledger and Projects base tables underneath.

Key Columns

• SET_OF_BOOKS_NAME — the ledger name from GL_SETS_OF_BOOKS.
• CURRENCY — the ledger functional currency; in the reporting branch it originates from GL_ALC_LEDGER_RSHIPS_V.
• SET_OF_BOOKS_TYPE — the decoded MRC_SOB_TYPE meaning, truncated to 30 bytes via SUBSTRB, typically "Primary" or "Reporting".
• SET_OF_BOOKS_TYPE_CODE — the raw lookup code, P or R.
• SET_OF_BOOKS_ID — the ledger identifier; taken from PA_IMPLEMENTATIONS in the primary branch and from GL_ALC_LEDGER_RSHIPS_V.LEDGER_ID in the reporting branch.
• ORG_ID — the operating unit from PA_IMPLEMENTATIONS, used to scope results by organization.

Common Use Cases and Queries

The view is commonly used to present a ledger selection list on Projects setup and transaction forms, and to resolve which reporting ledgers exist for a primary ledger prior to MRC conversion or reporting. A typical query lists all ledgers for an operating unit:

• SELECT set_of_books_name, currency, set_of_books_type, set_of_books_id FROM apps.pa_gl_set_of_books_v WHERE org_id = :p_org_id;
• SELECT set_of_books_id FROM apps.pa_gl_set_of_books_v WHERE set_of_books_type_code = 'P' AND org_id = :p_org_id;
• SELECT b.set_of_books_name FROM apps.pa_gl_set_of_books_v b WHERE b.set_of_books_type_code = 'R' AND b.org_id = :p_org_id;

Because the reporting branch filters on APPLICATION_ID = 275, only MRC relationships enabled for Projects are surfaced, ensuring that callers see a ledger set consistent with the Projects implementation rather than a general General Ledger listing.