Search Results rework_code

Overview

CSD_REPAIRS_NON_SEC_V is an APPS-owned database view in the Oracle E-Business Suite Depot Repair (CSD) module. As its name indicates, the view presents depot repair order data without applying Service Security. Its documented purpose is "the view for getting repair orders. It is without Service Security." This distinguishes it from security-enabled repair views that filter rows based on the operating unit, service organization, or user responsibility context using FND_PROFILE and PA_SECURITY logic.

Because the view omits Service Security predicates, it returns repair order lines across organizations and customers visible to the querying session at the database level, rather than restricting them by the Service Security profile. It therefore serves reporting, data extraction, and integration scenarios where a trusted or administrative session must access the complete repair population, or where security filtering is applied downstream by the consuming application. In Oracle EBS 12.1.1 and 12.2.2, the view remains a read-only construct owned by APPS and is commonly referenced by concurrent programs, custom reports, and interface extracts.

Underlying Base Objects

The view is defined over a substantial set of base objects. The documented referenced objects in the ETRM 12.2.2 metadata include:

• CSD_REPAIRS (SYNONYM) — the primary repair line table (aliased DRA in the view text), supplying repair numbers, quantities, statuses, dates, and descriptive flexfield attributes.
• CS_INCIDENTS_ALL_B (SYNONYM) — the service request/incident header, providing ORG_ID, INCIDENT_NUMBER, and CUSTOMER_ID through the SR alias.
• CSI_ITEM_INSTANCES (SYNONYM) and CSI_INSTANCE_STATUSES (SYNONYM) — customer product instances, instance numbers, serial numbers, revisions, lot numbers, and system/location references.
• CSD_REPAIR_TYPES_VL (VIEW) — repair type name, reference, and internal order flag (DRTVL).
• MTL_SYSTEM_ITEMS_VL (VIEW) and MTL_UNITS_OF_MEASURE_VL (VIEW) — inventory item concatenated segments, description, and unit of measure descriptions.
• OKC_K_HEADERS_B and OKC_K_LINES_B (SYNONYMS) — contract header and line information (contract number, contract line ID).
• PJM_PROJECTS_V, PJM_TASKS_V (VIEWS), and the PA packages (PA_PROJECT_UTILS, PA_TASK_UTILS, PA_SECURITY, PA_CROSS_BUSINESS_GRP) — project and task number resolution and project security.
• FND_LOOKUPS (VIEW), FND_GLOBAL, FND_PROFILE, and CS_STD (PACKAGE) — lookup meanings for status, approval status, and status reason, plus session context and standard utility routines.
• QP_LIST_HEADERS_TL (SYNONYM) — price list header name.

The view text joins these objects using DECODE and NVL constructs to reconcile data between the customer product instance and the repair line where no instance exists.

Key Columns

Notable columns exposed by CSD_REPAIRS_NON_SEC_V include:

• REPAIR_LINE_ID, REPAIR_NUMBER — primary key and human-readable repair order identifier.
• ORG_ID, INCIDENT_ID, INCIDENT_NUMBER, CUSTOMER_ID — operating unit and originating service request context.
• INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, ITEM_DESC, UNIT_OF_MEASURE — repaired item identity.
• QUANTITY, QUANTITY_IN_WIP, QUANTITY_RCVD, QUANTITY_SHIPPED — repair quantities, defaulted to zero via NVL.
• PROJECT_ID, PROJECT_NUMBER, TASK_ID, TASK_NUMBER — project and task attribution.
• UNIT_NUMBER, CUSTOMER_PRODUCT_ID, INSTANCE_NUMBER, SERIAL_NUMBER, LOT_NUMBER, SYSTEM_ID, LOCATION_ID — customer product instance detail, with DECODE fallback to repair line revision and serial number.
• REPAIR_TYPE_ID, NAME, REPAIR_TYPE_REF, INTERNAL_ORDER_FLAG, BUSINESS_PROCESS_ID — repair type classification.
• STATUS, STATUS_REASON_CODE, APPROVAL_STATUS, APPROVAL_REQUIRED_FLAG — workflow state, resolved through FND_LOOKUPS meanings.
• DATE_CLOSED, PROMISE_DATE, CURRENCY_CODE, PRICE_LIST_HEADER_ID, ATTRIBUTE1 through ATTRIBUTE15 — dates, financial context, and descriptive flexfields.

Note that the view metadata does not list a REWORK_CODE column; users searching for rework_code should verify whether it is exposed through a descriptive flexfield attribute (for example ATTRIBUTE columns) or an alternate repair view.

Common Use Cases and Queries

Typical usage includes open repair order reporting, aging analysis, and interface extraction. A representative query follows:

• Extract open repairs with customer and item detail:
  SELECT REPAIR_NUMBER, INCIDENT_NUMBER, CUSTOMER_ID, CONCATENATED_SEGMENTS, SERIAL_NUMBER, STATUS, PROMISE_DATE FROM CSD_REPAIRS_NON_SEC_V WHERE STATUS NOT IN ('CLOSED','CANCELLED');
• Repair volume by repair type:
  SELECT NAME, COUNT(*) FROM CSD_REPAIRS_NON_SEC_V GROUP BY NAME;
• Quantity reconciliation of received versus shipped units:
  SELECT REPAIR_NUMBER, QUANTITY, QUANTITY_RCVD, QUANTITY_SHIPPED FROM CSD_REPAIRS_NON_SEC_V WHERE QUANTITY_RCVD <> QUANTITY_SHIPPED;

Because Service Security is not enforced, consumers must apply their own organizational or responsibility filtering when the query is exposed to non-administrative users.