An automatic network point consolidation method and device based on a data warehouse

The automated data warehouse branch closure and consolidation method and device solves the problem of low processing efficiency in bank data warehouse systems during branch closure and consolidation, achieving efficient closure and consolidation operations, reducing manual intervention, and improving system stability and efficiency.

CN114840481BActive Publication Date: 2026-02-06INDUSTRIAL AND COMMERCIAL BANK OF CHINA
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210534363.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-05-17
Publication Date
2026-02-06
Estimated Expiration
2042-05-17

AI Technical Summary

Technical Problem

In existing technologies, bank data warehouse systems require manual intervention when branches are closed or merged, resulting in low processing efficiency and affecting the user experience for business personnel.

Method used

An automated branch closure and consolidation method and apparatus based on a data warehouse is provided. By scanning the job configuration file, the closure and consolidation comparison and initial storage files are loaded into the temporary storage area, and the basic layer data tables of the data warehouse are updated based on these files to perform the addition and storage merging process, reducing manual intervention.

Benefits of technology

It enables timely processing of branch closures and mergers, improves the efficiency of branch closures and mergers, reduces manual intervention, and enhances the robustness and processing efficiency of the data warehouse system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114840481B_ABST
    Figure CN114840481B_ABST
Patent Text Reader

Abstract

The application provides an automatic network point withdrawal method and device based on a data warehouse, which can be used in the field of finance or other technical fields. The method comprises the following steps: scanning a shared disk of the data warehouse according to a job configuration file; wherein the job configuration file is preset; if a withdrawal contrast file is scanned, loading the withdrawal contrast file to a temporary storage area of the data warehouse; if a withdrawal first storage file is scanned, loading the withdrawal first storage file and a withdrawal data file to the temporary storage area of the data warehouse; wherein the withdrawal data file is obtained in advance; updating a basic layer data table of the data warehouse based on the withdrawal contrast file, and performing an incremental storage quantity merging processing based on the withdrawal data file and the withdrawal first storage file, so as to complete a withdrawal job processing. The device is used for executing the above method. The automatic network point withdrawal method and device based on the data warehouse provided by the embodiment of the application improve the efficiency of network point withdrawal.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, in particular to an automatic branch merging method and device based on a data warehouse. BACKGROUND

[0002] With the development and change of banking business, the layout of bank branches will also change. In the process of operation and development, each institution will continuously optimize and adjust the layout of branches according to strategic deployment and management needs.

[0003] The bank will merge some branches according to the needs of external economic development, internal management requirements, etc. Branch merging refers to the process of migrating the business of the original branch to the new branch without affecting the customers according to the business migration principle. The bank data warehouse system needs to update the data when the branch is merged. In the prior art, the processing of branch merging data requires the bank data warehouse system to stop batch processing, and the developers manually intervene in the processing, which is time-consuming and inefficient, affecting the user experience of business personnel. SUMMARY

[0004] To solve the problems in the prior art, the embodiments of the present application provide an automatic branch merging method and device based on a data warehouse, which can at least partially solve the problems in the prior art.

[0005] In one aspect, the present application provides an automatic branch merging method based on a data warehouse, comprising:

[0006] scanning the shared disk of the data warehouse according to a job configuration file; wherein the job configuration file is preset;

[0007] if a merging reference file is scanned, loading the merging reference file to the temporary storage area of the data warehouse;

[0008] if a merging first storage file is scanned, loading the merging first storage file and the merging data file to the temporary storage area of the data warehouse; wherein the merging data file is obtained in advance;

[0009] updating the basic layer data table of the data warehouse based on the merging reference file, and performing incremental merging processing based on the merging data file and the merging first storage file to complete the merging job processing.

[0010] In another aspect, the present application provides an automatic branch merging device based on a data warehouse, comprising:

[0011] a scanning module for scanning the shared disk of the data warehouse according to a job configuration file; wherein the job configuration file is preset;

[0012] The first loading module is configured to load the merger-contrasted file to a temporary storage area of the data warehouse if the merger-contrasted file is scanned.

[0013] The second loading module is configured to load the merger-data file and the merger-initial file to the temporary storage area of the data warehouse if the merger-initial file is scanned.

