Search Results rel_attribute15




Overview

APPS.CSI_INST_PARENT_DETAILS_V is a reporting and integration view in Oracle E-Business Suite (12.1.1 and 12.2.2) that exposes parent-to-child relationships between item instances together with the detail attributes of the child instance. It is defined over the CSI relationships model and the CSI item instance master, presenting each relationship row alongside the descriptive, transactional, and lifecycle attributes of the associated child instance. The view is owned by APPS and is consumed by ETRM (Enterprise Track and Return Management) functionality and by customer extensions that need to navigate installed base hierarchies.

The object is particularly relevant to the search term "rel_attribute1". The view does not expose a bare ATTRIBUTE1 column; instead, the attribute columns inherited from CSI_II_RELATIONSHIPS are prefixed with REL_ so that they can coexist with the instance-level columns projected from CSI_ITEM_INSTANCES. REL_ATTRIBUTE1 through REL_ATTRIBUTE15 therefore represent the descriptive-flexfield segments of the relationship record itself, not of the child instance.

Underlying Base Objects

The documented base objects referenced by the view are:

  • CSI_II_RELATIONSHIPS (SYNONYM) — the relationship table that stores parent/child links between item instances, including relationship type, position reference, display order, mandatory flag, context, attributes, and the standard WHO columns.
  • CSI_ITEM_INSTANCES (SYNONYM) — the item instance master, supplying instance number, item and revision, serial and lot information, location, status, and the many transactional reference columns.

The join correlates the relationship's subject (child) to the instance identifier, so that each row of the view combines one relationship with the child instance it points to. Because the view is defined over synonyms in the APPS schema, it is available to any responsibility or concurrent program that can read the CSI schema objects.

Key Columns

Common Use Cases and Queries

Typical uses include installed-base hierarchy reporting, where a parent instance must be listed with all of its children; service and depot repair lookups, where the relationship flexfield is used to classify the link; and integration extracts that publish parent/child structures to external systems.

To retrieve relationship flexfield values for a known parent:

  • SELECT PARENT_ID, CHILD_ID, RELATIONSHIP_TYPE_CODE, REL_CONTEXT, REL_ATTRIBUTE1 FROM APPS.CSI_INST_PARENT_DETAILS_V WHERE PARENT_ID = :p_parent_id AND TRUNC(SYSDATE) BETWEEN REL_ACTIVE_START_DATE AND NVL(REL_ACTIVE_END_DATE, TRUNC(SYSDATE));

To find children of a specific serial-numbered instance:

  • SELECT v.PARENT_ID, v.CHILD_ID, v.SERIAL_NUMBER, v.REL_ATTRIBUTE1 FROM APPS.CSI_INST_PARENT_DETAILS_V v WHERE v.INSTANCE_NUMBER = :p_instance_number OR v.PARENT_ID = :p_parent_id;

To report all relationships carrying a specific flexfield value:

  • SELECT RELATIONSHIP_ID, PARENT_ID, CHILD_ID, REL_ATTRIBUTE1 FROM APPS.CSI_INST_PARENT_DETAILS_V WHERE REL_ATTRIBUTE1 = :p_value;

Because the view performs a straightforward join across the two CSI base tables, the usual predicates on ACTIVE_START_DATE/ACTIVE_END_DATE and REL_ACTIVE_START_DATE/REL_ACTIVE_END_DATE should be applied to avoid returning expired links.