Card Reader Parameter
The following program description deals with:
By use of this program you can maintain basic data of the parameter records of the card reader in the system, i.e.
insert new records, edit and delete the existing ones. You can also display the
data on the screen for enquiry only.
Via this program, you can define the parameters for
interpreting and processing the data read from the magnetic cards.
It functions as follows:
Any arbitrary magnetic card is drawn through the magnetic
card reader. The system reads all the information of all the tracks (maximum 3)
of the card. The defined parameters interpret the data of each track and
determine how the data is to be processed in the system.
Note:
- The shown internal procedure is
independent of the card type, so parameters can be defined for credit
cards, internal customer cards, operator ID cards for signing on/off, etc.
Credit cards are usually programmed as Payment
type of category "EFT" and in some
cases as "Credit". Setting up of these cards is maintained via Issuer , Clearing Institute, Card type, Card usage etc.. A general description can be found under Credit card
processing. If credit cards are also to be
read in via a swipe reader, this credit card must be programmed as payment
type of category "Cash" (see example under Setting up credit card for
reding via swipe reader.
- However, the function or the event will
depend on the card type and the parameters defined. For example, an
operator can sign on or off directly without entering an operator no..
- If several numbers are to be read in from
one card, each no. must be programmed under its own “Cons.no.”. All
data to be read in must be stored on the same track. This applies even
though all three tracks are read.
At the end of this program description, there are two
application Examples.
This paragraph will provide a short overview over the
options available for updating these Basic Data.
Just like in almost any other program:
- The Input Mask may
be different in your MICROS Retail OSCAR POS program depending on the set-up of the
application. In some cases some Data Fields may be missing.
- Some input fields may contain default
values or defined selection options; these cannot be updated.
- The input mask contains some fields that
require an entry and others in which entries are optional.
- If the data record is updated via
multi-page input masks, go to the Dialog Window by
clicking on the appropriate buttons with <Mouse key 1>.
- The same procedure applies to call up
another update program from this program.
- In some cases you may find that so-called
"Switches" which - depending on the default - can be activated
or deactivated with <Mouse key 1>. Activated switches are identified
by their dark color, deactivated switches are lighter-colored.
Permitted input range: numeric, 1 - 9999
Select the number of the company for which the card reader
parameters are to be defined.
If you do not know the number, you can also select the data
record via the Search Function.
The company data is maintained with the Company maintenance program.
Permitted input range: numeric, 1 - 9999
Select the number of the branch for which this program is
carried out.
If you do not know the number, you can also select the data
record via the Search Function.
Branches are maintained using the program Branch.
Permitted input range: numeric, 1 - 9
Enter the track number of the magnetic card to be defined.
Permitted input range: numeric, 1 - 999
This is an arbitrary number given to the track parameter
defined here. The sequence number identifies the different data read.
Permitted input range: alphanumeric, max 20 characters
Enter an arbitrary descriptive name for the parameter to be
defined.
Permitted input range: numeric, 0 - 99
The basic requirement for processing read-in data is that
the type of card is recognized. The card identification is done via the fields Compare
start position and Compare with. This is particularly important if
several parameterings have been programmed for one track and if this is
important to differentiate between the cards.
Compare with shows the no. of characters with which the card is identified after
the read operation. The start position of the comparison is entered under Compare
from position. Please note that the payment begins with "0". When
the first character is to be read, a "0" should be entered. With credit and EC cards this is the so-called start character, the
first "readable" (= relevant) no. is in Position1.
Example:
Credit cards are programmed for your company and these all begin with
characters XYZ. In this case, 0 should be entered under Compare
from position and XYZ under Compare with.
Permitted input range: alphanumeric, max 14 characters
This parameter works together with the previous parameter Compare Start Position.
It is possible that several parameters are defined for the
tracks of the magnetic card. In order to recognize and process the respective
parameters, a proof field is used. The data entered in this Compare with
field has to be present on the track at the position defined in the field Compare Start Position.
Note:
- The layout of the track has to be known
under all circumstances. Otherwise, the comparision is not possible.
Permitted input range: alphanumeric, max 20 characters
Enter the code of the key to be used for processing the
data read. The key to be selected depends on the function to be performed. It
does not have to be a pure financial posting function. For example, the key
code <COMES> for waiter comes can also be entered, as well as a
key code for payment type.
A listing of the key codes can be found in the sections
- Key Codes
(sorted in alphabetical order of the key codes)
- Key Codes
(German) (sorted in alphabetical order of the German description of
the codes)
- Key Codes
(English) (sorted in alphabetical order of the English description of
the codes).
The MICROS Retail OSCAR POS application recognises the following keyboard
events (XXX stands for the code name):
- XXX
A key code without prefixed f and/or
n implies that neither fixed data nor manual data or data
read in is transferred. Example: the item search key SEARCHART.
- fXXX
The prefixed f stands for fixed
and implies that firmly defined data is transferred. Example: With payment
type 1 1 would be entered under Simulated key fPM
and under Std.device data 1.
- XXXn
This entry only applies if the system expects another no. (not a firmly defined) in addition to the key
entry. Example: To record a customer enter the CUSTOMERn. The
system is informed of the customer no. either manually or from reading a
card. There will be no entry under Std.device data. Note: The fact
that n is added does not imply that the number entry does not have
to be made after depression of the key during the recording. The
recording sequence remains unchanged.
- fXXXn
Simultaneous transfer of fixed and non-fixed
data does not happen very often. Example: A key is assigned to the fixed
Department 10. fDEPT is entered and 10 is
entered under Std.device data 10. During the recording the
system then requests entry of the price.
Permitted input range: numeric, 0 - 99
Field 1 corresponds to the keys device data, e.g. preset
item no.. This field is not required often, see example Credit payment.
Please note that count starts at "0" during
entry. If field 1 begins with the 5th character, 4 should be entered
here.
Permitted input range: numeric, 0 - 99
Number of places of the first field.
Permitted input range: numeric, 0 - 99
Field 2 defines the character sequence of the card which
would follow as keyboard entry if the card was not read. Please note that
counting begins at "0". If field 2 begins with the 20th
character, 19 should be entered here.
Example:
As this is a customer card fCUSTOMER has been entered under Simulated
key; this corresponds to key Customer preset. If this were a manual
recording, the customer no. would now be entered. The customer no. is stored on
the magnetic stripe. It begins at the 4th character and has 6 digits
in length. In this case, the operator would enter 3 under Offset
Field 2 and 6 undr Length field 2. The system would then
interpret positions 4 to 9 as the customer no..
Permitted input range: numeric, 0 - 99
Number of places of the second field.
Permitted input range: alphanumeric, max 20 characters
In this field, you can enter the key device data which
corresponds to the keyboard event entered in the field Simulated Key. "1" would be entered here
for the payment type 1 (cash) after entering fPM (payment type) under
"Simulated key".
- Cashier sign-on
Tre cashiers/waiters are to sign on using a
magnetic card. These sign-on cards always begin with 111 followed
by the cashier no. (here: 10); track 1.
The layout is as follows:
Track: 1
Compare from pos.: 9
Compare with: 111
Simulated key: WAITERn
Offset Field 2: 4
Length Field 2: 2.
- Customer number
In your sales terminal system, the magnetic card is used exclusively for
reading a customer number. Example: All customer cards begin with 333
followed by the 5-digit customer no. This number is stored in the third
track of the magnetic card.
Track: 3
Compare from pos.: 0
Compare with: 333
Simulated key: CUSTOMERn
Offset Field 2: 4
Länge Field 2: 5
- Credit
card with simultaneous payment settlement
As from MICROS Retail OSCAR POS version 1.5 d credit payment by a customer can be
completed in one read operation with customer no. and finance type no..
The finance type is defined in field 1, the customer no. in field 2.
Example: All customer cards begin with 333 followed by a 5-digit customer
no.. The no. of the finance type "Credit sale" is in Position 9
(= 10th character). The numbers are on track 3 of the magnetic
card.
Track: 3
Compare from pos.: 0
Compare with: 333
Simulated key: CREDSALEn
Offset Field 1: 9 (Finance type no.)
Length Field 1: 1 (Finance type no.)
Offset Field 2: 3 (Customer no.)
Length Field 2: 5 (Customer no.)
- Offline debit
In the system debits are programmed as payment
type no. 5. The card layout is as follows:
Track: <Number of track>
Compare from pos.: 0
Compare with: <Code of card>
Simulated key: fPM
Offset and length of fields 1 and 2 remain free
Std. Device data: 5.
- Cheque payment:
Read in number from card and manual number entry
An example can be found under Number
entry for cheque payments
- Credit card reading:
Read in no. of card via MDR and manual number entry
An example can be found under Set up of credit card for reading via MDR.
MICROS Retail Deutschland GmbH
Salzufer 8
D-10587 Berlin
Germany