Results for “okx_ins_provider_v”

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

Overview

OKX_INS_PROVIDER_V is a reporting view owned by the APPS schema within the OKX - Contracts Integration product module of Oracle E-Business Suite. Its stated purpose is to expose insurance providers as a clean, denormalized record set suitable for consumption by contracts integration processes and downstream reporting. The view is documented with valid status in both EBS 12.1.1 and 12.2.2, and appears in the E-Business Suite Technical Reference Manual (ETRM) as part of the OKX object inventory.

The view is not a physical table. It is a read-only projection over supplier master data, filtering the vendor population down to those trading partners whose vendor type indicates they are insurers. In this role it functions as a lightweight adapter: supplier records captured in Payables are reshaped into a party-oriented structure that contract-side logic can consume without directly querying the vendor tables. This separation allows the integration layer to depend on a stable interface even if the underlying vendor schema changes.

Underlying Base Objects

The view is defined over a single documented base object, PO_VENDORS, which in EBS is itself a view rather than a base table. It resolves against the supplier/vendor schema maintained by Oracle Payables and Purchasing. The dependency chain is therefore OKX_INS_PROVIDER_V → PO_VENDORS → underlying supplier entities such as AP_SUPPLIERS and related party tables.

The defining query applies a single predicate: only rows where VENDOR_TYPE_LOOKUP_CODE equals INSURER are returned. This is a lookup-code-based filter sourced from the standard vendor type lookup, meaning the view's result set is directly governed by how supplier records are classified in the supplier master. No joins, unions, or aggregations are present, so the cardinality of the view equals the number of active supplier records flagged as insurers, subject to the visibility rules inherent in PO_VENDORS.

Key Columns

• PARTY_ID — Sourced from VEN.VENDOR_ID. The supplier's primary identifier, exposed under a party-oriented alias to align with contracts integration naming conventions.
• ID2 — A static literal value of #. This placeholder column supports interface conventions where a secondary identifier key is expected but no distinct value exists for insurers.
• PARTY_NAME — Sourced from VEN.VENDOR_NAME. The display name of the insurance provider.
• PARTY_NUMBER — Sourced from VEN.SEGMENT1. The supplier number, the human-readable business key for the vendor record.
• CATEGORY_CODE — Sourced from VEN.VENDOR_TYPE_LOOKUP_CODE. Because of the view's filter, this column always evaluates to INSURER.
• INSURER_TYPE — A static literal value of INS_PROVIDER, used to positively tag every row as belonging to the insurance provider category.

Common Use Cases and Queries

Typical applications include populating insurance provider lists on contract templates, validating that a referenced insurer exists as a classified supplier, and driving integration extracts that feed external insurance or risk systems. Because two columns are constants, the view effectively serves as a filtered, renamed slice of supplier data rather than a transformation.

A straightforward lookup of all insurance providers is shown below.

• SELECT party_id, party_name, party_number FROM apps.okx_ins_provider_v ORDER BY party_name;
• SELECT party_number, party_name FROM apps.okx_ins_provider_v WHERE party_name LIKE :p_name;
• SELECT COUNT(*) FROM apps.okx_ins_provider_v;

Consumers should note that the view inherits the security and performance characteristics of PO_VENDORS; restricting queries by PARTY_NUMBER or PARTY_NAME is advisable when the supplier population is large.