Search Results delete_itemauthor

Overview

JTF_AMV_ITEM_PUB is the public PL/SQL API for managing items and their related attributes within the Oracle E-Business Suite "JTF" (Java Toolkit Foundation) schema, specifically the AMV (Ask Me View / Knowledge Management) subsystem. The package is declared with AUTHID CURRENT_USER and is classified as a PUB interface, meaning it is intended for direct invocation by external callers, including Oracle Forms, concurrent programs, and custom extensions. It consolidates the create, read, update, and delete (CRUD) operations for knowledge items (content records) as well as for their associated keywords and authors, providing a single, supported entry point for manipulating the JTF_AMV_ITEMS_B base table and its satellites. The header comment confirms the package's stated purpose: "This package is a public API managing items (contents) and their related attributes in JTF." Functions relating to item files, perspectives, and content types were deliberately excluded and moved into separate packages (for example, the AMV MES-specific private packages amv_perspective_pvt and amv_contenttype_pvt), which keeps JTF_AMV_ITEM_PUB focused on the core item lifecycle. The package also defines global constants and PL/SQL collection/record types (number_tab_type, char_tab_type, and item_rec_type) that standardize the item data structure across the API.

Key Procedures and Functions

The ETRM 12.2.2 documentation records sixteen procedures and functions, grouped by the entity they manage.

• Item lifecycle: CREATE_ITEM, DELETE_ITEM, UPDATE_ITEM, and GET_ITEM provide the core maintenance operations for item/content records. DELETE_ITEM (relevant to the user's keyword-deletion interest, as it typically cascades or precedes removal of related keywords) removes an item and its dependent attribute rows.
• Keyword management: ADD_ITEMKEYWORD, DELETE_ITEMKEYWORD, REPLACE_ITEMKEYWORD, and GET_ITEMKEYWORD manage the association between items and keywords. DELETE_ITEMKEYWORD removes a specific keyword link from an item, while REPLACE_ITEMKEYWORD substitutes the entire keyword set for an item in a single call.
• Author management: ADD_ITEMAUTHOR, DELETE_ITEMAUTHOR, UPDATE_ITEMAUTHOR, and GET_ITEMAUTHOR maintain item authorship records.

The package also contains utility routines and the global constant G_VERSION (set to 1.0), plus the collection and record type definitions used to pass multi-row item and keyword data. No parameter lists are documented here, so callers should obtain signatures from the package specification.

Tables Accessed

The documented tables, all accessed through APPS synonyms, reflect the package's role in maintaining items and their attributes.

• JTF_AMV_ITEMS_B and JTF_AMV_ITEMS_B_S: the base and translated tables holding item content, names, descriptions, text strings, URL strings, status, effective dates, and ownership attributes.
• JTF_AMV_ITEM_KEYWORDS and JTF_AMV_ITEM_KEYWORDS_S: the keyword association tables read and written by the keyword routines, including DELETE_ITEMKEYWORD.
• JTF_AMV_ITEM_AUTHORS and JTF_AMV_ITEM_AUTHORS_S: the author association tables used by the author routines.
• JTF_AMV_ATTACHMENTS: referenced for item file/attachment linkage.
• FND_APPLICATION: looked up to resolve or validate the owning application.
• DUAL and PLITBLM: used for single-row reads and PL/SQL table (index-by table) handling within the API internals.

Usage Notes

JTF_AMV_ITEM_PUB is normally invoked from Oracle Forms-based knowledge management maintenance screens, from concurrent programs that load or synchronize item content, and from custom PL/SQL extensions that must create or maintain AMV items without writing directly to the underlying tables. Because keywords and authors are stored in separate child tables, the API enforces consistent handling — for instance, calling DELETE_ITEMKEYWORD rather than issuing a direct DML statement ensures the corresponding keyword rows are removed cleanly. The package is referenced by five other packages, so changes to its behavior can affect dependent modules; callers should therefore rely on the documented public procedures rather than the internal tables. When a user searches for "delete_itemkeyword," the relevant entry point is DELETE_ITEMKEYWORD, which targets the JTF_AMV_ITEM_KEYWORDS table. As with all PUB APIs in EBS, proper validation of item context, effective dates, and application ownership (FND_APPLICATION) should be performed before invocation.