Search Results gl_ussgl_transaction_codes

Overview

The view POR_USSGL_TC_LOV_V, owned by the APPS schema, is a reporting and user-interface support object within Oracle E-Business Suite. It belongs to the ICX product family, which covers Oracle iProcurement and related self-service procurement functionality. As documented in the ETRM metadata, the view exists specifically as the source on which the List of Values (LOV) for the United States Standard General Ledger (USSGL) Transaction Codes is based. In practice, this means that when a user in iProcurement or a related Oracle EBS form needs to select a USSGL Transaction Code, the underlying LOV query is satisfied by this view rather than by direct access to the USSGL transaction code table.

The view is recorded as VALID in the ETRM documentation, and the same definition is documented for both Oracle EBS 12.1.1 and 12.2.2. Its principal function is to filter and contextualize USSGL transaction codes so that only those relevant to the current set of books, and currently active, are surfaced to the end user.

Underlying Base Objects

The documented base objects referenced by this view are FINANCIALS_SYSTEM_PARAMETERS (a synonym), GL_SETS_OF_BOOKS (a view), and GL_USSGL_TRANSACTION_CODES (a synonym). The iProcurement LOV is therefore constructed from the intersection of general ledger setup and the USSGL transaction code catalog.

The documented view text joins GL_USSGL_TRANSACTION_CODES TC to GL_SETS_OF_BOOKS SB on CHART_OF_ACCOUNTS_ID, and joins SB.SET_OF_BOOKS_ID to FINANCIALS_SYSTEM_PARAMETERS FP. Date filtering is applied with SYSDATE BETWEEN NVL(TC.START_DATE_ACTIVE, SYSDATE-1) AND NVL(TC.END_DATE_ACTIVE, SYSDATE+1), ensuring only active codes are returned, with open-ended date ranges defaulted when the start or end dates are null.

Key Columns

• USSGL_TRANSACTION_CODE — The USSGL transaction code value presented to the user in the LOV and stored on the transaction.
• CHART_OF_ACCOUNTS_ID — The chart of accounts to which the transaction code belongs; used to restrict codes to the relevant accounting structure.
• DESCRIPTION — The descriptive text for the transaction code, displayed alongside the code in the List of Values to aid selection.

Because the view is a restricted projection, it exposes only these three columns even though the underlying GL_USSGL_TRANSACTION_CODES table carries additional attributes such as active dates and other control columns.

Common Use Cases and Queries

This view is typically consumed indirectly through the iProcurement LOV, but it can also be queried directly for validation, reporting, or troubleshooting purposes. A representative query retrieves the active transaction codes and descriptions available to the current operating unit's set of books:

• SELECT ussgl_transaction_code, description FROM apps.por_ussgl_tc_lov_v ORDER BY ussgl_transaction_code;
• SELECT ussgl_transaction_code, chart_of_accounts_id, description FROM apps.por_ussgl_tc_lov_v WHERE chart_of_accounts_id = :p_coa_id;
• SELECT COUNT(*) FROM apps.por_ussgl_tc_lov_v WHERE ussgl_transaction_code = :p_code; — used to validate that a code is active and valid before it is assigned to a requisition or purchase order line.

Typical scenarios include confirming that a USSGL transaction code appearing in iProcurement is still within its active date range, diagnosing a missing code in the LOV, and building ad hoc reports that align iProcurement purchasing activity with the general ledger USSGL transaction code catalog. Because the view depends on FINANCIALS_SYSTEM_PARAMETERS, results are inherently scoped by the set of books configured for the financials system parameters, which reinforces its role as a context-aware LOV source.