Search Results get_onhand_notavailable

Overview

APPS.AHL_PRD_MRSHL_PVT is a private PL/SQL package within the Oracle E-Business Suite Discrete Manufacturing and Maintenance Management product family. The package supplies the business logic that supports material marshalling operations associated with work orders, visits, and item instances tracked through the AHL (Productivity Manufacturing / Maintenance) schema foundations and the WIP discrete jobs infrastructure. It is classified in ETRM as a PVT (private) API, indicating that its constituent procedures are intended for internal consumption by Oracle-developed forms, concurrent programs, and higher-level public packages rather than by direct customer extension code. The package serves as the data retrieval and aggregation engine behind material availability, marshalling detail, and work order completion reporting used in the maintenance and discrete manufacturing flows.

Key Procedures and Functions

The documented package exposes eight procedures and functions, none of which are enumerated with public parameter lists in the metadata. Their purposes are as follows:

• GET_UNAVAILABLE_ITEMS — Returns the set of material requirements that cannot be satisfied from current supply, populated into the unavailable items record and table types declared in the package specification.
• GET_AVAILABLE_ITEMS — Returns the corresponding list of material requirements for which supply is available, using the available items record structure.
• GET_WORKORDER_COUNT — Supplies a count of work orders relevant to the current marshalling search context.
• GET_ITEM_COUNT — Supplies a count of item instances or requirements within the given search criteria.
• GET_VISIT_COMPLETION_PERC — Computes the percentage of completion for a visit, supporting status visibility in the marshalling interface.
• GET_MRSHL_DETAILS — Retrieves marshalling header and detail information, relying on the Mrshl_search_rec_type structure.
• GET_ONHAND_AVAILABLE — This procedure is the one referenced by the search term "get_onhand_available." It identifies on-hand quantities that are available to satisfy a requirement, drawing on inventory locations and reservations data.
• GET_ONHAND_NOTAVAILABLE — The complementary routine, returning on-hand quantity that is not available for the requirement (for example, reserved or otherwise consumed stock).

Tables Accessed

The package reads from a defined set of APPS synonyms spanning maintenance, inventory, and manufacturing tables. AHL_SCHEDULE_MATERIALS, AHL_WORKORDERS, and AHL_PRD_MB_UC_DETAILS are the primary sources for marshalling and work order requirement data. AHL_VISITS_B, AHL_VISIT_TASKS_B, AHL_ITEM_ASSOCIATIONS_B, AHL_MC_RELATIONSHIPS, and CSI_II_RELATIONSHIPS / CSI_ITEM_INSTANCES link visits, item instances, and their relationships. Inventory availability is derived from MTL_ITEM_LOCATIONS, MTL_RESERVATIONS, and MTL_SERIAL_NUMBERS, while item attribution is resolved through MTL_SYSTEM_ITEMS_KFV. Work order and operation context is supplied by WIP_DISCRETE_JOBS and WIP_REQUIREMENT_OPERATIONS. The package is documented as referenced by one other package, indicating it is consumed as a supporting utility rather than as an entry point.

Usage Notes

Because AHL_PRD_MRSHL_PVT is a private package, it is normally invoked indirectly — through the Oracle forms and concurrent programs that present the material marshalling and work order availability screens, and through any public API layered above it. The procedures perform read-oriented retrieval and aggregation rather than transactional DML, so callers should not rely on them for committing inventory or work order state changes. Current on-hand and reservation data is read at call time, so results reflect the state of MTL_RESERVATIONS and MTL_ITEM_LOCATIONS at execution. In customizations, the package should be treated as internal and unguaranteed; safer integration points are the public AHL APIs or the underlying base tables. The GET_ONHAND_AVAILABLE and GET_ONHAND_NOTAVAILABLE pair is specifically used wherever the application must distinguish available from unavailable on-hand quantity for a marshalling requirement, and its behavior is tied to the availability rules configured for the organization and subinventory in scope.