Results for “associate_items_to_section”

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

Overview

IBE_DSP_HIERARCHY_SETUP_PVT is a private PL/SQL package in the Oracle E-Business Suite iStore (IBE) module responsible for managing the hierarchy of sections that make up a storefront's navigational and content structure. Within the Oracle EBS 12.1.1 and 12.2.2 architectures, it functions as the backend persistence layer for the personalization framework, allowing administrators and the storefront application to save, retrieve, update, and delete sections, logically associate items and mini-sites with those sections, and manage the physical mapping of content. The package body header identifies it as a "Private API for saving, retrieving and updating sections," with a noted purpose to be used by all sources for persisting personalized queries within the personalization framework.

The package name contains a typographical variant in the source: the constant G_PKG_NAME is set to 'IBE_DSP_HIERAHCY_SETUP_PVT', while the actual object and file (IBEVCHSB.pls) reference the correct spelling. This package is referenced by six other packages, confirming its role as a shared, foundational dependency rather than an entry point invoked directly by end users.

Key Procedures and Functions

The package exposes 25 documented procedures and functions, organized around the core CRUD and association operations for storefront sections:

• Section lifecycle: CREATE_HIERARCHY_SECTION, UPDATE_HIERARCHY_SECTION, and DELETE_HIERARCHY_SECTION manage the creation, modification, and removal of section records in the hierarchy.
• Item and section association: ASSOCIATE_ITEMS_TO_SECTION, ASSOCIATE_SECTIONS_TO_ITEM, ASSOCIATE_MSITES_TO_SECTION, ASSOCIATE_ROOT_SCT_TO_MSITE, and ASSOCIATE_MSITES_TO_ITEM establish relationships between store items, mini-sites, and sections. DISASSOCIATE_SCTS_TO_ITMS and DISASSOCIATE_SCTS_ITMS remove those associations.
• Structural manipulation: CUT_AND_PASTE_SECTION supports moving sections within the hierarchy, while UPDATE_DELETE_SCT_SCTS and UPDATE_HIERARCHY_ITEM, UPDATE_HIERARCHY_LAYOUT_MAP handle updates to nested sections, items, and layout mappings.
• Content and copy operations: COPY_SECTION_REF_CONTENT, COPY_LOGICAL_MEDIA, REFERENCE_SECTION_CONTENT, SAVE_PHYSICAL_MAP, and SAVE_OBJECT_LOGICAL_CONTENT handle the copying, referencing, and physical/logical storage of section content and media.
• Lookup utility: GET_MASTER_MINI_SITE_ID retrieves the master mini-site ID and its root section ID, raising FND_API.G_EXC_ERROR if no master mini-site is found.

The header history notes modifications for NOCOPY (performance), debug tracing, exception handling, and a 2004 performance fix removing literals from cursor queries.

Tables Accessed

The package reads and writes several core iStore base and translation tables via APPS synonyms:

• IBE_DSP_SECTIONS_B and IBE_DSP_SECTIONS_TL — base and translated section definitions.
• IBE_DSP_SECTION_ITEMS — associations between sections and items.
• IBE_DSP_MSITE_SCT_SECTS and IBE_DSP_MSITE_SCT_ITEMS — mini-site to section and item relationships.
• IBE_MSITES_B — mini-site definitions, queried to identify the master mini-site.
• IBE_DSP_LGL_PHYS_MAP and IBE_DSP_LGL_PHYS_MAP_S1 — logical-to-physical content mappings.
• IBE_DSP_OBJ_LGL_CTNT and IBE_DSP_OBJ_LGL_CTNT_S1 — object logical content storage.
• IBE_DSP_CONTEXT_B, FND_LANGUAGES, JTF_AMV_ITEMS_B, DUAL, and PLITBLM — supporting context, language, media item, and utility lookups.

Usage Notes

As a PVT-classified API, this package is not intended for direct invocation by external or custom code; it is called internally by the iStore storefront and the personalization framework, and is referenced by six other packages. It is typically exercised through the iStore administrative UI (section management and personalization screens), concurrent programs that rebuild or copy store content, and the runtime storefront engine that renders sections and their associated items and mini-sites. Customizations should treat it as an internal contract and prefer documented public APIs, since procedure signatures and behavior may change between patch levels in 12.1.1 and 12.2.2.