Results for “customer_product_id”

50+ results




Overview
Explore in AI Chat

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

Overview

CSI_CP_FORM_CONFIG_V is a backward-compatibility view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CSI (Install Base) product family. Its documented purpose is to expose Customer Product Form Configuration data in a form compatible with earlier releases of the Install Base application, allowing legacy customizations, reports, and integrations to continue functioning against the 12.1.1 and 12.2.2 data model.

The view presents the relationship between a customer product instance and its configuration parent, together with descriptive attributes such as configuration type, effective dates, root and parent descriptive information, and a children indicator. Because it is a view rather than a table, it carries no independent storage; the STATUS value of VALID indicates the definition compiles cleanly against its underlying objects. The view is read-only from a functional perspective and is intended for query and reporting use rather than direct DML. Notably, the alias PARENT_CP_ID — the term most commonly searched by implementers — is derived from the relationship's OBJECT_ID, not a dedicated base column.

Underlying Base Objects

The view is defined over four documented base objects plus one public package:

Joins to CSI_II_RELATIONSHIPS and CSI_I_VERSION_LABELS are outer joins, so instances without an active COMPONENT_OF relationship or version label are still returned.

Key Columns

  • CUSTOMER_PRODUCT_ID — the Install Base instance identifier.
  • RELATIONSHIP_ID / EXT_OBJECT_VERSION_NUMBER — relationship surrogate key and its object version number for optimistic locking metadata.
  • PARENT_CP_ID — the parent instance id, sourced from CIR.OBJECT_ID. This is the column most often sought by developers tracing configuration hierarchies.
  • CP_CONFIG_TYPE — relationship type code, defaulting to the version label when null.
  • CONFIG_TYPE — descriptive relationship type name from CSI_II_RELATION_TYPES.
  • CONFIG_START_DATE / CONFIG_END_DATE — effective dating of the configuration relationship.
  • CONFIG_ENABLED_FLAG — hard-coded to 'Y'.
  • CONFIG_PARENT_INFO / CONFIG_ROOT_INFO / CONFIG_CHILDREN_FLAG — descriptive and hierarchical indicators resolved through CSICUMPI_PUB.

Common Use Cases and Queries

Typical uses include configuration hierarchy reports, migration validation against legacy views, and integrations that must resolve a product's parent or root configuration. To find a specific parent configuration:

SELECT CUSTOMER_PRODUCT_ID, PARENT_CP_ID, CONFIG_TYPE, CONFIG_PARENT_INFO
FROM APPS.CSI_CP_FORM_CONFIG_V
WHERE PARENT_CP_ID IS NOT NULL;

To list all configured roots for a given instance, join through CUSTOMER_PRODUCT_ID and filter on CONFIG_CHILDREN_FLAG = 'Y'. Because the view performs PL/SQL function calls per row, queries returning large result sets should restrict rows through the relationship table and expected configuration types to avoid performance degradation.