Web Based Report Building: Selecting the correct View
The Web Based Reporting (WBR) structure uses reporting View tables. A View has finite fields available. If you choose a View that does not have the data fields that you need, you cannot add them in later and will need to start your report again with a different view selected. Therefore, It’s important that you’ve already chosen this from your View using the supplementary WBR Views document before starting.
This document provides a description of each reporting view and field available in Web Based Reporting (WBR).
WBR General Tab
The View is selected on the General Tab - each view will load sample data.
Recommended Views
Product Sales View: Provides itemised information for product sales on each ticket.
Note: Product Sales View provides transaction item level detail, this is useful for when the quantity/volume of product is required, as it displays each product on the transaction. There are some considerations to make before selecting this View as to how the data is presented. If a transactional header field is pulled into the report, it replicates this information across each row and the calculation for this header information is duplicated in any totals. Transactional header level data includes bulked waste classes and cartage (this is generally only an issue for multi-weigh, or for each items on the same ticket as a weighed transaction). For example, bulk waste in QWDS (Queensland EPA) comprises of Municipal, C&I or C&D waste classes. This means that the Product Sales View will show 3 records for the same ticket.
Ticket Details View: A listing of tickets, with no product details. Provides one detail row for each ticket. It does not break down each product and will only show the primary weighed product. This is useful for Cartage based reports.
Note: When using the Ticket details view you must filter out cancelled tickets. This filtering must be embed in the report definition.