Search Results get_citems_meta_by_assoc

Overview

IBC_CITEM_RUNTIME_PUB is a public PL/SQL package in the APPS schema that provides the runtime retrieval interface for content items managed by Oracle EBS's Content Manager / iSupport content integration framework. Content items represent versioned, publishable artifacts — documents, files, or structured records — that are associated with business objects through the IBC_ASSOCIATIONS model. The package exposes read-oriented APIs that return content item metadata and basic content item structures, allowing callers to enumerate items bound to an association, inspect a single content item, or obtain XML representations suitable for downstream rendering or transport.

The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the invoking session rather than the definer, and it depends on APPS synonyms for its base tables. The header dates the source to 2005, and the object is present in both EBS 12.1.1 and 12.2.2, where it is classified as a PUB (public) API intended for supported external invocation.

Key Procedures and Functions

The documented interface comprises eight public subprograms:

• GET_CITEMS_META_BY_ASSOC — Returns content item metadata for all content items linked to a given association.
• GET_CITEMS_META_BY_ASSOC_CTYP — As above, but filtered by content type code, restricting results to items of a specific type.
• GET_CITEMS_META — Returns metadata for a set of content items, typically driven by an input collection of content item identifiers.
• GET_CITEM_META — Returns metadata for a single content item, populating the Content_Item_Meta_Rec structure defined in the package specification.
• GET_CITEM_BASIC — Returns the basic content item structure for a single item, populating Content_Item_Basic_Rec. This is the routine most commonly located by users searching for "get_citem_basic". Unlike the meta variants, the basic record includes nested rendition collections (file names, file IDs, MIME types, and rendition names) and, where applicable, an attribute bundle CLOB and compound-item attribute codes.
• GET_CITEM_BASIC_XML — Produces an XML rendering of the basic content item data, suitable for web service or integration consumption.
• GET_CITEM_DEEP_XML — Produces a deeper XML representation that traverses related content, such as compound item relationships and rendition detail.

The specification also declares the supporting collection types (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) that these APIs use to return multi-row and nested data to PL/SQL callers.

Tables Accessed

The package reads from the core content tables through APPS synonyms:

• IBC_CONTENT_ITEMS — master content item rows supplying identifiers, names, descriptions, references, and date ranges.
• IBC_CITEM_VERSIONS_TL and IBC_CITEM_VERSION_LABELS — translated version text and version labels.
• IBC_RENDITIONS — rendition file names, file IDs, and MIME types attached to items.
• IBC_ASSOCIATIONS — the mapping between content items and the business objects they are associated with, driving the BY_ASSOC lookups.
• IBC_COMPOUND_RELATIONS — parent/child structure used by compound items and the deep XML routine.
• FND_LOOKUP_VALUES — lookup code validation and decoding of content type and related codes.
• DBMS_LOB and PLITBLM — used to manipulate CLOB attribute bundles and to convert PL/SQL tables of strings into values suitable for dynamic SQL IN-lists.

These accesses are read-oriented; the package is a query and rendering layer rather than a maintenance API.

Usage Notes

IBC_CITEM_RUNTIME_PUB is normally invoked at runtime rather than during setup. Typical callers include Content Manager and iSupport forms or OAF pages that need to display item metadata or rendition lists, concurrent programs that export or transmit content items, and custom integration code that requires XML output for web services. Because the package is AUTHID CURRENT_USER and relies on APPS synonyms, the invoking schema must have appropriate grants on the IBC tables. The two XML entry points are the preferred route for external integrations, while GET_CITEM_BASIC and the metadata routines suit PL/SQL callers that need typed records and collections. Two other packages reference this object, indicating layered composition within the content integration stack. When searching for "get_citem_basic", the relevant public entry point is the GET_CITEM_BASIC procedure, with GET_CITEM_BASIC_XML and GET_CITEM_DEEP_XML providing the XML equivalents.