1 End of Day Maintenance

This topic describes the EOD process and its maintenance.

Introduction

Oracle FLEXCUBE Universal Banking allows to execution of several functions every day on a routine basis as part of the End of cycle (EOC) process. These functions can be run at various stages of the EOC process.

EOD ensures that once End of Cycle processing starts, each function that will be run in the specified sequence will be executed automatically. However, take manual control if there are any problems in running the function. Certain functions require some inputs (called run-time inputs) before they are executed. This also can be automated.

The EOD process should be defined and executed separately for different branches of the bank. When the process is running, choose to monitor it from a central location, perhaps from the data center.

Various Stages of EOC Process

Table 1-1 Various Stages of EOC Process

Stages of EOC Process Description
End of Transaction input (EOTI)

The End of Transaction input (EOTI) stage is the first stage in EOD operations. The system should be moved to this status after all the transactions for the day have been entered into the system. In addition, all the transactions should be authorized and the relevant messages generated.

Note: All the messages don't need to be generated on the same day as transaction input, it is ideally done that way. In an exceptional situation, go ahead with the End of Day processes without generating a message. This message will remain in the un-generated status in the Outgoing Message Browser and can be generated on any other day. An un-generated message will not be archived.EOTI must not be marked under the following circumstances:
  • When a message is in an unprocessed state

    Note: When a reply to the message sent has either not been received or arrived at by the system.

  • The above validations are applicable for RTGS messages only.
  • When transactions that have been input are yet to be authorized.
  • When the debit and credit totals for the day do not match for some reason.
Under such circumstances, examine the transaction(s), which have resulted in the imbalance (with the help of the Transaction Journal) and take the necessary action. The action could be in posting an extra entry or moving an entry from one account to another, etc.

After the system is moved to this status, the user will neither be allowed to enter further transactions into the system nor will be allowed to perform any maintenance functions. All the relevant toolbar actions will also be disabled. However, the user can perform queries on the system.

The user can run only those automated functions that have been defined for this stage of End of Day processing.
End of Financial Input (EOFI)

At this stage, no further accounting entries can be passed for the day either through transactions that have been entered or by transactions that are automatically triggered by the system.

After the system is moved to this status, the user can generate financial reports for the day now since all the automatic processes have been run for the day and since the balances available will be the latest.

After EOFI is marked, the user can generate all advice-related messages like reports, tracers, and all other information on the day’s activities.
End of DayMandatory Batch Program Maintenance

The EOD process is designed to tie up all the operations for a financial day and prepare the system for the next day.

The End of Day operations for a branch can begin after all the transactions for the day have been input and authorized. Ideally, all the messages for the day should also be generated before the End of Day operations begins. A message should be carried over to a subsequent day only under exceptional conditions.

The End of Day status indicates that the user has completed all the activities for the day. After EOD for a branch is run, the system will not allow running any other operation in the branch, till the system date has been changed to the next working day, and authorized. If the user tries to run any application, it will be prompted to change the system date first.

Mandatory Batch Program Maintenance

Refer to the topic Mandatory Batch Program Maintenance for detailed information.

Batch EOD Function Inputs

Refer to the topic Maintain Data Values for EOD Functions for detailed information.

End of Cycle Groups

Refer to the topic Maintain End of Cycle Groups for detailed information.

Pending Maintenance

Refer to the topic Process Unauthorized Maintenance for detailed information.

End of Cycle Process

To start the End of Cycle process, choose End of Cycle and the Start EOC option under it. The End of Cycle operations consists of several stages. In this topic, the various stages that are a part of the cycle are discussed. The various stages in this cycle have been diagrammatically represented below:
Description of end-cycle-process_flowchart.png follows
Description of the illustration end-cycle-process_flowchart.png

This topic contains the following sub-topics:
  1. Maintain End of Cycle Operations
  2. Process End of Cycle Status
  3. Stop EOC Process for Running Branches

Deferred EOD Process

The below flowchart indicates the EOD process in the system:

Figure 1-1 EOD Process Flowchart


Description of Figure 1-1 follows
Description of "Figure 1-1 EOD Process Flowchart"

The EOPD is run parallel to the Transaction Input. The next day Mark EOTI is allowed only when the EOPD stage is completed. The user cannot mark the end of transaction input if the automatic end of day status of EOPD is N.

End of Cycle Monitor

Refer to the topic Maintain EOC Monitor Screen for detailed information.

Changing System Date

The first task for a business day is to change the system date to the current working date. This date is used by the system for all purposes that are associated with a date automatic processes scheduled for the day, the date/time stamp for the activities that take place during the day, and so on. Refer to the topic Maintain System Dates for detailed information.