Search Results bism_objects_uk1

Overview

APPLSYS.BISM_OBJECTS is a transactional repository table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. Its name derives from the Business Intelligence System Manager (BISM) component, and it functions as the central registry of business intelligence objects — folders, reports, aggregates, and their descriptive metadata — that are surfaced through the EBS embedded analytics and BI repository layers. The table is owned by the APPLSYS schema and carries the FND design data reference FND.BISM_OBJECTS, confirming it is tracked as a seed/design object within the Applications foundation. Its storage resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and it is validated as VALID in the ETRM registry.

The heuristic Data Vault classification mined from the foreign key structure is standalone. This suggests the table behaves largely as a self-contained entity hub rather than a pure transactional satellite, since it holds its own surrogate key, self-referencing folder containment, and several business-key candidates. Analysts modeling this object for downstream integration may treat it as an entity hub with satellite-like descriptive attributes (TITLE, DESCRIPTION, KEYWORDS).

Key Information Stored

The surrogate primary key is OBJECT_ID, a RAW(16) globally unique identifier enforced by the unique index BISM_OBJECTS_PK. Business-key candidates are defined by the additional 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). The search term bism_objects_uk1 refers specifically to the unique constraint on FOLDER_ID, OBJECT_NAME, and USER_VISIBLE, which guarantees no duplicate object name within a folder for a given visibility state.

The most significant columns include: OBJECT_ID (surrogate key, RAW(16)); FOLDER_ID (RAW(16), self-referencing parent folder); CONTAINER_ID (RAW(16), the enclosing container); OBJECT_NAME (VARCHAR2(256)) and TITLE (VARCHAR2(128)) as the primary human-readable identifiers; USER_VISIBLE as a visibility flag participating in UK1; OBJECT_TYPE_ID (NUMBER) referencing the object type taxonomy; VERSION (NUMBER); APPLICATION and DATABASE (VARCHAR2(256)) describing the hosting context; DESCRIPTION and KEYWORDS for search and categorization; XML for serialized object definitions; and the audit columns TIME_DATE_CREATED, TIME_DATE_MODIFIED, TIME_DATE_LAST_ACCESSED, CREATED_BY, and LAST_MODIFIED_BY.

Common Use Cases and Queries

Typical usage centers on locating, enumerating, and auditing BI repository content for a given folder or user. A representative query retrieves visible objects within a folder:

• SELECT object_id, object_name, title, object_type_id FROM applsys.bism_objects WHERE folder_id = :p_folder AND user_visible = 'Y';
• SELECT o.object_name, o.title, t.object_type_name FROM bism_objects o, bism_object_types t WHERE o.object_type_id = t.object_type_id AND o.application = :p_app;
• SELECT COUNT(*) FROM bism_objects WHERE time_date_modified > SYSDATE - 30;

Reporting scenarios include inventory of objects by application, stale-object detection via TIME_DATE_LAST_ACCESSED, and security review joined to BISM_PERMISSIONS. Because FOLDER_ID is both a foreign key and part of UK1, hierarchical folder walks can be implemented with recursive CONNECT BY queries beginning at any root folder.

Related Objects

The following relationships are the most significant for join and dependency analysis:

• BISM_OBJECT_TYPES — joined via OBJECT_TYPE_ID; provides the type taxonomy.
• BISM_AGGREGATES — joined via CONTAINEE_ID and CONTAINER_ID; models aggregation membership.
• BISM_ASSOCIATES — joined via SOURCE_ID and TARGET_ID; captures object associations.
• BISM_PERMISSIONS — joined via OBJECT_ID; governs access control.
• BISM_SUBJECTS — joined via CREATED_BY and LAST_MODIFIED_BY; resolves the owning user/subject.
• BISM_OBJECTS (self) — joined via FOLDER_ID and CONTAINER_ID; recursive containment.
• JTF_PERZ_LF_OBJECT_TYPE — an external reference for OBJECT_TYPE_ID in personalization contexts.
• WSH_PACKED_CONTAINERS — an external reference for CONTAINER_ID, indicating cross-module container linkage within shipping/warehouse data.

These relationships establish BISM_OBJECTS as a connective hub within the BI repository schema, tying together type, permission, association, and containment metadata while remaining self-referential for folder hierarchy.