Search Results oks_resources_v




Overview
Explore in AI Chat

Overview

OKS_RESOURCES_V is a VALID Oracle E-Business Suite view owned by the APPS schema within the OKS – Service Contracts product family. Its documented purpose is to present the preferred resources associated with Service Contracts coverages, consolidating resource assignment data drawn from the Service Contracts party-role and contact tables into a single queryable structure. Because it is a view rather than a base table, it does not store data; instead it derives its result set dynamically at query time from the underlying OKS contact infrastructure.

In EBS 12.1.1 and 12.2.2, the view functions principally as a reporting and integration surface. It exposes resource assignment information—such as resource identity, resource type, resource class, and the associated business process and contract identifiers—in a denormalized form that is convenient for reports, extracts, and inbound/outbound interfaces. The resource_class column is a common search target, as it enables filtering or grouping of resources by their classification within a contract context.

Underlying Base Objects

The view is defined over two referenced base objects, both exposed to APPS through synonyms:

  • OKC_CONTACTS (aliased as CONTS) – supplies the contact and resource rows, contributing the resource identifiers, resource type, resource class, primary flag, contract identifier, and the internal ID used for the join.
  • OKC_K_PARTY_ROLES_B (aliased as KPROL) – supplies party-role data, contributing the associated business process CLE identifier through KPROL.CLE_ID.

The two objects are joined on the condition CONTS.CPL_ID = KPROL.ID, which links each contact record to its corresponding party-role record. This relationship ensures that only contacts tied to a valid party role are returned, effectively scoping the view to genuine resource assignments rather than orphaned contact rows.

Key Columns

The view exposes the following documented columns:

  • ROW_ID – the ROWID of the underlying CONTS record, useful for row-level identification.
  • ID – the primary identifier of the contact/resource row.
  • OBJECT_VERSION_NUMBER – the optimistic locking version number, relevant for programmatic updates.
  • BUS_PROCESS_CLE_ID – the business process identifier derived from OKC_K_PARTY_ROLES_B, linking the resource to its business context.
  • DNZ_CHR_ID – the contract header identifier, tying the resource to a specific contract.
  • RESOURCE_ID1 / RESOURCE_ID2 – the two-part object identifier resolving the resource to its source entity.
  • RESOURCE_TYPE – the CRO_CODE classifying the kind of resource.
  • JTOT_OBJECT1_CODE – the object type code for the first resource identifier.
  • PRIMARY_YN – indicates whether the resource is the primary resource for the coverage.
  • RESOURCE_CLASS – the classification of the resource, frequently used for filtering and reporting.

Common Use Cases and Queries

Typical scenarios include reporting preferred resources per contract, filtering resources by class, and integrating resource assignments into external systems. A representative query filtering on the searched attribute is:

  • SELECT resource_id1, resource_id2, resource_type, resource_class, primary_yn, dnz_chr_id FROM oks_resources_v WHERE resource_class = :p_class;
  • SELECT dnz_chr_id, resource_id1, primary_yn FROM oks_resources_v WHERE dnz_chr_id = :p_contract_id AND primary_yn = 'Y';

Because the view is read-oriented and built on the _B (base) table of party roles, it reflects current, untranslated resource data, making it suitable for operational reporting where the latest assignment state is required.