Open topic with navigation
End of Day Overview
End of Day is affected by property selection and when it is
run, checks the selected property for open batches, generates exception
reporting and updates the last End of Day date within the property file
with the current system date.
Auto-Process EOD
The process is typically run from the Processing menu but can be automatically
called by the Begin of Day process if the date entered in the Run As Of
field expands past one day. In this case, BOD controls the validation
of the date. For instance, if today is March 1, 2006 and BOD needs to
be run and the last EOD date is March 1, 2006 then the system automatically
runs BOD and EOD for those dates when End of Day is run.
Understanding Dates
Several dates are mentioned when referring to the
Begin of Day and End of Day processes. Refer to the list below for a brief
explanation of each:
- Last
BOD Date —
the last date the Begin of Day process was run. It must be equal to or
after the eSite log on date in order to enter date-sensitive activities
such as: applications, move-ins, notices and move-outs. Begin of day processes
are run once for every day from the last BOD
date to the Run As Of date specified on the Begin of Day Tab.
- Last
EOD Date —
the last date the End of Day
process was run. If this date is earlier than the day before the eSite
log on date, running the Begin of Day
process prints a message on the Exception
Report reminding you that the End
of Day process has not been run and does not allow you to proceed
until the process is completed.
See
Also
End
of Day Overview
End of Day Tab
To Run
End of Day
Effect
of Global Policies
Effect
of Property Policies
Begin
of Day Overview
Processing
Overview