Validity and performance date
In the Hypersoft system, there is the function Validity date, which can also be regarded as a performance date, as required. This date can be used by Hypersoft programs, by 3rd parties via interfaces and it can also be manually determined in POS checkout mode for bookings.
For example, ticket items for the future can be sold via the 3rd party interface, which then contain the validity date or performance date. You can then name and use this date accordingly on forms.
Transactions or individual items of the transactions can be given a validity date. The checkout function Validity date is used to initiate the function. Applied as a macro at the completion of a transaction, the validity date is applied to the entire transaction. Otherwise for a previously booked item. The validity date is also used for the very special Property Report.
The entry is made using the /number pad or by entering the date in advance and pressing the function. Full stop, comma, hyphen are valid separators, but not compulsory. The setting of a validity date can also be entered for returns for the past.
The following entries are permitted (the placeholders stand for numbers):
| d | d stands for day, m for month and j for year |
| dd |
Up to two-digit day indication without further characters, the current day is compared here and the next month applied if necessary. |
|
ddmm |
Here, the day and month are compared with the current date and, if necessary, the next year is applied. |
|
dd.mm |
|
|
dd,mm |
|
| dd-mm | |
|
Ddmmjj |
|
|
dd.mm.yy |
|
|
dd,mm,yy |
|
| dd-mm-jj | Here, the year is checked and the millennium is added in the case of two-digit or one-digit entries. Example: 22 becomes 2022. |
|
Ddmmjjj |
|
|
dd.mm.yyyy |
|
|
dd,mm,yyyy |
|
| dd-mm-yyyy |
All other (invalid) entries are rejected with a hint message.
Reset the input...
An empty entry or also 0 resets the validity date in connection with this function.
Variables for form output in different areas
Variables here denote placeholders in layouts that are then filled with the respective validity date.
On invoices, individual item entries can also have a different validity date. If you use the system as a service date, for example, it would be usual to place the service date with the invoice date or invoice number. This then also indicates that this applies to the complete process.
For example, if you sell tickets for different destination dates in one transaction, then the validity date should be better placed with the respective bookings.
Validity date on NoCOO and DIN A4 invoices...
| Header.BillValidDate |
Total Invoice Variable - If this is filled, the ones in the item are all empty, or all in the item have the same date). |
| Booking.ValidDate |
Column in the booking. Per entry - Is filled if BillValidDate is empty, and at all if a date is given. |
Evaluations regarding the validity date
In general, of course, all bookings with a validity date are also evaluated in the standard system. However, the only report that evaluates the validity date with priority is the BWA report.
Back to the parent page: Global Hypersoft Topics