|[ < Prev | Contents | Next > ]|
[ Selectors ]
Transaction selectors are used to select which transactions are to be included in reports, such as the selected transaction report which lists individual transactions and the transaction summary report which shows the cumulative effect of a number of transactions and to select transactions for display and processing.
Transactions must match all of the parts of the transaction selector in order to be included in the selection. When Max2 starts the transaction selector is set to match all non-deleted transactions for the current month.
Themenu item allows this default to be restored as well as the setting of other selections which are commonly used.
The following sections describe each of the transaction selector parts in turn. Use the tabs across the top of the form to select the pages containing these parts.
This part defines which types of transactions are to be included in the selection.
Thelist shows all of the types of transaction which are to be included in the selection, whereas the list shows those which will be ignored.
To move types between the lists use the buttons in the middle. Thebuttons move, in the indicated direction, the types which are selected in the source list. To select or unselect a transaction type just click on it with the left mouse button.
This part is not used as much as one might expect as the transaction type is often implied by the following parts. For example, using thepart to specify the glider number of transactions implicitly selects glider flight transactions - these are the only ones with glider numbers.
This part is used to select a date or range of dates to be included in the selection.
The default setting is to choose all of the transactions for the current month.
This setting selects all transactions in August, September or October 1997.
This setting selects all transactions in the last complete week of 1997 - that is, from the 22nd of December to the 28th inclusive.
Zero in the start day number text box indicates that start-of-month transactions for the first selected month are to be included. The default end day number is 31. This applies even in months with 28, 29 or 30 days - there shouldn't be any transactions with invalid day numbers but if there are they will be selected.
Selected periods can run from one day in one month to another day in a following month. E.g., to select all the transactions between the northern spring and autumn equinoxes one could use something like:
The drop down list for the month contains the "(current month)" option plus the last year's months. If you want to do an earlier year then just type in the month name and year number in the same format as used in the list.
This part allows transactions to be selected depending on the attributes of the primary account (proper or trial lesson) associated with the transaction.
The default setting has all of the boxes checked. This example shows the selection of transactions which are for the proper accounts specified by the account selector. Pressing thebutton opens a window to allow the account selection to be entered.
The usual uses of this part, other than the default, have only one box checked. There are a few unusual cases, though. For example, it might be desirable to select all transactions on which VAT has been charged. Assuming that the Account Selector can be used to choose proper accounts which are VATed (temporary members and shorter courses) and that all trial lessons are VATed the following could be used:
A similar setting (but with a different account selector, of course) would be used to select all trial lesson transactions, including trial lesson groups which are treated as temporary members.
A subtle issue arises with respect to the combination of the transaction and account selectors. The question is, which account state is used in the selection - that current at the time of the transaction or that which is presently recorded?
The answer is that the most recent state of the account for the month of the transaction is used. For example, suppose an attempt was made to print a list of all glider flights made by people who had an aerotow credit of more than 2000ft. Suppose also that an account started the month with a 3000ft credit and took a single 2000ft tow. This tow would not be included in the selection because, at the end of the month, the account only had a credit of 1000ft.
This part allows selection of glider flights on the basis of the P1 or non-paying pilot's membership number.
Selects all glider flights in which the holder of account D285 was the instructor or non-paying pilot.
The default, with the text box blank, matches any transaction. If the text box is filled in then only transactions with a P1 number field are selected.
This part selects transactions depending on the transaction's sales heading.
This example would select all transactions with a heading of "Members' Flying".
The third check box indicates the action to take when the transaction has no heading. Almost invariably, this will need to be clear if this part is being used.
Most transactions have only one heading. However, membership sales have two: one for the joining fee and one for the membership component. If either of the transaction's headings match that specified then a match is assumed.
This part selects transactions depending on the cash heading. Currently only cash received and trial lesson sale transactions have a cash heading.
Operation is quite similar to thepart described above.
This part selects flight transactions based on the glider and/or powered aircraft involved. If any of the text boxes are filled in they are matched against the associated fields in the transaction. If the transaction does not have the relevant field (e.g., it is not a flight transaction) then it is not matched.
This example selects all glider flights by the glider EBZ.
The glider-type field.text box selects the glider type, as specified by the charging rules
The tug-registration field and powered aircraft flight transactions on the aircraft-registration field.text box selects glider flight transactions on the
The aircraft-type field. Normally the charging rules are not written to set this field for the tug type for glider flight transactions so normally this text box will not match glider flights.text box selects transactions on the
Selects transactions based on the special-rule-code field.
The drop-down list allows selection of any of the available special rule codes configured or it can be left blank.
This part selects transactions based on their general type.
Normally the other parts will indicate the transactions to be selected without the need to fill in this part. However, if it is known that all the transactions to be selected are daily transactions or that all are start-of-month transactions then filling in this part as well will speed up operation by avoiding the need to scan the other file.
This parts selects transactions based on whether they have been deleted or not.
This part is unusual in that, by default, it does not select all transactions but only those which are in a non-deleted state.
This part selects transactions based on the day of the week they are dated for.
The options are:-
Any choice except "Any Day" will only match daily transactions, not start-of-month transactions.
They should mostly be self explanatory except that the last two select Mondays through Fridays except for bank holidays (defined by the's command and Saturdays, Sundays and bank holidays respectively.
|[ < Prev | Contents | Next > ]|