Mechanism withdrawing method and device, electronic equipment and storage medium

By generating merger operation statements and automatically judging legality and handling failure alarms, the cumbersome problems of institutional merger methods in the existing technology are solved, and the efficiency and accuracy of data migration and management are improved.

CN119025503APending Publication Date: 2024-11-26BEIYIN FINANCIAL TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411080508.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-07
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The existing institutional merger method is cumbersome and inconvenient in the data migration and management and maintenance process, especially when query conditions change or organization status changes, the migration method needs to be manually modified and tested, resulting in inefficiency.

Method used

By generating merger operation statements based on the target organization, and determining the effective date, legality and failure alarms of the merger operation during the merger operation, automatically adjust the merger plan and configuration data to achieve automated data migration and management.

Benefits of technology

It improves the efficiency and management convenience of institutional mergers, reduces manual intervention, and ensures the accuracy and feasibility of merger plans.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119025503A_ABST
    Figure CN119025503A_ABST
Patent Text Reader

Abstract

The invention discloses an institution withdrawing method and device, electronic equipment and a storage medium, and relates to the technical field of data management, and the method comprises the steps: generating a withdrawing operation statement corresponding to a target institution based on a withdrawing instruction of the target institution and an institution configuration item; and executing the withdrawing operation of the target mechanism based on the withdrawing operation statement. Through the method, management and maintenance are facilitated, and the mechanism withdrawal efficiency can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of data management technology, and in particular to a method, device, electronic device and storage medium for institution merger and dissolution. Background Art

[0002] Institutions are the carriers of functions, and functions are the basis for the existence of institutions. Through scientifically setting up institutions, rationally allocating functions, coordinating the use of staffing, and improving systems and mechanisms, the strategic development of the bank can be effectively supported. The main tasks of institutional mergers and withdrawals are to transform functions, adjust division of labor, and improve systems. Common types of mergers and withdrawals are as follows: The first is that branch A1 is directly merged to the parent institution. In this type of merger and withdrawal, branch A1 disappears, and its assets and liabilities are incorporated into the parent institution; the second is that branch A2 relocates and changes its name without changing its parent institution. This type of merger and withdrawal is further divided into two types: one is to merge to an existing branch B2 at the same level, and the other is to open a new empty branch B2 and then merge A2 to B2.

[0003] Regardless of the method, after the merger or withdrawal of an institution, the data migration of the withdrawn institution is the primary problem that needs to be solved in the industry. Currently, different migration methods are manually configured for the data tables of different withdrawn institutions, so that the withdrawal data can be queried in the corresponding database through the query conditions in the migration method, and the withdrawn data can be withdrawn and merged. However, if the query conditions change, the corresponding migration method must be modified, and the modified migration method needs to be tested and deployed; and when a certain attribution table is added or deleted, the corresponding migration method needs to be added or deleted to realize the withdrawal or withdrawal of the institution, which brings cumbersomeness and inconvenience to the subsequent management and maintenance. Summary of the invention

[0004] The present application provides an organization merging and dismantling method, device, electronic device and storage medium, which can solve the problem that the current organization merging and dismantling method is not convenient for subsequent management and maintenance.

[0005] In a first aspect, the present application provides a method for merging and dissolving an institution, the method comprising:

[0006] Generate a merging and unmerging operation statement corresponding to the target organization based on the merging and unmerging instruction and organization configuration item of the target organization; wherein the organization configuration item includes at least one merging and unmerging field identifier;

[0007] The unmerge operation of the target mechanism is executed based on the unmerge operation statement.

[0008] The above method not only facilitates the management and maintenance of organization configuration items, but also improves the efficiency of organization mergers and dissolutions.

[0009] In a possible embodiment, before generating a merging and unmerging operation statement corresponding to the target organization based on the merging and unmerging instruction of the target organization and the organization configuration item, the method further includes:

[0010] Upon receiving the registration withdrawal request of the target institution, determining whether the effective date of the registration withdrawal request exceeds a preset date;

[0011] When the withdrawal and merger effective date exceeds a preset date and it is determined that the target institution and the withdrawal and merger receiving institution are legitimate, generating the withdrawal and merger registration information of the target institution based on the withdrawal and merger registration request;

