Page Comparison

...

Date:

Author:

Version:

Changes:

Completed

Ext.

Int.

Is in Core

Jira Ref.

Wiki Markup
{page-info:created-date\|dateFormat=dd MMMM yyyy}

Wiki Markup
{page-info:created-user}

19 July 2013

Luca Casarini

0.1

Doc. created

No

x

N/A

22 July 2013

SD

1.0

Checked

Yes

x

N/A

...

Contents

Table of Contents

...

Overview

Name of report	Wholesale Files Report (previously "Incoming Queue and Engine Processing")
Schedule	Every 2 hours
System	Wholesale; Prepaid/Postpaid
Customer role	Informed, Responsible
CDRator Operations role	Informed, Responsible
CDRator role	Informed

...

Note
CDRator Operations is involved only in case of a Managed Service Agreement with the customer.

At the moment the report is called Incoming Queue and Processed Records of Main Engines Report and looks like these:

...

Field	Direction (from the system's point of view)	Description	Handling
Minutes since last file loaded	incoming	How long in the past (in minutes) the last CDR file was loaded into the wholesale platform. If the system handles different types of CDR files, then these are displayed as separate lines.	The value should be always low. We expect to received CDR files continuously. If the value grows then it could be that the loading functionality has problems or that the Rator system does not receive files from the network.
Number of Unrated CDRs	incoming	How many CDRs are not yet rated.	The value should be always low. We expect rating to work continuously. If the value grows then it could be that the Rator system received a huge amount of CDRs or that there is a problem with the rating process.
Minutes since last export_file was created	outgoing	How long in the past (in minutes) the last export file was generated; for each brand in the wholesale setup.	The value should always be low. We expect the system to rate and export these files continuously. If the value grows then there could be problems with the processes that load and rate CDR files or with the export file generation itself.