Implementation system and method of multi-corporation mode of bank core business system

Abstract

The application provides a kind of bank core business system multi-law implementation system and method of person mode, comprising: bottom support platform module: according to bank legal person code, the configuration file directory of person is deposited; Database storage module: introduce bank legal person code field design core database bottom; Application layer transaction module: according to bank legal person code field, the parameter reading of specific transaction process is carried out, and process differentiation is handled; Batch processing module: after obtaining the bank legal person code parameter input by batch processing terminal, uniformly assign to each batch transaction.The whole bank legal person code concept and model construction are introduced in the application, and run through the whole life cycle of system;The application can support multiple persons at different levels, improve product function, and greatly reduce hardware investment cost.

Description

Technical Field

[0001] This invention relates to the field of software system development technology, and more specifically, to a system and method for implementing a multi-legal entity model in a core banking business system. Background Technology

[0002] Currently, in providing core business system construction services for numerous city commercial banks, private banks, and rural banks, the traditional model of building a dedicated server for each legal entity involves significant server overhead, as well as development and maintenance costs. To better serve clients and efficiently respond to their personalized business needs, a multi-legal entity solution for the core system is urgently needed.

[0003] Patent document CN103366243A (application number: CN201310241438.4) discloses a core system for banking operations. Based on the core system functions of conventional banking operations, it integrates various related systems currently used by Huaxia Bank, providing unified management functions for public information including customer, account and transaction information, standardized product design, branch network, currency, interest rates, and fees. It also provides basic business applications such as deposits, loans, internal accounting, contingent liabilities, payments, and card management. However, this invention does not introduce the concept and model of a bank legal entity code. Summary of the Invention

[0004] In view of the deficiencies in the prior art, the purpose of this invention is to provide a system and method for implementing a multi-legal entity model in a core banking business system.

[0005] According to the present invention, a system for implementing a multi-legal entity model in a core banking business system includes:

[0006] The underlying support platform module stores configuration files in directories categorized by bank legal entity code.

[0007] Database storage module: The core database underlying design incorporates a bank legal entity code field;

[0008] Application layer transaction module: Reads parameters for specific transaction processes based on the bank's legal entity code field and performs process differentiation processing;

[0009] Batch processing module: After obtaining the bank legal entity code parameter input from the batch processing terminal, it uniformly assigns the value to each batch processing transaction.

[0010] Preferably, in the underlying support platform module:

[0011] The bank's legal entity code is defined in the header of the inter-system communication message. After receiving the message, it is parsed and classified according to the message header.

[0012] Configuration files are stored separately by bank legal entity code; logs and reports are also stored separately by bank legal entity code.

[0013] During the system construction phase, the project team uniformly assigned bank legal entity codes to each legal entity to distinguish them; all systems associated with the core communication assigned bank legal entity codes to the message headers.

[0014] Preferably, in the database storage module:

[0015] Multiple legal entities under the same initiating bank share the same database instance. Business-related tables in the database are uniformly revised, a bank legal entity code field is added, data is assigned and stored according to different bank legal entity codes, and common parameter data is stored according to default values.

[0016] Add a bank legal entity code field to the index; adjust the locking mode of all tables to row-level locking.

[0017] Preferably, in the application layer transaction module:

[0018] Multiple legal entities use a unified version of their business transaction procedures;

[0019] The entire business transaction interface has been redesigned, and a bank legal entity code field has been added to all messages. The specific transaction process is based on the bank legal entity code field for parameter reading and process differentiation.

[0020] All business-related official document interfaces have been fully adjusted, and a bank legal entity code field has been added to the input parameters; specific transaction processes will be differentiated based on the bank legal entity code field for parameter reading and process differentiation.

[0021] The business processes and business parameter values ​​of multiple legal entities are configured differently. The specific business transaction processes are read and processed according to the bank's legal entity code field; the functions are configured with parameters, and the process switches control the branch direction.

[0022] Preferably, in the batch processing module:

[0023] A centralized deployment model is adopted, with all legal entities sharing a single instance of data;

[0024] The batch processing transactions have been fully adjusted, and a bank legal entity code interface has been added. After the batch processing master obtains the bank legal entity code parameter input by the batch processing terminal, it is uniformly assigned to each batch processing transaction.

[0025] Batch processing operates independently for each legal entity, and the batch processing workflows between different legal entities do not interfere with each other.

