Results for “external_reference”

6 results




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

Overview

OKS_AUTH_SHOWALL_PROD_V is an Oracle E-Business Suite service contracts view owned by the APPS schema and defined within the OKS (Service Contracts) product family. It is classified as VALID in the ETRM repository for both release 12.1.1 and 12.2.2. The view presents a consolidated, authorization-oriented projection of customer products, contract lines, pricing attributes, and site addressing information. Its name reflects its function: it exposes the full set of authorized products ("SHOWALL") associated with service contract entitlements, so that downstream reporting, service authorization, and integration routines can retrieve contract-covered instances without repeatedly joining the OKC and CSI base tables directly.

The view is principally consumed by service contract authoring pages, entitlement validation logic, and customer-facing reporting on installed base coverage. Note that it is distinct from OKX_PARTY_SITES_V, which the user query referenced; OKX_PARTY_SITES_V belongs to the OKX (Trading Community) schema and serves party-site purposes. OKS_AUTH_SHOWALL_PROD_V instead returns contract-linked customer products, with the party site surfaced only through a descriptive ADDRESS column.

Underlying Base Objects

The view is built over a broad set of documented objects spanning several EBS schemas:

The view text references aliases such as KLIN (contract lines), KHDR (contract headers), CII (CSI item instances), PSITE (party site), CIPA (pricing attributes), OOL (order lines), CST (CSI system), and ACCT (customer account), confirming these join paths.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting all contract-authorized products for a customer, validating whether a serialized instance is covered, and feeding entitlement checks in field service or depot repair integrations.

SELECT customer_name, product_name, current_serial_number, address, net_amount
FROM   apps.oks_auth_showall_prod_v
WHERE  customer_name = :p_customer
AND    SYSDATE BETWEEN start_date AND end_date;

A second common pattern retrieves pricing attribute context for a specific instance:

SELECT customer_product_id, reference_number, pricing_attribute1, pricing_attribute5
FROM   apps.oks_auth_showall_prod_v
WHERE  reference_number = :p_instance_number;

Because the view joins many base objects, queries should be filtered by contract, customer, or instance to avoid full scans.