Search Results cp_revision_id




Overview
Explore in AI Chat

Overview

The CS_CP_REVISIONS table is a core data object within the Oracle E-Business Suite Service (CS) module, specifically for versions 12.1.1 and 12.2.2. It serves as the central repository for managing revision-level information for products tracked in the installed base. This table is fundamental to the configuration management and service history of customer assets. It enables the tracking of different versions or revisions of a product over its lifecycle, which is critical for accurate service delivery, incident management, and understanding the precise configuration of a customer's installed base at any point in time.

Key Information Stored

The table's primary purpose is to store discrete revision records linked to customer products. Its structure is defined by key columns that establish relationships and capture revision details. The primary key, CP_REVISION_ID, uniquely identifies each revision record. The CUSTOMER_PRODUCT_ID column is a foreign key to CS_CUSTOMER_PRODUCTS_ALL, linking the revision to the specific product instance in the installed base. The LINE_SERVICE_DETAIL_ID foreign key links to CS_LINE_INST_DETAILS, connecting the revision to its originating service line detail. While the provided metadata does not list all columns, the foreign key relationships imply the table likely contains version identifiers, effective dates, and status information to manage the revision's validity and lifecycle.

Common Use Cases and Queries

This table is essential for queries related to product configuration history and service impact analysis. A common use case is retrieving the complete revision history for a specific customer product to support troubleshooting or warranty validation. Another critical scenario involves joining to incident tables to determine which product revision was associated with a reported service request. A typical reporting query might join CS_CP_REVISIONS with CS_CUSTOMER_PRODUCTS_ALL and CS_INCIDENTS_ALL_B to analyze failure rates or service trends by product revision.

  • Sample Query Pattern: Selecting revision details for incidents: SELECT inc.incident_number, cpr.* FROM cs_incidents_all_b inc, cs_cp_revisions cpr WHERE inc.cp_revision_id = cpr.cp_revision_id;
  • Use Case: Identifying the current active revision for a product instance by leveraging the CS_CUSTOMER_PRODUCTS_ALL.CURRENT_CP_REVISION_ID pointer.

Related Objects

The CS_CP_REVISIONS table is integral to the Service schema's data model, with several key dependencies. It has direct foreign key relationships to CS_CUSTOMER_PRODUCTS_ALL and CS_LINE_INST_DETAILS, which are its primary parents. Crucially, it is referenced as a parent table by CS_CUSTOMER_PRODUCTS_ALL via the CURRENT_CP_REVISION_ID column, which points to the active revision. Furthermore, it is heavily referenced by the CS_INCIDENTS_ALL_B table through three separate foreign key columns (CP_REVISION_ID, CP_COMPONENT_VERSION_ID, CP_SUBCOMPONENT_VERSION_ID), underscoring its vital role in linking service incidents to the exact product configuration involved.