Search Results rel_attribute1

Overview

The CSI_INST_CHILD_DETAILS_V view is a predefined Oracle E-Business Suite database object owned by the APPS schema and delivered as part of the CSI (Install Base) product family. Its stated purpose, per the ETRM metadata, is to "give the children of a Known Instance." In practical terms, the view flattens the parent-child hierarchy maintained in the Install Base relationship model so that a reporting or integration layer can retrieve every child instance associated with a given parent instance in a single query, without joining the relationship table to the item instance table manually.

Because Install Base relationships are stored generically in CSI_II_RELATIONSHIPS using subject and object identifiers, the raw table is difficult to consume directly: it does not carry descriptive instance attributes such as serial number, item identifier, or status. The view bridges that gap by projecting the relationship row alongside the attribute set of the child instance itself. This makes it a natural source for customer-facing 360-degree asset views, service contract eligibility checks, warranty coverage reports, and integration extracts that must push installed base hierarchies into external CRM, field service, or data warehouse platforms.

In both Oracle EBS 12.1.1 and 12.2.2 the object retains a VALID status in the APPS schema. The 12.2.2 metadata confirms the two documented base objects described below. The view is read-only and exposes no DML capability; consumers treat it purely as a query surface.

Underlying Base Objects

The documented reference list for the view contains two synonyms: CSI_II_RELATIONSHIPS and CSI_ITEM_INSTANCES. CSI_II_RELATIONSHIPS is the relationship registry that holds the parent-child linkage, the relationship type, positional information, display ordering, the mandatory flag, the DESCRIPTIVE flexfield context and attribute columns, and the standard WHO audit columns. CSI_ITEM_INSTANCES is the installed base master instance table holding the descriptive attributes of each tracked item instance, including serial number, lot number, inventory item identity, and status.

The view text drives off CSI_II_RELATIONSHIPS (aliased CIR) as the primary relationship source, using CIR.SUBJECT_ID as the CHILD_ID and CIR.OBJECT_ID as the PARENT_ID, then joins to CSI_ITEM_INSTANCES (aliased CII) to enrich the child with its instance attributes. Both underlying objects are resolved through APPS synonyms, so the view remains stable across multi-org and localization installations.

Key Columns

The relationship-derived columns are prefixed REL_ to disambiguate them from the instance columns. CHILD_ID and PARENT_ID identify the hierarchy endpoints; RELATIONSHIP_ID and RELATIONSHIP_TYPE_CODE classify the linkage; POSITION_REFERENCE and DISPLAY_ORDER control presentation sequence; REL_ACTIVE_START_DATE and REL_ACTIVE_END_DATE bound the validity of the relationship itself. REL_ATTRIBUTE1 through REL_ATTRIBUTE15 expose the descriptive flexfield segments, while REL_CONTEXT identifies the flexfield structure used.

Critically for the searching user, the view exposes REL_LAST_UPDATE_DATE, mapped from CIR.LAST_UPDATE_DATE, which records when the relationship row was last modified. This is distinct from the instance-level LAST_UPDATE_DATE semantics that appear on the underlying instance record, and it is the column most often used to drive incremental extracts. The audit trio REL_CREATED_BY, REL_LAST_UPDATED_BY, and REL_LAST_UPDATE_LOGIN, together with REL_OBJECT_VERSION_NUMBER, provides concurrency and change-tracking support. Instance columns include INSTANCE_NUMBER, SERIAL_NUMBER, LOT_NUMBER, INVENTORY_ITEM_ID, QUANTITY, UNIT_OF_MEASURE, INSTANCE_STATUS_ID, ACCOUNTING_CLASS_CODE, and active date ranges for the child instance.

Common Use Cases and Queries

The most frequent use is retrieving all children of a known parent instance. Because the view filters by parent internally through the join predicate, callers typically add the parent key explicitly:

• Hierarchy expansion — retrieve children for a specific parent to render an asset tree.
• Incremental integration — extract relationships changed since a watermark using REL_LAST_UPDATE_DATE.
• Warranty and entitlement checks — join child INSTANCE_STATUS_ID and active dates to entitlement rules.
• Data quality reporting — identify relationships lacking a matching instance row or with stale dates.

A representative query for the searched attribute is:

SELECT child_id, parent_id, relationship_id, relation_type_code, serial_number, rel_last_update_date, rel_last_updated_by FROM csi_inst_child_details_v WHERE parent_id = :p_parent_instance_id AND rel_last_update_date >= :p_since_date ORDER BY display_order;

When filtering on the searched term, note that REL_LAST_UPDATE_DATE reflects the relationship change timestamp, not the instance change timestamp; both should be evaluated when building a complete delta extract.