TFNRegistry Reporting: SCP Reverse Results Table (RHDB_SCPSMSAUDITRESULTS) – Somos

The Service Control Point (SCP) Reverse Audit Results table contains results of audit between Customer Records in the SCPs and those in the TFNRegistry (see Table 99 RHDB_SCPSMSAUDITRESULTS).

In order to ensure consistency between the Customer Records in the SCPs and records stored in the TFNRegistry, SCP Reverse Audits are performed on a regular basis by Somos and SCP Owner/Operators (SCP O/Os). To audit an SCP, the SCP owner/operator sends (via SFTP) to the Somos SCP-generated files listing all of the Toll-Free Number (TFN) records in the SCP. The Somos then runs an audit process, which compares the records in the SCP files to the records in the TFNRegistry. The discrepancies found between the two systems are stored in the SCP Reverse Audit Results report and contained in this table (RHDB_SCPSMSAUDITRESULTS).

When the audit is completed, Somos notifies the Help Desk of the SCP Reverse Audit Results report. The TFNRegistry records included in the SCP Reverse Audit Results report are those that meet the following criteria:

The record’s Eff Date/Time is earlier than or equal to the start time of the SCP-generated audit file.
The record's status is either Active, Sending or Disconnect. For records that have both an Active and Sending record, or both a Disconnect and Sending record, only the Sending record is used in the audit.

Table 99 RHDB_SCPSMSAUDITRESULTS

RHDB_SCPSMSAUDITRESULTS
Field	Characters	Description
ScpId	varchar2(4)	The SCP ID being audited.
AuditTapeDate	Date	The date and time the SCP audit file was generated.
AuditDate	Date	The date and time the batch SCP Reverse Audit was performed.
DialNbr	varchar2(12)	The Toll-Free Number (TFN) for which a discrepancy was found.
ScpEffectiveDate	Date	The Effective Date and time of the TFN record in the SCP.
CrStatus	char(1)	The status of the record. Status and definitions are: A – Active D – Disconnect with Referral F – Failed H – Hold I – Invalid M - Must Check P – Pending S – Sending U - Saved
DiscrepancyMsg	varchar2(30)	One of the following six messages is listed: NO MATCH IN SMS/800 - The TFN is in the SCP file, but there is no matching ACTIVE, SENDING, or DISCONNECT record in the TFNRegistry. SCP NOT IN AOS - The TFN is in the SCP file and there is a matching record in the TFNRegistry. However, the Area of Service defined in the TFNRegistry record does not include the audited SCP’s network. MIS-MATCHED DATE/TIME SMS>SCP - The TFN is in the SCP file and there is a matching record in the TFNRegistry. However, the EFF DATE/TIME of the record in the TFNRegistry is greater than (later than) the EFF DATE/TIME of the record in the SCP. MIS-MATCHED DATE/TIME SMS>SCP - The TFN is in the SCP file and there is a matching record in the TFNRegistry. However, the EFF DATE/TIME of the record in the SCP is greater than (later than) the EFF DATE/TIME of the record in the TFNRegistry. RECORD NOT FOUND IN SCP - A TFN found in the TFNRegistry that should have also been in the SCP was not found in the SCP. In this case, the Help Desk should contact Software Support to confirm that step 2 of the audit process was run (this step will cause the record to be resent to the SCP). MIS-MATCHED RESP ORG - The TFN’s Resp Org in the SCP does not match the Resp Org in the TFNRegistry.
ExtractDate	Date	The date when the record was sent to the RHDB database.

Index for RHDB_SCPSMSAUDITRESULTS Table

The index and fields used for the RHDB_SCPSMSAUDITRESULTS table are:

RHDB_SCPSMSAUDITRESULTS
Index Name	Fields Used
rhdb_ SCPSMSAuditResults _idx1	SCPId AuditDate DialNbr