Search Results routing_ref_id




Overview
Explore in AI Chat

Overview

The APPS.PJM_PROJECT_WIP_V view is a Project Manufacturing (PJM) reporting object that consolidates project-related Work in Process (WIP) discrete job information for the Oracle E-Business Suite Web Inquiry interface. It is maintained in the APPS schema with a VALID status and is shipped in both Oracle EBS 12.1.1 and 12.2.2. The view exists primarily to support inquiry and reporting surfaces where project and task context must be presented alongside the underlying WIP job details, rather than forcing the caller to join WIP_ENTITIES, WIP_DISCRETE_JOBS, and the related descriptive tables manually.

Because the view exposes a curated, denormalized projection of job, project, item, organization, and status attributes, it is commonly referenced in custom reports, Oracle Discoverer or BI Publisher data models, and integration extracts that need project-aware WIP visibility. Its SELECT DISTINCT clause guarantees that each unique combination of the exposed columns is returned only once, which is important given the multiplicity of joins across lookup and organization tables.

Underlying Base Objects

The documented metadata identifies six referenced base objects, all accessed through APPS synonyms or views:

  • WIP_DISCRETE_JOBS (SYNONYM) — the primary fact source, aliased as WDJ; supplies job identity, project and task, quantities, dates, primary item, BOM and routing references.
  • WIP_ENTITIES (SYNONYM) — aliased as WE; supplies the WIP entity name (job name).
  • MTL_SYSTEM_ITEMS_KFV (SYNONYM) — aliased as ITEMKFV; supplies concatenated item segments, item description, primary item id, and UOM. Joined with the (+) outer-join operator on inventory_item_id and organization_id.
  • MTL_PARAMETERS (SYNONYM) — aliased as PARA; joined on organization_id, establishing the inventory organization context for the job.
  • MFG_LOOKUPS (VIEW) — aliased as MLC; supplies the decoded job status meaning via LOOKUP_TYPE = 'WIP_JOB_STATUS' and LOOKUP_CODE = WDJ.STATUS_TYPE. This outer join is what the search term "wip_job_status" refers to.
  • HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) — aliased as HOU; supplies the translated organization name, filtered by USERENV('LANG') for the session language.

Key Columns

The view exposes the following columns, several of which are aliases of underlying columns:

Common Use Cases and Queries

Typical scenarios include: listing open project jobs with decoded status for a project manager's Web Inquiry page; extracting project WIP balances by organization for cost analysis; and validating job status transitions for project manufacturing jobs. A representative query filtering on project and status might read:

SELECT JOB_NAME, JOB_STATUS, ASSEMBLY, START_QUANTITY, QUANTITY_COMPLETED, QUANTITY_REMAINING FROM APPS.PJM_PROJECT_WIP_V WHERE PROJECT_ID = :p_project_id AND JOB_STATUS IN ('Released','Unreleased') ORDER BY START_DATE;

Because QUANTITY_REMAINING is a computed expression rather than a stored column, it is appropriate to use it directly in arithmetic or aggregate contexts. Status filtering should use the decoded MEANING values exposed by JOB_STATUS (derived from the WIP_JOB_STATUS lookup), which conveniently isolates callers from the raw STATUS_TYPE codes. Organizations are restricted through MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS_TL, so the view returns rows only for valid, language-appropriate organization contexts. In 12.2.2 the same definition holds, with the referenced synonyms resolving against the online patching edition of the APPS schema.