Search Results ibe_logicalcontent_grp




Overview
Explore in AI Chat

Overview

IBE_LOGICALCONTENT_GRP is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified in ETRM metadata as an API of type GRP (group/management package). It belongs to the iStore and Oracle iMarketing (IBE) module family, which manages web storefront content, deliverable definitions, and the logical organization of published content. The package provides the programmatic interface for creating, modifying, and removing logical content structures that ultimately map to displayable objects in the storefront.

Functionally, the package acts as a maintenance layer over logical content records, allowing administrative content to be grouped by context, category, section, item, and deliverable. The ETRM metadata records the package body as VALID in both Oracle EBS 12.1.1 and 12.2.2, and notes that it is not referenced by any other database object, indicating it is a top-level maintenance API rather than a shared utility consumed by other PL/SQL units. It does, however, depend on FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, and IBE_DSPMGRVALIDATION_GRP, confirming that it follows Oracle's standard API conventions for error handling, message publishing, and validation.

Key Procedures and Functions

The ETRM metadata documents seven public procedures or functions within this package body. Their names describe the logical content hierarchy they manage:

  • SAVE_DELETE_LGL_CTNT — The primary maintenance routine, handling persistence and deletion of logical content records, presumably dispatching to the more granular delete operations below.
  • DELETE_CONTEXT — Removes a logical content context, the highest-level grouping element in the logical content hierarchy.
  • DELETE_CATEGORY_DLV — Deletes the association between a category and a deliverable within the logical content model.
  • DELETE_SECTION — Removes a section node from the logical content structure.
  • DELETE_CATEGORY — Removes a category node from the logical content structure.
  • DELETE_ITEM — Removes an individual item belonging to a logical content section or category.
  • DELETE_DELIVERABLE — Removes a deliverable record associated with the logical content hierarchy.

Parameter lists are not exposed in the ETRM extract, so no signatures are reproduced here. Consistent with Oracle's GRP API pattern, each routine is expected to accept identifying keys for the record being manipulated and to raise or publish errors through FND_MSG_PUB rather than returning raw SQL errors.

Tables Accessed

The package body references two application tables through APPS synonyms:

  • IBE_DSP_OBJ_LGL_CTNT — The base table storing logical content records tied to display objects. This is the primary read/write target for the save and delete routines.
  • IBE_DSP_OBJ_LGL_CTNT_S1 — A secondary (likely sequence-backed or secondary index) structure associated with the same logical content entity; the user's search term corresponds to this object, and the metadata confirms it is directly referenced by the package body.
  • DUAL — Standard single-row utility table, typically used for sequence value retrieval or existence checks.
  • PLITBLM — The PL/SQL integer table type declared in the STANDARD package, used for PL/SQL table operations rather than data storage.

The package also depends on IBE_DSPMGRVALIDATION_GRP for validation logic and on the FND_API/FND_GLOBAL/FND_MESSAGE/FND_MSG_PUB stack for API error handling, globalization context, and message dictionary lookups.

Usage Notes

IBE_LOGICALCONTENT_GRP is a management API rather than a concurrent program. It is typically invoked from Oracle iStore administrative forms, from the iMarketing content management user interface, or from custom PL/SQL extensions that programmatically manipulate logical content structure. Because it is a GRP-classified API, it is intended for internal application use and should not be called directly by end users.

ETRM records that the package is referenced by nine other packages and references eight others (including itself), so changes to its behavior can ripple through the iStore content pipeline. Developers modifying or extending storefront content logic should invoke these delete routines only within a transaction that preserves referential integrity across the logical content hierarchy — context, category, section, item, and deliverable — since the granular delete procedures operate on individual levels of that structure. Error conditions are surfaced through the FND message stack, so callers should check FND_MSG_PUB after execution rather than relying solely on exceptions.