Search Results get_physical_location

Overview

INV_PROJECTLOCATOR_PUB is a public PL/SQL package in the APPS schema that exposes project and task locator functionality for Oracle Inventory. It provides a supported API surface for validating the association between inventory locators and Oracle Projects entities (projects and tasks), resolving project and task identifiers to their displayable numbers, and retrieving physical location information for a given locator. The package body resides in the INV source tree, but as documented in the package header comment, its implementation has been migrated to the PJM_PROJECT_LOCATOR and PJM_PROJECT packages under the PJM source tree. INV_PROJECTLOCATOR_PUB therefore functions primarily as a backward-compatibility wrapper, delegating each call to the corresponding PJM routine. This design allows existing Inventory, Order Management, and third-party integrations to continue invoking the INV-namespaced API while Oracle maintains a single implementation in the Projects codebase.

Key Procedures and Functions

• CHECK_PROJECT_REFERENCES — Validates whether a locator is properly associated with project-related references in the context of a specified organization. It accepts arguments covering the organization, locator, validation mode, required flag, and optional project and task identifiers, and returns a Boolean result. Internally it delegates to PJM_PROJECT_LOCATOR.CHECK_PROJECT_REFERENCES, passing a NULL for the final argument. This function is retained only for backward compatibility.
• GET_PHYSICAL_LOCATION — Returns physical location information for a given organization and locator combination, returning a Boolean status. The documented signature takes P_ORGANIZATION_ID and P_LOCATOR_ID and forwards the request to PJM_PROJECT_LOCATOR.GET_PHYSICAL_LOCATION.
• GET_PROJECT_NUMBER — Accepts a numeric project identifier and returns the corresponding project number as a VARCHAR2 value. It delegates to PJM_PROJECT.ALL_PROJ_IDTONUM, providing a convenient Inventory-side entry point for project number resolution.
• GET_TASK_NUMBER — Accepts a numeric task identifier and returns the corresponding task number as a VARCHAR2 value. It delegates to PJM_PROJECT.ALL_TASK_IDTONUM. Although the package header is authored with an alias of GET_TASK_NUMBER, the body function name is GET_TASK_NUMBER.

Tables Accessed

The ETRM metadata lists no direct table references accessed by this package via APPS synonyms. This is consistent with its role as a delegation wrapper: all data retrieval and validation is performed inside PJM_PROJECT_LOCATOR and PJM_PROJECT, which read the underlying Oracle Projects and Inventory tables such as project and task definition tables and locator definitions. Custom code should not assume that INV_PROJECTLOCATOR_PUB queries Inventory tables directly; any table access occurs within the delegated PJM routines.

Usage Notes

Because the implementation has been migrated, Oracle recommends calling the PJM_PROJECT_LOCATOR and PJM_PROJECT routines directly for new development. INV_PROJECTLOCATOR_PUB is nonetheless widely referenced: the metadata indicates it is referenced by 16 other packages, reflecting its historical role in Inventory and Projects integration points. Typical invocation scenarios include Oracle Forms-based Inventory and receiving flows that must confirm a locator is valid for a project or task, custom concurrent programs that resolve project or task IDs to displayable numbers, and legacy integrations that call the INV-namespaced API. When invoking GET_TASK_NUMBER or GET_PROJECT_NUMBER, callers should expect a VARCHAR2 return and handle the possibility of a NULL when the identifier cannot be resolved. Applications upgrading from 12.1.1 to 12.2.2 can rely on this package remaining in place, but should plan migration to the PJM routines to avoid dependency on a compatibility shim that may be deprecated in future releases.