Results for “ibe_dsp_hierarchy_setup_pub”

41 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.IBE_DSP_HIERARCHY_SETUP_PUB package body is a public, source-facing API within the Oracle iStore (IBE) personalization and catalog publishing framework. Its stated purpose is to provide a private API for saving, retrieving, and updating sections, while simultaneously serving as a publicly accessible package intended for use by all sources for saving, retrieving, and updating personalized queries within the personalization framework. In practice, this package is the programmatic entry point through which iStore storefront hierarchies and the logical content assigned to their nodes are created and maintained.

The package is owned by APPS and is classified as PUB, meaning its procedures constitute a supported interface for external invocation rather than an internal-only helper unit. The header comment identifies the file as IBEPCHSB.pls and records a creation date of 09/05/00 by VPALAIYA, with a later modification by ABHANDAR on 09/17/05 at version 120.5. The package exposes three documented procedures and is referenced by one other package, confirming it is a dependency within the broader iStore hierarchy setup stack.

Key Procedures and Functions

  • CREATE_SECTION — Creates a section within the catalog hierarchy. This is the procedure most closely associated with the search term create_hierarchy_section; the API name recorded in the internal comments is Create_Hierarchy_Section, and the local constant l_api_name is set to that same value. The comments state the API version as 1.0 across initial, previous, and current versions, with no prerequisites. Its parameter block follows the standard EBS API convention: p_api_version, p_init_msg_list, and p_commit as IN parameters, x_return_status, x_msg_count, and x_msg_data as OUT parameters, a p_hierachy_section_rec record of type SECTION_REC_TYPE carrying the section definition, and x_section_id returning the identifier of the newly created section.
  • CREATE_SECTION_ITEMS — Populates a previously created hierarchy section with the items or content nodes that belong to it. This procedure addresses the assignment stage of hierarchy setup, distinct from the section header creation handled above.
  • CREATE_OBJECT_LOGICAL_CONTENT — Establishes the logical content relationship for an object within the personalization framework, linking persisted content to its logical representation so that personalized queries and hierarchy content resolve correctly at runtime.

Tables Accessed

The documented table reference for this package is PLITBLM, accessed through an APPS synonym. PLITBLM is the iStore personalization storage table family used to persist personalized query definitions and related hierarchy personalization records. Because this package exists to save, retrieve, and update sections and the queries associated with them, all persistence for the section header and its associated content is written to and read from this table. No other base tables are documented in the ETRM metadata for this object.

Usage Notes

This package is invoked programmatically rather than through a direct form or concurrent program interface. Typical callers include the iStore administration and personalization UI layers, which call CREATE_SECTION first to obtain a section identifier and then call CREATE_SECTION_ITEMS to attach content, and other packages that depend on this unit as a shared hierarchy service. Custom code should call the procedures with the standard EBS API conventions: pass p_api_version as 1.0, set p_init_msg_list to FND_API.G_TRUE when a fresh message stack is required, and set p_commit to FND_API.G_TRUE only when the caller is prepared to commit the transaction. Callers must inspect x_return_status for FND_API.G_RET_STS_ERROR or FND_API.G_RET_STS_UNEXP_ERROR and extract diagnostics through x_msg_count and x_msg_data. The same behavior applies in both Oracle EBS 12.1.1 and 12.2.2, where the package signature and public classification are unchanged.