QtyDiscounts PHYSICAL Table Structure
This page contains technical detail about the physical database structure. It is not required for normal day to day operation of the Point Of Sale.
|qid||number||Primary Key. Not zero||100/E||A unique internal id assigned to this row.|
|IsUnit||number||104/E||Control and flags information.
bit 0,1,2 pricing mode. 0=each, 1=outers, 2=threshold pricing
bit 4 = sale limited
|pct||string, 16 zerolen||106/s|
|dow||string:7||107/s||Day of week mask. Used to set pricemap entries that should only apply on certain days of the week.
If a DOW mask is present (not empty), all days default to off unless present and enabled. To enable a field place a Y (or 'y' or '1') into its day position. Sunday is the first field, followed by Monday. We recommend capital Y and N as the mask characters for maximum reliability
Mask: YY - only allow on Sunday and Monday
|dtstart||date||109/s||Start date for this record. It cannot be selected until this date. Time may be included.|
|dtend||date||110/s||End date that this record will no longer be selectable. A precise time of day can be applied, such as "24-feb-2018 14:04"|
|maxqty||number||112/E||Set the maximum number of units over all sales that this discount can apply too. It is not restricting how many units the shopper may purchase. Use of MaxQty has a number of additional restrictions and is not recommended.|
IndexingA unique primary key should exist on the qid field.
This table can be complex to load directly, we suggest using the Quantity pricing prompt screens to set this information
If using an Oracle database, some of the fields above may need renaming. "table" should be renamed "qtable" and "group" should be renamed "qgroup".