Search Results ibc_compound_relations_pkg




Overview

IBC_COMPOUND_RELATIONS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle iStore and Oracle iMarketing (IBC) product family, which manages catalog content, storefront configuration, and compound product relationships. The package encapsulates the data-access and maintenance logic for the IBC_COMPOUND_RELATIONS entity, a table that stores the defined relationships between a parent (compound) item and its constituent child items or related catalog entries.

In EBS 12.1.1 and 12.2.2 the package is documented as status VALID and is classified as an OTHER API, meaning it supports internal application logic rather than a formally published public API. Its primary business role is to provide a controlled, reusable layer for inserting, updating, locking, deleting, and seeding compound-relation records, ensuring that the underlying table is manipulated consistently by both runtime forms and seed-data loading routines.

Key Procedures and Functions

The ETRM metadata documents six procedures in this package. No parameter lists are published, so only their intent is described here.

  • INSERT_ROW — Creates a new record in the compound relations table, populating the relationship between a compound item and its associated child or related item.
  • LOCK_ROW — Acquires a row-level lock on an existing compound-relation record, typically used before performing an update or delete to prevent concurrent modification.
  • UPDATE_ROW — Modifies an existing compound-relation record, allowing attributes of the relationship to be changed while preserving the record identity.
  • DELETE_ROW — Removes an existing compound-relation record from the table, dissolving the defined association.
  • LOAD_ROW — Loads a single compound-relation record, generally as part of a bulk or seed-data loading process, translating external or seed definitions into table rows.
  • LOAD_SEED_ROW — Loads seeded (delivered) compound-relation data, used to establish baseline relationships shipped with the application during installation, upgrade, or seed-data refresh.

Tables Accessed

The package operates against three documented objects, referenced through APPS synonyms:

  • IBC_COMPOUND_RELATIONS — The primary table holding the parent-child or compound relationship definitions. It is the target of the insert, update, delete, and load operations.
  • IBC_COMPOUND_RELATIONS_S1 — A supplementary/sequence-related object associated with the compound relations entity, referenced to support record identification and integrity during row maintenance.
  • DUAL — The standard Oracle single-row utility table, typically used for validation, sequence retrieval, or conditional PL/SQL logic within the package.

Usage Notes

IBC_COMPOUND_RELATIONS_PKG is referenced by one other package, IBC_CITEM_ADMIN_GRP, which indicates that compound-relation maintenance is driven through the iStore catalog item administration flow. Administrators configuring storefront catalogs rely on this chain to define and maintain how compound items relate to their constituent entries without direct table manipulation.

In practice the package is invoked from the iStore administrative forms and from seed-data loading routines that populate IBC_COMPOUND_RELATIONS during installation, patching, or data refresh. Because the procedures are classified as OTHER rather than as a public API, custom development should treat them as internal interfaces: callers should favor the supported administrative UI or wrapper logic rather than invoking the procedures directly, as signatures and behavior are not guaranteed across releases. When writing seed or migration scripts, LOAD_ROW and LOAD_SEED_ROW are the appropriate entry points for inserting delivered relationship data, while INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW support interactive maintenance. Direct DML against the base table should generally be avoided to preserve the locking and integrity conventions enforced by the package.