Basic Data Update Method, Device, Computer Equipment and Storage Medium

Abstract

The present application relates to a method, an apparatus, and a computer device for updating basic data. The method includes: obtaining a requester identifier, an original basic data main identifier, an update version date, and update data carried in an update request, where the original basic data main identifier is shared from a creator; obtaining the original basic data of the creator identifier and the original start and end version dates based on the original basic data main identifier; updating the original basic data based on the update data to obtain updated basic data; dividing the original start and end version dates based on the update version date to obtain a first target start and end version date and a second target start and end version date, and generating a first secondary identifier; associating the original basic data main identifier, the first secondary identifier, the second target start and end version date, the requester identifier with the updated basic data, and associating the original basic data main identifier, the first target start and end version date, the requester identifier with the original basic data. Using this method can improve the flexibility of basic data update.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a method, device, computer equipment, storage medium, and computer program product for updating basic data. Background Art

[0002] With the development of computer technology, data update technology has emerged. Data update usually involves modifying the data to be updated in the data to obtain the updated data. Since the data update is based on the original data, when subsequent processing is performed on the data, only the updated data can be used for processing, and the data before the update cannot be processed subsequently, resulting in the problem of low flexibility in data update. Summary of the Invention

[0003] Based on this, it is necessary to provide a method, device, computer equipment, computer-readable storage medium, and computer program product for updating basic data that can improve the flexibility of data update in view of the above technical problems.

[0004] In a first aspect, this application provides a method for updating basic data. The method includes:

[0005] Obtain an update request, where the update request carries a requester identifier, an original basic data main identifier, an update version date, and update data, and the original basic data main identifier is shared from the creator corresponding to the creator identifier;

[0006] Based on the original basic data main identifier, obtain the original basic data corresponding to the creator identifier and the original start and end version dates corresponding to the original basic data;

[0007] Update the original basic data based on the update data to obtain updated basic data;

[0008] Based on the update version date, divide the original start and end version dates to obtain a first target start and end version date and a second target start and end version date, and generate a first secondary identifier;

[0009] Associate the original basic data main identifier, the first secondary identifier, the second target start and end version date, the requester identifier with the updated basic data, and associate the original basic data main identifier, the first target start and end version date, the requester identifier with the original basic data.

[0010] In one embodiment, before obtaining the update request, where the update request carries a requester identifier, an original basic data main identifier, an update version date, and update information, and the original basic data main identifier is shared from the creator corresponding to the creator identifier, it further includes:

[0011] Obtain a query request, where the query request carries the identifier of the requesting party;

[0012] Based on the query request, search for the identifier of the requesting party in the shared object identifiers of the preset original basic data sharing relationship table corresponding to the identifier of the creating party;

[0013] When the identifier of the requesting party is found, generate original basic data record information based on the original basic data code, the identifier of the creating party, and the original start and end version dates in the original basic data sharing relationship table, and associate the original basic data record information with the original basic data;

[0014] Return the original basic data record information to the terminal corresponding to the identifier of the requesting party;

[0015] When a modification request for the original basic data record information is obtained, obtain the original basic data update interface based on the modification request, and return the original basic data update interface to the terminal corresponding to the identifier of the requesting party;

[0016] Obtain an update request, including:

[0017] Obtain an update request, where the update request is sent by the terminal corresponding to the identifier of the requesting party through the original basic data update interface.

[0018] In one embodiment, before obtaining the query request, it further includes:

[0019] Receive a sharing request, where the sharing request carries the identifier of the creating party, the shared object identifier, and the original basic data main identifier;

[0020] Based on the sharing request, associate and write the identifier of the creating party and the shared object identifier into the original basic data sharing relationship table corresponding to the original basic data main identifier.

[0021] In one embodiment, after associating the original basic data main identifier, the first secondary identifier, the second target start and end version dates, and the identifier of the requesting party with the updated basic data, and associating the original basic data main identifier, the first target start and end version dates, and the identifier of the requesting party with the original basic data, it further includes:

[0022] Generate updated basic data record information based on the original basic data code, the second target start and end version dates, and the identifier of the requesting party, and associate the updated basic data record information with the updated basic data;

[0023] Generate target original basic data record information based on the original basic data code, the first target start and end version dates, and the identifier of the requesting party, and modify the association relationship between the original basic data record information and the original basic data to the association between the target original basic data record information and the original basic data;

[0024] Return the updated basic data record information and the target original basic data record information to the terminal corresponding to the requester identifier.

[0025] In one embodiment, after returning the updated basic data record information and the target original basic data record information to the terminal corresponding to the requester identifier, it further includes:

[0026] Obtain a deletion request, where the deletion request carries the updated basic data record information;

[0027] Delete the updated basic data record information and the updated basic data associated with the updated basic data record information, and restore the second target start and end version dates in the original basic data record information to the original start and end version dates.

[0028] In one embodiment, after associating the original basic data main identifier, the first secondary identifier, the second target start and end version dates, the requester identifier with the updated basic data, and associating the original basic data main identifier, the first target start and end version dates, the requester identifier with the original basic data, it further includes:

[0029] Obtain a current update request, where the current update request carries the current version date, the current update data, and the original basic data main identifier;

[0030] When the current version date is within the first target start and end version dates, divide the first target start and end version dates based on the current version date to obtain the first updated start and end version dates and the second updated start and end version dates, and generate a second secondary identifier;

[0031] Update the original basic data based on the current update data to obtain the current basic data, and update the updated basic data based on the current update data to obtain the target basic data corresponding to the first secondary identifier;

[0032] Associate the original basic data main identifier, the second secondary identifier, the current second start and end version dates, the requester identifier with the current basic data, and update the first target start and end version dates associated with the original basic data to the first updated start and end version dates.

[0033] In a second aspect, the present application also provides a basic data processing device. The device includes:

[0034] An acquisition module, configured to acquire an update request, where the update request carries a requester identifier, an original basic data main identifier, an update version date, and update data, and the original basic data main identifier is shared from the creator corresponding to the creator identifier;

[0035] Obtain the original basic data corresponding to the creator identifier and the original start and end version dates corresponding to the original basic data based on the original basic data main identifier;

[0036] An update module, configured to update the original basic data based on the update data to obtain updated basic data;

[0037] A division module, configured to divide the original start and end version dates based on the update version date to obtain a first target start and end version date and a second target start and end version date, and generate a first secondary identifier;

