Results for “okl_cs_lessor_uv”

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

Overview

OKL_CS_LESSOR_UV is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered as part of the OKL – Leasing and Finance Management module. Its status is VALID in both Release 12.1.1 and 12.2.2. The view presents lessor-side party and address information associated with lease and finance contracts. Specifically, it exposes the operating unit that acts as the lessor on a contract, together with the corresponding role assignment, contact, and mailing address details. The suffix "_UV" identifies the object as a user view, a naming convention Oracle applies to simplified, presentation-oriented views intended primarily for reporting, inquiry, and downstream integration rather than for transactional processing.

Because the view joins contract header data to party role and organization definitions, it allows reporting tools and custom code to retrieve lessor identity and location attributes through a single, denormalized result set, avoiding the need to reconstruct the multi-table relationship between contracts, roles, and operating units manually.

Underlying Base Objects

The view is defined over the following documented objects:

• OKC_K_HEADERS_B (SYNONYM) – the contract header base table, supplying CONTRACT_ID and CONTRACT_NUMBER.
• OKC_K_PARTY_ROLES_V (VIEW) – the contract party roles view, supplying the ROLE and the join keys that link a role to a specific organization.
• OKX_ORGANIZATION_DEFS_V (VIEW) – the organization definitions view, filtered to operating units, supplying organization type, name, and party number.
• HR_ALL_ORGANIZATION_UNITS (SYNONYM) – the organization unit definition, joined by ORGANIZATION_ID to obtain the location reference.
• HR_LOCATIONS (VIEW) – the location view, supplying telephone and address attributes.
• ARP_ADDR_LABEL_PKG, FND_GLOBAL, and HR_GENERAL (PACKAGEs) – referenced metadata objects consistent with address label formatting, session context, and HR utility usage.

The joins are governed by a fixed filter: OKX_OPERUNIT.ORGANIZATION_TYPE = 'OPERATING_UNIT' and OKX_OPERUNIT.INFORMATION_TYPE = 'OPERATING UNIT INFORMATION'. The location join is outer (LOC.LOCATION_ID(+) = OU.LOCATION_ID), so contracts with an operating unit lacking a location still return a row with null address fields.

Key Columns

• CONTRACT_ID / CONTRACT_NUMBER – unique identifier and business number of the contract header.
• ROLE_NAME – the party role held on the contract, typically the lessor role.
• AMT_GUARANTEED – returned as NVL('',0), i.e., a placeholder column with no underlying data in this definition.
• PTYPE – the organization type from OKX_OPERATION_DEFS_V, resolved to 'OPERATING_UNIT'.
• COMPANY / CUSTOMER_NUMBER – the operating unit name and its party number.
• EMAIL – returned as NVL('',''), a placeholder with no populated value.
• PHONE – the primary telephone number from HR_LOCATIONS.
• ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4, CITY, COUNTY, PROVINCE, STATE, POSTAL_CODE, COUNTRY – address elements; ADDRESS4, COUNTY, and PROVINCE are placeholders returning empty values.

Common Use Cases and Queries

Typical uses include lessor identification on lease contract reports, lessor address population on generated correspondence, and integration extracts feeding external systems. A representative query:

• SELECT CONTRACT_NUMBER, ROLE_NAME, COMPANY, CUSTOMER_NUMBER, PHONE, ADDRESS1, CITY, STATE, POSTAL_CODE, COUNTRY FROM APPS.OKL_CS_LESSOR_UV WHERE CONTRACT_NUMBER = :contract_number;
• SELECT CONTRACT_ID, COMPANY, CITY, COUNTRY FROM APPS.OKL_CS_LESSOR_UV WHERE PTYPE = 'OPERATING_UNIT';

Because EMAIL, AMT_GUARANTEED, ADDRESS4, COUNTY, and PROVINCE are hard-coded placeholders, consumers should not rely on those columns and must source such data elsewhere.