Search Results bism_associates_pk

Overview

APPLSYS.BISM_ASSOCIATES is a persistent database table in the Oracle E-Business Suite Applications schema (APPLSYS). It resides in the APPS_TS_TX_DATA tablespace with a PCT Free value of 10. The table is registered under FND Design Data as FND.BISM_ASSOCIATES, and its status is documented as VALID in ETRM 12.2.2. The "BISM" prefix associates this object with the Business Intelligence System Model or Business Intelligence Supplemental Metadata layer used by Oracle EBS to store metadata-driven relationships between modeled objects.

Functionally, BISM_ASSOCIATES records named associations between two entities identified as a SOURCE_ID and a TARGET_ID, where each association carries an attribute NAME and a corresponding VALUE. This design supports generic, extensible metadata storage, allowing attribute-value pairs to be attached to relationships between objects in the BISM_OBJECTS repository without requiring schema changes for each new attribute.

From a heuristic Data Vault modeling perspective, this table is classified as standalone based on mined foreign-key structure. In practice, the table exhibits characteristics of a link table: SOURCE_ID and TARGET_ID together represent the relationship between two object instances, while NAME and VALUE act as descriptive link attributes. This classification should be treated as a modeling suggestion rather than a prescriptive design constraint, given the limited documented metadata.

Key Information Stored

The documented physical schema contains four columns, and the table's identity is governed by the BISM_ASSOCIATES_PK unique index on (SOURCE_ID, NAME, VALUE). Notably, the documented columns and the primary key composition must be read carefully: while the unique index covers SOURCE_ID, NAME, and VALUE, the table also stores TARGET_ID as a RAW(16) column.

• SOURCE_ID — RAW(16); the originating object reference. Participates in the BISM_ASSOCIATES_PK unique index and the nonunique BISM_ASSOCIATES_IK1 index, and carries a foreign key to BISM_OBJECTS.
• TARGET_ID — RAW(16); the destination object reference. Documented FK to BISM_OBJECTS (also noted against AMS_DM_TARGETS_B in relationship metadata) and indexed by nonunique BISM_ASSOCIATES_IK2.
• NAME — VARCHAR2(256); the attribute or association name attached to the source-to-target relationship. Part of the unique index BISM_ASSOCIATES_PK.
• VALUE — VARCHAR2(256); the value of the named attribute. Part of the unique index BISM_ASSOCIATES_PK.

The primary key index (BISM_ASSOCIATES_PK) enforces uniqueness on the (SOURCE_ID, NAME, VALUE) tuple, making it the business-key candidate for this object. Two additional nonunique indexes — BISM_ASSOCIATES_IK1 (SOURCE_ID) and BISM_ASSOCIATES_IK2 (TARGET_ID) — support reverse lookups from either side of the association. All indexes reside in the APPS_TS_TX_IDX tablespace.

Common Use Cases and Queries

Typical usage involves resolving named attributes for a given BISM association, tracing all associations originating from a source object, or finding all links that point to a particular target object. The unique key allows deterministic retrieval of a specific attribute value.

• Retrieve all associations for a source object: SELECT TARGET_ID, NAME, VALUE FROM APPLSYS.BISM_ASSOCIATES WHERE SOURCE_ID = :source_id;
• Retrieve a specific named value: SELECT VALUE FROM APPLSYS.BISM_ASSOCIATES WHERE SOURCE_ID = :source_id AND NAME = :name AND VALUE = :value;
• Reverse lookup by target: SELECT SOURCE_ID, NAME, VALUE FROM APPLSYS.BISM_ASSOCIATES WHERE TARGET_ID = :target_id;
• Join to BISM_OBJECTS to resolve object names against SOURCE_ID and TARGET_ID.

These patterns support metadata governance reporting, dependency analysis, and reconciliation between modeled objects during implementation or upgrade of EBS 12.1.1/12.2.2 environments.

Related Objects

The most significant related object is BISM_OBJECTS, referenced by both the SOURCE_ID and TARGET_ID foreign keys. This table supplies the object identities that BISM_ASSOCIATES links together. Relationship metadata also records a link from TARGET_ID to AMS_DM_TARGETS_B, indicating that BISM associations can target records in the marketing/targeting data model. Additional references include APPS.BISM_ASSOCIATES as the application-layer synonym or view of the same underlying object.

• APPLSYS.BISM_OBJECTS — joined via BISM_ASSOCIATES.SOURCE_ID and BISM_ASSOCIATES.TARGET_ID.
• APPLSYS/AMS.AMS_DM_TARGETS_B — target-side join on TARGET_ID per documented relationship data.
• APPS.BISM_ASSOCIATES — application-facing reference to the same table.

Direct dependency metadata records no outgoing references beyond those foreign keys, and the object is referenced by APPS.BISM_ASSOCIATES within the Oracle EBS instance.