[0012] The merger and closure registration information is filled into the institution merger and closure plan registration form, and a merger and closure instruction of the target institution is generated.

[0013] Through the above method, the merger and closure plan of the target institution is stored in the institution merger and closure plan registration table. By judging whether the merger and closure effective date exceeds the preset date and whether the target institution and the merger and closure receiving institution are legal, the feasibility and accuracy of the merger and closure plan can be guaranteed.

[0014] In a possible embodiment, determining that the target institution and the merge-receiving institution are legal includes:

[0015] When it is found that the target institution ID and the withdrawal receiving institution ID in the withdrawal registration request exist in the institution maintenance table, the first institution status of the target institution and the second institution status of the withdrawal receiving institution are respectively obtained; wherein the institution maintenance table contains multiple institution IDs;

[0016] When the first institution status and the second institution status are both not invalid, it is determined that the target institution and the merged receiving institution are legal.

[0017] Through the above method, it can be determined whether the target institution and the merged and accepted institution are legal, thereby ensuring the feasibility and accuracy of the merge and withdrawal plan of the target institution.

[0018] In a possible embodiment, the method further includes:

[0019] When a closure failure alarm of the target mechanism is detected, obtaining the closure times of the target mechanism, and determining whether the closure times is less than a preset value;

[0020] If yes, then based on the target organization identifier, reacquire the target configuration data related to the target organization from the organization merger and revocation configuration table, and perform the merger and revocation operation of the target organization based on the target configuration data;

[0021] If not, the withdrawal and merger log corresponding to the target organization is obtained, and prompt information is generated based on the withdrawal and merger log; wherein the prompt information includes the withdrawal and merger failure reason and the solution strategy corresponding to the withdrawal and merger failure reason.

[0022] Through the above method, when the merger failure alarm is detected, there are many reasons for the failure, such as network delay and network interruption. By performing the merger and re-running operation when the merger and re-running times of the target organization is less than the preset value, and generating a prompt message when the merger and re-running times is greater than or equal to the preset value, the merger and re-running efficiency can be further improved.

[0023] In a second aspect, the present application provides a mechanism merging and dismantling device, the device comprising:

[0024] A generation module, used for generating a merging and dissolving operation statement corresponding to the target organization based on the merging and dissolving instruction and organization configuration items of the target organization;

[0025] A merging and unmerging module is used to execute the merging and unmerging operation of the target mechanism based on the merging and unmerging operation statement.

[0026] In a possible embodiment, the device further includes:

[0027] A judgment module, configured to judge whether the withdrawal and merger effective date in the withdrawal and merger registration request exceeds a preset date upon receiving the withdrawal and merger registration request from the target institution;

[0028] A determination module, configured to generate the deregistration information of the target institution based on the deregistration registration request when the deregistration effective date exceeds a preset date and it is determined that the target institution and the deregistration receiving institution are legal;

[0029] The registration module is used to fill the merger and closure registration information into the institution merger and closure plan registration form and generate a merger and closure instruction for the target institution.

[0030] In a possible embodiment, the determining module is specifically configured to:

[0031] When it is found that the target institution ID and the withdrawal receiving institution ID in the withdrawal registration request exist in the institution maintenance table, the first institution status of the target institution and the second institution status of the withdrawal receiving institution are respectively obtained; wherein the institution maintenance table contains multiple institution IDs;

[0032] When the first institution status and the second institution status are both not invalid, it is determined that the target institution and the merged receiving institution are legal.

[0033] In a possible embodiment, the merging module is further used for:

[0034] When a closure failure alarm of the target mechanism is detected, obtaining the closure times of the target mechanism, and determining whether the closure times is less than a preset value;

[0035] If yes, then based on the target organization identifier, reacquire the target configuration data related to the target organization from the organization merger and revocation configuration table, and perform the merger and revocation operation of the target organization based on the target configuration data;

[0036] If not, the withdrawal and merger log corresponding to the target organization is obtained, and prompt information is generated based on the withdrawal and merger log; wherein the prompt information includes the withdrawal and merger failure reason and the solution strategy corresponding to the withdrawal and merger failure reason.

[0037] In a third aspect, the present application provides an electronic device, including:

[0038] Memory, used to store computer programs;

[0039] The processor is used to implement the mechanism merging method of the first aspect when executing the computer program stored in the memory.

