Search Results status_change_allowed_flag




Overview
Explore in AI Chat

Overview

CSI_CUSTOMER_PRODUCT_STATUS_V is an APPS-owned database view within the CSI (Install Base) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. The view is documented as "Backward Compatible: Customer Product Statuses," which identifies its role as a compatibility shim rather than a new object. In earlier releases of Oracle EBS, customer product status definitions were exposed to forms, concurrent programs, and integrations under a legacy naming convention. When Install Base was re-architected around the CSI_INSTANCE_STATUSES entity, this view was retained so that dependent code, custom reports, and external interfaces referencing the older name would continue to resolve without modification. It therefore presents instance-status reference data in the shape expected by legacy consumers, providing a read-only, denormalized projection of status setup rows.

Underlying Base Objects

The ETRM metadata records a single referenced base object, the synonym CSI_INSTANCE_STATUSES. The view text confirms this relationship directly: every column is sourced from the alias CIS, which resolves to CSI_INSTANCE_STATUSES, joined to no other table. The SELECT list contains only simple column references and one literal, so the view is a pure projection with no joins, unions, or aggregation. Because the join is trivial, row counts and identity are preserved: each row in CSI_INSTANCE_STATUSES corresponds to exactly one row in CSI_CUSTOMER_PRODUCT_STATUS_V. The CANCELLED_FLAG column is not a stored attribute; it is emitted as a literal NULL, indicating that cancellation semantics were consolidated elsewhere and that the legacy column is retained only to satisfy callers expecting it to exist. Administrators should note that DML against the view is not intended; status setup must be maintained through the Install Base setup forms or APIs that target the underlying status table.

Key Columns

The first column, CUSTOMER_PRODUCT_STATUS_ID, is the legacy identifier mapped from INSTANCE_STATUS_ID and serves as the primary key. NAME and DESCRIPTION carry the status name and its descriptive text, while START_DATE_ACTIVE and END_DATE_ACTIVE govern the effective dating window. The controlling behavior flags include STATUS_CHANGE_ALLOWED_FLAG, which determines whether a customer product can transition away from the status; INCIDENT_ALLOWED_FLAG, controlling service request creation; SERVICE_ORDER_ALLOWED_FLAG, controlling service order activity; and TERMINATED_FLAG, marking terminal statuses. SEEDED_FLAG and SEEDED_STATUS_UPDATEABLE_FLAG distinguish Oracle-supplied statuses and indicate whether their attributes may be modified. UPDATEABLE_FLAG governs user maintenance of the row generally. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER support concurrency control, while ATTRIBUTE1 through ATTRIBUTE15 plus CONTEXT supply the flexfield and descriptive flexfield storage used by the status definition.

Common Use Cases and Queries

Because the user search term was "status_change_allowed_flag," the most typical query filters on that column to identify statuses from which transitions are permitted — useful when validating transitions, troubleshooting Install Base errors, or driving custom reporting. Other common scenarios include listing all active statuses for a responsibility, checking seeded versus user-defined statuses, and auditing flag settings across environments.

  • List statuses permitting status change: SELECT customer_product_status_id, name, terminated_flag, incident_allowed_flag FROM csi_customer_product_status_v WHERE status_change_allowed_flag = 'Y' AND NVL(end_date_active, SYSDATE) >= SYSDATE ORDER BY name;
  • Identify Oracle-seeded, non-updateable statuses: SELECT name, seeded_flag, seeded_status_updateable_flag FROM csi_customer_product_status_v WHERE seeded_flag = 'Y' AND NVL(seeded_status_updateable_flag,'N') = 'N';
  • Audit activity and service controls by status: SELECT name, incident_allowed_flag, service_order_allowed_flag, terminated_flag FROM csi_customer_product_status_v ORDER BY name;

Because the view is read-only and unfiltered, reports should apply their own date and flag predicates rather than relying on the view to restrict rows.