Results for “trx_currency_code”

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

Overview

OKL_TRX_SUBSIDY_POOLS is a transaction-level table within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. The entity stores subsidy pool transaction information associated with lease contracts, lease quotes, lease applications, and lease opportunities. In leasing operations, manufacturers and vendors frequently provide subsidies or incentive credits that reduce the effective cost of financed equipment. This table records each movement of subsidy value against a defined subsidy pool, allowing the application to track pool balances, vendor contributions, and the currency conversions applied when a transaction currency differs from the pool currency.

The Data Vault classification derived heuristically from the foreign key structure identifies this object as a link table. This is consistent with its design: it associates a subsidy pool (OKL_SUBSIDY_POOLS_B), a source lease transaction, and a supplier (AP_SUPPLIERS) through a set of transactional relationships rather than storing a single descriptive business entity. Modelers implementing a Data Vault or dimensional warehouse should treat it as a transactional link between the pool hub and the source document.

Key Information Stored

The table contains 38 documented columns. The surrogate primary key is ID, enforced by the OKL_TRX_SUBSIDY_POOLS_PK constraint and mirrored by the unique index OKL_TRX_SUBSIDY_POOLS_U1. Since ID is a system-generated surrogate, it is not a business key; the business identity of a row is instead derived from the combination of the source object, transaction type, and subsidy pool.

• SUBSIDY_POOL_ID — foreign key to OKL_SUBSIDY_POOLS_B, identifying the pool against which the transaction is recorded.
• SUBSIDY_ID — reference to the specific subsidy definition driving the transaction.
• VENDOR_ID — foreign key to AP_SUPPLIERS, identifying the vendor that funds or sponsors the subsidy.
• TRX_TYPE_CODE and TRX_REASON_CODE — classify the nature and cause of the transaction, such as accrual, consumption, or adjustment.
• SOURCE_TYPE_CODE and SOURCE_OBJECT_ID — denote the originating document type (contract, quote, application, opportunity) and its identifier.
• TRX_DATE and SOURCE_TRX_DATE — the effective transaction date and the date of the originating source transaction.
• TRX_AMOUNT and TRX_CURRENCY_CODE — the transaction amount in its own currency.
• SUBSIDY_POOL_AMOUNT and SUBSIDY_POOL_CURRENCY_CODE — the equivalent amount expressed in the pool currency.
• CONVERSION_RATE — the rate applied between transaction and pool currencies.
• DNZ_ASSET_NUMBER — the asset identifier associated with the subsidized transaction.
• OBJECT_VERSION_NUMBER — used for optimistic locking during concurrent updates.

Fifteen ATTRIBUTE columns and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) complete the structure.

Common Use Cases and Queries

Typical usage centers on reconciling subsidy pool balances, reporting vendor-funded subsidies, and auditing currency conversion impacts. A basic query joining the pool header might read:

• SELECT t.ID, t.TRX_TYPE_CODE, t.TRX_AMOUNT, t.SUBSIDY_POOL_AMOUNT, t.CONVERSION_RATE FROM OKL_TRX_SUBSIDY_POOLS t WHERE t.SUBSIDY_POOL_ID = :pool_id ORDER BY t.TRX_DATE;
• Aggregating consumption by pool: SELECT SUBSIDY_POOL_ID, SUM(SUBSIDY_POOL_AMOUNT) FROM OKL_TRX_SUBSIDY_POOLS GROUP BY SUBSIDY_POOL_ID;
• Vendor exposure reporting: joining VENDOR_ID to AP_SUPPLIERS to summarize subsidies funded by supplier.

These patterns support month-end close, subsidy pool depletion analysis, and integration extracts feeding downstream financial systems.

Related Objects

The most significant related objects are OKL_SUBSIDY_POOLS_B, joined on SUBSIDY_POOL_ID, which holds the pool definition; AP_SUPPLIERS, joined on VENDOR_ID, which identifies the funding vendor; and the lease document tables (contracts, quotes, applications, opportunities) reachable through SOURCE_OBJECT_ID and SOURCE_TYPE_CODE. The subsidy definition referenced by SUBSIDY_ID, the OKL_TRX_SUBSIDY_POOLS_PK and OKL_TRX_SUBSIDY_POOLS_U1 indexes, and the OKL module's public subsidy pool APIs complete the principal dependency set. Together these objects allow transaction-level subsidy data to be traced from vendor through pool to the originating lease transaction.