Results for “trx_reason_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_TRX_SUBSIDY_POOLS_V is an APPS-owned database view within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, belonging to the OKL - Leasing and Finance Management product. The view exposes subsidy pool transaction records maintained in the Oracle Leasing and Finance Management module, which is used to administer lease contracts, financing agreements, and the associated subsidy and residual value arrangements. As documented, the view holds subsidy pool transactions, presenting a denormalized, read-oriented projection of the underlying transaction table for reporting, inquiry, and integration purposes.

The view performs no aggregation, filtering, or joining; it is a direct projection over its single base table, exposing every row. This design makes it a safe read-only interface for external extracts, business intelligence queries, and downstream interfaces that require access to subsidy pool transaction activity without touching the base table directly. Because it is a simple view, no materialized data or redundant storage is introduced.

Underlying Base Objects

According to the ETRM metadata, the view is defined over the base object OKL_TRX_SUBSIDY_POOLS, which is exposed in the APPS schema as a synonym. The view text confirms the relationship: every column in the view is sourced directly from OKL_TRX_SUBSIDY_POOLS, aliased as SIXB, with the current-row identifier exposed as ROW_ID via SIXB.ROWID. Consequently, the view and the table maintain a strict one-to-one correspondence: one view row for every base table row, with column names preserved identically between the table and the view. Any DML against the view would be reflected in the base table, though in practice the view is intended for query access only.

Key Columns

The columns relevant to the trx_type_code search criteria, and the broader structure of the view, include:

• TRX_TYPE_CODE — Classifies the subsidy pool transaction type (for example, accrual, payment, adjustment, or transfer activity against a pool). This is the principal discriminator used when filtering subsidy pool transactions by nature.
• SOURCE_TYPE_CODE and SOURCE_OBJECT_ID — Identify the originating object that generated the transaction, supporting traceability back to the source document.
• ID / OBJECT_VERSION_NUMBER — Surrogate primary key and optimistic locking version for the transaction record.
• SUBSIDY_POOL_ID — Foreign reference to the subsidy pool against which the transaction was recorded.
• SUBSIDY_ID — Identifies the related subsidy definition.
• DNZ_ASSET_NUMBER / VENDOR_ID — Asset and vendor references associated with the transaction.
• TRX_DATE / SOURCE_TRX_DATE — Effective transaction date and the source document date.
• TRX_CURRENCY_CODE, TRX_AMOUNT, SUBSIDY_POOL_CURRENCY_CODE, SUBSIDY_POOL_AMOUNT, CONVERSION_RATE — Amount and currency information, including the transaction currency amount, the pool currency amount, and the conversion rate applied.
• TRX_REASON_CODE — Reason or justification associated with the transaction.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield columns for extensible transaction attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Audit columns.

Common Use Cases and Queries

The view is typically queried to analyze subsidy pool activity by transaction type, reconcile pool balances, and feed downstream reporting. A representative query filtered on the transaction type code follows:

• SELECT trx_type_code, trx_date, trx_amount, subsidy_pool_amount FROM okl_trx_subsidy_pools_v WHERE trx_type_code = :p_trx_type_code AND trx_date BETWEEN :p_from AND :p_to;
• SELECT subsidy_pool_id, trx_type_code, SUM(trx_amount) FROM okl_trx_subsidy_pools_v GROUP BY subsidy_pool_id, trx_type_code;
• SELECT id, source_type_code, source_object_id, vendor_id FROM okl_trx_subsidy_pools_v WHERE subsidy_id = :p_subsidy_id;

These patterns support subsidy accrual reconciliation, vendor-related subsidy analysis, and source-document drill-down directly from the view.