Search Results variable_method_code

Overview

OKL_TRX_REQUESTS_V is a reporting and integration view within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Leasing and Finance Management (OKL) module. It exposes transaction-level request information, where each row represents either a contract-level request or an asset-level request. The view consolidates the request attributes that drive lease and loan origination, pricing, and payment processing, and presents them in a single denormalized structure suitable for inquiry, downstream integration, and custom reporting against the OKL request tables.

Because the request records carry both business attributes (request type, apply-to context, dates, amounts, rates) and standard EBS audit columns, the view serves as a convenient access point for developers building extracts, reconciliations, or interfaces that need request data without joining the underlying request and request-line tables directly.

Underlying Base Objects

Per the ETRM metadata, the view is documented as not implemented in the reference database, and no referenced base objects are documented. The view text nevertheless shows the driving table aliased as TRQ, indicating that OKL_TRX_REQUESTS_V is defined primarily over the OKL transaction request table (the OKL_TRX_REQUESTS family, with associated request-line detail under the OKL_TRX_REQUEST_LINES family). Records are distinguished as contract-level or asset-level through the object identifier columns (OBJECT1_ID1, OBJECT1_ID2) and the JTOT_OBJECT1_CODE column.

Standard EBS who-columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and the multi-org ORG_ID column are exposed from the base table. The concurrent-program audit columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also carried through.

Key Columns

• ID / ROW_ID — Primary identifier of the request record; ROW_ID is the ROWID of the base row.
• OBJECT1_ID1 / OBJECT1_ID2 / JTOT_OBJECT1_CODE — Identify the subject of the request. These, together with APPLY_TO_CODE, determine whether the record applies to a contract or an asset.
• REQUEST_TYPE_CODE — Classifies the request (for example paydown or rate-adjustment style requests).
• APPLY_TO_CODE — Indicates the object context to which the request applies, distinguishing contract-level from asset-level requests.
• START_DATE / END_DATE / TERM_DURATION — Effective period and term associated with the request.
• AMOUNT / PAYMENT_AMOUNT / PAYMENT_DATE / PAYDOWN_TYPE — Monetary and payment-related attributes, used for paydown and cash-application processing.
• CURRENCY_CODE / CURRENCY_CONVERSION_RATE / CURRENCY_CONVERSION_TYPE / CURRENCY_CONVERSION_DATE — Currency and conversion details for the requested amount.
• MINIMUM_RATE / MAXIMUM_RATE / BASE_RATE / TOLERANCE / ADJUSTMENT_FREQUENCY_CODE / INDEX_NAME / VARIABLE_METHOD_CODE / ADDER / DAYS_IN_YEAR — Interest-rate and adjustment parameters describing the requested pricing terms.
• SUBSIDY_YN / CASH_APPLIED_YN — Flags indicating subsidy treatment and whether cash has been applied.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield columns available for client-specific extension.
• ORG_ID — Operating unit identifier supporting multi-org security.

The column most closely associated with the search term request_reason_code is not enumerated in the documented select list; reason-code semantics in OKL are typically captured through the descriptive flexfield attributes or the request-type classification. Where a dedicated reason column exists in the underlying request table, it would be exposed through this view as part of the request attribute set.

Common Use Cases and Queries

Typical uses include reconciling open requests against contracts and assets, extracting request data for pricing or paydown analysis, and feeding downstream integration. A basic query filters by request type and apply-to context for a given operating unit:

• SELECT id, request_type_code, apply_to_code, object1_id1, amount, currency_code FROM okl_trx_requests_v WHERE org_id = :p_org_id AND request_type_code = :p_type;
• SELECT id, start_date, end_date, term_duration, minimum_rate, maximum_rate FROM okl_trx_requests_v WHERE apply_to_code = 'CONTRACT';
• SELECT id, object1_id1, attribute_category, attribute1 FROM okl_trx_requests_v WHERE subsidy_yn = 'Y';

Because the view is documented as not implemented in the reference database, availability and exact column population should be verified in the target instance before relying on it for production reporting.