Results for “rs_resource”

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

Overview

OKL_CS_INTERACTIONS_PARTY_UV is an APPS-owned database view in Oracle E-Business Suite, documented under ETRM 12.2.2 and applicable to 12.1.1 as well. It exposes the relationship between interaction records captured in the Interaction History (JTF_IH) schema and the parties or resources associated with those interactions in the Oracle Knowledge Lite / Contracts (OKL) service context. The "UV" suffix denotes a user-facing validation or uniqueness-oriented view designed primarily for LOV (List of Values) population and reporting rather than transactional DML.

The central purpose of the view is to return every interaction together with its owning party and the resource that handled it, while filtering to resources whose underlying person record is effective as of the current system date. This makes it a convenient single source for interaction-party-resource lookups in service request, tele-service, and contract lifecycle reporting. The literal column 'RS_RESOURCE' is emitted as a constant resource_type, which aligns with Resource Manager conventions and allows downstream consumers to treat the row as a resource-type interaction uniformly.

Underlying Base Objects

The view is defined over a join of eight documented objects:

• JTF_IH_INTERACTIONS (synonym) — the driving table, aliased IHI. Provides interaction_id, party_id, resource_id, outcome_id, result_id, reason_id, and handler_id.
• JTF_RS_RESOURCE_EXTNS (synonym) — resolved as RES; supplies resource_id and SOURCE_ID, which links to the person record.
• PER_PEOPLE_F (view) — the date-tracked person view, joined via RES.SOURCE_ID = P.PERSON_ID and constrained to TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date. Supplies start_date and end_date.
• FND_APPLICATION_VL (view) — joined by APPLICATION_ID = IHI.HANDLER_ID, ensuring the handler is a valid application.
• JTF_IH_OUTCOMES_TL, JTF_IH_RESULTS_TL, JTF_IH_REASONS_TL (synonyms) — language-enabled lookup tables joined with outer joins (+) and filtered by USERENV('LANG').
• JTF_IH_ACTIVITIES_VL (view) — referenced in the FROM clause for lookup validation of activity context.

Indirect dependencies include HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages, which underpin PER_PEOPLE_F and enforce person-level security and name resolution.

Key Columns

• interaction_id — primary identifier of the interaction row from JTF_IH_INTERACTIONS.
• party_id — the party (customer, organization, or contact) associated with the interaction.
• start_date / end_date — the effective date range of the person record driving the resource, exposed for date-aware filtering.
• resource_id — the resource that performed or owned the interaction, sourced from JTF_RS_RESOURCE_EXTNS.
• resource_type — a constant literal 'RS_RESOURCE', identifying the row as resource-typed for uniform downstream processing.

Common Use Cases and Queries

This view is typically queried to enumerate interactions for a given party or resource, or to feed LOVs. The constant resource_type simplifies union operations across heterogeneous interaction sources. A representative query retrieving interactions for a specific resource is:

SELECT interaction_id, party_id, resource_id, start_date, end_date FROM apps.okl_cs_interactions_party_uv WHERE resource_id = :p_resource_id ORDER BY interaction_id;

Because the view applies TRUNC(SYSDATE) and language filters internally, results are automatically limited to currently effective persons and the session language, so consumers need not reapply those predicates. For reporting by party, filtering on party_id returns all qualifying resource interactions, supporting service-history and contract-service analyses where the literal resource_type column is used to segregate resource-driven records.