Search Results get_item_details

Overview

APPS.PO_ITEMS_SV2 is a server-side PL/SQL package in Oracle E-Business Suite that exposes Item-related Application Program Interfaces (APIs) for the Purchasing and Inventory modules. As stated in its header, the package "contains the server side Item related Application Program Interfaces (APIs)" and its purpose is to "obtain information based on the item and organization." The package declares AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, and it is owned by APPS. The original header identifies Melissa Snyder as owner and carries a revision identifier ($Header: POXCOI2S.pls 120.0 ...) reflecting its maintenance lineage. Within ETRM 12.2.2 the package is classified under the generic API category OTHER, but functionally it belongs to the family of purchasing item validation and attribute-lookup utilities (the _SV2 suffix denoting a server-side versioned API stub). Its role is to centralize the retrieval of item attributes that drive purchasing behaviour — planned item status, outside processing, receipt and invoice tolerances, stock and purchasing enablement, and asset-related flags — so that forms, concurrent programs, and custom code do not need to query the underlying inventory tables directly.

Key Procedures and Functions

• get_item_details — The primary API and the object most commonly associated with the search term "get_item_details." It accepts an item identifier and an inventory organization identifier as inputs and returns, through IN OUT NOCOPY parameters, the item's purchasing and inventory attributes. Documented outputs include the planned item flag, outside operation flag and outside operation UOM type, invoice close tolerance, receive close tolerance, receipt required flag, stock enabled flag, internal orderable flag, purchasing enabled flag, and inventory asset flag. Later additions in support of intercompany invoicing (/* INVCONV BEGIN PBAMB */ ... /* INVCONV END PBAMB */) extend these outputs with a secondary default indicator, grade control flag, and secondary unit of measure.
• get_item_status — Retrieves the item status used when autocreating shipments and distributions. The source comments state it was created deliberately to minimize "ripple effect to all other people who might have already used either get_item_details or get_item_info procedures," and that it could later be merged into those procedures.
• get_item_cost — A companion procedure that returns item cost information, listed alongside the other two in the package header's procedure names.
• Additional documented program units are present (five procedures/functions are registered in ETRM), supplementing the three principal entry points above.

Tables Accessed

The package reads and writes against the following base tables through APPS synonyms:

• MTL_SYSTEM_ITEMS — The core item master, source of the purchasing and inventory enablement flags, asset flag, and tolerance attributes.
• MTL_SYSTEM_ITEMS_KFV — The key-flexfield view of the item master, used to resolve concatenated item identifiers.
• MTL_PARAMETERS — Organization-level inventory parameters, providing defaults that govern stock-enabled and related organization behaviour.
• MTL_ITEM_REVISIONS — Item revision data, consulted where revision-controlled items affect the returned status.
• MTL_UNITS_OF_MEASURE — Unit-of-measure definitions, required to resolve the outside operation UOM type and secondary unit of measure.

Usage Notes

PO_ITEMS_SV2 is a server-side package, so it is typically invoked from PL/SQL rather than directly by an end user. It is referenced by 14 other packages in the EBS schema, indicating it acts as a shared dependency for purchasing and inventory logic. The most common consumers are Purchasing forms (for example, validation and defaulting logic on requisition, purchase order, and receipt windows), concurrent programs that process receipts and shipments, and custom extensions that need authoritative item attributes without duplicating MTL_SYSTEM_ITEMS queries. Because attributes are organization-specific, callers must always supply a valid inventory organization identifier; passing an organization in which the item is not assigned will yield defaults rather than meaningful values. The IN OUT NOCOPY parameter convention matters for performance: callers should initialize the OUT parameters and treat them as mutable, allowing the package to pass PL/SQL collections and large values back without copying overhead. Note that the interface remains stable but versioned (SV2), so custom code should reference this package rather than earlier variants, while remaining aware that get_item_status was introduced separately to avoid disrupting existing callers of get_item_details and get_item_info.