Search Results load_associations

Overview

IBC_CITEM_RUNTIME_PVT is a private PL/SQL package in the APPS schema that supports the runtime infrastructure for Oracle iStore / Oracle Content Items (IBC) functionality in Oracle E-Business Suite 12.1.1 and 12.2.2. Content items in EBS are structured, versioned, translatable storefront content elements — titles, images, rich text blocks, style associations, and compound relationships between reusable content assets. This package sits beneath the public API layer, IBC_CITEM_RUNTIME_PUB, and performs the heavy-lifting logic that the public package exposes to callers. Its classification as a PVT (private) package indicates it is not intended for direct invocation by external code, forms, or concurrent programs; instead, it is consumed internally by the corresponding PUB package and by the IBC_STYLESHEETS_GRP style-sheet group logic. The package encapsulates validation, metadata retrieval, XML generation, bulk loading, translated-content loading, version-number resolution, and association loading for content items.

Key Procedures and Functions

• VALIDATE_CITEM — Performs validation logic on a content item, confirming required attributes and structural integrity before persistence or publication.
• VALIDATE_START_END_DATE — Validates effective start and end dates associated with a content item or its version, ensuring date-range consistency.
• GET_CITEM_META — Retrieves metadata describing a content item, supporting the metadata-driven rendering and administrative display of content attributes.
• GET_CITEM_XML — Produces an XML representation of a content item, typically consumed by storefront presentation or integration layers.
• BULK_LOAD — Loads content items in bulk, supporting batch import or replication operations; leverages collection types such as JTF_VARCHAR2_TABLE_100 and JTF_NUMBER_TABLE.
• LOAD_TRANSLATED_CONTENT_ITEMS — Loads translated content item data into the translation tables (IBC_CITEM_VERSIONS_TL), enabling multi-language storefront content.
• LOAD_CITEM_VERSION_NUMBER — Resolves and loads the correct version number for a content item, coordinating with IBC_CITEM_VERSIONS_B.
• LOAD_ASSOCIATIONS — Loads associations between content items, using the IBC_ASSOCIATIONS and IBC_COMPOUND_RELATIONS structures that model compound and related content.

Nine documented procedures/functions are listed; the eighth, together with the others above, forms the operational core invoked by IBC_CITEM_RUNTIME_PUB.

Tables Accessed

• IBC_CONTENT_ITEMS — The primary content item master, read and written during loading and validation.
• IBC_CITEM_VERSIONS_B / IBC_CITEM_VERSIONS_TL — Base and translated version records; the TL table supports multilingual content.
• IBC_CITEM_VERSION_LABELS — Stores labels used to identify and select content-item versions.
• IBC_ASSOCIATIONS / IBC_COMPOUND_RELATIONS — Model relationships and compound structures among content items, populated by LOAD_ASSOCIATIONS.
• FND_LOOKUP_VALUES — Provides reference lookup values used for validation and display.
• DBMS_LOB / PLITBLM — Utility packages for LOB handling and PL/SQL table management during XML generation and bulk operations.

Dependencies also include FND_API (for the standard API error-handling framework) and JTF_CLOB_TABLE, JTF_NUMBER_TABLE, and JTF_VARCHAR2_TABLE_100 (for bulk parameter passing).

Usage Notes

Because IBC_CITEM_RUNTIME_PVT is a private package, it is not invoked directly from Oracle Forms, concurrent programs, or custom integrations. It is referenced by IBC_CITEM_RUNTIME_PUB (the public API entry point), by the IBC_STYLESHEETS_GRP concurrent program group, and recursively by itself. Callers requiring content-item validation, metadata retrieval, XML generation, bulk loading, translated-content loading, version resolution, or association loading should route through IBC_CITEM_RUNTIME_PUB, which wraps this private logic with the FND_API standard error and message conventions. In both 12.1.1 and 12.2.2, the package remains VALID and functions identically as part of the content-item runtime stack. Custom code should never call the private routines directly, as signatures and behavior are subject to change without public-API notice.