Search Results ibe_dsp_hierarchy_setup_pvt




Overview
Explore in AI Chat

Overview

IBE_DSP_HIERARCHY_SETUP_PUB is a public PL/SQL package in the APPS schema that supports the Oracle iStore (IBE) content and hierarchy setup infrastructure within Oracle E-Business Suite 12.1.1 and 12.2.2. The package name follows the standard EBS API naming convention: the IBE prefix identifies the iStore application, DSP denotes the display/storefront content subsystem, and the _PUB suffix designates it as a published, callable interface intended for external invocation, as opposed to the companion _PVT package that contains the private implementation logic.

Functionally, the package serves as the public entry point for programmatically creating and maintaining the structural elements of an iStore storefront hierarchy. These structural elements include store sections, the items assigned to those sections, and the logical content objects associated with the display hierarchy. This enables administrators, setup utilities, and migration routines to build or refresh storefront navigation and content organization without manual data entry through the iStore administration UI.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions exposed by this package:

  • CREATE_SECTION — Creates a section within the iStore display hierarchy. A section represents a navigational or organizational node in the storefront structure, forming the parent context under which content items are subsequently arranged.
  • CREATE_SECTION_ITEMS — Creates or assigns items associated with a section. This procedure populates the membership of a section, linking the section node to the products, content, or display entries it is intended to present.
  • CREATE_OBJECT_LOGICAL_CONTENT — Creates the logical content record associated with an object in the hierarchy. This establishes the content-side representation that links a display object to the logical content model used by iStore.

No parameter lists are documented in the ETRM metadata for these routines, and they should not be assumed; signature details must be confirmed against the installed package specification in the target environment.

Tables Accessed

The only table documented as referenced through APPS synonyms is PLITBLM. This is a multilingual (translated) base table used within the iStore/PLI content framework, and access to it indicates that the procedures in this package persist hierarchy or content definitions that may carry translated text attributes. Writes to this table through the package would support the storage of section, item, or logical content definitions in a language-aware manner consistent with EBS MLS conventions.

Usage Notes

IBE_DSP_HIERARCHY_SETUP_PUB is typically invoked as part of iStore storefront setup, content migration, and bulk configuration activities rather than through routine runtime storefront browsing. It would commonly be called from custom PL/SQL routines, setup or migration scripts, or concurrent programs that automate the construction of store hierarchies across environments. Because it depends on FND_API and the STANDARD package, it participates in the standard EBS API error-handling and messaging framework, so callers should observe the conventional API return-status and message-handling patterns.

The documented dependency further shows that IBE_DSP_HIERARCHY_SETUP_PVT references this public package, and the public package is referenced by one other package. This confirms the standard EBS public/private split: the _PUB layer presents the supported interface while the _PVT layer carries internal logic. Direct calls should be directed to the _PUB routines, not the private implementation. Because the user query referenced ibe_dsp_hierarchy_setup_pvt, note that the PVT package is internal and should not be called directly; it is reached through the published procedures described above. As with any EBS API, validate the package status as VALID and confirm the current specification before use, and test in a non-production instance before deploying hierarchy changes to a live storefront.