Results for “ast_tasks_bali_v”

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

Overview

AST_TASKS_BALI_V is a reporting and integration view within the Oracle E-Business Suite TeleSales (AST) module. It consolidates task data from the JTF (CRM Foundation) task framework into a single flattened result set optimized for retrieval by TeleSales and related CRM applications. The view is defined with the FIRST_ROWS hint, indicating that it was designed for interactive query patterns where the application retrieves the first qualifying rows as quickly as possible rather than performing full-table aggregation over the entire task population.

AST_TASKS_BALI_V exposes task header information together with denormalized lookup values, including task type, status, priority, source object, owner, and parent task identifiers. This makes it suitable for list-of-values screens, task worklists, dashboard queries, and outbound integration feeds where the consumer requires readable lookup names rather than raw foreign key identifiers. In the ETRM documentation set for 12.1.1 and 12.2.2, the object is catalogued under the AST product with a note stating it is not implemented in the reference database, meaning the view is deployed conditionally based on licensed TeleSales functionality and applied patch levels.

Underlying Base Objects

The view text references the following documented base objects:

• JTF_TASKS_VL — the base task table (alias TASK), supplying the primary task attributes. A self-join on the same table (alias PARENT) resolves the parent task number.
• JTF_TASK_TYPES_VL — task type lookup, joined on TASK_TYPE_ID.
• JTF_TASK_STATUSES_VL — task status lookup, joined on TASK_STATUS_ID; also supplies the CLOSED_FLAG used to signal task completion.
• JTF_TASK_PRIORITIES_VL — priority lookup, joined on TASK_PRIORITY_ID.
• JTF_OBJECTS_VL — source object lookup, joined on the task's source object reference.
• FND_USER — the assigning user, joined via ASSIGNED_BY_ID to return USER_NAME.

The join predicates also filter out logically deleted rows by excluding records where DELETED_FLAG = 'Y', while retaining rows where the flag is null. The documented metadata lists no explicit base objects at the ETRM level; the relationships above are derived from the embedded view definition.

Key Columns

• TASK_ID / TASK_NUMBER / TASK_NAME — primary identifier, user-visible number, and descriptive name of the task.
• TASK_TYPE_ID / NAME, TASK_STATUS_ID / NAME, TASK_PRIORITY_ID / NAME — foreign keys paired with their decoded lookup names for direct display.
• CLOSED_FLAG — derived from the status record; 'Y' indicates a closed task.
• OWNER_ID / OWNER_TYPE_CODE / GET_OWNER(...) — the task owner, resolved to a display value through JTF_TASK_UTL.GET_OWNER.
• SOURCE_OBJECT_ID / SOURCE_OBJECT_NAME / SOURCE_OBJECT_TYPE_CODE / OBJECT.NAME — the business object the task relates to, such as an opportunity, lead, or contact.
• CUSTOMER_ID, CUST_ACCOUNT_ID, ADDRESS_ID — customer and location references used for TeleSales targeting.
• PARENT_TASK_ID / PARENT.TASK_NUMBER — hierarchical task relationships.
• PLANNED_START_DATE, PLANNED_END_DATE, SCHEDULED_* , ACTUAL_* — scheduling and effort tracking columns.
• PERCENTAGE_COMPLETE, DURATION, DURATION_UOM, PLANNED_EFFORT, ACTUAL_EFFORT — progress and workload metrics.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — flexfield-enabled descriptive attributes.
• ASSIGNED_BY_ID / USER_NAME — audit-style assignment reference to an FND user.
• ATTRIBUTE columns, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard Who columns and optimistic locking support.

Common Use Cases and Queries

Typical consumers use this view to build task worklists for TeleSales agents, resolve lookup names for reporting, and drill into parent/child task hierarchies.

Example: retrieve open, high-priority tasks with decoded lookups.

SELECT task_id, task_number, task_name, name_status, name_priority,
       owner_full_name, source_object_name, planned_start_date
FROM   ast_tasks_bali_v
WHERE  NVL(closed_flag,'N') = 'N'
  AND  priority_id = :p_priority;

Example: locate all child tasks belonging to a given parent.

SELECT task_id, task_number, parent_task_id, parent_task_number
FROM   ast_tasks_bali_v
WHERE  parent_task_id = :p_parent_id
  AND  NVL(deleted_flag,'N') = 'N';

Example: summarize open task counts by status and owner for dashboard reporting.

SELECT status_id, status_name, owner_id, COUNT(*)
FROM   ast_tasks_bali_v
WHERE  NVL(closed_flag,'N') = 'N'
GROUP  BY status_id, status_name, owner_id;

Because the view includes the FIRST_ROWS hint, queries should avoid unnecessary sorting or full scans where interactive responsiveness is required. Consumers should also honor the DELETED_FLAG filter and be aware that the view is not implemented in every environment, so existence checks against ALL_VIEWS are advisable before building dependent logic.