Results for “component_of”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.CSI_CP_FORM_CONFIG_V is an Oracle E-Business Suite view within the Customer Products (CSI) module, exposed under the APPS schema. In Oracle EBS 12.1.1 and 12.2.2 it functions as the form-driven configuration data source for Customer Product instances, presentational layer that denormalizes configuration relationships into a single, form-friendly result set. The view is particularly significant when users search on the term component_of, because its row-producing logic is anchored to the relationship type code 'COMPONENT_OF' defined in CSI_II_RELATION_TYPES. Rather than storing data itself, the view assembles instance identifiers, relationship metadata, and derived descriptive attributes so that Oracle Forms and concurrent programs can render a Customer Product configuration hierarchy without issuing complex joins directly against the base transaction tables.

The view is owned by APPS and is therefore queried by application modules, personalizations, and ad hoc reporting tools under the standard APPS security context. It also serves integration points, such as interfaces that need to publish configuration composition to downstream systems, because its column set already includes labels, dates, and root/child indicators required by external consumers.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects for APPS.CSI_CP_FORM_CONFIG_V:

• CSICUMPI_PUB (PACKAGE) — supplies the PL/SQL functions GET_PART_INFORMATION, GET_ROOT_INFORMATION, and GET_CHILDREN_FLAG used to derive descriptive configuration attributes.
• CSI_II_RELATIONSHIPS (SYNONYM) — the relationship fact table (CIR alias) linking subject instances to parent instances, including relationship type, active dates, and object version.
• CSI_II_RELATION_TYPES (SYNONYM) — the relationship type lookup (CIRT alias) providing the human-readable CONFIG_TYPE name.
• CSI_ITEM_INSTANCES (SYNONYM) — the item instance master (CII alias), source of INSTANCE_ID for each Customer Product instance.
• CSI_I_VERSION_LABELS (SYNONYM) — version label data (CIVL alias) supplying fallback configuration type and start date values.

The join between CII and CIR is an outer join on SUBJECT_ID, and both the CIVL join and the 'COMPONENT_OF' predicate are outer-joined, so instances without a component relationship still appear. The CIRT join is likewise outer-joined to avoid dropping relationships whose type is not defined in the lookup.

Key Columns

• CUSTOMER_PRODUCT_ID — INSTANCE_ID from CSI_ITEM_INSTANCES; the Customer Product instance key.
• RELATIONSHIP_ID / EXT_OBJECT_VERSION_NUMBER — the underlying relationship identifier and its version (from CIR.OBJECT_VERSION_NUMBER).
• CP_CONFIG_TYPE — NVL of the relationship type code and the version label; typically 'COMPONENT_OF'.
• CONFIG_START_DATE / CONFIG_END_DATE — active start (falling back to version label timestamp) and active end date of the relationship.
• CONFIG_TYPE — descriptive name from CSI_II_RELATION_TYPES.NAME.
• CONFIG_ENABLED_FLAG — hard-coded 'Y', indicating configuration is active.
• PARENT_CP_ID — CIR.OBJECT_ID, the parent Customer Product instance.
• CONFIG_PARENT_INFO / CONFIG_ROOT_INFO / CONFIG_CHILDREN_FLAG — derived via CSICUMPI_PUB functions to describe parent, root, and child presence.

Common Use Cases and Queries

Typical usage includes displaying the composition of a configured product on an Oracle Form, verifying which instances are components of a parent, and validating active configuration windows. A representative query follows:

• SELECT customer_product_id, parent_cp_id, cp_config_type, config_start_date, config_end_date FROM apps.csi_cp_form_config_v WHERE cp_config_type = 'COMPONENT_OF';
• SELECT customer_product_id, config_root_info, config_children_flag FROM apps.csi_cp_form_config_v WHERE parent_cp_id = :parent_instance_id;
• SELECT config_type, COUNT(*) FROM apps.csi_cp_form_config_v GROUP BY config_type;

Because the derived columns invoke packaged functions, performance-sensitive extracts should filter on indexed base identifiers such as CUSTOMER_PRODUCT_ID or PARENT_CP_ID before evaluating the function-based columns.