Search Results okx_operunit




Overview
Explore in AI Chat

Overview

APPS.OKL_CS_LESSOR_UV is a reporting view in the Oracle EBS Lease and Finance Management (OKL) / Contracts (OKC) schema. It presents lessor and counterparty address information for lease and contract records, consolidating party role assignments held against a contract with the corresponding Operating Unit organization definition and its associated HR location data. The view is intended primarily for lessor/customer contact reporting, including telephone, postal address, and party number details, and is commonly consumed by Oracle Contracts customer-facing reports, forms, and integration extracts. It answers the practical business question of "which lessor or operating unit party is associated with this contract, and what is its address and contact information." In 12.1.1 and 12.2.2 the view definition is largely identical, though the 12.2.2 metadata aligns the OKX_ORGANIZATION_DEFS_V filter on ORGANIZATION_TYPE = 'OPERATING_UNIT' and INFORMATION_TYPE = 'Operating Unit Information'.

Underlying Base Objects

The view is defined over five principal objects, joined through the OKX organization framework:

  • OKC_K_PARTY_ROLES_V — the contract party role view (PR). It supplies the role name and the JTOT object keys (jtot_object1_code, object1_id1, object1_id2) used to resolve the party to an operating unit.
  • OKC_K_HEADERS_B — the contracts header table (CHR), contributing id and contract_number.
  • OKX_ORGANIZATION_DEFS_V — the OKX organization definitions view (aliased OKX_OPERUNIT). This is the object referenced by the user's search term "okx_operunit" and is the central driver of the join.
  • HR_ALL_ORGANIZATION_UNITS — the HR organization units table (OU), matched on organization_id = OKX_OPERUNIT.id1.
  • HR_LOCATIONS — the HR locations view (LOC), outer-joined via location_id(+) so that parties without a defined location still return a row.

Documented dependencies also include ARP_ADDR_LABEL_PKG, FND_GLOBAL, and HR_GENERAL, which supply supporting functions used within the OKX and HR views.

Key Columns

  • CONTRACT_ID, CONTRACT_NUMBER — identify the contract header.
  • ROLE_NAME — the party role held on the contract (for example, lessor or customer).
  • PTYPE — ORGANIZATION_TYPE, filtered to 'OPERATING_UNIT'.
  • COMPANY, CUSTOMER_NUMBER — the organization name and party number from OKX_ORGANIZATION_DEFS_V.
  • PHONE, ADDRESS1–ADDRESS4, CITY, STATE, POSTAL_CODE, COUNTRY — address elements sourced from HR_LOCATIONS.
  • AMT_GUARANTEED, EMAIL, COUNTY, PROVINCE — returned as NVL placeholders (empty string or zero) and therefore carry no data in the current definition.

Common Use Cases and Queries

Typical usage is a contract-level listing of lessor parties and their addresses for reporting or downstream extracts:

SELECT contract_number,
       role_name,
       company,
       customer_number,
       phone,
       address1,
       city,
       state,
       postal_code,
       country
  FROM apps.okl_cs_lessor_uv
 WHERE contract_number = :p_contract_number;

To retrieve all parties tied to a specific operating unit organization:

SELECT contract_number, role_name, company
  FROM apps.okl_cs_lessor_uv
 WHERE customer_number = :p_party_number;

Because AMT_GUARANTEED, EMAIL, COUNTY and PROVINCE are hard-coded placeholders, these columns should not be relied upon for business data; address and party identification fields are the substantive content of the view.