[0038] An association module, configured to associate the main identifier of the original basic data, the first secondary identifier, the second target start and end version date, the requester identifier with the updated basic data, and associate the main identifier of the original basic data, the first target start and end version date, the requester identifier with the original basic data.

[0039] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor. The memory stores a computer program. When the processor executes the computer program, the following steps are implemented:

[0040] Obtain an update request, where the update request carries a requester identifier, a main identifier of the original basic data, an update version date, and update data, and the main identifier of the original basic data is shared from the creator corresponding to the creator identifier;

[0041] Obtain the original basic data corresponding to the creator identifier and the original start and end version dates corresponding to the original basic data based on the main identifier of the original basic data;

[0042] Update the original basic data based on the update data to obtain updated basic data;

[0043] Divide the original start and end version dates based on the update version date to obtain a first target start and end version date and a second target start and end version date, and generate a first secondary identifier;

[0044] Associate the main identifier of the original basic data, the first secondary identifier, the second target start and end version date, the requester identifier with the updated basic data, and associate the main identifier of the original basic data, the first target start and end version date, the requester identifier with the original basic data.

[0045] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the following steps are implemented:

[0046] Obtain an update request, where the update request carries a requester identifier, a main identifier of the original basic data, an update version date, and update data, and the main identifier of the original basic data is shared from the creator corresponding to the creator identifier;

[0047] Obtain the original basic data corresponding to the creator identifier and the original start and end version dates corresponding to the original basic data based on the main identifier of the original basic data;

[0048] Update the original basic data based on the updated data to obtain the updated basic data;

[0049] Divide the target start and end version dates based on the updated version date to obtain the first target start and end version dates and the second target start and end version dates, and generate the first secondary identifier;

[0050] Associate the main identifier of the original basic data, the first secondary identifier, the second target start and end version dates, the requester identifier with the updated basic data, and associate the main identifier of the original basic data, the first target start and end version dates, the requester identifier with the original basic data.

[0051] In a fifth aspect, the present application also provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0052] Obtain an update request, where the update request carries a requester identifier, a main identifier of the original basic data, an updated version date, and updated data, and the main identifier of the original basic data is shared from the creator corresponding to the creator identifier;

[0053] Obtain the original basic data corresponding to the creator identifier and the original start and end version dates corresponding to the original basic data based on the main identifier of the original basic data;

[0054] Update the original basic data based on the updated data to obtain the updated basic data;

[0055] Divide the original start and end version dates based on the updated version date to obtain the first target start and end version dates and the second target start and end version dates, and generate the first secondary identifier;

[0056] Associate the main identifier of the original basic data, the first secondary identifier, the second target start and end version dates, the requester identifier with the updated basic data, and associate the main identifier of the original basic data, the first target start and end version dates, the requester identifier with the original basic data.

[0057] The above basic data update method, device, computer device, storage medium, and computer program product update the original basic data according to the update data carried in the update request to obtain the updated basic data. Then, the version division is performed on the original start and end version dates corresponding to the original basic data through the version update date carried in the update request, and the first sub-identifier is generated. The obtained first target start and end version dates and the second target start and end version dates are respectively associated and saved with the original basic data and the updated basic data. Thus, the requester can use the first target start and end version dates to perform subsequent processing on the original basic data after the update, realizing the version management of the basic data, improving the flexibility of updating and using the basic data, and enhancing the user experience. Moreover, the main identifier of the original basic data is shared from the creator corresponding to the creator identifier, and the main identifier corresponding to the same original basic data will not change, including the original basic data and the updated basic data corresponding to different requester identifiers, enabling the requester to update the original basic data created by the creator, generate the updated basic data required by the requester based on the original basic data, and save the original basic data and the updated basic data simultaneously. The requester can view the update records of the original basic data according to the business requirements and modify the historical basic data, and the creator can also view the basic data corresponding to the requester identifier according to the main identifier of the original basic data. Further, the flexibility of using and updating the original basic data is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 FIG. is an application environment diagram of the basic data update method in an embodiment;

[0059] Figure 2 FIG. is a flowchart of the basic data update method in an embodiment;

[0060] Figure 3 FIG. is a flowchart of generating the original basic data record information in an embodiment;

[0061] Figure 4 FIG. is a schematic diagram of the original basic data update interface in an embodiment;

[0062] Figure 5 FIG. is a flowchart of generating the updated basic data record information in an embodiment;

[0063] Figure 6 FIG. is a schematic diagram of the target original basic data record information in an embodiment;

[0064] Figure 7 FIG. is a flowchart of generating the current basic data in an embodiment;

[0065] Figure 8Schematic diagram of the process for sharing and updating original basic data in a specific embodiment;

[0066] Figure 9 Structural block diagram of a basic data processing device in an embodiment;

[0067] Figure 10 Internal structure diagram of a computer device in an embodiment;

[0068] Figure 11 Internal structure diagram of a computer device in another embodiment. Detailed implementation manners

[0069] In order to make the objectives, technical solutions, and advantages of the present application clearer and more understandable, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0070] The basic data update method provided by the embodiments of the present application can be applied to an application environment as shown in Figure 1 In the figure. Among them, the terminal 102 communicates with the server 104 through a network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or can be placed in the cloud or other network servers. The server 104 obtains the update request sent by the terminal 102. The update request carries a requester identifier, an original basic data main identifier, an update version date, and update data. The original basic data main identifier is shared from the creator corresponding to the creator identifier; the server 104 obtains the original basic data corresponding to the creator identifier and the original start and end version dates corresponding to the original basic data based on the original basic data main identifier; the server 104 updates the original basic data based on the update data to obtain updated basic data; the server 104 divides the original start and end version dates based on the update version date to obtain a first target start and end version date and a second target start and end version date, and generates a first secondary identifier; the server 104 associates the original basic data main identifier, the first secondary identifier, the second target start and end version date, the requester identifier with the updated basic data, and associates the original basic data main identifier, the first target start and end version date, the requester identifier with the original basic data. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, Internet of Things devices, and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. The portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The server 104 can be implemented by an independent server or a server cluster composed of multiple servers.

[0071] In an embodiment, as shown in Figure 2As shown, a basic data update method is provided. Taking the server in Figure 1 as an example for illustration, the method includes the following steps:

