Search Results resource_id2




Overview
Explore in AI Chat

Overview

APPS.OKS_RESOURCES_V is a reporting view in Oracle E-Business Suite that exposes service resource information drawn from the contact and party-role tables of the Contracts (OKC / Service Contracts) data model. Within the ETRM (Enterprise Technical Reference Manual) schema documentation for releases 12.1.1 and 12.2.2, the view is catalogued under the APPS schema and is defined as a simple join between contract contact records and their associated party roles. It presents a denormalised, query-friendly projection of resource data — including the resource identifier, resource type, class, and primary flag — without requiring the calling application or report to reconstruct the join between the contact and party-role entities manually.

The view is primarily consumed by Oracle Service Contracts and related ETRM functionality, where service resources (such as technicians, engineers, or vendors) must be resolved against contract line and coverage records. Because it exposes the surrogate keys used by the underlying Contracts tables, it is equally useful in integration and data-migration contexts, where external systems must map EBS resource identifiers to legacy or third-party identifiers.

Underlying Base Objects

The documented base objects referenced by the view are OKC_CONTACTS and OKC_K_PARTY_ROLES_B, both exposed to the APPS schema through public synonyms. OKC_CONTACTS stores the contact (resource) records associated with a contract, including the surrogate identifiers and the resource class and type attributes. OKC_K_PARTY_ROLES_B holds the party-role assignments for a contract and provides the business-process context through its CLE_ID column.

The view joins the two in a single equijoin predicate, conts.cpl_id = kprol.id, meaning each contact row is linked to the party-role row whose primary key matches the contact's CPL_ID foreign key. The view is therefore read-only and inherits the ROWID of OKC_CONTACTS as its ROW_ID column, confirming that OKC_CONTACTS is the driving table for row identity purposes.

Key Columns

  • ROW_ID — the ROWID of the underlying OKC_CONTACTS row, useful for direct DML targeting or row-level auditing.
  • ID — the contact's primary key (OKC_CONTACTS.ID), the unique resource record identifier.
  • OBJECT_VERSION_NUMBER — optimistic locking column carried through from OKC_CONTACTS for concurrency control in OAF-based pages.
  • BUS_PROCESS_CLE_ID — the contract line (CLE_ID) from OKC_K_PARTY_ROLES_B, identifying the business process to which the resource is attached.
  • DNZ_CHR_ID — the contract header identifier, used to scope resources to a specific contract.
  • RESOURCE_ID1 / RESOURCE_ID2 — the two-part resource identifier (OBJECT1_ID1 and OBJECT1_ID2); these are the columns most frequently searched for as "resource_id1" by developers and report authors.
  • RESOURCE_TYPE — the CRO_CODE value, classifying the resource type.
  • JTOT_OBJECT1_CODE — the JTOT object code that qualifies how the resource identifier is interpreted.
  • PRIMARY_YN — indicates whether the resource is the primary party role on the contract.
  • RESOURCE_CLASS — the resource class, distinguishing categories such as employee or organisation.

Common Use Cases and Queries

Typical usage centres on resolving resource identifiers for a given contract or party role, validating primary resource assignments, and feeding resource data into service-contract reports.

  • Retrieve all resources attached to a specific contract:
    SELECT resource_id1, resource_id2, resource_type, resource_class, primary_yn FROM apps.oks_resources_v WHERE dnz_chr_id = :contract_id;
  • Find a resource by its identifier:
    SELECT id, dnz_chr_id, bus_process_cle_id, primary_yn FROM apps.oks_resources_v WHERE resource_id1 = :resource_id1;
  • Identify primary resources only:
    SELECT resource_id1, resource_id2, resource_class FROM apps.oks_resources_v WHERE primary_yn = 'Y' AND bus_process_cle_id = :cle_id;
  • Join to contract line tables for reporting:
    SELECT v.resource_id1, v.resource_class, l.line_number FROM apps.oks_resources_v v, apps.okc_k_lines_b l WHERE v.bus_process_cle_id = l.cle_id;

Because the view exposes only the joined projection and no row-level security predicate of its own, callers should apply the appropriate contract-header or business-process filter to ensure correct scoping and performance.