Search Results sob_type




Overview
Explore in AI Chat

Overview

APPS.AP_SOB_INFO_V is a read-only Oracle EBS view published in the APPS schema that consolidates the ledgers (sets of books) relevant to the Oracle Payables application into a single, uniformly shaped result set. It exists to answer a recurring integration and reporting question: for a given Payables operating unit, which ledgers are visible, which of them is the primary ledger, how does each ledger account, and what is each ledger's encumbrance posture?

The view is defined as a three-branch UNION ALL, each branch tagged with a constant APPLICATION_ID of 200 (Payables) and a literal SOB_TYPE discriminator. The first branch returns the primary set of books, the second returns reporting (MRC) ledgers linked through the subledger accounting relationship, and the third returns secondary ledgers linked to the primary ledger. Because the accounting method column is derived differently in each branch, the view normalizes three different underlying flag conventions into a single Cash / Accrual vocabulary. This makes it suitable as a lookup source in concurrent programs, custom reports, and integration extracts where the caller needs an application-neutral ledger list without navigating GL ledger relationship views directly.

Underlying Base Objects

The documented base objects are AP_SYSTEM_PARAMETERS, FINANCIALS_SYSTEM_PARAMETERS, GL_SETS_OF_BOOKS, GL_ALC_LEDGER_RSHIPS_V, and GL_SECONDARY_LEDGER_RSHIPS_V. The first three are synonyms over their respective Payables and General Ledger tables; the latter two are General Ledger views.

  • AP_SYSTEM_PARAMETERS supplies the driving join key, SET_OF_BOOKS_ID, along with BASE_CURRENCY_CODE and ORG_ID. Every branch of the union anchors on this object.
  • FINANCIALS_SYSTEM_Parameters (synonym over the Payables system parameters table structure) supplies PURCH_ENCUMBRANCE_FLAG, the source of the ENCUMBRANCE_FLAG value.
  • GL_SETS_OF_BOOKS provides the ledger name and the SLA_LEDGER_CASH_BASIS_FLAG used to derive the accounting method, and is joined by SET_OF_BOOKS_ID.
  • GL_ALC_LEDGER_RSHIPS_V provides reporting ledger relationships where RELATIONSHIP_TYPE_CODE = 'SUBLEDGER', RELATIONSHIP_ENABLED_FLAG='Y', APPLICATION_ID = 200, and ORG_ID matches the system parameters row.
  • GL_SECONDARY_LEDGER_RSHIPS_V provides secondary ledger relationships on the same subledger, enabled-only criteria.

Key Columns

  • APPLICATION_ID — constant 200, identifying Oracle Payables as the owning application.
  • NAME — ledger (set of books) name.
  • SET_OF_BOOKS_ID — ledger identifier; for the primary branch this equals the Payables system parameter ledger.
  • SOB_TYPE — literal discriminator with values Primary, Reporting, or Secondary.
  • ACCOUNTING_METHOD — Cash or Accrual, decoded from SLA_LEDGER_CASH_BASIS_FLAG for primary and reporting ledgers, and from SLA_ACCOUNTING_METHOD_CODE for secondary ledgers.
  • BASE_CURRENCY_CODE — taken from AP_SYSTEM_PARAMETERS; it is the Payables base currency, not necessarily the ledger currency.
  • ENCUMBRANCE_FLAG — Y or N. Only the primary branch can yield Y, and only when the ledger matches the Payables system parameter ledger and PURCH_ENCUMBRANCE_FLAG is set. Both reporting and secondary branches hard-code N.

Common Use Cases and Queries

The view is typically used to enumerate ledgers for a Payables operating unit or to test whether purchasing encumbrance accounting is active. A representative query lists all ledgers and flags the primary:

  • SELECT sob_type, name, set_of_books_id, accounting_method, encumbrance_flag FROM ap_sob_info_v ORDER BY sob_type;
  • SELECT set_of_books_id FROM ap_sob_info_v WHERE sob_type = 'Primary' AND encumbrance_flag = 'Y';
  • SELECT name, base_currency_code FROM ap_sob_info_v WHERE accounting_method = 'Cash';

Because the reporting and secondary branches always return ENCUMBRANCE_FLAG = 'N', any query intended to determine whether encumbrance accounting applies must filter on SOB_TYPE = 'Primary'; otherwise the result set will include non-encumbered ledger rows that can mislead a join or a control total. The view is also frequently joined back to AP_SYSTEM_PARAMETERS or GL_SETS_OF_BOOKS on SET_OF_BOOKS_ID to enrich extracts with additional ledger attributes.