The selection window allows you to filter the report by:

• Date Range: You can either select a pay period, or you can simply enter the start and end date directly into the selection criteria window. The Period selection is merely a short-cut for entering a date range, so you can always edit the start and end dates to be any date you choose. For example, you can pick a period defined as 8/1/2004 to 8/12/2004, and then extend the end date by three days to 8/15/2004. If you leave the end time blank, the program will assume you want the entire day for the end date. In the example below, the start date/time is 8/1/2004 00:00:00 (a blank is assumed to be time 00:00:00) and the end date/time is 8/15/2004 00:00:00. Because the end date time is blank (or 00:00:00), the program assumes you want the whole day of the 15th and makes the end date/time 8/16/2004 00:00:00. In the selection query, the program returns records whose start date/time is greater than OR equal to the start/date time and strictly less than the end date/time.
• Note:  for report information that is based on load tickets, the report uses the Date Out (not the Date In).
• Destination:  You can select any or all of your destinations.
• Block:  You can select any or all of your blocks.  Users often like to run this report for a single block, across all destinations.
• Summary Data Only:  Most users prefer to view this report in summary mode, so you will want to check this box in general.
• Use Invoice Revenue:  For users who are configured to enter revenue manually on a ticket-by-ticket basis, the report will use the hand-entered revenue if this box is unchecked.  If you want to review this report before you've received your settlements from the mill and reconciled them through the Logger's Edge, you can check this box, in which case the report will use the revenue figures calculated by the system.

The report shows payments due for each load on an activity-by-activity basis.  The columns are:

• Destination:  Destination of the Loads
• Block Code:  Source Block of the Loads
• Date:  Exit date/time of the load -- suppressed in the summary view of the report
• Ticket: Load ticket number
• Species:  This column is based on C_PART_4 in the database.  For most users, this field is "Species."
• Product:  This column is based on C_PART_5 in the database.  For most users, this field is "Product" or "Sort."
• Contract:  Revenue or Payment Contract under which activity should be paid
• Activity:  Activity for which revenue was received or pay was issued.
• Net Weight:  Net (Gross less Tare) load weight taken directly from the load tickets.  The unit of measure is based on the delivery units specified during the block setup process.
• Pay Weight:  Basis (e.g., tons, mbf, cords, distance) used for calculating revenue and payments.
• Pay Rate:  $ Rate used for calculating revenues or payments.
• Revenue:  Revenue from the mill is reported with a positive sign; payments to contractors (or employees) are reported with a negative sign.  The difference between the revenues and the payments (cost) is the profit (which ideally will be a positive number!).
• $/Volume:  Revenue or Cost stated on a per unit of volume basis.  The volume measure is the production unit of measure specified during the block setup process.  Thus, if revenue is based on one unit of measure (say tons) and pay is based on another unit (say cords), this column will show the revenues and costs all converted into a common unit of measure (which, again, is the production unit of measure specified during block setup).

• Calculators (employees, vendors, and invoices) must be run in order for this report to contain complete information.
• The report only covers cash outlays in the form of payments to vendors or payments to employees who are paid on a load basis.  Thus, the report is most useful when all activities are paid on a load-by-load basis (rather than by day rates, or hourly rates).
• The load count field on the ticket window is not used when calculating the load counts on this report.  Rather, the load counts assume that each record entered as a ticket into the Logger's Edge is to be counted as one load.
• This report makes NO distinction between Header and Detail records (C_Part_13) for piece-based systems.

This example shows the report in the format in which it is most commonly run:  in summary mode, for one block and all destinations.  The report is ordered first by destination and then block for each destination.  For example, deliveries of pine sawlogs from the Evans block going to Greenville amounted to 123.94 mbf.  At $160 per mbf, the total revenue was $19,829.60.  Cutting payments were made for these deliveries based on the ton, stumpage payments were based on the mbf, and trucking payments were issued to both employee drivers as well as contract truck owner/operators by the mile (distance), for a total cost of $17,034.85.  Total profit for the 25 loads of Pine Sawlogs was $2,794.75, or $3.76 per ton.

Example 1 - Summary View for One Block and All Destinations

This example shows the report in detailed form so that you can see the revenue and costs associated with each individual ticket.  Most users only use this detailed view if they are trying to research the summary numbers.  For example, Ticket 708011 (a Pine Pulpwood ticket) had revenue of $456.13 (8.29 cords at $55 per cord).  It had a cutting payment based on tons, a stumpage payment based on cords, and a trucking payment based on distance.  Together, the payments totaled $410.80, for a total profit of $45.33, or $1.82 per ton (which is the production unit of measure specified on the block).  Likewise, ticket 708068's revenues and payments are detailed in the report, and the results are summarized by tract, and then by destination, with a grand total at the bottom.

 

Example 2 - Detailed View (Ticket by Ticket)