As@R26WM 7 - End of Day Functions

WebMaster End of Day Functions AS@R 2.6 - Sec.
Web 7
WebMaster Section 7 - End of Day Functions
Contents Page
End of Day Functions........................................................................................................................ 2
6.1 Sytem End-of-Day ......................................................................................................................... 3

Explanation of Terminal Status: ................................................................................................... 5
Terminals ready for EoD .............................................................................................................. 5
Terminal not ready for EoD .......................................................................................................... 5
Checker Settlement Evaluation.................................................................................................... 6
End-of-Day sequence .................................................................................................................. 8
EoD Trouble Shooting ................................................................................................................... 12

At start of End-of-Day................................................................................................................. 12
During End-of-Day ..................................................................................................................... 14
6.2 Reset Points at next EoD ............................................................................................................ 18
6.3 Print EoD Reports ....................................................................................................................... 18

6.3.1 Print EoD Spoolfile................................................................................................................ 18
6.3.2 Print old EoD Spoolfiles ........................................................................................................ 20
6.7 Re-Run EoD ................................................................................................................................ 20
6.8 POS-EoD..................................................................................................................................... 22
***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 1 - 22

-
WebMaster End of Day Functions AS@R 2.6 - Sec. Web 7
End of Day Functions

The standard menu for the End of Day Functions shows the following subitems:
6.1 System End-of-Day This function will initiate the End-of-Day procedure
6.2 Reset Points

at next EoD When The Frequent Shopper module
is implemented, this function will reset the customer points to zero
for the next day.
6.3 Print EoD Reports This function shows the following subitem
Print EoD Spoolfile
Print old EoD Spoolfiles
Print DOS EoD
6.7 Re-Run EoD Due to hardware problems the End-of-Days might have to be
performed as exception at the server. The Re-Run EoD function will
process these End-of-Days at a later date in order to update all files.
6.8 POS-EoD This function can be only started if the Server is set for Auto-End-of-
day (24 hour store). See also AS@R docu Sec. 5 - Cluster Sytem.
Therefore, a higher authorization level is used for this button and has
to be changed when the option for 24 hour is set.
When this button is pressed, an End-of-Day request will be initiated.

-
6.1 Sytem End-of-Day

This function will start the End-of-Day procedure.
The End-of-Day can start after
all Checkers are signed off or settled
other WebMaster terminals have finalized specific functions,
which do not allow the End-of-Day (see lock flags).
The system will check if there are still the process running to apply parameters. If the apply
is still in progress, no other parameters can be exported nor the End-of-Day started.
Click on button 'System-End-of-Day'
If the settings in param_maint.properties are set to export parameters at End of Day, the first
step will check if there are still parameters at POS Server which are not applied yet. The
message Exporting / Transferring parameters to server will be displayed. Only in case the
system will not continue to the next window, because there might be still parameters not applied,
then cancel this and check for the reason.
When the new parameter export can take place, the system will continue to the following screen:
The field Export Date shows when the system should check for any parameter maintenance
with this data or earlier. Parameter files for the POS Server / POS terminals will be created.
Example:
On Saturday 17.02.2007 is the last End-of-Day before Monday morning.
Parameters might have an activation date of 19.02.2007 and should be active on Monday,
19.02.2007.
In this case the Date for export (= next open day) has to be selected for the
Monday 19. 02. 2007.
Change date to next business day

Normally this is the next day which is proposed no change is necessary
except at weekends, holidays etc. date change is necessary
Click on button Start

-
The parameter files will be exported from the data base and sent to the POS Server. These
parameters will be available at the POS terminals at Start-of-Day the next day.
The system will be initialized. When the Core is running, then certain checks will now be
performed by the system if the End-of-Day is possible at this moment.
After the export of parameters, the system will check again, if there are still the process
running to apply parameters. If the parameter apply is still in progress, the End-of-Day
cannot be started immediately. Some time has to be waited, then it will be possible to start
the EoD again.
6.1.1 Automatic Check on POS Lock Status

