Results for “policy_type”

50+ results




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

Overview

The view APPS.OKL_CS_CUST_INS_POLICY_UV is a customer-facing insurance policy view within the Oracle Lease and Finance Management (OKL) module. It consolidates insurance policy information attached to lease contracts together with the associated customer party, contract status, and the operating unit that owns the lease. Its primary role is to present a single, denormalized result set that joins a lease contract header, its associated insurance policy record, the customer party role, fnd_lookups-based policy type, and status lookups into one queryable structure. Technically, it is a multi-table join view defined over both OKL and OKC (Contracts Core) objects, and it surfaces the POLICY_NUMBER attribute — the exact term users typically search for when reconciling insurance coverage against lease contracts. Because it exposes ORG_ID and OPERATING_UNIT, it is naturally suited to multi-org aware reporting and can be constrained by the MO: Operating Unit profile or by an explicit ORG_ID predicate.

Underlying Base Objects

The view is defined with a SELECT DISTINCT over the following documented base objects:

The join keys are consistent and tightly coupled: INB.KHR_ID = CHR.ID and INB.KHR_ID = CPR.CHR_ID, ensuring policy, contract header, and party role align on the same contract. The FND_LOOKUPS join is a non-keyed reference lookup based on lookup code and type.

Key Columns

  • CONTRACT_NUMBER — the lease contract the insurance policy is attached to.
  • POLICY_NUMBER — the insurance policy identifier, sourced from OKL_INS_POLICIES_ALL_B.
  • POLICY_TYPE — decoded meaning of the IPY_TYPE lookup (OKL_INSURANCE_TYPE).
  • START_DATE / END_DATE — contract-level effective dates as exposed by the header.
  • STATUS — decoded contract status meaning; ABANDONED contracts are excluded.
  • PARTY_ID — the customer party tied to the contract via the OKX_PARTY role.
  • CONTRACT_ID / ORG_ID — technical identifiers for the contract and operating unit.
  • OPERATING_UNIT — descriptive name of the owning HR operating unit.
  • DESCRIPTION — free-text contract description.

Common Use Cases and Queries

Typical uses include verifying insurance coverage per lease, locating policies by policy number, and reporting active insurance by operating unit.

  • Search by policy number:
    SELECT contract_number, policy_number, policy_type, status
    FROM   okl_cs_cust_ins_policy_uv
    WHERE  policy_number = :p_policy_number;
  • List all policies for a customer:
    SELECT contract_number, policy_number, policy_type, start_date, end_date
    FROM   okl_cs_cust_ins_policy_uv
    WHERE  party_id = :p_party_id
    ORDER BY start_date DESC;
  • Report insurance coverage by operating unit:
    SELECT operating_unit, policy_number, policy_type, status
    FROM   okl_cs_cust_ins_policy_uv
    WHERE  org_id = :p_org_id;

Because the view is multi-org aware through ORG_ID/OPERATING_UNIT and filters out ABANDONED contracts, it is suitable for operational dashboards and integration extracts that require current, non-abandoned lease insurance data.