Results for “csd_ro_summary_v”

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

Overview

CSD_RO_SUMMARY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined against the CSD (Depot Repair) product. It is documented with a status of VALID and is described in ETRM metadata as the "Repair Order Summary View." The object consolidates header-level repair order data with customer, product, item, status, and estimate-approval attributes into a single denormalized row per repair line, allowing Depot Repair users and integrators to query repair activity without joining the underlying transactional tables directly.

The view is read-only and is intended primarily for inquiry, reporting, and downstream integration rather than for transactional processing. Because it joins translated lookup and flow-status tables using the session language, it returns user-facing descriptions rather than raw codes, which makes it suitable for operational dashboards, service-call tracking, and repair depot performance reporting.

Underlying Base Objects

The documented base objects referenced by CSD_RO_SUMMARY_V include CSD_REPAIRS (a synonym to the repair order line table), CSD_INCIDENTS_NON_SEC_V (a view providing incident and customer information), CSD_REPAIR_TYPES_VL, CSD_FLOW_STATUSES_B, CSD_FLOW_STATUSES_TL, CSI_ITEM_INSTANCES, MTL_SYSTEM_ITEMS_VL, MTL_UNITS_OF_MEASURE_VL, and FND_LOOKUPS. Supporting packages referenced include CS_STD, FND_GLOBAL, HR_API, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and CSD_PROCESS_UTIL.

The join structure links each repair line (CSD_REPAIRS) to its incident (CSD_INCIDENTS_NON_SEC_V) via INCIDENT_ID, to the customer product instance (CSI_ITEM_INSTANCES) via CUSTOMER_PRODUCT_ID using an outer join, and to item and UOM definitions through INVENTORY_ITEM_ID and UNIT_OF_MEASURE. Lookups such as CSD_APPROVAL_STATUS, CSD_REPAIR_STATUS, and CSD_REPAIR_FLOW_STATUS are resolved through FND_LOOKUPS, while flow-status codes and translated descriptions are drawn from CSD_FLOW_STATUSES_B and CSD_FLOW_STATUSES_TL. The view filters the item organization through CS_STD.GET_ITEM_VALDN_ORGZN_ID and the flow-status translation through USERENV('LANG').

Key Columns

• REPAIR_NUMBER — the depot repair order identifier from CSD_REPAIRS.
• INCIDENT_NUMBER / INCIDENT_ID — the associated service incident.
• REPAIR_TYPE_NAME — translated repair type from CSD_REPAIR_TYPES_VL.
• SR_STATUS / STATUS_MEANING — incident status and its lookup meaning.
• REFERENCE_NUMBER — instance number of the customer product (CP.INSTANCE_NUMBER).
• ITEM / ITEM_DESC / ITEM_REVISION — concatenated item segments, description, and revision.
• SERIAL_NUMBER — resolved from either the repair line or the customer product via DECODE.
• INSTALL_SITE_USE_ID — the install site use identifier derived from CP.LOCATION_ID, identifying the customer's installed-at location.
• CUSTOMER_ID / CUSTOMER_NAME / CUSTOMER_ACCOUNT / ACCOUNT_DETAIL — customer identification and account concatenation.
• CREATION_DATE / DATE_CLOSED / PROMISE_DATE — key repair lifecycle dates.
• QUANTITY, UOM — repair quantity and unit of measure.
• FLOW_STATUS_CODE / FLOW_STATUS_MEANING — flow status code and its external or looked-up display name.
• ESTIMATE_APPROVED — approval status meaning from FND_LOOKUPS.

Common Use Cases and Queries

Typical uses include open repair order reporting, customer-facing repair tracking by installed site, and integration extracts feeding data warehouses. Because the user searched for install_site_use_id, the following query returns repair orders grouped by installed-at site:

• SELECT repair_number, incident_number, customer_name, install_site_use_id, item, serial_number, flow_status_meaning FROM csd_ro_summary_v WHERE install_site_use_id = :p_site_use_id;
• SELECT customer_account, COUNT(*) FROM csd_ro_summary_v WHERE TRUNC(creation_date) BETWEEN :p_from AND :p_to GROUP BY customer_account;
• SELECT repair_number, promise_date, flow_status_meaning FROM csd_ro_summary_v WHERE flow_status_meaning NOT IN ('Closed','Cancelled') ORDER BY promise_date;

Note that INSTALL_SITE_USE_ID is populated from the customer product instance (CSI_ITEM_INSTANCES.LOCATION_ID) and may be null for repairs without a linked product instance, since that join is outer.