Sharp UP-3515 (serv.man5) Service Manual ▷ View online
Page 4 - 6
9.
Registration of different PLUType combinations together with SideablePLU.
With ROM Version V1.30 the SIDEABLE PLU type has been introduced. Even the registration of
SIDEABLE PLU’s in combination with other types of PLU (e.g. LINK, COMBO, CONDIMENT) underlay
to certain restrictions, they were possible sometimes. This could result in wrong print out of the
registration. In the following, we summarize such restrictions and add the new ones which are
introduced with this new ROM Version.
Neither a “SIDE” nor a “SIDE W.ROLLUP” PLU can be registered individually. They are belonging
to a “SIDEABLE” PLU, but it is possible to assign them to a Link or Combo PLU. In such kind of
registration, they will be treated as normal articles.
Even a “SIDEABLE” PLU can be part of a Condiment, Link or Combo PLU, they will be registered
as a normal article. It will loose its SIDEABLE property. It is neither possible to register a “SIDE” nor
a “SIDE W.ROLLUP” after such a registration.
After the registration of a “SIDEABLE” PLU, up to 30 SIDE PLU types/Free Texts which should
belong to this leading PLU can be registered.
A registration of a “SIDE” or a “SIDE W.ROLLUP” PLU after a SIDEABLE PLU registration which is a
CondimentTied is not possible.
A Sideable PLU may have a Condiment Link.
Following registration is possible:
Sideable PLU with Condiment Link
Condiment Tied(s)
Side(s) or SideRU(s)
If the Sideable PLU will be voided, all of the Condiment Tied(s), Side(s) and SideRU(s) will be voided
as well.
The Sideable PLU with all of its Side(s)/SideRU(s) must belong to the same PLU Group (SortGroup).
A CondimentTied can be a Sideable, but if such a Condiment Tied is registered, it will loose its
Sideable property.
Side/SideRU must not be a LeadingCondiment (must not have a Condiment Link).
Side/SideRU must not be a CondimentTied.
Side/SideRU must not be a LeadingLink or LeadingCombo PLU.
A LinkTied or ComboTied should not be a Sideable, Side or SideRU. If such a Tied is registered, it
will loose its Side property.
SIDEABLE PLU’s in combination with other types of PLU (e.g. LINK, COMBO, CONDIMENT) underlay
to certain restrictions, they were possible sometimes. This could result in wrong print out of the
registration. In the following, we summarize such restrictions and add the new ones which are
introduced with this new ROM Version.
Neither a “SIDE” nor a “SIDE W.ROLLUP” PLU can be registered individually. They are belonging
to a “SIDEABLE” PLU, but it is possible to assign them to a Link or Combo PLU. In such kind of
registration, they will be treated as normal articles.
Even a “SIDEABLE” PLU can be part of a Condiment, Link or Combo PLU, they will be registered
as a normal article. It will loose its SIDEABLE property. It is neither possible to register a “SIDE” nor
a “SIDE W.ROLLUP” after such a registration.
After the registration of a “SIDEABLE” PLU, up to 30 SIDE PLU types/Free Texts which should
belong to this leading PLU can be registered.
A registration of a “SIDE” or a “SIDE W.ROLLUP” PLU after a SIDEABLE PLU registration which is a
CondimentTied is not possible.
A Sideable PLU may have a Condiment Link.
Following registration is possible:
Sideable PLU with Condiment Link
Condiment Tied(s)
Side(s) or SideRU(s)
If the Sideable PLU will be voided, all of the Condiment Tied(s), Side(s) and SideRU(s) will be voided
as well.
The Sideable PLU with all of its Side(s)/SideRU(s) must belong to the same PLU Group (SortGroup).
A CondimentTied can be a Sideable, but if such a Condiment Tied is registered, it will loose its
Sideable property.
Side/SideRU must not be a LeadingCondiment (must not have a Condiment Link).
Side/SideRU must not be a CondimentTied.
Side/SideRU must not be a LeadingLink or LeadingCombo PLU.
A LinkTied or ComboTied should not be a Sideable, Side or SideRU. If such a Tied is registered, it
will loose its Side property.
10.
Bill Separation in combination with item split.
If an item is split during the Bill Separation operation (a bottle of wine for two people), it was
possible that a zero amount for the split items were transferred to the target GLU. With this
version, the correct amount for the items will be split.
possible that a zero amount for the split items were transferred to the target GLU. With this
version, the correct amount for the items will be split.
Page 5 - 6
11.
CCD error at TimeOut of Employee.
Following setting have been made at the ECR:
‘Employee working time entry’ is set to COMPULSORY (SRV #987A).
‘Automatic Clerk SignOn after TimeIn/BreakOut’ and ‘Automatic Clerk SignOff after TimeOut’ and
‘Employee and Clerk relationship is removed (i.e. Clerk Z is done)’ is set to YES (SRV #987B).
‘Terminal CCD’ is set to YES (SRV #988D).
Under some circumstances, i.e. after a Service Reset, the TimeOut operation of an Employee after
the GeneralZ report has been carried out will result in the error ‘CCD NOT DONE’, even the CCD
entry has been made. This error is corrected at this version.
‘Employee working time entry’ is set to COMPULSORY (SRV #987A).
‘Automatic Clerk SignOn after TimeIn/BreakOut’ and ‘Automatic Clerk SignOff after TimeOut’ and
‘Employee and Clerk relationship is removed (i.e. Clerk Z is done)’ is set to YES (SRV #987B).
‘Terminal CCD’ is set to YES (SRV #988D).
Under some circumstances, i.e. after a Service Reset, the TimeOut operation of an Employee after
the GeneralZ report has been carried out will result in the error ‘CCD NOT DONE’, even the CCD
entry has been made. This error is corrected at this version.
12.
Secured Reports.
During the execution of “Secured Reports”, the data of the following files were saved and cleared
automatically:
Hourly, Employee Transaction, GT, Customer Sales, CCD Shift, Employee Time, Open GLU,
Z Counter, Closed Transaction, Entry Mask files (Universal 120), TLOG and Electronic Journal.
Unfortunately, for “Employee Time” and “Entry Mask files” the data were not cleared, even they
have been saved successfully onto SD Card. By using the new ROM Version also these data are
cleared.
automatically:
Hourly, Employee Transaction, GT, Customer Sales, CCD Shift, Employee Time, Open GLU,
Z Counter, Closed Transaction, Entry Mask files (Universal 120), TLOG and Electronic Journal.
Unfortunately, for “Employee Time” and “Entry Mask files” the data were not cleared, even they
have been saved successfully onto SD Card. By using the new ROM Version also these data are
cleared.
13.
Secured Reports in InlineSystem.
Because the reports in an InlineSystem will be taken at the Master, the “Secured Reports” feature
introduced at V1.50, is advisable at the Master only. The “Secured Reports” feature was not
available at the Satellite.
Beside of the main function of the “Secured Reports” feature, it is also possible to get i.e. the
Electronic Journal data saved onto the SD Card. Due to it is not possible to receive and store the
Electronic Journal data from a Satellite at Master side, the “Secured Reports” feature is now
available at the Satellite as well.
If the “Secured Reports” feature is enabled at the Satellite it will save the Electronic Journal data
and the All RAM Backup respectively the PGM Backup according to their PGM setting onto the
local SD Card.
Furthermore the function key “EOD_READY_CHECK” is also enabled at the Satellite in order to
check if the machine is in a status that the “Secured Reports” can be carried out.
In case of an Inline System with a BackupMaster while the BackupMaster has taken over the role
of the Master (due to Master down), the BackupMaster still behaves like the Satellite. Only the
Electronic Journal as well as PGM Backup and ALL RAM Backup, according to their setting, will be
saved on SD Card.
introduced at V1.50, is advisable at the Master only. The “Secured Reports” feature was not
available at the Satellite.
Beside of the main function of the “Secured Reports” feature, it is also possible to get i.e. the
Electronic Journal data saved onto the SD Card. Due to it is not possible to receive and store the
Electronic Journal data from a Satellite at Master side, the “Secured Reports” feature is now
available at the Satellite as well.
If the “Secured Reports” feature is enabled at the Satellite it will save the Electronic Journal data
and the All RAM Backup respectively the PGM Backup according to their PGM setting onto the
local SD Card.
Furthermore the function key “EOD_READY_CHECK” is also enabled at the Satellite in order to
check if the machine is in a status that the “Secured Reports” can be carried out.
In case of an Inline System with a BackupMaster while the BackupMaster has taken over the role
of the Master (due to Master down), the BackupMaster still behaves like the Satellite. Only the
Electronic Journal as well as PGM Backup and ALL RAM Backup, according to their setting, will be
saved on SD Card.
14.
Secured Reports with a folder name length of 8 characters.
If a folder name consists out of 8 characters, it will not be taken over correctly sometimes. With this
version, the given folder name will be set correctly although it has the max. of 8 characters.
version, the given folder name will be set correctly although it has the max. of 8 characters.
Page 6 - 6
15.
Online function (Clerk ZReport) in relation to the ECR status.
16.
Leaving the Diagnostic mode may result in an error.
If the machine has been powered off and on again, the error ‘LACKING MEMORY’ may occur
when leaving the Diagnostic mode. At this version, this error will not be shown anymore.
when leaving the Diagnostic mode. At this version, this error will not be shown anymore.
17.
Stacked Reports.
A Stacked Report called at the Satellite shows a “strange” behaviour like no cut between the
individual reports or even not printed correctly at all. This is corrected.
individual reports or even not printed correctly at all. This is corrected.
Page 6 - 6
15.
Online function (Clerk ZReport) in relation to the ECR status.
16.
Leaving the Diagnostic mode may result in an error.
If the machine has been powered off and on again, the error ‘LACKING MEMORY’ may occur
when leaving the Diagnostic mode. At this version, this error will not be shown anymore.
when leaving the Diagnostic mode. At this version, this error will not be shown anymore.
17.
Stacked Reports.
A Stacked Report called at the Satellite shows a “strange” behaviour like no cut between the
individual reports or even not printed correctly at all. This is corrected.
individual reports or even not printed correctly at all. This is corrected.
Display
