Results for “ibe_dsp_obj_lgl_ctnt”

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

Overview

The IBE_DSP_OBJ_LGL_CTNT table resides in the IBE schema, which supports the Oracle iStore application within Oracle E-Business Suite. It stores the default logical items associated with selected display context labels and objects, enabling iStore to resolve which content items appear for a given display context and object combination. This table operates as a configuration and mapping table within the iStore display and personalization framework, where display contexts, sections, and catalog objects are linked to specific content items managed through the Application Message and Variable (AMV) infrastructure.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure suggests this object functions as a link table. It resolves many-to-many style associations between display contexts, objects such as categories and sections, and content items, rather than acting as a descriptive satellite or a standalone business hub. This classification reflects its role as a connective entity joining independent master data elements.

Key Information Stored

The table contains twelve documented columns. The most significant are summarized below.

• OBJ_LGL_CTNT_ID — the surrogate primary key, enforced through the IBE_DSP_OBJ_LGL_CTNT_PK constraint and uniquely indexed by IBE_DSP_OBJ_LGL_CTNT_U2.
• CONTEXT_ID — foreign key to IBE_DSP_CONTEXT_B, identifying the display context label under which the logical content mapping applies.
• OBJECT_ID — foreign key referencing either MTL_CATEGORIES_B or IBE_DSP_SECTIONS_B, identifying the catalog category or iStore section to which the content item is bound.
• OBJECT_TYPE — discriminator column distinguishing the nature of OBJECT_ID, resolving the polymorphic relationship to categories versus sections.
• ITEM_ID — foreign key to JTF_AMV_ITEMS_B, identifying the content item treated as the default logical content for the context/object pairing.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling multi-tenant visibility and access isolation.
• OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns recording creation and modification lineage.

The business-key candidate is defined by the unique index IBE_DSP_OBJ_LGL_CTNT_U1 across OBJECT_TYPE, OBJECT_ID, and CONTEXT_ID, ensuring that a given context and object pairing resolves to a single logical content record.

Common Use Cases and Queries

Typical usage centers on iStore merchandising and content administration. Administrators and developers query this table to determine which content item renders by default for a given display context and category or section. Reporting queries frequently join to JTF_AMV_ITEMS_B to retrieve content text or media references, and to IBE_DSP_CONTEXT_B to resolve context labels.

• Resolving default content for a category: SELECT ITEM_ID FROM IBE_DSP_OBJ_LGL_CTNT WHERE OBJECT_TYPE = :type AND OBJECT_ID = :cat AND CONTEXT_ID = :ctx;
• Auditing mappings by context label, joining IBE_DSP_CONTEXT_B on CONTEXT_ID.
• Validating content coverage across sections by joining IBE_DSP_SECTIONS_B on OBJECT_ID.
• Extracting changed records for migration using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

• IBE_DSP_CONTEXT_B — joined via CONTEXT_ID; supplies display context definitions.
• MTL_CATEGORIES_B — joined via OBJECT_ID where OBJECT_TYPE denotes a category.
• IBE_DSP_SECTIONS_B — joined via OBJECT_ID where OBJECT_TYPE denotes a section.
• JTF_AMV_ITEMS_B — joined via ITEM_ID; provides the logical content item details.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for access control.
• IBE_DSP_OBJ_LGL_CTNT_PK, IBE_DSP_OBJ_LGL_CTNT_U1, IBE_DSP_OBJ_LGL_CTNT_U2 — constraints and indexes enforcing integrity and uniqueness.