Search Results common_project_name

Overview

APPS.PJMFV_PROJECT_MFG_ORGS is a Business Intelligence System (BIS) view owned by the APPS schema and registered under the FND Design Data reference PJM.PJMFV_PROJECT_MFG_ORGS. It consolidates the manufacturing organization parameters that govern Project Manufacturing and Project Resource Management behavior in Oracle E-Business Suite 12.1.1 and 12.2.2. The view joins Oracle Inventory organization definitions with Project Manufacturing setup parameters, project control attributes, expenditure transfer options, and payback variance accounts, presenting each manufacturing organization as a single denormalized row. Because the object is a view rather than a base table, it carries no storage of its own and always reflects the current state of the underlying setup tables.

The object is primarily a reporting and integration artifact. It is referenced when integrators or reporting tools require the Project Manufacturing configuration context for an inventory organization without navigating multiple setup forms. The searched term common_project_number corresponds to the COMMON_PROJECT_NUMBER column exposed by this view, which is central to organizations configured to charge transactions to a common (indirect) project.

Underlying Base Objects

The documented base objects referenced by the view, all accessed through APPS synonyms, are:

• PJM_ORG_PARAMETERS — the Project Manufacturing organization parameter table that supplies project control level, expenditure transfer flags, expenditure types, and payback variance accounts.
• MTL_PARAMETERS — the Inventory organization parameters table that identifies manufacturing organizations and links to the inventory organization definition.
• HR_ALL_ORGANIZATION_UNITS — the Human Resources organization definition that provides the organization code and organization name.
• PA_PROJECTS_ALL — the Projects table joined to resolve the common project identifier, number, and name.
• GL_CODE_COMBINATIONS — the General Ledger account combinations used to validate and describe the payback variance account identifiers.

The view therefore acts as a pre-joined convenience layer across the Inventory, Projects, and General Ledger schemas, removing the need for consumers to reproduce the join logic themselves.

Key Columns

• ORGANIZATION_ID, ORGANIZATION_CODE, ORGANIZATION_NAME — identification of the manufacturing organization, derived from MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS.
• PROJECT_CONTROL_LEVEL — the numeric indicator of how tightly the organization enforces project references on transactions.
• COMMON_PROJECT_ID, COMMON_PROJECT_NUMBER, COMMON_PROJECT_NAME — the identifier, number, and description of the common project used for indirect or non-project transactions in the organization. This is the column set matched by the search term common_project_number.
• _LA:ALLOW_CROSS_PROJ_ISSUES — a descriptive flexfield-derived display column indicating whether cross-project issues are permitted.
• _LA:TRANSFER_IPV, _LA:TRANSFER_ERV, _LA:TRANSFER_FREIGHT, _LA:TRANSFER_TAX, _LA:TRANSFER_MISC — lookups describing whether each cost element is transferred, paired with the corresponding IPV_EXPENDITURE_TYPE, ERV_EXPENDITURE_TYPE, FREIGHT_EXPENDITURE_TYPE, TAX_EXPENDITURE_TYPE, and MISC_EXPENDITURE_TYPE columns.
• PAYBACK_MAT_VAR_ACCOUNT, PAYBACK_MOH_VAR_ACCOUNT, PAYBACK_RES_VAR_ACCOUNT, PAYBACK_OSP_VAR_ACCOUNT, PAYBACK_OVH_VAR_ACCOUNT — account identifiers for material, overhead, resource, outside processing, and overhead variance payback, each accompanied by a _KF key flexfield display column resolving the GL_CODE_COMBINATIONS segment string.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns inherited from the underlying setup records.

Common Use Cases and Queries

Typical uses include verifying which common project an organization charges indirect manufacturing activity to, auditing expenditure transfer configuration before period close, and extracting payback variance accounts for reconciliation reporting. The following query lists manufacturing organizations and their common project configuration:

• SELECT organization_code, organization_name, project_control_level, common_project_number, common_project_name FROM apps.pjmfv_project_mfg_orgs ORDER BY organization_code;
• SELECT organization_code, ipv_expenditure_type, erv_expenditure_type, freight_expenditure_type FROM apps.pjmfv_project_mfg_orgs WHERE _LA:TRANSFER_IPV = 'Yes';
• SELECT organization_code, payback_mat_var_account, _KF:ACC_NO:PAYBK_MTLVAR:_CO FROM apps.pjmfv_project_mfg_orgs;

Note that columns whose names begin with _LA or _KF are generated display columns and must be referenced exactly as named. Because the view is granted to the APPS schema, access should be provisioned through the standard EBS responsibility and data security model rather than granted directly to end users.