Search Results csd_ro_service_codes_u1

Overview

CSD.CSD_RO_SERVICE_CODES is a transaction table in the Oracle E-Business Suite Depot Repair (CSD) schema. It stores the mapping between Repair Orders and Service Codes, capturing which service codes apply to a given repair line and how those codes are applied through the estimation and work execution phases. The object resides in the APPS_TS_TX_DATA tablespace and is owned by the CSD schema, with FND design data registered as CSD.CSD_RO_SERVICE_CODES.

From a Data Vault modeling perspective, the metadata heuristic classifies this table as standalone. In practice it behaves as a link or intersection entity associating repair lines with service codes, carrying descriptive flags and a descriptive flexfield. Because the heuristic identifies no incoming hubs according to the FK structure, it is best treated as an associative/link-style object rather than a pure satellite, though its standard Who columns and version number give it satellite-like change-tracking characteristics.

Key Information Stored

The table contains 32 documented columns. The most significant are:

• RO_SERVICE_CODE_ID — surrogate primary key (NUMBER), enforced by the unique index CSD_RO_SERVICE_CODES_U1 and the primary key constraint CSD_RO_SERVICE_CODES_PK1.
• REPAIR_LINE_ID — repair line identifier; foreign key to CSD_REPAIRS, linking the service code to a specific repair line.
• SERVICE_CODE_ID — foreign key to CSD_SERVICE_CODES_B, identifying the applied service code.
• SERVICE_ITEM_ID — references the specific service item within the service code definition.
• SOURCE_TYPE_CODE and SOURCE_SOLUTION_ID — indicate how the service code was sourced and any originating solution.
• APPLICABLE_FLAG — indicates whether the service code applies to the line.
• APPLIED_TO_EST_FLAG and APPLIED_TO_WORK_FLAG — record whether the code has been applied to the estimate and to work execution respectively.
• REC_TYPE_CODE — record type classification for the mapping row.
• OBJECT_VERSION_NUMBER — optimistic locking and standard versioning column.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield structure and segment columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns.

The only documented business-key candidate is RO_SERVICE_CODE_ID via index CSD_RO_SERVICE_CODES_U1. The non-unique index CSD_RO_SERVICE_CODES_N1 covers REPAIR_LINE_ID and SERVICE_CODE_ID, supporting line-driven lookups.

Common Use Cases and Queries

This table is queried to report which service codes have been attached to repair lines, to determine estimate versus work application status, and to trace service code sourcing. A typical query joins the table to CSD_REPAIRS on REPAIR_LINE_ID and to CSD_SERVICE_CODES_B on SERVICE_CODE_ID:

• List all service codes for a repair line: SELECT sc.SERVICE_CODE, rs.APPLICABLE_FLAG, rs.APPLIED_TO_EST_FLAG, rs.APPLIED_TO_WORK_FLAG FROM CSD_RO_SERVICE_CODES rs, CSD_SERVICE_CODES_B sc WHERE rs.SERVICE_CODE_ID = sc.SERVICE_CODE_ID AND rs.REPAIR_LINE_ID = :repair_line_id;
• Identify codes applied to work but not to estimation, using APPLIED_TO_WORK_FLAG and APPLIED_TO_EST_FLAG.
• Trace downstream usage by joining CSD_REPAIR_ESTIMATE_LINES and CSD_REPAIR_JOB_XREF on RO_SERVICE_CODE_ID.
• Filter by SOURCE_TYPE_CODE to analyze how service codes were introduced to the order.

The N1 index makes REPAIR_LINE_ID/SERVICE_CODE_ID lookups efficient, while the U1 index optimizes single-row fetches by primary key.

Related Objects

The following objects depend on or are referenced by CSD_RO_SERVICE_CODES:

• CSD_REPAIRS — referenced via REPAIR_LINE_ID; the parent repair line.
• CSD_SERVICE_CODES_B — referenced via SERVICE_CODE_ID; the base service code definition.
• CSD_REPAIR_JOB_XREF — references this table via RO_SERVICE_CODE_ID, linking service codes to repair jobs.
• CSD_REPAIR_ESTIMATE_LINES — references this table via RO_SERVICE_CODE_ID, tying service codes to estimate lines.
• FND_USER — referenced by CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — referenced by LAST_UPDATE_LOGIN.

These relationships confirm the table's role as the central link between repair lines, service code definitions, estimates, and jobs within Depot Repair processing.