The EoD can only take place if the End-of-Day was not already started by another Webclient.
This means, if one of the WebMaster terminals has already started the End-of-Day, it cannot be
started twice.
9 Cluster EoD
If a terminal is defective and the locking function cannot be finalized, then the lock can be
released by 4 System Functions / 6 Remove Function Lock.
6.1.2 Automatic Check on POS Terminal Status (Ready for EoD)

All POS terminals will be checked on their status. The POS terminals have to be in signed-
out mode (AC 02), so that the EoD can continue.
The following action codes will be accepted by the End-of-Day procedure and have to be
found for each client in the columns Ready for EoD - Online / WebGM / Defect:
AC 02 = Signed out
AC 87 = Define terminal o.k. the same day
AC 88 = Define terminal o.k. the next day
AC 98 = Define terminal defect
AC 99 = This terminal performed already a short End-of-Day;
e.g. POS in the flower shop which closes earlier.

-
Example:
A checker is still signed-in at POS terminal 011
WebMaster terminal 802 is still in a WebMaster function and not signed out
POS terminal 011 and WebMaster terminal 802 can be informed to close or can be
automatically logged out by pressing the button LogoutWebClients.
This is not possible when the client is performing a GrandMaster function. This has to
be closed locally so that the End-of-Day can be started.
POS terminal 011 has to be signed out at the terminal
The system will check every 5 seconds the status. If someone signs in during at another terminal
during this start, it will be automatically shown in this screen as Not closed.
When all clients are in the blue (online) area the End-of-Day can be started.
The button StartEOD has to be pressed or Alt + S.
Note:
In case the checker is signed out at POS, however, the system is not recognizing the code.
Perform sign in and sign out at the POS terminal and start End-of-Day again.
Explanation of Terminal Status:
Header POS Server number, date and time
Terminals ready for EoD
Online
All POS terminals which worked today must be either in the Online or
in the Defect column.
WebClient
All WebMaster terminals which were online today must be either in the
WebGM or in the Defect column.
Defect
A POS terminal or a WebMaster terminal which had hardware
problems during the day and is shut down, will be shown in the
terminal status as offline. That the terminal data can take part at the
End-of-Day, the terminal must be declared defective. The data of the
POS server will be used for the End-of-Day procedure.
For Define Defective see WebMaster Section 5.
EoD The client is already in End-of-Day (Code 99)
Terminal not ready for EoD
Not closed
The checker/supervisor is still signed in at the POS terminal.
A sign out is required.
Offline
The terminal is either
not within the POS program
is turned off or
is not connected to the LAN
The situation has to be checked and corrected.
If a terminal is defective and therefore turned off, it has to be declared
defective.
For Define Defective see WebMaster Section 5.

-
Files Mismatch
Data mirroring of this terminal to the server is disabled.
Possible reasons are:
The Server has already POS totals and counters and the terminal
totals were reset and are zero. The Reset Control counter of the
Server M_LANxxx.DAT and the POS CMOS do not match.
The Server has more Item Data Capture records than the terminal
itself.
The Release number of the parameters does not match between
Server M_LANxxx.DAT and POS S_REGxxx.DAT.
The M_LANxxx.DAT shows already an AC 90 - 99 for this terminal
and the terminal tries to get online
The EoD Flag is on (M_LANxxx.DAT Status 08) and the terminal
which has not worked before tries to get online
In any of the above cases, the POS terminal has to be shut down, the
WebMaster terminal has to be disconnected and the POS terminal
has to be declared defective for the End-of-Day. Thus the data of the
server will be taken for the EoD procedure.
For Define Defective see WebMaster Section 5 and EoD Trouble

