Search Results check_context_exists

Overview

JTF_DSPMGRVALIDATION_GRP is a validation group (GRP) package in the Oracle E-Business Suite Applications (APPS) schema, operating with AUTHID CURRENT_USER. It belongs to the Oracle Marketing / Deliverables infrastructure family, specifically the JTF (Java Technology Framework) Deliverables and Digital Asset Management components that underpin attachment, media, template, and content management in Oracle EBS 12.1.1 and 12.2.2. The package centralizes the referential and business-rule validation logic used throughout the Deliverables Manager and Attachment Management subsystem, allowing callers to verify the existence, type, context, and relationships of deliverables, attachments, legal content, categories, sections, and multi-site records before committing data.

The header comment records a constant g_api_version := 1.0 and a g_pkg_name constant, consistent with the FND_API standard API framework. The package declares a set of named exceptions — including 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 — signalling that required-attribute and mapping failures are surfaced as structured errors rather than generic Oracle exceptions.

Key Procedures and Functions

The package exposes 29 documented functions. These fall into logical validation families:

• Deliverable validations: CHECK_DELIVERABLE_EXISTS returns true when a deliverable identifier exists, optionally constrained by object version number, and pushes JTF_DSP_DLV_NOT_EXISTS when absent. CHECK_DELIVERABLE_TYPE_EXISTS confirms that a deliverable matches a valid type (TEMPLATE or MEDIA), optionally scoped by applicable-to, returning JTF_DSP_DLV_TYPE_NOT_EXISTS on failure.
• Legal content validations: CHECK_LGL_OBJECT_EXISTS, CHECK_LGL_CTNT_ID_EXISTS, and CHECK_LGL_OBJECT_EXISTS verify the existence of legal objects and content identifiers in the deliverable legal context.
• Attachment validations: CHECK_ATTACHMENT_EXISTS, CHECK_ATTACHMENT_DELIVERABLE, and CHECK_DEFAULT_ATTACHMENT confirm that attachments exist, are associated with a valid deliverable, and correctly identify default attachments. The user search term "check_attachment_deliverable" corresponds directly to CHECK_ATTACHMENT_DELIVERABLE, the routine that validates the linkage between an attachment and its parent deliverable.
• Category, item, and section validations: CHECK_CATEGORY_EXISTS, CHECK_ITEM_EXISTS, CHECK_SECTION_EXISTS, CHECK_ROOT_SECTION_EXISTS, CHECK_CTG_TPL_RELATION_EXISTS, CHECK_ITEM_DELIVERABLE, and CHECK_CATEGORY_DELIVERABLE establish integrity across catalog structures.
• Context validations: CHECK_CONTEXT_EXISTS, CHECK_CONTEXT_ACCESSNAME, CHECK_VALID_CONTEXT_TYPE, and CHECK_CONTEXT_TYPE_CODE validate deliverable contexts and their access names.
• Master site validations: CHECK_MASTER_MSITE_EXISTS confirms the presence of a master multi-site record.
• Object type validations: CHECK_VALID_OBJECT_TYPE confirms the supplied object type is recognized.

Tables Accessed

Validation queries read from a defined set of base and interface tables via APPS synonyms: JTF_AMV_ATTACHMENTS and JTF_AMV_ITEMS_B for attachment and item data; JTF_DSP_CONTEXT_B for deliverable contexts; JTF_DSP_LGL_PHYS_MAP and JTF_DSP_OBJ_LGL_CTNT for legal-to-physical mapping and object legal content; JTF_DSP_SECTIONS_B for section hierarchies; JTF_DSP_TPL_CTG for template-category relationships; JTF_MSITES_B and JTF_MSITE_LANGUAGES for multi-site and language records; and the inventory masters MTL_SYSTEM_ITEMS, MTL_ITEM_CATEGORIES, and MTL_CATEGORIES for item and category validation. DUAL supports constant evaluation. These accesses are read-oriented, supporting existence checks rather than data manipulation.

Usage Notes

Because the package is a GRP group, it is invoked primarily by other PL/SQL APIs, forms, and concurrent programs within the Deliverables and Attachment framework rather than by end users directly. The metadata records that seven other packages reference it, confirming its role as a shared validation service. Typical invocation patterns include being called from Attachments forms before saving attachment-deliverable associations, from Deliverables Manager setup screens, and from custom extensions that must enforce the same integrity rules as the seeded application. Developers extending the system should call these functions rather than reproducing validation logic, and should handle the package's declared exceptions and message-stack errors (such as JTF_DSP_DLV_NOT_EXISTS) to present user-friendly feedback.