As an extra to the normal returns recordings via the Key event <RET> with which any item can be recorded as a return, MICROS Retail OSCAR POS offers the option of controlled returns recording via key event <RETSEL>.
"Controlled returns sales" via function <RETSEL> ensures that items which have already been recorded as returns can be recorded again as returns.
When function <RETSEL> is called up the operator is prompted to enter the transaction no. (24 digits as per the EAN parameter for SCANNEDREC) or to scan the bar code. This calls up the receipt which has already been recorded in the past. The payment type of the original recording is shown on the terminal when key event <RETPAY> is activated during "Controlled returns sales".
Parameter settings in MICROS Retail OSCAR POS:
The option "Bar code on receipt" or "Transaction ID on receipt" must be set in program Application -> Parameter -> Misc.Parameters. -> Terminaltype -> Details 2 for "Controlled returns sales" to ensure that a transaction no. can be entered or the bar code can be scanned.
In function "Controlled returns sales" receipts of other branches can be released for returns of this type. Therefore, the transaction no. must contain the branch no. which issued the receipt so that this transaction can be clearly marked. This option can be activated or deactivated in program Application -> Organisation -> Branch -> Details1 "No. branch no. on receipt barcode". The transaction no. or the bar code will be extended by the 6-digit branch no. with leading zero if this option is deactivated (24 digits). This should be included in the settings for the EAN parameter with function "SCANNEDREC" in program Branch.
To ensure that receipts from other branches can be used with "Controlled returns sales" the option "Retsel via Head Office" should be activated in program Application -> Organisation -> Company -> Details.
Note:
This option should only be used for controlled returns sales if returns are to
be recorded for receipt transactions from other branches. It must also be
ensured that head office permanently receives status, statistics and
transaction data from all connected branches (sub-installations) (see Realtime data transfer).
Key event <RETSEL> can only be executed outside a receipt transaction. If the transaction no. entered or if the bar code scanned for the recorded receipt cannot be found in the database the program returns automatically to normal returns recording (RET) after <ST>. The key event is not accepted. The only deviation in mode "Controlled returns sale" possible is if the current operator is in training mode and a receipt has been recorded in training mode.
After activation of key <RETSEL> and entry or scanning of the transaction no. the positions of the receipt are displayed in the window (see Transactions of type Returns).
The exceptions are positions which are not displayed: (see Application -> Sales -> Receipt transaction)
The operator has to enter the item price for returns for the following receipt positions:
After activation of the <RETSEL> key and entry or scanning of the transaction no. of a receipt from another branch the system tries to read the transaction data from the database (see Retsel via Head Office).
If the receipt with the matching transction no. is found the Returns recording can be continued.
Note:
Reading receipts which were issued by another branch assumes that the database
of the linked main installation can be read and that the data in the server
database of head office has the up-to-date data of the branches (see Realtime data transfer).