The Service Control Point (SCP) Reverse Audit Results report is a pre-defined report that is initiated from and output to Reporting. This report provides discrepancies found between SCP records and TFNRegistry™ (tfnregistry.somos.com) that resulted from the audit.
The SCP reverse audit is performed to ensure consistency between the Customer Records in the SCPs and those in the TFNRegistry. The TFNRegistry audits are performed on a regular basis upon a Special Request received from the SCP Owner/Operator (SCP O/O) via the Somos Portal Website (portal.somos.com) which is processed by the Help Desk. In order to audit an SCP, the SCP O/O sends the Software Support an SCP-generated audit file listing all of the Customer Records in the SCP via a Secure File Transfer Protocol (SFTP). The SCP O/O will need to work with the Help Desk and Somos to obtain an SFTP Login ID for the reverse audit. Software Support then runs an audit process that compares the records on the SCP audit file to the records in the TFNRegistry. The discrepancies found between the two sets of data are generated on the SCP Reverse Audit Results report.
When the audit is complete, the Software Support notifies the Help Desk, that the audit has been completed. The Help Desk notifies the SCP O/O, who then reviews the SCP Reverse Audit Results report. If any discrepancies in SCPs are found, a Customer Record resend process is run to correct them.
Customer Records included in the audit are those that meet the following criteria:
- The record’s Effective Date/Time is earlier than or equal to the start time of the SCP-generated audit file.
- The Customer Record status is Active, Sending or Disconnect. For Toll-Free Numbers (TFNs) that have both an Active and Sending record, or both a Disconnect and Sending record, only the Sending record is used in the audit.
|
This data is updated nightly. The data retention may be 60 days though this may subject to change. |
Disclaimer: Any images in this article are intended to be used as a guide for educational purposes only and they may differ slightly from the Production Environment.
|
SCP Reverse Audit Results Field Descriptions |
|
|
Field |
Description |
|
SCP ID |
Identifies the ID of the audited SCP. |
|
Audit Date |
Identifies the date the audit was performed. |
|
SCP Tape Creation Date |
Identifies the date and time of the SCP audit file was generated. |
|
NPA |
Identifies the NPAs (area codes). |
|
Toll-Free Number/Template |
Identifies the Toll-Free Number or Template Name for which a discrepancy was found between the TFNRegistry and an SCP(s). |
|
SCP Eff Date/Time |
Identifies the Effective Date and Time of the TFN record in the SCP. |
|
CR Status |
Identifies the Customer Record status of the TFN record in the TFNRegistry. Status definitions are:
|
|
Discrepancy Message |
One of the following 6 messages is listed:
|
|
Last Updated Date/Time |
The date and time updated in the Transactional database (when activity occurred). |
|
Last Refresh Date/Time |
Identifies the date and time the report was last refreshed. |
|
Record Count |
Display the count of records associated with the filtered data set (xxxxxxx) and the grand total of records (yyyyyyy) formatted as xxxxxxx/yyyyyyy. |
Data Source Used to Create the Report
The “RHDB_SCPSMSAUDITRESULTS” data source is used to create the SCP Reverse Audit Results report. The fields used from this table are:
- CR Status
- Discrepancy Message
- Last Updated Date/Time
- NPA
- SCP Eff Date/Time
- SCP ID
- SCP Tape Creation Date
- TFN Registry Audit Date
- Toll-Free Number/Template
Please Note: For more information, please refer to the SCP Reverse Audit Results Table (RHDB_SCPSMSAUDITRESULTS).