[0040] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method for merging and dismantling the mechanism according to the first aspect is implemented.

[0041] In a fifth aspect, the present application provides a computer program product, which includes: a computer program code, when the computer program code is run on a computer, it enables the computer to execute the mechanism merging method of the first aspect mentioned above.

[0042] The technical effects that can be achieved in each of the above-mentioned second to fifth aspects and each of the above-mentioned aspects refer to the technical effects that can be achieved in the above-mentioned first aspect or various possible schemes in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 A flowchart of a method for dismantling and merging an organization provided in an embodiment of the present application;

[0044] Figure 2 A flowchart of a method for registering a merger and relocation plan provided in an embodiment of the present application;

[0045] Figure 3 A schematic diagram of the structure of a mechanism merging and dismantling device provided in an embodiment of the present application;

[0046] Figure 4 A schematic diagram of the structure of another mechanism merging and disassembling device provided in an embodiment of the present application;

[0047] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. The specific operating methods in the method embodiments can also be applied to device embodiments or system embodiments. It should be noted that in the description of the present application, "multiple" is understood as "at least two". "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, and A and B exist, and B exists alone. A is connected to B, which can represent: A is directly connected to B and A is connected to B through C. In addition, in the description of the present application, words such as "first" and "second" are only used to distinguish the purpose of description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order.

[0049] In order to facilitate understanding by those skilled in the art, the background technology in the embodiments of the present application is first introduced.

[0050] The main tasks of institutional mergers and reorganizations are to transform functions, adjust division of labor, and improve systems. Common types of mergers and reorganizations are as follows: The first is that branch A1 is directly merged to the superior branch. In this type of merger and reorganization, branch A1 disappears, and its assets and liabilities are incorporated into the superior branch. The second is that branch A2 relocates and changes its name without changing its superior branch. This type of merger and reorganization is further divided into two types: one is to merge to an existing branch B2 at the same level, and the other is to open a new empty branch B2 and then merge A2 to B2.

[0051] Regardless of the method, after the merger or withdrawal of institutions, the data migration of the withdrawn institutions is the primary problem that needs to be solved in the industry. At present, different migration methods are manually configured for the data tables of different withdrawn institutions, so that the withdrawal data can be queried in the corresponding data tables through the query conditions in the migration method, and the withdrawal data can be withdrawn and merged. However, if the query conditions change, the corresponding migration method must be modified, and the modified migration method needs to be tested and deployed; and when a certain attribution table is added or deleted, the corresponding migration method needs to be added or deleted to realize the withdrawal or withdrawal of institutions, which brings cumbersomeness and inconvenience to the subsequent management and maintenance.

[0052] In order to solve the above problems, an embodiment of the present application provides a method for merging and demerging an organization, which generates a merging and demerging operation statement corresponding to the target organization based on the merging and demerging instruction and organization configuration items of the target organization, and executes the merging and demerging operation of the target organization based on the merging and demerging operation statement, which is not only convenient for managing and maintaining the organization configuration items, but also can improve the efficiency of merging and demerging an organization. Among them, the method and the device described in the embodiment of the present application are based on the same technical concept. Since the principles of the problems solved by the method and the device are similar, the embodiments of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0053] To further illustrate the technical solution provided by the embodiment of the present application, this is described in detail below in conjunction with the accompanying drawings and specific implementation methods. Although the embodiment of the present application provides the method operation steps as shown in the following embodiments or drawings, more or fewer operation steps may be included in the method based on routine or no creative labor. In the steps where there is no necessary causal relationship logically, the execution order of these steps is not limited to the execution order provided by the embodiment of the present application. The method may be executed or executed in parallel in the actual processing process or when the device is executed in accordance with the method sequence shown in the embodiment or drawings.

[0054] Figure 1 This is a flow chart of a method for merging and dismantling an organization provided in an embodiment of the present application. The process can be executed by an organization merging and dismantling device, which can be implemented by software, hardware, or a combination of software and hardware. Figure 1 As shown, the process includes the following steps:

[0055] 101: Generate a corresponding merge and withdrawal operation statement of the target organization based on the merge and withdrawal instruction and organization configuration items of the target organization.

