Search Results okl_trq_u1

Overview

OKL.OKL_TRX_REQUESTS is a transaction-level request table within the Oracle Leasing (OKL) module of Oracle E-Business Suite. It stores request information that either pertains to a contract or to an asset. When a record represents a contract-level request, the table functions as an extension of OKL_TRX_CONTRACTS. When it represents an asset-level request, it acts as an extension of OKL_TXR_ASSETS. The parent record for any given row is identified by the value held in the JTOT_OBJECT1_CODE column, which discriminates between the two request contexts.

From a Data Vault modeling perspective, the heuristic classification of this object is hub-leaning. This suggests OKL_TRX_REQUESTS could be modeled as a hub, anchored by its unique business key REQUEST_NUMBER (index OKL_TRQ_U1) and its surrogate primary key ID (index OKL_TRX_REQUESTS_U1). The rich descriptive attributes—terms, rates, dates, and status—function as satellite content attached to that hub, while foreign key references to contracts, legal entities, and related OKL entities behave as link columns.

Key Information Stored

The table is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its primary key is ID, which is the surrogate identifier indexed by the unique index OKL_TRX_REQUESTS_U1. Two unique indexes serve as business-key candidates: OKL_TRQ_U1 on REQUEST_NUMBER and OKL_TRX_REQUESTS_U1 on ID. In addition, two non-unique indexes support retrieval performance: OKL_TRQ_REQUEST_TYPE_IDX on REQUEST_TYPE_CODE and OKL_TRQ_REQ_STATUS_IDX on REQUEST_STATUS_CODE.

The most operationally significant columns include:

• ID — surrogate primary key column uniquely identifying each request record.
• REQUEST_NUMBER — the business-facing unique identifier for the request.
• JTOT_OBJECT1_CODE — indicates the parent object type, distinguishing contract-level from asset-level requests.
• OBJECT1_ID1 / OBJECT1_ID2 — generic object identifier components carrying the parent key reference.
• DNZ_KHR_ID — denormalized contract identifier retained for performance reasons.
• REQUEST_TYPE_CODE — categorizes the request, referenced by a dedicated index.
• REQUEST_STATUS_CODE — the lifecycle status of the request, also indexed.
• APPLY_TO_CODE — specifies what the request applies to.
• START_DATE / END_DATE / TERM_DURATION — the request's effective period and duration.
• AMOUNT / CURRENCY_CODE — monetary value and its currency.
• SUBSIDY_YN / CASH_APPLIED_YN — flags controlling subsidy and cash application behavior.
• ORG_ID — multi-org operating unit context.
• OBJECT_VERSION_NUMBER — optimistic locking column used during concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns for customer-defined extensions.

The documented physical schema contains 81 columns in total, including interest rate terms such as BASE_RATE, INDEX_NAME, VARIABLE_METHOD_CODE, INTEREST_METHOD_CODE, YIELD, and RESIDUAL.

Common Use Cases and Queries

Typical reporting and integration scenarios include retrieving all requests of a given type or status, tracing requests back to their parent contract or asset, and joining request financial terms for lease accounting analysis. Because REQUEST_TYPE_CODE and REQUEST_STATUS_CODE are indexed, filter predicates on these columns perform efficiently.

A representative query resolving contract-level requests to their parent contract uses DNZ_KHR_ID:

• SELECT r.REQUEST_NUMBER, r.REQUEST_TYPE_CODE, r.REQUEST_STATUS_CODE, r.AMOUNT, tr.CONTRACT_NUMBER FROM OKL_TRX_REQUESTS r, OKL_TRX_CONTRACTS tr WHERE r.DNZ_KHR_ID = tr.ID AND r.JTOT_OBJECT1_CODE = :object_code;

Another common pattern aggregates requests by status for dashboard reporting:

• SELECT REQUEST_STATUS_CODE, COUNT(*) FROM OKL_TRX_REQUESTS WHERE ORG_ID = :org_id GROUP BY REQUEST_STATUS_CODE;

Joins to OKL_TAX_LINES and OKL_TAX_LINES_ALL via TRQ_ID are used to reconcile tax details associated with a request.

Related Objects

The following objects reference OKL_TRX_REQUESTS or are referenced by it:

• OKL_TRX_CONTRACTS — the parent contract table; joined via DNZ_KHR_ID or via OBJECT1_ID1/OBJECT1_ID2 when JTOT_OBJECT1_CODE indicates a contract-level request.
• OKL_TXR_ASSETS — the parent asset table for asset-level requests.
• OKL_TAX_LINES — references OKL_TRX_REQUESTS.TRQ_ID, linking tax line detail to a request.
• OKL_TAX_LINES_ALL — the multi-org variant, also referencing TRQ_ID.
• OKL_UPG_TRX_CONTRACTS_T — referenced via the TCN_ID foreign key.
• FV_LEGAL_ENTITIES — referenced via the LEGAL_ENTITY_ID foreign key, tying requests to a legal entity.

Together these relationships confirm the table's role as a central request repository spanning both contract and asset transactions within the Oracle Leasing data model.