[0072] Step 202: Obtain an update request. The update request carries a requester identifier, an original basic data main identifier, an update version date, and update data. The original basic data main identifier is shared from the creator corresponding to the creator identifier.

[0073] Among them, the requester identifier refers to the user identifier that updates the original basic data. The original basic data main identifier refers to the unique identifier of the original basic data generated by the creator when creating the original basic data. The update version date refers to the date set by the user to update the basic data, which is used to divide the versions of the original basic data update. The update data refers to the specific update content that needs to be updated in the original basic data. The creator refers to the terminal party that creates the original basic data. The basic data can be the basic information data of an enterprise management system. For example, the accounting subjects in financial management, including subjects such as cash on hand and accounts receivable.

[0074] Specifically, the creator identifier is the identifier of the creating user, and the creating user can be the superior user of the requester corresponding to the requester identifier. The original basic data main identifier can also be authorized from the creator corresponding to the creator identifier. The server obtains the update request sent by the terminal corresponding to the requester identifier, and the update request carries the user identifier, the original basic data main identifier, the update version date, and the update data. The update version date can be the current date at the time of update or the date after the update.

[0075] Step 204: Based on the original basic data main identifier, obtain the original basic data corresponding to the creator identifier and the original start and end version dates corresponding to the original basic data.

[0076] Among them, the creator identifier refers to the identity identifier corresponding to the creating user of the original basic data. The original start and end version dates refer to the start and end dates used to represent the version of the original basic data, including: start date and end date.

[0077] Specifically, the server can search and obtain the original basic data corresponding to the original basic data main identifier and the original start and end version dates in the data storage system according to the original basic data main identifier. The original basic data can be created by the creator through the terminal corresponding to the creator identifier, and then the creator uploads the original basic data and the original start and end version dates to the data storage system through the terminal corresponding to the creator identifier.

[0078] Step 206: Update the original basic data based on the update data to obtain the updated basic data.

[0079] Specifically, the original basic data can be composed of different basic data items. The server can use the update data and the basic data items in the original basic data that do not need to be updated to obtain the updated basic data. In one embodiment, when updating, the server can also first back up the original basic data, and then replace the data of the corresponding basic data items in the original basic data according to the update data to obtain the updated basic data.

[0080] Step 208: Based on the updated version date, divide the original start and end version dates to obtain the first target start and end version dates and the second target start and end version dates, and generate a first secondary identifier.

[0081] Among them, the start date in the first target start and end version dates is the start date in the original start and end version dates, and the end date is the updated version date; the start date in the second target start and end version dates is the updated version date, and the end date is the end date in the original start and end version dates. The first secondary identifier is the identification information corresponding to the updated basic data, and this first secondary identifier is associated with the requesting party.

[0082] Specifically, the server divides the time range to which the original start and end version dates belong according to the updated version date to obtain two time periods, namely the first target start and end version dates and the second target start and end version dates. At the same time, the server generates the first secondary identifier corresponding to the updated basic data.

[0083] Step 210: Associate the original basic data main identifier, the first secondary identifier, the second target start and end version dates, the requesting party identifier with the updated basic data, and associate the original basic data main identifier, the first target start and end version dates, and the requesting party identifier with the original basic data.

[0084] Specifically, the server establishes association relationships, including the association relationship of the updated basic data and the association relationship of the original basic data, and then saves the established association relationships. That is, the server uses the original basic data main identifier, the first secondary identifier, the second target start and end version dates, and the requesting party identifier together to identify the updated basic data. And uses the original basic data main identifier, the first target start and end version dates, and the requesting party identifier together to identify the original basic data.

[0085] In the above basic data update method, the original basic data is updated according to the update data carried in the update request to obtain the updated basic data. Then, the original start and end version dates corresponding to the original basic data are divided by the version update date carried in the update request, and the first secondary identifier is generated. The obtained first target start and end version dates and the second target start and end version dates are respectively associated and saved with the original basic data and the updated basic data. Therefore, the requester can use the first target start and end version dates to perform subsequent processing on the original basic data after the update, realizing the version management of the basic data, improving the flexibility of updating and using the basic data, and enhancing the user experience. Moreover, the main identifier of the original basic data is shared from the creator corresponding to the creator identifier, and the main identifier corresponding to the same original basic data will not change, including the original basic data and the updated basic data corresponding to different requester identifiers, enabling the requester to update the original basic data created by the creator, generate the updated basic data required by the requester based on the original basic data, and save the original basic data and the updated basic data at the same time. The requester can view the update records of the original basic data according to the business requirements and modify the historical basic data, and the creator can also view the basic data corresponding to the requester identifier according to the main identifier of the original basic data. Further, the flexibility of using and updating the original basic data is improved.

[0086] In one embodiment, as Figure 3 shown, a flowchart of generating the original basic data record information is provided. Step 202, before obtaining the update request, where the update request carries the requester identifier, the main identifier of the original basic data, the update version date, and the update information, and the main identifier of the original basic data is shared from the creator corresponding to the creator identifier, further includes:

[0087] Step 302, obtain a query request, where the query request carries the requester identifier;

[0088] Step 304, based on the query request, search for the requester identifier in the shared object identifier of the preset original basic data sharing relationship table corresponding to the creator identifier;

[0089] Step 306, when the requester identifier is found, generate the original basic data record information based on the original basic data code, the creator identifier, and the original start and end version dates in the original basic data sharing relationship table, and associate the original basic data record information with the original basic data;

[0090] Step 308, return the original basic data record information to the terminal corresponding to the requester identifier;

[0091] Step 310, when a modification request for the original basic data record information is obtained, an original basic data update interface is obtained based on the modification request, and the original basic data update interface is returned to the terminal corresponding to the requester identifier;

[0092] Step 312, obtain an update request, including: obtaining an update request, where the update request is sent by the terminal corresponding to the requester identifier through the original basic data update interface.

[0093] Among them, the query request is a query request sent by the terminal corresponding to the requester identifier to the server for querying the original basic data shared by the creator. The original basic data sharing relationship table is established by the creator, and the original basic data main identifier and the associated shared object identifier are recorded in the original basic data sharing relationship table. The original basic data code is used to identify the business data category corresponding to the original basic data and is associated with the original basic data main identifier. The original basic data record information is the record information displayed on the terminal interface corresponding to the requester identifier, which is convenient for the requester to view and subsequent processing, such as updating and deleting the original basic data.

