Search Results get_citem_basic_xml

Overview

IBC_CITEM_RUNTIME_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Setup (EBS) Release 12.1.1 and 12.2.2. It belongs to the Oracle iMarketing/IBC content management subsystem and provides the runtime interface for retrieving content item metadata and content item body information. Content items represent the reusable assets — documents, URLs, images, and other media — stored and versioned within the IBC content repository, and this package exposes that repository to calling code in a controlled, API-oriented manner. The package is declared with AUTHID CURRENT_USER, and it defines a set of PL/SQL collection and record types that shape the returned data, including Rendition_File_Name_Tbl, Rendition_File_Id_Tbl, Rendition_Mime_Type_Tbl, Rendition_Name_Tbl, Comp_Item_Attrib_Tcode_Tbl, Comp_Item_Citem_Id_Tbl, Content_Item_Meta_Rec/Tbl, and Content_Item_Basic_Rec. The final declaration shows that Content_Item_Basic_Rec carries scalar content item attributes plus nested rendition collections, an attribute_bundle CLOB, and compound item attribute code collections, confirming that the package returns both header-level and detailed content item structures.

Key Procedures and Functions

The ETRM documentation records eight public procedures and functions. GET_CITEMS_META_BY_ASSOC and GET_CITEMS_META_BY_ASSOC_CTYP retrieve metadata for multiple content items associated with a given association (and, in the _CTYP variant, filtered by content type). GET_CITEMS_META returns metadata for a set of content items, while GET_CITEM_META returns metadata for a single content item. Metadata results conform to the Content_Item_Meta_Rec structure, which exposes identifiers, version, availability and expiration dates, content type and reference codes, encryption flag, names, descriptions, attachment information, and default mime type/rendition name. GET_CITEM_BASIC returns the basic record for a single content item, populating the Content_Item_Basic_Rec with rendition collections and the attribute_bundle. GET_CITEM_BASIC_XML performs the same retrieval but returns the content item basic data serialized as XML, which is the entry point most commonly referenced by integration code. GET_CITEM_DEEP_XML returns the fully expanded XML representation, including nested compound item relationships. Parameter lists are intentionally not reproduced here; callers should consult the package specification for exact signatures.

Tables Accessed

The package reads and writes through APPS synonyms. IBC_CONTENT_ITEMS, IBC_CITEM_VERSIONS_TL, and IBC_CITEM_VERSION_LABELS supply the core content item header, translatable version text, and version labelling data. IBC_RENDITIONS provides the rendition file names, ids, mime types, and rendition names assembled into the rendition collections of Content_Item_Basic_Rec. IBC_ASSOCIATIONS and IBC_COMPOUND_RELATIONS drive the association-based metadata lookups and the compound item expansion used by GET_CITEM_DEEP_XML. FND_LOOKUP_VALUES is used to resolve lookup codes such as content types and flags. DBMS_LOB is invoked for CLOB handling of the attribute_bundle, and PLITBLM supports the PL/SQL table (index-by table) manipulation logic required to populate and return the collection types declared in the specification.

Usage Notes

IBC_CITEM_RUNTIME_PUB is a runtime read-oriented API invoked by Oracle iMarketing forms, concurrent programs, and custom integration code that needs to render or transport content item data. GET_CITEM_BASIC_XML is typically called when a consuming application requires a self-describing XML payload for a single content item, such as populating a web or portal surface, building an outbound message, or feeding a downstream publishing process. The package is referenced by two other PL/SQL packages, indicating that it serves as a shared lower-level service within the IBC stack. Because it is classified as PUB and runs with AUTHID CURRENT_USER, customizations and extensions are expected to call it directly rather than reimplementing the underlying queries; callers should nevertheless grant the necessary privileges on the IBC tables and rely on the documented record and collection types to interpret results consistently across Release 12.1.1 and 12.2.2.