Results for “ibe_deliverable_expimp_pvt”

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

Overview

IBE_DELIVERABLE_EXPIMP_PVT is a private PL/SQL package that resides in the APPS schema and forms part of Oracle iStore's deliverable export/import infrastructure within Oracle E-Business Suite. In release 12.1.1 and 12.2.2, iStore relies on a set of deliverable objects to move merchandising and content configuration between environments, and this package provides the low-level programmatic logic that supports the loading and persistence of deliverable templates. The object carries a status of VALID and is classified as a PVT package, meaning it is intended for internal use by the iStore application layer rather than as a public integration API. Its principal responsibility is to accept template mapping information supplied by the caller and write the resulting records into the underlying iStore deliverable mapping tables, so that a merchant's catalog structure, mapping rules, or content associations can be reproduced consistently across instances. Because it is a private implementation package, it should be regarded as one of the internal building blocks of the broader iStore deliverable import process rather than a supported extension point.

Key Procedures and Functions

The documented package metadata identifies a single public subprogram: SAVE_TEMPLATE_MAPPING. This procedure is the persistence routine for deliverable template mapping data. It receives mapping information from its caller and applies the appropriate insert or update logic against the deliverable mapping tables, subject to validation performed within the package.

• SAVE_TEMPLATE_MAPPING — Saves template mapping records for the iStore deliverable export/import process. It is the sole documented entry point exposed by the package specification and encapsulates the write logic required to persist a mapping definition.

No other procedures or functions are documented in the ETRM metadata for this object. Because the package specification is not publicly exposed, its full internal helper routines are not enumerated; the parameter list of SAVE_TEMPLATE_MAPPING is intentionally not reproduced here.

Tables Accessed

The package operates against the following tables, referenced through APPS synonyms:

• IBE_DSP_LGL_PHYS_MAP — the primary iStore deliverable mapping table, holding the logical-to-physical mapping definitions that SAVE_TEMPLATE_MAPPING creates and maintains.
• IBE_DSP_LGL_PHYS_MAP_S1 — the associated sequence used to generate unique primary key values for new mapping rows inserted into the mapping table.
• JTF_AMV_ATTACHMENTS — the attachments table used by the shared JTF media/attachment framework, referenced for attachment associations tied to deliverable items.
• JTF_AMV_ITEMS_B — the base items table of the same framework, providing the item-level records that mapping or attachment rows relate to.
• DUAL — the standard single-row utility table used for scalar evaluations and sequence access within PL/SQL.
• PLITBLM — the standard PL/SQL binary integer table type used internally for bulk operations and PL/SQL table handling.

The dependency list also shows references to FND_API, JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, and the SYS STANDARD package. These indicate that the package uses the Oracle Application Object Library API error/message convention along with JTF collection types for passing structured parameter sets, rather than scalar arrays, into its routines.

Usage Notes

IBE_DELIVERABLE_EXPIMP_PVT is invoked by Oracle iStore application logic and by the deliverable export/import utility that moves merchandising configuration between EBS instances. The ETRM dependency report shows no other packages referencing it, confirming it is an internal, leaf-level utility rather than a shared service. In practice, administrators trigger the surrounding deliverable export/import functionality through iStore administrative pages or related concurrent processes; SAVE_TEMPLATE_MAPPING is then called to persist each mapping definition. Customizations should not call this package directly, since it is a private object whose signature and behaviour are subject to change without notice. Where the package is modified or its dependencies are invalidated, the standard EBS recompilation approach — recompiling the package specification and body with the APPS schema credentials — restores it to a VALID state.