Search Results csi_ii_relationships

Overview

The CSI_II_RELATIONSHIPS table is a core data structure within the Oracle E-Business Suite Install Base (CSI) module. It serves as the central repository for defining and storing all relationships between inventory item instances. An item instance represents a specific, trackable unit of an item, such as a particular serialized server or a lot-controlled component. This table enables the modeling of complex physical and logical assemblies, dependencies, and hierarchies within an enterprise's deployed asset base. Its integrity is critical for functions like configuration management, service tracking, and impact analysis, as it documents how individual instances are connected within larger systems.

Key Information Stored

The table's primary purpose is to link two item instances in a directed relationship. The most critical columns are the foreign keys that define this link and its type. The SUBJECT_ID and OBJECT_ID columns each reference the CSI_ITEM_INSTANCES table, storing the identifiers for the related item instances. The direction of the relationship is meaningful; the subject is typically considered the "parent" or "source," and the object is the "child" or "target." The nature of the connection is defined by RELATIONSHIP_TYPE_CODE, which references the CSI_II_RELATION_TYPES table (e.g., "COMPONENT_OF," "CONNECTED_TO"). The table's primary key is RELATIONSHIP_ID, a unique identifier for each relationship record. Other columns typically manage lifecycle metadata such as active dates and context details.

Common Use Cases and Queries

A primary use case is generating a bill of materials or configuration report for a top-level asset. Support analysts use this data to understand component dependencies when diagnosing issues. For example, to find all components installed within a specific server instance, a query would join CSI_II_RELATIONSHIPS to CSI_ITEM_INSTANCES twice: once for the parent subject and once for the child objects.

• Sample Query: SELECT child.instance_number, child.serial_number FROM csi_ii_relationships rel, csi_item_instances parent, csi_item_instances child WHERE rel.subject_id = parent.instance_id AND rel.object_id = child.instance_id AND parent.instance_id = :p_parent_instance_id AND rel.relationship_type_code = 'COMPONENT_OF';
• Another common pattern is validating relationship integrity before a service operation, such as ensuring a component is not removed if it has active dependent connections.

Related Objects

As indicated by the foreign keys, CSI_II_RELATIONSHIPS has direct dependencies on several key Install Base tables. CSI_ITEM_INSTANCES is the master table for all tracked instances, referenced twice for the subject and object of each relationship. CSI_II_RELATION_TYPES provides the valid codes and descriptions for relationship types. The table also has a history counterpart, CSI_II_RELATIONSHIPS_H, which tracks changes to relationship records over time for auditing purposes. Furthermore, the transactional interface table CSI_T_II_RELATIONSHIPS references it, serving as the staging area for importing or processing relationship data from external systems before it is validated and merged into the base table.