[0056] In the embodiment of the present application, in order to facilitate the management and maintenance of the organization merger and closure, the organization merger and closure plan can be first recorded in the organization merger and closure plan registration table, as shown in Table 1, which is an organization merger and closure plan registration table provided in the embodiment of the present application:

[0057]

[0058]

[0059] Table 1: Registration form for merger and closure plan of an institution

[0060] In Table 1, the identifiers can be numbers or names, depending on the specific situation and are not limited here.

[0061] Optional, such as Figure 2 FIG. 1 is a flowchart of a method for registering a merger and relocation plan provided in an embodiment of the present application, which specifically includes the following steps:

[0062] 201: upon receiving a registration withdrawal request from a target institution, determining whether the effective date of the registration withdrawal request exceeds a preset date; if so, proceeding to 202; if not, outputting a first warning message.

[0063] In the embodiment of the present application, since the time of institution merger and closure is generally early in the morning, the merger and closure effective date must be greater than the current date. In this case, the current date can be used as the preset date, or the next date after the current date can be used as the preset date, depending on the specific situation and is not limited here.

[0064] 202: Determine whether the target organization is legal. If so, go to 203; if not, output the second alarm information.

[0065] Specifically, the institution maintenance table is queried to see whether the target institution ID in the registration cancellation and merger request exists; when the target institution ID exists in the institution maintenance table, the first institution status of the target institution is obtained, and when the first institution status is not an invalid state (*), it is determined that the target institution is legal. The institution maintenance table contains multiple institution IDs.

[0066] 203: Determine whether the withdrawn and merged receiving institution corresponding to the target institution is legal. If so, go to 204; if not, output the third alarm information.

[0067] Specifically, the institution maintenance table is queried to determine whether the withdrawal receiving institution identifier in the withdrawal registration request exists; when the withdrawal receiving institution identifier exists in the institution maintenance table, the second institution status of the withdrawal receiving institution is obtained, and when the second institution status is not an invalid state, it is determined that the withdrawal receiving institution is legal.

[0068] 204: Fill the merger and closure registration information into the institution merger and closure plan registration form. As shown in Table 2, this is an institution merger and closure plan registration form for a target institution provided in an embodiment of the present application:

[0069]

[0070] Table 2 Registration form for merger and closure plan of a target institution

[0071] Furthermore, when an unprocessed merger and closure plan is found in the institution merger and closure plan registration table, a corresponding merger and closure instruction is generated based on the merger and closure plan, that is, the merger and closure instruction of the target institution is obtained, and the merger and closure processing status of the target institution in the institution merger and closure plan registration table is updated to being processed (2), wherein the merger and closure instruction includes the target institution identifier and the merger and closure receiving institution identifier corresponding to the target institution.

[0072] In an embodiment of the present application, when there are multiple unprocessed merger and closure plans in the organization merger and closure plan registration table, merger and closure instructions can be obtained through multi-threaded concurrent processing to achieve batch processing of organization merger and closure.

[0073] Further, in order to facilitate the management and maintenance of the organization configuration items, the organization configuration items may also be stored in an organization merger and revocation configuration table; wherein the organization configuration items include at least one merger and revocation field identifier, as shown in Table 3, which is an organization merger and revocation configuration table provided in an embodiment of the present application:

[0074]

[0075]

[0076] Table 3: Configuration table of one type of institution closure and merger

[0077] In Table 3, the data table identifier may be the data table name corresponding to each institution, and there may be multiple ones; the identification field of the institution to be merged may be the branch number field; based on the auxiliary update field, auxiliary update value, condition field and condition value, the data to be revoked may be queried from the corresponding data table, and the corresponding merge and revocation operation may be performed on the data to be revoked; the partition representation is the data storage form, for example, data may be partitioned and stored by day or by week, so that the data to be revoked may be queried in the corresponding data table according to the partition; the operator identifier may be the operator name or the operator number, depending on the specific situation, and is not limited here; the update time represents the generation time of the configuration data corresponding to the institution.

[0078] Thus, based on the target organization's merge and dismantle instruction and organization configuration items, a merge and dismantle operation statement corresponding to the target organization is generated. As shown in Table 3, a target organization merge and dismantle configuration table provided in an embodiment of the present application is shown as follows:

[0079]

