1.1 Mandatory Batch Program Maintenance

This topic explains systematic instructions to maintain a mandatory batch program that defines the functions to run automatically.

Through the Mandatory Batch Program Maintenance screen, indicate the functions that should be automatically triggered as part of the Automatic End of Cycle.

Note:

The fields which are marked in asterisk are mandatory.

1. On Homescreen, type EIDMANPE in the text box, and click Next.
   The Mandatory Batch Program Maintenance screen displays.

   Figure 1-2 Mandatory Batch Program Maintenance

   
   

   
   Description of "Figure 1-2 Mandatory Batch Program Maintenance"

   
   
2. On the Mandatory Batch Program Maintenance screen, specify the fields.
   For more information on fields, refer to the field description table.

   Table 1-2 Mandatory Batch Program Maintenance - Field Description

   Field	Description
   Branch	The system displays the branch code.
   Module	Click Search and specify the module code from the list of values.
   Function	Click Search and specify the Function from the list of values.
   Sequence Number	Specify the Sequence Number.
   Description	Type a description of the sequence number.
   End of Cycle Group	The end of cycle processing has different stages as follows: Txn Input - This stage indicates that all the transactions for the day have been input and authorized. Thus, the automated processes that involve transaction input during the day have to be executed (periodic accruals, any automatic interest or commission liquidation triggered by transactions that were input during the day, etc.) when the system is in the EOTI stage. End of Txn Input - EOTI indicates the End of all Transaction Inputs, during which all transaction inputs are completed and the batch should be run before EOFI. EOFI indicates the End of Financial Input, during which all accounting transactions are completed and the batch should be run before EOD. EOD indicates the End of Day, during which all activities for that day are completed and the batch should be run before BOD. BOD indicates the Beginning of the Day, during which the transactions are Input. EOPD indicates the End of Previous Day, during which all the EOD processes that are deferred to the next day are processed. End of Fin Input - This stage indicates that no further accounting entries can be passed for the day either through transactions or by automated processes. End of Day - This stage indicates that all the activities for the day are complete. Further activities can be done on the system only after the system date has been changed to the next working day and authorized. Most of the automated functions will be a part of the Beginning of Day operations. Thereafter, some of them (say accruals, for example) should be executed when the system is in the EOTI stage. Some of the functions run during the Beginning of the Day should be repeated during the EOTI stage so that any automated liquidation triggered by transactions input during the day will be processed. Beginning of Day - This is the stage after the system date has been changed and authorized, and before the transaction input for the day can begin. At this stage, the system is expecting certain functions to be executed. For example, automatic liquidation of interest or commission scheduled for the day. The execution of these functions during this stage ensures that all the debits and credits to a customer account that are triggered automatically are done and the balances updated. Thus, when the customers of the bank walk in to execute transactions during the day, records will reflect the latest balance. End of Previous Day - In this stage after BOD processes, all the noncritical processes such as GL statement generation, archival, and purging are deferred to the next day during an EOD process.
   Frequency	Certain functions performed at the bank will have to be run daily, while some others may need to be executed at other periodic frequencies. Specify the functions that should be run at AEOD and select the frequency with which they should be run from the adjoining drop-down list. This list displays the following values: Daily Month End Quarter End Half Year End Year End Nth Day of the Month 'N' Days before End of Month Weekly Repayments due to loans or deposits, liquidation of commissions due to an LC, etc. would be functions that should execute daily since such transactions may happen on any day, depending on the liquidation date specified for the individual contracts. If the Nth Day of the Month or N Days before End of Month option is selected, specify the exact date in the Run Date field or the number of days before which the function should be run in the Number of Days field respectively. It is a known fact that month-ends are usually a period of hectic activity for bankers. Hence, it might require postponing certain activities to a later date, so that the load can be spread evenly. For instance, To run the liquidation of interest on current and savings accounts to the fifth day of every month. While defining the IC liquidation function, specify the frequency as the Nth Day of the Month and specify the number of days as five. The liquidation function will be executed on the fifth, but the processing will be done as of the end of the previous month. Similarly, it is possible to execute a function a few days before the month-end. To do this, specify the frequency level as 'N' Days before End of Month. Specify the number of days before which the function should be executed. If the frequency is defined as a Specific date, enter the date on which the particular function has to be executed.
   Holiday Rule	Select the holiday rule from the drop-down list: Do Not Execute Next working Day Previous Working Day
   Execution Layer	This indicates the execution layer where the batch should be processed. It can have two values: Database Application For example, BIP reports at EOD can be automatically generated using the job scheduler.
   Sub Stage	Specify a valid sub-stage number to run a batch ensuring inter-branch dependency from the adjoining drop-down list. 1 (One) 2 (Two) 3 (Three) The following sub-stages are available for different EOC stages: Post End of Transaction Input Post End of Transaction Input 1 Post End of Transaction Input 2 Post End of Transaction Input 3 Post End of Financial Input Post End of Financial Input 1 Post End of Financial Input 2 Post End of Financial Input 3 Post End of End of Day Post End of End of Day 1 Post End of End of Day 2 Post End of End of Day 3 Post End of Beginning of Day Post End of Beginning of Day 1 Post End of Beginning of Day 2 Post End of Beginning of Day 3 Mark Transaction Input Mark End of Previous Day Post End of Previous Day 1 Post End of Previous Day 2 Post End of Previous Day 3 For example, To run a batch at head office, after running the batch at all the reporting branches, then the batch run at head office is maintained at sub stage 3 and the batch run at reporting branches is maintained at 1 or 2 so that the system runs stage 3 after completing stage 2 in all branches. EOD run mode is maintained as Parallel.
   Error Handling	Select an error-handling option from the following list: Stop Automatic End of Day and Run Emergency Program Continue with Automatic End of Day
   Number Of Days	Specify the Number Of Days.
   Run Date	Click Calendar and select the run date.
   Job Code	Click Search and specify the Predecessors that need to be run to process the job scheduler operations.
   Description	The system displays the job description based on the Job Code specified.
   Predecessors	Click Search and specify the Predecessors from the list of values.

3. Click Exit to end the transaction.