Results for “csp_product_tasks”

50+ results




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

Overview

CSP_PRODUCT_TASKS is a transactional configuration table within the Oracle E-Business Suite Spares Management (CSP) module. It serves as the association layer that binds a product or inventory item to a reusable service or maintenance task template, effectively defining which tasks apply to a given product and how those tasks are triggered. In the spares and field service domain, this table is the mechanism by which organizations declare that a specific part or product requires a defined sequence of tasks—whether automatically scheduled or manually initiated—during depot repair, field service, or preventive maintenance workflows.

From a data modeling perspective, the ETRM metadata classifies CSP_PRODUCT_TASKS as satellite-leaning under the heuristic Data Vault classification. This suggests the table behaves primarily as a descriptive satellite that carries attributes and history around a defined business key pair (product and task template), rather than acting as a pure hub or link. The uniquely constrained combination of PRODUCT_ID and TASK_TEMPLATE_ID reinforces this interpretation, indicating that the table is a controlled, keyed store of task-to-product relationships rather than an open-ended associative structure.

Key Information Stored

The table contains 28 documented columns. The most significant are:

Notably, the business key is distributed: the surrogate PRODUCT_TASK_ID provides technical identity, while PRODUCT_ID plus TASK_TEMPLATE_ID provides the meaningful business identity. This split is characteristic of satellite structures in which technical and natural keys diverge.

Common Use Cases and Queries

CSP_PRODUCT_TASKS is most commonly queried when configuring or auditing service task assignments for products. Typical patterns include verifying which tasks are tied to a product, identifying automatically triggered tasks, and evaluating task utilization via ACTUAL_TIMES_USED.

A representative join resolves the task template details:

SELECT cpt.product_task_id, cpt.product_id, jttb.name, cpt.auto_manual
FROM   csp.csp_product_tasks cpt,
       jtf.jtf_task_templates_b jttb
WHERE  cpt.task_template_id = jttb.task_template_id
AND    cpt.product_id = :product_id;

Reporting use cases include generating product-task matrices for engineering change review, analyzing which tasks are most frequently executed, and reconciling task configuration against security group assignments. The AUTO_MANUAL field supports filtering that distinguishes proactive automated maintenance from discretionary manual work.

Related Objects

  • JTF_TASK_TEMPLATES_B — Referenced via TASK_TEMPLATE_ID; provides the task template definition (name, type, and defaults).
  • FND_DM_PRODUCTS — Referenced via PRODUCT_ID; identifies the product or item master record.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs data visibility and multi-org access.
  • CSP_TASK_PARTS — Child table referencing CSP_PRODUCT_TASKS.PRODUCT_TASK_ID; defines the parts required or consumed by each product task.

Together, these relationships position CSP_PRODUCT_TASKS at the intersection of product definition, task templating, and parts planning—making it a pivotal configuration object for Spares Management task setup.