Results for “adjustment_time_uom”

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

Overview

JTF_TASK_DEPENDS is a CRM Foundation (JTF) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores dependency relationships between tasks. Each row records that one task depends upon another task, enabling scheduling logic, predecessor/successor sequencing, and constraint enforcement within the Task Manager and related CRM task flows. The table is owned by the JTF schema and holds a status of VALID in the ETRM repository for release 12.2.2.

Within the documented physical schema, the table contains 31 columns and is uniquely indexed by JTF_TASK_DEPENDS_U1 on DEPENDENCY_ID, which also serves as primary key via JTF_TASK_DEPENDENCIES_PK (and alternatively JTF_TASK_DEPENDS_PK). From a Data Vault modeling perspective, the mined FK structure suggests a link classification: the table resolves a many-to-many association between a task and the task it depends upon, rather than acting as a descriptive hub or satellite. It also carries descriptive and audit attributes that would typically reside in a satellite in a strict Data Vault design.

Key Information Stored

The most significant columns are:

• DEPENDENCY_ID — Surrogate primary key and the unique business-key candidate (JTF_TASK_DEPENDS_U1). Uniquely identifies each dependency row.
• TASK_ID — The dependent task; foreign key to JTF_TASKS_B and JTF_TASK_TEMPLATES_B.
• DEPENDENT_ON_TASK_ID — The predecessor task that the dependent task relies upon; also FK to JTF_TASKS_B and JTF_TASK_TEMPLATES_B.
• DEPENDENCY_TYPE_CODE — Classifies the nature of the dependency (for example, finish-to-start semantics).
• TEMPLATE_FLAG — Indicates whether the row applies to a task template rather than a live task instance, aligning with the dual FK targets.
• ADJUSTMENT_TIME and ADJUSTMENT_TIME_UOM — Optional offset and unit of measure applied against the dependency.
• VALIDATED_FLAG — Records whether the dependency has passed validation checks.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-org/security-group data partitioning.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the ORM layer.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield (DFF) columns for customer-specific extensions.

The key distinction is that DEPENDENCY_ID is the surrogate key, while the operational business meaning is carried by the TASK_ID / DEPENDENT_ON_TASK_ID pair together with DEPENDENCY_TYPE_CODE.

Common Use Cases and Queries

Typical scenarios include reconstructing task sequencing for a project or service request, validating that no circular dependencies exist, and reporting predecessor/successor chains for scheduling dashboards.

To list all dependencies for a given task:

• SELECT d.dependency_id, d.task_id, d.dependent_on_task_id, d.dependency_type_code, d.validated_flag FROM jtf.jtf_task_depends d WHERE d.task_id = :task_id;

To find all predecessors constraining a task:

• SELECT t.task_id, t.task_name FROM jtf.jtf_tasks_b t, jtf.jtf_task_depends d WHERE d.dependent_on_task_id = t.task_id AND d.task_id = :task_id;

To isolate template-level dependencies from live task dependencies, filter on TEMPLATE_FLAG. Reporting queries frequently join to JTF_TASKS_B to resolve task names and to FND_SECURITY_GROUPS to enforce row-level security. Audit and change-tracking reports leverage OBJECT_VERSION_NUMBER and the LAST_UPDATE columns.

Related Objects

• JTF_TASKS_B — Referenced twice: JTF_TASK_DEPENDS.TASK_ID → JTF_TASKS_B and JTF_TASK_DEPENDS.DEPENDENT_ON_TASK_ID → JTF_TASKS_B. The primary source for task definitions.
• JTF_TASK_TEMPLATES_B — Also referenced by both TASK_ID and DEPENDENT_ON_TASK_ID, supporting template-derived dependencies.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for data security partitioning.
• BIS_OBJECTS — References JTF_TASK_DEPENDS via DEPENDENCY_ID, linking tasks into the BIS/CRM object model.
• JTF_TASK_DEPENDENCIES_PK / JTF_TASK_DEPENDS_PK / JTF_TASK_DEPENDS_U1 — Primary key and unique index constraints governing the table.