Search Results assoc_interest_ussgl_code

Overview

The view GL_USSGL_TRANSACTION_CODES_V is an APPS-owned database object in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the United States Standard General Ledger (USSGL) transaction code definitions maintained within the General Ledger module, and makes them available to the Purchasing (PO) product family. USSGL transaction codes are used primarily by federal and public-sector implementations to tag financial transactions with standardized Treasury account symbols required for government reporting. The view is classified under the PO - Purchasing product/module in the ETRM metadata and carries a "Retrofitted" description, indicating that it was reconstructed or re-pointed during upgrade activity rather than introduced as a native GL object.

Functionally, GL_USSGL_TRANSACTION_CODES_V presents a single source of truth for transaction code metadata — including the chart of accounts, active date range, descriptive attributes, and the associated interest and discount USSGL codes — so that purchasing transactions and downstream reporting can reference USSGL values consistently. Because it is a view rather than a table, it adds no storage of its own but instead applies a currency/active-segment filter against the underlying base table.

Underlying Base Objects

As documented in the ETRM metadata, the view is defined over a single referenced base object:

• GL_USSGL_TRANSACTION_CODES (accessed through a SYNONYM in the APPS schema)

The view text is a direct projection of the base table's columns, with one critical filtering predicate applied:

WHERE SYSDATE BETWEEN NVL(START_DATE_ACTIVE, SYSDATE) AND NVL(END_DATE_ACTIVE, SYSDATE)

This predicate ensures that only currently active transaction code definitions are returned. Rows whose START_DATE_ACTIVE is in the future, or whose END_DATE_ACTIVE has passed, are excluded. Null start or end dates are treated as open-ended, so a row with no active dates remains visible. The view therefore behaves as a "current effective" snapshot of USSGL transaction codes, which is the appropriate semantic for transactional and integration scenarios.

Key Columns

The view exposes the complete column set of the base table. The most significant columns are:

• CHART_OF_ACCOUNTS_ID — identifies the chart of accounts to which the transaction code belongs; the primary partitioning key for USSGL definitions.
• USSGL_TRANSACTION_CODE — the standard USSGL transaction code value used to classify federal accounting events.
• ASSOC_INTEREST_USSGL_CODE — the associated interest USSGL code, matched by the search term assoc_interest_ussgl_code. This links an interest-bearing transaction to its corresponding standard general ledger code.
• ASSOC_DISCOUNT_USSGL_CODE — the associated discount USSGL code, the counterpart to the interest code for discount-related transactions.
• START_DATE_ACTIVE / END_DATE_ACTIVE — define the effective window during which the transaction code is valid; these drive the view's active-record filter.
• DESCRIPTION — human-readable description of the transaction code.
• ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — the standard Oracle flexfield descriptive columns, enabling customer-specific extensions without schema changes.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically used in federal financial reporting, purchasing integration, and validation logic where only active USSGL codes should be considered. A representative query retrieving interest and discount associations for a given chart of accounts is:

SELECT ussgl_transaction_code, assoc_interest_ussgl_code, assoc_discount_ussgl_code
FROM apps.gl_ussgl_transaction_codes_v
WHERE chart_of_accounts_id = :p_coa_id;

To locate the interest code associated with a specific transaction code:

SELECT assoc_interest_ussgl_code
FROM apps.gl_ussgl_transaction_codes_v
WHERE ussgl_transaction_code = :p_code
AND chart_of_accounts_id = :p_coa_id;

Because the view filters to active records, it is well suited for LOV (list of values) definitions, concurrent program parameters, and integration extracts that must not surface expired USSGL codes. For historical analysis, querying the base table GL_USSGL_TRANSACTION_CODES directly is required, since the view intentionally suppresses inactive definitions.