The TFNRegistry generates the SCP load files for loading the new SCP. Verify the number of records generated in each SCP load file (one file per NPA plus Template load file).
The SCP load files are copied on USB drives and shipped to the SCP Owner/Operator (O/O) or sent via Secured File Transfer Protocol (SFTP) from the Data Center. Please note: The TFNRegistry Sandbox environment may or may not be similar in size and data contents to the Production environment. Please be aware that the Sandbox environment is neither a replica nor an identical duplicate of the Production environment.
SCP O/O loads its SCP database using the SCP load files. When a mated pair of SCPs is tested, the SCP O/O will be responsible for copying the database from the loaded SCP to the second, mated SCP. On the TFNRegistry side, the SCP Clone Utility will be used to copy the database information from the loaded SCP to the mated SCP. After the loading of the SCP load file onto the new SCP is completed by the SCP O/O, Software Support uses the Customer Record Audit (CRA) tool to spot check records on the SCPs to confirm that the loaded SCPs have the same records as the TFNRegistry.
SCP O/O generates the SCP load response files (one per NPA plus Template) and sends the files via SFTP to the Data Center of the Sandbox environment.
The TFNRegistry processes the SCP Load response files. Verify the output of the response processing jobs to confirm that all records generated in the load files in step 1 of Test Case #1 have corresponding records in the SCP response files. Verify that the responses have been processed successfully by the TFNRegistry.
The TFNRegistry does the resend to the SCPs (via the communication link) for the database updates that occurred during the time-period spanning steps 3 and 5 in Test Case #1.
SCP O/O generates the reverse audit files (one per NPA plus Template) and uses SFTP to send the audit files to Software Support.
The TFNRegistry performs a reverse audit, identifies discrepancies between the TFNRegistry and SCP, and subsequently the TFNRegistry resends (via the interface communication link) records to correct the discrepancies. If a mated pair of SCPs is defined, the reverse audit shall be performed on both SCPs. After the reverse audit has been completed, use CRA tool to verify that the discrepancies have been corrected and the SCPs have the same records as the TFNRegistry.