Results for “delete_allowed_flag”

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

Overview

JTF_TASK_ALL_STATUSES_VL is an Oracle EBS multilingual (MLS) view owned by the APPS schema and belonging to the JTF – CRM Foundation product family. It presents the complete set of task and escalation statuses defined in the CRM Foundation, exposing both the base descriptive attributes and the translated name and description for the session language. The view is the standard read interface for status lookups, providing a single denormalized source that joins the base status definition table with its translation table so that consumers receive language-appropriate display text without performing the join themselves.

Because it carries the _VL suffix, the view is intended for presentation and reference-data queries rather than for direct DML. It is widely referenced by task management, escalation, and workflow components of JTF, and it is a common dependency for reports, concurrent programs, Discoverer workbooks, and integration extracts that must resolve a TASK_STATUS_ID to a human-readable status label. The searched attribute task_status_flag is exposed directly by this view, making it a central column for consumers that classify statuses by their functional role.

Underlying Base Objects

The view is defined over two base objects, both documented as synonyms in the APPS schema:

• JTF_TASK_STATUSES_B — the base table holding the non-translated status definition, including identity, audit, flag, attribute, and date-control columns.
• JTF_TASK_STATUSES_TL — the translation table supplying NAME and DESCRIPTION per language.

The join condition links B.TASK_STATUS_ID = T.TASK_STATUS_ID and restricts the translation to T.LANGUAGE = USERENV('LANG'), so only the row matching the current session language is returned. Every column from the base table is projected unaliased except ROWID, which is exposed as ROW_ID. NAME and DESCRIPTION are taken from the translation table; all remaining columns, including OBJECT_VERSION_NUMBER, USAGE, TASK_STATUS_FLAG, ASSIGNMENT_STATUS_FLAG, START_DATE_TYPE, and END_DATE_TYPE, come from the base table.

Key Columns

• TASK_STATUS_ID — primary identifier of the status; the join key between the base and translation rows and the value stored on task records.
• NAME / DESCRIPTION — the translated status label and its explanatory text for the session language.
• TASK_STATUS_FLAG — indicates whether the row is available for use as a task status.
• ASSIGNMENT_STATUS_FLAG — indicates whether the row may be used as an assignment status.
• CLOSED_FLAG — identifies statuses that represent a closed or terminal state.
• USAGE — distinguishes the functional usage context for which the status is intended.
• State indicator flags — ASSIGNED_FLAG, WORKING_FLAG, APPROVED_FLAG, COMPLETED_FLAG, CANCELLED_FLAG, REJECTED_FLAG, ACCEPTED_FLAG, and ON_HOLD_FLAG mark the lifecycle states this status represents.
• SEEDED_FLAG — marks Oracle-seeded statuses versus customer-defined entries.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective date range for the status definition.
• SCHEDULABLE_FLAG and DELETE_ALLOWED_FLAG — control scheduling eligibility and whether the status may be deleted.
• START_DATE_TYPE / END_DATE_TYPE — define how start and end dates are derived for tasks in the status.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard DFF flexfield columns.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

The view is most often used to populate status list-of-values, to translate stored status identifiers in task reports, and to filter statuses by functional purpose. A typical lookup returning the current-language label for active, non-seeded task statuses:

SELECT task_status_id, name, description
FROM   apps.jtf_task_all_statuses_vl
WHERE  task_status_flag = 'Y'
AND    (start_date_active IS NULL OR start_date_active <= SYSDATE)
AND    (end_date_active   IS NULL OR end_date_active   >= SYSDATE);

To resolve the status text on task records, the view is joined to the task entity on TASK_STATUS_ID. Because the view already filters by USERENV('LANG'), a join requires no additional language predicate:

SELECT t.task_id, s.name AS status_name
FROM   apps.jtf_tasks_b t, apps.jtf_task_all_statuses_vl s
WHERE  t.task_status_id = s.task_status_id;

Because the _VL suffix implies a multi-table, translated source, the view should be treated as read-only in all custom code. Any status maintenance must target the underlying base and translation tables through supported APIs.