Results for “ins_provider”

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

Overview

APPS.OKX_INS_PROVIDER_V is a reporting and integration view within the Oracle E-Business Suite (EBS) Trading Community and Order Management infrastructure. Its role is to expose supplier records that have been classified as insurers, presenting them in a normalized "party" style structure suitable for downstream consumption by insurance-related processes.

In the EBS data model, a vendor (supplier) that also acts as a provider of insurance must be distinguishable from ordinary suppliers. OKX_INS_PROVIDER_V serves precisely this purpose: it filters the supplier master to return only those vendors whose type classification is INSURER, and it re-labels the vendor columns using party-centric aliases. This mapping allows insurance, agreement, and order management modules to treat an insurer as a "party" entity without querying the broader supplier table directly.

The view is owned by the APPS schema, which is standard for shared EBS objects and ensures consistent visibility across the applications. It is common in both 12.1.1 and 12.2.2, where it supports supplier selection and insurance provider lookups.

Underlying Base Objects

According to the ETRM metadata, OKX_INS_PROVIDER_V is defined over a single referenced base object:

• PO_VENDORS — documented as a VIEW in this release lineage (in earlier or alternative schema layouts it corresponds to the core supplier master).

The view performs a simple projection and filter over PO_VENDORS. No joins to party, site, or contact tables are present in the documented view text; the relationship is therefore one-to-one filtered projection. Every row returned by OKX_INS_PROVIDER_V corresponds to a row in PO_VENDORS where VENDOR_TYPE_LOOKUP_CODE = 'INSURER'. Because the metadata lists PO_VENDORS as a view rather than a base table, the true physical source is the interface layer beneath PO_VENDORS, but functionally OKX_INS_PROVIDER_V depends on that supplier-facing object.

Key Columns

The view exposes six columns, several of which are aliased to reflect party semantics rather than supplier semantics:

• PARTY_ID — sourced from VEN.VENDOR_ID. This is the unique identifier of the insurer supplier, re-cast as a trading community party identifier.
• ID2 — a literal '#' value. This placeholder distinguishes the party identifier namespace and is useful when concatenating identifiers.
• PARTY_NAME — sourced from VEN.VENDOR_NAME. The display name of the insurer.
• PARTY_NUMBER — sourced from VEN.SEGMENT1. The supplier number, presented as the party number.
• CATEGORY_CODE — sourced from VEN.VENDOR_TYPE_LOOKUP_CODE. For every row this resolves to 'INSURER', confirming the classification.
• INSURER_TYPE — a literal 'INS_PROVIDER' value. This constant tags each row as an insurance provider, supporting downstream filtering and type discrimination.

Common Use Cases and Queries

The view is typically used to populate insurance provider lists for certificates, policies, or agreements, and to integrate EBS supplier data into insurance subsystems. A simple listing query returns all insurers:

• SELECT party_id, party_name, party_number FROM apps.okx_ins_provider_v ORDER BY party_name;
• SELECT * FROM apps.okx_ins_provider_v WHERE party_number = :supplier_number; — to resolve a specific insurer by supplier number.
• Joining to other agreement or certificate tables on PARTY_ID when building insurer-provider lookups.

Because the filter and literal tags are hard-coded, the view is safe to query directly without additional predicates; every row is, by definition, an insurer. Any change to an insurer classification in PO_VENDORS automatically flows through the view.