Results for “subsidy_currency_code”

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

Overview

The view OKL_QUOTE_SUBPOOL_USAGE_V is an Oracle E-Business Suite database object owned by the APPS schema and registered as VALID in the ETRM repository for Oracle EBS 12.1.1 and 12.2.2. It belongs to the OKL - Leasing and Finance Management product family and exposes the contents of the OKL_QUOTE_SUBPOOL_USAGE entity. The view is a thin, row-preserving projection: rather than joining, aggregating, or filtering the base data, it re-presents the underlying table's columns, prefixed by a synthetic ROW_ID derived from ROWID. Its purpose is to provide a stable, read-oriented interface for reporting, extraction, and integration consumers who need quote-level sub-pool and subsidy usage detail without querying the base table directly.

In leasing and finance management, sub-pools and subsidies are funding constructs associated with vendor programs and quotes. The view captures the consumption of those pools against individual quote transactions, making it relevant to funding reconciliation, program utilization analysis, and downstream financial reporting.

Underlying Base Objects

The view is defined over a single base object, OKL_QUOTE_SUBPOOL_USAGE, which is referenced internally as a synonym within the APPS schema. The SELECT statement lists the base columns and adds ROWID ROW_ID as the leading expression. Because the definition is a direct column projection, each row in the view corresponds one-to-one with a row in the base table; there are no joins to quote headers, contracts, or vendor tables, and no aggregation or filtering predicates are applied. This design implies that any contextual enrichment—such as quote number, contract identifier, or vendor name—must be obtained by joining the view back to the relevant OKL quote and vendor entities on the exposed identifier columns.

Key Columns

• ROW_ID — Synthetic row identifier derived from the base table ROWID; useful for deduplication and row-level addressing.
• ID — Primary identifier of the sub-pool usage record.
• OBJECT_VERSION_NUMBER — Optimistic locking value used by the OKL framework for concurrent update control.
• SUBPOOL_TRX_ID — Reference to the sub-pool transaction against which usage is recorded.
• SOURCE_TYPE_CODE, SOURCE_OBJECT_ID — Polymorphic reference identifying the originating business object and its type.
• ASSET_NUMBER, ASSET_START_DATE — The asset associated with the usage and its effective start date.
• SUBSIDY_POOL_ID, SUBSIDY_POOL_AMOUNT, SUBSIDY_POOL_CURRENCY_CODE — Identifier, amount consumed, and currency of the subsidy pool.
• SUBSIDY_ID, SUBSIDY_AMOUNT, SUBSIDY_CURRENCY_CODE — Identifier, amount, and currency of the specific subsidy applied.
• VENDOR_ID — Vendor associated with the subsidy or pool program.
• CONVERSION_RATE — Rate applied between pool and subsidy currencies.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments for customer-defined extension data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO audit columns.

Common Use Cases and Queries

The view supports investigation of how subsidy pools are consumed at the quote level. A frequent scenario is tracing usage for a specific pool when the identifier is known, for example:

• Retrieving all usage rows linked to a subsidy pool: SELECT id, subpool_trx_id, asset_number, subsidy_pool_amount, subsidy_amount, vendor_id FROM apps.okl_quote_subpool_usage_v WHERE subsidy_pool_id = :p_pool_id;
• Reconciling subsidy amounts against pool amounts by currency, grouping on SUBSIDY_POOL_CURRENCY_CODE and SUBSIDY_CURRENCY_CODE.
• Auditing recently modified records using LAST_UPDATE_DATE for incremental extraction into a data warehouse.
• Joining the view to vendor and quote entities through VENDOR_ID and SOURCE_OBJECT_ID to produce program utilization reports.

Because the view performs no filtering, consumers should apply their own predicates—particularly on SUBSIDY_POOL_ID, VENDOR_ID, or date ranges—to constrain result sets in production reporting.