Search Results csd_ro_v




Overview
Explore in AI Chat

Overview

CSD_RO_V is an APPS-owned database view in Oracle E-Business Suite, belonging to the Depot Repair (CSD) product family. It presents a consolidated, read-only projection of depot repair orders, joining repair header and line information from the Depot Repair data model with customer account details from Oracle Receivables. The view is designed primarily for reporting, inquiry, and integration scenarios in which repair order data must be exposed alongside the customer name and account number that own the repaired item.

The view is documented as VALID in ETRM 12.2.2 and is referenced in the 12.1.1 / 12.2.2 documentation set. Because it draws on a repair header view (CSD_REPAIRS_V) rather than on base tables directly, it encapsulates the security and status logic applied by the underlying repair view, including organization and business-group access restrictions enforced through the PA security and cross-business-group packages. This makes CSD_RO_V a convenient, security-aware source for ad hoc queries and custom reports without requiring the consumer to reconstruct the join logic.

Underlying Base Objects

The view text is defined as a join between two objects:

  • CSD_REPAIRS_V (VIEW) — the principal Depot Repair source, supplying repair order and repair line attributes.
  • HZ_CUST_ACCOUNTS (SYNONYM) — the Trading Community Architecture customer account entity, supplying ACCOUNT_NUMBER and ACCOUNT_NAME.

The join predicate is CSD.CUSTOMER_ID = HZ.CUST_ACCOUNT_ID, linking each repair order to its owning customer account. Additional documented dependencies of the view are CS_STD, FND_GLOBAL, FND_PROFILE, PA_CROSS_BUSINESS_GRP, PA_PROJECT_UTILS, PA_SECURITY, and PA_TASK_UTILS. These packages are inherited through CSD_REPAIRS_V and provide the profile-option lookups, multi-org context, and project/business-group security filters that govern which repair records are visible to the querying user. As a result, results returned from CSD_RO_V are subject to the same access controls as the Depot Repair application itself.

Key Columns

  • REPAIR_NUMBER — the user-visible repair order number and the attribute most commonly used for lookup and search.
  • INCIDENT_NUMBER, INCIDENT_ID — the associated service/incident identifier and its surrogate key.
  • REFERENCE_NUMBER — an external or customer-supplied reference for the repair order.
  • INVENTORY_ITEM_ID, ITEM — the inventory item identifier and item name of the repaired product.
  • CUSTOMER_ID, ACCOUNT_NUMBER, ACCOUNT_NAME — the customer account key, number, and descriptive name from HZ_CUST_ACCOUNTS.
  • SERIAL_NUMBER — the serial number of the unit under repair.
  • CREATION_DATE, DATE_CLOSED, PROMISE_DATE — order creation, closure, and committed delivery dates.
  • STATUS — the current repair status.
  • REPAIR_LINE_ID, QUANTITY, UNIT_OF_MEASURE — the repair line key and the quantity/UOM of the item on that line.

Common Use Cases and Queries

Typical uses include open repair order reporting, aging analysis of repair orders against PROMISE_DATE, customer-facing status inquiries, and inbound integration extracts. A representative query retrieving repair orders for a given repair number is:

  • SELECT repair_number, incident_number, item, serial_number, status, promise_date, date_closed, account_number, account_name FROM csd_ro_v WHERE repair_number = :p_repair_number;

For open-order analysis by customer, a query such as SELECT account_name, repair_number, item, serial_number, promise_date FROM csd_ro_v WHERE status NOT IN ('CLOSED','CANCELLED') ORDER BY promise_date; is commonly used. Because access is governed by profile and security packages, reports executed under a given responsibility automatically return only the repair orders that responsibility is permitted to see.