[0014] The job module is configured to update the basic layer data table of the data warehouse based on the merger-contrasted file, and perform the incremental storage quantity merging processing based on the merger-data file and the merger-initial file to complete the merger job processing.

[0015] In another aspect, the present application provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the data warehouse-based automated branch merger method according to any one of the above embodiments when executing the program.

[0016] In another aspect, the present application provides a computer readable storage medium having a computer program stored thereon, wherein the computer program is executable on a processor to implement the data warehouse-based automated branch merger method according to any one of the above embodiments.

[0017] The data warehouse-based automated branch merger method and device provided by the embodiments of the present application can scan the shared disk of the data warehouse according to the job configuration file, load the merger-contrasted file to the temporary storage area of the data warehouse if the merger-contrasted file is scanned, load the merger-data file and the merger-initial file to the temporary storage area of the data warehouse if the merger-initial file is scanned, update the basic layer data table of the data warehouse based on the merger-contrasted file, and perform the incremental storage quantity merging processing based on the merger-data file and the merger-initial file to complete the merger job processing, so that the merger job processing can be performed in time, the manual participation is reduced, and the efficiency of the branch merger is improved. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without any creative effort. In the drawings:

[0019] Figure 1 is a flowchart of the data warehouse-based automated branch merger method provided by the first embodiment of the present application.

[0020] Figure 2is a flowchart of the data warehouse-based automatic network point merger method provided by the second embodiment of the present application.

[0021] Figure 3 is a flowchart of the data warehouse-based automatic network point merger method provided by the third embodiment of the present application.

[0022] Figure 4 is a flowchart of the data warehouse-based automatic network point merger method provided by the fourth embodiment of the present application.

[0023] Figure 5 is a structural diagram of the data warehouse-based automatic network point merger device provided by the fifth embodiment of the present application.

[0024] Figure 6 is a structural diagram of the data warehouse-based automatic network point merger device provided by the sixth embodiment of the present application.

[0025] Figure 7 is a structural diagram of the data warehouse-based automatic network point merger device provided by the seventh embodiment of the present application.

[0026] Figure 8 is a structural diagram of the data warehouse-based automatic network point merger device provided by the eighth embodiment of the present application.

[0027] Figure 9 is a structural diagram of the data warehouse-based automatic network point merger device provided by the ninth embodiment of the present application.

[0028] Figure 10 is a structural diagram of the data warehouse-based automatic network point merger device provided by the tenth embodiment of the present application.

[0029] Figure 11 is a structural diagram of the electronic device provided by the eleventh embodiment of the present application. DETAILED DESCRIPTION

[0030] To make the objects, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application are further described in detail below with reference to the drawings. Herein, the schematic embodiments of the present application and the descriptions thereof are used to explain the present application, but not as a limitation to the present application. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other at will.

[0031] To facilitate the understanding of the technical solutions provided by the present application, the related contents of the technical solutions of the present application are described first below.

[0032] Net point merger: the net point merger refers to a process of completing migration of original net point business to a new net point according to a business migration principle. In the embodiment of the present application, the original net point is referred to as a merger net point, and the new net point migrated to is referred to as a merged net point.

[0033] Data warehouse: the data warehouse is a subject-oriented, integrated, relatively stable, historical change reflecting data set, which can provide data support for business analysis and management decision.

[0034] Figure 1 is a flowchart of the data warehouse-based automatic net point merger method provided by the first embodiment of the present application, as Figure 1 indicated, the data warehouse-based automatic net point merger method provided by the embodiment of the present application comprises:

[0035] S101, scanning a shared disk of a data warehouse according to a job configuration file; wherein the job configuration file is preset;

[0036] Specifically, the batch scheduling server scans the shared disk of the data warehouse every day, and scans whether there is a merger comparison file and a merger first storage file of a net point in the data warehouse according to a job configuration file. The job configuration file is preset, and includes a scanning file list, and the scanning file list includes the merger comparison file and the merger first storage file to be scanned.

[0037] Wherein, after the net point merger, the net point platform business server will send the merger comparison file, the merger data file and the merger first storage file of the net point to the shared disk of the data warehouse. If the bank net point determines to need to be merged, but has not completed the merger, then an empty merger comparison file will be sent to the shared disk of the data warehouse every day, and the merger data file can also be sent to the shared disk of the data warehouse at the same time. The merger comparison file includes a net point migration net point number comparison file and a net point merger comparison file, and specifically relates to information such as accounts with the merger net point as an opening net point, accounts with the merger net point as a billing net point, and customers with the merger net point as a belonging net point. The merger first storage file includes first storage data of accounts and agreements related to deposits and loans. The merger data file includes daily data related to deposits, loans and the like of the net point.

