Search Results replace_content

Overview

IBE_PHYSICALMAP_GRP is a PL/SQL package body owned by the APPS schema within Oracle E-Business Suite, classified as an API group (GRP) under the iStore/Electronic Commerce (IBE) module. It provides the consolidated programmatic interface for managing the physical mapping layer of the iStore catalog — the rules that translate logical catalog entities (sites, languages, deliverables, attachments) into their physical storage and presentation equivalents. In Oracle EBS 12.1.1 and 12.2.2 the package acts as the maintenance and seed-loading gateway for the IBE_DSP_LGL_PHYS_MAP and IBE_DSP_LGL_PHYS_MAP_S1 tables, wrapping validation logic, multi-language site handling, and attachment lifecycle operations behind a stable API surface. Because it is a group package rather than a single-purpose API, it aggregates related operations — save, delete, replace, and seed data loading — used by the iStore administration UI and by deployment utilities.

Key Procedures and Functions

The documented interface exposes fourteen procedures and functions, summarized below by purpose:

• SAVE_PHYSICALMAP — Persists a physical map definition, validating the row through IBE_DSPMGRVALIDATION_GRP before insert or update.
• DELETE_PHYSICALMAP — Removes a physical map record and its associated dependent rows.
• DELETE_ATTACHMENT — Deletes an attachment record from the JTF_AMV_ATTACHMENTS repository for a mapped entity.
• DELETE_DELIVERABLE — Removes a deliverable association from the physical map.
• DELETE_MSITE — Deletes a multi-site (MSITE) entry associated with the physical map.
• DELETE_MSITE_LANGUAGE — Removes a language-specific MSITE mapping from IBE_MSITE_LANGUAGES.
• DELETE_ATTACHMENT_MSITE — Deletes attachments attached at the multi-site level.
• DELETE_DLV_ALL_ALL — Purges deliverables across all sites and languages, used for bulk cleanup.
• REPLACE_CONTENT — Substitutes attachment or mapping content, typically used when re-pointing a physical map to updated media.
• LOAD_SEED_ROW — Loads a single seeded row (via FND_LOAD_UTIL) for configuration deployment.
• LOAD_ROW — Loads a physical map row from seed data during installation, upgrade, or patching.

All routines rely on FND_API for API-level return status handling, FND_MSG_PUB and FND_MESSAGE for error messaging, and FND_PROFILE/FND_GLOBAL for session context.

Tables Accessed

• IBE_DSP_LGL_PHYS_MAP — the base table storing logical-to-physical mapping definitions; written by SAVE_PHYSICALMAP and LOAD_ROW.
• IBE_DSP_LGL_PHYS_MAP_S1 — the corresponding DDL/sequence-support object referenced in the package dependencies, supporting key generation for the mapping table.
• IBE_MSITE_LANGUAGES — holds multi-site language associations; managed by the DELETE_MSITE_LANGUAGE routine.
• JTF_AMV_ATTACHMENTS — the attachments repository accessed through JTF_AMV_ATTACHMENT_PUB for attachment add/delete operations.
• DUAL and PLITBLM — utility references used for PL/SQL table and singleton queries.

Usage Notes

IBE_PHYSICALMAP_GRP is typically invoked from iStore administration forms, from concurrent programs performing catalog deployment, and from seed-data loading during installation or patching via FND_LOAD_UTIL. Custom code extending iStore catalog behavior should call these procedures rather than manipulating the underlying tables directly, in order to preserve validation and attachment-publisher consistency. Because it is documented as referenced by five other packages and not referenced by any database object itself, it represents a top-level maintenance layer. The object is VALID in both 12.1.1 and 12.2.2, and the referenced IBE_DSP_LGL_PHYS_MAP_S1 object matches the user search term "ibe_dsp_lgl_phys_map_s1".