Results for “okl_cs_interactions_party_uv”

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

Overview

OKL_CS_INTERACTIONS_PARTY_UV is a seeded Oracle E-Business Suite view owned by the APPS schema and validated in both 12.1.1 and 12.2.2. It belongs to the OKL product family — Oracle Leasing and Finance Management — and operates within the customer-service and interaction-tracking layer of that module. The suffix "UV" denotes a user view, indicating that it is intended as a reporting and integration access point rather than as a transactional entity. Its purpose is to present interaction records that are linked to a party (a person or organization) together with the assigned resource, so that the interaction data stored in the shared JTF interaction framework can be surfaced in leasing-specific reporting.

Because leasing and finance contracts are associated with parties through the TCA model, this view provides the bridge between the generic interaction history tables and the people/resource model. It is read-only and carries no package logic of its own; all enrichment is performed through joins to the person and resource structures.

Underlying Base Objects

The view is defined over the following documented objects:

• JTF_IH_INTERACTIONS (synonym) — the primary interaction fact table, supplying INTERACTION_ID and the handler, outcome, result, and reason references.
• JTF_RS_RESOURCE_EXTNS (synonym) — resource extension data, supplying RESOURCE_ID and the SOURCE_ID that maps to a person.
• PER_PEOPLE_F (view) — the effective-dated person record, supplying START_DATE and END_DATE and the join to the source person.
• FND_APPLICATION_VL (view) — the application/handler lookup, joined on APPLICATION_ID = HANDLER_ID.
• JTF_IH_OUTCOMES_TL, JTF_IH_RESULTS_TL, JTF_IH_REASONS_TL — translated lookup tables for outcome, result, and reason, joined with outer joins and filtered on USERENV('LANG').
• JTF_IH_ACTIVITIES_VL (view) — the activity definition lookup.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY (packages) — indirectly referenced through the person and resource views.

The joins are non-trivial: the view requires an active person record (TRUNC(SYSDATE) between effective dates), which means it returns only interactions whose associated person is currently effective.

Key Columns

• INTERACTION_ID — unique identifier of the interaction from JTF_IH_INTERACTIONS; the natural driving key.
• PARTY_ID — the party associated with the interaction, used to link to TCA party records.
• START_DATE / END_DATE — effective dates of the person record (PER_PEOPLE_F), not of the interaction itself.
• RESOURCE_ID — the resource that handled the interaction.
• RESOURCE_TYPE — a literal value 'RS_RESOURCE' identifying the resource origin.

Common Use Cases and Queries

This view is typically used to feed customer-service dashboards, extract interaction-by-party histories, or reconcile leasing interactions against resource assignment. A representative query:

SELECT interaction_id, party_id, resource_id, resource_type
FROM apps.okl_cs_interactions_party_uv
WHERE party_id = :p_party_id;

Because it filters on current person effectiveness, it should not be used for historical point-in-time reporting without a replacement query against the base tables. Reports requiring inactive resources or persons must query JTF_IH_INTERACTIONS directly.