[0038] S102, if the merger comparison file is scanned, loading the merger comparison file to a temporary storage area of the data warehouse;

[0039] Specifically, the batch scheduling server will load the scanned merger countercheck file to the temporary storage area of the data warehouse if the merger countercheck file is scanned in the shared disk of the data warehouse, so as to obtain relevant data for subsequent merger job. The merger countercheck file includes the change information of branch information, i.e. the information that needs to be changed when the merger branch is merged into the incorporated branch, and can be used to update the opening branch of the account, the account account branch, and the customer's belonging branch information in the data warehouse. The merger branch is the branch that is subjected to merger, and the incorporated branch is the branch that merges the merger branch.

[0040] S103, if the merger first storage file is scanned, load the merger first storage file and the merger data file to the temporary storage area of the data warehouse; wherein the merger data file is obtained in advance;

[0041] Specifically, the batch scheduling server will load the merger first storage file and the merger data file to the temporary storage area of the data warehouse if the merger first storage file is scanned in the data warehouse. The merger data file is obtained in advance by the batch scheduling server. The merger first storage file includes the first storage data of the relevant accounts generated by the deposit and loan business of the merger branch. The merger first storage file is the file sent by the merger branch to the shared disk of the data warehouse when the merger is completed.

[0042] S104, update the basic layer data table of the data warehouse based on the merger countercheck file, and perform the increase storage amount merging processing based on the merger data file and the merger first storage file to complete the merger job processing.

[0043] Specifically, the batch scheduling server will update the basic layer data table of the data warehouse based on the merger countercheck file. The basic layer data table records the relevant information of each branch, including the opening branch of the customer account, the account branch, and the customer's belonging branch information. The relevant information of the merger branch in the basic layer data table can be updated to the relevant information of the incorporated branch based on the change information of the branch information included in the merger countercheck file. The batch scheduling server will perform the increase storage amount merging processing based on the merger data file and the merger first storage file, i.e. merging the deposit, loan and other business data included in the merger first storage file and the merger countercheck file. After the update of the basic layer data table and the increase storage amount merging processing are completed, the merger job processing is completed. The specific process of the increase storage amount merging processing and the specific process of updating the basic layer data table are prior art, which will not be described here.

[0044] For example, after loading the merger contrast file to the temporary storage area of the data warehouse, the merger base layer job loading can be automatically identified and triggered when the merger base layer job is performed, and the information related to the merger branch of the data warehouse base layer data table is updated based on the change information of the branch information included in the merger contrast file.

[0045] For example, the batch scheduling server can scan the merger first storage file by the first storage loading tool every day, and after scanning the merger first storage file, trigger the first storage tool to perform the incremental storage quantity merging processing based on the merger first storage file and the merger data file, and set the base layer loading job state to 0, so that the base layer cannot load other merger jobs. After completing the current merger job, the base layer loading job state is set to 1, and other merger jobs can be loaded.

[0046] The automatic branch merger method based on the data warehouse provided by the embodiment of the application can scan the shared disk of the data warehouse according to the job configuration file, load the merger contrast file to the temporary storage area of the data warehouse if the merger contrast file is scanned, load the merger first storage file and the merger data file to the temporary storage area of the data warehouse if the merger first storage file is scanned, update the base layer data table of the data warehouse based on the merger contrast file, and perform the incremental storage quantity merging processing based on the merger data file and the merger first storage file to complete the merger job processing. The merger job processing can be performed in time, the manual participation is reduced, and the efficiency of the branch merger is improved.

[0047] Figure 2 is the flowchart of the automatic branch merger method based on the data warehouse provided by the second embodiment of the application, as shown in Figure 2 Before updating the base layer data table of the data warehouse based on the merger contrast file and performing the incremental storage quantity merging processing based on the merger data file and the merger first storage file to complete the merger job processing, the method further includes:

[0048] S201, performing merger preprocessing based on the merger contrast file, the merger data file and the merger first storage file to obtain a merger preprocessing result.

