Results for “okl_cs_ih_activities_uv”

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

Overview

OKL_CS_IH_ACTIVITIES_UV is an APPS-owned, VALID database view within the OKL – Leasing and Finance Management product family of Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a unified, reporting-oriented projection of leasing interaction activity records: the actions, outcomes, results, and reasons captured against a contract-related customer interaction. The view exists primarily to expose the rich descriptive fields held in the interaction history (IH) tables in a form that is convenient for reporting, inquiry screens, and downstream integration, avoiding the need for consumers to reimplement the multi-table joins against JTF_IH_ACTIVITIES_VL and its siblings.

The view carries the "_UV" suffix convention commonly used in OKL for user-facing, denormalized views. Because it resolves codes to their meanings (for example OUTCOME_CODE alongside OUTCOME_MEANING) and surfaces human-readable descriptions, it is well suited to analytical reporting, Oracle Business Intelligence dataset definitions, and inquiry-based form or OAF customization. The appearance of reason_desc among its columns reflects the frequent user requirement to report not merely the reason code recorded on an activity but the corresponding descriptive text.

Underlying Base Objects

The documented base objects for this view are:

• JTF_IH_ACTIVITIES_VL (VIEW) – the driving source of activity rows, aliased ACT; supplies outcome, result, reason, resource, and timing attributes.
• JTF_IH_ACTION_ITEMS_VL (VIEW) – aliased AI; supplies the action item identity and short description.
• JTF_IH_INTERACTIONS_V (VIEW) – aliased INT; supplies the interaction header and the follow-up action.
• JTF_IH_OUTCOMES_VL (VIEW) – aliased OTC; resolves the outcome code to its short description (meaning).
• OKL_CS_INTERACTIONS_PARTY_UV (VIEW) – aliased CIP; links the interaction to the leasing party and contract context.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY (PACKAGES) – inherited through the underlying JTF/HR-based views and used for name resolution and security enforcement.

Internally the view joins CIP to INT on INTERACTION_ID, ACTIVITIES to INT on INTERACTION_ID, ACTIVITIES to ACTION_ITEMS on ACTION_ITEM_ID, and ACTIVITIES to OUTCOMES on OUTCOME_ID. The result set is ordered by END_DATE_TIME then START_DATE_TIME, presenting the most recent completed activities first among those with equal end times.

Key Columns

• CONTRACT_ID – the leasing document identifier (from ACT.DOC_ID), tying the activity to the contract.
• PARTY_ID, INTERACTION_ID – the customer party and the interaction within which the activity occurred.
• ACTION_ITEM_ID, ACTION_ITEM_DESC – the action item performed and its short description.
• OUTCOME_CODE, OUTCOME_DESC, OUTCOME_MEANING – the outcome code, its description, and the resolved outcome meaning.
• RESULT_CODE, RESULT_DESCRIPTION – the recorded result and its descriptive text.
• REASON_CODE, REASON_DESC – the coded reason for the outcome and, importantly for reporting, its descriptive text; this is the column commonly targeted by users searching on "reason_desc".
• RESOURCE_NAME, DURATION, START_DATE, END_DATE – the resource who performed the activity, its duration, and its start/end timestamps.
• FOLLOWUP_ACTION – the follow-up action recorded on the parent interaction.
• DOC_SOURCE – the source object name of the document (ACT.DOC_SOURCE_OBJECT_NAME).

Common Use Cases and Queries

Typical uses include contact-center and collections reporting on leasing interactions, activity trend analysis by outcome or reason, and integration feeds that require descriptions rather than codes. A representative query retrieving activities with their reasons for a given contract is:

• SELECT contract_id, interaction_id, action_item_desc, outcome_meaning, result_description, reason_desc, resource_name, start_date, end_date FROM apps.okl_cs_ih_activities_uv WHERE contract_id = :p_contract_id ORDER BY end_date DESC;
• SELECT reason_code, reason_desc, COUNT(*) FROM apps.okl_cs_ih_activities_uv GROUP BY reason_code, reason_desc ORDER BY 3 DESC;
• SELECT resource_name, SUM(duration) FROM apps.okl_cs_ih_activities_uv WHERE start_date BETWEEN :p_from AND :p_to GROUP BY resource_name;

Because the view orders by end date, callers requiring deterministic ordering within equal timestamps should add an explicit secondary sort. Queries should be schema-qualified against APPS, and access to party and resource data remains subject to the HR security packages referenced by the underlying objects.