[0026] Different legal entities use independent batch processing environments to set and transfer operating parameters, and the batch processing of transactions and the order of each transaction are different for different legal entities.

[0027] The data generated during the batch processing stage is stored in the bank's legal entity code directory of the legal entity, and archived in various subdirectories. Each legal entity can only query the data corresponding to its own bank's legal entity code.

[0028] According to the present invention, a method for implementing a multi-legal entity model in a core banking business system is provided, wherein the system for implementing the multi-legal entity model in a core banking business system is used to perform the following:

[0029] Step S1: The underlying support platform module stores configuration files in directories according to the bank's legal entity code;

[0030] Step S2: The database storage module incorporates the bank's legal entity code field to design the core database underlying layer;

[0031] Step S3: The application layer transaction module reads the parameters of the specific transaction process based on the bank's legal entity code field and performs process differentiation processing;

[0032] Step S4: After the batch processing module obtains the bank legal entity code parameter input from the batch processing terminal, it assigns the value to each batch processing transaction.

[0033] Preferably, in step S1:

[0034] The bank's legal entity code is defined in the header of the inter-system communication message. After receiving the message, it is parsed and classified according to the message header.

[0035] Configuration files are stored separately by bank legal entity code; logs and reports are also stored separately by bank legal entity code.

[0036] During the system construction phase, the project team uniformly assigned bank legal entity codes to each legal entity to distinguish them; all systems associated with the core communication assigned bank legal entity codes to the message headers.

[0037] Preferably, in step S2:

[0038] Multiple legal entities under the same initiating bank share the same database instance. Business-related tables in the database are uniformly revised, a bank legal entity code field is added, data is assigned and stored according to different bank legal entity codes, and common parameter data is stored according to default values.

[0039] Add a bank legal entity code field to the index; adjust the locking mode of all tables to row-level locking.

[0040] Preferably, in step S3:

[0041] Multiple legal entities use a unified version of their business transaction procedures;

[0042] The entire business transaction interface has been redesigned, and a bank legal entity code field has been added to all messages. The specific transaction process is based on the bank legal entity code field for parameter reading and process differentiation.

[0043] All business-related official document interfaces have been fully adjusted, and a bank legal entity code field has been added to the input parameters; specific transaction processes will be differentiated based on the bank legal entity code field for parameter reading and process differentiation.

[0044] The business processes and business parameter values ​​of multiple legal entities are configured differently. The specific business transaction processes are read and processed according to the bank's legal entity code field; the functions are configured with parameters, and the process switches control the branch direction.

[0045] Preferably, in step S4:

[0046] A centralized deployment model is adopted, with all legal entities sharing a single instance of data;

[0047] The batch processing transactions have been fully adjusted, and a bank legal entity code interface has been added. After the batch processing master obtains the bank legal entity code parameter input by the batch processing terminal, it is uniformly assigned to each batch processing transaction.

[0048] Batch processing operates independently for each legal entity, and the batch processing workflows between different legal entities do not interfere with each other.

[0049] Different legal entities use independent batch processing environments to set and transfer operating parameters, and the batch processing of transactions and the order of each transaction are different for different legal entities.

[0050] The data generated during the batch processing stage is stored in the bank's legal entity code directory of the legal entity, and archived in various subdirectories. Each legal entity can only query the data corresponding to its own bank's legal entity code.

[0051] Compared with the prior art, the present invention has the following beneficial effects:

[0052] 1. This invention introduces the concept and model of bank legal entity code throughout the entire system lifecycle;

[0053] 2. This invention isolates and processes different legal entities based on the bank's legal entity code in different modules such as the underlying support platform, database storage, application layer transactions, and batch processing within the core system. This enables the deployment of core applications for multiple legal entities on a single server, thereby reducing server resource consumption and development and maintenance workload.

[0054] 3. This invention can support multiple legal entities at different levels, improve product functionality, and significantly reduce hardware investment costs;

[0055] 4. This invention provides unified and efficient management, reduces redundant development and maintenance workload, efficiently responds to customer needs, and also improves customer satisfaction with bank cloud services. Attached Figure Description

[0056] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0057] Figure 1 This is a system deployment diagram of the present invention;

[0058] Figure 2 This is a diagram showing the relationships between the various modules within this invention. Detailed Implementation

[0059] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0060] Example 1:

