Results for “cs_cp_maint_v”

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

Overview

CS_CP_MAINT_V is a Service (CS) module view that exposes the products currently held in the customer installed base. Each row represents a single customer product instance—the deliverable or configurabled item a customer has purchased, received, and (potentially) installed—together with its serial number, revision, status, original order and price information, party and account identification, and service-entitlement attributes. The name "CP" refers to the Customer Product entity, while "MAINT" denotes its role in maintenance and service operations.

The view is primarily used in Service reporting, installed-base maintenance, and integration scenarios. It presents the installed-base record joined to its status definition, its system (configuration) assignment, its original order context, and descriptive item information, so that field service, depot repair, and service contract processes can identify what a customer owns and how it may be serviced. The inclusion of both operational attributes (installation dates, quantities, shipped/delivered flags) and lifecycle controls (cancelled, terminated, status-change-allowed, incident-allowed, service-order-allowed) makes it suitable for both transactional inquiry and eligibility checks.

Underlying Base Objects

The ETRM metadata does not document the base tables explicitly; the view text, however, identifies its source columns by alias. The central table is CS_CP_MAINT, aliased CP, which holds the customer product rows. It is joined to HZ_ACCOUNTS (HZA) and HZ_PARTIES (HZP) for the account number and party name, to CS_CP_STATUSES (CPS) for the status name and lifecycle flags, to CS_SYSTEMS (S) for the system name, to a lookup (L) for the customer product type meaning, to OKS_AGREEMENTS (A1) for the product agreement name, to ITEM_REVISIONS (R) for the revision, and to the key item flexfield (KFV) for serial-number control code, item description, and BOM item type. The original order context comes from OE_ORDER_HEADERS_ALL (OOH) and OE_ORDER_LINES_ALL (OOL) via the original order line ID.

Because the view raises a column for CONFIG_TYPE and several CONFIG_* attributes (CONFIG_ENABLED_FLAG, CONFIG_START_DATE, CONFIG_END_DATE, CONFIG_ROOT_ID, CONFIG_PARENT_ID), it is commonly queried by users searching for cp_config_type. CONFIG_TYPE records the configuration perspective of the customer product instance, and it is paired here with a further lookup (L3) for its meaning.

Key Columns

• CUSTOMER_PRODUCT_ID – the primary key of the installed-base record.
• CUSTOMER_ID, ACCOUNT_NUMBER, PARTY_NAME – the owning customer, account, and party.
• INVENTORY_ITEM_ID, PRODUCT_DESCRIPTION, BOM_ITEM_TYPE – the item and its classification.
• CURRENT_SERIAL_NUMBER, REVISION, SERIAL_NUMBER_CONTROL_CODE – instance-level identification.
• CP_STATUS, CANCELLED_FLAG, TERMINATED_FLAG, INCIDENT_ALLOWED_FLAG, SERVICE_ORDER_ALLOWED_FLAG – lifecycle and service eligibility controls.
• QUANTITY, UNIT_OF_MEASURE_CODE, SHIPPED_FLAG, DELIVERED_FLAG, INSTALLATION_DATE – delivery and installation facts.
• ORDER_NUMBER, LINE_NUMBER, ORDERED_DATE, UNIT_SELLING_PRICE, CUST_PO_NUMBER – originating order and pricing context.
• CONFIG_ENABLED_FLAG, CONFIG_TYPE, CONFIG_ROOT_ID, CONFIG_PARENT_ID – configuration participation of the instance.
• ORG_ID – multi-org operating unit discriminator (implies VPD/security policy enforcement).

Common Use Cases and Queries

Typical uses include installed-base extracts, service-entitlement validation, and configuration analysis. Status-based filtering is common because the CPS flags determine whether a service request may be raised.

SELECT customer_product_id, party_name, account_number,
       product_description, current_serial_number,
       cp_status, installation_date, config_type
FROM   cs_cp_maint_v
WHERE  org_id = :p_org_id
AND    cancelled_flag = 'N'
AND    terminated_flag = 'N';

SELECT config_type, COUNT(*) instances
FROM   cs_cp_maint_v
WHERE  org_id = :p_org_id
AND    config_enabled_flag = 'Y'
GROUP  BY config_type;

Queries joining this view to CS_INCIDENTS or service orders use CUSTOMER_PRODUCT_ID as the link and rely on INCIDENT_ALLOWED_FLAG or SERVICE_ORDER_ALLOWED_FLAG for eligibility. Where multi-org access is configured, ORG_ID is enforced automatically by the security policy.