[0094] Specifically, when creating the original basic data sharing relationship table, the creator terminal obtains the shared object identifier selected by the creating user, sends the shared object identifier selected by the creating user and the associated original basic data main identifier to the server, and the server generates the original basic data sharing relationship table according to the shared object identifier selected by the creating user and the associated original basic data main identifier. It can also be that the creator terminal generates the original basic data sharing relationship table according to the shared object identifier selected by the creating user and the original basic data main identifier, and then the creator terminal sends the original basic data sharing relationship table to the server. Among them, the start date of the original start and end version date can be 1900-01-01, and the end date can be 2999-12-31. The requester identifier can be the user name of the requester or the terminal identifier of the requester. The creator identifier can be the user name of the creator or the terminal identifier of the creator.

[0095] The server obtains the query request sent by the requester terminal, and then queries the requester identifier among the shared object identifiers in the original basic data sharing relationship table. When the server queries the requester identifier, it obtains the original basic data code, creator identifier, and original start and end version date in the original basic data sharing relationship table to generate the original basic data record information, and associates the original basic data record information with the original basic data;

[0096] The server returns the original basic data record information to the requester terminal, and the requester terminal displays the original basic data record information. When the requester terminal detects a modification trigger event of the original basic data record information, it sends a modification request to the server and receives the original basic data update interface returned by the server;

[0097] The requesting party terminal obtains the updated data input by the user on the original basic data update interface and generates an update request to send to the server.

[0098] In a specific embodiment, as Figure 4 shown, a schematic diagram of the original basic data update interface is provided, in which the original basic data of the accounting subject is displayed, including the original basic data code of 0045.01, the original basic data name of other comprehensive income, the original basic data subject type of the owner's equity category, the superior of 0045, and the version date of 2021-10-08, etc. The superior refers to the code corresponding to the upper-level original basic data of the original basic data. Then, the requesting party can update the original basic data.

[0099] In this embodiment, the server generates an original basic data sharing relationship table according to the original basic data sharing object selected by the creating party. Then, each shared requesting party can use the query request to query the original basic data. The terminal corresponding to the requesting party identifier displays the original basic data record information on the interface, which can enable each shared requesting party to perform personalized updates on the original basic data according to their respective needs, and be more flexible when performing business processing on the original basic data, thereby improving the flexibility of updating and using the basic data, and further improving the utilization rate of the original basic data.

[0100] In an embodiment, before obtaining the query request, it further includes:

[0101] Receiving a sharing request, the sharing request carries a creating party identifier, a sharing object identifier, and an original basic data main identifier;

[0102] Based on the sharing request, the creating party identifier and the sharing object identifier are associated and written into the original basic data sharing relationship table corresponding to the original basic data main identifier.

[0103] Among them, the sharing request is a request sent by the creating terminal to the server when it detects that the creating party selects the original basic data sharing object, and is used to generate the original basic data sharing relationship table.

[0104] Specifically, when the creator terminal corresponding to the creator detects a sharing trigger event of the creator user for the original basic data, the creator terminal pops up a sharing object identifier selection box; when the creator terminal detects a confirmation sharing trigger event of the creator user for the original basic data, it obtains the sharing object identifier selected by the creator and the original basic data main identifier and generates a sharing request, and the creator terminal sends the sharing request to the server; when the server receives the sharing request sent by the creator terminal, it generates an original basic data sharing relationship table and associates and writes the creator identifier, sharing object identifier carried in the sharing request into the original basic data sharing relationship table corresponding to the original basic data main identifier.

[0105] In this embodiment, the server generates an original basic data sharing relationship table corresponding to the original basic data main identifier by obtaining the sharing request, so that the sharing object terminal can obtain the corresponding original basic data according to the original basic data sharing relationship table and perform personalized updates, thereby making the update and use of the original basic data more flexible and improving the utilization rate of the original basic data.

[0106] In one embodiment, as Figure 5 shown, a schematic flow chart for generating updated basic data record information is provided. Step 210, after associating the original basic data main identifier, the first secondary identifier, the second target start and end version dates, the requester identifier with the updated basic data, and associating the original basic data main identifier, the first target start and end version dates, the requester identifier with the original basic data, further includes:

[0107] Step 502, generating updated basic data record information based on the original basic data code, the second target start and end version dates, and the requester identifier, and associating the updated basic data record information with the updated basic data;

[0108] Step 504, generating target original basic data record information based on the original basic data code, the first target start and end version dates, and the requester identifier, and modifying the association relationship between the original basic data record information and the original basic data to the association between the target original basic data record information and the original basic data;

[0109] Step 506, returning the updated basic data record information and the target original basic data record information to the terminal corresponding to the requester identifier.

[0110] Among them, updating the basic data record information is to receive the updated basic data record information sent by the server at the requester's terminal and display it on the interface of the requester's terminal. The requester can perform subsequent processing on the updated basic data through the updated basic data record information, such as updating, deleting, adjusting, etc. The target original basic data record information is obtained by updating the original basic data record information according to the second target start and end version dates and the requester identifier after the original basic data is updated to obtain the updated basic data. The requester can perform subsequent processing on the original basic data through the updated basic data record information, such as updating, deleting, adjusting, etc.

[0111] Specifically, the server can directly use the original basic data encoding, the second target start and end version dates, and the requester identifier as the updated basic data record information, and associate the updated basic data record information with the updated basic data;

[0112] The server replaces the original start and end version dates in the original basic data record information with the first target start and end version dates according to the original basic data encoding, the first target start and end version dates, and the requester identifier, replaces the creator identifier with the requester identifier, uses the original basic data encoding, the first target start and end version dates, and the requester identifier as the target original basic data record information, and associates the target original basic data record information with the original basic data;

[0113] The server returns the updated basic data record information and the target original basic data record information to be displayed on the terminal interface corresponding to the requester identifier.

[0114] In a specific embodiment, as Figure 6 shown, a schematic diagram of the target original basic data record information is provided. For example, the requester is Organization A, the version date is January 19, 2021. The requester's terminal interface includes the target basic data record information corresponding to the original basic data and the updated basic data record information corresponding to the updated basic data. The requester identifiers corresponding to the target basic data record information and the updated basic data record information are the same, and the encoding is 1009. The user can update or delete the target basic data record information or the updated basic data record information through the requester's terminal interface.

