Results for “pjm_task_wip_acct_classes_v”

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

Overview

PJM_TASK_WIP_ACCT_CLASSES_V is a Project Manufacturing (PJM) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes task-level Work in Process (WIP) and Enterprise Asset Management (EAM) accounting class assignments, joining the PJM task accounting class entity to the Project Accounting task master. The view serves as a reporting and integration surface that allows users and interfaces to retrieve the accounting class codes associated with a given project task in a specific inventory organization, along with denormalized task number and task name attributes for readability.

The presence of the EAM_ACCT_CLASS_CODE column is directly relevant to searches for "eam_acct_class_code," which is a common point of inquiry when Project Manufacturing organizations configure accounting classes for asset-related or maintenance-driven discrete jobs and work orders. Because the view is documented as VALID with no further description text, its primary purpose is derived from its defining SQL and column list.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects, both accessed through APPS synonyms:

• PJM_TASK_WIP_ACCT_CLASSES (SYNONYM) — the primary table holding the organization, project, and task accounting class assignments.
• PA_TASKS (SYNONYM) — the Project Accounting task master, joined to supply TASK_NUMBER and TASK_NAME.

The defining query is a simple equi-join between the two sources on TASK_ID:

SELECT P.ROWID, P.ORGANIZATION_ID, P.PROJECT_ID, P.TASK_ID, T.TASK_NUMBER, T.TASK_NAME, P.CREATION_DATE, P.CREATED_BY, P.LAST_UPDATE_DATE, P.LAST_UPDATED_BY, P.LAST_UPDATE_LOGIN, P.WIP_ACCT_CLASS_CODE, P.EAM_ACCT_CLASS_CODE FROM PJM_TASK_WIP_ACCT_CLASSES P, PA_TASKS T WHERE T.TASK_ID = P.TASK_ID

All audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) originate from the PJM table, as does the ROWID pseudo-column alias ROW_ID.

Key Columns

• ROW_ID — the ROWID of the underlying row in PJM_TASK_WIP_ACCT_CLASSES, useful for uniquely identifying a row for update or de-duplication.
• ORGANIZATION_ID — the inventory organization context in which the accounting class assignment applies.
• PROJECT_ID — the project to which the task belongs.
• TASK_ID — the Project Accounting task identifier, the join key to PA_TASKS.
• TASK_NUMBER / TASK_NAME — denormalized descriptive attributes from PA_TASKS for reporting convenience.
• WIP_ACCT_CLASS_CODE — the accounting class code used for Work in Process transactions on the task.
• EAM_ACCT_CLASS_CODE — the accounting class code applied to Enterprise Asset Management (maintenance) transactions on the task.
• Audit columns — standard who-columns for change tracking and audit reporting.

Common Use Cases and Queries

The view is typically used to reconcile or report the accounting class configuration for project tasks, particularly where both WIP and EAM cost collection are enabled. A common query filters by organization and project to list all task-level accounting classes:

SELECT task_number, task_name, wip_acct_class_code, eam_acct_class_code FROM pjm_task_wip_acct_classes_v WHERE organization_id = :org_id AND project_id = :project_id;

Another frequent pattern targets the EAM_ACCT_CLASS_CODE specifically, to determine which tasks carry a maintenance accounting class versus a WIP class:

SELECT task_number, eam_acct_class_code FROM pjm_task_wip_acct_classes_v WHERE eam_acct_class_code IS NOT NULL AND organization_id = :org_id;

The view also supports integration extracts feeding external costing or asset systems, since it combines the assignment key set with human-readable task identifiers. Because it is a view over the transactional setup table, it should be treated as read-only; maintenance of the underlying accounting class assignments is performed against PJM_TASK_WIP_ACCT_CLASSES through the standard Project Manufacturing setup forms.