Search Results get_usermessage2

Overview

AMV_ITEM_PUB_W is a public PL/SQL wrapper package owned by APPS in Oracle E-Business PLM/Advanced Product Catalog (formerly Oracle Product Hub / Item Catalog). It exposes a service-oriented interface around the core item entity maintained by the AMV_ITEM_PUB package. The "_W" suffix denotes the generated wrapper layer that adapts the strong PL/SQL record and collection types declared in AMV_ITEM_PUB (such as amv_simple_item_obj_varray, amv_char_varray_type, and amv_number_varray_type) to the generic JTF scalar table types (JTF_VARCHAR2_TABLE_100, JTF_NUMBER_TABLE, JTF_DATE_TABLE, etc.) that the Oracle EBS integration and Java/repository framework can marshal across boundaries. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer, consistent with the generated wrapper convention.

Key Procedures and Functions

Twenty-seven documented members are exposed, falling into three functional groups.

• Rosetta copy routines — ROSETTA_TABLE_COPY_IN_P0, ROSETTA_TABLE_COPY_OUT_P0, ROSETTA_TABLE_COPY_IN_P1, ROSETTA_TABLE_COPY_OUT_P1, ROSETTA_TABLE_COPY_IN_P6, ROSETTA_TABLE_COPY_OUT_P6, ROSETTA_TABLE_COPY_IN_P8, and ROSETTA_TABLE_COPY_OUT_P8. These convert between PL/SQL object/collection types and the flat JTF table arrays. The _IN_ variants take a JTF table per attribute and populate the corresponding strongly typed varray; the _OUT_ variants reverse the mapping. Each numbered suffix corresponds to a specific parameter group in the parent API (P0 for character varrays, P1 for numeric varrays, and P6/P8 for the large multi-attribute item record structures).
• Item entity maintenance — CREATE_ITEM, UPDATE_ITEM, GET_ITEM, and FIND_ITEM. These provide the wrapper-level insert, modify, retrieve-by-key, and search operations for the item master record, delegating the actual validation and DML to AMV_ITEM_PUB.
• Child entity maintenance — ADD_ITEMKEYWORD, DELETE_ITEMKEYWORD, REPLACE_ITEMKEYWORD, GET_ITEMKEYWORD, and the parallel set ADD_ITEMAUTHOR, DELETE_ITEMAUTHOR, REPLACE_ITEMAUTHOR, GET_ITEMAUTHOR. These manage the keyword and author associations of an item, supporting add, delete, replace-all, and query semantics.

Tables Accessed

The only table documented as referenced through APPS synonyms is PLITBLM, the item-related base table in the item catalog schema. The wrapper package does not perform direct joins; it relies on AMV_ITEM_PUB to translate the incoming JTF arrays into the appropriate PLITBLM DML and to hydrate the outgoing arrays from stored rows. Because the wrapper is generated, no other tables are listed, and any additional access (for example, to attribute or keyword intersection tables) is inherited through the underlying public package rather than declared here.

Usage Notes

AMV_ITEM_PUB_W is not intended for direct call by end users or for ad hoc SQL*Plus execution. It is the entry point invoked by the EBS integration framework — typically by the Business Object API / repository layer and by forms or concurrent programs written in Java or PL/SQL that need to move item data across a technology boundary. The "replace_itemfile" search term suggests interest in the file/attachment aspects of item definition; consumers looking for file replacement should confirm whether the operation is routed through UPDATE_ITEM (which ultimately reaches the file/media handling in AMV_ITEM_PUB) or handled by a separate attachment API, since AMV_ITEM_PUB_W itself exposes no explicit file procedure. No other package is documented as referencing AMV_ITEM_PUB_W, so it should be treated as a leaf-level public API. Customizations should call the wrapper only for cross-boundary integration scenarios; direct server-side PL/SQL should target AMV_ITEM_PUB to avoid the overhead of the Rosetta copy conversions. On 12.1.1 and 12.2.2 the package is shipped under the APPS schema with the header revision of 120.2, dated 2005, indicating it has been stable across releases.