Results for “mfg_organization_id”

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

Overview

APPS.PJM_UNIT_NUMBERS_LOV_V is a project manufacturing (PJM) list-of-values view that exposes unit numbers defined against an end item and a master organization. In Oracle EBS 12.1.1 and 12.2.2, unit numbers are the identifiers used to track discrete manufactured units — for example, a specific serialized configuration or contract deliverable built under Project Manufacturing or Contract Manufacturing. This view is designed to feed LOV (List of Values) windows and descriptive flexfield popups so that forms and self-service pages can present only those unit numbers relevant to the current master organization context.

The view joins unit-number records to item master flexfield data, and constrains the result set by the values of two profile options: MFG_ORGANIZATION_ID and ORG_ID. This contextual filtering is the defining feature of the view and explains why it is typically invoked from within a form session rather than from a batch report.

Underlying Base Objects

The view is defined over a small set of documented base objects:

• PJM_UNIT_NUMBERS (synonym) — the driving table, aliased PUN, holding unit number, end item, master organization, and comments.
• MTL_ITEM_FLEXFIELDS (view) — aliased MIF, supplying the concatenated item number for the end item and organization.
• MTL_PARAMETERS (synonym) — used in a scalar subquery to resolve the master organization of the current manufacturing organization.
• FND_PROFILE (package) — accessed via FND_PROFILE.VALUE to read MFG_ORGANIZATION_ID and ORG_ID.
• DUAL (synonym) — implied by the profile evaluation logic.

Because FND_PROFILE.VALUE is a PL/SQL function call, the view is not a pure SQL join; it depends on the session-level profile cache and therefore returns different rows per user session and responsibility context.

Key Columns

• UNIT_NUMBER — the user-visible unit identifier presented in the LOV.
• END_ITEM_ID — inventory item identifier of the end item the unit number represents.
• ITEM_NUMBER — the concatenated item number from MTL_ITEM_FLEXFIELDS, joined on END_ITEM_ID and MASTER_ORGANIZATION_ID.
• MASTER_ORGANIZATION_ID — the master organization that owns the unit-number definition.
• COMMENTS — free-text remarks captured against the unit number.

Common Use Cases and Queries

The view is primarily consumed by LOV record groups bound to descriptive flexfields and unit-number entry fields in Project Manufacturing and Contract Manufacturing forms. A representative query is:

• SELECT unit_number, end_item_id, item_number, master_organization_id, comments FROM apps.pjm_unit_numbers_lov_v WHERE unit_number LIKE :1;

The relevance predicate is applied implicitly inside the view: if MFG_ORGANIZATION_ID is null, the end item's organization must equal ORG_ID; otherwise it must equal the master organization derived from MTL_PARAMETERS for the current manufacturing organization. When diagnosing "no rows returned" behaviour, the profile values for the session must be checked first, followed by verification that the end item and unit number exist in the expected master organization.