[0049] Specifically, in order to ensure the reliability of the merger processing, the batch scheduling server can perform the merger preprocessing on the merger contrast file, the merger data file and the merger first storage file, that is, when updating the base layer data table based on the merger contrast file, the update result is temporarily stored, and when performing the incremental storage quantity merging processing based on the merger data file and the merger first storage file, the incremental storage quantity merging processing result is also temporarily stored, and a merger preprocessing result is obtained.

[0050] S202, verifying the merger preprocessing result.

[0051] Specifically, the batch scheduling server verifies the merger-preprocessing result, if the merger-preprocessing result cannot pass the verification, an error prompt can be given, and no merger job is performed; if the merger-preprocessing result passes the verification, a merger job can be performed.

[0052] For example, the updated base layer data table in the merger-preprocessing result and the incremental storage merging processing result are stored in the form of data tables, whether there is the same primary key data in the merger-preprocessing result can be queried, if there is the same primary key data, it indicates that the primary key data is repeated, and the data has a problem, and the merger-preprocessing result cannot pass the verification. If there is no same primary key data, the merger-preprocessing result passes the verification.

[0053] On the basis of the above embodiments, further, the automatic branch merger method based on a data warehouse provided by the embodiments of the present application further comprises:

[0054] If the merger comparison file is scanned and the merger comparison file is empty, the merger comparison file is empty loaded.

[0055] Specifically, before the merger is completed, the branch can send an empty merger comparison file to the shared disk of the data warehouse every day. If the batch scheduling server scans the merger comparison file and the merger comparison file is empty, the merger comparison file is empty loaded, that is, the action of loading the merger comparison file is performed, but the base layer data table of the data warehouse is not updated. The empty merger comparison file is used to ensure that the merger comparison business can be normally triggered, and manual participation is avoided.

[0056] On the basis of the above embodiments, further, the automatic branch merger method based on a data warehouse provided by the embodiments of the present application further comprises:

[0057] If the merger data file is scanned, the merger data file is stored.

[0058] Specifically, before the merger is completed, the branch can send a merger data file to the shared disk of the data warehouse every day. If the batch scheduling server scans the merger data file, the merger data file is stored, so as to be loaded when the merger first storage file is scanned subsequently.

[0059] On the basis of the above embodiments, further, the updating of the base layer data table of the data warehouse based on the merger comparison file comprises:

[0060] According to the merger comparison file, the base data table is changed from the merger branch as the opening branch, the account's account branch and the customer's belonging branch to the merger branch as the opening branch, the account's account branch and the customer's belonging branch.

[0061] Specifically, the batch scheduling server changes the merger site recorded in the basic data table as an opening site into an incorporated site according to the merger site and the incorporated site recorded in the merger counter file, changes the merger site recorded in the basic data table as a customer's account site into an incorporated site, and changes the merger site recorded in the locomotive data table as a customer's affiliated site into an incorporated site, thereby updating the basic layer data table.

[0062] Figure 3 is a flowchart of an automatic merger site merger method based on a data warehouse provided by the third embodiment of the present application, as shown in Figure 3 Further, the incremental storage quantity merging processing based on the merger data file and the merger first storage file includes the following steps:

[0063] S301, merging the merger data file and the merger first storage file to obtain the merged first storage data;

[0064] Specifically, the batch scheduling server merges the merger data file and the merger first storage file to obtain the merged first storage data. The merged first storage data stores data in the form of a data table, including each primary key and the data corresponding to the primary key.

[0065] S302, if it is determined that the merged first storage data does not have duplicate primary keys, the incremental storage quantity merging processing is completed.

[0066] Specifically, the batch scheduling server searches the merged first storage data for duplicate primary keys. If there are no duplicate primary keys, the merged first storage data is correct, and the incremental storage quantity merging processing is completed. If there are duplicate primary keys, the merged first storage data is incorrect, and the job is interrupted and a data error prompt is given.

[0067] Further, the automatic merger site merger method based on a data warehouse provided by the embodiments of the present application further includes the following steps:

[0068] If it is determined that the merged first storage data has duplicate primary keys, the corresponding job is interrupted and a data error prompt is given.

