Search Results position_reference

Overview

CSI_INST_PARENT_DETAILS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the CSI (Install Base) product family and its documented purpose is to return the parent of a known instance. In the Install Base data model, item instances are connected to one another through relationship records that express hierarchical or logical associations such as component-of, contains, or configured-with semantics. This view flattens the parent side of such a relationship into a single denormalized row so that callers do not have to join CSI_II_RELATIONSHIPS to CSI_ITEM_INSTANCES in order to identify the parent instance of a given child.

Because the view carries the full audit and descriptive column set for both the relationship and the parent instance, it is suited for reporting, reconciliation, and integration scenarios where a downstream system must resolve an instance to its parent and simultaneously obtain the parent's identifying attributes such as serial number, instance number, and inventory item. The view is identified in the ETRM repository as VALID and is referenced primarily by APPS-tier code and customer reporting objects.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS as synonyms:

• CSI_II_RELATIONSHIPS — the instance-to-instance relationship table. It supplies OBJECT_ID (aliased PARENT_ID), SUBJECT_ID (aliased CHILD_ID), the relationship identifiers, and the full set of relationship attributes including REL_LAST_UPDATE_DATE.
• CSI_ITEM_INSTANCES — the master instance table. It supplies the parent instance's INSTANCE_NUMBER, SERIAL_NUMBER, INVENTORY_ITEM_ID, and the remaining CII-prefixed columns.

Conceptually the view joins the relationship rows to the item instance rows so that OBJECT_ID of the relationship is matched to the parent instance record. The PREFIX convention makes the provenance explicit: CIR columns originate from CSI_II_RELATIONSHIPS, while CII columns originate from CSI_ITEM_INSTANCES. No column from the child instance is projected, so the view describes the parent only.

Key Columns

• PARENT_ID / CHILD_ID — the OBJECT_ID and SUBJECT_ID of the underlying relationship, identifying the parent and child instances respectively.
• RELATIONSHIP_ID, RELATIONSHIP_TYPE_CODE — surrogate key and semantic classification of the relationship.
• REL_ACTIVE_START_DATE, REL_ACTIVE_END_DATE — validity window of the relationship itself, distinct from the instance validity dates.
• REL_LAST_UPDATE_DATE — the Last Update Date of the underlying CSI_II_RELATIONSHIPS row, surfaced with the REL_ prefix. This is the column users typically search for when they need to identify recently modified parent relationships.
• REL_CREATED_BY, REL_CREATION_DATE, REL_LAST_UPDATED_BY, REL_LAST_UPDATE_LOGIN, REL_OBJECT_VERSION_NUMBER — audit and concurrency columns inherited from the relationship record.
• INSTANCE_NUMBER, SERIAL_NUMBER, INVENTORY_ITEM_ID, INVENTORY_REVISION — the principal identifying attributes of the parent instance.
• INSTANCE_STATUS_ID, INSTANCE_CONDITION_ID, INSTANCE_TYPE_CODE — state and classification of the parent instance.
• LOCATION_TYPE_CODE, LOCATION_ID, INV_ORGANIZATION_ID, INV_SUBINVENTORY_NAME, INV_LOCATOR_ID — physical placement of the parent instance.
• QUANTITY, UNIT_OF_MEASURE, LOT_NUMBER, MFG_SERIAL_NUMBER_FLAG — quantity and lot-level attributes.
• REL_ATTRIBUTE1 through REL_ATTRIBUTE15, REL_CONTEXT — the descriptive flexfield segments of the relationship.

Common Use Cases and Queries

Typical uses include install-base hierarchy reporting, identifying the parent configuration of a component instance, and incremental interfaces that pull only relationships changed since a prior extraction. The REL_LAST_UPDATE_DATE column is the natural watermark for such incremental loads.

To list all parents with their serial numbers:

• SELECT PARENT_ID, CHILD_ID, RELATIONSHIP_TYPE_CODE, INSTANCE_NUMBER, SERIAL_NUMBER FROM APPS.CSI_INST_PARENT_DETAILS_V;

To identify parent relationships modified after a given date:

• SELECT PARENT_ID, CHILD_ID, RELATIONSHIP_ID, INSTANCE_NUMBER, SERIAL_NUMBER, REL_LAST_UPDATE_DATE FROM APPS.CSI_INST_PARENT_DETAILS_V WHERE REL_LAST_UPDATE_DATE >= :p_from_date ORDER BY REL_LAST_UPDATE_DATE;

To resolve the parent configuration of a specific child instance:

• SELECT PARENT_ID, RELATIONSHIP_TYPE_CODE, INSTANCE_NUMBER, SERIAL_NUMBER FROM APPS.CSI_INST_PARENT_DETAILS_V WHERE CHILD_ID = :p_child_id AND SYSDATE BETWEEN REL_ACTIVE_START_DATE AND NVL(REL_ACTIVE_END_DATE, SYSDATE);

Because the view exposes only the parent side, reverse traversal (finding children of a given instance) requires querying CSI_II_RELATIONSHIPS directly or a complementary view.