Results for “ibc_stylesheets”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IBC_STYLESHEETS is a reference table in the Oracle E-Business Suite Content Manager (IBC) product module. It stores the association between a given content type and the stylesheets applied to content items of that type. In EBS, the Content Manager is responsible for managing large objects, documents, and binary content that other applications — such as iProcurement, iSupplier, and various self-service modules — attach to business entities. Stylesheets stored here control the rendering and presentation of that content when it is displayed or transformed.

The table resides in the IBC schema and is documented as VALID in both EBS 12.1.1 and 12.2.2. The documented physical schema contains 11 columns. Based on the foreign key structure, the heuristic Data Vault classification for this object is a link. This is a modeling suggestion: IBC_STYLESHEETS primarily functions as an associative table resolving relationships between content items, content types, and security groups, rather than storing descriptive attributes of a single business entity (a satellite) or a standalone entity (a hub).

Key Information Stored

The 11 documented columns support the associative and audit requirements of the table. The most significant are:

• CONTENT_TYPE_CODE — Identifies the content type whose stylesheet association is being recorded. This is a foreign key to IBC_CONTENT_TYPES_B and part of the primary key.
• CONTENT_ITEM_ID — Identifies the specific content item. This is a foreign key to IBC_CONTENT_ITEMS and the other component of the primary key.
• DEFAULT_STYLESHEET_FLAG — Indicates whether the associated stylesheet is the default for the given content type and item combination.
• OBJECT_VERSION_NUMBER — Supports optimistic locking and change detection, standard in EBS 12.2.2 tables.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data isolation across operating units and responsibility boundaries.
• ZD_EDITION_NAME — Editioning column supporting Online Patching (adop) in EBS 12.2.2.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard "Who" columns present on nearly every transactional EBS table.

The surrogate primary key is IBC_STYLESHEETS_PK, composed of (CONTENT_TYPE_CODE, CONTENT_ITEM_ID). The documented unique index IBC_STYLESHEETS_U1 covers (CONTENT_ITEM_ID, CONTENT_TYPE_CODE, ZD_EDITION_NAME) and functions as the business-key candidate under editioning.

Common Use Cases and Queries

Typical scenarios involve determining which stylesheet applies to content items of a given type, auditing default stylesheet assignments, and joining content metadata for reporting or migration.

• List stylesheets for a content type:

  SELECT s.content_item_id, s.default_stylesheet_flag
  FROM   ibc.ibc_stylesheets s
  WHERE  s.content_type_code = :type_code;

• Identify default stylesheets: Filter on DEFAULT_STYLESHEET_FLAG = 'Y' to enumerate the default rendering stylesheet per content item.
• Join to content items and types for a full descriptive view of the association, using CONTENT_ITEM_ID and CONTENT_TYPE_CODE as join keys.
• Security-scoped reporting: Constrain queries by SECURITY_GROUP_ID to respect multi-org access rules.
• Migration or clone validation: Compare row counts and DEFAULT_STYLESHEET_FLAG distributions across source and target instances.

Related Objects

The most significant related objects, based on documented foreign keys, are:

• IBC_CONTENT_ITEMS — referenced via IBC_STYLESHEETS.CONTENT_ITEM_ID.
• IBC_CONTENT_TYPES_B — referenced via IBC_STYLESHEETS.CONTENT_TYPE_CODE.
• FND_SECURITY_GROUPS — referenced via IBC_STYLESHEETS.SECURITY_GROUP_ID.
• IBC_STYLESHEETS_PK — the primary key constraint enforcing uniqueness of content type and item combinations.
• IBC_STYLESHEETS_U1 — the unique index providing the business-key candidate.

Because Content Manager sits beneath several self-service and procurement flows, dependent views and PL/SQL APIs within the IBC schema frequently join this table when resolving how attached content should be rendered to end users.