Results for “po_order_number”

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

Overview

OKL_TRX_EXTENSION_V is a PL/SQL view owned by the APPS schema within the Oracle E-Business Suite Leasing and Finance Management module (OKL). It functions as the transaction header extension view, exposing descriptive and operational attributes attached to lease and finance transaction headers. In ETRM implementations, the transaction header records the core commercial identity of a contract, while the extension table stores the supplementary data used for reporting, letter generation, integration payloads, and downstream processing. This view presents a denormalized, read-only projection of those extension attributes, joined with the language-specific translation rows so that reports and interfaces retrieve the correct descriptive text based on the session language.

Within Oracle EBS 12.1.1 and 12.2.2, the view is typically consumed by concurrent programs, BI Publisher data templates, Oracle Reports, and custom integration extracts. Because it is an APPS-owned view rather than a table, it carries no maintenance responsibility for the developer and remains consistent with the multi-language architecture of the OKL schema. One attribute of direct interest to users searching for contract_effective_from is the CONTRACT_EFFECTIVE_FROM column, which is surfaced here alongside the equivalent INV_AGRMNT_EFFECTIVE_FROM value.

Underlying Base Objects

The documented base objects referenced by OKL_TRX_EXTENSION_V are:

• OKL_TRX_EXTENSION_B — the transactional base table holding the extension header records, including the CONTRACT_EFFECTIVE_FROM, CONTRACT_NUMBER, currency, customer, and the CUST_ATTRIBUTE1 through CUST_ATTRIBUTE15 flexfield columns.
• OKL_TRX_EXTENSION_TL — the translation table providing the LANGUAGE column and any translatable descriptive columns exposed by the view.

The view aliases the base table as TEH and the translation table as TEHL, joining them so that the language-specific row is returned for the caller's language environment. Both base objects are exposed through synonyms in the APPS schema, which is standard for OKL objects and allows the view definition to remain schema-independent. The view also exposes TEH.ROWID as ROW_ID, giving consumers a unique row identifier, and OBJECT_VERSION_NUMBER for optimistic locking awareness where the view is used inside Oracle Forms-based flows.

Key Columns

Several column groups are significant when building reports or extracts against this view:

• Identity and linkage: HEADER_EXTENSION_ID, SOURCE_ID, SOURCE_TABLE, and CONTRACT_NUMBER. SOURCE_TABLE and SOURCE_ID allow the extension header to be tied back to the originating transaction entity.
• Effective dating: CONTRACT_EFFECTIVE_FROM captures the date from which the lease contract takes effect, while INV_AGRMNT_EFFECTIVE_FROM records the corresponding effective date for the invoice agreement. These are the primary columns returned when a user queries contract_effective_from.
• Commercial and party data: CONTRACT_CURRENCY_CODE, INV_AGRMNT_CURRENCY_CODE, CUSTOMER_NAME, CUSTOMER_ACCOUNT_NUMBER, SALES_REP_NAME, BILL_TO_ADDRESS_NUM, PO_ORDER_NUMBER, and MASTER_LEASE_NUMBER.
• Accounting and process controls: INT_CALC_METHOD_CODE, REV_REC_METHOD_CODE, ACCRUAL_OVERRIDE_FLAG, ASSIGNABLE_FLAG, CONVERTED_ACCOUNT_FLAG, and CONVERTED_NUMBER.
• Insurance and quote references: INS_POLICY_TYPE_CODE, INS_POLICY_NUMBER, TERM_QUOTE_NUM, TERM_QUOTE_TYPE_CODE, and TERM_QUOTE_ACCEPT_DATE.
• Descriptive flexfields: CUST_ATTRIBUTE_CATEGORY and CUST_ATTRIBUTE1 through CUST_ATTRIBUTE15, providing the configurable attribute structure used for client-specific reporting.
• Language: LANGUAGE from the translation table, indicating which language row was joined.

Common Use Cases and Queries

The most frequent scenario is retrieving the effective date of a lease contract for a report or interface, often filtered by contract number or date range. A representative query is:

• SELECT contract_number, contract_effective_from, inv_agrmnt_effective_from, contract_currency_code FROM okl_trx_extension_v WHERE contract_effective_from >= :p_from_date AND contract_effective_from < :p_to_date ORDER BY contract_effective_from;

Customer-facing reports join this view to OKL_TRX_HEADERS_V using CONTRACT_NUMBER to combine header-level and extension-level attributes, while integration extracts select the CUST_ATTRIBUTE flexfield columns to populate external systems. Data migration and reconciliation checks compare CONTRACT_EFFECTIVE_FROM against the corresponding column on OKL_TRX_EXTENSION_B to confirm that translation rows are complete. Because the view is read-only, all such access is confined to query operations, making it safe for reporting use in both 12.1.1 and 12.2.2 environments.