Results for “date_issued”

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

Overview

OKL_CONDTLS_WELCOME_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is delivered as part of the OKL – Lease and Finance Management product family and is implemented as a user-facing ("UV") view intended to support the Contracts welcome page and related contract-detail reporting. The view consolidates contract header data, lease-specific header attributes, product information, customer (party) details, and status descriptions into a single denormalized structure, allowing callers to retrieve approved lease contract details without joining the underlying base tables directly.

Because the view is defined with an ORDER BY START_DATE DESC clause, results are returned sorted by contract start date in descending order, presenting the most recently commencing contracts first. This makes the view particularly convenient for features that display a list of active or recently approved contracts.

Underlying Base Objects

The documented view text references the following base objects, all exposed to APPS through synonyms:

• OKC_K_HEADERS_B — the contract header base table (CHRB), providing the primary contract ID and most scalar attributes.
• OKC_K_HEADERS_TL — the translated contract header table (CHRT), supplying language-dependent description and comment fields.
• OKL_K_HEADERS — the lease-specific header table (KHR), linking a contract to its lease product.
• OKL_PRODUCTS — the lease product definition (OP), joined via a partial outer join on PDT_ID.
• OKC_STATUSES_TL — the translated status lookup (OST), supplying the meaning for the STS_CODE.
• OKC_RULES_B — contract rules (ORGB1), filtered to RULE_INFORMATION_CATEGORY = 'CAN'.
• OKC_RULE_GROUPS_B — contract rule groups (ORGB2), filtered to RGD_CODE = 'LACAN'.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — the customer account and party tables used to derive CUSTOMER_NAME.

The CAN/LACAN rule filter is significant: it restricts the result set to contracts that carry a customer acceptance rule configuration, which is the population relevant to the welcome page's purpose.

Key Columns

• ID and CONTRACT_NUMBER / CONTRACT_NUMBER_MODIFIER — the contract identifier and human-readable contract number.
• DATE_APPROVED — the date on which the contract was approved; this is the column most often targeted when users search for "date_approved".
• DATE_ISSUED, START_DATE, END_DATE — the issue date and the contract's effective start and end dates.
• STS_CODE and CONTRACT_STATUS — the status code and its translated meaning.
• INV_ORGANIZATION_ID and AUTHORING_ORG_ID — inventory and authoring organization identifiers.
• CURRENCY_CODE — the contract's transacting currency.
• KHR_ID and PDT_ID — the lease header identifier and the associated product identifier.
• CUSTOMER_NAME and PRDUCT_NAME — the customer party name and the lease product name.

Common Use Cases and Queries

Typical use is to list approved lease contracts together with their approval date, status, customer, and product. For example, to retrieve recently approved contracts:

• SELECT id, contract_number, date_approved, start_date, customer_name, contract_status FROM okl_condtls_welcome_uv WHERE date_approved IS NOT NULL ORDER BY date_approved DESC;
• SELECT contract_number, date_approved, prduct_name FROM okl_condtls_welcome_uv WHERE sts_code = 'APPROVED';

Because the view already filters for the LACAN rule group and joins party, product, and status information, it is well suited to welcome-page listings, approval-tracking reports, and lightweight integrations that require contract-level approval dates without replicating the underlying join logic.