[0069] Specifically, if the batch scheduling server searches the merged first storage data and finds two identical primary keys, it is determined that there are duplicate primary keys, indicating that the data is incorrect, and the corresponding job is interrupted and a data error prompt is given.

[0070] The implementation process of the automatic merger site merger method based on a data warehouse provided by the embodiments of the present application will be described below with reference to a specific embodiment, as shown in Figure 4 .

[0071] The first step is to send the withdrawal file. The withdrawal point platform service server of the withdrawal point sends the withdrawal comparison file, the withdrawal data file and the withdrawal first storage file to the shared disk of the data warehouse.

[0072] The second step is to scan the shared disk. The batch scheduling server scans the shared disk of the data warehouse according to the job configuration file every day.

[0073] The third step is to determine whether the withdrawal file is scanned. If the batch scheduling server scans the withdrawal comparison file, it enters the fourth step; if it scans the withdrawal first storage file, it enters the sixth step; if it scans the empty withdrawal comparison file, it enters the eighth step.

[0074] The fourth step is to load the withdrawal comparison file. The batch scheduling server loads the withdrawal comparison file to the temporary storage area of the data warehouse for subsequent withdrawal job.

[0075] The fifth step is to load the withdrawal first storage file. The batch scheduling server loads the withdrawal first storage file and the withdrawal data file to the temporary storage area of the data warehouse.

[0076] The sixth step is withdrawal preprocessing. After the withdrawal comparison file, the withdrawal first storage file and the withdrawal data file are loaded, the batch scheduling server performs withdrawal preprocessing based on the withdrawal comparison file, the withdrawal data file and the withdrawal first storage file, obtains the withdrawal preprocessing result, and verifies the withdrawal preprocessing result. After the verification is passed, it enters the seventh step; if the preprocessing result is not verified, the job is aborted and a data error prompt is given.

[0077] The seventh step is to perform the actual withdrawal job. The batch scheduling server updates the basic layer data table, updates the basic layer data table according to the withdrawal comparison file, changes the related information of the withdrawal point to the corresponding information of the incorporated point in the basic layer data table, and performs the incremental storage quantity merging processing based on the withdrawal data file and the withdrawal first storage file to complete the withdrawal job.

[0078] The eighth step is to load the empty withdrawal comparison file. The batch scheduling server loads the empty withdrawal comparison file to the temporary storage area of the data warehouse, but does not update the basic layer data table.

[0079] The method for automatically merging bank branches based on a data warehouse can effectively improve the timeliness of branch merging when the bank frequently proposes branch merging requirements; real-time monitoring of the execution of the merging task can timely process the merging files, solve the risk that the data warehouse batch task cannot be completed in time due to manual processing of the branch merging, and improve the robustness of the data warehouse system and the processing efficiency of the merging operation. The user only needs to maintain the file list and session information of the merging operation in the first storage tool, and does not need to manually process the loading of the merging comparison file and the merging first storage file, thereby greatly reducing the operation and maintenance cost and difficulty.

[0080] Figure 5 is a structural schematic diagram of the device for automatically merging bank branches based on a data warehouse provided by the fifth embodiment of the present application, as Figure 5 indicated, the device for automatically merging bank branches based on a data warehouse provided by the embodiment of the present application comprises a scanning module 501, a first loading module 502, a second loading module 503 and an operation module 504, wherein:

[0081] The scanning module 501 is used for scanning the shared disk of the data warehouse according to the operation configuration file; wherein the operation configuration file is preset; the first loading module 502 is used for loading the merging comparison file to the temporary storage area of the data warehouse if the merging comparison file is scanned; the second loading module 503 is used for loading the merging first storage file and the merging data file to the temporary storage area of the data warehouse if the merging first storage file is scanned; wherein the merging data file is obtained in advance; and the operation module 504 is used for updating the basic layer data table of the data warehouse based on the merging comparison file, and performing the incremental storage quantity merging processing based on the merging data file and the merging first storage file, so as to complete the merging operation processing.

[0082] Specifically, the scanning module 501 scans the shared disk of the data warehouse every day, and scans whether there are merging comparison files and merging first storage files of the branches in the data warehouse according to the operation configuration file. Wherein the operation configuration file is preset, and includes a scanning file list, the scanning file list includes the merging comparison files and the merging first storage files that need to be scanned.

