Results for “middle_name”

50+ results




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

Overview

OKL_INSURER_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL (Lease and Finance Management) product. Its documented purpose is to store and expose Insurer information, presenting a filtered subset of third-party party records that have been classified as insurers. The view is populated dynamically from the Oracle Trading Community Architecture (TCA) party model, meaning it contains no persisted data of its own; every query resolves against the underlying HZ_PARTIES table at runtime.

Because it is a view rather than a table, OKL_INSURER_V serves as a stable, semantically constrained interface for reports, concurrent programs, and integrations that need a list of active insurers without embedding TCA filter logic themselves. The view hard-codes the filter conditions CATEGORY_CODE = 'INSURER' and STATUS = 'A', so consumers automatically receive only active, insurer-categorised parties. In Oracle EBS 12.1.1 and 12.2.2 the view is reported with a VALID status, confirming that it compiles cleanly against the corresponding TCA schema in both releases.

Underlying Base Objects

The view is defined over a single referenced base object, HZ_PARTIES, accessed via a synonym from the APPS schema. The defining query aliases the table as PRT and selects a fixed set of party attributes, applying the restricting predicates described above:

  • HZ_PARTIES — the TCA registry table holding all parties (persons, organisations, groups, and relationships). OKL_INSURER_V draws party identity, category, status, and person-name attributes from this table.
  • The filter PRT.CATEGORY_CODE = 'INSURER' narrows the result set to parties whose TCA category is Insurer.
  • The filter PRT.STATUS = 'A' restricts output to active parties only.

Two literal expressions are projected into the result set: '#' returned under the alias ID2, and the constant string 'THIRD_PARTY'. These appear to support downstream lease UI or LOV components that require placeholder or classifying values alongside the party data.

Key Columns

The documented column list combines TCA identifiers with person-oriented attributes:

Common Use Cases and Queries

Typical usage includes insurer lookups in lease origination, populating insurer lists of values, and reporting on active insurers used across lease contracts. A basic query retrieving all active insurers follows:

  • SELECT party_id, party_name, party_number, email_address, insurer_type FROM okl_insurer_v ORDER BY party_name;

Filtering on a specific insurer or number is equally straightforward:

  • SELECT party_id, party_name FROM okl_insurer_v WHERE party_number = :p_party_number;

Because PARTY_ID is the common TCA key, the view is frequently joined to lease tables such as contract or party-role detail to resolve insurer names for a given lease, or joined back to HZ_PARTIES when attributes beyond the projected column list are required. Note that the view does not expose creation dates, addresses, or contact points beyond e-mail; those require joins to additional TCA entities.