Search Results ro_bulletin_pk

Overview

CSD_RO_BULLETINS is a transactional table in the CSD (Depot Repair) module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores the association between service bulletins defined in the depot repair catalog and the specific repair lines to which those bulletins apply. In practice, this table records which bulletins have been raised against a repair order line, together with viewing and source-tracking metadata. It operates within the CSD schema and holds a status of VALID in the documented environment.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as a link. The table primarily resolves a many-to-many association between repair lines (CSD_REPAIRS) and bulletin definitions (CSD_BULLETINS_B), with the remaining columns behaving as descriptive attributes on that relationship. This classification is a heuristic suggestion derived from the FK topology rather than a prescriptive design mandate.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are:

• RO_BULLETIN_ID — the surrogate primary key, enforced by the RO_BULLETIN_PK constraint and indexed uniquely via CSD_RO_BULLETINS_U1.
• BULLETIN_ID — the foreign key to CSD_BULLETINS_B, identifying the bulletin definition being applied.
• REPAIR_LINE_ID — the foreign key to CSD_REPAIRS, identifying the depot repair line the bulletin is associated with.
• LAST_VIEWED_DATE and LAST_VIEWED_BY — capture when and by whom the bulletin association was last accessed, supporting acknowledgement and audit tracking.
• SOURCE_TYPE and SOURCE_ID — polymorphic reference fields recording the originating document or system entity that generated the association.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the EBS framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns present on nearly all transactional EBS tables.

The unique index CSD_RO_BULLETINS_U2 on (BULLETIN_ID, REPAIR_LINE_ID) is the effective business-key candidate, preventing duplicate bulletin application to the same repair line.

Common Use Cases and Queries

Typical reporting scenarios include determining which bulletins apply to a given repair order, tracking bulletin acknowledgement, and auditing bulletin usage across repair lines.

• List bulletins for a specific repair line:
  SELECT rb.ro_bulletin_id, rb.bulletin_id, rb.last_viewed_date
FROM csd_ro_bulletins rb
WHERE rb.repair_line_id = :p_repair_line_id;
• Join to bulletin master data for descriptions:
  SELECT rb.repair_line_id, bb.bulletin_name
FROM csd_ro_bulletins rb, csd_bulletins_b bb
WHERE rb.bulletin_id = bb.bulletin_id;
• Track unviewed bulletins (LAST_VIEWED_DATE IS NULL) to identify repairs where service personnel have not acknowledged applicable bulletins.
• Audit recent activity using CREATION_DATE and LAST_UPDATED_BY for compliance or productivity reporting.

Related Objects

• CSD_REPAIRS — referenced via CSD_RO_BULLETINS.REPAIR_LINE_ID; the parent depot repair line table.
• CSD_BULLETINS_B — referenced via CSD_RO_BULLETINS.BULLETIN_ID; the bulletin definition base table.

These two FK relationships represent the primary dependencies documented in the ETRM metadata. Additional dependent views and concurrent programs in the Depot Repair module may consume this table indirectly through CSD_REPAIRS joins.