Search Results ibc_citem_runtime_pub




Overview
Explore in AI Chat

Overview

The APPS.IBC_CITEM_RUNTIME_PUB package body is a public runtime API within the Oracle EBS Content Integration framework, part of the product family historically delivered under the iStore/IBC module set. Its central responsibility is the assembly and delivery of content item metadata at runtime. Rather than representing a transactional or data-maintenance interface, this package functions as a read-oriented retrieval layer: it produces metadata about content items, their versions, their renditions, and their associations so that upstream callers can render, publish, or otherwise consume managed content.

The package is classified as a PUB package in the documented API classification, which indicates it forms part of the supported external call surface for the Content Integration schema. The companion private implementation logic resides in IBC_CITEM_RUNTIME_PVT, which this package body references. Supporting utility and validation routines are drawn from IBC_UTILITIES_PVT and IBC_VALIDATE_PVT, while error and message handling relies on the standard FND API stack: FND_API, FND_MESSAGE, and FND_MSG_PUB. Large object handling for XML payload assembly is delegated to DBMS_LOB. The package status is VALID in the documented environment.

Key Procedures and Functions

The documented interface exposes eight procedures and functions, all oriented toward metadata retrieval. Their names and purposes are as follows:

  • GET_CITEMS_META_BY_ASSOC — Retrieves content item metadata scoped to a specified association, returning the set of content items linked through that association.
  • GET_CITEMS_META_BY_ASSOC_CTYP — A variant of the preceding routine that further filters retrieved content item metadata by a content type, allowing association-based selection restricted to a particular item category.
  • GET_CITEMS_META — Returns metadata for a collection of content items, typically used when the caller already knows the identifiers of interest.
  • GET_CITEM_META — Returns metadata for a single content item, providing the singular counterpart to the plural retrieval routines.
  • GET_CITEM_BASIC — Retrieves the basic attributes of a content item without the deeper structural detail, suited to lightweight display or listing scenarios.
  • GET_CITEM_BASIC_XML — Produces an XML representation of the basic content item attributes, enabling serialized output for integration or messaging purposes.
  • GET_CITEM_DEEP_XML — Produces an expanded XML representation that includes the deeper, nested structure of the content item, such as related versions, renditions, and compound relationships.

Together these routines form a graduated retrieval model, moving from identifiers and associations, through basic attributes, to fully serialized deep XML documents.

Tables Accessed

The package reads from a defined set of IBC and FND tables through APPS synonyms. IBC_CONTENT_ITEMS supplies the master content item records that anchor all retrieval operations. Version-related metadata is drawn from IBC_CITEM_VERSIONS_TL, which holds translated version information, and IBC_CITEM_VERSION_LABELS, which provides the labels used to identify versions. Rendition information is obtained from IBC_RENDITIONS, supporting the delivery of alternate representations of a content item. Compound structure is resolved through IBC_COMPOUND_RELATIONS. Association-based retrieval depends on IBC_ASSOCIATIONS. Lookup code validation and translation use FND_LOOKUP_VALUES. The XML-producing routines rely on DBMS_LOB for large object manipulation, with PLITBLM available in the same context for PL/SQL table and index-by-table support.

Usage Notes

As a PUB package, IBC_CITEM_RUNTIME_PUB is intended for invocation from standard EBS runtime artifacts and from custom extensions that require content item metadata. Typical consumers include Content Integration forms and servlet or publishing flows that must materialize content item details on demand, as well as concurrent or batch processes that generate serialized XML output through the XML retrieval functions. The documentation records that the package is referenced by two other database objects, while it is not referenced by any database object in the reverse direction, consistent with its position as an upper-layer public runtime API. Because the interface depends on FND message and API infrastructure, callers should initialize the FND message stack and observe standard FND API return conventions when invoking these routines.