Search Results pjm_unit_numbers_lov_v




Overview
Explore in AI Chat

Overview

The PJM_UNIT_NUMBERS_LOV_V view is a Project Manufacturing (PJM) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its name and documented description indicate, it is an "End item model/unit number view for List of Values." In Oracle EBS, an LOV view is a purpose-built, denormalized query whose columns are designed to populate a List of Values window, typically reached from a form or a concurrent program parameter. This view surfaces the combination of a unit number, its associated end item, the item's number (segment), and the master organization, so that a user can identify and select a specific manufactured unit or model.

The view is defined in product PJM and is marked VALID in the ETRM 12.2.2 metadata. It returns a join across Project Manufacturing's unit-number table and Oracle Inventory's item and organization structures, filtered implicitly by the user's current manufacturing organization context. Because it is used as an LOV source, its design favors human-readable identifying columns (UNIT_NUMBER and END_ITEM_NUMBER) alongside the numeric keys (END_ITEM_ID and MASTER_ORGANIZATION_ID) needed to drive downstream lookups and form navigation.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects: FND_PROFILE (PACKAGE), MTL_ITEM_FLEXFIELDS (VIEW), MTL_PARAMETERS (SYNONYM), PJM_UNIT_NUMBERS (SYNONYM), and DUAL (SYNONYM). The view text joins PJM_UNIT_NUMBERS (aliased PUN) to MTL_ITEM_FLEXFIELDS (MIF) and MTL_PARAMETERS (MP).

  • PJM_UNIT_NUMBERS is the driving table, holding the unit number, the end-item identifier, the owning master organization, and comments for each manufactured unit.
  • MTL_ITEM_FLEXFIELDS supplies the descriptive item number. The join links MIF.INVENTORY_ITEM_ID = PUN.END_ITEM_ID and MIF.ORGANIZATION_ID = PUN.MASTER_ORGANIZATION_ID, resolving the end item in its master organization.
  • MTL_PARAMETERS provides the master-organization relationship used for context filtering.
  • FND_PROFILE.VALUE('MFG_ORGANIZATION_ID') is invoked to derive the current manufacturing organization, allowing the view to restrict results to the organization the user is operating in. DUAL underlies this profile function call.

The organization filter uses MP.MASTER_ORGANIZATION_ID = MIF.ORGANIZATION_ID together with MP.ORGANIZATION_ID = NVL(FND_PROFILE.VALUE('MFG_ORGANIZATION_ID'), MIF.ORGANIZATION_ID), so that when a manufacturing organization profile is set the view returns only units belonging to that organization, and otherwise falls back to the item's own organization.

Key Columns

  • UNIT_NUMBER — the human-readable identifier for the manufactured unit or model; this is the primary selection value presented in the LOV.
  • END_ITEM_ID — the inventory item identifier of the end item/model associated with the unit, used as a foreign key into item master data.
  • END_ITEM_NUMBER — the item number (from MTL_ITEM_FLEXFIELDS) displayed for the corresponding end item; the documented column list exposes this as END_ITEM_NUMBER.
  • MASTER_ORGANIZATION_ID — the master organization that owns the end item and the unit number, essential for organization-scoped lookups.
  • COMMENTS — free-text comments stored on the unit number record, available for display or filtering.

Common Use Cases and Queries

The view is typically invoked to populate unit-number LOVs in Project Manufacturing forms and to resolve a selected unit number to its numeric keys. A representative query follows:

  • SELECT unit_number, end_item_number, end_item_id, master_organization_id, comments FROM apps.pjm_unit_numbers_lov_v WHERE unit_number LIKE :p_unit || '%' ORDER BY 1;
  • To restrict by end item: add AND end_item_id = :p_end_item_id.
  • Because the view depends on FND_PROFILE.VALUE('MFG_ORGANIZATION_ID'), results are scoped to the caller's current manufacturing organization unless the profile is null.

Typical consumers include custom reports, form LOV definitions, and integration extracts that must resolve a displayed unit number to the underlying unit-number keys.