[0061] Technical Field: This invention belongs to the field of core banking systems and is based on the upgrade and construction of the Industrial Bank Digital Finance V3 core business system. The V3 core is based on the AIX operating system, developed in C language, uses the Informix database, and employs Tuxedo middleware.

[0062] This invention includes multiple subsystems such as product factory, expense factory, account accounting and fund clearing. Its functions include: performing accounting, storing the bank's accounting data, performing fund scheduling and clearing, supporting the bank's traditional deposit, loan, payment and settlement products, and providing billing and interest support as well as media and voucher management.

[0063] According to the present invention, a method for implementing a multi-legal entity model in a core banking business system is provided, and the system for implementing the multi-legal entity model in a core banking business system is adopted, such as... Figures 1-2 As shown, the execution includes:

[0064] Step S1: The underlying support platform module stores configuration files in directories according to the bank's legal entity code;

[0065] Step S2: The database storage module incorporates the bank's legal entity code field to design the core database underlying layer;

[0066] Step S3: The application layer transaction module reads the parameters of the specific transaction process based on the bank's legal entity code field and performs process differentiation processing;

[0067] Step S4: After the batch processing module obtains the bank legal entity code parameter input from the batch processing terminal, it assigns the value to each batch processing transaction.

[0068] Specifically, in step S1:

[0069] The bank's legal entity code is defined in the header of the inter-system communication message. After receiving the message, it is parsed and classified according to the message header.

[0070] Configuration files are stored separately by bank legal entity code; logs and reports are also stored separately by bank legal entity code.

[0071] During the system construction phase, the project team uniformly assigned bank legal entity codes to each legal entity to distinguish them; all systems associated with the core communication assigned bank legal entity codes to the message headers.

[0072] Specifically, in step S2:

[0073] Multiple legal entities under the same initiating bank share the same database instance. Business-related tables in the database are uniformly revised, a bank legal entity code field is added, data is assigned and stored according to different bank legal entity codes, and common parameter data is stored according to default values.

[0074] Add a bank legal entity code field to the index; adjust the locking mode of all tables to row-level locking.

[0075] Specifically, in step S3:

[0076] Multiple legal entities use a unified version of their business transaction procedures;

[0077] The entire business transaction interface has been redesigned, and a bank legal entity code field has been added to all messages. The specific transaction process is based on the bank legal entity code field for parameter reading and process differentiation.

[0078] All business-related official document interfaces have been fully adjusted, and a bank legal entity code field has been added to the input parameters; specific transaction processes will be differentiated based on the bank legal entity code field for parameter reading and process differentiation.

[0079] The business processes and business parameter values ​​of multiple legal entities are configured differently. The specific business transaction processes are read and processed according to the bank's legal entity code field; the functions are configured with parameters, and the process switches control the branch direction.

[0080] Specifically, in step S4:

[0081] A centralized deployment model is adopted, with all legal entities sharing a single instance of data;

[0082] The batch processing transactions have been fully adjusted, and a bank legal entity code interface has been added. After the batch processing master obtains the bank legal entity code parameter input by the batch processing terminal, it is uniformly assigned to each batch processing transaction.

[0083] Batch processing operates independently for each legal entity, and the batch processing workflows between different legal entities do not interfere with each other.

[0084] Different legal entities use independent batch processing environments to set and transfer operating parameters, and the batch processing of transactions and the order of each transaction are different for different legal entities.

[0085] The data generated during the batch processing stage is stored in the bank's legal entity code directory of the legal entity, and archived in various subdirectories. Each legal entity can only query the data corresponding to its own bank's legal entity code.

[0086] Example 2:

[0087] Example 2 is a preferred embodiment of Example 1, and is used to illustrate the present invention in more detail.

[0088] Summary of the Invention and Implementation Methods:

[0089] This invention introduces the concept and model of "bank legal entity code" (hereinafter referred to as "bank legal entity code") throughout the entire system lifecycle. In different modules within the core system, such as the underlying support platform, database storage, application layer transactions, and batch processing, different legal entities are isolated, differentiated, and processed based on the bank legal entity code.

[0090] During its development, this invention addressed the needs of multiple legal entities by employing technical means to modify the underlying support platform, database storage, application-layer transactions, batch processing, and other aspects:

[0091] Application sharing: Multiple legal entities share a single application system, which has functions such as overall management, internal remittance, and basic statistics;

