Results for “bism_object_types”

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

Overview

BISM_OBJECT_TYPES is a reference (lookup) table owned by the APPLSYS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the FND – Application Object Library product family and, in the context of the ETRM repository, is documented as a standalone object with a defined physical schema and unique indexes. The object is a member of the BISM (Business Intelligence System Manager / personalization infrastructure) naming family, which underpins the personalization and object-registration framework used by OA Framework pages and related runtime services.

The table's purpose is to provide a controlled enumeration of object type definitions used by the personalization layer, specifically the per-zone personalization configuration referenced by JTF_PERZ_LF_OBJECT_TYPE. Its Data Vault classification, mined heuristically from the foreign-key structure, is standalone. In Data Vault modeling terms this suggests the table behaves as an independent reference or hub-like entity (or a small lookup satellite) rather than as a transactional link; it holds slowly changing reference definitions rather than business event transactions.

Key Information Stored

The documented physical schema of BISM_OBJECT_TYPES in ETRM 12.2.2 contains exactly two columns. Both are significant:

• OBJECT_TYPE_ID – The surrogate primary key. It is enforced by the unique index BISM_OBJECT_TYPES_PK. This identifier is the value propagated to dependent tables (notably JTF_PERZ_LF_OBJECT_TYPE) as a foreign key, and it is the join key for all downstream personalization metadata.
• OBJECT_TYPE_NAME – The business-key candidate. It is enforced by the unique index BISM_OBJECT_TYPES_UK, which guarantees that each named object type is distinct. This column carries the human-readable type label referenced in personalization administration and configuration screens.

Because the table is narrow (two columns), it functions purely as a code-and-description lookup. The surrogate key drives referential integrity; the name column provides the descriptive business identity that developers and administrators see. No descriptive or attribute-heavy columns are documented, which reinforces its role as a compact enumeration rather than a detail table.

Common Use Cases and Queries

Typical usage involves resolving an object type identifier to its readable name during personalization reporting, or validating that a supplied object type exists before inserting dependent personalization rows. A standard lookup query is:

• SELECT object_type_id, object_type_name FROM applsys.bism_object_types ORDER BY object_type_name;
• Join to the dependent personalization table to enrich reports:

SELECT bot.object_type_name, j.* FROM applsys.bism_object_types bot JOIN jtf_perz_lf_object_type j ON bot.object_type_id = j.object_type_id;

Reporting use cases include auditing which object types are registered in the personalization framework, producing reference data extracts for migration or cloning activities, and troubleshooting personalization failures where an expected object type is missing from the enumeration. Because the UK enforces uniqueness on the name, data-quality checks can rely on the name column as a stable business identifier across environments.

Related Objects

The documented foreign-key relationship identifies the dependent object that references this table:

• JTF_PERZ_LF_OBJECT_TYPE – references BISM_OBJECT_TYPES via OBJECT_TYPE_ID. This is the primary consuming object and the principal target for joins.
• BISM_OBJECT_TYPES_PK and BISM_OBJECT_TYPES_UK – the unique indexes that enforce the surrogate key and the business-key name, respectively.

As a standalone reference object with a single documented outbound/inbound relationship, BISM_OBJECT_TYPES has limited dependency surface. Administrators working with OA Framework personalization metadata should treat it as a foundational lookup whose OBJECT_TYPE_ID values must remain synchronized with JTF_PERZ_LF_OBJECT_TYPE entries to preserve referential integrity across the APPLSYS schema.