Results for “okl_quote_subpool_usage”

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

Overview

The OKL_QUOTE_SUBPOOL_USAGE table resides in the OKL schema, which is the foundation of the Oracle E-Business Suite Leasing and Finance Management (OKL) module. As its documented description states, the table "stores the maximum subsidy pool usage for an object." In practical terms, it captures the consumption of subsidy pools and individual subsidies against lease or financing quote lines so that the application can enforce pool ceilings and report on remaining capacity. This object is central to subsidy program administration, where vendors and internal programs fund portions of a transaction and the system must track how much of a defined pool each quoted asset consumes.

From a heuristic Data Vault modeling perspective, the mined metadata classifies this object as "standalone," meaning it carries no discovered foreign-key relationships to other documented tables within the extracted schema. This suggests it can reasonably be treated as a standalone satellite or reference record rather than a hub or link, though in a rigorous Data Vault design it would likely attach to a quote or subsidy-pool hub via its business keys. The absence of formal foreign-key metadata does not preclude logical relationships; it reflects only that referential constraints were not mined from the dictionary.

Key Information Stored

The table is physically documented in ETRM 12.2.2 with 36 columns. Its surrogate primary key is the single column ID, defined through constraint OKL_QUL_PK. Business-key candidates center on the combination of SUBPOOL_TRX_ID, SOURCE_TYPE_CODE, and SOURCE_OBJECT_ID, which together identify the transaction source from which a usage record originates.

• ID – surrogate primary key (OKL_QUL_PK) uniquely identifying each usage row.
• SUBPOOL_TRX_ID – identifier of the subsidy pool transaction that generated the usage record.
• SOURCE_TYPE_CODE and SOURCE_OBJECT_ID – the source entity type and its identifier, linking the record to the originating quote or object.
• ASSET_NUMBER and ASSET_START_DATE – the asset associated with the usage and the date its coverage begins.
• SUBSIDY_POOL_ID, SUBSIDY_POOL_AMOUNT, and SUBSIDY_POOL_CURRENCY_CODE – the pool being consumed, the maximum amount available, and its currency.
• SUBSIDY_ID, SUBSIDY_AMOUNT, and SUBSIDY_CURRENCY_CODE – the specific subsidy drawn and the amount and currency applied.
• VENDOR_ID – the vendor funding the subsidy pool.
• CONVERSION_RATE – the rate used to translate between pool and subsidy currencies.
• OBJECT_VERSION_NUMBER – optimistic locking control for concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard WHO-column audit tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – the standard EBS flexfield extension columns for customer-specific data.

Common Use Cases and Queries

The most frequent operational use is validating that accumulated subsidy usage does not exceed the pool maximum before a quote is finalized. A typical reporting query aggregates usage by pool:

• Summing SUBSIDY_POOL_AMOUNT and SUBSIDY_AMOUNT grouped by SUBSIDY_POOL_ID to compute utilization and remaining capacity.
• Joining on SOURCE_OBJECT_ID to reconcile usage against a specific quote line.
• Filtering by VENDOR_ID to produce vendor-level exposure reports.
• Using CONVERSION_RATE to restate amounts into a reporting currency where pool and subsidy currencies differ.
• Auditing change history through LAST_UPDATED_BY and LAST_UPDATE_DATE for compliance reviews.

A representative pattern is: SELECT subsidy_pool_id, SUM(subsidy_amount), MAX(subsidy_pool_amount) FROM okl.okl_quote_subpool_usage GROUP BY subsidy_pool_id. Because the table is flagged as standalone, analysts typically join it to quote and pool tables via SUBPOOL_TRX_ID and SUBSIDY_POOL_ID rather than relying on declared constraints.

Related Objects

As the mined relationship data classifies OKL_QUOTE_SUBPOOL_USAGE as standalone, no formal foreign-key dependencies were documented. The following are the logical objects most commonly associated through its business-key columns:

• OKL_SUBSIDY_POOLS – joined on SUBSIDY_POOL_ID to obtain pool definitions and ceilings.
• OKL_SUBPOOL_TRX – joined on SUBPOOL_TRX_ID to retrieve the originating subsidy pool transaction.
• OKL_QUOTES / OKL_QUOTE_LINES – joined through SOURCE_OBJECT_ID where SOURCE_TYPE_CODE indicates a quote source.
• OKL_SUBSIDIES – joined on SUBSIDY_ID for subsidy master details.
• PO_VENDORS / AP_SUPPLIERS – joined on VENDOR_ID for supplier attribution.
• OKL_ASSETS – associated through ASSET_NUMBER for asset-level reporting.

These associations are supported by shared business keys rather than enforced constraints, and should be validated against the target instance before use in production reporting.