RAW TRANSACTION FORMAT |
---|
Overview Overview Record Type Field Fields Common to all Records Common Fields for all Records Common Fields for Transaction Lines Unique Record Types H Records. Transaction Header Records E Records. Transaction End Record P Records. Product Sale Records F Records. Finalisation Records A Records. Adjustment Records S Records. Statistic Records Z Records. Z-Read Records U Records. Masterfile Update Records |
Overview |
Transactions processed in SELLmatix are saved as a Unicode Text file where the fields are delimited by commas,
and each record in the file is separated by a carriage return/line feed combination. The name of the transaction file
is tran.csv. Standard .csv files can be read by standard text editors, or read into spreadsheets such as OpenOffice or Excel. There are several lines for each sales transaction including one header line, a line for each item on the sale, a line for each payment toward the sale, and an end sale line. Other lines in the transaction file include statistic lines, Z-Read lines, and product update lines. |
Record Type Field |
The first field in each line of the tran.csv file is a line type field which indicates the type of data
contained in the line. this first field is always 3 characters long and the 3 characters are as follows. Offset 0 contains the posting flag. If this line has been passed to a higher level controller then this field contains a "P", otherwise it contains a <SPACE> character. For example, transaction lines are written by each POS system when the transaction is completed. Initially, this character contains a space. When the transaction file is updated to a controller such as SELLmatix Control, this character is changed to a "P" when the line is acknowledged as processed by SELLmatix Control. Offset 1 contains a general line type flag. For example, a product sold would contain a "P" character, a finalisation (payment) line would contain an "F" and a statistic line would contain an "S" character. Offset 2 contains a line subtype flag. The value of this character depends on the general line type. |
Fields Common to Each Record | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Fields Common to Transaction Records | ||||||||||||||||||||||
|
H Records. Transaction Headers |
There are no record subtypes for transaction headers, and the third digit in the record type field is set the same as the record type so that the record type field for headers is "?HH". There are no fields in header records which are additional to the fields common to all record types. |
E Records. Transaction End |
There are no record subtypes for transaction end records, and the third digit in the record type field is set the same as the record type so the record type field is "?EE". There are no fields in header records which are additional to the fields common to all record types. |
P Records. Product Sale Records | ||||||||||||||||||||||||||||||
Record Subtype The record subtype for a product sale line reflects the way the line item is priced. For an item
sold for a Unit price, the subtype is "U". For items sold by weight from an electronic scale, the record subtype is "W".
For items which have the price encoded in the barcode, such as happens with a Deli Scale where an item is weighed and the scale
produces a barcode label which is affixed to the package, the record subtype is "B". For items where the quantity is supplied by
a Wetstock dispenser such as a Gilbarco Fuel Pump Controller, the record subtype is "T".
|
F Records. Finalise (Pay for) Sale Records | ||||||||||||||||
Record Subtype The record subtype for a finalisation record reflects the finalisation type.
For bankable finalisations, the record subtype contains "B". Bankable finalisations would typically
be used for Cash, Cheques and manual credit card transactions. For Electronic finalisations the subtype field contains "E". Electronic finalisations are typically used where credit cards are processed online, and the proceeds deposited directly to a bank account. For account finalisations, the subtype contains "A". Account finalisations are typically used where the business offers credit to customers, and sends an account statement at regular intervals. Where an account finalisation is used, SELLmatix will have required that the operator select a valid customer that can have sales charged to their account.
|
A Records. Adjustment (non sale) Records | ||||||||||||||||
Adjustments are used to record financial transactions that affect the cash balance in the till, which are not
sales. Examples of this type of item would include cash paid in to the till for float, cash paid out of the
till for purchase of goods, cash paid out of the till to a customer as part of a cash out transaction on a
credit card and so forth. In each case, the balance of the till is affected, but sales are not affected.
Each Adjustment requires a corresponding balance to one of the finalisations, however that balance may occur
in the overall sale total. For example, a customer may buy 5 separate items, take cash out and pay for the
entire transaction by a cheque or credit card. Record Subtype The record subtype for Adjustments reflects the way that the Adjustment changes the balance of the till. For Adjustments where money is paid in the subtype contains an "I". For Adjustments where money is paid out of the till, the subtype contains an "O". For Cash Out to customer the subtype contains a "C". For cents rounding the subtype contains a "R". For Adjustments where an account customer makes a payment to their account with the business, the subtype contains a "A".
|
S Records. Statistic (non sale) Records | ||||||||||||||||||||||||||||||||||
Statistic records are used to supply data to a back office system which would not normally be
used but may have some value in a specialised application. The record subtypes for statistic
records are as follows:
The following fields are available in addition to the fields common to all records:-
|
Z Records. Z-Read Data Records | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Z fields contain the data printed on Z-Read reports which are run. The format of Z Records is different to other records
and most of the fields common to other records do not apply. Z records do not currently contain a subtype, but this may
change in the future. The fields available on a Z transaction are as follows:-
|
U Records. Product Update Records | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
UP Records contain Product Masterfile information for items which have been added "On the Fly" at the Point of Sale
by the operator when they try to sell an item and find that it does not exist. UP Records do not follow the format of other transaction records. The higher level controller, on receipt of an UP record should add the product to the master file. The fields available in UP records are as follows:-
|