Search Results okl_trx_requests




Overview
Explore in AI Chat

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:

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 — references OKL_TRX_REQUESTS via TRQ_ID.
  • OKL_TAX_LINES_ALL — references OKL_TRX_REQUESTS via TRQ_ID.
  • OKL_UPG_TRX_CONTRACTS_T — referenced by OKL_TRX_REQUESTS.TCN_ID.
  • FV_LEGAL_ENTITIES — referenced by OKL_TRX_REQUESTS.LEGAL_ENTITY_ID.
  • OKL_TRX_REQUESTS.CHR_ID — self-referencing or external contract reference used to associate requests with contracts.