Search Results okx_cust_prod_statuses_v

Overview

The OKX_CUST_PROD_STATUSES_V view is a reporting and integration object owned by the APPS schema within the OKX – Contracts Integration product module. It exposes the set of statuses that may be assigned to products in the installed base, providing a read-only, denormalized projection of the customer product status configuration held in the underlying Customer Support foundation tables. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the integration touchpoint through which contract and installed base functionality validates and resolves the lifecycle state of a customer product — for example, whether the product is active, cancelled, or terminated, and which downstream operations (incidents, service orders, or status changes) are permitted against it.

Because the view is a simple projection over a single base object, it is inexpensive to query and is commonly joined to installed base and contract line queries to enrich transactional data with status semantics. Its columns also carry the audit and multi-tenant context fields (START_DATE_ACTIVE, END_DATE_ACTIVE, OBJECT_VERSION_NUMBER, CONTEXT) expected of a standard EBS 12.2.2 date-effective and OAF-enabled entity.

Underlying Base Objects

The view is defined exclusively over the synonym CS_CUSTOMER_PRODUCT_STATUSES, which resolves to the APPS-owned base table holding the customer product status definitions. No joins, unions, or aggregations are performed — the view text selects columns directly from the CPS alias of that table. Consequently, the view inherits the row-level content, date-effectiveness, and any row-level security or org context applied to the base table. The documented referenced base object list confirms CS_CUSTOMER_PRODUCT_STATUSES (SYNONYM) as the sole dependency, and the view carries a VALID status in the APPS schema.

Key Columns

• CUSTOMER_PRODUCT_STATUS_ID — Primary identifier for each customer product status record; the join key to installed base and contract objects.
• NAME — User-facing status name (for example, Active, Cancelled, Terminated).
• CANCELLED_FLAG / TERMINATED_FLAG — Indicate whether the status represents a cancelled or terminated product state.
• STATUS_CHANGE_ALLOWED_FLAG — Determines whether a product currently in this status may transition to another status. This is the column most frequently used to control lifecycle transition validation.
• INCIDENT_ALLOWED_FLAG — Controls whether service incidents may be created against a product in this status.
• SERVICE_ORDER_ALLOWED_FLAG — Controls whether service orders may be raised for a product in this status.
• SEEDED_FLAG / SEEDED_STATUS_UPDATEABLE_FLAG — Distinguish Oracle-seeded statuses from user-defined ones and indicate whether seeded rows may be modified.
• UPDATEABLE_FLAG — Indicates whether the status record itself is maintainable.
• DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE — Descriptive text and date-effective activation window.
• OBJECT_VERSION_NUMBER, CONTEXT — Optimistic locking and DFF context columns standard to EBS 12.2.2.

Common Use Cases and Queries

The view is typically queried to resolve status attributes for a given installed base product, to drive conditional logic in contract or service processes, and to filter allowable statuses in LOVs. A representative query returning only statuses that permit status changes is:

• SELECT customer_product_status_id, name FROM okx_cust_prod_statuses_v WHERE status_change_allowed_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
• SELECT name, cancelled_flag, terminated_flag, incident_allowed_flag, service_order_allowed_flag FROM okx_cust_prod_statuses_v WHERE NVL(seeded_flag,'N') = 'Y';
• SELECT status.customer_product_status_id, status.name FROM cs_installed_base_products prod, okx_cust_prod_statuses_v status WHERE prod.customer_product_status_id = status.customer_product_status_id;