Description of the illustration ''%s''prc_roaming_rapin

This figure shows how the RAP processing works. RAP files enter the RAP processing pipeline which generates an acknlowledment files. It sends the TAP records to the suspended events loader and TAP files to the suspended batch loader from where the data is loaded into the BRM database. Entries entered in the Suspense GUI are stored directly in the BRM database. If there were no roaming EDRs for a network operator, the RAP processing pipeline sends missing TAP data as notifications. The pipeline specifies the extraction criteria for extracting settlement events associated with the TAP3.11 file or records. The settlement pipeline finishes processing the outcollect TAP3.11 file. The file is moved to another pre-defined directory for sending the TAP3.11 file to your roaming partner or clearing house. Erroneous TAP3.11 files and records are reprocessed and corrected. New TAP3.11 files are generated to to send to roaming partner.If the erroneous TAP3.11 files and records were previously recorded in the BRM database, the processing backs out the balance impacts of settlement events associated with them..