Search Results audit_discrepancy_id

Overview

The XNP_AUDIT_DISCREPANCIES table is a core data object within the Oracle E-Business Suite Number Portability (XNP) module, applicable to both versions 12.1.1 and 12.2.2. It functions as a detailed audit log for data integrity failures encountered during the number porting process. Specifically, it stores records of mismatched network data identified when comparing information between a service provider and a specific version of a subscription. Its primary role is to track and persist discrepancies that require investigation or reconciliation, ensuring compliance and accuracy in telecommunications number management.

Key Information Stored

The table is structured to capture the essential elements of each identified data mismatch. The primary identifier is the AUDIT_DISCREPANCY_ID. A unique composite key ensures that for a given audit, telephone number, and service provider, a specific error is recorded only once. This key consists of SUBSCRIPTION_TN (the telephone number in question), SP_ID (the service provider identifier), AUDIT_ID (linking to the parent audit run), and ERROR_CODE (categorizing the type of discrepancy). Other critical columns, inferred from the context, likely include timestamps, detailed mismatch descriptions, and the specific data values that failed validation from the network and subscription records.

Common Use Cases and Queries

The primary use case is generating discrepancy reports for audit analysis and troubleshooting. Administrators and operational staff query this table to identify systematic data issues or to resolve individual porting failures. A common pattern is to join with the parent audit and service provider tables to produce meaningful reports.

• Listing all discrepancies for a specific audit run: SELECT * FROM xnp_audit_discrepancies WHERE audit_id = <value> ORDER BY subscription_tn;
• Finding active discrepancies for a specific service provider: SELECT error_code, COUNT(*) FROM xnp_audit_discrepancies WHERE sp_id = <value> GROUP BY error_code;
• Detailed discrepancy report with descriptive context: SELECT d.subscription_tn, d.error_code, a.audit_date FROM xnp_audit_discrepancies d, xnp_sv_audits a WHERE d.audit_id = a.audit_id AND a.audit_status = 'COMPLETE';

Related Objects

The XNP_AUDIT_DISCREPANCIES table has defined relationships with other key XNP tables, forming a critical part of the audit data model.

• XNP_SV_AUDITS: This is the parent table. The foreign key on AUDIT_ID links each discrepancy record to a specific audit execution instance, providing context like the audit date and initiating parameters.
• XNP_SERVICE_PROVIDERS: The foreign key on SP_ID links each discrepancy to the involved service provider, enabling reporting and analysis by provider.
• XNP_SUBSCRIPTION_VERSIONS: While not explicitly listed as a foreign key, the SUBSCRIPTION_TN column is intrinsically related to subscription data, and queries often join to subscription-related views to get customer or service details.