[0115] In this embodiment, the user can update or delete the target basic data record information or the updated basic data record information through the requestor terminal interface, and synchronously update the creator identifier and the original start and end version dates in the original basic data record information after the original basic data is updated, so as to quickly identify the operator who updates the original basic data and the updated basic data; and can query the original basic data according to the first target start and end version dates corresponding to the original basic data, thereby improving the utilization rate of the original basic data, and further making the user more flexible when performing business operations on the original basic data and the updated basic data, and improving the flexibility of updating and using the basic data.

[0116] In one embodiment, after returning the updated basic data record information and the target original basic data record information to the terminal corresponding to the requestor identifier, it further includes:

[0117] Obtain a deletion request, where the deletion request carries the updated basic data record information;

[0118] Delete the updated basic data record information and the updated basic data associated with the updated basic data record information, and restore the second target start and end version dates in the original basic data record information to the original start and end version dates.

[0119] Specifically, when the terminal corresponding to the requestor identifier detects a deletion event for the updated basic data record information, delete the updated basic data record information and restore the second target start and end version dates in the original basic data record information to the original start and end version dates, and then send the deletion request to the server;

[0120] The server obtains the deletion request, deletes the updated basic data according to the updated basic data record information carried in the deletion request, and restores the second target start and end version dates corresponding to the original basic data to the original start and end version dates.

[0121] In this embodiment, the original basic data can be restored by deleting the updated basic data record information in the requestor terminal interface, or the basic data record information corresponding to the basic data after the updated basic data is updated can be deleted, so that the updated basic data is restored to the current latest basic data, and further enables the user to restore the required basic data according to business needs and update the restored basic data again, improving the flexibility of updating and using the basic data.

[0122] In one embodiment, such as Figure 7As shown, a flow diagram for generating current basic data is provided. After associating the main identifier of the original basic data, the first secondary identifier, the second target start and end version dates, the requester identifier with the updated basic data, and associating the main identifier of the original basic data, the first target start and end version dates, the requester identifier with the original basic data, it further includes:

[0123] Step 702, obtain a current update request, where the current update request carries the current version date, the current update data, and the main identifier of the original basic data;

[0124] Step 704, when the current version date is within the first target start and end version dates, divide the first target start and end version dates based on the current version date to obtain the first update start and end version dates and the second update start and end version dates, and generate a second secondary identifier;

[0125] Step 706, update the original basic data based on the current update data to obtain the current basic data, and update the updated basic data based on the current update data to obtain the target basic data corresponding to the first secondary identifier;

[0126] Step 708, associate the main identifier of the original basic data, the second secondary identifier, the current second start and end version dates, the requester identifier with the current basic data, and update the first target start and end version dates associated with the original basic data to the first update start and end version dates.

[0127] Among them, the start date corresponding to the first update start and end version dates is the start date of the first target start and end version dates, and the end date is the current version date. The start date corresponding to the second update start and end version dates is the current version date, and the end date is the end date of the first target start and end version dates. The second secondary identifier is the identifier corresponding to the current basic data.

[0128] Specifically, the server obtains the current update request sent by the requester terminal. The current update data carried in the current update request includes the specific update content of the items to be updated in the original basic data. When it is detected that the current version date carried in the current update request is within the first target start and end version dates, the server divides the time period corresponding to the first target start and end version dates based on the current version date to obtain two corresponding time periods, namely the first update start and end version dates and the second update start and end version dates, and generates a second secondary identifier;

[0129] The server replaces the corresponding update items in the original basic data based on the specific update content in the current update data to obtain the current basic data, and synchronously replaces the updated basic data based on the specific update content in the current update data to obtain the target basic data corresponding to the first secondary identifier;

[0130] Then, associate the original basic data main identifier, the second secondary identifier, the current second start and end version date, the requester identifier with the current basic data, and modify the first target start and end version date associated with the original basic data to the first updated start and end version date.

[0131] In a specific embodiment, the server can also detect the modification items corresponding to the updated basic data and the basic data updated thereafter according to the modification items in the current updated data. When it is detected that the modification items corresponding to the updated basic data and the basic data updated thereafter are the same as the modification items corresponding to the original basic data, update the modification items corresponding to the updated basic data and the basic data updated thereafter to the modification items in the current updated data.

[0132] In this embodiment, while updating the modification items of the original basic data, the modification items of the updated basic data are synchronously updated according to the current updated data, avoiding the problem of inconsistent data during the update of the original basic data and improving the update accuracy of the basic data.

[0133] In a specific embodiment, as Figure 8 shown, a flow schematic diagram for sharing and updating the original basic data is provided, including:

[0134] The creating organization A creates an original basic data with a code of 1001 and a name of cash on hand and a subordinate original basic data with a code of 1001.01 on the terminal corresponding to organization A. The subordinate original basic data is the next-level original basic data created by organization A based on the original basic data according to business requirements. The main identifier and the secondary identifier corresponding to the original basic data are both 1, and the main identifier and the secondary identifier corresponding to the subordinate original basic data are both 100. The original version start and end dates corresponding to the original basic data and the subordinate original basic data are both (1900-01-01, 2999-12-31);

[0135] Organization A shares the original basic data and the subordinate original basic data with subordinate organizations B and C. Subordinate organization B updates the original basic data on December 1, 2020 and sets the version date to December 1, 2020, obtaining the updated basic data of organization B corresponding to subordinate organization B. The updated basic data of organization B represented by the code 1001’ in the figure is obtained by subordinate organization B's personalized update of the original basic data with the code 1001. At the same time, based on the version date of December 1, 2020, the original version start and end dates corresponding to the original basic data are divided, obtaining the first target start and end dates corresponding to the original basic data as (January 1, 1900, December 1, 2020) and the second target start and end dates corresponding to the updated basic data of organization B as (December 1, 2020, December 31, 2999), and generating a secondary identifier corresponding to the updated basic data of organization B, which can be 2. The main identifier corresponding to the updated basic data of organization B is the same as the main identifier corresponding to the original basic data. The updated basic data of organization B serves as the basic data for the next version corresponding to organization B of the original basic data; The allocation relationship pointer in the figure means that if subordinate organization B does not update the subordinate original basic data when receiving the subordinate original basic data with the code 1001.01, the relevant information of the subordinate original basic data remains unchanged, and organization B uses the same subordinate original basic data as organization A when conducting relevant business operations;

