Search Results ibc_renditions




Overview
Explore in AI Chat

Overview

IBC_RENDITIONS is a transactional table in the IBC (Content Manager) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Content Manager is the repository used by Oracle iStore, Oracle Partners, Oracle Marketing, and other modules to store and serve binary content items such as images, documents, media files, and downloadable assets. A single content item attachment (a logical content item version) may be published in several alternative representations: for example, a product image delivered as a JPEG thumbnail, a full-resolution TIFF, and a PDF datasheet. IBC_RENDITIONS stores one row per such rendition, binding a content item version to a physical file and recording the language and MIME type under which that file is served.

The object is owned by the IBC schema and holds fourteen documented columns in the ETRM 12.2.2 physical model. From a Data Vault modeling perspective, the mined foreign-key structure yields a standalone classification, suggesting IBC_RENDITIONS behaves as a standalone hub-like entity anchored on its own primary key and pointing outward to a content item version and a security group, rather than participating in a dense network of parent/child links.

Key Information Stored

The surrogate primary key is RENDITION_ID, enforced by IBC_RENDITIONS_PK. Two unique indexes act as business-key candidates: IBC_RENDITIONS_U1 (RENDITION_ID, ZD_EDITION_NAME) and IBC_RENDITIONS_U2 (CITEM_VERSION_ID, LANGUAGE, MIME_TYPE, ZD_EDITION_NAME). The U2 index is the more meaningful business key: it guarantees that any given content item version has at most one rendition per language and MIME type combination within an edition.

  • RENDITION_ID — Surrogate primary key identifying each rendition row.
  • CITEM_VERSION_ID — Foreign key to IBC_CITEM_VERSIONS_B; the specific content item version that this rendition represents.
  • LANGUAGE — Language/locale in which the rendition is published; part of the U2 business key.
  • MIME_TYPE — Media type of the stored file (e.g., image/jpeg, application/pdf); also part of U2 and used by the media-serving layer to set HTTP content types.
  • FILE_ID — Identifier of the physical file record holding the rendition binary.
  • FILE_NAME — Original or published file name presented to the end user or download.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS; enforces multi-org style data isolation across IBC content.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/BC4J persistence layer.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns maintained by the WHO columns framework.
  • ZD_EDITION_NAME — Editioning column present in 12.2 online patching architecture; part of both unique indexes.

Common Use Cases and Queries

Typical usage centers on catalog and media publishing: determining which file formats are available for a given content item version, auditing language coverage of product imagery, and diagnosing broken or missing downloads. A common query lists all renditions for a content item version:

  • SELECT r.rendition_id, r.mime_type, r.language, r.file_name FROM ibc.ibc_renditions r WHERE r.citem_version_id = :version_id;
  • Detecting items lacking a required MIME type (e.g., no PDF rendition): compare distinct MIME_TYPE values per CITEM_VERSION_ID against expected formats.
  • Reporting rendition volume by MIME type: SELECT mime_type, COUNT(*) FROM ibc.ibc_renditions GROUP BY mime_type;
  • Auditing stale files via LAST_UPDATE_DATE ranges, or reconciling SECURITY_GROUP_ID against FND_SECURITY_GROUPS for cross-organization visibility checks.

Because the table is editioned, reports run against the runtime edition must not filter ZD_EDITION_NAME explicitly unless coordinating with patching.

Related Objects

The most significant related objects, per documented referential data:

  • IBC_CITEM_VERSIONS_B — Parent content item version table; joined on IBC_RENDITIONS.CITEM_VERSION_ID = IBC_CITEM_VERSIONS_B.CITEM_VERSION_ID. Supplies the content item and version context.
  • FND_SECURITY_GROUPS — Joined on SECURITY_GROUP_ID; governs data visibility and multi-organization access.
  • IBC_CITEM_VERSIONS_TL — Translation table for content item versions, used when reporting rendition coverage per language alongside translatable titles.
  • IBC_CONTENT_ITEMS_B / _TL — Parent content item definitions; provide the catalog-level context for the rendition hierarchy.
  • FND_LOBS / FND_ATTACHED_DOCUMENTS — Commonly consulted to resolve FILE_ID into the physical binary when validating downloadable content.
  • IBC_RENDITIONS_PK / IBC_RENDITIONS_U1 / IBC_RENDITIONS_U2 — Constraints that enforce row identity and the version/language/MIME business key; useful in reverse-engineering ETL or interface logic.