Search Results proj_seg_default




Overview
Explore in AI Chat

Overview

PJM_PROJECT_LOCATOR is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It provides the project-related validation and defaulting logic that governs how inventory locators are associated with projects and tasks within the Project Manufacturing (PJM) and Inventory (INV) domains. Its central responsibility is to ensure that when a locator is used in a project-driven transaction, that locator carries the appropriate project and task references for the current organization. The package also resolves default project references for job, flow, and component supply operations, and manages the segment defaulting and organization profile behavior used by project-aware inventory transactions. Because Project Manufacturing depends on the correct linkage between material locators and project/task identifiers, this package acts as a validation gatekeeper for inbound and outbound inventory activity.

Key Procedures and Functions

The documented API surface includes thirteen procedures and functions. The following are the principal ones described in the metadata excerpt:

  • CHECK_PROJECT_REFERENCES — Validates whether a given locator has appropriate project and task references based on the current organization. In "specific" validation mode it also verifies that the supplied project and task identifiers hold valid values. It returns TRUE when the locator passes validation for the requested mode and FALSE otherwise. It is implemented as two overloaded functions, one accepting project and task identifiers, and a second overload that also accepts an item identifier.
  • CHECK_ITEMLOCATORCONTROL — Checks locator control at three levels: organization, subinventory, and item. When a hard-peg flag is supplied, it additionally verifies that the item is a hard-peg item. If the item carries a restricted list of subinventories or locators, the function confirms that the supplied subinventory and locator fall within that list.
  • GET_DEFAULTPROJECTLOCATOR — Returns the default project locator to be used when no explicit locator is supplied by the transaction.
  • GET_JOB_PROJECTSUPPLY, GET_FLOW_PROJECTSUPPLY, GET_COMPONENT_PROJECTSUPPLY — Resolve project supply references for job, flow, and component contexts respectively, supporting Work in Process integration with Project Manufacturing.
  • GET_PHYSICAL_LOCATION — Retrieves the physical location associated with a locator.
  • SET_SEGMENT_DEFAULT, PROJ_SEG_DEFAULT, TASK_SEG_DEFAULT — Populate default values for project and task key flexfield segments during transaction entry.
  • PUT_ORGPROFILE, GET_ORGPROFILE — Read and write organization-level profile settings that guide locator defaulting behavior.

Tables Accessed

The package reads and writes against several INV and PJM base tables through APPS synonyms. MTL_ITEM_LOCATIONS and MTL_ITEM_LOCATIONS_S hold the locator definitions, including project and task references. MTL_SYSTEM_ITEMS stores item-level locator control and hard-peg attributes. MTL_PARAMETERS holds organization-level inventory controls. MTL_SECONDARY_INVENTORIES and MTL_SECONDARY_LOCATORS define subinventory and locator restrictions. MTL_ITEM_SUB_INVENTORIES maps items to permitted subinventories. MTL_TRANSACTIONS_INTERFACE supports validation during transaction import. PJM_ORG_PARAMETERS and PJM_PROJECT_PARAMETERS supply the Project Manufacturing organization and project configuration that drives validation modes and required-reference flags. WIP_REQUIREMENT_OPERATIONS links locator logic to work order operations. FND_ID_FLEX_SEGMENTS supports project and task key flexfield defaulting, and DBMS_SQL and DUAL support dynamic SQL and singleton queries.

Usage Notes

PJM_PROJECT_LOCATOR is invoked indirectly by Oracle Inventory and Project Manufacturing forms, concurrent programs, and transaction-processing APIs whenever a locator is entered or validated for a project-controlled organization. Its documented list of referencing packages includes 26 other packages, indicating that it is a low-level utility relied upon by material transaction, move order, and WIP processing routines rather than being called directly by end users. Custom code extending project-aware inventory transactions can call CHECK_PROJECT_REFERENCES and CHECK_ITEMLOCATORCONTROL to enforce the same validation rules applied by the standard product. Because the package depends on organization and project parameters, callers must supply a valid organization context. The absence of a documented initialization routine means the functions are stateless and safe to invoke inside larger transaction flows.