[0136] Subordinate organization C updates the original basic data on June 1, 2020 and sets the version date to December 1, 2020, obtaining the updated basic data of organization C corresponding to subordinate organization C. The updated basic data of organization C represented by the code 1001” in the figure is obtained by subordinate organization C's personalized update of the original basic data with the code 1001. At the same time, based on the version date of June 1, 2020, the original version start and end dates corresponding to the original basic data are divided, obtaining the first target start and end dates corresponding to the original basic data as (January 1, 1900, June 1, 2020) and the second target start and end dates corresponding to the updated basic data of organization C as (June 1, 2020, December 31, 2999), and generating a secondary identifier corresponding to the updated basic data of organization C, which can be 3. The main identifier corresponding to the updated basic data of organization C is the same as the main identifier corresponding to the original basic data. The updated basic data of organization C serves as the basic data for the next version corresponding to organization C of the original basic data;

[0137] The lower-level organization C updated the basic data of organization C on July 1, 2021 and set the versioning date as July 1, 2021. The updated current basic data of organization C corresponding to the lower-level organization C was obtained. Based on the versioning date of July 1, 2021, the version start and end dates (June 1, 2020, December 31, 2999) corresponding to the updated basic data of organization C were divided to obtain the version start and end dates corresponding to the updated basic data of organization C as (June 1, 2020, July 1, 2021) and the version start and end dates corresponding to the current basic data of organization C as (July 1, 2021, December 31, 2999). And a secondary identifier corresponding to the current basic data of organization C was generated, which could be 4. The main identifier corresponding to the updated basic data of organization C was the same as the main identifier corresponding to the original basic data. The current basic data of organization C served as the basic data for the next version of the updated basic data of organization C. In the figure, the encoded 1001.01’ represents the basic data obtained after the lower-level organization C updated the lower-level basic data with the code 1001.01 on August 1, 2020, and the version date corresponding to this basic data is August 1, 2020;

[0138] Furthermore, the processes of the lower-level organization B and the lower-level organization C updating the original basic data or the lower-level original basic data are isolated from each other. The updated basic data generated respectively are the personalized updated basic data of the lower-level organization B and the personalized updated basic data of the lower-level organization C. And when organization A has the permission to modify the basic data of the lower-level organization B and the lower-level organization C, organization A can update the updated basic data corresponding to the lower-level organization B and the lower-level organization C. Organization A can also perform the business process of balance aggregation on the updated basic data of the lower-level organization B and the lower-level organization C according to the main identifier corresponding to the original basic data. Thus, the personalized update of the original basic data by different-level organizations is realized, and the superior organization can perform business processes on the updated basic data of the lower-level organization B and the lower-level organization C, improving the flexibility of updating and using the basic data and the utilization rate of the basic data.

[0139] It should be understood that although the steps in the flowcharts involved in the above-described embodiments are shown in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear indication in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-described embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same moment, but can be executed at different moments. The execution order of these steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or steps or stages in other steps.

[0140] Based on the same inventive concept, an embodiment of the present application further provides a basic data processing apparatus for implementing the basic data update method involved above. The solution provided by this apparatus to solve the problem is similar to the solution described in the above method. Therefore, the specific limitations in one or more embodiments of the basic data processing apparatus provided below can refer to the limitations on the basic data update method in the above text and will not be repeated here.

[0141] In one embodiment, as Figure 9 shown, a basic data processing apparatus 900 is provided, including: an acquisition module 902, an update module 904, a division module 906, and an association module 908, where:

[0142] The acquisition module 902 is configured to acquire an update request, where the update request carries a requester identifier, an original basic data main identifier, an update version date, and update data, and the original basic data main identifier is shared from the creator corresponding to the creator identifier; acquire the original basic data corresponding to the creator identifier and the original start and end version dates corresponding to the original basic data based on the original basic data main identifier;

[0143] The update module 904 is configured to update the original basic data based on the update data to obtain updated basic data;

[0144] The division module 906 is configured to divide the original start and end version dates based on the update version date to obtain a first target start and end version date and a second target start and end version date, and generate a first secondary identifier;

[0145] The association module 908 is configured to associate the original basic data main identifier, the first secondary identifier, the second target start and end version date, the requester identifier with the updated basic data, and associate the original basic data main identifier, the first target start and end version date, the requester identifier with the original basic data.

[0146] In one embodiment, the basic data processing apparatus 900 further includes:

[0147] A query request acquisition module, configured to acquire a query request, where the query request carries a requester identifier;

[0148] Search for the requester identifier in the shared object identifiers of a preset original basic data sharing relationship table corresponding to the creator identifier based on the query request;

[0149] When the requester identifier is found, generate original basic data record information based on the original basic data code, the creator identifier, and the original start and end version dates in the original basic data sharing relationship table, and associate the original basic data record information with the original basic data;

[0150] Return the original basic data record information to the terminal corresponding to the requester identifier;

[0151] When a modification request for the original basic data record information is obtained, obtain the original basic data update interface based on the modification request, and return the original basic data update interface to the terminal corresponding to the requester identifier;

[0152] The acquisition module 902 is further configured to: obtain an update request, where the update request is sent by the terminal corresponding to the requester identifier through the original basic data update interface.

[0153] In one embodiment, the basic data processing device 900 further includes:

[0154] A sharing request acquisition module, configured to receive a sharing request, where the sharing request carries a creator identifier, a sharing object identifier, and an original basic data main identifier; based on the sharing request, associate and write the creator identifier and the sharing object identifier into the original basic data sharing relationship table corresponding to the original basic data main identifier.

[0155] In one embodiment, the basic data processing device 900 further includes:

[0156] A target original basic data record information generation module, configured to generate updated basic data record information based on the original basic data code, the second target start and end version dates, and the requester identifier, and associate the updated basic data record information with the updated basic data; generate target original basic data record information based on the original basic data code, the first target start and end version dates, and the requester identifier, and modify the association relationship between the original basic data record information and the original basic data to the association relationship between the target original basic data record information and the original basic data; return the updated basic data record information and the target original basic data record information to the terminal corresponding to the requester identifier.

[0157] In one embodiment, the basic data processing device 900 further includes:

[0158] A deletion request acquisition module, configured to obtain a deletion request, where the deletion request carries updated basic data record information; delete the updated basic data associated with the updated basic data record information, and restore the second target start and end version dates in the original basic data record information to the original start and end version dates.

