Results for “oks_resources_hv”
22 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKS_RESOURCES_HV is a history view owned by the APPS schema within the OKS – Service Contracts module of Oracle E-Business Suite. It is documented in ETRM as a "History View for Coverage Resources" and carries a VALID status in both 12.1.1 and 12.2.2 environments. The view exists to expose the versioned resource assignments attached to service contract coverage, presenting them in a flattened, report-friendly form rather than requiring consumers to join the underlying history and party-role entities themselves.
Because the view exposes a MAJOR_VERSION column and is built over history-bearing synonyms, it is intended for audit and point-in-time reporting rather than transactional data entry. It plays a supporting role in reporting and integration: external extracts, custom concurrent programs, OBIEE/BI Publisher data models, and interfaces that need to resolve which vendor resources were associated with coverage across successive contract versions can select from this view directly.
Underlying Base Objects
The documented base objects referenced by OKS_RESOURCES_HV are FND_GLOBAL (PACKAGE), OKC_CONTACTS_H (SYNONYM), and OKC_K_PARTY_ROLES_HV (VIEW). The view text confirms this dependency: it joins OKC_K_PARTY_ROLES_HV (aliased KPROL) to OKC_CONTACTS_H (aliased CONTS) on CONTS.CPL_ID = KPROL.ID and CONTS.MAJOR_VERSION = KPROL.MAJOR_VERSION, filtered by KPROL.RLE_CODE = 'VENDOR'.
This relationship is significant for the user's search term okc_k_party_roles_hv. That view is the primary driver of OKS_RESOURCES_HV: it supplies the party-role history rows (CLE_ID, ID, MAJOR_VERSION, RLE_CODE) for the vendor role, while OKC_CONTACTS_H supplies the contact-level history records that carry the DNZ_CHR_ID and the RESOURCE_ID1/RESOURCE_ID2 pairs. FND_GLOBAL is referenced for session context resolution (for example, the effective user and responsibility used by multi-org and security predicates inherited through the base views). In practice, OKS_RESOURCES_HV should be understood as a filtered, coverage-oriented projection of OKC_K_PARTY_ROLES_HV restricted to vendor-role rows.
Key Columns
- ROW_ID — The ROWID of the underlying contact history row, useful for deduplication and direct row access.
- ID — Identifier of the party-role record (KPROL.ID), linking back to OKC_K_PARTY_ROLES_HV.
- OBJECT_VERSION_NUMBER — Optimistic locking/versioning attribute from the source record.
- MAJOR_VERSION — The contract version under which the resource assignment was effective; central to historical analysis.
- BUS_PROCESS_CLE_ID — The business-process CLE identifier (KPROL.CLE_ID) identifying the contract line/entity context.
- DNZ_CHR_ID — The contract header identifier, enabling joins to contract headers in reporting.
- RESOURCE_ID1 / RESOURCE_ID2 — The contact/party identifiers representing the vendor resource parties.
- RESOURCE_TYPE — CRO_CODE, classifying the resource role.
- JTOT_OBJECT1_CODE — The JTOT object type code describing the referenced object class.
Common Use Cases and Queries
Typical usage includes auditing vendor coverage resources across contract versions and feeding downstream extracts with the correct resource identity per version.
- List all vendor resources for a given contract header across versions:
SELECT id, major_version, resource_id1, resource_id2, resource_type FROM oks_resources_hv WHERE dnz_chr_id = :p_chr_id ORDER BY major_version; - Compare resources between two versions of a coverage to detect additions or removals: filter on
major_version IN (:v1, :v2)and reconcile byresource_id1. - Join to OKC_K_HEADERS_HV via
dnz_chr_idto report contract number alongside the vendor resource for audit reporting. - Resolve the individual contact behind a resource by joining
resource_id1to contact/party tables in the OKC/OKS model. - Restrict by
resource_typeto isolate a specific class of vendor resource for integration payloads.
Because the view is built exclusively for the 'VENDOR' role, queries seeking non-vendor party roles must access OKC_K_PARTY_ROLES_HV directly instead.
-
View: OKS_RESOURCES_HV 12.1.1
History View for Coverage Resources
APPS.OKS_RESOURCES_HV·↳ FND_GLOBAL·↳ OKC_CONTACTS_H·↳ OKC_K_PARTY_ROLES_HV·Explore OKS module →
-
View: OKS_RESOURCES_HV 12.2.2
History View for Coverage Resources
APPS.OKS_RESOURCES_HV·↳ FND_GLOBAL·↳ OKC_CONTACTS_H·↳ OKC_K_PARTY_ROLES_HV·Explore OKS module →
-
VIEW: APPS.OKS_RESOURCES_HV 12.2.2
-
VIEW: APPS.OKS_RESOURCES_HV 12.1.1
-
SYNONYM: APPS.OKC_CONTACTS_H 12.2.2
-
SYNONYM: APPS.OKC_CONTACTS_H 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - OKS Tables and Views 12.1.1
Stores the template set information.
-
eTRM - OKS Tables and Views 12.2.2
-
eTRM - OKC Tables and Views 12.1.1
Intersection entity between templates and rules.
-
12.2.2 DBA Data 12.2.2
-
eTRM - OKC Tables and Views 12.2.2
Intersection entity between rules and templates
-
12.1.1 DBA Data 12.1.1
-
eTRM - OKS Tables and Views 12.2.2
-
eTRM - OKS Tables and Views 12.1.1
Stores the template set information.
-
eTRM - OKC Tables and Views 12.1.1
Intersection entity between templates and rules.
-
eTRM - OKC Tables and Views 12.2.2
Intersection entity between rules and templates