Results for “cs_cp_revisions_maint_v”

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

Overview

CS_CP_REVISIONS_MAINT_V is an APPS-owned database view in the Oracle E-Business Suite Service (CS) module, designated with a status of VALID in both the 12.1.1 and 12.2.2 releases. Its purpose, as documented in the ETRM metadata, is to present the "Revision Details of a Product in InstalledBase." The view consolidates revision-level records stored in the CS_CP_REVISIONS table together with descriptive and contextual attributes drawn from Oracle Inventory, Order Management, and Installed Base tables. This combination allows revision history for a customer product to be reported alongside the item definition, the originating sales order, and the concatenated item flexfield. The view is therefore positioned as a reporting and integration surface rather than a transactional maintenance entity, despite the "MAINT" token in its name. It exposes the LINE_SERVICE_DETAIL_ID column that frequently prompts user searches, linking each revision to its corresponding service detail line.

Underlying Base Objects

The documented referenced base objects are CS_CP_REVISIONS, CS_CUSTOMER_PRODUCTS_ALL, MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, OE_ORDER_HEADERS_ALL, and OE_ORDER_LINES_ALL, together with the CS_STD and CSICUMPI_PUB packages. CS_CP_REVISIONS is the primary driving table, supplying all revision-level identifiers and attributes. CS_CUSTOMER_PRODUCTS_ALL is joined on CUSTOMER_PRODUCT_ID to anchor each revision to its installed base instance and to obtain the original order line reference. MTL_SYSTEM_ITEMS is joined on INVENTORY_ITEM_ID and ORGANIZATION_ID to retrieve the BOM_ITEM_TYPE, while MTL_SYSTEM_ITEMS_KFV supplies the concatenated item flexfield as PRODUCT. OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL are outer-joined to retrieve ORDERED_DATE, ORDER_NUMBER, and LINE_NUMBER. The CS_STD package is invoked repeatedly, notably GET_ITEM_VALDN_ORGZN_ID for the validation organization and GET_ITEM_REV_DESC to derive REVISION_DESCRIPTION. CSICUMPI_PUB is referenced as part of the object's dependent infrastructure.

Key Columns

The view exposes ROW_ID and CP_REVISION_ID as the primary row and revision identifiers, with OBJECT_VERSION_NUMBER supporting optimistic locking. CUSTOMER_PRODUCT_ID ties the record to CS_CUSTOMER_PRODUCTS_ALL. INVENTORY_ITEM_ID, SERIAL_NUMBER, REVISION, and LOT_NUMBER identify the specific item instance and its revision. LINE_SERVICE_DETAIL_ID and ORDER_LINE_ID associate the revision with its source order and service detail line, while SHIPPED_FLAG, DELIVERED_FLAG, and SHIPPED_DATE record fulfillment status. START_DATE_ACTIVE and END_DATE_ACTIVE bound the revision's effective period. Audit columns include LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. Fifteen ATTRIBUTE columns plus CONTEXT provide descriptive flexibility. NET_AMOUNT and CURRENCY_CODE carry financial data, and derived columns BOM_ITEM_TYPE, ORDERED_DATE, ORDER_NUMBER, LINE_NUMBER, PRODUCT, and REVISION_DESCRIPTION enrich reporting.

Common Use Cases and Queries

Typical scenarios include reporting all revisions of an installed product, tracing a revision back to its originating sales order, and joining revisions to service detail lines via LINE_SERVICE_DETAIL_ID. The following sample retrieves revision detail for a given customer product:

• SELECT cp_revision_id, inventory_item_id, serial_number, revision, line_service_detail_id, order_number, line_number FROM cs_cp_revisions_maint_v WHERE customer_product_id = :p_customer_product_id;
• SELECT cp_revision_id, serial_number, revision, shipped_flag, delivered_flag, shipped_date FROM cs_cp_revisions_maint_v WHERE inventory_item_id = :p_item_id AND revision = :p_revision;
• SELECT cp_revision_id, order_number, ordered_date, line_service_detail_id FROM cs_cp_revisions_maint_v WHERE line_service_detail_id = :p_line_service_detail_id;

Because the view references CS_STD for organization validation and revision description, query performance depends on the validation organization context. Consumers should treat the output as read-only and filter by CUSTOMER_PRODUCT_ID or INVENTORY_ITEM_ID to constrain result sets.