Results for “suspension_activity_id”

48 results




Overview
Explore in AI Chat

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

Overview

The CSC_SUSPENSION_ACTIVITY_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Customer Care (CSC) product family. It presents suspension activity records associated with a customer account, exposing the full lifecycle of actions taken to suspend or reinstate services, sites, or accounts. The view is defined as a simple projection over the HZ_SUSPENSION_ACTIVITY synonym, meaning it does not perform joins, aggregations, or transformations — it surfaces the underlying columns directly. Its primary role is to provide a stable, customer-facing interface for reporting, extensions, and integration programs that need to read suspension history without querying the base table directly. Because the view is a thin wrapper, it inherits the security and data model of HZ_SUSPENSION_ACTIVITY while offering a controlled column list suitable for downstream use.

Underlying Base Objects

The documented base object referenced by this view is HZ_SUSPENSION_ACTIVITY, referenced through a SYNONYM. The view text confirms this relationship:

No additional joins or filters are applied, so every row returned by the view corresponds to a single row in HZ_SUSPENSION_ACTIVITY. The synonym abstraction allows Oracle to relocate or restructure the base object without breaking dependent code. Note that the documented description references the internal name AST_SUSPENSION_ACTIVITY_V, while the object name and view text consistently use CSC_SUSPENSION_ACTIVITY_V; this reflects the historical product lineage of the suspension activity feature within Oracle's customer care and service tracking modules.

Key Columns

The view exposes the following columns, which are relevant to suspension tracking and, in particular, to notification management:

  • CUST_ACCOUNT_ID — Identifier of the customer account whose suspension activity is recorded.
  • SUSPENSION_ACTIVITY_ID — Primary identifier for the suspension activity row.
  • SITE_USE_ID — The site use affected by the suspension action.
  • ACTION_TYPE / ACTION_REASON — The nature and cause of the suspension action.
  • ACTION_EFFECTIVE_ON_DATE, BEGIN_DATE, END_DATE — Effective, start, and end dates for the action.
  • NOTICE_TYPE — Classification of the notice associated with the suspension.
  • NOTICE_METHOD — The delivery channel used for the notice. This is the column most relevant to the searched term notice_method, and it records how the customer was notified (for example, mail, email, or other channel designations).
  • NOTICE_SENT_DATE — Date the notice was dispatched.
  • NOTICE_RECEIVED_CONFIRMATION — Indicator of whether receipt was confirmed.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns managed by the EBS framework.

Common Use Cases and Queries

The view is typically employed to investigate notification failures, audit suspension timelines, and feed downstream correspondence or collections processes. A basic retrieval of notice-related activity for a customer is shown below:

  • SELECT cust_account_id, suspension_activity_id, notice_type, notice_method, notice_sent_date, notice_received_confirmation FROM csc_suspension_activity_v WHERE cust_account_id = :p_account_id ORDER BY notice_sent_date DESC;
  • SELECT notice_method, COUNT(*) FROM csc_suspension_activity_v WHERE notice_sent_date IS NULL GROUP BY notice_method; — identifies pending notifications by channel.
  • SELECT * FROM csc_suspension_activity_v WHERE action_type = :p_action AND action_effective_on_date BETWEEN :p_start AND :p_end; — supports period-based suspension reporting.

Because the view is not indexed independently, performance depends on indexes on HZ_SUSPENSION_ACTIVITY, notably those on CUST_ACCOUNT_ID and SUSPENSION_ACTIVITY_ID.