Results for “hz_suspension_activity”

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

Overview

HZ_SUSPENSION_ACTIVITY is a Receivables (AR) module table in the Oracle E-Business Suite, owned by the AR schema. It records suspension activity associated with customer accounts and site uses, capturing the point in time at which a service is no longer provided. The table functions as a historical record of service suspension events, enabling organizations to track when service interruptions were initiated, the reasons behind them, and the associated notice and confirmation details.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure designates this table as a link. This classification suggests the table primarily serves to associate two or more business entities — specifically customer accounts and site uses — while also carrying descriptive event attributes. Analysts designing downstream integration or warehouse models may treat HZ_SUSPENSION_ACTIVITY as a link table connecting the customer account hub and the site use hub, with the surrounding columns acting as a satellite payload that records the transactional context of each suspension event.

Key Information Stored

The table contains 22 documented columns. The surrogate primary key is SUSPENSION_ACTIVITY_ID, enforced by the index HZ_SUSPENSION_ACTIVITY_PK. A second unique index, HZ_SUSPENSION_ACTIVITY_U1, is also defined on SUSPENSION_ACTIVITY_ID, reinforcing its role as the business-key candidate for uniquely identifying each suspension activity record.

The most significant columns include:

• SUSPENSION_ACTIVITY_ID — Surrogate primary key uniquely identifying each suspension record.
• CUST_ACCOUNT_ID — Foreign key to HZ_CUST_ACCOUNTS, identifying the customer account subject to suspension.
• SITE_USE_ID — Foreign key to HZ_CUST_SITE_USES_ALL, identifying the specific site use affected.
• ACTION_TYPE — The category of suspension action taken.
• ACTION_REASON — The reason the suspension action was performed.
• ACTION_EFFECTIVE_ON_DATE — The date the suspension action takes effect.
• BEGIN_DATE and END_DATE — The effective date range for the suspension period.
• NOTICE_METHOD, NOTICE_TYPE, NOTICE_SENT_DATE — Details describing how and when suspension notice was delivered.
• NOTICE_RECEIVED_CONFIRMATION — Indicator of whether notice receipt was confirmed.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard auditing WHO columns.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program context, indicating which process created or last modified the row.

Common Use Cases and Queries

Typical scenarios include investigating active suspensions for a customer, auditing notice delivery compliance, and reconciling suspended services against billing activity. A common query joins the table to customer accounts to retrieve suspension history:

• Reporting all suspensions for a given account: SELECT * FROM HZ_SUSPENSION_ACTIVITY WHERE CUST_ACCOUNT_ID = :acct_id;
• Identifying currently active suspensions: filter on BEGIN_DATE <= SYSDATE AND (END_DATE IS NULL OR END_DATE >= SYSDATE).
• Auditing notices: select NOTICE_METHOD, NOTICE_SENT_DATE, and NOTICE_RECEIVED_CONFIRMATION to verify notification compliance.
• Concurrent program analysis: group by REQUEST_ID and PROGRAM_ID to trace batch activity.

Related Objects

The following objects are most significant in relation to HZ_SUSPENSION_ACTIVITY:

• HZ_CUST_ACCOUNTS — referenced via CUST_ACCOUNT_ID; the customer account hub.
• HZ_CUST_SITE_USES_ALL — referenced via SITE_USE_ID; the site use hub.
• HZ_SUSPENSION_ACTIVITY_PK — primary key constraint on SUSPENSION_ACTIVITY_ID.
• HZ_SUSPENSION_ACTIVITY_U1 — unique index on SUSPENSION_ACTIVITY_ID.
• AR.HZ_SUSPENSION_ACTIVITY — the fully qualified table reference in the AR schema.