[0083] If the first loading module 502 scans the merging comparison file in the shared disk of the data warehouse, the scanned merging comparison file will be loaded to the temporary storage area of the data warehouse, so as to obtain the related data for subsequent merging operation. Wherein the merging comparison file includes the change information of the branch information, that is, the information that needs to be changed when the merging branch is merged into the merged branch, and can be used to update the opening branch information, the account accounting branch information and the customer's belonging branch information in the data warehouse. The merging branch is the branch that is subjected to merging, and the merged branch is the branch that merges the merging branch.

[0084] The second loading module 503 loads the merger data file and the merger first deposit file to the temporary storage area of the data warehouse if the merger first deposit file is scanned in the shared disk of the data warehouse. The merger data file is obtained in advance. The merger first deposit file includes the first deposit data of the merger branch generated by the deposit and loan business of the merger branch. The merger first deposit file is the file sent to the shared disk of the data warehouse by the merger branch when the merger is completed.

[0085] The job module 504 updates the basic layer data table of the data warehouse based on the merger reference file. The basic layer data table records the relevant information of each branch, including the opening branch of the customer account, the account branch, and the information of the customer belonging to the branch. The relevant information of the merger branch in the basic layer data table can be updated to the relevant information of the merged branch based on the change information of the branch information included in the merger reference file. The job module 504 performs the incremental deposit merging processing based on the merger data file and the merger first deposit file, that is, the deposit, loan and other business data included in the merger first deposit file and the merger reference file are merged. After the basic layer data table is updated and the incremental deposit merging processing is completed, the merger job processing is completed. The specific process of the incremental deposit merging processing and the specific process of updating the basic layer data table are prior art, which will not be described here.

[0086] The automatic branch merger device based on the data warehouse provided by the embodiment of the application can scan the shared disk of the data warehouse according to the job configuration file. If the merger reference file is scanned, the merger reference file is loaded to the temporary storage area of the data warehouse. If the merger first deposit file is scanned, the merger first deposit file and the merger data file are loaded to the temporary storage area of the data warehouse. The basic layer data table of the data warehouse is updated based on the merger reference file. The incremental deposit merging processing is performed based on the merger data file and the merger first deposit file, so as to complete the merger job processing. The merger job processing can be performed in time, the manual participation is reduced, and the efficiency of the branch merger is improved.

[0087] Figure 6 The structure schematic diagram of the automatic branch merger device based on the data warehouse provided by the sixth embodiment of the application is shown in FIG. 6. Based on the above embodiments, further, the automatic branch merger device based on the data warehouse provided by the embodiment of the application further includes a preprocessing module 505 and a verification module 506. Figure 6

[0088] The preprocessing module 505 is used for performing the merger preprocessing based on the merger reference file, the merger data file and the merger first deposit file, and obtaining the merger preprocessing result. The verification module 506 is used for verifying the merger preprocessing result.

[0089] Figure 7 ​is a structure schematic view of the automatic network point merger device based on a data warehouse provided by the seventh embodiment of the present application, as shown in the figure, on the basis of the above embodiments, further, the automatic network point merger device based on a data warehouse provided by the embodiment of the present application further comprises: Figure 7

[0090] The empty loading module 507 is used for empty loading the merger reference file if the merger reference file is scanned and the merger reference file is empty.

[0091] Figure 8 is a structure schematic view of the automatic network point merger device based on a data warehouse provided by the eighth embodiment of the present application, as shown in the figure, on the basis of the above embodiments, further, the automatic network point merger device based on a data warehouse provided by the embodiment of the present application further comprises: Figure 8

[0092] The storage module 508 is used for storing the merger data file if the merger data file is scanned.

[0093] On the basis of the above embodiments, further, the job module 504 is specifically used for:

[0094] According to the merger reference file, the account opening network point, the account's account network point and the customer's belonging network point corresponding to the merger network point in the basic data table are changed to the merger network point.

[0095] Figure 9 is a structure schematic view of the automatic network point merger device based on a data warehouse provided by the ninth embodiment of the present application, as shown in the figure, on the basis of the above embodiments, further, the job module 504 comprises a data merging unit 5041 and a judging unit 5042, wherein: Figure 9

[0096] The data merging unit 5041 is used for merging the merger data file and the merger first storage file to obtain the merged first storage data; the judging unit 5042 judges that the merged first storage data does not exist primary key duplication, and then completes the increase storage amount merging processing.

