Results for “okl_pool_transactions_v”

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

Overview

OKL_POOL_TRANSACTIONS_V is a reporting and integration view owned by the APPS schema in Oracle Lease and Finance Management (OKL). It is classified as an entity view for the OKL_POOL_TRANSACTIONS base entity, meaning it presents a flattened, denormalized projection of pool transaction records that is suitable for concurrent program reporting, Oracle XML Publisher (BI Publisher) data templates, and outbound interface extraction. In Oracle E-Business Suite 12.1.1 and 12.2.2, the view is registered with status VALID and is exposed as APPS.OKL_POOL_TRANSACTIONS_V. Pool transactions represent events that affect a lease pool — for example, transactions that add contracts to a pool, remove them, or adjust the attributes of a pooled asset. Because the view carries the standard EBS WHO columns and the concurrent request columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID), it is well suited to audit trails and to traceability reports that tie each pool transaction back to the program that created it.

Underlying Base Objects

The view text is a simple single-table projection:

• SELECT ... FROM OKL_POOL_TRANSACTIONS POX

The referenced base object documented in the ETRM metadata is OKL_POOL_TRANSACTIONS, exposed to APPS through a SYNONYM. No joins, unions, aggregations, or filters are applied inside the view definition. As a consequence, the view is a one-to-one pass-through of the base table's rows: every pool transaction row in OKL_POOL_TRANSACTIONS appears once in OKL_POOL_TRANSACTIONS_V, and the ROWID-level relationship is preserved. This direct mapping means the view adds no performance overhead beyond ordinary SQL parsing, and it can be used interchangeably with the synonym for read-only access when the consuming tool prefers a "_V" entity view name (a common convention in the OKL data model). Because the view is defined over the synonym, the base table retains full control over indexes, partitions, and constraints, while the view supplies a stable, documented column interface for external consumers.

Key Columns

The view exposes the complete column list of OKL_POOL_TRANSACTIONS. The principal columns are described below.

• ID — Primary key of the pool transaction row.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OKL business object layer.
• POL_ID — Foreign key to the lease pool (OKL_POOLS) affected by the transaction.
• TRANSACTION_NUMBER — Human-readable transaction identifier.
• TRANSACTION_DATE and DATE_EFFECTIVE — The date the transaction was created and the accounting-effective date.
• TRANSACTION_TYPE and TRANSACTION_SUB_TYPE — Classify the nature of the pool event; the sub-type is the user's search term and typically distinguishes variants within a major transaction type.
• CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_RATE — Currency and conversion attributes applied to the transaction.
• TRANSACTION_REASON — Free-text or lookup-based explanation for the transaction.
• TRANSACTION_STATUS — Workflow or processing state of the transaction.
• LEGAL_ENTITY_ID — Owning legal entity for multi-org and subledger accounting purposes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1..ATTRIBUTE15 — Descriptive flexfield (DFF) columns available for customer-specific extension.
• WHO columns and concurrent request columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include pool transaction registers, audit reports that trace sub-type activity, and extracts that feed downstream treasury or accounting systems. The following examples illustrate common patterns.

List all transactions for a pool by sub-type:

• SELECT transaction_number, transaction_date, transaction_type, transaction_sub_type, transaction_status FROM okl_pool_transactions_v WHERE pol_id = :p_pol_id ORDER BY transaction_date DESC;

Report sub-type activity over a date range:

• SELECT transaction_sub_type, COUNT(*) FROM okl_pool_transactions_v WHERE transaction_date BETWEEN :p_start AND :p_end GROUP BY transaction_sub_type;

Trace transactions back to the concurrent program that created them:

• SELECT t.transaction_number, t.transaction_sub_type, t.request_id, t.program_id, t.creation_date FROM okl_pool_transactions_v t WHERE t.request_id IS NOT NULL;