[0092] Data isolation: Data from multiple legal entities remains independent and complete at each stage of transmission and storage;

[0093] Business Differences: Business processes and parameter values ​​of multiple legal entities can be configured differently, supporting personalized and differentiated businesses in various industries;

[0094] And it achieved the following objectives:

[0095] Unified deployment avoids redundant construction and significantly reduces hardware investment costs;

[0096] Unified management reduces the workload of development and maintenance.

[0097] The present invention also provides an implementation system for a multi-legal entity model of a bank's core business system. The implementation system for a multi-legal entity model of a bank's core business system can be implemented by executing the process steps of the implementation method of the multi-legal entity model of a bank's core business system. That is, those skilled in the art can understand the implementation method of the multi-legal entity model of a bank's core business system as a preferred embodiment of the implementation system for the multi-legal entity model of a bank's core business system.

[0098] According to the present invention, a system for implementing a multi-legal entity model in a core banking business system includes:

[0099] The underlying support platform module stores configuration files in directories categorized by bank legal entity code.

[0100] Database storage module: The core database underlying design incorporates a bank legal entity code field;

[0101] Application layer transaction module: Reads parameters for specific transaction processes based on the bank's legal entity code field and performs process differentiation processing;

[0102] Batch processing module: After obtaining the bank legal entity code parameter input from the batch processing terminal, it uniformly assigns the value to each batch processing transaction.

[0103] Specifically, in the underlying support platform module:

[0104] The bank's legal entity code is defined in the header of the inter-system communication message. After receiving the message, it is parsed and classified according to the message header.

[0105] Configuration files are stored separately by bank legal entity code; logs and reports are also stored separately by bank legal entity code.

[0106] During the system construction phase, the project team uniformly assigned bank legal entity codes to each legal entity to distinguish them; all systems associated with the core communication assigned bank legal entity codes to the message headers.

[0107] Specifically, in the database storage module:

[0108] Multiple legal entities under the same initiating bank share the same database instance. Business-related tables in the database are uniformly revised, a bank legal entity code field is added, data is assigned and stored according to different bank legal entity codes, and common parameter data is stored according to default values.

[0109] Add a bank legal entity code field to the index; adjust the locking mode of all tables to row-level locking.

[0110] Specifically, in the application layer transaction module:

[0111] Multiple legal entities use a unified version of their business transaction procedures;

[0112] The entire business transaction interface has been redesigned, and a bank legal entity code field has been added to all messages. The specific transaction process is based on the bank legal entity code field for parameter reading and process differentiation.

[0113] All business-related official document interfaces have been fully adjusted, and a bank legal entity code field has been added to the input parameters; specific transaction processes will be differentiated based on the bank legal entity code field for parameter reading and process differentiation.

[0114] The business processes and business parameter values ​​of multiple legal entities are configured differently. The specific business transaction processes are read and processed according to the bank's legal entity code field; the functions are configured with parameters, and the process switches control the branch direction.

[0115] Specifically, in the batch processing module:

[0116] A centralized deployment model is adopted, with all legal entities sharing a single instance of data;

[0117] The batch processing transactions have been fully adjusted, and a bank legal entity code interface has been added. After the batch processing master obtains the bank legal entity code parameter input by the batch processing terminal, it is uniformly assigned to each batch processing transaction.

[0118] Batch processing operates independently for each legal entity, and the batch processing workflows between different legal entities do not interfere with each other.

[0119] Different legal entities use independent batch processing environments to set and transfer operating parameters, and the batch processing of transactions and the order of each transaction are different for different legal entities.

[0120] The data generated during the batch processing stage is stored in the bank's legal entity code directory of the legal entity, and archived in various subdirectories. Each legal entity can only query the data corresponding to its own bank's legal entity code.

[0121] Example 3:

[0122] Example 3 is a preferred example of Example 1, and is used to illustrate the present invention in more detail.

[0123] This invention introduces the concept of "bank legal entity code" as a whole.

[0124] Module 1 Name: Underlying Support Platform

[0125] The design adds a new message communication specification Z04, which defines the bank's legal entity code in the header of inter-system communication messages. After receiving the message, the core system parses and classifies it according to the message header.

[0126] The core system configuration file directory is stored separately by bank legal entity code to meet differentiated configuration requirements; the log and report directories are also stored separately by bank legal entity code to facilitate operation and maintenance troubleshooting and management.