Shooting within this section.
Datatransfer
The terminal total mirroring is currently running.
After some seconds the terminal will change its status.
After all checks are performed and it was proofed that all clients are now ready for the End-of-
Day the End-of-Day can start.
Click on button 'StartEOD' or press Alt +S
Checker Settlement Evaluation
A definition in the core.properties for settlement evaluation allows an additional check on checker
unsettled or settled. The End-of-Day can be stopped at this point and it is the decision of the user
to return to cashier settlement functions.
Continue: This will continue the End-of-Day.
Exit: This will interrupt the End-of-Day and it is possible to perform settlement functions.
Note: An evaluation on Media-Count can be also checked before End-of-Day is performed. The
settings are done in core.properties.

-
Final check on Web-Terminals (Ready for EoD)
A Web-Terminal can be still signed on; e.g. in PLU maintenance etc., when End-of-Day is
started at End-of-Day-Web-terminal.
The system will check the status every <N> seconds. This value is determined within the
core.properties (property: core.eval.delay).
The client can be informed with the button Inform terminals.
The terminal will receive an information:

Example: Message from End-of-Day terminal REG 802 / User 806: Please sign out logout at
12:11. Depending on parameters this will be e.g. within 1 minute.
An automatic logout can be performed by pressing the button LogoutWebClients or Alt + L.
All terminals are now ready for End-of-Day:
End-of-Day will be started automatically after all terminals are ready.
All terminals will be shown in the EOD column and the End-of-Day is started.
Sign-in at another WebClient is possible again, after the End-of-Day is finished.
The End-of-Day is now in progress and performs its steps. When all data and functions are in a
good and normal stage, then the Core will finalize the End-of-Day. It will even continue in the
background, when the browser is stopped.
A progress of the End-of-Day is shown in the progress bar.

-
End-of-Day sequence
The following End-of-Day sequence will be performed automatically:
Seq. # EoD Module Task

1 ApplicationInvoker This module will call batches; e.g. SW-Update
10 CheckerSettlement If cashiers are not balanced during day, this module

will
settle all.
15 CshDefaultPart1 This is an EOD module which should run before

server EOD. This version moves loans of inactive
checkers to next day by doing a float.
16 CshFxFloatPart1 Is an EOD module which should run before server

EOD. This version set a fixed float value for each
cashier on every day.
17 CshDwrMnyPart1 Is an EOD module which should run before server

EOD. This version takes all money from drawer
and set this money as float.
30 PrimaryServer POS Server performes its End-of-Day

Todays IDCs will receive the timestamp
31 EodInfoUpdate Updates the existing EOD entry with the

current EOD timestamp. Creates a new
entry for the next EOD.
32 Backup Server Backup Server performs its End-of-Day
33 Parameters Parameter generations will be renamed

and updated with newer versions of the
POS Server
35 CshDefaultPart2 Is an EOD module which should run after server

EOD. This version moves loans of inactive
checkers to next day by doing a float. The float is
converted to loan for the new day.
36 CshFxFloatPart2 Is an EOD module which should run after server

EOD. This version set a fixed float value for each
cashier on every day. The float is converted into
loan for the new day.
38 IDCUpdate Only if old IDC Update (Rel. 2.0.2) is

enabled (property):
Validate the IDC and sales data which was
applied during the day by the old IDC Update. If the
data is wrong, it is re-applied based on the HOCIDC.

-
39 HocImportModule If IDCs were not updated during day, this

will take care (gm\lan\old HOCIDC.001 is
imported to DB).
40 Reports Creates reports based on data from the

