Search Results cp_status




Overview
Explore in AI Chat

Overview

CSI_CUST_PROD_MAINT_V is a backward-compatibility view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is delivered by the CSI (Install Base) product module and presents customer product maintenance details — that is, the installed base of customer products together with the associated customer, party, order, system, and status information. The view exists so that customizations, reports, and integrations written against earlier releases (notably 11i) continue to function after an upgrade to R12, without requiring those consumers to be rewritten against the newer Install Base data model.

The view is documented as VALID in the ETRM metadata. Its name reflects its purpose: CSI for the Install Base schema, CUST_PROD_MAINT for "customer product maintenance," and _V denoting a database view rather than a physical table. Because it is a view, no data is stored in it; all columns are derived at query time from the underlying tables, synonyms, and package functions. From a reporting standpoint, it is principally a read-only construct intended for querying, not for DML.

Underlying Base Objects

The view is defined over a mixture of base tables (referenced through synonyms), other views, and a PL/SQL package. The documented referenced base objects are:

Key Columns

The projection exposes a broad set of attributes. Identity and audit columns include ROW_ID, INSTANCE_ID, INSTANCE_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. Notably, the view explicitly selects CII.MANUALLY_CREATED_FLAG, the column most closely related to the user search term "created_manually_flag"; this flag indicates whether the item instance was created manually rather than through an automated process.

Product and item columns include INVENTORY_ITEM_ID, INVENTORY_REVISION, SERIAL_NUMBER, LOT_NUMBER (aliased CP_LOT_NUMBER), QUANTITY, UNIT_OF_MEASURE, and the key flexfield CONCATENATED_SEGMENTS. Customer-facing columns include ACCOUNT_NUMBER, PARTY_NAME, SHIP_TO_ADDRESS, BILL_TO_ADDRESS, and PARTY_ACCOUNT_ID. Order and commercial columns include ORDERED_DATE, ORDER_NUMBER, LINE_NUMBER, LINK_TO_LINE_ID, UNIT_SELLING_PRICE, PRICE_LIST_ID, CUST_PO_NUMBER, and PRODUCT_AGREEMENT. Lifecycle and status columns include INSTANCE_STATUS_ID, CP_STATUS, TERMINATED_FLAG, STATUS_CHANGE_ALLOWED_FLAG, INCIDENT_ALLOWED_FLAG, SERVICE_ORDER_ALLOWED_FLAG, ACTIVE_START_DATE, ACTIVE_END_DATE, and RETURN_BY_DATE/ACTUAL_RETURN_DATE. Fifteen generic ATTRIBUTE columns plus CONTEXT are also exposed. Several positions are populated with NULL as placeholders retained for backward compatibility.

Common Use Cases and Queries

Typical uses include install base reporting, tracing an instance back to its originating sales order, identifying manually created instances, and extracting configuration hierarchies. The manual-creation flag is frequently queried to reconcile items entered by users against those generated automatically.

Example — list instances that were created manually:

  • SELECT instance_id, instance_number, serial_number, inventory_item_id, manually_created_flag FROM apps.csi_cust_prod_maint_v WHERE manually_created_flag = 'Y';

Example — join installed products to their order context:

  • SELECT instance_number, party_name, order_number, line_number, ordered_date, quantity FROM apps.csi_cust_prod_maint_v WHERE account_number = :account_number ORDER BY ordered_date DESC;

Example — inspect configuration hierarchy for an instance:

  • SELECT instance_id, config_parent_info FROM apps.csi_cust_prod_maint_v WHERE instance_id = :instance_id;

Because the view performs concatenated lookups and invokes package functions per row, queries returning large result sets should be filtered tightly and avoided in high-volume batch processes where direct access to the underlying Install Base tables is preferred.