Results for “subscription_tn”

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

Overview

The XNP_AUDIT_DISCREPANCIES table is a core data object within the XNP – Number Portability module of Oracle E-Business Suite, deployed in both the 12.1.1 and 12.2.2 releases. Its documented purpose is to store mismatched network data for a given service provider and subscription version. In operational terms, the table captures the deltas detected when the local network database is compared against external or downstream network systems during a number portability audit cycle. Each row records a divergence identified for a specific subscription telephone number, tied to the service provider that owns the record and to the audit run that produced the finding.

Based on the foreign key structure mined from the ETRM data dictionary metadata, the heuristic Data Vault classification for this object is link. This is a modeling suggestion rather than a physical implementation constraint: the table resolves relationships between an audit run (XNP_SV_AUDITS), a service provider (XNP_SERVICE_PROVIDERS), and a subscription telephone number, while also carrying descriptive attributes of the discrepancy itself. It sits between the audit header and the underlying network provisioning data, and is populated by XNP audit processes rather than by direct user entry.

Key Information Stored

The table is defined in the XNP schema and contains 37 documented columns. The following are the most operationally significant:

• AUDIT_DISCREPANCY_ID — The surrogate primary key, enforced by the XNP_AUDIT_DISCREPANCIES_PK constraint and also carried by unique index XNP_AUDIT_DISCREPANCIES_U1. This is the internal identifier for each discrepancy row.
• SUBSCRIPTION_TN — The subscription telephone number to which the discrepancy applies. Together with SP_ID, AUDIT_ID, and ERROR_CODE, it forms the business-key unique index XNP_AUDIT_DISCREPANCIES_U2, which prevents duplicate findings for the same number, provider, audit, and error condition.
• SP_ID — The service provider associated with the audited data; joins to XNP_SERVICE_PROVIDERS.
• AUDIT_ID — The audit run that generated the discrepancy; joins to XNP_SV_AUDITS.
• ERROR_CODE — The classification code describing the nature of the mismatch.
• ROUTING_NUMBER, CNAM_ADDRESS, CNAM_SUBSYSTEM, ISVM_ADDRESS, ISVM_SUBSYSTEM, LIDB_ADDRESS, LIDB_SUBSYSTEM, CLASS_ADDRESS, CLASS_SUBSYSTEM, WSMSC_ADDRESS, WSMSC_SUBSYSTEM, RN_ADDRESS, RN_SUBSYSTEM — Pairs of address/subsystem fields representing the locally held values for routing, calling name (CNAM), ISVM, LIDB, CLASS, WSMSC, and rating/routing number data.
• EXT_* counterparts — The EXT_-prefixed columns (EXT_ROUTING_NUMBER, EXT_CNAM_ADDRESS, EXT_CNAM_SUBSYSTEM, and equivalents) hold the externally sourced values that the local values were compared against, enabling the discrepancy to be reconstructed without re-querying the external system.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS who-column audit trail.
• SECURITY_GROUP_ID — Multi-tenant security grouping, referencing FND_SECURITY_GROUPS.

Common Use Cases and Queries

The primary use case is audit remediation reporting: identifying every telephone number whose network attributes differ from the external reference, scoped by provider and audit run. A representative query joins the discrepancy table to its parent audit and provider records:

• SELECT d.SUBSCRIPTION_TN, d.ERROR_CODE, d.ROUTING_NUMBER, d.EXT_ROUTING_NUMBER FROM XNP.XNP_AUDIT_DISCREPANCIES d WHERE d.AUDIT_ID = :audit_id AND d.SP_ID = :sp_id;
• Grouping by ERROR_CODE to produce a discrepancy summary per audit cycle, useful for carrier scorecards and service-level reporting.
• Joining to XNP_SV_AUDITS on AUDIT_ID to filter discrepancies by audit date range or audit status, supporting trend analysis of recurring mismatches.
• Data-quality dashboards that count distinct SUBSCRIPTION_TN values per SP_ID to quantify the affected subscriber population.

Related Objects

• XNP_SV_AUDITS — Parent audit table; joined on XNP_AUDIT_DISCREPANCIES.AUDIT_ID = XNP_SV_AUDITS.AUDIT_ID.
• XNP_SERVICE_PROVIDERS — Service provider master; joined on XNP_AUDIT_DISCREPANCIES.SP_ID = XNP_SERVICE_PROVIDERS.SP_ID.
• FND_SECURITY_GROUPS — Security group reference used by SECURITY_GROUP_ID.
• XNP_AUDIT_DISCREPANCIES_PK / _U1 / _U2 — The primary key and unique indexes that enforce row identity and business-key uniqueness.

Because the table is written by XNP audit programs, direct DML should be avoided; consumers should treat it as a read-only reporting source and rely on the unique indexes for deduplication logic.