Results for “instance_id”

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

Overview

The CSD_MASS_RO_SN_V view is a reporting and integration object within the Oracle E-Business Suite (EBS) CSD – Depot Repair module. It is owned by the APPS schema and holds a VALID status in both EBS 12.1.1 and 12.2.2. The view exposes a denormalized, read-only projection of mass repair order serial number data, joining the mass repair order serial number table to the corresponding repair order and item instance records. Its purpose is to allow reporting tools, concurrent programs, and external integrations to resolve a mass repair order line to a specific serialized item instance and its parent repair order without needing to author multi-table joins at the application layer.

Because it is a view rather than a base table, no DML (insert, update, delete) should be issued against CSD_MASS_RO_SN_V; write operations must be directed to the underlying transactional tables. The view is defined with an outer join on the item instance table, so repair records that are not yet associated with a serialized instance remain visible.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over three referenced base objects, each accessed via a synonym in the APPS schema:

• CSD_MASS_RO_SN (SYNONYM) — the driving table storing the mass repair order serial number records (alias A in the view text).
• CSD_REPAIRS (SYNONYM) — the repair order header/line table supplying the human-readable repair number (alias C).
• CSI_ITEM_INSTANCES (SYNONYM) — the installed base / item instance table supplying the instance number (alias B).

The documented view text is:

SELECT A.MASS_RO_SN_ID, A.SERIAL_NUMBER, A.REPAIR_LINE_ID, C.REPAIR_NUMBER, A.INSTANCE_ID, B.INSTANCE_NUMBER, A.OBJECT_VERSION_NUMBER FROM CSD_MASS_RO_SN A, CSI_ITEM_INSTANCES B, CSD_REPAIRS C WHERE A.INSTANCE_ID = B.INSTANCE_ID (+) AND A.REPAIR_LINE_ID = C.REPAIR_LINE_ID

Note the outer join (+) applied to the CSI_ITEM_INSTANCES join, permitting mass repair order serial numbers with no matching item instance to be returned with a null instance number.

Key Columns

The view exposes seven columns, detailed as follows:

• MASS_RO_SN_ID — primary key value of the underlying mass repair order serial number record in CSD_MASS_RO_SN.
• SERIAL_NUMBER — the serial number captured on the mass repair order serial number record.
• REPAIR_LINE_ID — foreign key linking the record to the corresponding repair line; used to join to the CSD_REPAIRS table.
• REPAIR_NUMBER — the user-facing repair order number sourced from CSD_REPAIRS.
• INSTANCE_ID — foreign key identifying the associated item instance record in the installed base.
• INSTANCE_NUMBER — the user-facing instance number from CSI_ITEM_INSTANCES; null when no matching instance exists due to the outer join.
• OBJECT_VERSION_NUMBER — the standard Oracle EBS optimistic locking / concurrency control column, sourced from CSD_MASS_RO_SN.

Common Use Cases and Queries

This view is typically used in Depot Repair reporting to reconcile mass repair order serial numbers against repair orders and installed base instances. Representative scenarios include generating serial number traceability reports, validating mass repair order lines that lack an associated item instance, and feeding downstream integrations.

Sample query listing all serial numbers for a given repair number:

SELECT mass_ro_sn_id, serial_number, repair_number, instance_number
FROM apps.csd_mass_ro_sn_v
WHERE repair_number = :p_repair_number;

Sample query identifying mass repair order serial numbers with no matched item instance:

SELECT mass_ro_sn_id, serial_number, repair_line_id, instance_id
FROM apps.csd_mass_ro_sn_v
WHERE instance_number IS NULL;

Sample query joining the view to additional installed base attributes via the instance identifier:

SELECT v.serial_number, v.repair_number, i.instance_number, i.serial_number ib_serial
FROM apps.csd_mass_ro_sn_v v, apps.csi_item_instances i
WHERE v.instance_id = i.instance_id;

Because the view is read-only and carries OBJECT_VERSION_NUMBER, it should be treated strictly as a query surface; all maintenance of mass repair order serial number records must be performed against CSD_MASS_RO_SN through the supported Depot Repair forms or APIs.