[0159] In one embodiment, the basic data processing device 900 further includes:

[0160] A target basic data generation module is used to obtain a current update request, where the current update request carries a current version date, current update data, and an original basic data main identifier; when the current version date is within the first target start and end version dates, the first target start and end version dates are divided based on the current version date to obtain a first update start and end version date and a second update start and end version date, and a second secondary identifier is generated; the original basic data is updated based on the current update data to obtain current basic data, and the updated basic data is updated based on the current update data to obtain the target basic data corresponding to the first secondary identifier; the original basic data main identifier, the second secondary identifier, the current second start and end version date, the requester identifier, and the current basic data are associated, and the first target start and end version dates associated with the original basic data are updated to the first update start and end version dates.

[0161] Each module in the above basic data processing device can be implemented in whole or in part by software, hardware, and their combination. Each of the above modules can be embedded in or independent of a processor in a computer device in the form of hardware, or stored in a memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0162] In one embodiment, a computer device is provided. The computer device can be a server, and its internal structure diagram can be as Figure 10 shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O), and a communication interface. Among them, the processor, the memory, and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store original basic data, updated basic data, current basic data, etc. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals through a network connection. When the computer program is executed by the processor, it implements a basic data update method.

[0163] In one embodiment, a computer device is provided. The computer device can be a terminal, and its internal structure diagram can be as Figure 11As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. Among them, the processor, the memory, and the input / output interface are connected through a system bus, and the communication interface, the display unit, and the input device are connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals in a wired or wireless manner, and the wireless manner can be achieved through WIFI, a mobile cellular network, NFC (Near Field Communication), or other technologies. The computer program, when executed by the processor, implements a basic data update method. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer covering the display screen, or a button, a trackball, or a touchpad provided on the housing of the computer device, or an external keyboard, touchpad, or mouse, etc.

[0164] Those skilled in the art can understand that Figures 10 - 11 the structure shown in is only a block diagram of some structures related to the solution of this application, and does not constitute a limitation on the computer device to which the solution of this application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

[0165] In one embodiment, a computer device is provided, including a memory and a processor. A computer program is stored in the memory. When the processor executes the computer program, the following steps are implemented:

[0166] Obtain an update request, where the update request carries a requester identifier, an original basic data main identifier, an update version date, and update data. The original basic data main identifier is shared from the creator corresponding to the creator identifier; obtain the original basic data corresponding to the creator identifier and the original start and end version dates corresponding to the original basic data based on the original basic data main identifier; update the original basic data based on the update data to obtain updated basic data; divide the original start and end version dates based on the update version date to obtain a first target start and end version date and a second target start and end version date, and generate a first secondary identifier; associate the original basic data main identifier, the first secondary identifier, the second target start and end version date, the requester identifier with the updated basic data, and associate the original basic data main identifier, the first target start and end version date, and the requester identifier with the original basic data.

[0167] In one embodiment, when the processor executes the computer program, the following steps are further implemented:

[0168] Before obtaining the update request, where the update request carries a requester identifier, an original basic data main identifier, an update version date, and update information, and the original basic data main identifier is shared from the creator corresponding to the creator identifier, it further includes: obtaining a query request, where the query request carries a requester identifier; searching for the requester identifier in the shared object identifiers of a preset original basic data sharing relationship table corresponding to the creator identifier based on the query request; when the requester identifier is found, generating original basic data record information based on the original basic data code, creator identifier, and original start and end version dates in the original basic data sharing relationship table, and associating the original basic data record information with the original basic data; returning the original basic data record information to the terminal corresponding to the requester identifier; when a modification request for the original basic data record information is obtained, obtaining an original basic data update interface based on the modification request, and returning the original basic data update interface to the terminal corresponding to the requester identifier; obtaining the update request, including: obtaining the update request, where the update request is sent by the terminal corresponding to the requester identifier through the original basic data update interface.

[0169] In one embodiment, when the processor executes the computer program, the following steps are further implemented:

[0170] Before obtaining the query request, it further includes: receiving a sharing request, where the sharing request carries a creator identifier, a shared object identifier, and an original basic data main identifier; associating and writing the creator identifier and the shared object identifier into the original basic data sharing relationship table corresponding to the original basic data main identifier based on the sharing request.

[0171] In one embodiment, when the processor executes the computer program, the following steps are further implemented:

[0172] After associating the original basic data main identifier, the first secondary identifier, the second target start and end version dates, the requester identifier with the updated basic data, and associating the original basic data main identifier, the first target start and end version dates, the requester identifier with the original basic data, it further includes: generating updated basic data record information based on the original basic data code, the second target start and end version dates, and the requester identifier, and associating the updated basic data record information with the updated basic data; generating target original basic data record information based on the original basic data code, the first target start and end version dates, and the requester identifier, and modifying the association relationship between the original basic data record information and the original basic data to the association between the target original basic data record information and the original basic data; returning the updated basic data record information and the target original basic data record information to the terminal corresponding to the requester identifier.

[0173] In one embodiment, when the processor executes the computer program, it further implements the following steps:

[0174] After returning the updated basic data record information and the target original basic data record information to the terminal corresponding to the requester identifier, it further includes: obtaining a deletion request, where the deletion request carries the updated basic data record information; deleting the updated basic data associated with the updated basic data record information and the updated basic data record information, and restoring the second target start and end version dates in the original basic data record information to the original start and end version dates.

[0175] In one embodiment, when the processor executes the computer program, it further implements the following steps:

[0176] After returning the updated basic data record information and the target original basic data record information to the terminal corresponding to the requester identifier, the following steps are further included: obtaining a deletion request, where the deletion request carries the updated basic data record information; deleting the updated basic data record information and the updated basic data associated with the updated basic data record information, and restoring the second target start and end version dates in the original basic data record information to the original start and end version dates. In one embodiment, when the processor executes the computer program, the following steps are further implemented: after associating the original basic data main identifier, the first secondary identifier, the second target start and end version dates, the requester identifier with the updated basic data, and associating the original basic data main identifier, the first target start and end version dates, the requester identifier with the original basic data, the following steps are further included: obtaining a current update request, where the current update request carries the current version date, the current update data, and the original basic data main identifier; when the current version date is within the first target start and end version dates, dividing the first target start and end version dates based on the current version date to obtain the first updated start and end version dates and the second updated start and end version dates, and generating a second secondary identifier; updating the original basic data based on the current update data to obtain the current basic data, and updating the updated basic data based on the current update data to obtain the target basic data corresponding to the first secondary identifier; associating the original basic data main identifier, the second secondary identifier, the current second start and end version dates, the requester identifier with the current basic data, and updating the first target start and end version dates associated with the original basic data to the first updated start and end version dates.

