Search Results bism_objects

Overview

BISM_OBJECTS is a table owned by the APPLSYS schema within the FND — Application Object Library product of Oracle E-Business Suite. It is a foundational object used by the Business Intelligence System Manager (BISM) framework, which underlies the personalization, folder, and object-registration infrastructure shared across the EBS application tier. The table records discrete business objects and their descriptive metadata, enabling the application to identify, categorize, version, and retrieve objects persisted across multiple product modules.

Under the heuristic Data Vault classification mined from its foreign key structure, BISM_OBJECTS is assessed as a standalone entity rather than a strict hub, link, or satellite. In modeling terms, it may be treated as a reference hub for object identity, with its descriptive attributes behaving satellite-like. However, because the mined classification is standalone, practitioners should confirm referential intent against their specific integration requirements before imposing a Data Vault pattern.

Key Information Stored

The documented physical schema contains 23 columns in ETRM 12.2.2. The most operationally significant are:

• OBJECT_ID — the surrogate primary key, enforced by the BISM_OBJECTS_PK unique index. This is the primary identifier used by downstream references.
• OBJECT_NAME and TITLE — human-readable identifiers and display labels for the object.
• FOLDER_ID — the organizing folder to which the object belongs; a frequent component of business-key candidates.
• USER_VISIBLE — a visibility flag included in the BISM_OBJECTS_UK1 unique index, distinguishing user-accessible objects from internal ones.
• OBJECT_TYPE_ID — a foreign key to JTF_PERZ_LF_OBJECT_TYPE, classifying the object's type.
• CONTAINER_ID — a foreign key to WSH_PACKED_CONTAINERS, linking objects to physical container records.
• VERSION — tracks the object definition's revision level.
• CREATED_BY, LAST_MODIFIED_BY, TIME_DATE_CREATED, TIME_DATE_MODIFIED, and TIME_DATE_LAST_ACCESSED — audit and lifecycle columns.
• DESCRIPTION, KEYWORDS, and XML — descriptive and payload content, with XML holding serialized object definitions.

Business-key candidates are captured by the unique indexes: BISM_OBJECTS_UK1 (FOLDER_ID, OBJECT_NAME, USER_VISIBLE), BISM_OBJECTS_UK2 (OBJECT_ID, FOLDER_ID), and BISM_OBJECTS_UK3 (FOLDER_ID, OBJECT_ID). Two SYS_IL indexes on columns 17 and 23 support LOB storage.

Common Use Cases and Queries

Typical scenarios include resolving an object by its name within a folder, auditing object creation and modification activity, and reporting on objects by type or visibility. A representative query joins the type lookup to classify objects:

• Retrieving visible objects in a folder: SELECT OBJECT_ID, OBJECT_NAME, TITLE FROM APPLSYS.BISM_OBJECTS WHERE FOLDER_ID = :folder_id AND USER_VISIBLE = 'Y';
• Classifying objects by type: SELECT o.OBJECT_ID, t.OBJECT_TYPE_NAME FROM APPLSYS.BISM_OBJECTS o JOIN APPLSYS.JTF_PERZ_LF_OBJECT_TYPE t ON o.OBJECT_TYPE_ID = t.OBJECT_TYPE_ID;
• Activity auditing: filter on TIME_DATE_CREATED or TIME_DATE_MODIFIED within a reporting window and group by CREATED_BY.

Related Objects

The most significant related objects, per the documented foreign keys, are:

• JTF_PERZ_LF_OBJECT_TYPE — joined via BISM_OBJECTS.OBJECT_TYPE_ID to resolve object type classification.
• WSH_PACKED_CONTAINERS — joined via BISM_OBJECTS.CONTAINER_ID to associate objects with packed containers.

Beyond these direct references, dependent views, folder-personalization APIs, and BISM framework routines rely on OBJECT_ID and FOLDER_ID as the principal access paths, making BISM_OBJECTS a central registration point for the personalization subsystem in both 12.1.1 and 12.2.2.