Search Results bism_object_types_pk

Overview

APPLSYS.BISM_OBJECT_TYPES is a reference (lookup) table in Oracle E-Business Suite that defines the set of object types recognized by the Business Intelligence System Manager (BISM) subsystem. It serves as the master enumeration of object classifications used throughout the BISM framework, allowing other BISM entities to reference object categories by a compact numeric identifier rather than by name. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the APPLSYS schema, is shipped under the FND design data directory as FND.BISM_OBJECT_TYPES, and is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10.

Because the table contains only two columns and carries no foreign keys of its own, the heuristic Data Vault classification is standalone. In Data Vault modeling terms this table functions as a small reference hub: OBJECT_TYPE_ID acts as the hub key, and OBJECT_TYPE_NAME behaves as a descriptive attribute that could be modeled as a satellite attached to that hub. It is a type/reference construct rather than a transactional or link entity.

Key Information Stored

The documented structure is deliberately minimal, consisting of two columns:

• OBJECT_TYPE_ID (NUMBER) — The surrogate primary key and the column most frequently queried by users searching for "object_type_id." It is the unique numeric handle for each object type and is enforced by the unique index BISM_OBJECT_TYPES_PK. This is the value propagated to dependent tables such as BISM_OBJECTS.OBJECT_TYPE_ID.
• OBJECT_TYPE_NAME (VARCHAR2, length 32) — The human-readable business name of the object type. It is a business-key candidate, protected by the unique index BISM_OBJECT_TYPES_UK. This is the value typically displayed in forms, reports, and LOVs, and it is the column users search on when they do not already know the numeric identifier.

The distinction between the two is important: OBJECT_TYPE_ID is the surrogate key used for referential integrity and joins, while OBJECT_TYPE_NAME is the business key used for identification and display. Together they form a compact but complete reference set. No mandatory flags, nullability, or default values are documented for either column, so the naming conventions and unique constraints are the primary source of design intent.

Common Use Cases and Queries

Typical usage centers on resolving a numeric object type identifier to its descriptive name, or vice versa, during reporting and diagnostic work. The canonical query documented for this object is:

• SELECT OBJECT_TYPE_ID, OBJECT_TYPE_NAME FROM APPLSYS.BISM_OBJECT_TYPES;

A frequent pattern is joining this reference to the child table to produce readable output — for example, selecting BISM_OBJECTS rows and joining on OBJECT_TYPE_ID to display OBJECT_TYPE_NAME instead of the raw number. Lookup-by-name is equally common when a user knows the object type label but needs the identifier to filter another query. Because OBJECT_TYPE_NAME is uniquely constrained, such lookups return at most one row, which makes the table safe to use as a validation source or an LOV backing query. Reporting consumers often treat this table as a domain or reference dataset in BI Publisher and Oracle Analytics extracts, driving parameter prompts and value lists for object-type filtering.

Related Objects

• APPLSYS.BISM_OBJECTS — The principal dependent table. Its OBJECT_TYPE_ID column is documented as a foreign key referencing BISM_OBJECT_TYPES.OBJECT_TYPE_ID, making this the strongest and most important relationship in the metadata.
• JTF_PERZ_LF_OBJECT_TYPE — An additional foreign-key relationship is documented from BISM_OBJECT_TYPES.OBJECT_TYPE_ID to JTF_PERZ_LF_OBJECT_TYPE, linking BISM object types into the JTF personalization / object-type framework.
• APPS.BISM_OBJECT_TYPES — The APPS-level synonym, listed as referencing this APPLSYS table and providing the standard application-facing access path.

The only key definitions documented are the primary key BISM_OBJECT_TYPES_PK and the unique constraint BISM_OBJECT_TYPES_UK, on OBJECT_TYPE_ID and OBJECT_TYPE_NAME respectively. Together with BISM_OBJECTS, these form the complete documented dependency picture for this reference table.