Results for “academic_title”

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

Overview

OKX_INSURER_V is a reporting view owned by the APPS schema within the OKX - Contracts Integration product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents insurance agency trading partners as they are registered in the Oracle Trading Community Architecture (TCA) model. Its documented description is "Insurance Agency," reflecting its purpose: to expose a denormalized, flat projection of party records that have been classified with the TCA category code INSURER.

In the context of EBS reporting and integration, OKX_INSURER_V functions as a lookup and validation source rather than a transactional entity. It does not store data of its own; it renders the current state of the underlying TCA tables. External systems, contract-generation routines, or concurrent programs that require a list of insurers — for example, to attach an insurance agency to a contract or to populate a value set or LOV — can consume this view without needing to join the more granular HZ_PARTIES and HZ_PARTY_SITES tables directly. Because the view is documented as VALID in the ETRM metadata, it is exposed as a supported object in both the 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The documented view text joins two base objects, both referenced through synonyms in the APPS schema:

• HZ_PARTIES (SYNONYM) — aliased as PRT in the view SQL. This is the TCA registry table holding the master party record, including party name, party number, category code, address components, and person-name attributes.
• HZ_PARTY_SITES (SYNONYM) — aliased as HPS. This table holds the party site (location) records associated with a party, exposing the site identifier.

The join condition is defined as PRT.CATEGORY_CODE = 'INSURER' AND PRT.PARTY_ID = HPS.PARTY_ID. The category-code predicate is the defining filter: only parties flagged as insurers are returned. The equality between PARTY_ID in both tables means the view returns one row per party-site combination, so a party with multiple sites will appear on multiple rows. The view also embeds a literal, 'THIRD_PARTY', into a column aliased as INSURER_TYPE (derived from the THIRD_PARTY literal in the select list), and a constant literal '#' aliased as ID2.

Key Columns

The view projects 25 columns. The most significant include:

• PARTY_ID — Primary identifier of the insurer party in TCA; the principal join key to contract and party-related tables.
• PARTY_NAME / PARTY_NUMBER — The insurer's display name and the TCA party number used for cross-reference.
• CATEGORY_CODE — Always 'INSURER' for rows returned by this view.
• ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTRY, COUNTY — Address components sourced from the party record.
• ADDRESS — A concatenated single-string address built from the individual components using comma and space delimiters, convenient for display and printing.
• SITE_ID / PARTY_SITE_ID — Identifier of the associated party site from HZ_PARTY_SITES.
• STATUS, THIRD_PARTY_FLAG — Status and classification attributes of the party.
• PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_LAST_NAME, PERSON_TITLE, PERSON_ACADEMIC_TITLE — Person-name attributes for parties that are individuals rather than organizations (exposed under aliases FIRST_NAME, MIDDLE_NAME, LAST_NAME, TITLE, ACADEMIC_TITLE in the documented column list).
• EMAIL_ADDRESS — Electronic contact address for the party.
• INSURER_TYPE — A constant value ('THIRD_PARTY'), indicating the integration classification expected by OKX consumers.

Common Use Cases and Queries

Typical uses include insurer lookups for contract capture, value-set population, and ad hoc reporting of the insurance agency registry. A basic listing query is:

• SELECT party_id, party_name, party_number, address FROM okx_insurer_v WHERE status = 'A'; — returns active insurers with a formatted address.
• SELECT DISTINCT party_id, party_name FROM okx_insurer_v; — produces a de-duplicated insurer list, since the underlying join can yield multiple rows per party where several sites exist.
• SELECT party_name, site_id, city, country FROM okx_insurer_v WHERE category_code = 'INSURER' ORDER BY party_name; — site-level detail for integration feeds.

Because the category predicate is embedded in the view, callers should not expect to retrieve non-insurer parties through it; filtering is applied at the source. Consumers should also account for the one-row-per-site behavior when counting or aggregating insurers.