[0080] Table 4 A target organization merger and withdrawal configuration table

[0081] Based on Table 4, the first configuration information generates the corresponding merge and withdraw operation statement for the target organization, for example, UPDATE ASET SEND=?, RECORDD_DT=? WHERE SEND=?, the corresponding value is: [00023, 00024, 20240802]. In this statement, UPDATE is used to specify that the table to be updated is A, SET is used to specify the specific update object, and WHERE is used to specify the update condition. Only when the condition is met will it be updated, which improves the security of the data.

[0082] 102: Execute the merge and unmerge operation of the target organization based on the merge and unmerge operation statement.

[0083] In an embodiment of the present application, a Java Database Connectivity (JDBC) method can be called to execute a merger operation statement, obtain target data from the database corresponding to the target organization, and migrate the target data to the merger receiving organization, thereby completing the merger operation of the target organization and updating the merger processing status of the target organization in the organization merger plan registration table to successful processing (1).

[0084] During this process, exceptions may be thrown, usually indicating problems when using JDBC to connect to the database. Here is a brief overview of some common JDBC exceptions and their solutions:

[0085] SQLException: This is the most common JDBC exception, indicating that an error occurred during the database operation; Solution: Check whether the SQL statement is correct, ensure that the database connection information (such as URL, user name, password) is correct, and check whether the network connection is normal. SQLIntegrityConstraintVio lationException: Thrown when the integrity constraint is violated. Solution: Check whether the database uniqueness constraint, foreign key constraint or other constraint is violated.

[0086] Exemplarily, when a target organization's merger failure alarm is detected from the Common Task Manager (CTM), the merger failure count of the target organization is obtained, and it is determined whether the merger failure count is less than a preset value. If so, based on the target organization's identifier, the target configuration data related to the target organization is re-obtained from the organization merger configuration table, and the merger failure operation of the target organization is performed based on the target configuration data; if not, the merger failure log corresponding to the target organization is obtained, and prompt information is generated based on the merger failure log; wherein the prompt information includes the reason for the merger failure and the corresponding solution strategy. The preset value can be 1 or 2, depending on the specific situation, and is not limited here.

[0087] Through the above-mentioned organization merging and demerging method, the configuration data of each of the multiple organizations are stored based on the organization merging and demerging configuration table, which is not only convenient for management and maintenance, but also when the merging and demerging instruction of the target organization is obtained, the target configuration data related to the target organization is queried from the organization merging and demerging configuration table, and a merging and demerging operation statement is generated based on the target configuration data, so that the merging and demerging operation of the target organization is executed based on the merging and demerging operation statement, which can also improve the efficiency of organization merging and demerging.

[0088] Based on the same inventive concept, the embodiment of the present application also provides a mechanism merging device, such as Figure 3 FIG. 1 is a schematic diagram of a structure of a mechanism merging device provided in an embodiment of the present application, the device comprising:

[0089] A generating module 301 is used to generate a corresponding merge and unmerge operation statement of a target organization based on the merge and unmerge instruction and the organization configuration item of the target organization; wherein the organization configuration item includes at least one merge and unmerge field identifier;

[0090] The unmerge module 302 is used to execute the unmerge operation of the target mechanism based on the unmerge operation statement.

[0091] In a possible embodiment, the merging module 302 is further configured to:

[0092] When a target organization's merging failure alarm is detected, the merging times of the target organization are obtained, and it is determined whether the merging times are less than a preset value;

[0093] If yes, then based on the target organization identifier, reacquire the target organization-related target configuration data from the organization merger and revocation configuration table, and perform the merger and revocation operation of the target organization based on the target configuration data;

[0094] If not, the corresponding merger and closure log of the target organization is obtained, and prompt information is generated based on the merger and closure log; wherein the prompt information includes the merger and closure failure reason and the corresponding solution strategy of the merger and closure failure reason.

[0095] In other embodiments, in addition to the above Figure 3 In addition to the modules shown in FIG. 1 , it may further include a judgment module, a determination module and a registration module, such as Figure 4 , which is a schematic diagram of another mechanism merging and dismantling device provided in an embodiment of the present application. The device comprises: a generating module 301 , a dismantling and dismantling module 302 , a judging module 401 , a determining module 402 and a registering module 403 .

