Search Results split_flag




Overview
Explore in AI Chat

Overview

CSI_CP_FORM_GRID_V is a backward-compatibility view owned by the APPS schema in Oracle E-Business Suite, defined within the CSI (Install Base) product. Its documented description — "Backward Compatible: Customer Product Form Grid" — indicates that it was created to preserve the column interface and behaviour of an earlier Customer Product form grid after the underlying Install Base data model was refactored. The view presents a flattened, form-oriented projection of install base instance records joined to customer account, party, order, and item information, allowing existing forms, concurrent programs, and custom extensions to continue querying under the original column names.

For reporting purposes the view behaves as a denormalised "customer product" fact source: one row per install base instance, enriched with account, party, order, and item attributes. The status VALID in 12.1.1 and 12.2.2 confirms it remains operational across both releases, so any query or report written against it is portable between them.

Underlying Base Objects

ETRM documents the following referenced objects: CSICUMPI_PUB (package), CSI_II_RELATIONSHIPS, CSI_INSTALL_PARAMETERS, CSI_INSTANCE_STATUSES, CSI_IP_ACCOUNTS, CSI_ITEM_INSTANCES, CSI_I_ORG_ASSIGNMENTS, CSI_I_PARTIES, CSI_LOOKUPS (view), CSI_SYSTEMS_VL (view), HR_OPERATING_UNITS (view), HZ_CUST_ACCOUNTS, HZ_PARTIES, MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, OE_AGREEMENTS, OE_ORDER_HEADERS_ALL, and OE_ORDER_LINES_ALL.

The primary driving entity is CSI_ITEM_INSTANCES (aliased CII), which supplies the instance identifier, serial number, revision, quantity, unit of measure, install location, status, dates, and the ATTRIBUTE1–15/ CONTEXT flexfield columns. CSI_I_PARTIES and CSI_IP_ACCOUNTS link instances to parties and accounts; HZ_CUST_ACCOUNTS and HZ_PARTIES supply ACCOUNT_NUMBER, PARTY_NAME, and ship-to/bill-to references. Order context is derived from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL via the instance's LAST_OE_ORDER_LINE_ID, yielding order number, ordered date, line number, and unit selling price. Item details come from MTL_SYSTEM_ITEMS and its key flexfield view. OE_AGREEMENTS supports agreement-based attributes, and CSI_INSTANCE_STATUSES, CSI_LOOKUPS, CSI_SYSTEMS_VL, HR_OPERATING_UNITS, CSI_I_ORG_ASSIGNMENTS, CSI_INSTALL_PARAMETERS, CSI_II_RELATIONSHIPS and the CSICUMPI_PUB package complete the dependency set. The column list in the view text corresponds directly to this join, and MOST_RECENT_FLAG is hard-coded to 'Y', reflecting the single-current-row semantics of the legacy form grid.

Key Columns

Columns defined as NULL in the view text (ORIGINAL_LINE_SERV_DETAIL_ID, SHIPPED_FLAG, DELIVERED_FLAG, PARENT_CP_ID, SHIPPED_DATE) are retained purely for backward interface compatibility and carry no data.

Common Use Cases and Queries

Typical uses include install base reporting, entitlement and service contract validation, order-to-install traceability, and customer product dashboards. Because the user searched on product_agreement_id, note that this view does not expose a column of that name; agreement linkage is implied through the OE_AGREEMENTS dependency and must be joined separately, or sourced from CSI_II_RELATIONSHIPS / CSICUMPI_PUB APIs. A representative query is:

SELECT customer_product_id, current_serial_number, account_number, principal_party_name, installation_date, original_order_number FROM apps.csi_cp_form_grid_v WHERE account_number = :p_account AND installation_date >= :p_from_date;

Additional filters on INVENTORY_ITEM_ID, CUSTOMER_PRODUCT_STATUS_ID, or ATTRIBUTE columns are common. Consumers should treat the NULL placeholder columns as non-queryable and use the view primarily for read-only reporting, since it is a legacy compatibility layer rather than a current interface.