[0127] During the system construction phase, the project team uniformly assigned a 5-digit bank legal entity code to each legal entity. This identifier is used to uniquely distinguish each legal entity. All systems associated with the core communication must assign a value to the bank legal entity code in the message header.

[0128] In the application examples, the basic application is a unified version; the configuration file directory is stored separately by bank legal entity code to meet differentiated configuration requirements; the log directory is stored separately by bank legal entity code to facilitate operation and maintenance troubleshooting and management.

[0129] Module 2 Name: Database Storage

[0130] A bank legal entity code field was introduced into the underlying design of the core database. Multiple legal entities under the same initiating bank share the same database instance. Approximately 700 business-related tables (parameters, business, accounting, customers, transaction records, etc.) in the core database were uniformly revised, and a bank legal entity code field was added to all of them. Differentiated parameters and other data are assigned and stored separately for different bank legal entity codes, while common parameters are stored with default values, achieving data logical isolation and independent differentiated management.

[0131] Add a bank legal entity code field to the index to increase data processing efficiency.

[0132] The locking mode of all tables has been adjusted to row-level locking to reduce the probability of lock conflicts.

[0133] Module 3 Name: Application Layer Transactions

[0134] The business transaction procedures of multiple legal entities adopt a unified version, which greatly reduces the workload of redundant development.

[0135] The entire business transaction interface has been redesigned, and a bank legal entity code field has been added to all messages. For specific transaction processes, parameters can be read based on the bank legal entity code field, and the process can be differentiated accordingly.

[0136] The entire interface for business-related official documents has been redesigned, and a bank legal entity code field has been added to the input parameters. For specific transaction processes, parameters can be read based on the bank legal entity code field, and the process can be differentiated accordingly.

[0137] The business processes and parameter values ​​of multiple legal entities can be configured differently, supporting personalized and differentiated businesses for each bank. Specific business transaction processes are handled by reading parameters and processing them based on the bank's legal entity code field; functional parameters are configured, and process switches control branch flow.

[0138] Module 4 Name: Batch Processing

[0139] The core batch processing is deployed on the database host in a centralized deployment mode, with all legal entities sharing a single instance of data.

[0140] The batch processing transactions were fully adjusted, and a bank legal entity code interface was added. After the batch processing master controller obtains the bank legal entity code parameter input by the batch processing terminal, it uniformly assigns the value to each batch processing transaction.

[0141] Batch processing operates independently as a single legal entity, unrelated to the operations of other legal entities, and the batch processing workflows between different legal entities do not interfere with each other.

[0142] Different legal entities use independent batch processing environments to set and transfer operating parameters, and the batch processing of transactions and the order of each transaction can be different for different legal entities.

[0143] The logs, files, and other data generated during the batch processing stage are stored in the bank's legal entity code directory, archived in various subdirectories, for each legal entity's front-end system to query. Each legal entity can only query the data corresponding to its own bank's legal entity code.

[0144] Those skilled in the art will understand that, in addition to implementing the system, apparatus, and their modules provided by this invention in purely computer-readable program code, the same program can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, the system, apparatus, and their modules provided by this invention can be considered a hardware component, and the modules included therein for implementing various programs can also be considered structures within the hardware component; alternatively, modules for implementing various functions can be considered both software programs implementing the method and structures within the hardware component.

