Results for “pjmfv_project_mfg_projects”

50+ results




Overview
Explore in AI Chat

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

Overview

PJMFV_PROJECT_MFG_PROJECTS is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined under the Project Manufacturing (PJM) module. Its documented purpose is to expose "Project Manufacturing Projects" — that is, the set of manufacturing-relevant project identifiers that Oracle Project Manufacturing (PJM) and its Seiban integration use to associate discrete manufacturing, work-in-process, and inventory transactions with a project context. The view is registered as VALID and is documented in ETRM for both 12.1.1 and 12.2.2.

The view is primarily a reporting and integration surface. Because Oracle Project Manufacturing and Seiban functionality (used extensively in Japanese discrete manufacturing deployments) rely on project identifiers for cost collection and material assignment, this view provides a single, consistent source for listing the projects recognized by the PJM module. Its inclusion of a translated value expression rather than a stored column indicates it is intended for UI-driven reporting (for example, in Oracle Forms or OAF pages) and for external integrations retrieving project reference lists.

Underlying Base Objects

The view is defined over two referenced base objects, both exposed as SYNONYMs in the APPS schema:

The two sources are combined using UNION, not UNION ALL, and the entire definition is suffixed WITH READ ONLY. This structure ensures that the view returns a deduplicated, read-only, combined list of project-level identifiers from both the general Projects repository and the Seiban-specific source.

Key Columns

  • PROJECT_ID — the unique identifier for the project, sourced from both PA_PROJECTS_ALL and PJM_SEIBAN_NUMBERS. This is the primary join key used throughout PJM and Oracle Projects reporting.
  • PROJECT_NUMBER — the user-visible project number. For rows from PA_PROJECTS_ALL this maps to SEGMENT1; for rows from PJM_SEIBAN_NUMBERS this maps to PROJECT_NUMBER.
  • PROJECT_NAME — the descriptive name of the project (NAME or PROJECT_NAME depending on the source).
  • "_LA:PA_PROJECT_FLAG" — a literal string column whose value is generated as '_LA:1:MFG_LOOKUPS:SYS_YES_NO:MEANING' for PA_PROJECTS_ALL rows and '_LA:2:MFG_LOOKUPS:SYS_YES_NO:MEANING' for PJM_SEIBAN_NUMBERS rows. This is a message/lookup token rather than a data column; the numeric prefix (1 or 2) distinguishes the two origins, and the token instructs the runtime to resolve the value against the MFG_LOOKUPS lookup type for the SYS_YES_NO lookup. It effectively serves as a source discriminator.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard Oracle audit columns carried through from each base source.

Common Use Cases and Queries

Typical uses include populating project LOVs in PJM-enabled forms, validating project references in inventory and WIP integrations, and reporting on the full set of projects available to the manufacturing module.

SELECT PROJECT_ID
     , PROJECT_NUMBER
     , PROJECT_NAME
     , "_LA:PA_PROJECT_FLAG" AS SOURCE_FLAG
  FROM APPS.PJMFV_PROJECT_MFG_PROJECTS
 WHERE PROJECT_NUMBER LIKE :p_number

SELECT PROJECT_ID
     , PROJECT_NUMBER
     , PROJECT_NAME
  FROM APPS.PJMFV_PROJECT_MFG_PROJECTS
 WHERE "_LA:PA_PROJECT_FLAG" = '_LA:2:MFG_LOOKUPS:SYS_YES_NO:MEANING'

The second query restricts output to Seiban-originated rows, which is useful when validating material assignments and Seiban-driven work orders. Because the view is read-only and defined with UNION, it should be used strictly for querying; any maintenance of project or Seiban definitions must be performed against PA_PROJECTS_ALL or PJM_SEIBAN_NUMBERS directly. Callers should not rely on the literal _LA column as stored data, as its value is a runtime resolution token.