Salelog Database Table

Records details of major events that occur relating to a single sale. This information is often interesting to auditors or support staff

Distrbuted Access: Lanes( insert edit )

Fields

physkey

#100, Datatype: String 44 bytes
Unique key assigned to this record

physkeys

#101, Datatype: String 44 bytes
Reference key to original sale. The join to sales is "sales.physkey = salelog.physkeys". There can be multiple rows in this table with the same Physkeys value.

lanesid

#102, Datatype: Integer
Original sale id on the source lane.

dt

#103, Datatype: DateTime
Date/Time this record was created

code

#104, Datatype: Integer
A coded number indicating what type of detail is being stored

Possible Values

Value	Description
20	Sale was parked
21	Sale was un-parked (from P2016)
22	Receipt was reprinted manually from PastSales to a print queue
23	During Pos restart an eftpos in progress sale was rechecked
24	During Pos restart a normal sale was reactivated
25	During Pos restart a normal sale, marked autocomplete, was finished normally
26	During Pos restart a normal sale, marked autocomplete, was voided
27	During Pos restart a zero value sale was voided
28	During Pos restart a sale was killed due to "kill all sales" being enabled
30	Product return screen was invoked for this sale (from P2158)
31	Product return was completed for this sale (from P2158)
32	Message to user while sale active
33	Receipt was emailed manually from PastSales
34	Different versions of sale detected. User asked for help
35	System location was changed during startup due to a restart sale
36	Receipt printed or emailed
37	Sale set as finalisation pending
50	A Photo reference taken when the first item was sold. param1 contains the camera number and fileref contains the name of the original capture file
80	Status change advice message being sent to another application
81	Saleline edit via API
82	Picking fields edit via API
83	Receipt template emailed as PDF
100	A photo was captured as a prepay/SVC card was used to pay a sale
101	A photo was captured as a prepay/SVC card was topped up or purchased
200	Status of network transmission to offsite.
201	Error from EFTPOS provider during recovery processing
202	A subscreen was invoked
203	Fatal Error from EFTPOS provider user prompted for payment status
300	Completed Sale Edit
301	Completed Saleline Edit
302	Sale removed from account A and moved to account B
303	Date of sale manually changed during entry
304	Customer on sale changed as original customer deleted/merged
401	Completed Payment Edit
800	Return reason prompt was cancelled multiple times
2000	Saleline was removed from sale (from P2189)
3001	Payment was removed from sale (from P2189)
10002	Sale was voided. Param1 contains the source of the delete request

param1

#105, Datatype: Integer
General purpose value. Meaning depends on code value

fileref

#106, Datatype: String
General purpose value. Meaning depends on code value

tid

#107, Datatype: Integer
Pos Login Id#

ridutc

#108, Datatype: Integer

srcuid

#109, Datatype: Integer
Unique id referencing lane number

errormessage

#110, Datatype: String
Error message. If the operation encountered an unexpected error the details of the error might be recorded here.

errorcode

#111, Datatype: Integer

Param2

#112, Datatype: Money/Currency
General purpose amount. Exact contents depends on code field

param3

#113, Datatype: Integer

physkeyother

#114, Datatype: String 44 bytes
A physkey reference to another record.

rvel

#115, Datatype: Double
Internal system field used for replication, ignore this field.