Search Results mtl_item_locations_s

Overview

PJM_PROJECT_LOCATOR is an Oracle EBS Applications (APPS) PL/SQL package body that provides the core service layer for Project Manufacturing and inventory locator processing. Its central business function is to resolve, validate, and default project and task references that are associated with inventory locators in an Oracle Project Manufacturing environment. In Project Manufacturing, material stored in inventory can be owned or reserved against a specific project and task, and the locator record itself carries the project and task segment values. PJM_PROJECT_LOCATOR encapsulates the logic required to determine which project/task combination applies to a given locator, organization, or transaction context, and to enforce referential integrity between locators and projects. Because the package is classified as OTHER within the ETRM repository and is referenced by 26 other database objects, it functions as a foundational utility rather than a user-facing API. It is tightly coupled with Oracle Inventory (MTL), Project Manufacturing (PJM), Work in Process (WIP), and the Oracle Applications flexfield and profile infrastructure.

Key Procedures and Functions

The package body exposes thirteen documented procedures and functions, grouped by responsibility:

• CHECK_PROJECT_REFERENCES — verifies that project and task references associated with locators are valid and consistent.
• CHECK_ITEMLOCATORCONTROL — validates locator control rules for items, typically in support of inventory transaction validation.
• GET_DEFAULTPROJECTLOCATOR — returns the default project locator for a given context, driving automatic project assignment during transactions.
• GET_JOB_PROJECTSUPPLY — derives the project supply reference for a work in process job.
• GET_FLOW_PROJECTSUPPLY — determines project supply in a flow manufacturing context.
• GET_COMPONENT_PROJECTSUPPLY — resolves the project supply associated with a component issued to or required by a job.
• GET_PHYSICAL_LOCATION — returns the physical inventory location corresponding to a project locator.
• SET_SEGMENT_DEFAULT — applies default key flexfield segment values for project or task segments.
• PUT_ORGPROFILE and GET_ORGPROFILE — store and retrieve organization-level profile values used in locator determination.
• PROJ_SEG_DEFAULT and TASK_SEG_DEFAULT — supply default project segment and task segment values respectively.

Tables Accessed

The package references a defined set of Inventory, Project Manufacturing, and Applications foundation tables. From Oracle Inventory it reads MTL_ITEM_LOCATIONS and MTL_ITEM_LOCATIONS_S (locator definitions and their translations), MTL_ITEM_SUB_INVENTORIES, MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, MTL_SECONDARY_LOCATORS, MTL_SYSTEM_ITEMS, and MTL_TRANSACTIONS_INTERFACE. These support locator validation, item/locator control, and transaction interface processing. Project Manufacturing tables include PJM_ORG_PARAMETERS, PJM_PROJECT_PARAMETERS, and by dependency PJM_PROJECT and project/task views. WIP_REQUIREMENT_OPERATIONS is accessed for job supply resolution. Foundation tables include FND_ID_FLEX_SEGMENTS for key flexfield segment metadata, and FND_MESSAGE for message handling. DBMS_SQL, DBMS_STANDARD, DUAL, and STANDARD are used for dynamic SQL and standard PL/SQL utilities.

Usage Notes

PJM_PROJECT_LOCATOR is invoked indirectly rather than directly by end users. It is called by Oracle Inventory and Project Manufacturing forms and concurrent programs whenever a locator is validated, defaulted, or associated with a project and task. The package is also called by the 26 database objects that reference it, including PJM and INV transaction processing routines. Custom code extending Project Manufacturing should call the public procedures rather than duplicating locator logic, since the package centralizes profile and flexfield defaulting behavior across Oracle EBS 12.1.1 and 12.2.2.