Results for “position_reference”

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

Overview

CSI_II_RELATIONSHIPS is a core table within the Oracle E-Business Suite Install Base (CSI) module. It stores instance-to-instance relationships, meaning the directed associations between two item instances in the install base. Each row defines how one instance (the object) relates to another instance (the subject) through a named relationship type. This table is central to modeling real-world configurations such as parent-child assemblies, dependent components, and other logical associations between tracked units.

Heuristically, the FK structure suggests a satellite-leaning classification in a Data Vault model. Because the table references itself back to instance entities and captures descriptive attributes such as position, order, and active dates, it behaves functionally as an attribute-bearing satellite attached to instance and relationship-type hubs, rather than a pure hub or link.

Key Information Stored

The table has 33 documented columns in ETRM 12.2.2. The most significant are:

• RELATIONSHIP_ID — The surrogate primary key (CSI_II_RELATIONSHIPS_PK) and sole unique index candidate (CSI_II_RELATIONSHIPS_U01).
• RELATIONSHIP_TYPE_CODE — FK to CSI_II_RELATION_TYPES; classifies the nature of the association.
• OBJECT_ID — FK to CSI_ITEM_INSTANCES; identifies the object instance in the relationship.
• SUBJECT_ID — FK to CSI_ITEM_INSTANCES; identifies the subject instance.
• POSITION_REFERENCE — Positional context for the relationship.
• ACTIVE_START_DATE / ACTIVE_END_DATE — Effective-dating for the relationship.
• DISPLAY_ORDER — Controls presentation sequence in UI and reports.
• MANDATORY_FLAG — Indicates whether the relationship is required.
• CONTEXT, ATTRIBUTE1–15 — Descriptive flexfield storage for extensible attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns.
• OBJECT_VERSION_NUMBER — Optimistic locking support.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS for data security.
• MIGRATED_FLAG — Indicates migration provenance.

Common Use Cases and Queries

Typical uses include install base configuration reporting, service dependency analysis, and impact assessment when a parent instance is scheduled for change or decommission.

To retrieve relationships for a given instance:

• SELECT r.RELATIONSHIP_ID, r.RELATIONSHIP_TYPE_CODE, r.OBJECT_ID, r.SUBJECT_ID FROM CSI_II_RELATIONSHIPS r WHERE r.OBJECT_ID = :instance_id;

To list relationships with their descriptive types and active status:

• SELECT r.*, t.NAME FROM CSI_II_RELATIONSHIPS r, CSI_II_RELATION_TYPES t WHERE r.RELATIONSHIP_TYPE_CODE = t.RELATIONSHIP_TYPE_CODE AND r.ACTIVE_END_DATE IS NULL;

Reporting commonly joins to CSI_ITEM_INSTANCES twice — once for the object and once for the subject — to display both instance identifiers. History tracking relies on CSI_II_RELATIONSHIPS_H.

Related Objects

• CSI_ITEM_INSTANCES — referenced twice via OBJECT_ID and SUBJECT_ID; the primary instance source.
• CSI_II_RELATION_TYPES — lookup for RELATIONSHIP_TYPE_CODE.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.
• CSI_II_RELATIONSHIPS_H — history table keyed by RELATIONSHIP_ID.
• CSI_T_II_RELATIONSHIPS — staging/interface table referencing CSI_INST_RELATIONSHIP_ID.