Search Results okl_trq_pk
Overview
OKL.OKL_TRX_REQUESTS is a Leasing and Finance Management (OKL) transaction table that stores transaction-level request information. Each row represents either a contract-level request or an asset-level request, functioning as the operational log through which lease and finance transactions are initiated and tracked. The table carries descriptive attributes for loan and lease terms, interest and rate calculation parameters, currency details, subsystem references, and standard EBS WHO columns, positioning it as a central fact source for contract origination and financial restructuring activity in both EBS 12.1.1 and 12.2.2.
The primary key is the surrogate key ID, enforced by the constraint OKL_TRQ_PK. A separate unique index, OKL_TRQ_U1, is defined on REQUEST_NUMBER, which serves as the business-key candidate. The second documented unique index, OKL_TRX_REQUESTS_U1, is defined on ID. The Data Vault classification derived heuristically from the foreign key structure is hub-leaning; in a dimensional or Data Vault model, this table is best treated as a hub candidate, with its request identifiers acting as the durable business key and the many descriptive columns modeled as satellite attributes.
Key Information Stored
The 81 documented columns span request identity, financial terms, and cross-module references. The most significant include:
ID— surrogate primary key (OKL_TRQ_PK).REQUEST_NUMBER— human-readable business key, uniquely indexed byOKL_TRQ_U1.REQUEST_TYPE_CODEandAPPLY_TO_CODE— classify the request and determine the target level (contract or asset).REQUEST_STATUS_CODEandREQUEST_REASON_CODE— track workflow state and the business reason for the request.AMOUNT,BASE_RATE,MINIMUM_RATE,MAXIMUM_RATE,ADDER— the pricing and tolerance terms used to derive the loan or lease rate.YIELD,YIELD_TYPE,RESIDUAL,CUR_PRINCIPAL_BALANCE,CUR_ACCUM_INTEREST— yield and balance-related measures.START_DATE,END_DATE,DATE_OF_CONVERSION,RESTRUCTURE_DATE,PAYMENT_DATE— key lifecycle dates and term boundaries.TERM_DURATION,PAYMENT_FREQUENCY_CODE,PAYMENT_AMOUNT,ADJUSTMENT_FREQUENCY_CODE— term and payment schedule configuration.CURRENCY_CODE,CURRENCY_CONVERSION_RATE,CURRENCY_CONVERSION_TYPE,CURRENCY_CONVERSION_DATE— currency and conversion context.- Foreign key columns
CHR_ID,TCN_ID,LEGAL_ENTITY_ID, plusORG_ID— link the request to contracts, transactions, legal entities, and the operating unit. - Standard EBS audit columns (
CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE,OBJECT_VERSION_NUMBER) and theATTRIBUTE1–ATTRIBUTE15flexfield set.
Common Use Cases and Queries
Typical reporting and reconciliation scenarios include: retrieving all outstanding requests by status or type, analyzing pricing terms such as yield and rates, and reconciling tax lines associated with a request. Sample patterns are shown below.
- Retrieve a request by business key:
SELECT * FROM OKL_TRX_REQUESTS WHERE REQUEST_NUMBER = :p_request_number; - List requests awaiting action:
SELECT REQUEST_NUMBER, REQUEST_TYPE_CODE, REQUEST_STATUS_CODE, AMOUNT, CURRENCY_CODE FROM OKL_TRX_REQUESTS WHERE REQUEST_STATUS_CODE = 'PENDING'; - Report by operating unit and date range:
SELECT REQUEST_NUMBER, CREATION_DATE FROM OKL_TRX_REQUESTS WHERE ORG_ID = :p_org_id AND CREATION_DATE BETWEEN :p_start AND :p_end; - Join tax lines to requests:
SELECT r.REQUEST_NUMBER, t.* FROM OKL_TRX_REQUESTS r JOIN OKL_TAX_LINES t ON t.TRQ_ID = r.ID; - Analyze yield terms:
SELECT REQUEST_NUMBER, BASE_RATE, MINIMUM_RATE, MAXIMUM_RATE, YIELD FROM OKL_TRX_REQUESTS WHERE YIELD IS NOT NULL; - Link requests to legal entities:
SELECT r.REQUEST_NUMBER, le.* FROM OKL_TRX_REQUESTS r JOIN FV_LEGAL_ENTITIES le ON r.LEGAL_ENTITY_ID = le.LEGAL_ENTITY_ID;
Related Objects
Relationship metadata identifies the following dependents and references:
OKL_TAX_LINES— referencesOKL_TRX_REQUESTSviaTRQ_ID.OKL_TAX_LINES_ALL— referencesOKL_TRX_REQUESTSviaTRQ_ID.OKL_UPG_TRX_CONTRACTS_T— referenced byOKL_TRX_REQUESTS.TCN_ID.FV_LEGAL_ENTITIES— referenced byOKL_TRX_REQUESTS.LEGAL_ENTITY_ID.OKL_TRX_REQUESTS.CHR_ID— self-referencing or external contract reference used to associate requests with contracts.
-
Table: OKL_TRX_REQUESTS
12.1.1
owner:OKL, object_type:TABLE, fnd_design_data:OKL.OKL_TRX_REQUESTS, object_name:OKL_TRX_REQUESTS, status:VALID, product: OKL - Leasing and Finance Management , description: Stores transaction-level request information. Records in this table either represent Contract-level requests or Asset-level requests. , implementation_dba_data: OKL.OKL_TRX_REQUESTS ,
-
Table: OKL_TRX_REQUESTS
12.2.2
owner:OKL, object_type:TABLE, fnd_design_data:OKL.OKL_TRX_REQUESTS, object_name:OKL_TRX_REQUESTS, status:VALID, product: OKL - Lease and Finance Management , description: Stores transaction-level request information. Records in this table either represent Contract-level requests or Asset-level requests. , implementation_dba_data: OKL.OKL_TRX_REQUESTS ,
-
eTRM - OKL Tables and Views
12.2.2
description: Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards ,
-
eTRM - OKL Tables and Views
12.1.1
description: Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards ,
-
eTRM - OKL Tables and Views
12.2.2
description: Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards ,
-
eTRM - OKL Tables and Views
12.1.1
description: Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards ,