Search Results replace_itemauthor

Overview

JTF_AMV_ITEM_PUB_W is the public wrapper package for the Oracle E-Business Suite Item Media/Attachment utility, part of the JTF (Common Technology Foundation) Advanced Media Viewers (AMV) module. Its business purpose is to provide a stable, invocable PL/SQL API for creating, updating, and retrieving "items" — the centrally stored content records (such as documents, images, or published media entries) that the AMV framework associates with product information, knowledge base articles, and catalog content. The package declared it as AUTHID CURRENT_USER, meaning all DML is executed with the privileges of the calling user, and it accesses the underlying AMV base tables through APPS synonyms.

The "_PUB_W" suffix indicates this is a public wrapper layer. The wrapper abstracts the underlying business logic of the JTF_AMV_ITEM_PUB base package, principally through Rosetta-generated table-copy shims that reconcile the PL/SQL nested-table datatypes used by the internal API with the generic JTF table types exposed to callers. This design supports Java/BC4J and concurrent-program integrations that communicate with PL/SQL through the Oracle Applications framework, where bulk data is passed as JTF_NUMBER_TABLE and JTF_VARCHAR2_TABLE_200 collections rather than native PL/SQL records.

Key Procedures and Functions

The ETRM repository documents fifteen procedures and functions in this package:

• ROSETTA_TABLE_COPY_IN_P1 / ROSETTA_TABLE_COPY_OUT_P1 — Rosetta-generated marshalling routines that copy data between the package's internal NUMBER_TAB_TYPE collection and the standard JTF_NUMBER_TABLE used by Java-facing APIs.
• ROSETTA_TABLE_COPY_IN_P2 / ROSETTA_TABLE_COPY_OUT_P2 — The equivalent marshalling routines for character data, copying between CHAR_TAB_TYPE and JTF_VARCHAR2_TABLE_200.
• CREATE_ITEM — Creates a new AMV item. Its signature follows the standard EBS public API convention (p_api_version, p_init_msg_list, p_commit, x_return_status, x_msg_count, x_msg_data) and returns the new x_item_id. The remaining parameters are generated placeholders (p6_a0 … p6_a26) because the underlying table has many columns.
• UPDATE_ITEM — Modifies an existing item identified by its item ID, using the same Standard API messaging pattern.
• GET_ITEM — Retrieves the attributes of a single item for display or downstream processing.
• ADD_ITEMKEYWORD / DELETE_ITEMKEYWORD / REPLACE_ITEMKEYWORD / GET_ITEMKEYWORD — Manage the keyword associations that drive search, categorization, and retrieval of AMV content. REPLACE_ITEMKEYWORD removes existing associations and applies a new set in one call.
• ADD_ITEMAUTHOR / DELETE_ITEMAUTHOR / REPLACE_ITEMAUTHOR / GET_ITEMAUTHOR — Manage author assignments for an item. REPLACE_ITEMAUTHOR is the procedure most directly relevant to the search term "replace_itemauthor": it re-sets the complete set of authors on a given item in a single transactional call, superseding whatever author rows previously existed.

Tables Accessed

The documented table reference for this package is PLITBLM (accessed through an APPS synonym). PLITBLM is the generic EBS "PL/SQL interface table for numbers" used by the Rosetta bulk-copy mechanism to stage NUMBER_TABLE data during multi-row transfers. The item, keyword, and author entities themselves reside in the underlying JTF_AMV_ITEM base tables, which the base package manipulates; the wrapper surfaces the DML through the PLITBLM staging path. No other tables are documented in the ETRM metadata for this wrapper.

Usage Notes

JTF_AMV_ITEM_PUB_W is invoked from Java/BC4J business components, Oracle Forms, and custom PL/SQL that need to create, maintain, or query AMV items and their keyword and author associations. The ETRM metadata records zero dependent packages, so it is a leaf-level public API rather than an internal building block. Callers should supply fnd_api.g_miss_char, fnd_api.g_miss_date, and the numeric miss sentinel for any parameter they do not intend to change, and should always check x_return_status against fnd_api.g_ret_sts_success before committing. Because the package runs AUTHID CURRENT_USER, grants on the APPS synonyms must be in place for the invoking account.