Search Results install_to_county

Overview

CS_CUST_PROD_FORM_V is a Service (CS) module view that consolidates customer product information — the installed base records that represent products a customer owns or has received — into a single denormalized result set. In Oracle EBS 12.1.1 and 12.2.2, the view joins the core customer products table (CS_CUSTOMER_PRODUCTS) to associated status, system, item, agreement, order-line, and party reference data, producing the flattened structure consumed by Service/Field Service forms and by the Customer Product (ISUR — Install, Setup, Update, Repair) flows surfaced through the Service Portal.

The user search term "Service Portal - ISUR Home" reflects a common entry point: the ISUR home dashboard exposes installed-base items to service agents and technicians, and the underlying query feeding that page relies on a view such as CS_CUST_PROD_FORM_V to return customer product rows with account, party, status, order, and serial-number context in one pass. This makes the view important for both online form rendering and downstream reporting/integration.

Underlying Base Objects

The view text SELECTs from several base objects through aliases:

• CP — CS_CUSTOMER_PRODUCTS, the primary driving table holding customer product instances.
• HZA — HZ_CUST_ACCOUNTS, providing ACCOUNT_NUMBER.
• HZP — HZ_PARTIES, providing PRINCIPAL_PARTY_NAME.
• OOH / OOL — OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, supplying the original order date, number, line number, link-to-line, unit selling price, price list, and customer PO number.
• CPS — CS_CUST_PRODUCT_STATUSES, supplying the status name and status behavior flags.
• S — likely CS_SYSTEMS (SYSTEM name).
• L (lookup) — FND_LOOKUPS / MFG_LOOKUPS for CP_TYPE meaning.
• A1 — a product agreement table supplying PRODUCT_AGREEMENT.
• R, SI — revision/serial control and item master (MTL_SYSTEM_ITEMS_B) providing description, serial-number control code, and BOM item type.

Note the ETRM metadata marks this view as "Not implemented in this database" for the queried instance and documents no referenced base objects, so column-level lineage above is derived from the view text rather than a catalog dependency.

Key Columns

• CUSTOMER_PRODUCT_ID — primary key of the customer product instance.
• ACCOUNT_NUMBER, PRINCIPAL_PARTY_NAME — customer account and party context.
• INVENTORY_ITEM_ID, PRODUCT_DESCRIPTION, BOM_ITEM_TYPE, SERIAL_NUMBER_CONTROL_CODE — identification of the product and its item attributes.
• CP_STATUS, CANCELLED_FLAG, TERMINATED_FLAG, STATUS_CHANGE_ALLOWED_FLAG, INCIDENT_ALLOWED_FLAG, SERVICE_ORDER_ALLOWED_FLAG — status and the behavioral permissions governing allowed service actions.
• CURRENT_SERIAL_NUMBER, REVISION, LOT_NUMBER, QUANTITY, UNIT_OF_MEASURE_CODE — instance specifics.
• ORIGINAL_ORDER_DATE/NUMBER/LINE_NUMBER, ORIGINAL_NET_AMOUNT, PURCHASE_ORDER_NUM, PRICE_LIST_ID — originating order detail.
• SHIP_TO_SITE_USE_ID, BILL_TO_SITE_USE_ID, INSTALL_SITE_USE_ID — address/site references.
• START_DATE_ACTIVE, END_DATE_ACTIVE, INSTALLATION_DATE, SHIPPED_DATE, RETURN_BY_DATE, ACTUAL_RETURNED_DATE — lifecycle dates.
• CONFIG_* columns (CONFIG_ENABLED_FLAG, CONFIG_ROOT_ID, CONFIG_PARENT_ID, CONFIG_TYPE) — configuration/assembly hierarchy.
• ATTRIBUTE1–15, CONTEXT, ORG_ID — flexfield and multi-org context.

Common Use Cases and Queries

Typical uses include populating the ISUR home list for a Service Portal user, validating whether a product may accept an incident or service order, and reporting installed base by customer, item, or status.

SELECT ACCOUNT_NUMBER,
       PRINCIPAL_PARTY_NAME,
       PRODUCT_DESCRIPTION,
       CURRENT_SERIAL_NUMBER,
       CP_STATUS,
       INSTALLATION_DATE
FROM   CS_CUST_PROD_FORM_V
WHERE  ACCOUNT_NUMBER = :p_account
  AND  MOST_RECENT_FLAG = 'Y'
  AND  ORG_ID = :p_org_id;

A second common pattern restricts to products eligible for service activity:

SELECT CUSTOMER_PRODUCT_ID, PRODUCT_DESCRIPTION, CP_STATUS
FROM   CS_CUST_PROD_FORM_V
WHERE  SERVICE_ORDER_ALLOWED_FLAG = 'Y'
  AND  TERMINATED_FLAG = 'N';

Because the metadata does not confirm deployment in the queried environment, consumers should verify the view's presence in their specific 12.1.1 or 12.2.2 instance before relying on it for customization.