/safe/*.001 files.
41 ArticleDateUpdate
44 ApplicationInvoker This module will call batches;

e.g. SW-Update
45 LoadDatabase Updates the database with report data

from the current day.
90 UserTrackerReset Reset the user tracker to the new AS@R

parameters
95 WebserverBridgeCleaner Free all resources of the Webserver

Bridge used during the End-of-Day.

e.g. SW-Update
110 RetentionModule Function is performed as defined in

property; e.g. 90 days for IDC
118 UserTrackerReset Reset the user tracker to the new AS@R parameters
119 WebserverBridgeCleaner Free all resources of the Webserver Bridge used

during the End-of-Day
120 FinalTask The directories are cleaned up, the

generation change is performed etc.
End-of-Day WebMaster terminal

The terminal which initiated the End-of-Day will show each step of the End-of-Day procedure.
After the EoD is finished the following message will be shown:
Press the Exit button or Alt + X.

-
POST End-of-Day functions
The End-of-Day itself is now finished. There are Post-End-of-Day activities following. This
depends on the settings in eod.properties (completion.shutdown=TRUE,
automatic.execution=FALSE etc.)
The standard performs the following functions:
Stop JRE
Stop database
Save database
The database will be saved depending on the configuration of the system. The batch
\web\mtxwm\upd\DB_SAFE.BAT takes care where it will be saved.
either on Backup-Server in \server\safesql if a Backup-Server is defined or
if Backup Server and Database are on the same PC it will be saved on WebMaster PC
in the directory \web\mtxwm\upd\sql.dat
on Primary Server in \server\safesql if no Backup-Server is defined and the POS Server
software is running in a different PC then the WebMaster or
if POS Server, WebMaster and Database are installed in the same PC the database will
be saved in a different directory \web\mtxwm\upd\sql.dat. However, since it is the same
PC the following batch should be activated and modified:
\web\mtxwm\upd\DB_PRE to DB_PRE.BAT. The example shows that e.g. POS 10 will
be used to safe the DB.
set dest=\\REG010\c$
set dest_path=sql.dat
Thus the database can be saved to a different device within the LAN.
SW-Update will take place to all parts of the system POS terminal, POS Server, WebMaster,
DB if available
Database is started
JRE is started
Login screen will be shown
Login with your operator number and password

-
Other WebMaster terminals

When a sign-in is performed at another WebMaster terminal which is taking part in the End-of-
Day, the following screen is shown:
A login will be only possible after the End-of-Day is finalized.

Click on ok
The login screen will be displayed
Login with your operator number
Also a combination of End-of-Day and e.g. ReRun EoD or System Init is not possible at the
same
time.
POS terminals ready after End-of-Day

After step 20 "POS Server EoD" the POS terminals are in the night program waiting for LU
maintenance.
In the POS display the LU counters will be shown:
Example JavaPOS:
Three fields are available for the lookup maintenance:
new look ups

look up changes
look ups deleted
This night program has to be finalized at the POS terminals with

Transaction Abort
The new day is startet at the POS terminals with

1 POS program.

-
EoD Trouble Shooting
At start of End-of-Day
1. WebMaster terminals are within a function

which has to be finalized before the End-of-Day can be started.
Finalize function and
Retry End-of-Day again
For possible functions see
6.1.1 Automatic Check on POS Lock Status
If the terminal has hardware problems and cannot finalize the function
any more
Go to another WebMaster terminal
Select
5 System Functions
6 Remove Function Lock
Click on check box "Lock Status" to remove status
Click on button "Unlock"
Retry End-of-Day again
2. POS terminals not closed

Sign off cashier / supervisor
3. POS terminals are closed, but show not closed

Sign in cashier and sign out again at the same terminal
4. Offline
Check why the terminal is offline and correct the situation
(e.g. not turned on, LAN cable pulled etc.)
If the situation cannot be corrected,

turn off terminal,
declare it defective.
Start End-of-Day again
Call NCR technician
Leave the terminal turned off until it is repaired again.
5. Files Mismatch
Turn off terminal which has file mismatch,
Declare this terminal defect
Call NCR technician
Leave the terminal turned off until it is repaired again.
Reasons for Files Mismatch see

"Terminals that are not ready for EoD"
6. Datatransfer
Wait some seconds until datatransfer from terminal to POS Server is
finished.

-
7. Terminal is locked
The lock flag of this client is shown; e.g. the client is still in
maintenance. See example 6.1.1
The function cannot be finalized at this client due to hardware problems.

Remove Function Lock from this client
Function: 5 - 6 - Remove Function Lock
8. Terminal is locked (WebMaster function)

The WebMaster terminal could not log out properly; e.g. IDC records
were not updated at the WebMaster.
The WebMaster terminal could not log out properly

Status = offline
Status = offline / Files Mismatch
In case of Offline and Offline / Files Mismatch the terminal has to be
declared defective
Function: 4 - 1 - Define defective Terminal
When this terminal is again function properly again, it has to be

declared o.k.: Function 5 - 1 - CRT o.k. again

-
During End-of-Day
1. The End-of-Day could not be finalized due to communication problems
Start End-of-Day again at the same terminal

The End-of-Day will continue at the step where it stopped.
If the End-of-Day was aborted manually, the End-of-Day has to be started again and will
continue where it was stopped.
2. The terminal which initialized End-of-Day has hardware problems, EoD stopped.
2.1 Check User number, terminal number

Menu 5 7 1 Display Logs (WM)
Current Version
CoreStatus.Log Example:
2004/12/02 12:13:43 Login - #==========================
Login - # <USER-LOGIN>
Login - #
Login - # USER NUMBER : 802
Login - # USER NAME : Supervisor 2
Login - # LOGIN ID : 802
Login - # TERMINAL NUMBER : 801
Login - # POS SERVER : 915
Login - # SECRET NUMBER : 2
..
2004/12/02 12:13:45 TerminalEvaluation - TERMINALS_READY [---]
TerminalEvaluation - WEB_CLIENTS_READY [802]
TerminalEvaluation - SIGNED_IN [011,801]
TerminalEvaluation - DATATRANSFER [---]
TerminalEvaluation - OFFLINE [---]
TerminalEvaluation - FILES_MISMATCH [---]
TerminalEvaluation - DEFECTIVE [---]
TerminalEvaluation - EOD [---]
The user 802 started the EoD at Terminal 801 and only user 802 with the terminal selection
801 can continue with the End-of-Day procedure!

-
2.2 Allow terminal selection:

Start Windows NT Explorer
Select drive:\web\mtxwm\conf
Open login.properties; e.g. with Notepad
Excerpt of the login.properties:
the default login module if not specified as servlet parameter

login.defaultModule=LoginCTL
-----------------------------------------------------
LoginCTL
-----------------------------------------------------
0 / false = use dynamic terminals

1 / true = allows selection of a user-defined terminal
LoginCTL.selectTerminal=0
Change LoginCTL.selectTerminal=1
Exit file
Save changes
2.3 Stop / Start JRE Server
Click on desktop icon Advanced Store@Retail twice

-
Click on JREStop
Wait until the JRE Server has stopped

Start JRE Server again with
Click on JREStart
The login screen will be displayed
2.4 Login
Login with
correct User number (in this example: 806)
Secret number
Select correct terminal (in this example: 806)
2.5 Start End-of-Day
The End-of-Day procedure will continue at the step where it was interrupted.

-
3. Sign-in at another terminal than the EoD-Start-Terminal

EoD stopped with error. The following will be displayed.
Check at the WebMaster PC for the reason.

After the problem is solved, start EoD again at the terminal it was started before.
4. End-of-Day aborted
The EoD was aborted through an incident.
The screen will show End-of-Day aborted.
The Main Menu will show the status as following:
Start End-of-Day again with same Operator number and password. The system will continue at
the next following EoD step if there is no major file or hardware problem detected.
Note: Further information on troubleshooting can be found in Sec. 8c.

-
6.2 Reset Points at next EoD

Points saved in customer / employee sales are stored in the M_HSHCLS file at the server and will
be reset within the next EoD when this function is performed.
This menu item is under higher password control.
This function has to be confirmed with o.k.
6.3 Print EoD Reports

This function shows the following subitem
Print EoD Spoolfile
Print old EoD Spoolfiles
6.3.1 Print EoD Spoolfile

This function will display the last End-of-Day reports. The same function is available on the Main
screen.
Click on button Print EoD Spoolfile
The print icon will print all reports defined to be included in the End-of-Day.
Click on print icon

-
Note:
The print of the End-of-Day reports has to be before the next End-of-Day is started.
The print can be repeated until the next End-of-Day was performed. The next day the last End-of-
Day reports can be printed with the function "Print old EoD Spoolfiles" - see 6.3.2.
In the standard (= demo version) the following reports are included in the End-of-Day reports:
LAN Status Report

Hourly Activity Report - Total
Financial Report - Total
Sales Person Report - Total - all levels
Department Report - Total - all levels
Checker Reports - Total - single checkers
Reset Control Counters
The report string can be modified in the eod.properties.

For some reports it also can be selected if the report should be
on terminal basis (= single terminal reports)
on group basis or
only print totals greater than zero
For the property settings refer to Section 7a.

-
6.3.2 Print old EoD Spoolfiles
Click on button 'Print old EoD Spoolfiles'
This function will display the last 10 days of End-of-Day spoolfiles. The last one is always No. 1
and on top of the list. 10 days is the standard setting and can be modified in the eod.properties
ptd.duration=10.
Click on selected spool file
The print icon will print all reports.
The printing of the last End-of-Day Reports will add onother entry to the old EoD Spoolfiles and
insert it as No. 1.
6.7 Re-Run EoD

In worst cases, when no End-of-Day procedure can be started at the WebMaster terminal
because of hardware problems; e.g. hard disk down etc, and a new day has to be started at the
POS terminals.
There is a possibility to run a cluster End-of-Day from a POS terminal including only POS
terminals and the POS Server. See AS@R documentation Section 5 - Cluster EOD with POS
Server / Java POS Terminals only.
If the WebMaster had to be installed again, then the DB which is saved every day at Backup-
Server or at Primary-Server, then the DB can be restored again and no Re-Run EoD is
required.
A Re-Run is only possible when there is no generation count, e.g. GEN_XXX.001, in the safe
directory of the Server.
The End-of-Day change at the Server will be performed, all files will be saved, the terminals will
be reset and receive the new days data. The reports are printed at the POS terminal which
started the EOD.
When the WebMaster is life again, this function is used to Re-Run the Server End-of-Day at the
WebMaster. All WebMaster files will be updated and End-of-Day reports can be printed.
Click on button 'Re-Run EoD'
A list of the last End-of-Days performed by the POS terminals and finalized through the POS
Server will be shown.

-
In the example above two generations are available at the POS Server, no WebMaster files
were updated.
The oldest generation will be processed first when the rerun is now started.
All generations have to be processed.
Press the button Start Rerun or Alt + S
The WebMaster End-of-Day procedure will start.
If there are unprocessed POS Server End-of-Day files, a WebMaster End-of-Day cannot be
started. The older End-of-Day files have to be processed first with a Rerun-End-of-Day.
A Re-Run EoD can be done any time during the day. The POS Server and the POS terminals
will not be included in this procedure.
Note:
A Re-Run EoD can only be started if no End-of-Day procedure was aborted. The normal End-
of-Day procedure has to be finalized first, then a Re-Run of an earlier performed Server-End-
of-Day can be started.
The following steps are performed:

Seq. # EoD Module Task
1 RerunFileLoader Copies all files, belonging to the selected

generation, from the POS Server to the
WebMaster.
3 RerunReports Creates reports based on data from the

/safe/*.<SELECTED_GENERATION>
files.

e.g. SW-Update
5 LoadDatabase Updates the database with report data

from the specified day (Rerun selection).
10 RerunFinalTask The directories are cleaned up, the

generation change is performed etc

-
6.8 POS-EoD
This button is under higher authorization and has to be opened when the option for a 24 hour
store is set.
For 24 hour stores the Auto-EoD flag has be set at the POS server (srv.ini) to allow an End-
of-Day terminal by terminal.
This means, when the POS-EoD button is pressed at WebMaster, the Server will provide new
parameters and will set an EoD request for all POS terminals. As soon as a POS terminal is
signed off, it will perform it's EoD and copy the new parameters from the Server. The next
terminals will act in the same manner.
The terminals can be started again immediately. All transactions will add to the new day. Data
mirroring to the server is disabled until the System-EoD has been performed through the
WebMaster.
When all terminals have performed their End-of-Day the System End-of-Day has to be
started.

-

As@R26WM 7 - End of Day Functions

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

As@R26WM 7 - End of Day Functions

Uploaded by

Copyright:

Available Formats

WebMaster End of Day Functions AS@R 2.6 - Sec.

WebMaster Section 7 - End of Day Functions

End of Day Functions........................................................................................................................ 2

6.1 Sytem End-of-Day ......................................................................................................................... 3

EoD Trouble Shooting ................................................................................................................... 12

6.2 Reset Points at next EoD ............................................................................................................ 18

6.3 Print EoD Reports ....................................................................................................................... 18

6.7 Re-Run EoD ................................................................................................................................ 20

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 1 - 22

End of Day Functions

6.2 Reset Points

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 2 - 22

6.1 Sytem End-of-Day

Click on button 'System-End-of-Day'

Change date to next business day

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 3 - 22

6.1.1 Automatic Check on POS Lock Status

6.1.2 Automatic Check on POS Terminal Status (Ready for EoD)

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 4 - 22

Explanation of Terminal Status:

Header POS Server number, date and time

Terminals ready for EoD

EoD The client is already in End-of-Day (Code 99)

Terminal not ready for EoD

For Define Defective see WebMaster Section 5.

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 5 - 22

For Define Defective see WebMaster Section 5 and EoD Trouble

Click on button 'StartEOD' or press Alt +S

Checker Settlement Evaluation

Continue: This will continue the End-of-Day.

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 6 - 22

Final check on Web-Terminals (Ready for EoD)

The terminal will receive an information:

An automatic logout can be performed by pressing the button LogoutWebClients or Alt + L.

All terminals are now ready for End-of-Day:

End-of-Day will be started automatically after all terminals are ready.

A progress of the End-of-Day is shown in the progress bar.

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 7 - 22

The following End-of-Day sequence will be performed automatically:

Seq. # EoD Module Task

10 CheckerSettlement If cashiers are not balanced during day, this module

15 CshDefaultPart1 This is an EOD module which should run before

16 CshFxFloatPart1 Is an EOD module which should run before server

17 CshDwrMnyPart1 Is an EOD module which should run before server

30 PrimaryServer POS Server performes its End-of-Day

31 EodInfoUpdate Updates the existing EOD entry with the

32 Backup Server Backup Server performs its End-of-Day

33 Parameters Parameter generations will be renamed

35 CshDefaultPart2 Is an EOD module which should run after server

36 CshFxFloatPart2 Is an EOD module which should run after server

38 IDCUpdate Only if old IDC Update (Rel. 2.0.2) is

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 8 - 22

39 HocImportModule If IDCs were not updated during day, this

40 Reports Creates reports based on data from the

44 ApplicationInvoker This module will call batches;

45 LoadDatabase Updates the database with report data

90 UserTrackerReset Reset the user tracker to the new AS@R

95 WebserverBridgeCleaner Free all resources of the Webserver

100 ApplicationInvoker This module will call batches;

110 RetentionModule Function is performed as defined in

119 WebserverBridgeCleaner Free all resources of the Webserver Bridge used

120 FinalTask The directories are cleaned up, the

End-of-Day WebMaster terminal

After the EoD is finished the following message will be shown:

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 1 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 2 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 3 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 4 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 5 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 6 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 7 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 8 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 9 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 10 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 11 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 12 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 13 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 14 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 15 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 16 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 17 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 18 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 19 - 22

Copyright NCR GmbH AUGSBURG 5/9/2008 Page 20 - 22