VAST transaction and evaluation master data

Table : VAST Global table Number of attributes: 47 Description : transaction and evaluation master data

Description Transaction and evaluation key number

VANR KEY FIX 1 99 2 2 INTEGER

VART Goods receiving BART Without price / delivery note

OPLS - EXP 0 1 183 2 INTBFEX PARA Scale and POS tickets

WKMO - EXP 0 2 185 2 INTBFEX PARA Transaction enabling / disabling

VBST - EXP 0 1 187 2 INTBFEX PARA Transaction with date

ZEIT - EXP 0 2 189 2 INTBFEX PARA Sales storage time in days

HTAG - EXP 0 31 191 2 INTBFEX PARA POS with flash memory

KFLS - EXP 0 1 193 2 INTBFEX

TABS Training sales

c – Data structure VAST transaction and evaluation master data typedef struct

{

short walo; /* Cancel flag */

short vanr; /* Transaction and evaluation key number */

IntBfDb16 vart; /* DBM bit field for sales modes */

IntBfDb16 bart; /* DBM bit field for ticket types */

IntBfDb16 para; /* DBM bit field for parameters */

short mast; /* Sales master address */

short back; /* Sales backup address */

IntBfDb32 tabs; /* DBM bit field for sales table allocation */

IntBfDb32 vtab; /* DBM bit field for internal sales assignment */

long mdat; /* Date of modification */

ushort rv; /* BART Wastage weighing/rewrap no=0, yes=1 */

ushort ret; /* BART Returns no=0, yes=1 */

ushort opls; /* BART Without price, delivery note no=0,Yes=1 */

ushort wkmo; /* PARA Scale/POS tickets */

ushort vbst; /* PARA Transaction enabling/disabling */

ushort zeit; /* PARA Transaction with date */

ushort htag; /* PARA Sales storage time in days */

ushort mwum; /* TABS VAT sales no=0, yes=1 */

ushort beum; /* TABS Operator sales no=0, yes=1 */

ushort tpum; /* TABS Fidelity point sales no=0, yes=1 */

ushort abum; /* TABS Department sales no=0, yes=1 */

ushort haum; /* TABS Main dpt. sales no=0, yes=1 */

ushort fbum; /* TABS Frequency sales no=0, yes=1 */

ushort trum; /* TABS Training sales no=0, yes=1 */

ushort kaum; /* TABS Cashier sales no=0, yes=1 */

ushort ksum; /* TABS POS sales no=0, yes=1 */

ushort zaum; /* TABS Markup/discount sales no=0, yes=1 */

} TYvast_entry;

Explanations:

WALO: Cancel flag :

0= record is modified or created 1= record is deleted

VANR: Key number

This is the key under which the posted sales are stored in all relevant sales tables.

VART: Internal value (=0) BART: Internal value (=0) PARA: Internal value (=0) MAST: Address of sales master

0 = local:

If no sale address is entered (MAST=0), the sales remain locally in the scale which makes the entries. With a valid scale address entered, the locally posted sales are obtained from the sales master at variable periods of time and locally deleted.

BACK: Address of the sales backup if MAST <> 0

This parameter is only valid if a valid master address is entered.

The data communication between the sales master and backup takes place via difference records (in the following referred to as DELTA sales).

In these records, only sales modifications are stored which are not known to the remote station. After adjustment of the sales master and backup, this data is deleted. These records are for internal use only.

TABS: Internal value (=0) VTAB: Internal value (=0)

WREF: Scale allocation

The position in this scheme represents the scale address. Only the values '0' and '1' are permitted.

'0' = the scale is not to post sales '1' = the scale is to post sales VATE: Infotext

This extra text is not relevant to the scale management.

TRAI: Sales modes of assisted sale

. no = 0

. yes = 1

BS:

NORM: Ticket types of assisted sale

. no = 0

. yes = 1

OPLS:

WKMO: Transaction mode

Differentiation according to scale sales and/or POS (cash register) 0 = scale and POS tickets

1 = scale tickets only 2 = POS tickets only

VBST: Status of preset data for transactions 0 = enabled

1 = disabled

With the status disabled (VBST=1), no sales are posted to the tables. The ticket is directly transferred to the ticket journal.

An entry in the log is then made for each ticket which is not posted (error number 51090).

ZEIT: Entry of time in sales (posting according to time) 0 = without time

1 = posting according to daily date 2 = recopy when deleting

( applies only to POS or cashier sales )

This is an optional parameter which must only be used in conjunction with the global device configuration. Here, the setting must be identical

throughout the system, in order to ensure that a sales evaluation takes all sales data into account.

HTAG: Sales storage time in days (0-31) if ZEIT=1 or ZEIT=2:

0 = store for an undefined period of time

> 0 number of days during which the sales data is to be stored

After 24h00 all sales tables are checked and sales older than the current date 'Storage time' are deleted.

This parameter is only of importance if ZEIT=1 or ZEIT=2 is entered in the aforesaid parameter.

KFLS: POS with FLASH memory

0 = no storage of POS sales in FLASH

1 = storage of POS sales in FLASH if FLASH is existing

This parameter should be set for only one VAST record with POS ticket transaction in the system. For POS evaluations 'with clearing', POS sales are transmitted to the Flash memory.

ULOE: Sales clearing 0 = do not clear 1 = clear if VBST=1

This parameter is checked during loading of the management data. If the transaction is disabled and the 'Cancel' flag set, the sales for this VAST record are deleted from all local tables.

This assignment is provided if, for example, a VAST record is disabled for transactions and if the existing sales are no longer required. This function may also be used for service, in order to correct all sales tables.

For the time being, a checking facility to ascertain whether or not this clearing has been carried out at all active scales is not yet provided.

Loading or updating of the preset VAST data

The records are now loaded from the preset data of the VAST table according to which entries are to be made in the scale or for which the scale operates as the master or backup device. For these records, additional information is stored in a buffer.

VAST data is loaded on the task start and after (partial) database configuration of the scale. Whether or not the VAST data has been modified is checked at intervals of 30 seconds. This is done by checking a control record (VANR=0) of the VAST table, in which a date entry has been made. This date field is stored after a data refreshing in the management range of each scale. During the loading procedure, the program checks recordwise whether or not a sales data adjustment is to be carried out. If yes, this is done after loading of the VAST data.

The time interval depends on the loading of scale and the system activity. It should, however, be 30 seconds if no sales evaluation is active in the system.

Distribution of sales within the system

If a scale is defined as a sales master for one or several VAST records, this master device asks for the sales from scales which make their entries according to this VAST key at cyclic intervals.

In the event that a sales backup is also defined, the received sales data is stored as DELTA sales in addition. After the sales are called up from all other scales, the sales master transmits all modifications to its remote station. The generated DELTA sales are deleted after a successful communication with the remote station.

The time interval depends on the loading of scale and the system activity. It should, however, not exceed 3 minutes if no sales evaluation is active in the system.

A scale defined as a sales backup device acts as a normal scale in a functioning system, operates, however, as a master if it detects that the sales master is inactive. All sales collected in this way are additionally stored as DELTA sales for the remote scale.

If the sales master becomes again active, it obtains this data automatically from its remote backup station and reacts as a master device.