Search Results ap_sob_info_v




Overview
Explore in AI Chat

Overview

AP_SOB_INFO_V is a Payables (AP) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose the set of books — or, under the Multi-Org Access Control (MOAC) and Subledger Accounting architecture, the ledgers — that the Payables application is configured to post to and report against. The view consolidates the primary accounting book defined in the Payables system options with any enabled reporting and secondary ledgers, presenting a uniform result set that downstream Payables reports, concurrent programs, and integration interfaces can query without embedding multi-ledger logic.

The view text reveals that it unions three distinct sources: the primary set of books, reporting (MRC) ledgers linked through the subledger relationship, and secondary ledgers linked through the Subledger Accounting relationships. Each row is tagged with a SOB_TYPE of 'PRIMARY', 'REPORTING', or 'SECONDARY', and a constant APPLICATION_ID of 200, which is the Oracle application identifier for Payables. This constant allows consuming programs to identify the owning application consistently.

Underlying Base Objects

The ETRM metadata documents the following referenced objects, all resolved through APPS synonyms or views:

  • AP_SYSTEM_PARAMETERS — supplies the Payables primary set of books, base currency, and organization context.
  • FINANCIALS_SYSTEM_PARAMETERS — provides the financials-level system parameters, including the purchase encumbrance flag used for the primary ledger row.
  • GL_SETS_OF_BOOKS — the General Ledger definition of the accounting book, supplying the name, ledger identifier, and cash-basis flag.
  • GL_ALC_LEDGER_RSHIPS_V — the Accounting Ledger Configuration relationship view used to derive enabled subledger reporting ledgers.
  • GL_SECONDARY_LEDGER_RSHIPS_V — the secondary ledger relationship view used to derive enabled subledger secondary ledgers.

Joins are driven by the Payables primary set of books in AP_SYSTEM_PARAMETERS, with relationship views filtered on RELATIONSHIP_TYPE_CODE = 'SUBLEDGER' and RELATIONSHIP_ENABLED_FLAG = 'Y' so that only active ledger relationships appear.

Key Columns

  • APPLICATION_ID — constant 200, identifying the Payables application.
  • NAME — the ledger or set of books name.
  • SET_OF_BOOKS_ID — the ledger identifier for the row (ledger ID in 12.x terms).
  • SOB_TYPE — classification of the row as PRIMARY, REPORTING, or SECONDARY.
  • ACCOUNTING_METHOD — returns CASH or ACCRUAL, derived from the SLA cash-basis flag for the primary and reporting rows, and from the SLA accounting method code for secondary ledgers.
  • BASE_CURRENCY_CODE — the Payables base (functional) currency from the system parameters.
  • ENCUMBRANCE_FLAG — indicates whether encumbrance accounting is enabled; populated for the primary ledger from the financials system parameters and defaulted to 'N' for reporting and secondary rows.

Common Use Cases and Queries

This view is typically queried to enumerate the ledgers available to Payables, to determine the accounting method and currency for reporting, or to drive multi-ledger reporting programs. A representative query follows:

SELECT sob_type,
       name,
       set_of_books_id,
       accounting_method,
       base_currency_code,
       encumbrance_flag
FROM   apps.ap_sob_info_v
ORDER  BY DECODE(sob_type,'PRIMARY',1,'REPORTING',2,'SECONDARY',3,4);

Filtering to the primary ledger is accomplished by WHERE sob_type = 'PRIMARY', which is useful when a report must reconcile to the operative set of books. Because the view normalizes ledger type, currency, accounting method, and encumbrance status into a single row-per-ledger structure, it eliminates the repeated decoding logic that would otherwise be required in custom Payables reports and interfaces.