Results for “chr_start_date”

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

Overview

OKL_K_HDRS_FULL_UV is an APPS-owned database view in the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL). Its documented purpose is to serve as the UI view for the LLA (Lease/Loan/Line of Credit Agreement) Contract Details page. The view consolidates contract header, version, status, customer, lessor, currency, and product-level information into a single denormalized projection that the Oracle Forms and OAF-based contract pages consume at runtime. Because it is a view rather than a table, it introduces no storage of its own; it is a read-only access path over the normalized OKC and OKL base objects that underlie the leasing contract data model. The view is marked VALID in ETRM 12.2.2 metadata, indicating that its underlying dependencies are intact.

Underlying Base Objects

The view is defined over a broad set of synonyms, views, and packages across the contracting (OKC), leasing (OKL), trading community (HZ), general ledger (GL), and human resources (HR) schemas. Core contract data is sourced from OKC_K_HEADERS_B, OKC_K_HEADERS_V, OKC_K_VERS_NUMBERS, OKC_STATUSES_B, OKC_STATUSES_TL, OKC_K_PARTY_ROLES_B, OKC_CONTACTS, OKC_RULES_B, and OKC_RULE_GROUPS_B. Leasing-specific attributes come from OKL_K_HEADERS, OKL_PRODUCTS, OKL_PRODUCT_PARAMETERS_V, and OKL_SYS_ACCT_OPTS_ALL. Party and location information is resolved through HZ_PARTY_SITES, HZ_PARTY_SITE_USES, and HZ_LOCATIONS, while currency data is drawn from FND_CURRENCIES_TL. Organizational and ledger context is provided by HR_OPERATING_UNITS and GL_LEDGERS_PUBLIC_V. Supporting logic is delivered by packages such as OKC_UTIL, OKL_ACCOUNTING_UTIL, and ARP_ADDR_LABEL_PKG.

Key Columns

The view exposes aliased columns that group by functional area. Contract identity and status are represented by CHR_ID, CHR_CONTRACT_NUMBER, CHR_DESCRIPTION, CHR_STS_CODE, and CHR_STS_MEANING. Versioning is handled via VERS_VERSION, which concatenates the major and minor version numbers. Date fields are surfaced as character strings (for example CHR_START_DATE, CHR_END_DATE, CHR_DATE_SIGNED, KHR_ACCEPTED_DATE, KHR_EXPECTED_DELIVERY_DATE) to suit UI display formatting. Leasing indicators such as KHR_GENERATE_ACCRUAL_YN, KHR_SYNDICATABLE_YN, KHR_PREFUNDING_ELIGIBLE_YN, KHR_REVOLVING_CREDIT_YN, KHR_CONVERTED_ACCOUNT_YN, and KHR_CREDIT_ACT_YN drive contract behavior flags. Customer and lessor identities are exposed through CUST_ID, CUST_OBJECT1_ID1, CUST_OBJECT1_ID2, CUST_JTOT_OBJECT1_CODE, LESSOR_ID, LESSOR_OBJECT1_ID1, LESSOR_OBJECT1_ID2, and LESSOR_JTOT_OBJECT1_CODE, with placeholder literals 'CUST_NAME' and 'LESSOR_NAME' defined so the UI layer supplies resolved names via address label logic. Currency details appear as CHR_CURRENCY_CODE, CURRENCY_NAME, and KHR_CURRENCY_CONVERSION_TYPE. Several MLA-related columns (MLA_CONTRACT_NUMBER, MLA_GVR_CHR_ID_REFERRED, MLA_GVR_ID) are explicitly cast to NULL, reflecting a reserved or not-yet-populated extension.

Common Use Cases and Queries

A frequent driver for querying this view is locating the lessor associated with a contract, since the user search term "lessor_name" maps directly to the LESSOR_* columns. Reporting use cases include contract detail extracts, status dashboards, and integration feeds that require a single-row flattened contract header.

• Retrieve contract header details for a specific contract:

  SELECT chr_contract_number, vers_version, chr_sts_meaning, lessor_id
  FROM   apps.okl_k_hdrs_full_uv
  WHERE  chr_contract_number = :contract_number;

• List contracts by lessor:

  SELECT chr_contract_number, chr_description, lessor_object1_id1, lessor_object1_id2
  FROM   apps.okl_k_hdrs_full_uv
  WHERE  lessor_object1_id1 IS NOT NULL;

• Report active contracts with accrual generation enabled:

  SELECT chr_contract_number, chr_sts_meaning, khr_generate_accrual_yn
  FROM   apps.okl_k_hdrs_full_uv
  WHERE  khr_generate_accrual_yn = 'Y'
  AND    chr_sts_code = 'ACTIVE';

Because the view returns lessor and customer names as static literals rather than resolved values, callers that require an actual lessor name should join the LESSOR_ID or LESSOR_OBJECT1_ID1/ID2 columns back to the trading community or party tables (for example via OKC_K_PARTY_ROLES_B and HZ tables) or invoke OKC_UTIL / ARP_ADDR_LABEL_PKG name-resolution routines. Direct DML against the view is not supported; inserts and updates must target the underlying OKC and OKL base tables.