Search Results object_function

Overview

OKL_CS_ACTIVITIES_UV is a PL/SQL view owned by the APPS schema within the OKL (Leasing and Finance Management) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates leasing-related customer service activities into a single denormalized reporting structure by joining the JTF Interaction History (IH) activity tables with customer, party, and task reference data. The "_UV" suffix conventionally denotes a user view exposed for inquiry, reporting, and integration purposes rather than for direct DML. In practice, the view serves as the runtime source for the OKL customer service Activities page and as the underlying query target for leases-related action tracking.

The user search term action_desc maps directly to the ACTION_DESC column exposed by this view. This column corresponds to the SHORT_DESCRIPTION from JTF_IH_ACTIONS_TL, joined through ACT.ACTION_ID and returned as ACTN.SHORT_DESCRIPTION. It provides the translatable, user-facing name of the action performed during an activity, distinguishing it from ACTION_ITEM_DESC (the short description of the related action item).

Underlying Base Objects

The view is defined over twelve synonym-referenced base objects, all resolved through the APPS schema:

• JTF_IH_ACTIVITIES — the driving table (alias ACT), holding each recorded activity and its identifiers, dates, durations, and source attributes.
• JTF_IH_INTERACTIONS — supplies the parent interaction linkage used to derive PARTY_ID.
• JTF_IH_MEDIA_ITEMS — source of DIRECTION and MEDIA_ITEM_TYPE, concatenated into MEDIADIRTYPE.
• JTF_IH_ACTIONS_TL — provides ACTION and ACTION_DESC (the action short description).
• JTF_IH_ACTION_ITEMS_TL — provides ACTION_ITEM and ACTION_ITEM_DESC.
• JTF_IH_OUTCOMES_TL, JTF_IH_RESULTS_TL, JTF_IH_REASONS_TL — lookup tables yielding OUTCOME_CODE/OUT_DESC, RESULT_CODE/RSL_DESC, and REASON_CODE/REA_DESC.
• HZ_PARTIES — supplies PARTY_NAME.
• HZ_CUST_ACCOUNTS — supplies ACCOUNT_NUMBER through CUST_ACCOUNT_ID.
• JTF_TASKS_B and JTF_OBJECTS_B — provide task and object-function context.

Because the view references synonym objects, it is portable across environments where the JTF and HZ schemas are installed, as is standard for EBS.

Key Columns

• ACTIVITY_ID, INTERACTION_ID, TASK_ID — primary activity keys.
• PARTY_ID, PARTY_NAME, ACCOUNT_NUMBER — customer identification.
• ACTION_ID, ACTION, ACTION_DESC — the action taken; ACTION_DESC is the searched term's target.
• ACTION_ITEM_ID, ACTION_ITEM, ACTION_ITEM_DESC — the action item reference.
• OUTCOME_ID, OUTCOME_CODE, RESULT_ID, RESULT_CODE, REASON_ID, REASON_CODE — disposition lookups.
• MEDIA_ID, DIRECTION, MEDIA_ITEM_TYPE, MEDIADIRTYPE — channel information.
• START_DATE_TIME, END_DATE_TIME, DURATION — timing metrics.
• OBJECT_ID, OBJECT_TYPE, OBJECT_FUNCTION, OBJECT_PARAMETERS — polymorphic linkage to the business object acted upon.
• DESCRIPTION, ROLE, SOURCE_CODE, SOURCE_CODE_ID, INTERACTION_ACTION_TYPE — descriptive and classification fields.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, OBJECT_VERSION_NUMBER — audit columns.

Common Use Cases and Queries

Typical usage covers activity history reporting, action outcome analysis, and integration extracts keyed to leasing contracts or parties. A representative query filtering on the searched attribute is shown below:

• Action description lookup: SELECT activity_id, action, action_desc, party_name, start_date_time FROM okl_cs_activities_uv WHERE action_desc IS NOT NULL AND start_date_time >= :p_from_date;
• Activity volume by action: SELECT action_desc, COUNT(*) FROM okl_cs_activities_uv GROUP BY action_desc ORDER BY 2 DESC;
• Outcome analysis by party: SELECT party_name, action_desc, outcome_code, result_code FROM okl_cs_activities_uv WHERE party_id = :p_party_id;
• Object-linked activity detail: SELECT object_function, object_id, activity_id, mediadirtype, duration FROM okl_cs_activities_uv WHERE object_type = :p_object_type;

These queries reflect the view's intended read-only reporting role and its dependence on the JTF and HZ base objects described above.