Please enable JavaScript.
Coggle requires JavaScript to display documents.
COB (Extended Multi Company and COB (In an Extended Multi Company…
COB
-
Multi Company and COB
Application level COB batches will be separate for each Lead Company.
Example : The Lead Companies USG, JPN, SWL will have their own Batch records :
USG/AC.REPORTS, JPN/AC.REPORTS, SWL/AC.REPORTS
These batches will be separately processed
Multi Book and COB
In a Multi Book environment, application level Close of Business (COB) batches for the Branches will be linked to their Lead Company.
Example: For the LD application level Batch, there will be only one Batch record :
MF1/LD.END.OF.DAY for the Lead Company: MF1 and its Branches: MF2 and MF3
The LD records of the Lead Company and its Branches will be processed in the same Batch job
Global Processing (GP)
-
The GP product will allow independent close of business processing for companies whilst other companies continue to process online transactions.
Global Processing allows the COB processing in a Multi Company environment to be run independently at Lead Company or Lead Company group level.
It is restricted to lead companies. i.e., all branches linked to a Lead Company are processed together.
If the Lead Companies in a T24 database are located in a variety of time zones then the COB processing can take place at a convenient time for the relevant group, with the other groups in the system online.
-
-
Global Processing (GP)
Multi Company and GP
-
-
-
If the bank operates over a large geographical area with different time zones, and a separate COB processing is required for the Companies using the GP functionality.
Multi Book and GP
There is no need to have separate COB processing (Global Processing) for the Companies, for example, when they are in the same time zone
-
-
-
COB
Without GP
In any installation of T24 when you run COB it gets executed for all companies by default that means in a Non – GP Environment the COB processing for all companies takes place at the same time on a common system calendar.
This implies that the common calendar must ensure that a working day in one country must be a working day for all companies.
Each company must share a common LOCAL.COUNTRY or LOCAL.REGION table.
This implies that a shared system calendar is used for the bank’s processing, even though the actual financial entities may exist in different countries.
With GP
The ability to allow COB processes to run at different times for companies or groups of companies requires the system to allow each company to use a different system calendar, since different countries will have different holidays.