Sharp UP-3500 (serv.man21) Service Manual ▷ View online
Page 9 14
6.
Improvement of the SCM(+) / SCM() function.
With the existing SRV parameter #907A, SCM input can be set to compulsory.
In case this parameter is set i.e. to 6 (compulsory for all Clerks) one Clerk has to make the SCM
input in order to perform the SCM entry for all Clerks.
In previous versions, in case of SCM(2), the ECR is comparing the SCM(2) amount against the
individual Clerk totalizer of that Clerk who wants to make the SCM(2). If the Clerk who wants to
make the SCM(2) differs from that Clerk who makes the SCM(+), it is possible to make a SCM(2) of
only that amount which is less or equal to the turnover of the Clerk. In this case, the previous
entered SCM(+) amount by the other Clerk is disregarded. This has been changed at this version.
If SRV parameter #907A is set to +1 (1 or 5), the ECR compares the SCM(2) amount against the
individual Clerk totalizer. This is like in the previous version.
If SRV parameter #907A is set to +2 (2 or 6), the ECR compares the SCM(2) amount against the
CA/CHK ID totalizer of the terminal. This has been changed compared to the previous version.
If SRV parameter #907A is set to 0 or 4 (SCM input is not compulsory), the new below SRV
parameter #991A will be considered.
If SRV parameter #991A is set to +4, the ECR compares the SCM(2) amount against the CA/CHK ID
totalizer.
If SRV parameter #991A is set to 0, the ECR compares the SCM(2) amount against the individual
Clerk totalizer.
Because of the additional checking of the new SRV parameter, it is possible to set up the ECR like
with the previous ROM version.
In case this parameter is set i.e. to 6 (compulsory for all Clerks) one Clerk has to make the SCM
input in order to perform the SCM entry for all Clerks.
In previous versions, in case of SCM(2), the ECR is comparing the SCM(2) amount against the
individual Clerk totalizer of that Clerk who wants to make the SCM(2). If the Clerk who wants to
make the SCM(2) differs from that Clerk who makes the SCM(+), it is possible to make a SCM(2) of
only that amount which is less or equal to the turnover of the Clerk. In this case, the previous
entered SCM(+) amount by the other Clerk is disregarded. This has been changed at this version.
If SRV parameter #907A is set to +1 (1 or 5), the ECR compares the SCM(2) amount against the
individual Clerk totalizer. This is like in the previous version.
If SRV parameter #907A is set to +2 (2 or 6), the ECR compares the SCM(2) amount against the
CA/CHK ID totalizer of the terminal. This has been changed compared to the previous version.
If SRV parameter #907A is set to 0 or 4 (SCM input is not compulsory), the new below SRV
parameter #991A will be considered.
If SRV parameter #991A is set to +4, the ECR compares the SCM(2) amount against the CA/CHK ID
totalizer.
If SRV parameter #991A is set to 0, the ECR compares the SCM(2) amount against the individual
Clerk totalizer.
Because of the additional checking of the new SRV parameter, it is possible to set up the ECR like
with the previous ROM version.
Checking of SCM(2) amount
(only if 907A=0 or 4)
GLU key status
after Media & Bill
9912A Default
Setting 1
0
√
Setting 2
1
against individual Clerk
totalizer
Setting 3
2
Setting 1
4
Setting 2
5
against
CA/CHK ID totalizer
Setting 3
6
Entry of SCM after registration
SCM compulsory
9072A Default
non compulsory (refer #991A)
0
√
for individual Clerk (Cashier)
1
disable
for all Clerks (Cashiers)
2
non compulsory (refer #991A)
4
for individual Clerk (Cashier)
5
enable
for all Clerks (Cashiers)
6
Page 10 14
7.
Adjustable print outs for Customer registration.
To simplify the print out for Customer registration two new SRV parameters have been introduced
at the new version. According to their setting the print out of Customer registrations are changed.
at the new version. According to their setting the print out of Customer registrations are changed.
Skip PBAL on
Charge RCPT&BILL
Skip
PBAL/CHARGE/NBAL
on Media RCPT/BILL
9902C Default
NO
0
√
NO
YES
2
NO
4
YES
YES
6
Examples:
Customer registration finalized by Charge
If #990C is set to +4, the line “PBAL” and the 2
nd
“CHARGE” line will not be printed neither on the
receipt nor on the bill, if the Customer registration is finalized by CHARGE.
previous layout
new layout
Customer registration finalized by media
If #990C is set to +2, the lines “PBAL”, “CHARGE” and “NBAL” will not be printed neither on the
receipt nor on the bill, if the Customer registration is finalized by any MEDIA.
previous layout
new layout
Page 11 14
8.
Change of the VAT Shift function.
In the current specification VAT Shift is working as follows:
A PLU assigned to VAT1 will shift to VAT2. A PLU assigned to VAT1 & VAT3 will stay on VAT1.
The current specification and the VAT Shift toggle specification have to be kept.
For shifting from VAT2 to VAT1 the entry syntax for VAT shift is changed.
With the new version, a number input prior to the VAT shift key press is possible. As for the
number input, only “1” is allowed. When ever “1” has been entered, all items which are assigned
to VAT2 will be shifted to VAT1. If VAT2 and VAT3 are assigned to an item, VAT shift entry is
ignored for this item.
Following new key entry sequences are possible.
For VAT shift per transaction.
a) VAT shift transaction at the start of the transaction
1 [VATSFT TRANS.] item registration(s)
b) VAT shift transaction at the end of the transaction
item registration(s) 1 [VATSFT TRANS.]
For VAT shift per item.
c) VAT shift item
1 [VATSFT ITEM] item registration
reset VAT shift status after one item registration automatically
For VAT shift toggle.
d) VAT shift toggle
1 [VATSFT TRANS.] item registration(s)
reset VAT shift status after pressing VATSF TRANS. again
Remark:
2 VAT shift by Clerk will not support this new feature.
2 The VAT shift change and VAT shift delete totalizers will only be updated in case of shift from
VAT1 to VAT2, but not in case of shift from VAT2 to VAT1.
2 The VAT shift toggle function, implemented in version V1.22 (SRV #921C +4), supports this new
feature.
In case VAT ITEM SHIFT,
Link Tied’s will not be shifted, but kept their original assignment.
Combo Tied’s will be shifted.
Condiment Tied’s will not be shifted.
In case VAT TRANS SHIFT,
Link Tied’s will be shifted.
Combo Tied’s will be shifted.
Condiment Tied’s will be shifted.
A PLU assigned to VAT1 will shift to VAT2. A PLU assigned to VAT1 & VAT3 will stay on VAT1.
The current specification and the VAT Shift toggle specification have to be kept.
For shifting from VAT2 to VAT1 the entry syntax for VAT shift is changed.
With the new version, a number input prior to the VAT shift key press is possible. As for the
number input, only “1” is allowed. When ever “1” has been entered, all items which are assigned
to VAT2 will be shifted to VAT1. If VAT2 and VAT3 are assigned to an item, VAT shift entry is
ignored for this item.
Following new key entry sequences are possible.
For VAT shift per transaction.
a) VAT shift transaction at the start of the transaction
1 [VATSFT TRANS.] item registration(s)
b) VAT shift transaction at the end of the transaction
item registration(s) 1 [VATSFT TRANS.]
For VAT shift per item.
c) VAT shift item
1 [VATSFT ITEM] item registration
reset VAT shift status after one item registration automatically
For VAT shift toggle.
d) VAT shift toggle
1 [VATSFT TRANS.] item registration(s)
reset VAT shift status after pressing VATSF TRANS. again
Remark:
2 VAT shift by Clerk will not support this new feature.
2 The VAT shift change and VAT shift delete totalizers will only be updated in case of shift from
VAT1 to VAT2, but not in case of shift from VAT2 to VAT1.
2 The VAT shift toggle function, implemented in version V1.22 (SRV #921C +4), supports this new
feature.
In case VAT ITEM SHIFT,
Link Tied’s will not be shifted, but kept their original assignment.
Combo Tied’s will be shifted.
Condiment Tied’s will not be shifted.
In case VAT TRANS SHIFT,
Link Tied’s will be shifted.
Combo Tied’s will be shifted.
Condiment Tied’s will be shifted.
Page 12 14
>>> Changes / Improvements / Corrections <<<
9.
SystemXReports can not be taken in case of TerminalCCD.
Even the General Z report has been carried out at every machine in an Inline System, the System X
reports is not possible, if Terminal2CCD is active. This has been corrected.
reports is not possible, if Terminal2CCD is active. This has been corrected.
10.
Lost of Name&Address by making a normal registration to a GLU registration.
In case a normal registration will be transferred to a GLU registration, an already assigned
Name&Address to this GLU will be lost. With this version, the assigned Name&Address is still
assigned to the GLU.
Name&Address to this GLU will be lost. With this version, the assigned Name&Address is still
assigned to the GLU.
11.
Reset of GLU key colour by Memory Initialize.
The colour of the GLU key has not been set to the programmed “GLU KEY COL DEF” in case of
Memory Initialize, but to “Black and White” colour. This has been corrected. Now the colour will
be set according to the programming.
Memory Initialize, but to “Black and White” colour. This has been corrected. Now the colour will
be set according to the programming.
12.
Pint Text after PLU range programming.
For the PLU Pint Text, a text with more than 3 characters has been programmed. After the PLU
range programming, were for “OPERATION” was set to “MAINTENANCE”, the Pint Text is garbled.
This has been corrected.
range programming, were for “OPERATION” was set to “MAINTENANCE”, the Pint Text is garbled.
This has been corrected.
13.
Orderman with TAX system.
The system is set up for the TAX system by setting SRV parameter #901B to 0. In case of the
Orderman is requesting the Subtotal by pressing on “Subtot”, only the Net amount, without the
TAX amount, is displayed. Also in case of finalizing the transaction by a press on “Bill”, only the
Net amount was displayed. With this version, by carrying out the above mentioned functions, the
transaction amount including the TAX amount will be shown at the Orderman.
Orderman is requesting the Subtotal by pressing on “Subtot”, only the Net amount, without the
TAX amount, is displayed. Also in case of finalizing the transaction by a press on “Bill”, only the
Net amount was displayed. With this version, by carrying out the above mentioned functions, the
transaction amount including the TAX amount will be shown at the Orderman.
14.
Orderman and small tender amount at the ECR.
Overlapped clerk is activated. While the ECR shows small tender amount, the Orderman send a
registration. Because of the ECR is not “free” the Orderman receive an error and will disregard the
registration. With this new ROM version, the Orderman will receive a busy. Now the registration
will not be disregarded but the Orderman tries to synchronize after a certain time again.
registration. Because of the ECR is not “free” the Orderman receive an error and will disregard the
registration. With this new ROM version, the Orderman will receive a busy. Now the registration
will not be disregarded but the Orderman tries to synchronize after a certain time again.
15.
KP Hold&Go with tender amount.
If a transaction is finalized with tender amount, but there are still some not printed articles, they are
not printed on the KP, regardless if the transaction is a GLU or a normal –transaction. This is
corrected.
not printed on the KP, regardless if the transaction is a GLU or a normal –transaction. This is
corrected.
16.
Closed Transaction with Bill and Bill number.
Under some circumstances, it could happen that a bill of a recalled Closed Transaction got a new
bill number. With this version the reprinted Bill has the original bill number.
bill number. With this version the reprinted Bill has the original bill number.
17.
Inline system with Backup Master and Master down.
If in an Inline system with activated overlapped clerk function the Master is down, it is not possible
to make a clerk sign on at the Backup Master anymore. In this case it is also not possible to make
the “DECLARE MASTER & STOP DB UPDATE” troubleshooting job code at the Backup Master. This
is corrected. Now, if a clerk tries to make a sign on at the Backup Master while the Master is down,
the message “MASTER DOWN” is displayed. Afterwards the entry of a manager code is required
and the clerk will be signed on. Now the troubleshooting job code can be carried out.
to make a clerk sign on at the Backup Master anymore. In this case it is also not possible to make
the “DECLARE MASTER & STOP DB UPDATE” troubleshooting job code at the Backup Master. This
is corrected. Now, if a clerk tries to make a sign on at the Backup Master while the Master is down,
the message “MASTER DOWN” is displayed. Afterwards the entry of a manager code is required
and the clerk will be signed on. Now the troubleshooting job code can be carried out.
Click on the first or last page to see other UP-3500 (serv.man21) service manuals if exist.