Search Results current_unit_number




Overview
Explore in AI Chat

Overview

APPS.PJM_UNIT_EFF is an Oracle E-Business Suite PL/SQL package that encapsulates the Model/Unit Effectivity (also known as Unit Effectivity or Unit Number control) feature used within the Oracle Project Manufacturing and Discrete Manufacturing environments. Unit Effectivity provides a mechanism to track and control the manufacture, issue, receipt and shipment of configured items at the individual unit number level rather than by lot or serial number alone. The package serves as a central API for determining whether model/unit effectivity has been enabled for an organization, resolving the current, previous and next unit numbers against a transaction context, validating serial numbers against unit numbers, and recording the linkage between serials and unit numbers in the unit serial history.

The package is classified as an "OTHER" type API in the ETRM repository and is referenced by 28 other packages across the manufacturing, order management, receiving and purchasing modules, indicating that it is a foundational utility invoked broadly wherever unit effectivity logic must be applied consistently.

Key Procedures and Functions

The package exposes seventeen documented procedures and functions. Several provide configuration and context lookups:

  • ENABLED — returns a Y/N indicator stating whether Model/Unit effectivity is enabled.
  • ALLOW_CROSS_UNITNUM_ISSUES — returns Y/N indicating whether cross-unit number WIP issues are permitted for an organization.
  • UNIT_EFFECTIVE_ITEM — checks the effectivity control setting for a specific item and organization, returning Y/N.
  • SET_UNIT_NUMBER — sets the global variable Current_Unit_Number.
  • CURRENT_UNIT_NUMBER — retrieves the value of the global variable G_Unit_Number.
  • PREV_UNIT_NUMBER and NEXT_UNIT_NUMBER — return the immediately preceding or following unit number within a sequence.

Additional functions resolve the applicable unit number from the context of a specific transaction source: WIP_UNIT_NUMBER, WIP_UNIT_NUMBER_CACHED, RCV_UNIT_NUMBER, OE_LINE_UNIT_NUMBER, OE_LINE_UNIT_NUMBER_CACHED, RMA_RCPT_UNIT_NUMBER, and OE_ATTRIBUTE. The functions VALIDATE_SERIAL, SERIAL_UNITNUM_LINK, and UNIT_SERIAL_HISTORY provide the serial-to-unit-number validation and history maintenance logic that the searched term "unit_serial_history" relates to.

Tables Accessed

The package accesses a broad set of transactional and master tables through APPS synonyms. Master and setup data are read from MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, PJM_UNIT_NUMBERS and PJM_ORG_PARAMETERS, which supply item attributes and organization-level unit effectivity configuration. Transaction tables include MTL_MATERIAL_TRANSACTIONS, MTL_TRANSACTION_LOT_NUMBERS, MTL_SERIAL_NUMBERS and MTL_UNIT_TRANSACTIONS, which record material movements, lots, serials and unit movements. Manufacturing and distribution contexts are sourced from WIP_DISCRETE_JOBS, WIP_ENTITIES, RCV_TRANSACTIONS, PO_DISTRIBUTIONS_ALL, PO_REQ_DISTRIBUTIONS_ALL and OE_ORDER_LINES_ALL. The unit serial history is persisted in PJM_UNIT_SERIAL_HISTORY, the primary table behind the UNIT_SERIAL_HISTORY function.

Usage Notes

APPS.PJM_UNIT_EFF is typically invoked indirectly by forms, concurrent programs and other PL/SQL packages rather than being called directly by end users. Because it is referenced by 28 dependent packages, it acts as a shared service layer for unit effectivity decisions across WIP, Order Management, Purchasing, Receiving and Inventory. Custom code that must determine unit effectivity status, resolve a unit number from a WIP, RCV, OM or RMA context, or validate a serial against a unit number should call these public functions rather than replicating the logic, ensuring consistent behaviour with standard Oracle functionality in both 12.1.1 and 12.2.2.