Results for “cs_cp_revisions”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CS_CP_REVISIONS is a Service (CS) module table in the Oracle E-Business Suite database, owned by the CS schema. It stores revision-level information about products that exist in the installed base. In EBS Service, an installed base instance (held in CS_CUSTOMER_PRODUCTS_ALL) can have multiple revisions recorded over its lifecycle, and CS_CP_REVISIONS is the repository for those revision records. Each row captures details about a specific revision of a customer product, including ordering, shipping, and pricing context, and is linked to the parent installed base instance, the underlying inventory item, and the line service detail record used to originally transact the item.

From a data modeling perspective, the heuristic classification for this object is hub-leaning. It carries a strong single-column surrogate key (CP_REVISION_ID) that many downstream tables reference, while also holding descriptive shipping, order, and pricing attributes. In practice it functions as a central reference point for revision identity, with the surrounding order, incident, and shipping attributes acting as satellite-style context.

Key Information Stored

The primary key is CP_REVISION_ID, which is also the unique index documented as CS_CP_REVISIONS_U1 and the source of the CS_CP_REVISIONS_PK constraint. This surrogate identifier is the business-key candidate used to uniquely identify a revision record; there is no separate multi-column business key exposed in the metadata.

Among the 62 documented columns, the most operationally significant are:

• CP_REVISION_ID — surrogate primary key and the column most commonly used in joins and lookups.
• CUSTOMER_PRODUCT_ID — foreign key to CS_CUSTOMER_PRODUCTS_ALL, identifying the installed base instance this revision belongs to.
• INVENTORY_ITEM_ID — the inventory item being revised.
• PRODUCT_USAGE_ID and SERIAL_NUMBER — usage context and the serial number of the physical unit.
• REVISION — the revision label or value assigned to this record.
• SHIPPED_FLAG, DELIVERED_FLAG, SHIPPED_DATE — shipment lifecycle state and date.
• ORDER_NUMBER, ORDER_LINE_NUMBER, ORDER_LINE_ID, ORDER_DATE, LINK_TO_ORDER_LINE_ID — the originating order and line reference.
• NET_AMOUNT and CURRENCY_CODE — monetary context for the revision.
• LINE_SERVICE_DETAIL_ID — foreign key to CS_LINE_INST_DETAILS, tying the revision to its line-level service detail.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective dating for the revision record.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security access.
• COMPONENT_FROZEN_FLAG, MIGRATED_STATUS_FLAG, and OBJECT_VERSION_NUMBER — state, migration, and optimistic locking controls.

Fifteen ATTRIBUTE and fifteen PRICING_ATTRIBUTE columns with corresponding CONTEXT and PRICING_CONTEXT fields provide flexfield extensibility.

Common Use Cases and Queries

The most frequent access pattern is resolving a revision by its primary key or by its parent installed base instance. For example, retrieving all revisions for an installed base product:

• SELECT cp_revision_id, revision, shipped_flag, shipped_date, order_number, net_amount FROM cs.cs_cp_revisions WHERE customer_product_id = :cp_id ORDER BY creation_date DESC;

Because CS_CUSTOMER_PRODUCTS_ALL.CURRENT_CP_REVISION_ID references this table, a common query identifies the current revision of an installed base product by joining the parent's current pointer to the revision row. Incident analysis joins CS_INCIDENTS_ALL_B to CS_CP_REVISIONS through CP_REVISION_ID, CP_COMPONENT_VERSION_ID, or CP_SUBCOMPONENT_VERSION_ID to determine which revision a service incident affects. Reporting use cases include shipment tracking (SHIPPED_FLAG, SHIPPED_DATE, DELIVERED_FLAG), pricing reconciliation by NET_AMOUNT and CURRENCY_CODE, and effective-dated revision history using START_DATE_ACTIVE and END_DATE_ACTIVE. The version column OBJECT_VERSION_NUMBER should be checked during updates to prevent lost writes.

Related Objects

• CS_CUSTOMER_PRODUCTS_ALL — parent installed base table; joined via CS_CP_REVISIONS.CUSTOMER_PRODUCT_ID and referenced back through CURRENT_CP_REVISION_ID.
• CS_LINE_INST_DETAILS — line service detail; joined via LINE_SERVICE_DETAIL_ID.
• CS_INCIDENTS_ALL_B — service incidents; joined via CP_REVISION_ID, CP_COMPONENT_VERSION_ID, and CP_SUBCOMPONENT_VERSION_ID.
• CS_INCIDENTS_AUDIT_B — audit trail for incidents; joined via CP_REVISION_ID.
• FND_SECURITY_GROUPS — security group lookup; joined via SECURITY_GROUP_ID.

These relationships place CS_CP_REVISIONS at the center of installed base revision tracking, incident diagnosis, and order-to-customer-product lineage in the CS module.