Advanced Usage Utility
|
Advanced Usage Utility
|
Previous Top Next |
| i). Date Range - determines the hire period you wish to report on. This is limited to 800 days.
|
| ii) Special Job Type - Most Eclipse users create a Job Type for managing their repairs (some use Global Jobs). It is likely that you will want to select these jobs out (or in if you want report on repairs) of any database build. You can report on all jobs in the period if you want to.
|
| iii) Daily Usage - Builds a table which records how many items for each Eclipse equipment type were out for each day in your selected reporting period. NOTE: because of the amount of processing involved, you may only want to run this option for specific equipment types only.
|
| iv) Composites - although most users will want to report on their composites (e.g. an amp rack) as opposed to their composite components (e.g. the amplifiers in the amp rack) full control is given to you. Note that items that are components in composites but which are hired out on their own, are not affected by this option.
|
| v) Equipment Filters. - If you want to report on selected categories or types then using this filter will speed up the reporting process and reduce you paperwork. Note that if you select a specific category, you cannot report on "composite components only".
|
| vi) Address Book Filters - Note that the "Special Filter" refers to the user-defined filters which are created in the Address Book.
|
| vi) Status Filters - Just tick the statuses of the equipment lists that you wish to report on. By default "Confirmed" and "Active" are already ticked, but you could also just report on lists that never progressed beyond quote status.
|
| vii) Site Filters – Multi-Site users have the facility to report on ALL sites of just specific ones. You can also specify at what level you wish to focus on site specific usage: the job, the equipment list or specific entries on an equipment list.
|
| vii) Currency – You can choose to report on the usage of equipment in specific job currencies, but please keep in mind that the report tells you what you have earned from jobs done ONLY in that currency
|
| 1. Eql_merge.db
|
|
|
| This table combines essential data from sort.db and archeql.db according to the filters / options you have selected. If your reports need to show data relating to clients/suppliers or to actual equipment lists then you should use this table as the basis for you report. Please note that all the data from all equipment lists who's Out Date or who's Back Date falls inside your reporting period will be included. As such the table contains 2 calculated fields: "fullhiredays" gives you the absolute number of days an item was on hire multiplied by the quantity booked; "shorthiredays" gives you the number of days on hire in the period you are reporting on, again multiplied by the quantity booked. So the two fields may contain the same data however, if you are reporting from 01/04/98 to 01/05/98 and one item was on hire from 26/03/98 to 05/04/98, then the "shorthiredays" value will be "6" while the "fullhiredays" value will be "10".
|
|
|
| 2. NewUsage.db
|
| This table contains summary usage information on a "per equipment type" basis, again according to the filters / options you have selected. It is the most useful of all the tables and is the database used by the main usage report. The fields are TYPE, FULLHIREDAYS, SHORTHIREDAYS, FULLSUBDAYS, SHORTSUBDAYS, and PEAKUSAGE. The standard reports use the SHORT (pro-rata) fields for their output rather than the FULL because this is what most users want to see; changing this or adding the FULL field is quick and ease to do.
|
|
|
| 3. DailyUse.db
|
| This table is only filled if you have checked the "Daily Usage" box. It has 4 fields: TYPE, DATE, OUT and SUBHIRED.
|
|
|
| 4. Usagelog.db
|
| In addition to the usage tables, the programme compiles a "log" table which stores information about the last used database build options. This data is printed on the standard reports.
|