The following program description deals with:
This window displays the data of all receipt transactions stored in the system. This program is purely for information. Attempts to save entries will be rejected with the message "Not allowed" (cp. Button Reconfirm).
As long as you do not limit the overview by activating options, the receipt transactions of all companies, branches, operators and terminals will be displayed.
Via the menu item Report-> Receipt Transaction List / Receipt Transaction Survey, you can also have the transactions put out on an output medium of your choice.
Notes:
The following input fields appear in this program:
Number of the company for which the receipt transaction has been carried out.
Number of the branch in which the receipt transaction has been carried out.
Terminal at which the receipt transaction has been carried out.
Every transaction in the terminal system receives its own transaction number. Apart from receipt confirmations, transactions are also functions such as transfers out, float, sign on / off, receipt copies etc. Therefore, the transaction number often differs from the number of the Receipt.
Sequential receipt number; might differ from the Transaction number.
Sequence receipt number of the fiscal unit.
Profit center in which the receipt transaction has been carried out.
Operator who has carried out the receipt transaction.
The turnover of the transaction. Depending on the finance type, the value can be positive or negative.
Number of the shift in which the transaction has been carried out.
Field with firmly defined selection options
The following status can be linked to a transaction in this field.
Click
on graphic for further help with Data
integrity MICROS Retail OSCAR POS.
Day on which the transaction was carried out.
Time at which the transaction was carried out.
Terminal at which the GC was opened.
For every guest check, a GC transaction is opened. The number is displayed here.
The table no. on which this receipt transaction is based. The table no. (from/to) can be entered in report "Transaction report".
The price level (special price) on which the item booking transaction is based. Price levels are maintained in the sub-window Price of the window Item.
Displays the transaction category. Categories are maintained via the program Transaction Types (Parameters -> Misc. Params).
The following categories can be linked to a receipt transaction:
Displays the receipt "status" of the currently displayed receipt transaction.
The following receipt modes are offered for a receipt transaction:
Name English |
Value |
|
Variable UiText |
Technical name |
|
0 |
|
recMode_optn1 |
RmCollectRec |
|
1 |
|
recMode_optn2 |
RmSingleRec |
|
2 |
|
recMode_optn3 |
RmItemisingRec |
|
10 |
|
recMode_optn4 |
R mNoSale |
|
11 |
|
recMode_optn5 |
RmRecAbort |
|
12 |
|
recMode_optn6 |
RmLayedAway |
|
13 |
|
recMode_optn7 |
RmRecalled |
|
14 |
|
recMode_optn8 |
RmGcFinalize |
|
15 |
|
recMode_optn9 |
RmGcManip |
|
16 |
|
recMode_optn10 |
RmCallup |
|
17 |
|
recMode_optn11 |
RmPayIn |
|
18 |
|
recMode_optn12 |
RmPayOut |
|
19 |
|
recMode_optn13 |
RmVoidedLater |
|
20 |
|
recMode_optn14 |
RmExchange |
|
21 |
|
recMode_optn15 |
RmCardCancel |
|
22 |
|
recMode_optn16 |
RmTipReceipt |
|
23 |
|
recMode_optn17 |
RmCOReceipt |
|
24 |
|
recMode_optn18 |
RmCDReceipt |
|
25 |
|
recMode_optn19 |
RmCOTReceipt |
|
26 |
|
recMode_optn20 |
RmExchBonus |
|
27 |
|
recMode_optn21 |
RmQuotation |
|
28 |
|
recMode_optn22 |
RmGcFinalizeVoid
Note: This mode refers to a guest check which was finalised with a payment type and recalled with GCSELECT. If a change is made in a finalised guest check the whole guest check will be voided (=GC finalise void) and a new guest check is stored together with the change.
|
|
29 |
|
recMode_optn23 |
RmAutoFiscVoid |
|
30 |
|
recMode_optn24 |
RmAbortFiscAbort |
|
31 |
|
recMode_optn25 |
RmVoidComm Only with option: Beverage |
|
32 |
|
recMode_optn26 |
RmPetrolPump Only with option: MIGROS |
|
50 |
|
recMode_optn27 |
RmLVoidedLater Only with option: EDEKA Bauhaus |
|
53 |
|
recMode_optn28 |
RmCustInvNBK Only with option: EDEKA |
|
56 |
|
recMode_optn29 |
RmCatCoupon Only with option: CATALINA EDEKA |
|
33 |
|
recMode_optn30 |
RmRetRegAbort Only with option: Kamps |
|
34 |
|
recMode_optn31 |
RmCustomerAbort Only with option: Kamps |
|
57 |
|
recMode_optn32 |
RmAutoReceiptVoid |
|
|
|
recMode_optn33 |
|
Number of the transaction type; maintained via the program Transaction Types (Parameters -> Misc. Params).
Day on which the receipt transaction was opened. The input date only differs from the date if there has been a date change between the opening and the closing of the receipt (guest check).
The total of the time intervals between the closing of the drawer and the opening of the next receipt.
Note:
The total of the time intervals between the opening of a receipt and the payment type confirmation.
When you work with time periods, the number is displayed. Time periods are maintained via the program Time Periods.
When the receipt has been booked on a customer, the customer number is displayed. Customers are maintained via the window Customer.
The counter for invoice (bill) print is stored in this field. If a transaction is printed via button "Print invoice" the number of the next invoice print for this transaction is shown.
If the receipt has been recorded for a customer no. and if a customer card is scanned the number of the customer card is displayed. Customer cards can be linked to a customer with program Customer -> Customer cards .
Number of the type to which the customer has been assigned in the window Customer Type.
Number of the booked credit customers. A customer counter can be activated by use of the parameter Customer Count which is maintained in the window Customer Type.
Depending on the parameter setting (window Customer Type, field: Cust Specifying) the customer sometimes has to enter an individual number within the booking transaction. In this case, this number is displayed in this field.
The no. entry in this field defines the TGC type (tasting/give-away/coupon).
Note:
The appropriate finance type "Coupon" and the correct options should be programmed to allow for tasting, give-away and coupon types to be recorded. When tastings/give away are recorded the appropriate finance type is marked from 1 to 7 in the receipt transaction.
The following shows some examples of recording tasting/give-away and coupons in a beverages supermarket and the options for finance type Coupon
Finance type |
Option |
Yes/No |
Coupon |
Pack |
X |
|
Deposit paid |
|
|
Deposit in branch |
X |
|
Coupon |
|
Finance type |
Option |
Yes/No |
Coupon |
Pack |
|
|
Deposit paid |
|
|
Deposit in branch |
|
|
Coupon |
|
Finance type |
Option |
Yes/No |
Coupon |
Pack |
|
|
Deposit paid |
X |
|
Deposit in branch |
|
|
Coupon |
|
Finance type |
Option |
Yes/No |
Coupon |
Pack |
|
|
Deposit paid |
|
|
Deposit in branch |
X |
|
Coupon |
|
Finance type |
Option |
Yes/No |
Coupon |
Pack |
X |
|
Deposit paid |
|
|
Deposit in branch |
|
|
Coupon |
X |
Finance type |
Option |
Yes/No |
Coupon |
Pack |
|
|
Deposit paid |
|
|
Deposit in branch |
|
|
Coupon |
X |
Finance type |
Option |
Yes/No |
Coupon |
pack |
|
|
Deposit paid |
X |
|
Deposit in branch |
|
|
Coupon |
X |
The delivery note no. is displayed in this field in the same way as it is printed on the customer’s receipt.
Button activated:
Button deactivated:
Button activated:
Button deactivated:
Button activated:
Button deactivated:
Button activated:
Button deactivated:
Button activated:
Button deactivated:
The number of bonus points prior to the booking transaction. The currently received or cashed-in bonus points are not considered here.
Number of points the customer has earned due to his purchase.
Number of bonus points the customer has cashed in within the booking transaction.
No. of deposit receipt which was finalised with <DEPOSITSALE> key. A bottles returned receipt is printed out and can be cashed in later.
Number of the subcustomer of a main customer for whom this recording is intended.
Expiry date for an offer to a customer.
By a click on this button, all receipt transactions stored in the system which have the status "Not confirmed" are selected. Depending on the amount of data, this selection process might take some time. You can view confirmed transactions by activating the option Confirmed and clicking on the Search button (magnifying glass).
If a transaction cannot be confirmed (e.g. because an item or a price list has been deleted in the meantime), the transaction is still written into the database. The button "Confirmed" is deactivated accordingly. You can view the unconfirmed receipt transactions, find out the reason for the non-confirmation and confirm the transaction by use of the button Reconfirm.
The activated option characterizes confirmed transactions (cp. List "Unconfirmed" Receipt Transactions).
If this option is activated, the receipt transaction is a void receipt.
If this option is activated, the takeaway sales function has been preset at the beginning of the receipt transaction.
If this option is activated, the receipt transaction is a deposit receipt.
If this option is activated, the transaction has been carried out in the training mode.
If this option is activated, the receipt transaction is an invoice copy.
If this option is activated, this receipt has been booked on a net price customer.
This finance position is an meal voucher.
Click
onto the graphic for further help with Meal coupons.
If this option is activated, the receipt has been printed via the function "On Call" defined in the window Terminal Type.
If this option is activated, a special VAT rate has been predefined for the receipt by use of the function fSPECVAT. This function can also be related to an Item Position.
This receipt was cashed in.
Note:
Normally deposit returns are finalised with key <DEPOSITSALE>. When the
receipt is cashed in these receipts are coded subsequently with "Deposit
cash in".
If this button is active a special price level was predepressed with key <LEVGE>.
MICROS Retail Deutschland GmbH
Salzufer 8
D-10587 Berlin
-Germany-