[0145] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. A system for implementing a multi-corporation mode of a bank core business system, characterized by, Comprise: The bottom layer support platform module: according to the bank legal person code, the legal person configuration file directory is deposited; Database storage module: introduce the bank legal person code field design core database bottom; Application layer transaction module: according to the bank legal person code field, the specific transaction process parameter reading is carried out, and the process differentiation is handled; Batch processing module: after obtaining the bank legal person code parameter input by the batch terminal, the bank legal person code parameter is uniformly assigned to each batch transaction; In the database storage module: Multiple legal persons of the same initiating bank share the same database instance, the tables related to the business in the database are uniformly revised, the bank legal person code field is added, the data is stored by assigning different bank legal person codes, and the common parameter data is stored according to the default value; The bank legal person code field is added in the index; the lock mode of the table is adjusted to row lock; In the application layer transaction module: The business transaction program of multiple legal persons adopts a unified version; The business transaction interface is adjusted in full amount, and the bank legal person code field is added in the message; the specific transaction process is read according to the bank legal person code field, and the process differentiation is handled; The business related public letter interface is adjusted in full amount, and the bank legal person code field is added in the input parameter; the specific transaction process is read according to the bank legal person code field, and the process differentiation is handled; The business process and business parameter value of multiple legal persons are differentiated, the specific business transaction process is read according to the bank legal person code field, and the process is handled; the functional parameterization configuration is configured, and the process switch control branch direction is differentiated; In the batch processing module: A centralized deployment mode is adopted, and each legal person data shares an instance; The batch processing transaction is adjusted in full amount, and the bank legal person code interface is added; After the bank legal person code parameter input by the batch terminal is obtained, the bank legal person code parameter is uniformly assigned to each batch transaction; The batch processing is independently operated according to a single legal person, and the batch processing processes of each legal person do not interfere with each other; Different legal persons adopt independent batch processing environment operation parameter setting and transmission, and different legal persons batch processing operation transaction and each transaction operation sequence are different; The data generated in the batch processing stage is stored in the bank legal person code directory of the legal person, and is stored in each subdirectory for archiving, and each legal person can only query the data corresponding to the bank legal person code.

2. The bank core business system multi-law firm mode implementation system according to claim 1, characterized in that, In the bottom layer support platform module: The bank legal person code is defined in the system communication message header, and after receiving the message, the message header is parsed and classified; The configuration file directory is deposited according to the bank legal person code; the log and report are deposited according to the bank legal person code; During the system construction stage, the project team uniformly allocates the bank legal person code for each legal person, and the bank legal person code is used to distinguish each legal person; all the related systems of the core communication are assigned the bank legal person code in the message header.

3. A method for implementing a multi-corporation mode of a bank core business system, characterized in that, The bank core business system multi-legal person mode implementation system of claim 1 is executed, and the execution comprises: Step S1: the bottom layer support platform module deposits the configuration file directory according to the bank legal person code; Step S2: the database storage module introduces the bank legal person code field to design the core database bottom; Step S3: the application layer transaction module reads the parameters of the specific transaction process according to the bank legal person code field, and carries out process differentiation processing; Step S4: After the batch processing module obtains the bank legal person code parameter input by the batch processing terminal, it uniformly assigns the parameter to each batch processing transaction; In the step S2: Multiple legal persons of the same initiating bank share the same database instance, and the bank legal person code field is added to the business-related tables in the database, and the data is stored according to different bank legal person codes, and the common parameter data is stored according to the default value; The bank legal person code field is added to the index, and the lock mode of the table is adjusted to row lock; In the step S3: The business transaction program of multiple legal persons uses a unified version; The business transaction interface is adjusted in full, and the bank legal person code field is added to the message; the specific transaction process reads parameters and processes differently according to the bank legal person code field; The business-related public letter interface is adjusted in full, and the bank legal person code field is added to the input parameter; the specific transaction process reads parameters and processes differently according to the bank legal person code field; The business process and business parameter value of multiple legal persons are configured differently, and the specific business transaction process reads parameters and processes according to the bank legal person code field; the functional parameter configuration and the process switch control branch direction are configured; In the step S4: A centralized deployment mode is used, and the data of each legal person shares an instance; The batch processing transaction is adjusted in full, and the bank legal person code interface is added; after the batch processing master obtains the bank legal person code parameter input by the batch processing terminal, it uniformly assigns the parameter to each batch processing transaction; The batch processing is independently run according to a single legal person, and the batch processing processes of each legal person do not interfere with each other; Different legal persons use independent batch processing environment running parameter settings and transmission, and different legal persons have different batch processing running transactions and running sequences; The data generated in the batch processing stage is stored in the bank legal person code directory of the legal person, and is archived and stored in each subdirectory, and each legal person can only query the data corresponding to its own bank legal person code.

4. The implementation method of the bank core business system multi-law firm mode according to claim 3, characterized in that, In the step S1: The bank legal person code is defined in the system communication message header, and after receiving the message, it is classified and processed according to the message header; The configuration file directory is stored according to the bank legal person code; the log and report are stored according to the bank legal person code; During the system construction stage, the project team uniformly allocates the bank legal person code to each legal person, which is used to distinguish each legal person; the bank legal person code in the message header is assigned by all related systems that communicate with the core.

Images