Search Results check_category_exists

Overview

IBE_DSPMGRVALIDATION_GRP is a PL/SQL validation package owned by the APPS schema within the Oracle iStore (IBE) product family. Its declared API classification is GRP, indicating that it functions as a grouped collection of reusable validation routines rather than a transactional business API. The package is defined with AUTHID CURRENT_USER and exposes a single constant, g_api_version, set to 1.0, along with the package name constant g_pkg_name.

The core business purpose of IBE_DSPMGRVALIDATION_GRP is to centralize existence, type, and relationship validation logic used by the iStore Deliverable and Display Manager subsystem. Deliverables in iStore represent reusable presentation content such as templates and media, and they are associated with catalog categories, items, sections, contexts, master sites, and attachments. Before any of these associations or objects are created, modified, or published, the application must confirm that the referenced entities actually exist and that their types are legal. This package encapsulates that checking logic so that multiple callers apply identical rules and return consistent error messages onto the FND message stack.

Key Procedures and Functions

The package exposes thirty documented procedures and functions. The deliverable-centric validators include CHECK_DELIVERABLE_EXISTS, which returns TRUE when a deliverable identifier exists, optionally qualified by an object version number, and raises the message IBE_DSP_DLV_NOT_EXISTS when not found; CHECK_DELIVERABLE_TYPE_EXISTS, which verifies that a deliverable matches a valid type such as TEMPLATE or MEDIA and pushes IBE_DSP_DLV_TYPE_NOT_EXISTS on failure; and CHECK_ITEM_DELIVERABLE, CHECK_CATEGORY_DELIVERABLE, CHECK_ATTACHMENT_DELIVERABLE, and CHECK_DEFAULT_ATTACHMENT, which validate deliverable associations against items, categories, attachments, and default attachment assignments respectively.

Object and content validators include CHECK_LGL_OBJECT_EXISTS and CHECK_LGL_CTNT_ID_EXISTS, which confirm legal content objects and content identifiers; CHECK_VALID_OBJECT_TYPE, which validates object type codes; and CHECK_ATTACHMENT_EXISTS. Hierarchy and relationship validators include CHECK_CATEGORY_EXISTS, CHECK_ITEM_EXISTS, CHECK_SECTION_EXISTS, CHECK_ROOT_SECTION_EXISTS, CHECK_CTG_TPL_RELATION_EXISTS, and CHECK_MASTER_MSITE_EXISTS. Context-related validators include CHECK_CONTEXT_EXISTS, CHECK_CONTEXT_ACCESSNAME, CHECK_VALID_CONTEXT_TYPE, and CHECK_CONTEXT_TYPE_CODE. The specification additionally declares exceptions such as context_accname_req_exception, context_req_exception, category_req_exception, template_req_exception, lglctnt_id_req_exception, msite_req_exception, and physmap_not_exists_exception, which signal mandatory-attribute and physical-map failures.

Tables Accessed

The package reads through APPS synonyms across iStore, Oracle Marketing, and Oracle Inventory. Deliverable and context data is read from IBE_DSP_CONTEXT_B, IBE_DSP_OBJ_LGL_CTNT, IBE_DSP_SECTIONS_B, IBE_DSP_TPL_CTG, and IBE_DSP_LGL_PHYS_MAP. Master site validation uses IBE_MSITES_B and IBE_MSITE_LANGUAGES. Attachment validation uses JTF_AMV_ITEMS_B and JTF_AMV_ATTACHMENTS. Catalog and item validation uses MTL_CATEGORIES, MTL_ITEM_CATEGORIES, and MTL_SYSTEM_ITEMS. Lookup validation, such as valid type and context codes, reads FND_LOOKUP_VALUES.

Usage Notes

IBE_DSPMGRVALIDATION_GRP is typically invoked internally by iStore deliverable management forms, concurrent programs, and the seven packages documented as referencing it, rather than being called directly by end users. Custom code extending iStore deliverable behavior should call these validators before performing inserts or updates, checking the boolean return value and inspecting the FND message stack for the pushed error message.