Search Results media_template_mig
Overview
The APPS.IBE_M_MIGRATION_PVT package is a private PL/SQL utility within the Oracle iStore (IBE) application module of Oracle E-Business Suite. Its name and structure indicate that it performs migration-related processing, moving or transforming content, context, and media configuration data between representations or releases within the iStore content management framework. The _PVT suffix designates it as a private package, meaning it is not published as a public API and is intended for internal invocation by other iStore components or by migration routines rather than by external custom code. The package is owned by the APPS schema and is documented as VALID in ETRM for both 12.1.1 and 12.2.2. It depends on FND_PROFILE, the standard Oracle Applications profile option facility, which suggests migration behaviour may be conditioned on profile settings such as operating unit or site-level configuration. It is referenced by no other packages, confirming its role as a terminal worker in the migration call chain.
Key Procedures and Functions
The ETRM metadata documents five procedures or functions within the package. Parameter lists are not published, so only their purposes are described here.
- CONTEXT_MIG — Handles migration of display context definitions. It targets the
IBE_DSP_CONTEXT_Btable and its associated legal/physical mapping structures, transferring context metadata into the current model. - MEDIA_TEMPLATE_MIG — Migrates media template definitions associated with iStore content items, supporting the transformation of template-driven media rendering configuration.
- ATTACHMENT_MIG — Migrates attachment records, moving attachment metadata and linkage between legacy and current attachment storage such as the
JTF_AMV_ATTACHMENTStable. - ATTACHTYPE — Determines or returns the attachment type classification used during attachment migration, allowing
ATTACHMENT_MIGto route records to the appropriate target. - OCMMIGRATION — Performs the broader content-item migration, orchestrating movement of content items and their version data across the
IBC_CONTENT_ITEMSandIBC_CITEM_VERSIONS_Bstructures.
Tables Accessed
The package reads and writes through APPS synonyms for the following documented tables:
IBC_CITEM_VERSIONS_BandIBC_CITEM_VERSION_LABELS— base and label version records for iStore content items.IBC_CONTENT_ITEMS— the primary content item registry.IBE_DSP_CONTEXT_BandIBE_DSP_LGL_PHYS_MAP/IBE_DSP_LGL_PHYS_MAP_S1— display context and legal-to-physical mapping definitions.IBE_DSP_OBJ_LGL_CTNT— objects related to legal content within display contexts.IBE_MIGRATION_HISTORY— the audit trail recording which migration steps have executed.JTF_AMV_ATTACHMENTSandJTF_AMV_ITEMS_B— attachment and media item storage used by the AMV framework.DUALandPLITBLM— standard Oracle utility/pseudo objects used for control flow and context handling.
Usage Notes
Because IBE_M_MIGRATION_PVT is a private package and is referenced by no other documented packages, it is normally invoked indirectly rather than called from custom code. Typical invocation paths include iStore migration concurrent programs, internal setup routines triggered during upgrade or configuration, or other private iStore packages that orchestrate migration phases. Its reliance on FND_PROFILE indicates that profile option values influence its behaviour, so administrators should verify relevant iStore and site profile settings before running migration. The IBE_MIGRATION_HISTORY table provides a record of execution, which can be queried to confirm that migration steps completed. Direct calls from customer extensions are not recommended, as the package forms part of Oracle's internal iStore implementation and its interface may change between releases. Database administrators and functional consultants should treat it as a diagnostic and reference object when troubleshooting iStore content migration issues.