SaleChangesAfterComplete 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.

Goto: Documentation Home

This table stores transactional information about a sale that was received after the sale was finalised. Information in this table is of a more significant nature than general logging/auditing which is stored in SaleLog

Columns

FieldName	Datatype	Meta Info	Gnap	Description
Physkey	string:44,zerolen	Required	100/s	Unique key assigned to this record
Physkeys	string:44,zerolen		101/s	Reference key to original sale. The join to sales is "sales.physkey = salelog.physkeys". This field can potentially have duplicates
LaneSid	long		102/E	Original sale id on the source lane.
Dt	datetime		103/s	Date/Time this record was created
Code	long		104/E	A coded number indicating what type of record is being stored 80. A saleline was involved in a return operation 81. A complete sale was returned
Tid	long		107/E	Pos Login Id#
Srcuid	long		109/E	Unique id referencing lane number
LineSeqnce	long		160/E	Saleline sequence number this applies too. Optional, only if required
RelatedSid	long		161/E	Related Saleid

Indexing

❖ A unique primary key should exist on the physkey field.
❖ You may wish to index Physkeys as an alternative for performance reasons.
❖ Stores will typically have a non unique index on LaneSid for performance reasons.

Remarks