Search Results is_itemidvalid

Overview

JTF_AMV_ITEM_PUB is the public PL/SQL package that governs the lifecycle of "items" stored in the Oracle EBS AMV (Application Media/Content) repository, part of the framework supporting attachments, keywords, and authorship metadata for content items. The package body, shipped as jtfpitmb.pls, exposes a controlled API surface used by other application modules to create, modify, retrieve, and delete content items and their associated auxiliary data. In Oracle EBS 12.1.1 and 12.2.2 the package resides in the APPS schema and is classified as a public API (PUB), meaning its procedures are intended to be invoked directly by external callers such as forms, concurrent programs, or custom extensions rather than being treated as internal implementation details.

The package operates within the FND message and content framework, maintaining referential integrity between item master records, their translations, keyword associations, author associations, and physical attachment records. The header comment indicates creation in late 1999, with the most recent revision noted in the source header as version 115.8.

Key Procedures and Functions

The documented API comprises sixteen public procedures and functions. The core item entity is managed through CREATE_ITEM, UPDATE_ITEM, DELETE_ITEM, and GET_ITEM, which together provide full CRUD semantics for records held in the item base and translation tables. Keyword relationships are managed by ADD_ITEMKEYWORD, DELETE_ITEMKEYWORD, REPLACE_ITEMKEYWORD, and GET_ITEMKEYWORD, allowing keyword sets to be attached, extended, fully replaced, or retrieved for a given item. Author relationships follow a parallel pattern with ADD_ITEMAUTHOR, DELETE_ITEMAUTHOR, REPLACE_ITEMAUTHOR, and GET_ITEMAUTHOR. Internally the body also declares private utility functions — CURRENT_USER_ID and CURRENT_LOGIN_ID (both delegating to FND_GLOBAL), check_lookup_exists, and an application-id validator such as Is_ApplIdValid — which perform validation and context resolution. These private routines, including the pattern answering the "is_itemidvalid" style of validation query, rely on cursor- and lookup-based checks before allowing a public operation to proceed.

Tables Accessed

The package reads and writes a defined set of tables accessible through APPS synonyms. JTF_AMV_ITEMS_B and its translation table JTF_AMV_ITEMS_B_S hold the base item records. JTF_AMV_ITEM_KEYWORDS and JTF_AMV_ITEM_KEYWORDS_S store keyword associations and their translations, while JTF_AMV_ITEM_AUTHORS and JTF_AMV_ITEM_AUTHORS_S store author associations similarly. JTF_AMV_ATTACHMENTS holds the linked attachment records. FND_APPLICATION is queried for application-id validation, DUAL serves as the standard single-row source, and PLITBLM is referenced in the package's table usage footprint. Because translation tables are paired with base tables, write operations must maintain consistency across both.

Usage Notes

JTF_AMV_ITEM_PUB is typically invoked from EBS forms and concurrent programs that maintain content items, and it is referenced by five other packages, indicating that downstream APIs depend on its behavior for maintaining the AMV repository. Custom code should call the public procedures rather than performing direct DML against the underlying JTF_AMV_ITEMS tables, because the package enforces validation against FND_APPLICATION and lookup values, manages the base/translation pairing, and applies FND_GLOBAL context for user and login identity. Because validation helpers such as Is_ApplIdValid are private, external callers cannot invoke them directly; validity enforcement therefore occurs transparently within the public CRUD and association procedures.