Results for “orig_system_reference_id”

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

Overview

IBC_CONTENT_ITEMS is the master (header) table for Oracle EBS Content Manager (IBC), the module that manages reusable content and collateral used across marketing, proposals, and web placement. As its documented description states, it stores non-version and non-language-specific information about content items — that is, the identity, classification, ownership, and lifecycle status that remain constant across all versions and translations of a given item. Version-specific and language-specific attributes are held in the companion tables IBC_CITEM_VERSIONS_B and IBC_CITEM_VERSION_LABELS, both of which carry a CONTENT_ITEM_ID foreign key back to this table.

Its heuristic Data Vault classification is hub. In modeling terms, IBC_CONTENT_ITEMS corresponds to a hub: a single row per business entity (the content item) carrying its durable business key, while attributes that change over time — versions, labels, and relationships — are modeled as satellites and links in surrounding tables.

Key Information Stored

The table is defined in the IBC schema with 29 documented columns. The most significant are:

• CONTENT_ITEM_ID — the surrogate primary key, enforced by IBC_CONTENT_ITEMS_PK; it is the join column to every dependent table.
• ITEM_REFERENCE_CODE — the business-key candidate, enforced by unique index IBC_CONTENT_ITEMS_UK. A second unique index, IBC_CONTENT_ITEMS_U1, combines CONTENT_ITEM_ID and ZD_EDITION_NAME, which supports multi-edition deployments.
• CONTENT_TYPE_CODE — classifies the item; foreign key to IBC_CONTENT_TYPES_B.
• DIRECTORY_NODE_ID — the folder or node in which the item resides; foreign key to IBC_DIRECTORY_NODES_B.
• PARENT_ITEM_ID — enables hierarchical or compound content structures.
• LIVE_CITEM_VERSION_ID — points to the currently published version in IBC_CITEM_VERSIONS_B.
• CONTENT_ITEM_STATUS — the workflow/lifecycle state of the item.
• LOCKED_BY_USER_ID — identifies a user holding the item for editing.
• BASE_LANGUAGE and TRANSLATION_REQUIRED_FLAG — drive multilingual content processing.
• WD_RESTRICTED_FLAG — governs restricted (whitelist/distribution) access.
• OWNER_RESOURCE_ID and OWNER_RESOURCE_TYPE — identify the owning resource.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling multi-org/security access.
• OBJECT_VERSION_NUMBER — optimistic locking.
• ENCRYPT_FLAG, ORIG_SYSTEM_REFERENCE_ID, and ORIG_SYSTEM_REFERENCE_CODE — track encryption state and the item's origin in an external or legacy system.
• Standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent-program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical reporting needs are finding all live items of a given type, auditing items awaiting translation, and locating content by folder.

• List active content by type:

  SELECT ci.content_item_id, ci.item_reference_code, ct.content_type_code
  FROM   ibc_content_items ci,
         ibc_content_types_b ct
  WHERE  ci.content_type_code = ct.content_type_code
  AND    ci.content_item_status = 'ACTIVE';

• Find items pending translation:

  SELECT content_item_id, item_reference_code, base_language
  FROM   ibc_content_items
  WHERE  translation_required_flag = 'Y';

• Resolve the current published version:

  SELECT ci.item_reference_code, cv.version_number
  FROM   ibc_content_items ci,
         ibc_citem_versions_b cv
  WHERE  ci.live_citem_version_id = cv.content_item_id;

Related Objects

• IBC_CITEM_VERSIONS_B — referenced via LIVE_CITEM_VERSION_ID and referencing back via CONTENT_ITEM_ID; holds version data (the satellite).
• IBC_CITEM_VERSION_LABELS — language/label rows keyed by CONTENT_ITEM_ID.
• IBC_CONTENT_TYPES_B — content classification, joined on CONTENT_TYPE_CODE.
• IBC_DIRECTORY_NODES_B — folder hierarchy, joined on DIRECTORY_NODE_ID.
• IBC_ASSOCIATIONS and IBC_COMPOUND_RELATIONS — link tables linking content items to each other and to other entities.
• IBC_CONTENT_ITEM_NODES — site/node placement records.
• AMS_CONTENT_RULES_B — references content items as cover letters via COVER_LETTER_ID.
• PRP_PROPOSALS and PRP_COMPONENT_STYLES_B — proposal and style components referencing CONTENT_ITEM_ID.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for access control.