Search Results ibe_physicalmap_grp




Overview
Explore in AI Chat

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

Overview

IBE_PHYSICALMAP_GRP is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as a Group (GRP) type API. It forms part of the Oracle iStore (IBE) module, which provides the storefront and commerce infrastructure within EBS. The package encapsulates the business logic that governs the relationship between iStore site content and physical media or deliverable mappings. In practice, it manages the association of deliverables, attachments, and multi-site (MSITE) records to a physical map hierarchy that determines how content is organized and presented across localized storefronts.

The Group classification indicates that the package exposes a collection of related procedures that operate as a cohesive unit of business functionality, rather than a single transactional API. It is a dependency-rich object: it references FND_API (the Oracle Application Object Library foundation API used for consistent error handling and message propagation), STANDARD, and internally calls its own procedures. The package is also referenced by several sibling iStore packages, including IBE_ATTACHMENT_GRP, IBE_DELIVERABLE_GRP, IBE_DSP_HIERARCHY_SETUP_PVT, IBE_MSITE_GRP, and its wrapper IBE_PHYSICALMAP_GRP_W, confirming that it is a central utility layer for physical map maintenance rather than an end-user entry point.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents fourteen procedures and functions associated with this package. Their purpose, based on naming and the object's role, is summarized below. Parameter lists are intentionally omitted as they are not documented in the source metadata.

  • SAVE_PHYSICALMAP — Persists a physical map record, creating or updating the mapping between a logical site and its physical counterpart.
  • DELETE_PHYSICALMAP — Removes a physical map record and its dependent associations.
  • DELETE_ATTACHMENT — Deletes an attachment linked to a physical map or site.
  • DELETE_DELIVERABLE — Removes a deliverable association from the mapping.
  • DELETE_MSITE — Deletes a multi-site (MSITE) record tied to the physical map.
  • DELETE_MSITE_LANGUAGE — Removes the language-specific rendition of an MSITE entry.
  • DELETE_ATTACHMENT_MSITE — Deletes the intersection of an attachment and an MSITE record.
  • DELETE_DLV_ALL_ALL — A bulk deletion routine clearing deliverable mappings across all applicable scopes.
  • REPLACE_CONTENT — Substitutes existing mapped content with updated content, typically during propagation or re-layout operations.
  • LOAD_SEED_ROW — Loads a seed data row as part of the application's initial data installation.
  • LOAD_ROW — Inserts a row during data migration, upgrade, or bulk loading activities.

Tables Accessed

The package reads and writes through APPS synonyms for the following tables, each serving a distinct purpose within the physical map domain:

  • IBE_DSP_LGL_PHYS_MAP — The primary base table holding logical-to-physical map definitions.
  • IBE_DSP_LGL_PHYS_MAP_S1 — A secondary/supplementary table, likely a staging or sequence-supporting structure for the same mapping.
  • IBE_MSITE_LANGUAGES — Stores language definitions for multi-site storefronts, used when handling localization-specific deletions.
  • JTF_AMV_ATTACHMENTS — The shared attachment repository used by Oracle's media/attachment framework, supporting the attachment deletion procedures.
  • DUAL — The standard single-row utility table, used for validation or PL/SQL expression evaluation.
  • PLITBLM — The PL/SQL integer table type used internally for array or bulk operations.

Usage Notes

IBE_PHYSICALMAP_GRP is not typically invoked directly by end users. It is consumed by higher-level iStore packages such as IBE_ATTACHMENT_GRP, IBE_DELIVERABLE_GRP, and IBE_MSITE_GRP during administrative maintenance of storefront content, including iStore administration forms and concurrent programs that propagate or reorganize physical map data. The wrapper IBE_PHYSICALMAP_GRP_W provides the interface layer called by those dependent packages.

Because it manipulates seed and configuration data, the LOAD_ROW and LOAD_SEED_ROW procedures are relevant during installation, patching, and upgrade cycles. Customizations should avoid modifying this package directly, as it is an Oracle-owned object and any changes would be overwritten by patches. Extensions should instead call its public procedures through supported APIs or the wrapper package to preserve upgrade integrity.