Results for “ast_tasks_v”

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

Overview

AST_TASKS_V is a consolidated reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the TeleSales (AST) product family. It exposes task and activity records maintained by the Oracle Common Task framework (JTF), presenting them in a denormalized form that is convenient for reporting, concurrent programs, personalizations, and integration interfaces. In EBS 12.1.1 and 12.2.2 the view is registered as VALID and is available to any responsibility with execute privilege on the underlying objects.

The view's principal value is that it resolves foreign keys into human-readable names. Task type, status, priority, owner, and source object references are translated through their respective translation views and utility functions, so consumers do not need to join repeatedly to JTF reference tables. TeleSales agents, sales managers, and telemarketing supervisors typically encounter it indirectly through OA Framework pages and CRM dashboards; developers encounter it directly when building custom reports.

Underlying Base Objects

AST_TASKS_V is defined over the following documented objects:

• JTF_TASKS_VL (view) — the primary source of task rows; supplies identity, classification, ownership, scheduling, effort, and the ATTRIBUTE1–15 DFF columns.
• JTF_TASK_TYPES_TL (synonym) — provides the translatable task type name.
• JTF_TASK_STATUSES_VL (view) — supplies status name and the CLOSED_FLAG, CANCELLED_FLAG, COMPLETED_FLAG, and REJECTED_FLAG indicators.
• JTF_TASK_PRIORITIES_TL (synonym) — supplies the priority name.
• JTF_OBJECTS_VL (view) — joined twice, once for the source object and once for the owner object, supplying their display names.
• FND_USER (synonym) — resolves ASSIGNED_BY_ID to the assigning user's USER_NAME.
• JTF_TASK_UTL (package) — supplies JTF_TASK_UTL.GET_OWNER, which resolves the polymorphic OWNER_TYPE_CODE/OWNER_ID pair into a displayable owner string.

The defining query filters out soft-deleted rows via the predicate on DELETED_FLAG, so the view returns only live tasks. Two columns in the select list are defined as NULL placeholders, and the remaining joins map surrogate identifiers to descriptive values.

Key Columns

• TASK_ID, TASK_NUMBER, TASK_NAME, DESCRIPTION — task identity and descriptive text.
• TASK_TYPE_ID / NAME, TASK_STATUS_ID / NAME, TASK_PRIORITY_ID / NAME — classification lookups with resolved names.
• OWNER_ID, OWNER_TYPE_CODE, OWNER_TERRITORY_ID — ownership assignment; GET_OWNER returns the resolved owner label.
• SOURCE_OBJECT_ID, SOURCE_OBJECT_NAME, SOURCE_OBJECT_TYPE_CODE — the originating business object (for example, a lead, opportunity, or customer).
• PLANNED_START_DATE, PLANNED_END_DATE, SCHEDULED_START_DATE, SCHEDULED_END_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE — the scheduling timeline.
• ALARM_START, ALARM_START_UOM, NOTIFICATION_PERIOD, NOTIFICATION_PERIOD_UOM — alarm and reminder configuration. ALARM_START defines when the task alarm fires, expressed in the unit given by ALARM_START_UOM; it is frequently used to drive reminder notifications to the owner.
• DURATION / DURATION_UOM, PLANNED_EFFORT / UOM, ACTUAL_EFFORT / UOM, PERCENTAGE_COMPLETE — effort tracking metrics.
• PRIVATE_FLAG, PUBLISH_FLAG, NOTIFICATION_FLAG, DELETED_FLAG — visibility and lifecycle controls.
• CUSTOMER_ID, CUST_ACCOUNT_ID, ADDRESS_ID — CRM party context.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield storage.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — concurrency and audit columns.

Common Use Cases and Queries

Typical scenarios include open-task lists by owner, overdue task reporting, and alarm-driven reminder extracts. A query listing tasks with their alarm configuration and owner:

SELECT task_number, task_name, status_name, priority_name,
       JTF_TASK_UTL.GET_OWNER(owner_type_code, owner_id) owner,
       alarm_start, alarm_start_uom, planned_start_date
FROM   apps.ast_tasks_v
WHERE  NVL(completed_flag,'N') = 'N'
ORDER BY planned_start_date;

To identify tasks whose alarms fall within an upcoming window for notification processing, constrain ALARM_START with the appropriate unit conversion applied in the surrounding report logic. For lead- or opportunity-based analysis, filter on SOURCE_OBJECT_TYPE_CODE and join SOURCE_OBJECT_ID to the corresponding CRM entity. Because the view already excludes deleted rows and resolves the major lookups, it is well suited to ad hoc reporting and to feed interfaces that must publish task activity to external systems.