Search Results common_project_name

Overview

The PJMFV_PROJECT_MFG_ORGS view is a Project Manufacturing (PJM) setup inquiry object owned by the APPS schema. It presents the full set of Project Manufacturing organization parameters, joining each PJM-enabled inventory organization to its organization definition, its common project assignment, and the five variance accounts used for payback accounting. The view is defined with a WITH READ ONLY clause, confirming it is intended exclusively for query and reporting rather than for DML operations.

Functionally, PJMFV_PROJECT_MFG_ORGS acts as a denormalized, display-ready projection of the PJM_ORG_PARAMETERS table. Rather than exposing raw foreign keys and lookup codes, it embeds Flexfield and Lookup metadata markers (for example _DF:PJM:PJM_ORG_PARAMETERS, _LA:...:FND_COMMON_LOOKUPS, and _KF:SQLGL:GL#) so that the Oracle Forms-based Project Manufacturing Setup window can render descriptive values. For integration and reporting, the view provides a single, consistent source for auditing which organizations are configured for project manufacturing and how they behave. It is relevant across Oracle EBS 12.1.1 and 12.2.2, where the underlying table structures are unchanged in this area.

Underlying Base Objects

The view is defined over five documented base objects, all referenced through APPS synonyms:

• PJM_ORG_PARAMETERS (POP) — the driving table holding the Project Manufacturing organization parameters.
• MTL_PARAMETERS (MP) — supplies the inventory organization code; joined on ORGANIZATION_ID.
• HR_ALL_ORGANIZATION_UNITS (HOU) — supplies the organization name; joined on ORGANIZATION_ID.
• PA_PROJECTS_ALL (PROJ) — supplies the common project segment and name; outer-joined on COMMON_PROJECT_ID.
• GL_CODE_COMBINATIONS (GCC1–GCC5) — five outer-joined aliases resolving the payback variance accounts for material, overhead, resources, outside processing, and overhead variances.

The joins on MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS are enforced (inner) joins, whereas the common project and all five GL account joins are outer joins (marked with (+)), reflecting that a common project and variance accounts are optional configurations.

Key Columns

• ORGANIZATION_ID / ORGANIZATION_CODE / ORGANIZATION_NAME — identify the Project Manufacturing organization.
• PROJECT_CONTROL_LEVEL — the control level governing project and task entry for the organization.
• COMMON_PROJECT_ID — the identifier of the default common project, with its SEGMENT1 and NAME surfaced from PA_PROJECTS_ALL. This is the column most closely associated with the user's search term "common_project_name".
• ALLOW_CROSS_PROJ_ISSUES — Yes/No lookup controlling whether material may be issued across projects.
• TRANSFER_IPV / ERV / FREIGHT / TAX / MISC — Yes/No flags controlling transfer of each cost component.
• IPV_EXPENDITURE_TYPE, ERV_EXPENDITURE_TYPE, FREIGHT_EXPENDITURE_TYPE, TAX_EXPENDITURE_TYPE, MISC_EXPENDITURE_TYPE — expenditure types applied when transferring each component.
• PAYBACK_MAT_VAR_ACCOUNT, PAYBACK_MOH_VAR_ACCOUNT, PAYBACK_RES_VAR_ACCOUNT, PAYBACK_OSP_VAR_ACCOUNT, PAYBACK_OVH_VAR_ACCOUNT — the five variance accounts used for payback, each resolved through GL_CODE_COMBINATIONS.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Typical uses include auditing PJM organization setup, identifying each organization's common project, and validating payback variance account configuration before period close.

• Listing all Project Manufacturing organizations and their common projects:

SELECT organization_id,
       organization_code,
       organization_name,
       common_project_id,
       name   common_project_name,
       project_control_level
FROM   apps.pjmfv_project_mfg_orgs;

• Finding the organization(s) associated with a specific common project:

SELECT organization_code, organization_name
FROM   apps.pjmfv_project_mfg_orgs
WHERE  common_project_id = :p_project_id;

• Reviewing transfer flags and payback account assignments per organization:

SELECT organization_code,
       allow_cross_proj_issues,
       transfer_ipv, transfer_erv,
       payback_mat_var_account,
       payback_osp_var_account
FROM   apps.pjmfv_project_mfg_orgs;

Because the view is read-only and already resolves names, codes, and account combinations, it is well suited to custom reports, data extracts, and diagnostic queries without requiring additional joins.