Search Results problem_description

Overview

CSD_REPAIRS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the CSD (Depot Repair) product family. As its ETRM description states, the view is used "for getting repair orders," and it serves as the primary consolidated reporting interface for Depot Repair order headers and their most frequently referenced descriptive attributes. Because the view joins the transactional repair line table (CSD_REPAIRS) to a wide set of lookup, reference, and master-data objects, consumers can retrieve a fully denormalized picture of a repair order without reconstructing the dozens of foreign-key relationships themselves.

The view is present and VALID in both the 12.1.1 and 12.2.2 releases. Its role is primarily reporting, inquiry, and integration: it is commonly queried by custom concurrent programs, OBIEE/BI Publisher reports, and external integration layers that need repair order status, customer, item, contract, and project context in a single result set. It is not intended as a DML target; updates to repair orders must be performed against the base CSD_REPAIRS table or through the Depot Repair application APIs.

Underlying Base Objects

The view text performs an outer-driven SELECT based on CSD_REPAIRS (aliased DRA), the core Depot Repair line/order table, joined with SR (CS_INCIDENTS_B_SEC / service request data) for incident and customer context. The documented referenced base objects include:

• CSD_REPAIRS — the primary transactional source for repair line attributes.
• CSD_REPAIR_TYPES_VL, CSD_FLOW_STATUSES_B/TL — repair type names and flow-status configuration.
• CSI_ITEM_INSTANCES, CSI_INSTANCE_STATUSES — installed base instance, revision, serial, and lot data.
• MTL_SYSTEM_ITEMS_VL, MTL_UNITS_OF_MEASURE_VL — item concatenated segments, description, and UOM details.
• OKC_K_HEADERS_B, OKC_K_LINES_B — service contract header and line context.
• PJM_PROJECTS_V, PJM_TASKS_V and the PA_* packages (PA_PROJECT_UTILS, PA_TASK_UTILS, PA_SECURITY, PA_CROSS_BUSINESS_GRP) — project and task numbering subject to project security.
• QP_LIST_HEADERS_TL — price list name for the repair order.
• FND_LOOKUPS, FND_PROFILE, FND_GLOBAL, CS_STD — lookup meanings (approval status, repair status, status reason), profile values, and multi-org/security context.

Key Columns

• REPAIR_LINE_ID, REPAIR_NUMBER — primary identifier and human-readable repair order/line number.
• ORG_ID — operating unit, critical for multi-org security and reporting filters.
• INCIDENT_ID, INCIDENT_NUMBER, CUSTOMER_ID — originating service request and customer linkage.
• INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, ITEM_DESC, UNIT_OF_MEASURE — repaired item and UOM.
• QUANTITY, QUANTITY_IN_WIP, QUANTITY_RCVD, QUANTITY_SHIPPED — quantity tracking across the repair lifecycle (WIP/received/shipped are NVL-defaulted to 0).
• CUSTOMER_PRODUCT_ID, INSTANCE_NUMBER, SERIAL_NUMBER, LOT_NUMBER — installed base instance identity.
• APPROVAL_STATUS, STATUS, STATUS_REASON_CODE — decoded via FND_LOOKUPS to MEANING/DESCRIPTION.
• REPAIR_TYPE_ID and related repair-type attributes — including INTERNAL_ORDER_FLAG and BUSINESS_PROCESS_ID.
• PROJECT_ID, TASK_ID, CONTRACT_LINE_ID — project/task/contract associations, with corresponding numbers exposed.
• DATES — CREATION_DATE, PROMISE_DATE, DATE_CLOSED, and audit columns.
• ATTRIBUTE1–15 and FLOW_STATUS_ID — descriptive flexfield and flow-status integration.

Common Use Cases and Queries

A typical query retrieves open repair orders for an operating unit with customer and item detail:

• SELECT repair_number, incident_number, customer_id, concatenated_segments, quantity, status FROM csd_repairs_v WHERE org_id = :p_org_id AND date_closed IS NULL;
• Tracking WIP versus shipped quantities: SELECT repair_number, quantity, quantity_in_wip, quantity_shipped FROM csd_repairs_v WHERE quantity_shipped < quantity;
• Joining to installed base context for serialized items: SELECT repair_number, instance_number, serial_number, lot_number FROM csd_repairs_v WHERE customer_product_id IS NOT NULL;

Because the view applies project security through the PA_* packages, results are automatically filtered by the user's project security profile. Reporting queries should always qualify by ORG_ID, and performance-sensitive extracts should filter on REPAIR_NUMBER or CREATION_DATE rather than scanning full attribute sets.