The following program description deals with:
By use of this program you can maintain the data for the automatic receipt archiving, i.e. create new records, modify or delete existing data. You can also view already stored data for information purposes.
This program is an enhancement of the update program Archive Files by use of which the receipts can only be archived manually.
If this program is embedded (receipt archiving = LstRecLog) in a report chain and started by use of a Scheduler, the program is started e.g. at the end of each day. With the program execution, it is checked according to the data in the fields Interval (days) and Exclude (days), whether the conditions defined there are met or not.
You can start this program manually by clicking on the button Receipt Archiving and entering the selection data as follows:
Note:
When embedding this program in a Report Chain, you have to enter the appropriate
selection criteria in the Report Chain Parameters.
This paragraph will provide a short overview over the options available for updating these basic data
Just like in almost any other program:
Permitted input range: numeric, 1 - 9999
Enter the number of the company for the area of which you would like to archive the receipt transactions stored in the system. If you do not know the number, you can also select the data record via the Search Function.
Permitted input range: numeric, 1 - 99999
Enter the number of the branch for which you would like to archive the receipt transactions stored in the system. If you do not know the number, you can also select the data record via the Search Function.
Permitted input range: DDMMYYYY (day, month, year)
Date of the last execution of this program. A successful program execution depends on the conditions defined in the fields Interval (days) and Exclude (days).
Note:
If this program is embedded (receipt
archiving = LstRecLog) in a report chain and started by use of a Scheduler, the program is started e.g. at the end of
each day. With the program execution, it is checked according to the data in
the fields Interval (days) and Exclude (days), whether the conditions defined
there are met or not.
Example:
Interval (days) = 90
Exclude (days) = 30
You have defined that 90 days after the date Last successful execution, all receipt transactions stored in the system are to be archived. By the entry in the field Exclude (days), you define that the last 30 days prior to the system date are to be excluded.
With
the program execution, the condition is met as follows:
The program is executed if the date of the last successful receipt archiving is
older than 90 days.
The program is not executed if the date of the last successful receipt
archiving is younger than 90 days.
Permitted input range: DDMMYYYY(day, month, year)
Date of the last successful program execution. The successful program execution depends on the conditions defined in the fields Interval (days) and Exclude (days). In addition, the individual program steps of the receipt archiving are recorded and evaluated.
If one of the following program steps is recorded with an error message, the date in the field "Last successful" is not changed, and with the next program start, another program execution attempt is made.
Permitted input range: DDMYYYY (day, month, year)
Date of the last program start. This date shows only the date on which the program was started last. If and when the program has been executed is shown in the field Last Execution.
Permitted input range: numeric, 1 - 99999
Enter the interval in days in which the receipt archiving is to be carried out. The reference date is the system date.
Permitted input range: numeric, 1 - 99999
Enter the number of days to be excluded from the receipt archiving.
The program calculates the entered number of days back from the system date. The receipt transactions stored in the system within this time period will not be archived.
Permitted input range: alphanumeric, max. 40 chars.
Enter the complete path of the directory in which the archive files *.asc are to be backed up. The backup directory must definitely be valid and accessible at the time of the backup (e.g. external backup medium).