[0177] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0178] In one embodiment, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0179] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data that have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of the relevant data need to comply with the relevant laws, regulations, and standards of the relevant countries and regions.

[0180] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memories. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in the present application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in the present application can be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, data processing logics based on quantum computing, etc., without limitation.

[0181] The technical features of the above embodiments can be combined arbitrarily. For the sake of concise description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope recorded in this specification.

[0182] The above-described embodiments only represent several implementation manners of the present application. The description is relatively specific and detailed, but it should not be construed as a limitation on the patent scope of the present application. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.

Claims

1. A basic data update method, characterized in that, The method includes: Obtaining an update request, where the update request carries a requester identifier, an original basic data main identifier, an update version date, and update data, and the original basic data main identifier is shared from a creator corresponding to a creator identifier; Obtaining the original basic data corresponding to the creator identifier and the original start and end version dates corresponding to the original basic data based on the original basic data main identifier; Updating the original basic data based on the update data to obtain updated basic data; Dividing the time range to which the original start and end version dates belong based on the update version date to obtain a first target start and end version date and a second target start and end version date, and generating a first secondary identifier corresponding to the updated basic data; the first target start and end version date is a start and end date with the start date of the original start and end version date as the start date and the update version date as the end date; the second target start and end version date is a start and end date with the update version date as the start date and the end date of the original start and end version date as the end date; Associating the original basic data main identifier, the first secondary identifier, the second target start and end version date, the requester identifier with the updated basic data, and associating the original basic data main identifier, the first target start and end version date, the requester identifier with the original basic data.

2. The method according to claim 1, characterized in that, Before obtaining the update request, where the update request carries a requester identifier, an original basic data main identifier, an update version date, and update information, and the original basic data main identifier is shared from a creator corresponding to a creator identifier, it further includes: Obtaining a query request, where the query request carries the requester identifier; Searching for the requester identifier in the shared object identifiers of a preset original basic data sharing relationship table corresponding to the creator identifier based on the query request; When the requester identifier is found, generating original basic data record information based on the original basic data code, the creator identifier, and the original start and end version dates in the original basic data sharing relationship table, and associating the original basic data record information with the original basic data; Returning the original basic data record information to the terminal corresponding to the requester identifier; When a modification request for the original basic data record information is obtained, obtaining an original basic data update interface based on the modification request, and returning the original basic data update interface to the terminal corresponding to the requester identifier; The obtaining of the update request includes: Obtaining the update request, where the update request is sent by the terminal corresponding to the requester identifier through the original basic data update interface.

3. The method according to claim 2, wherein Before obtaining the query request, it further includes: Receiving a sharing request, where the sharing request carries the creator identifier, the shared object identifier, and the original basic data main identifier; Associating and writing the creator identifier and the shared object identifier into the original basic data sharing relationship table corresponding to the original basic data main identifier based on the sharing request.

4. The method according to claim 1, wherein After associating the original basic data main identifier, the first secondary identifier, the second target start and end version dates, the requester identifier with the updated basic data, and associating the original basic data main identifier, the first target start and end version dates, the requester identifier with the original basic data, the method further includes: Generating updated basic data record information based on the original basic data code, the second target start and end version dates, and the requester identifier, and associating the updated basic data record information with the updated basic data; Generating target original basic data record information based on the original basic data code, the first target start and end version dates, and the requester identifier, and modifying the association relationship between the original basic data record information and the original basic data to the association between the target original basic data record information and the original basic data; Returning the updated basic data record information and the target original basic data record information to the terminal corresponding to the requester identifier.

5. The method according to claim 4, characterized in that After returning the updated basic data record information and the target original basic data record information to the terminal corresponding to the requester identifier, it further includes: Obtaining a deletion request, where the deletion request carries the updated basic data record information; Deleting the updated basic data associated with the updated basic data record information and the updated basic data record information, and restoring the second target start and end version dates in the original basic data record information to the original start and end version dates.

6. The method according to claim 1, characterized in that, After associating the original basic data main identifier, the first secondary identifier, the second target start and end version dates, the requester identifier with the updated basic data, and associating the original basic data main identifier, the first target start and end version dates, the requester identifier with the original basic data, it further includes: Obtaining a current update request, where the current update request carries the current version date, the current update data, and the original basic data main identifier; When the current version date is within the first target start and end version dates, dividing the first target start and end version dates based on the current version date to obtain a first update start and end version date and a second update start and end version date, and generating a second secondary identifier; Updating the original basic data based on the current update data to obtain current basic data, and updating the updated basic data based on the current update data to obtain the target basic data corresponding to the first secondary identifier; Associating the original basic data main identifier, the second secondary identifier, the second update start and end version dates, the requester identifier with the current basic data, and updating the first target start and end version dates associated with the original basic data to the first update start and end version dates.

7. A basic data update device, characterized in that, The device includes: An acquisition module, configured to acquire an update request, where the update request carries a requester identifier, an original basic data main identifier, an update version date, and update data, and the original basic data main identifier is shared from a creator corresponding to the creator identifier; acquire the original basic data corresponding to the creator identifier and the original start and end version dates corresponding to the original basic data based on the original basic data main identifier; An update module, configured to update the original basic data based on the update data to obtain updated basic data; A division module, configured to divide the time range to which the original start and end version dates belong based on the update version date to obtain a first target start and end version date and a second target start and end version date, and generate a first secondary identifier corresponding to the updated basic data; the first target start and end version date is a start and end date with the start date of the original start and end version date as the start date and the update version date as the end date; the second target start and end version date is a start and end date with the update version date as the start date and the end date of the original start and end version date as the end date; An association module, configured to associate the original basic data main identifier, the first secondary identifier, the second target start and end version date, the requester identifier with the updated basic data, and associate the original basic data main identifier, the first target start and end version date, the requester identifier with the original basic data.

8. A computer device, comprising a memory and a processor, the memory storing a computer program, characterized in that, When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product comprising a computer program, characterized in that, When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images