My Oracle Support Banner

Close Branch Batch Without Opening Branch Batch (Doc ID 2874700.1)

Last updated on JUNE 06, 2022

Applies to:

Oracle Banking Branch - Version to [Release 14]
Information in this document applies to any platform.


On : version, Implementation Support

Close Branch Batch without opening branch batch

We are on August Innovation patchset and have consumed multiple set of hotfixes.

 Next date transaction not allowed for this function.

1] In the branch where EOD is completed but branch batch was never opened.
2] In a branch where EOD is not yet run, but branch batch was still never opened.
3] Same case as above, but closing the branch batch a 2nd time.

Description :
We go to a branch where the Open Branch Batch was never done at all. And we go to close branch batch without opening the branch batch. System allows directly closing the branch without opening.
After closing the Branch Batch, if we select close branch batch again, screen will open with same posting date and we are allowed to close again. But the Current Posting date and Next Posting date in the table SRV_TB_BC_BRANCH_INFO is moved ahead to the next working day.

When we submit again from this screen, even though it is showing posting date as 12-Mar here, but in the SRV_TB_BC_BRANCH_INFO table it is 16 Mar, in CMC SYSTEM DATE it is still 12 Mar, it will again move the posting date to the next working date that is 18 Mar.
After this if we try to go to the close branch batch again, it will throw error saying next date transaction not allowed for this function.

All of the above are tried without ever opening the branch batch at all.
Similarly after completing the EOD in branch, we can close the branch batch without opening for the new day and it follows the same mentioned pattern.

System is not checking if the branch batch is opened for the day when clicking close batch.
System is allowing close branch batch and moving the posting date 1 extra time(twice totally) even when next day transaction is not allowed for close branch batch.


After apply fix ,when we open the close branch batch after already closing branch batch once, or opening close branch batch without opening branch batch for the day - system throws an error with today's/previous day's date saying that the branch batch is already closed for the day/previous day.
This will essentially stop the users from closing branch batch after closing it once or never opening the branch batch. So this resolves the issue.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.