[0097] Figure 10 is a structure schematic view of the automatic network point merger device based on a data warehouse provided by the tenth embodiment of the present application, as shown in the figure, on the basis of the above embodiments, further, the job module 504 further comprises: Figure 10

[0098] The prompt unit 5043 is used for interrupting the corresponding job and prompting data error if it is judged that the merged first storage data exists primary key duplication.

[0099] ​​​​The device provided by the embodiments of the present application can be specifically used for executing the processing procedures of the above-mentioned method embodiments, and the functions thereof will not be repeated here, and the detailed description can be referred to the above-mentioned method embodiments.

[0100] It should be noted that the method and device for automatically merging network points based on a data warehouse provided by the embodiments of the present application can be used in the financial field, and can also be used in any technical field other than the financial field, and the application field of the method and device for automatically merging network points based on a data warehouse is not limited by the embodiments of the present application.

[0101] Figure 11 is the schematic diagram of the physical structure of the electronic device provided by the eleventh embodiment of the present application, as shown in Figure 11 The electronic device can include a processor 1101, a communications interface 1102, a memory 1103 and a communications bus 1104, wherein the processor 1101, the communications interface 1102 and the memory 1103 complete mutual communication through the communications bus 1104. The processor 1101 can invoke the logical instructions in the memory 1103 to execute the following method: scanning a shared disk of a data warehouse according to a job configuration file; wherein the job configuration file is preset; if a merging reference file is scanned, loading the merging reference file to a temporary storage area of the data warehouse; if a merging first storage file is scanned, loading the merging first storage file and a merging data file to the temporary storage area of the data warehouse; wherein the merging data file is obtained in advance; updating a basic layer data table of the data warehouse based on the merging reference file, and performing an incremental storage quantity merging processing based on the merging data file and the merging first storage file to complete a merging job processing.

[0102] In addition, the logical instructions in the memory 1103 described above can be implemented in the form of a software function unit and sold or used as an independent product, which can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or part of the technical solutions can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a plurality of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0103] The embodiment discloses a computer program product, the computer program product comprises a computer program stored on a non-transitory computer readable storage medium, the computer program comprises program instructions, when the program instructions are executed by a computer, the computer can execute the method provided by each method embodiment, for example, comprising: scanning a shared disk of a data warehouse according to a job configuration file; wherein the job configuration file is preset; if a merger contrast file is scanned, loading the merger contrast file to a temporary storage area of the data warehouse; if a merger first storage file is scanned, loading the merger first storage file and a merger data file to the temporary storage area of the data warehouse; wherein the merger data file is obtained in advance; updating a basic layer data table of the data warehouse based on the merger contrast file, and performing an incremental storage quantity merging processing based on the merger data file and the merger first storage file, to complete a merger job processing.

[0104] The embodiment provides a computer readable storage medium, the computer readable storage medium stores a computer program, the computer program enables the computer to execute the method provided by each method embodiment, for example, comprising: scanning a shared disk of a data warehouse according to a job configuration file; wherein the job configuration file is preset; if a merger contrast file is scanned, loading the merger contrast file to a temporary storage area of the data warehouse; if a merger first storage file is scanned, loading the merger first storage file and a merger data file to the temporary storage area of the data warehouse; wherein the merger data file is obtained in advance; updating a basic layer data table of the data warehouse based on the merger contrast file, and performing an incremental storage quantity merging processing based on the merger data file and the merger first storage file, to complete a merger job processing.

[0105] Those skilled in the art will understand that embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage media, etc.) having computer usable program code embodied therein.

