Use reports to analyze your data. Reports can be either "Simple" (a subset of the data) or "Grouped" (for statistical analysis)
When building a new report you have several steps:
¶ Basic Details
In the “Basic Details” section, you can choose the report’s name, the entity that you want to build the report on (Usage, Bills, etc), and the report type: simple (will present all the relevant rows), or grouped (will present grouped rows).
¶ Columns
In the “Columns” section, you can choose the columns that you want to add to the report, from the entity’s relevant fields. If the report is “grouped”, you’ll have to choose for each of the columns it’s “group function”. For example, you can create a report on the usages that you collected from a CDRs files, and group the report by “File name” field:
¶ Conditions
In the “Conditions” section, you can choose to filter the data that you want to see in your report.
You’ll choose the field/fields that you want your conditions to be on, and build the condition using “Operator” and “Value”. For example, if you want to build a report on the usages you collected from a CDRs files, and see only the CDRs that were received from a certain file, you can do it using a condition on the file name :
¶ Sort
In the “Sort” section, you can sort the report’s result. For example, if you build a report on the usages you collected from a CDRs files, and one of the columns that you chose to display on your report is “File name”, you can sort the report results in ascending/descending format, according to the file name:
¶ Formatting Style
In the “Formatting style” section, you can choose to display chosen fields, according to some format. For example, if one of your reports fields is a date field, you can choose how to display the date in your report :
¶ Usage report
You can run usage-based reports which apply to CDRs, charges / refunds and any plan / service for which a subscription has been charged in any of the billing cycles, or in short - all the subscriptions' "lines".
Fields which start with "Customer:" / "Subscriber:" relate to the latest customer / subscription known (and not necessarily to the customer / subscription data at the time of the CDR.
¶ Common Fields
- Activity volume - Total volume consumed in the CDR
- Billing cycle - Invoice period in which the line is included
- Billing cycle status - Same as "Billing cycle" but contains dynamic values:
- Current - Active cycle (by billing cycle date range)
- Last Confirmed - Last billing cycle that was confirmed
- First Unconfirmed - First cycle following the last confirmed one
- Confirmed - All confirmed billing cycles
- Calculator name - only relevant in the queue, will show the last calculator the CDR line completed successfully:
- FALSE - did not pass any calculator - likely because no subscriber was found for the line.
- Customer - found a customer but did not find a rate for the line.
- Rate - found a rate but had an issue setting a price.
- Pricing - line has a price but there is an issue with the tax.
- Campaign inclusive units - For campaigns (groups), this is the total free (not charged) volume out of the CDR total volume
- Campaign name - If the CDR benefited from a campaign (group), its name
- Charge before taxes - Total charge for the billing line, without taxes
- Customer ID - BillRun unique identifier for the customer
- File name - Source filename of the billing line (when relevant)
- Process Time - Time when the line was processed by BillRun
- Product key - Product matched for the line
- Record time - Time of the CDR
- Record unique ID - Unique BillRun identifier for the line
- Subscriber ID - BillRun unique identifier for the subscription
- Subscriber's plan key - Subscription's plan at the time of the CDR
- Total charge - Total charge for the billing line, including taxes