Search Results ussgl_transaction_code




Overview
Explore in AI Chat

Overview

GL_TRANSACTION_CODES_ACTIVE_V is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "10SC ONLY," indicating that the object is intended exclusively for the 10SC (Treasury Financial Manual / USSGL) federal accounting configuration and is not a general-purpose deliverable for commercial installations. The view provides a filtered, read-only listing of active United States Standard General Ledger (USSGL) transaction codes defined in the ledger, exposing only those codes whose activation window encompasses the current system date.

In an EBS reporting and integration context, the view serves as the lookup source for valid transaction codes at the time a query is executed. Rather than returning the entire transaction code table, it applies a date-range predicate so that downstream reports, concurrent programs, and interfaces display only currently effective codes. Analysts searching for "ussgl_transaction_code" typically encounter this view when building inquiries or extracts that must respect start and end dates of code validity.

Underlying Base Objects

The view is defined over a single documented base object: GL_USSGL_TRANSACTION_CODES, referenced through a synonym in the APPS schema. The view text performs a SELECT over this table with the alias TC, projecting three columns and applying the following WHERE clause:

This predicate treats a null start date as immediately active and a null end date as open-ended, so codes lacking date restrictions are always returned. Because the view is a simple projection and filter, it inherits the base table's security and any row-level restrictions applicable to GL_USSGL_TRANSACTION_CODES. No joins, aggregations, or DISTINCT operations are present, so the view returns one row per qualifying transaction code record.

Key Columns

The view exposes three documented columns:

  • USSGL_TRANSACTION_CODE — The transaction code itself, sourced directly from TC.USSGL_TRANSACTION_CODE. This is the principal identifier used in accounting entries, USSGL reporting, and crosswalks to the Standard General Ledger.
  • CHART_OF_ACCOUNTS_ID — The chart of accounts identifier, sourced from TC.CHART_OF_ACCOUNTS_ID, scoping each transaction code to a specific chart of accounts. This supports multi-chart environments where code definitions differ across ledgers.
  • DESCRIPTION — The descriptive text for the transaction code, sourced from TC.DESCRIPTION, providing the human-readable name or explanation of the code's intended use.

Notably, the view does not expose START_DATE_ACTIVE or END_DATE_ACTIVE even though those columns drive the filtering logic; consumers cannot see the underlying validity dates through this view alone.

Common Use Cases and Queries

Typical uses include validating transaction codes during data entry or conversion, driving value sets and list of values (LOVs) for federal accounting flexfields, and supplying pick lists for USSGL reporting extracts. A representative query retrieving all active codes for a given chart of accounts is:

  • SELECT ussgl_transaction_code, description FROM apps.gl_transaction_codes_active_v WHERE chart_of_accounts_id = :p_coa_id ORDER BY ussgl_transaction_code;

To confirm only currently effective codes are returned for a specific code, a caller might issue:

  • SELECT ussgl_transaction_code, chart_of_accounts_id, description FROM apps.gl_transaction_codes_active_v WHERE ussgl_transaction_code = :p_code;

Because the view filters on SYSDATE, query results change over time without any data modification, making it suitable for "as-of-today" reporting. For historical or audit reporting that must reflect codes active at a past date, the base table GL_USSGL_TRANSACTION_CODES should be queried directly with explicit date predicates, since the view cannot reproduce prior activation states. Consumers should also note the "10SC ONLY" designation: this view is documented as applicable solely to that federal configuration and should not be assumed present or populated in non-10SC environments.