Search Results routing_ref_id

Overview

APPS.PJM_PROJECT_WIP_V is a Web view in the Oracle E-Business Suite APPS schema that consolidates project-related Work in Process (WIP) discrete job information. The view is registered in FND Design Data as PJM.PJM_PROJECT_WIP_V and holds a VALID status in the ETRM metadata for EBS 12.1.1 and 12.2.2. Its primary purpose is to return all project-related WIP jobs, joining project and task identifiers to the manufacturing execution records that consume or produce inventory against them.

Because it is implemented as a Web view, PJM_PROJECT_WIP_V is designed to simplify data access from Oracle Self-Service Web Applications. The documentation notes that it corresponds directly to two functional inquiry regions: the WIP Job Summary (multi-row) and WIP Job Information (single-row) web pages. This makes it the natural data source for OAF-based or JSP-based pages that display job-level project cost collection information, and equally useful as a reporting view for custom concurrent programs, BI Publisher reports, and interface extracts that need project-to-job relationships.

Underlying Base Objects

The view is defined over a set of base objects supplied by the WIP, INV, and HR modules, as documented in the metadata:

• WIP_DISCRETE_JOBS — the principal source of discrete job header attributes, including job name, description, status, class, and quantity columns. Job identifiers such as JOB_ID, PRIMARY_ITEM_ID, and the reference IDs are sourced here.
• WIP_ENTITIES — supplies the project and task accounting context (PROJECT_ID, TASK_ID) attached to WIP entities, providing the "project-related" filter that distinguishes this view.
• MTL_SYSTEM_ITEMS_KFV — the key flexfield view over MTL_SYSTEM_ITEMS, used to derive the concatenated ASSEMBLY item number and ASSEMBLY_DESCRIPTION.
• MTL_PARAMETERS — the inventory organization definition table, joined to resolve ORGANIZATION_NAME and organization-level defaults.
• HR_ALL_ORGANIZATION_UNITS_TL — the translated organization name table, providing the display name for the inventory organization.
• MFG_LOOKUPS — the manufacturing lookup view used to translate coded values such as JOB_STATUS into its descriptive meaning.

Key Columns

The view exposes identifiers, descriptive attributes, and quantity measures required for project job inquiries:

• PROJECT_ID, TASK_ID — system-generated identifiers uniquely identifying the project (or seiban) and task against which the job is accounted.
• JOB_ID, JOB_NAME, JOB_DESCRIPTION — the WIP job unique identifier and its user-facing name and description.
• JOB_CLASS, JOB_STATUS — the WIP accounting class and the resolved job status description.
• ORGANIZATION_NAME, ASSEMBLY, ASSEMBLY_DESCRIPTION — the inventory organization and the assembly item number and description.
• PRIMARY_ITEM_ID, END_ITEM_UNIT_NUMBER — the assembly item identifier and the end item model or unit number for configured items.
• START_DATE, COMPLETION_DATE, START_QUANTITY, PRIMARY_UOM — scheduling and UOM context for the job.
• QUANTITY_COMPLETED, QUANTITY_REMAINING, QUANTITY_SCRAPPED — current execution quantities per job.
• BOM_REFERENCE_ID, BOM_REVISION, ROUTING_REF_ID — the bill of material reference identifier, its revision, and the routing reference unique identifier (ROUTING_REF_ID, NUMBER). The routing reference links the job to the specific routing used, and is frequently queried when tracing job structure or reconstructing the routing revision applied at release time.

Common Use Cases and Queries

Typical uses include project job status reporting, cost collection verification, and extracting job-to-routing or job-to-BOM associations for integration. The following query returns project jobs with their routing and BOM references:

SELECT project_id, task_id, job_name, job_status, assembly,
       quantity_completed, bom_reference_id, bom_revision, routing_ref_id
  FROM apps.pjm_project_wip_v
 WHERE project_id = :p_project_id
   AND job_status = 'Released';

To trace all jobs using a specific routing reference or listed as related to a project seiban, filter directly on ROUTING_REF_ID or on PROJECT_ID and TASK_ID. Because the view masks joins across WIP_DISCRETE_JOBS, WIP_ENTITIES, MTL_SYSTEM_ITEMS_KFV, MTL_PARAMETERS, HR_ALL_ORGANIZATION_UNITS_TL, and MFG_LOOKUPS, it is the preferred public interface for project WIP reporting, avoiding the need to reconstruct the underlying join logic in each custom report.