[0106] The present application is described with reference to flowcharts and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams 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 apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus produce a means for implementing the functions specified in the flowcharts and / or block diagrams. These computer program instructions can also be stored in a computer-usable storage medium that can direct a computer or other programmable data processing apparatus to function in a specific manner, such that the instructions stored in the computer-usable storage medium produce a product including an article of manufacture (including anFigure 1 apparatuses that perform the functions specified in the flow or flows and / or blocks Figure 1

[0107] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the flow Figure 1 apparatuses that perform the functions specified in the flow or flows and / or blocks Figure 1

[0108] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the flow Figure 1 apparatuses that perform the functions specified in the flow or flows and / or blocks Figure 1

[0109] In the description of the specification, the description of the terms "one embodiment", "one specific embodiment", "some embodiments", "for example", "exemplary", "specific example" or "some examples" etc. means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In the specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any appropriate manner in one or more embodiments or examples.

[0110] The above-described specific embodiments further illustrate the purpose, technical solutions and beneficial effects of the present application. It should be understood that the above-described specific embodiments are only specific embodiments of the present application and are not used to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.​​​

Claims

1. A method for automated branch office closure and consolidation based on a data warehouse, characterized in that, include: The shared disk of the data warehouse is scanned according to the job configuration file; wherein, the job configuration file is preset and includes a list of scanned files, which includes the retraction and merging comparison files and the retraction and merging initial storage files to be scanned. If a withdrawal / merger comparison file is found, the withdrawal / merger comparison file is loaded into the temporary storage area of ​​the data warehouse; If a merge initial file is detected, the merge initial file and the merge data file are loaded into the temporary storage area of ​​the data warehouse; wherein the merge data file is obtained in advance. The basic data tables of the data warehouse are updated based on the aforementioned merger and relocation comparison file, and the increase and decrease are merged based on the merger and relocation data files and the initial merger and relocation files to complete the merger and relocation operation. The basic layer data tables of the data warehouse updated based on the withdrawal and merger comparison documents include: According to the aforementioned merger and reorganization comparison document, the basic data table will be changed so that the account opening point, the accounting point, and the customer's affiliated point are the merged point, and the account opening point, the accounting point, and the customer's affiliated point are the merged point. The process of merging incremental data files based on merged data files and merged initial storage files includes: Merge the data files to be removed and merged, and the initial storage file to be removed and merged, to obtain the merged initial storage data; If it is determined that there are no duplicate primary keys in the initial data after the merger, the merging process for the new data is completed.

2. The method according to claim 1, characterized in that, Before updating the base-level data tables of the data warehouse based on the aforementioned merger and relocation comparison file, and performing incremental / incremental merging processing based on the merger and relocation data files and the initial merger and relocation file to complete the merger and relocation operation, the following steps are also included: Based on the aforementioned merger comparison file, merger data file, and merger initial storage file, merger preprocessing is performed to obtain merger preprocessing results; The results of the merger and relocation preprocessing were verified.

3. The method according to claim 1, characterized in that, Also includes: If a withdrawal comparison file is found and the withdrawal comparison file is empty, then the withdrawal comparison file is loaded empty.

4. The method according to claim 1, characterized in that, Also includes: If a merge data file is detected, then the merge data file is stored.

5. The method according to claim 1, characterized in that, Also includes: If it is determined that there is a duplicate primary key in the first stored data after merging, the corresponding job will be interrupted and a data error message will be displayed.

6. An automated branch office closure and consolidation device based on a data warehouse, characterized in that, include: The scanning module is used to scan the shared disk of the data warehouse according to the job configuration file; wherein, the job configuration file is preset and includes a list of scanned files, which includes the retraction and merging comparison files and the retraction and merging initial storage files to be scanned; The first loading module is used to load the merging and cancellation comparison file into the temporary storage area of ​​the data warehouse if a merging and cancellation comparison file is detected. The second loading module is used to load the initial file for truncation and the truncation data file into the temporary storage area of ​​the data warehouse if the initial file for truncation and truncation is detected during scanning; wherein the truncation data file is obtained in advance; The operation module is used to update the basic layer data tables of the data warehouse based on the withdrawal and merger comparison file, and to perform addition and storage merging processing based on the withdrawal and merger data file and the withdrawal and merger initial storage file to complete the withdrawal and merger operation. Specifically, the operation module is used to: change the corresponding account opening point, account accounting point and customer belonging point in the basic data table according to the merger and reorganization comparison document to the account opening point, account accounting point and customer belonging point of the merged point; The operation module includes: a data merging unit, used to merge the withdrawn data file and the withdrawn initial storage file to obtain the merged initial storage data; The judgment unit is used to complete the merging of new data if it is determined that there is no duplicate primary key in the first stored data after merging.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1 to 5.

Citation Information

Patent Citations

  • Data processing method and device

    CN110471974A

  • Data processing method and device for Hive data warehouse

    CN113434608A