Search Results csd_ro_bulletins_u2




Overview

CSD.CSD_RO_BULLETINS is a transactional table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 depot repair and field service module. The table is owned by the CSD schema and resides in the APPS_TS_TX_DATA tablespace. Its documented role is to link a Service Order (specifically a repair line) to one or more Service Bulletins, allowing field service and depot repair personnel to associate published bulletins — engineered-change notices, safety advisories, or repair instructions — with the repair work being performed.

The FND Design Data reference (CSD.CSD_RO_BULLETINS) indicates that the object is registered in the Applications Object Library and is therefore exposed through the standard EBS dictionary views and the Application Programming Interface layer. Its status is VALID, meaning the object is present and recognized by the EBS runtime. Based on the foreign key structure, the ETRM metadata heuristically classifies this object as a link table in a Data Vault-style model: it captures the association between two business entities (a repair line and a bulletin) and carries no independent descriptive payload of its own. The physical implementation is a conventional relational junction table rather than a Data Vault hub or satellite, so the classification should be treated as a modeling suggestion rather than a strict structural description.

Key Information Stored

The table contains 13 documented columns. The most important are:

The unique index CSD_RO_BULLETINS_U2, defined on (BULLETIN_ID, REPAIR_LINE_ID), represents the business-key candidate: it prevents the same bulletin from being attached twice to the same repair line, while still permitting a repair line to reference many bulletins and a bulletin to apply to many repair lines. This many-to-many resolution is the defining characteristic of the table.

Common Use Cases and Queries

The table is typically queried when building depot repair or field service reports that need to show which bulletins apply to a given repair order, or conversely, which repair orders reference a given bulletin. A typical join retrieves the bulletin detail for a repair line:

  • Join to CSD_BULLETINS_B on BULLETIN_ID to obtain bulletin title, number, and status.
  • Join to CSD_REPAIRS on REPAIR_LINE_ID to obtain repair order context.
  • Filter on LAST_VIEWED_DATE to find bulletins that have not yet been acknowledged by technicians.
  • Aggregate by BULLETIN_ID to measure how often a bulletin is applied across the service network.
  • Use SOURCE_TYPE and SOURCE_ID to reconcile system-generated link records against manually created ones.

A representative query joining the two parent tables follows the pattern: select the repair line, bulletin number, and last-viewed information, then restrict by repair order or bulletin status. Because the table is a link object, most reporting queries are two-hop joins and benefit from the CSD_RO_BULLETINS_U2 index when filtering on BULLETIN_ID or REPAIR_LINE_ID.

Related Objects

  • CSD.CSD_REPAIRS — Parent of REPAIR_LINE_ID; supplies the repair order and repair line context.
  • CSD.CSD_BULLETINS_B — Parent of BULLETIN_ID; base table holding bulletin definitions.
  • CSD.CSD_RO_BULLETINS# — The underlying base table referenced by the object; typically accessed through the synonym or the registered view.
  • CSD_BULLETINS_TL — Translation table for bulletin descriptive text, joined via BULLETIN_ID for multilingual reporting.
  • CSD_REPAIRS_INTERFACE and related depot repair APIs
  • — Consume or populate these link records during repair order creation and update.
  • FND standard WHO columns — Resolved to FND_USER via CREATED_BY, LAST_UPDATED_BY, and LAST_VIEWED_BY for audit reporting.

The relationship metadata confirms that CSD_RO_BULLETINS does not reference any object other than its two parents, and it is referenced only by its own base table derivative. Consequently, all meaningful integration and reporting flows pass through CSD_REPAIRS and CSD_BULLETINS_B.