Search Results amv_char_varray_type

Overview

AMV_ITEM_PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite. It provides a programmatic interface for managing MES (Media and Events/Content) items and their related attributes within the Oracle iStore and Marketing content infrastructure. The package header (amvpitms.pls, version 120.1, last modified 2005/06/22) documents its purpose as "a public API managing MES items (contents) and their related attributes," and it additionally defines global variables and shared collection types used by the broader AMV module.

The package exposes a set of record types that structure the payloads passed between callers and the API. These include AMV_RETURN_OBJ_TYPE (returned record count, next record position, total record count), AMV_REQUEST_OBJ_TYPE (records requested, start record position, return total count flag), and AMV_ITEM_OBJ_TYPE, which carries item identity and audit columns such as item_id, object_version_number, creation and update audit fields, application_id, external_access_flag, item_name, description, text_string, and language_code. The user query "amv_char_varray_type" refers to the collection type declared at line 51 of the header: TYPE AMV_CHAR_VARRAY_TYPE IS TABLE OF VARCHAR2(4000). A companion type, AMV_NUMBER_VARRAY_TYPE IS TABLE OF NUMBER, is declared at line 53. These varray/table types are used to pass multi-value lists (for example, batches of item identifiers or character-based keyword values) into and out of the API procedures.

Key Procedures and Functions

The package exposes 26 documented procedures and functions grouped by functional area:

• Item lifecycle: CREATE_ITEM, UPDATE_ITEM, DELETE_ITEM, GET_ITEM, and FIND_ITEM provide the core CRUD and search operations against content items.
• Keyword management: ADD_ITEMKEYWORD, DELETE_ITEMKEYWORD, REPLACE_ITEMKEYWORD, and GET_ITEMKEYWORD maintain the searchable keyword associations for an item.
• Author management: ADD_ITEMAUTHOR, DELETE_ITEMAUTHOR, REPLACE_ITEMAUTHOR, and GET_ITEMAUTHOR maintain authorship metadata.
• File/attachment handling: ADD_ITEMFILE, DELETE_ITEMFILE, REPLACE_ITEMFILE, and GET_ITEMFILE manage file attachments linked to items.
• Utility and message functions: GET_USERMESSAGE and GET_USERMESSAGE2 retrieve user-facing messages (typically from the FND message dictionary), while GET_CHANNELSPERITEM returns the channels associated with a given item, supporting channel/item matching logic.

The package header notes that perspective and content-type handling reside in amv_perspective_pvt and amv_contenttype_pvt, and that author/keyword APIs also exist in jtf_item_pub. AMV_ITEM_PUB adds user privilege checking on top of these lower-level routines.

Tables Accessed

Through APPS synonyms, the package references the following objects:

• AMV_C_CHL_ITEM_MATCH — channel-to-item match records supporting GET_CHANNELSPERITEM.
• AMV_U_ACCESS — user access and privilege data used for the package's added privilege checks.
• AMV_U_MY_CHANNELS — user-specific channel subscriptions relevant to item/channel resolution.
• JTF_AMV_ATTACHMENTS — attachment repository backing the Add/Delete/Replace/Get_ItemFile procedures.
• FND_LOBS — large object storage for attachment and text content.
• JTF_RS_GROUP_MEMBERS — resource group membership used in access or assignment resolution.
• PLITBLM — PL/SQL index-by table utility, loadable for manipulating in-memory collections such as AMV_CHAR_VARRAY_TYPE.

Usage Notes

AMV_ITEM_PUB is an API-classified (PUB) package intended for supported invocation from Oracle Forms, concurrent programs, and custom PL/SQL code that needs to create or maintain MES content items without direct DML. Because the package enforces user privilege checking through AMV_U_ACCESS and related tables, callers must run in an FND session context with appropriate user and responsibility initialization. The package is referenced by three other packages, indicating it acts as a hub for item-level operations invoked by higher-level content management modules. When invoking list-based parameters, callers should construct AMV_CHAR_VARRAY_TYPE or AMV_NUMBER_VARRAY_TYPE collections to pass multi-value sets, ensuring compatibility with the API's declared signatures. Customizations should always call the public procedures rather than insert into JTF_AMV_ATTACHMENTS or AMV_C_CHL_ITEM_MATCH directly, so that audit columns and privilege validation remain consistent. The header history indicates the package has been progressively refactored to delegate to JTF AMV item APIs, and later releases introduced utility functions (GET_USERMESSAGE2, GET_CHANNELSPERITEM) beyond the original header comment list.