Results for “resource_req_id”

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

Overview

JTF_TASK_RSC_REQS is a CRM Foundation (JTF) transaction table that stores the resource requirements associated with a task. In Oracle E-Business Suite 12.1.1 and 12.2.2, tasks are the atomic units of work managed by the Task Manager and resource management facilities of CRM Foundation, and this table records what resources a given task demands — for example a specific number of units of a particular resource type. The table is owned by the JTF schema and is reported as VALID in the ETRM data dictionary.

The object carries a documented Data Vault classification of link (a heuristic derived from its foreign-key structure). As a modeling suggestion, this indicates the table behaves primarily as an associative entity: it resolves relationships between a task (or task template / task type) and a resource type, with a small number of descriptive attributes such as required units and an enabled flag. It is not a standalone hub of business identity, nor does it carry the wide, historized attribute payload typical of a satellite.

Key Information Stored

The documented physical schema exposes 30 columns. The most significant are:

• RESOURCE_REQ_ID — the surrogate primary key, enforced by JTF_TASK_RESOURCE_REQS_PK and also by unique index JTF_TASK_RSC_REQS_U1. This is the single documented unique index and therefore the only business-key candidate identified in the metadata.
• TASK_ID — foreign key to JTF_TASKS_B, identifying the task for which the resource requirement applies.
• TASK_TEMPLATE_ID — foreign key to JTF_TASK_TEMPLATES_B, allowing requirements to be defined on reusable task templates rather than individual tasks.
• TASK_TYPE_ID — foreign key to JTF_TASK_TYPES_B, allowing requirements to be defined at the task-type level.
• RESOURCE_TYPE_CODE — foreign key to JTF_OBJECTS_B, identifying the kind of resource required.
• REQUIRED_UNITS — the quantity of the resource required by the task.
• ENABLED_FLAG — controls whether the requirement is active.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org / data-security partitioning.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE1 … ATTRIBUTE15, ATTRIBUTE_CATEGORY — the standard DFF (descriptive flexfield) columns for customer-specific extension.

The presence of TASK_ID, TASK_TEMPLATE_ID, and TASK_TYPE_ID together indicates the table can hold requirements sourced from three distinct levels of task definition, which is why the metadata classifies it as a link rather than a simple child satellite.

Common Use Cases and Queries

Typical reporting scenarios include: listing all resource requirements for a specific task, auditing template-level requirements, and determining total resource demand by resource type. Sample patterns:

• Requirements for a task: SELECT resource_type_code, required_units FROM jtf_task_rsc_reqs WHERE task_id = :task_id AND enabled_flag = 'Y';
• Template-based requirements: SELECT * FROM jtf_task_rsc_reqs WHERE task_template_id = :tmpl_id;
• Demand by resource type: SELECT resource_type_code, SUM(required_units) FROM jtf_task_rsc_reqs GROUP BY resource_type_code;
• Join to tasks and objects: SELECT t.task_id, o.object_name, r.required_units FROM jtf_task_rsc_reqs r, jtf_tasks_b t, jtf_objects_b o WHERE r.task_id = t.task_id AND r.resource_type_code = o.object_code;

Security-group-aware queries should filter on SECURITY_GROUP_ID in Multi-Org or CRM security environments.

Related Objects

• JTF_TASKS_B — parent task table; joined on TASK_ID.
• JTF_TASK_TEMPLATES_B — template definitions; joined on TASK_TEMPLATE_ID.
• JTF_TASK_TYPES_B — task type definitions; joined on TASK_TYPE_ID.
• JTF_OBJECTS_B — resource type registry; joined on RESOURCE_TYPE_CODE.
• FND_SECURITY_GROUPS — security partitioning; joined on SECURITY_GROUP_ID.

These five relationships account for all documented foreign keys on JTF_TASK_RSC_REQS, confirming the link classification and its central role in CRM Foundation task resource planning.