Search Results target_commitment_date

Overview

CSI_T_II_RELATIONSHIPS_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema within the CSI - Install Base product. It is documented as a view built on top of Transaction Details Relationships, exposing relationship data that links install base transaction lines to subject and object entities. The object carries a VALID status in both EBS 12.1.1 and 12.2.2, indicating it is a supported, active database object intended for query and reporting use.

Because the view is defined over a single underlying relationship table, its principal role is to provide a stable, presentation-layer access point for install base relationship records. This makes it suitable for reporting, integration extracts, and operational queries that need to retrieve relationship attributes without being coupled directly to the base table name. The presence of the TARGET_COMMITMENT_DATE column is significant for users searching on that term: it is the field that records the commitment date associated with a relationship, and it is surfaced directly through this view.

Underlying Base Objects

The documented view text shows a straightforward projection: every column is selected from CSI_T_II_RELATIONSHIPS, which is referenced as a SYNONYM in the documented metadata. No joins, filters, or computed expressions are applied. Consequently, CSI_T_II_RELATIONSHIPS_V is a one-to-one, row-preserving view over the base relationship table.

• Referenced base object: CSI_T_II_RELATIONSHIPS (SYNONYM).
• Relationship type: direct SELECT of all listed columns with no aggregation or transformation.
• Owner: APPS, consistent with the standard EBS schema convention for shared install base objects.
• Privileges: access is typically granted via APPS and controlled through the standard CSI/Install Base responsibility and role model.

Because the view mirrors the base table, any row inserted, updated, or deleted in the base relationship table is immediately reflected in the view. There is no materialization or caching layer.

Key Columns

The view exposes seventeen columns, all originating from the base table. The most relevant columns are summarized below.

• TXN_RELATIONSHIP_ID: Primary identifier for the relationship record.
• TRANSACTION_LINE_ID: Links the relationship to the originating install base transaction line.
• SUBJECT_TYPE / SUBJECT_ID: Identify the subject side of the relationship (the acting entity).
• OBJECT_TYPE / OBJECT_ID: Identify the object side of the relationship (the target entity).
• RELATIONSHIP_TYPE_CODE: Classifies the nature of the relationship between subject and object.
• SUB_CONFIG_INST_HDR_ID / SUB_CONFIG_INST_REV_NUM / SUB_CONFIG_INST_ITEM_ID: Identify the subject's configuration instance header, revision, and item context.
• OBJ_CONFIG_INST_HDR_ID / OBJ_CONFIG_INST_REV_NUM / OBJ_CONFIG_INST_ITEM_ID: Identify the object's configuration instance header, revision, and item context.
• TARGET_COMMITMENT_DATE: The commitment date targeted by the relationship, typically driving scheduling and fulfillment reporting.
• ACTIVE_START_DATE / ACTIVE_END_DATE: Date-range columns defining when the relationship is effective.
• OBJECT_VERSION_NUMBER: Concurrency control column used for optimistic locking.

Common Use Cases and Queries

The view is frequently used to report on install base relationships and, in particular, to surface commitment dates tied to those relationships. A typical query joins the view to configuration or item information while filtering on the target commitment date.

Example: retrieve relationships targeting a commitment date.

• SELECT txn_relationship_id, transaction_line_id, subject_id, object_id, relationship_type_code, target_commitment_date FROM csi_t_ii_relationships_v WHERE target_commitment_date >= :start_date AND target_commitment_date < :end_date;

Example: list active relationships for a specific subject.

• SELECT txn_relationship_id, object_type, object_id, active_start_date, active_end_date FROM csi_t_ii_relationships_v WHERE subject_id = :subject_id AND TRUNC(SYSDATE) BETWEEN active_start_date AND NVL(active_end_date, SYSDATE);

Because the view is a direct projection, developers and report authors can reliably use it in place of the base synonym when only the documented columns are required.