[0096] The judgment module 401 is used to judge whether the withdrawal and merger effective date in the withdrawal and merger registration request exceeds a preset date when receiving the withdrawal and merger registration request from the target institution;

[0097] The determination module 402 is used to generate the target institution's deregistration information based on the deregistration registration request when the deregistration effective date exceeds the preset date and it is determined that the target institution and the deregistration receiving institution are legal;

[0098] The registration module 403 is used to fill the merger and closure registration information into the institution merger and closure plan registration form and generate a merger and closure instruction for the target institution.

[0099] In a possible embodiment, the determining module 402 is specifically configured to:

[0100] When it is found that the target institution ID and the withdrawn institution ID in the withdrawal registration request exist in the institution maintenance table, the first institution status of the target institution and the second institution status of the withdrawn institution are respectively obtained; wherein the institution maintenance table contains multiple institution IDs;

[0101] When both the first institution status and the second institution status are not invalid, it is determined that the target institution and the merged receiving institution are legal.

[0102] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0103] Based on the same inventive concept, an electronic device is also provided in the embodiment of the present application, and the electronic device can realize the function of the aforementioned mechanism merging device, referring to Figure 5, the electronic device comprises:

[0104] At least one processor 501, and a memory 502 connected to the at least one processor 501. The specific connection medium between the processor 501 and the memory 502 is not limited in the embodiment of the present application. Figure 5 In the example, the processor 501 and the memory 502 are connected via a bus 500. The bus 500 is Figure 5 The connections between other components are shown in bold lines, and are not intended to be limiting. The bus 500 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. Alternatively, the processor 501 can also be called a controller, and there is no limitation on the name.

[0105] In the embodiment of the present application, the memory 502 stores instructions that can be executed by at least one processor 501. The at least one processor 501 can execute the mechanism merging method discussed above by executing the instructions stored in the memory 502. The processor 501 can implement Figure 3 Or the functions of each module in the device shown in 4.

[0106] Among them, the processor 501 is the control center of the device, and can use various interfaces and lines to connect the various parts of the entire control device. By running or executing instructions stored in the memory 502 and calling data stored in the memory 502, the various functions of the device and processing data, the device can be monitored as a whole.

[0107] In one possible design, the processor 501 may include one or more processing units, and the processor 501 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the modem processor may not be integrated into the processor 501. In some embodiments, the processor 501 and the memory 502 may be implemented on the same chip, and in some embodiments, they may also be implemented separately on separate chips.

[0108] The processor 501 may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the mechanism merging method disclosed in the embodiments of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0109] The memory 502 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 502 may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (Random Access Memory, RAM), a static random access memory (Static Random Access Memory, SRAM), a programmable read-only memory (Programmable Read Only Memory, PROM), a read-only memory (Read Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic memory, a disk, an optical disk, etc. The memory 502 is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory 502 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0110] By programming the processor 501, the code corresponding to the mechanism merging method described in the above embodiment can be fixed into the chip, so that the chip can execute the code when running. Figure 1 The steps of the mechanism merging method of the embodiment shown are as follows: How to design and program the processor 501 is a technique known to those skilled in the art and will not be described in detail here.

[0111] Based on the same inventive concept, an embodiment of the present disclosure provides a computer storage medium, the computer storage medium comprising: a computer program code, when the computer program code is executed on a computer, the computer executes any one of the mechanism merging and dismantling methods discussed above. Since the principle of solving the problem by the above-mentioned computer storage medium is similar to that of a mechanism merging and dismantling method, the implementation of the above-mentioned computer storage medium can refer to the implementation of the method, and the repeated parts will not be repeated.

[0112] In the specific implementation process, the computer storage medium may include: Universal Serial Bus Flash Drive (USB), mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and other storage media that can store program codes.

[0113] Based on the same inventive concept, the embodiment of the present disclosure also provides a computer program product, which includes: computer program code, when the computer program code is run on a computer, the computer executes any one of the mechanism merging and dismantling methods discussed above. Since the principle of solving the problem by the above computer program product is similar to that of a mechanism merging and dismantling method, the implementation of the above computer program product can refer to the implementation of the method, and the repeated parts will not be repeated.

[0114] The computer program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more conductors, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0115] The method in the present application can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the present application is executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, a core network device, an OAM or other programmable device.

