Results for “csd_project_details_v”

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

Overview

CSD_PROJECT_DETAILS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, validated against releases 12.1.1 and 12.2.2. It belongs to the CSD (Depot Repair) product family and serves as a lightweight denormalization layer that resolves project and task identifiers captured on depot repair product transactions into their corresponding user-visible project and task numbers. Depot Repair frequently processes returned or repaired items that must be charged against a project and task combination, and downstream users, reports, and interfaces require the human-readable project number and task number rather than the internal numeric identifiers. CSD_PROJECT_DETAILS_V supplies that translation without requiring callers to join the Projects views themselves. Because the view exposes both the transaction identifier and the resolved project and task numbers, it functions as a bridge object between Depot Repair transaction data and Projects accounting and billing structures.

Underlying Base Objects

The view text is defined as a join of three objects: CSD_PRODUCT_TRANSACTIONS, PJM_PROJECTS_V, and PJM_TASKS_V. CSD_PRODUCT_TRANSACTIONS, the driving object, is a synonym over the depot repair product transaction entity and supplies the transaction, project, task, unit, and version identifiers. PJM_PROJECTS_V is joined on PROJECT_ID to retrieve PROJECT_NUMBER, and PJM_TASKS_V is joined on TASK_ID to retrieve TASK_NUMBER. Both Projects views are outer-joined to the transaction row, so a product transaction with a null or unresolved project or task still returns its transactional columns while the corresponding number column remains null. The documented base objects also reference supporting PL/SQL components, including FND_PROFILE, PA_CROSS_BUSINESS_GRP, PA_PROJECT_UTILS, PA_SECURITY, and PA_TASK_UTILS. These packages underpin the security and project data access logic embedded in the PJM_PROJECTS_V and PJM_TASKS_V views, meaning the rows visible through CSD_PROJECT_DETAILS_V are implicitly filtered by the caller's Projects security profile and operating unit authority.

Key Columns

• PRODUCT_TRANSACTION_ID — Primary identifier of the depot repair product transaction that carries the project and task references; serves as the natural join key back to the transaction detail.
• PROJECT_ID — Internal numeric identifier of the project recorded on the transaction.
• PROJECT_NUMBER — User-visible project number resolved from PJM_PROJECTS_V.
• TASK_ID — Internal numeric identifier of the task recorded on the transaction.
• TASK_NUMBER — User-visible task number resolved from PJM_TASKS_V.
• UNIT_NUMBER — Unit number associated with the product transaction, used for depot repair tracking of the item being serviced.
• OBJECT_VERSION_NUMBER — Concurrency control attribute carried from the base transaction row.

Common Use Cases and Queries

Typical usage includes depot repair reporting, integration extracts that feed external billing or project costing systems, and diagnostic queries that validate whether project or task references on repair transactions resolved correctly. The view is frequently the source for Lookups and value sets, and it is a convenient target when a user searches for "pjm_tasks_v" in the context of depot repair, since it exposes TASK_NUMBER without a direct Projects join. A representative query retrieving project and task context for repair transactions follows:

• SELECT product_transaction_id, project_number, task_number, unit_number FROM apps.csd_project_details_v WHERE project_number IS NOT NULL AND task_number IS NOT NULL;
• SELECT project_number, COUNT(*) FROM apps.csd_project_details_v GROUP BY project_number ORDER BY 2 DESC;
• SELECT c.product_transaction_id, c.project_number, c.task_number FROM apps.csd_project_details_v c WHERE c.unit_number = :unit;

Because the project and task views are outer-joined, queries intended to surface only fully referenced transactions should include IS NOT NULL predicates on PROJECT_NUMBER and TASK_NUMBER. Access to rows remains governed by Projects security, so results vary with the responsibilities and profiles assigned to the executing user.