Search Results doc_source_object_name

Overview

AST_ACTIVITIES_V is a TeleSales (AST) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents interaction activities captured by the Interaction History (JTF_IH) framework, denormalized with the surrounding interaction, party, and lookup context required for business reporting. Each row in the view represents a single activity performed within a customer interaction, such as a call outcome, a logged action item, or a task assignment.

The view's principal value is translation-aware and denormalized output. Rather than requiring callers to join translation tables and decode identifiers, AST_ACTIVITIES_V resolves outcome, result, reason, action item, and action descriptions into a single flat structure, while carrying the language constraint USERENV('LANG'). This makes it suitable for TeleSales agent dashboards, interaction history reports, call center analytics, and outbound integration extracts where readable activity context is required.

The user search term action_desc corresponds directly to a projected column of this view. ACTION_DESC is the short description of the action recorded on the activity, sourced from JTF_IH_ACTIONS_TL. It is one of several description columns (OUT_DESC, RSL_DESC, REA_DESC, ACTION_ITEM_DESC) surfaced for the same purpose.

Underlying Base Objects

The view's FROM clause references twelve objects, all exposed as APPS synonyms. The driving table is JTF_IH_ACTIVITIES (alias ACT), which supplies the activity identifier, interaction link, media reference, start and end timestamps, duration, description, role, task and document references, object context, source information, and the outcome, result, reason, action item, and action foreign keys. JTF_IH_INTERACTIONS (INT) is joined on INTERACTION_ID and supplies the PARTY_ID that links the activity to its customer.

HZ_PARTIES (HZ) and HZ_CUST_ACCOUNTS (HZCA) provide PARTY_NAME and ACCOUNT_NUMBER. The HZ_CUST_ACCOUNTS join is outer (+), so activities without a customer account still appear. JTF_IH_MEDIA_ITEMS (MEDIA) supplies DIRECTION and MEDIA_ITEM_TYPE, also joined outer. JTF_TASKS_B (TSK) is joined on TASK_ID with no outer marker, and JTF_OBJECTS_B (OBJ) supplies OBJECT_FUNCTION and OBJECT_PARAMETERS for the referenced business object.

Five translation tables are used with the language constraint: JTF_IH_OUTCOMES_TL, JTF_IH_RESULTS_TL, JTF_IH_REASONS_TL, and JTF_IH_ACTIONS_TL are outer-joined, while JTF_IH_ACTION_ITEMS_TL carries an inner language condition (no outer marker on the language predicate in the documented text). This asymmetry means an activity whose action item has no row in the current language may be excluded from the result set.

Key Columns

• ACTIVITY_ID, INTERACTION_ID, PARTY_ID — the activity, its parent interaction, and the associated party.
• PARTY_NAME, ACCOUNT_NUMBER — customer name and account number for reporting context.
• ACTION_ID, ACTION, ACTION_DESC — the action code and its translated short description; ACTION_DESC is the column most commonly searched for.
• ACTION_ITEM_ID, ACTION_ITEM, ACTION_ITEM_DESC — action item code and description; concatenated with ACTION into the derived ACTITM column.
• OUTCOME_ID, OUTCOME_CODE, OUT_DESC — call outcome and its description.
• RESULT_ID, RESULT_CODE, RSL_DESC — result and its description.
• REASON_ID, REASON_CODE, REA_DESC — reason and its description.
• START_DATE_TIME, END_DATE_TIME, DURATION — activity timing, supporting duration and throughput analysis.
• MEDIA_ID, DIRECTION, MEDIA_ITEM_TYPE, MEDIADIRTYPE — media used and the derived direction-plus-type concatenation.
• TASK_ID, DOC_ID, DOC_REF, DOC_SOURCE_OBJECT_NAME — task and document associations.
• OBJECT_ID, OBJECT_TYPE, OBJECT_FUNCTION, OBJECT_PARAMETERS — the business object the activity relates to.
• SOURCE_CODE, SOURCE_CODE_ID, INTERACTION_ACTION_TYPE — origin and classification of the activity.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, ROW_ID — standard WHO columns and the ROWID-based ROW_ID, which supports update-through-view scenarios.

Common Use Cases and Queries

Typical uses include agent activity reports, outcome analysis by media type, and extracts of recent customer contacts for downstream systems. Because the view already resolves descriptions in the session language, most queries need no additional joins.

Activities showing action descriptions for a party:

SELECT ACTIVITY_ID, PARTY_NAME, ACTION, ACTION_DESC,
       OUTCOME_CODE, OUT_DESC, START_DATE_TIME, DURATION
FROM   APPS.AST_ACTIVITIES_V
WHERE  PARTY_ID = :p_party_id
ORDER  BY START_DATE_TIME DESC;

Filtering specifically on the searched column:

SELECT ACTIVITY_ID, ACTION_DESC, ACTION_ITEM_DESC,
       OUT_DESC, RSL_DESC, REA_DESC
FROM   APPS.AST_ACTIVITIES_V
WHERE  ACTION_DESC IS NOT NULL
AND    START_DATE_TIME >= :p_from_date;

Volume by media and outcome:

SELECT MEDIADIRTYPE, OUTCOME_CODE, OUT_DESC,
       COUNT(*) activity_count, SUM(DURATION) total_duration
FROM   APPS.AST_ACTIVITIES_V
WHERE  START_DATE_TIME BETWEEN :p_from AND :p_to
GROUP  BY MEDIADIRTYPE, OUTCOME_CODE, OUT_DESC
ORDER  BY activity_count DESC;

When tuning these queries, note that JTF_IH_ACTIVITY_ITEMS_TL joins as inner on language and that the outer-joined HZ_CUST_ACCOUNTS predicate returns activities without a customer account. Restricting on PARTY_ID, INTERACTION_ID, or START_DATE_TIME generally yields the most efficient plans, since those predicate columns map directly to the JTF_IH_INTERACTIONS and JTF_IH_ACTIVITIES indexes.