Results for “content_item_id”

50+ results




Overview
Explore in AI Chat

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

Overview

IBC_COMPOUND_RELATIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, released under the IBC — Content Manager product family. The view exposes the contents of the IBC_COMPOUND_RELATIONS base table and is registered in ETRM with a status of VALID in both 12.1.1 and 12.2.2. In EBS terminology, a view whose name ends in the _V suffix and whose defining query is a straight projection over a single base table is a reporting view. It does not perform joins, unions, or aggregations; its purpose is to provide a stable, named, APPS-owned access path for reports, concurrent programs, and integration interfaces instead of requiring those consumers to query the base table directly.

Users searching for compound_relation_id are typically tracing how content items within the IBC Content Manager are linked to one another, and this view is the primary documented entry point for that identifier.

Underlying Base Objects

According to the ETRM metadata, the referenced base object is IBC_COMPOUND_RELATIONS, which is exposed to the APPS layer as a SYNONYM. The view text is a single-table projection:

Because the view is defined over a synonym that resolves to the base table, it carries no filtering or transformation logic. All eleven projected columns map one-to-one to their base columns, with the sole addition of the pseudo-column ROWID aliased as ROW_ID. The documented dependency is therefore singular: IBC_COMPOUND_RELATIONS (SYNONYM) is the only referenced object.

Key Columns

The view exposes the following columns, each inherited directly from the base table:

  • ROW_ID — the physical ROWID of the underlying row, aliased for convenience and usable for direct row access or de-duplication.
  • COMPOUND_RELATION_ID — the primary key of the compound relation record. This is the identifier most frequently searched by developers and support analysts.
  • CONTENT_ITEM_ID — the content item participating in the compound relationship, joining this view to the broader IBC content item structures.
  • ATTRIBUTE_TYPE_CODE — classifies the nature or role of the relation (the relationship type).
  • CITEM_VERSION_ID — the specific content item version associated with the relation, allowing version-aware resolution.
  • CREATED_BY, CREATION_DATE — standard EBS audit columns identifying who created the row and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns capturing the most recent modification and the login that performed it.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle ADF/BC4J framework to detect concurrent updates.

Common Use Cases and Queries

Typical scenarios include resolving a known compound_relation_id to its content item and version, enumerating all relations attached to a given content item, and filtering relations by attribute type for reporting. The following sample queries reflect the documented column set:

  • Resolve a relation by primary key:
    SELECT compound_relation_id, content_item_id, attribute_type_code, citem_version_id FROM apps.ibc_compound_relations_v WHERE compound_relation_id = :p_relation_id;
  • List all relations for a content item:
    SELECT compound_relation_id, citem_version_id, attribute_type_code FROM apps.ibc_compound_relations_v WHERE content_item_id = :p_content_item_id ORDER BY creation_date;
  • Filter by relation type:
    SELECT compound_relation_id, content_item_id FROM apps.ibc_compound_relations_v WHERE attribute_type_code = :p_attr_type;

Because the view performs no transformation, it is safe to use in read-only reporting and integration extracts. Write operations should be directed at the base table through supported IBC APIs rather than through the view.