Results for “cp_status”

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

Overview

CS_SR_NEW_PRODUCTS_MAINT_V is an APPS-owned database view within the Oracle E-Business Suite Service (CS) module. It consolidates product and installed base information drawn from InstallBase releases 11.5.6 and higher, exposing a flattened, report-ready result set that Service Request functionality relies upon to resolve all products associated with a given customer account. Rather than requiring callers to join the customer, order, item, and instance schemas independently, the view presents a single denormalized source that maps owned items to their owning party, original sales order context, current service status, and location.

Its primary integration role is within the Service Request (SR) flow: when an agent or an external application opens an SR against an account, the view supplies the candidate product list from which the appropriate instance is selected. Because it joins across the Order Management, InstallBase (CSI), and Receivables/Trading Community (HZ) models, it is a convenient reporting surface for installed base analytics, entitlement lookups, and account-level product inventories.

Underlying Base Objects

The view is defined over the following documented objects:

• CSI_ITEM_INSTANCES (synonym) — the driving table, supplying instance identity, ownership, serial number, quantity, revision, lot, and status identifiers.
• CSI_SYSTEMS_TL (synonym) — provides the translated system name via OUTER join.
• CSI_INSTANCE_STATUSES (synonym) — supplies the instance status name, restricted to statuses where INCIDENT_ALLOWED_FLAG = 'Y'.
• MTL_SYSTEM_ITEMS (synonym) — source of the product description; joined on inventory item and constrained to the validation organization returned by CS_STD.GET_ITEM_VALDN_ORGZN_ID.
• ASO_I_OE_ORDER_HEADERS_V and ASO_I_OE_ORDER_LINES_V (views) — joined outer to the last order line, yielding original order number, ordered date, line number, shipment date, and the customer PO number.
• HZ_CUST_ACCOUNTS and HZ_PARTIES (synonyms) — resolve the owning party account number and party name.
• CS_LOOKUPS (view) — decodes the CP_SERVICE_STATUS lookup to produce the serviced status flag.
• CS_STD and FND_GLOBAL (packages) — supply the serviced-status function, item validation organization, and session language context.

Key Columns

• INSTANCE_ID, INSTANCE_NUMBER, SERIAL_NUMBER — unique identification of the installed item.
• INVENTORY_ITEM_ID, PRODUCT_DESCRIPTION — the product and its description.
• PURCHASE_ORDER_NUMBER — sourced from ASO_I_OE_ORDER_HEADERS_V.CUST_PO_NUMBER; the customer's PO reference from the original order.
• ORIGINAL_ORDER_NUMBER, ORIGINAL_ORDER_DATE, ORIGINAL_LINE_NUMBER, ACTUAL_SHIPMENT_DATE — original sales order context.
• PARTY_ACCOUNT_ID, ACCOUNT_NUMBER, PRINCIPAL_PARTY_NAME — owning party and account identity.
• SERVICED_STATUS_FLAG, CP_STATUS, INSTANCE_TYPE_CODE — service and status indicators.
• SYSTEM, SYSTEM_ID, LOCATION_ID, QUANTITY, EXTERNAL_REFERENCE — placement and supplementary attributes.

Common Use Cases and Queries

Typical usage includes listing an account's serviceable products, locating an instance by serial number, or reconciling installed base against original order data — including the customer purchase order reference.

SELECT instance_number,
       serial_number,
       product_description,
       original_order_number,
       purchase_order_number,
       serviced_status_flag
FROM   apps.cs_sr_new_products_maint_v
WHERE  account_number = :p_account_number
AND    serviced_status_flag = 'Y';

To trace a product by its customer PO number, the PURCHASE_ORDER_NUMBER column supports direct filtering:

SELECT account_number,
       serial_number,
       original_order_number,
       original_order_date
FROM   apps.cs_sr_new_products_maint_v
WHERE  purchase_order_number = :p_po_number;

Because the view already applies serviced-status and incident-allowed filtering, ad hoc queries return only products eligible for Service Request activity, reducing the need to replicate these business rules in custom SQL.