Results for “csd_bulletins_v”

26 results




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

Overview

CSD_BULLETINS_V is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the CSD product family (Depot Repair) and is documented with the description "View to fetch all Service Bulletins." Service bulletins are the mechanism by which depot repair organizations publish notifications, mandatory repair instructions, and escalation-driven notices to service agents, field personnel, and customers. This view consolidates the multilingual bulletin definition, its lookup-based classifications, and its associated Oracle Workflow process into a single denormalized projection suitable for concurrent programs, OAF/Forms LOVs, Oracle Reports, BI Publisher layouts, and inbound integration extracts.

Because the view joins translated and lookup tables internally, consumers do not need to re-implement those joins or filter by language. It is registered in ETRM with status VALID and is not an entity in its own right; it is a presentation layer over the underlying _B, _TL, FND_LOOKUPS, and WF_RUNNABLE_PROCESSES_V objects.

Underlying Base Objects

The documented base objects of the view are:

The ESCALATION and Workflow joins are outer joins, so bulletins without a valid escalation code or Workflow process still appear; the BULLETIN_TYPE and FREQUENCY joins are mandatory.

Key Columns

In addition to the primary key BULLETIN_ID and ROWID, the view exposes the following significant attributes:

  • NAME / DESCRIPTION — translated bulletin name and long description from CSD_BULLETINS_TL.
  • BULLETIN_TYPE_CODE, BULLETIN_TYPE_MEANING, BULLETIN_TYPE_DESC — the bulletin classification and its display text from 'CSD_BULLETIN_TYPES'.
  • ACTIVE_FROM / ACTIVE_TO — the validity window; only records where the current date falls inside this range should generally be treated as live.
  • PUBLISHED_FLAG and MANDATORY_FLAG — flags indicating whether the bulletin is published and whether it is compulsory reading for the target audience.
  • ESCALATION_CODE, ESCALATION_MEANING, ESCALATION_DESC — escalation classification resolved from 'CSD_ESCALATION_CODES'; may be null.
  • FREQUENCY_CODE, FREQUENCY_MEANING, FREQUENCY_DESC — the recurrence classification from 'CSD_BULLETIN_FREQUENCY'. This is the column of interest behind the "frequency_meaning" search, since it decodes the stored FREQUENCY_CODE into a user-readable value.
  • WF_ITEM_TYPE, WF_PROCESS_NAME, WF_PROCESS_DISPLAY_NAME — the Oracle Workflow item type, process name, and its display label.
  • WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), OBJECT_VERSION_NUMBER, and ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 — audit and descriptive flexfield context.

Common Use Cases and Queries

Typical consumers use the view to list currently active bulletins for an agent, to drive alerting or escalation workflows, and to report on mandatory bulletins by type and frequency.

List all active, published bulletins with their readable frequency meaning:

SELECT bulletin_id, name, bulletin_type_meaning,
       frequency_meaning, mandatory_flag,
       active_from, active_to
  FROM apps.csd_bulletins_v
 WHERE published_flag = 'Y'
   AND TRUNC(SYSDATE) BETWEEN active_from AND NVL(active_to, TRUNC(SYSDATE));

Summarize bulletins by frequency to identify recurring maintenance instructions:

SELECT frequency_code, frequency_meaning, COUNT(*)
  FROM apps.csd_bulletins_v
 WHERE published_flag = 'Y'
 GROUP BY frequency_code, frequency_meaning;

Identify bulletins tied to an escalation and a specific Workflow process:

SELECT bulletin_id, name, escalation_meaning,
       wf_item_type, wf_process_display_name
  FROM apps.csd_bulletins_v
 WHERE escalation_code IS NOT NULL
   AND wf_process_name IS NOT NULL;

Retrieve a single bulletin by identifier for an integration payload:

SELECT * FROM apps.csd_bulletins_v WHERE bulletin_id = :p_bulletin_id;

These patterns are supported on both 12.1.1 and 12.2.2, as the view definition and its referenced base objects are consistent across the two releases.