[0116] The computer program or instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; it may also be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.

[0117] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.

[0118] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that has the functions specified in one or more boxes.

[0119] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0120] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0121] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A method of withdrawing and merging institutions. It is characterized in that The method comprises: Generate a merging and unmerging operation statement corresponding to the target organization based on the merging and unmerging instruction and organization configuration item of the target organization; wherein the organization configuration item includes at least one merging and unmerging field identifier; The unmerge operation of the target mechanism is executed based on the unmerge operation statement.

2. The method according to claim 1, It is characterized in that Before generating the merging and unmerging operation statement corresponding to the target organization based on the merging and unmerging instruction of the target organization and the organization configuration item, the method further includes: Upon receiving the registration withdrawal request of the target institution, determining whether the effective date of the registration withdrawal request exceeds a preset date; When the withdrawal and merger effective date exceeds a preset date and it is determined that the target institution and the withdrawal and merger receiving institution are legitimate, generating the withdrawal and merger registration information of the target institution based on the withdrawal and merger registration request; The merger and closure registration information is filled into the institution merger and closure plan registration form, and a merger and closure instruction of the target institution is generated.

3. The method according to claim 2, It is characterized in that The determining that the target institution and the merged receiving institution are legal includes: When it is found that the target institution ID and the withdrawal receiving institution ID in the withdrawal registration request exist in the institution maintenance table, the first institution status of the target institution and the second institution status of the withdrawal receiving institution are respectively obtained; wherein the institution maintenance table contains multiple institution IDs; When the first institution status and the second institution status are both not invalid, it is determined that the target institution and the merged receiving institution are legal.

4. The method according to claim 1, It is characterized in that The method further comprises: When a closure failure alarm of the target mechanism is detected, obtaining the closure times of the target mechanism, and determining whether the closure times is less than a preset value; If yes, then based on the target organization identifier, reacquire the target configuration data related to the target organization from the organization merger and revocation configuration table, and perform the merger and revocation operation of the target organization based on the target configuration data; If not, the withdrawal and merger log corresponding to the target organization is obtained, and prompt information is generated based on the withdrawal and merger log; wherein the prompt information includes the withdrawal and merger failure reason and the solution strategy corresponding to the withdrawal and merger failure reason.

5. A mechanism merging and dismantling device, It is characterized in that The device comprises: A generation module, used to generate a merging and unmerging operation statement corresponding to the target organization based on the merging and unmerging instruction and organization configuration items of the target organization; wherein the organization configuration items include at least one merging and unmerging field identifier; A merging and unmerging module is used to execute the merging and unmerging operation of the target mechanism based on the merging and unmerging operation statement.

6. The device as claimed in claim 5, It is characterized in that The device also includes: A judgment module, configured to judge whether the withdrawal and merger effective date in the withdrawal and merger registration request exceeds a preset date upon receiving the withdrawal and merger registration request from the target institution; A determination module, configured to generate the deregistration information of the target institution based on the deregistration registration request when the deregistration effective date exceeds a preset date and it is determined that the target institution and the deregistration receiving institution are legal; The registration module is used to fill the merger and closure registration information into the institution merger and closure plan registration form and generate a merger and closure instruction for the target institution.

7. The device according to claim 5, It is characterized in that The withdrawing and merging module is also used for: When a closure failure alarm of the target mechanism is detected, obtaining the closure times of the target mechanism, and determining whether the closure times is less than a preset value; If yes, then based on the target organization identifier, reacquire the target configuration data related to the target organization from the organization merger and revocation configuration table, and perform the merger and revocation operation of the target organization based on the target configuration data; If not, the withdrawal and merger log corresponding to the target organization is obtained, and prompt information is generated based on the withdrawal and merger log; wherein the prompt information includes the withdrawal and merger failure reason and the solution strategy corresponding to the withdrawal and merger failure reason.

8. An electronic device, It is characterized in that include: Memory, used to store computer programs; A processor, configured to implement the method according to any one of claims 1 to 4 when executing the computer program stored in the memory.

9. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.

10. A computer program product, It is characterized in that The computer program product comprises: a computer program code, and when the computer program code is run on a computer, the computer is caused to execute the method according to any one of claims 1 to 4.