Search Results to_boolchar

Overview

APPS.INV_ITEM_API is the public PL/SQL package body that serves as the primary programmatic interface for creating and maintaining item master records in Oracle E-Business Suite. Within the Inventory module, the item master is the foundational data structure upon which all downstream supply chain activity depends: purchasing, receiving, inventory transactions, bills of material, order management, and costing all reference the item definitions maintained through this interface. The package encapsulates the business logic required to validate and persist item data across the base and translated item tables, insulating callers from the physical data model and providing a controlled, API-driven mechanism for item maintenance in Releases 12.1.1 and 12.2.2.

The ETRM metadata records INV_ITEM_API as owner APPS, status VALID, and classified as an API. It depends on the FND_API foundation package, which supplies the standard EBS API programming constructs (return status, error handling, message stacking), and on the INV_ITEM_API specification package. The package body is documented as referencing the underlying item tables directly rather than being referenced by other database objects, which reflects its role as a top-level entry point for item maintenance.

Key Procedures and Functions

The documented interface exposes three programs:

• UPDATE_ITEM_ROW — Updates a single row of the base item definition. This is the principal maintenance routine for modifying attributes of an existing item in the master organization, operating against the base item entity.
• UPDATE_ITEM_TL_ROW — Updates a single row of the translated item information, permitting maintenance of language-specific descriptive fields held separately from the base item record.
• TO_BOOLCHAR — A utility function that converts a Boolean value to the character representation expected by the API's flag parameters, supporting the package's internal consistency and the standard EBS convention of representing flags as single-character values.

No parameter lists are documented in the available metadata; callers should consult the package specification for signature details. The separation of base and translated update routines mirrors the underlying table design, in which descriptive text is stored in a translation table keyed to the base item.

Tables Accessed

The package references the following tables through APPS synonyms:

• MTL_SYSTEM_ITEMS_B — The base item master table, holding the core item definition common to all languages. This is the primary target of UPDATE_ITEM_ROW.
• MTL_SYSTEM_ITEMS_TL — The translated item master table, holding language-specific descriptions. This is the target of UPDATE_ITEM_TL_ROW.
• MTL_ITEM_ATTRIBUTES — Stores the attribute-level and, where applicable, organization-level settings that qualify an item, supporting attribute maintenance as part of the update flow.
• MTL_PARAMETERS — The inventory organization parameters table, consulted to resolve organization context and validation rules applicable to the item being maintained.

Additional dependencies include MTL_UNITS_OF_MEASURE_VL for unit of measure validation and the FND_API and STANDARD packages referenced within the body.

Usage Notes

INV_ITEM_API is typically invoked from custom PL/SQL programs, interfaces, and extensions that need to create or update item definitions without direct DML against the item tables. Because direct inserts and updates to MTL_SYSTEM_ITEMS_B bypass validation, attribute defaulting, and the translation handling performed by the API, use of the packaged interface is the supported practice for item maintenance. The metadata indicates the package is referenced by six other packages, confirming its role as a shared dependency across the application. It is commonly called during data conversion and migration routines, where item records are loaded from legacy or external systems, and from batch interfaces processing item changes. Callers must supply the organization context and adhere to the standard FND_API return status convention, checking the returned status and message stack for errors after each invocation. Attributes requiring organization-level specification should be maintained through the appropriate attribute-handling routines so that both the base and attribute tables remain synchronized.