Results for “event_cause_code”

14 results




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

Overview

XNP_SV_EVENT_HISTORY is a transactional table owned by the XNP schema within the Oracle E-Business Suite Number Portability (XNP) module. Its documented purpose is to store information about any kind of event that occurs against a porting number or a porting-related message. The table therefore functions as the audit and lifecycle trail for number portability activity, capturing discrete state changes, notifications, and processing milestones as they happen.

From an analytical modeling perspective, the mined foreign-key structure suggests a Data Vault classification of link. The table carries an explicit surrogate primary key, XNP_SV_EVENT_HISTORY_PK on SV_EVENT_HISTORY_ID, and references two parent entities — XNP_MSGS and XNP_SV_SOA — making it a natural associative record connecting an event to the message and service-order context in which it occurred. Treating it as a link satellite in a Data Vault model is a reasonable heuristic, given that it also carries descriptive attributes such as event code, event type, and event timestamp that describe the relationship itself rather than either parent.

Key Information Stored

The table is documented with 13 columns in release 12.2.2. The most significant are summarized below.

  • SV_EVENT_HISTORY_ID — Surrogate primary key, enforced by XNP_SV_EVENT_HISTORY_PK and backed by the unique index XNP_SV_EVENT_HISTORY_U1. This is also the column returned by the user search term "sv_event_history_id."
  • SV_SOA_ID — Foreign key to XNP_SV_SOA, tying the event to the parent service order or porting request.
  • MSG_ID — Foreign key to XNP_MSGS, tying the event to the specific portability message that triggered or recorded it.
  • EVENT_CODE — Code identifying the specific event that occurred.
  • EVENT_TYPE — Classification of the event, enabling grouping and reporting across event categories.
  • EVENT_TIMESTAMP — The point in time at which the event occurred, central to chronological reconstruction.
  • EVENT_CAUSE_CODE — Reason or cause associated with the event, useful for root-cause analysis.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data isolation and row-level security.
  • CREATED_BY / CREATION_DATE — Standard EBS WHO columns capturing the creating user and insertion timestamp.
  • LAST_UPDATED_BY / LAST_UPDATE_DATE — Standard EBS WHO columns capturing the last modifying user and update timestamp.
  • LAST_UPDATE_LOGIN — Login context of the last update, consistent with Oracle Application Object Library conventions.

Only SV_EVENT_HISTORY_ID appears as a documented business-key candidate via a unique index; the remaining identifiers are foreign keys or descriptive attributes.

Common Use Cases and Queries

Typical uses include reconstructing the full event timeline of a porting request, auditing message processing, monitoring porting throughput, and diagnosing failures. A common pattern joins the table to its parents to produce a readable history:

  • Reconstructing a porting timeline: SELECT e.EVENT_TIMESTAMP, e.EVENT_CODE, e.EVENT_TYPE, e.EVENT_CAUSE_CODE FROM XNP.XNP_SV_EVENT_HISTORY e WHERE e.SV_SOA_ID = :soa_id ORDER BY e.EVENT_TIMESTAMP;
  • Tracing events for a specific message: SELECT e.SV_EVENT_HISTORY_ID, e.EVENT_CODE, e.EVENT_TIMESTAMP FROM XNP.XNP_SV_EVENT_HISTORY e JOIN XNP.XNP_MSGS m ON e.MSG_ID = m.MSG_ID WHERE e.MSG_ID = :msg_id;
  • Reporting event volumes by type over a period, grouping on EVENT_TYPE and filtering on EVENT_TIMESTAMP.
  • Failure analysis, filtering on EVENT_CAUSE_CODE to isolate error conditions.

Reporting should always include SECURITY_GROUP_ID filtering where the deployment relies on Org or security-group isolation, mirroring the security model applied by the base tables XNP_MSGS and XNP_SV_SOA.

Related Objects

The most significant objects that reference or are referenced by XNP_SV_EVENT_HISTORY are:

  • XNP_SV_SOA — Parent service-order/SOA entity, joined via XNP_SV_EVENT_HISTORY.SV_SOA_ID.
  • XNP_MSGS — Parent message entity, joined via XNP_SV_EVENT_HISTORY.MSG_ID.
  • FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID for row-level security.
  • XNP_SV_EVENT_HISTORY_PK / XNP_SV_EVENT_HISTORY_U1 — Primary key constraint and unique index on SV_EVENT_HISTORY_ID.
  • XNP_SV_SOA and XNP_MSGS child implementations — Any XNP process or concurrent program writing porting events populates this table and typically reads it back for status reporting.

Together these relationships place XNP_SV_EVENT_HISTORY at the intersection of porting messages and service orders, making it the central audit link for number portability processing in EBS 12.1.1 and 12.2.2.