Results for “cs_sr_new_acc_cp_rg_v”

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

Overview

CS_SR_NEW_ACC_CP_RG_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Service (CS) product family. Its documented purpose is to support the main Service Request form, specifically as the source for a record group that retrieves install base information for Release 11.5.6 and higher. In practical terms, the view functions as a denormalized, presentation-oriented projection of Oracle Install Base data, joining item instance records to their statuses, systems, item definitions, and associated order context so that the Service Request user interface can present customer product information without issuing multiple direct lookups against the base tables.

Because it is a view over documented base objects and is registered as VALID in ETRM 12.2.2, it is commonly encountered when administrators and developers inspect the Service Request form's record group definitions or extend the form with custom fields. The internal naming convention—CS_SR for Service Request, NEW for the forward-compatible release-aware implementation, and ACC_CP_RG_V for account/customer product record group—reflects this targeted UI role.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms except where noted:

• CSI_ITEM_INSTANCES — the primary driving table, supplying each installed instance (ITEM alias), its serial number, lot number, revision, instance number, owner party, location, and lifecycle dates.
• CSI_INSTANCE_STATUSES — supplies the status name that surfaces as CUSTOMER_PRODUCT_STATUS, along with INCIDENT_ALLOWED_FLAG used as a filter.
• CSI_SYSTEMS_TL and CSI_SYSTEMS_B — provide the translated and base system records, joined on SYSTEM_ID with an outer join to the user's session language.
• MTL_SYSTEM_ITEMS_VL — a view supplying the product name (concatenated segments), description, item type, and organization.
• OE_ORDER_LINES_ALL and OE_ORDER_HEADERS_ALL — outer-joined through the instance's last order line to expose order number and customer PO number.
• CSI_II_RELATIONSHIPS — outer-joined on COMPONENT-OF relationships to identify parent/component hierarchy context and object identifiers.

Standard outer-join syntax (+) and active-date windowing are applied, restricting rows to instances and relationships current as of SYSDATE.

Key Columns

The projection includes several columns of particular interest to reporting and integration:

• INSTANCE_ID, INSTANCE_NUMBER, SERIAL_NUMBER, LOT_NUMBER, INVENTORY_REVISION — identify the specific installed item.
• CUSTOMER_PRODUCT_STATUS — the status name from CSI_INSTANCE_STATUSES; this is the column most closely associated with the search term "customer_product_status" and reflects whether the instance is active, terminated, or otherwise classified.
• INCIDENT_ALLOWED_FLAG — indicates whether a service request may be raised against the instance; the view filters to 'Y'.
• PRODUCT_NAME, PRODUCT_DESCRIPTION, PRODUCT_TYPE, ORGANIZATION_ID, INVENTORY_ITEM_ID — describe the product from MTL_SYSTEM_ITEMS_VL.
• SYSTEM_ID, SYSTEM_NAME — the owning install base system.
• PARTY_ACCOUNT_ID, OWNER_PARTY_ID, LOCATION_ID — customer and location identification; owner sourcing is restricted to HZ_PARTIES.
• ORDER_NUMBER, CUST_PO_NUMBER — commercial context from the last order line.
• OBJECT_ID — relationship object identifier from CSI_II_RELATIONSHIPS.

Columns such as PLATFORM, VERSION, and MAINT_ORGANIZATION_ID are deliberately projected as NULL, preserving a legacy output signature for the record group.

Common Use Cases and Queries

The canonical query filters by customer and product status when populating a Service Request:

SELECT instance_id,
       product_name,
       serial_number,
       customer_product_status
  FROM apps.cs_sr_new_acc_cp_rg_v
 WHERE party_account_id = :account_id
   AND customer_product_status = :status;

Because the view already restricts on INCIDENT_ALLOWED_FLAG and active dates, it is used directly in LOV record groups, reports joining installed base to service requests, and integration extracts requiring a serviceable-instance feed. Note that the record group usage and language-dependent joins mean results are sensitive to session language and SYSDATE.