ERP system update prompt method, device, electronic device and storage medium

Abstract

The present application provides an update prompt method, device, electronic device and storage medium for an ERP system, and relates to the field of ERP technology. The method is applied to a cloud server, and includes: receiving query metadata sent by a main system or an offline client when executing a local query instruction; determining the update status of the query target information according to the query metadata and the data update log; when it is determined that the update status is updated, sending update prompt information to the main system or client that sent the query metadata, so that the main system or client that executes the local query instruction displays the update status of the target information when the query result is obtained. The present application can prompt the user data update status and improve the user experience.

Description

Technical Field

[0001] The present application relates to the field of ERP technology, and in particular to an update prompt method, device, electronic device and storage medium for an ERP system. Background Art

[0002] In the application of enterprise resource planning (ERP) system, there are two main ways of data interaction: Internet-based connection and LAN-based connection. Each method has its specific application scenarios and advantages and disadvantages.

[0003] Internet-based ERP system:

[0004] This solution is usually deployed in the cloud, and its main features include:

[0005] a) Convenient remote access: Employees can access the ERP system from anywhere through the Internet.

[0006] b) Real-time data synchronization: As long as there is a network connection, the data can be kept updated in real time.

[0007] c) Centralized management: System maintenance and updates can be centralized in the cloud.

[0008] d) Scalability: Ability to quickly expand system resources based on demand.

[0009] However, this solution also has obvious disadvantages:

[0010] a) Data security risks: Enterprise data is exposed on the public network and faces higher security threats.

[0011] b) Strong network dependence: The operation of the system is heavily dependent on the stability of the Internet connection.

[0012] c) Data transfer costs: Large amounts of data transfer may result in high network charges.

[0013] d) Privacy compliance issues: Data in some industries may be subject to regulatory restrictions and are not allowed to be stored on public clouds.

[0014] ERP system based on LAN:

[0015] Many companies, especially those with high data security requirements, choose to use a LAN connection. The main advantages of this solution include:

[0016] a) Higher data security: Data storage and transmission are limited to the enterprise's internal network, greatly reducing the risk of external intrusion.

[0017] b) Faster data transfer speed: LANs usually provide higher bandwidth and lower latency.

[0018] c) Lower operating costs: No ongoing Internet data transfer charges are required.

[0019] d) Better privacy protection: Sensitive data is completely controlled by the enterprise itself, making it easier to comply with various data protection regulations.

[0020] e) High degree of customization: It can be deeply customized according to the specific needs of the enterprise.

[0021] However, LAN-based ERP systems also face some technical challenges, especially when dealing with clients that are temporarily offline:

[0022] Offline data update synchronization problem: When the client is temporarily out of the LAN (such as when an employee is away from home), the data updates performed locally cannot be synchronized to the main system in a timely manner.

[0023] Query results may be delayed: When offline, users can only access locally cached data, which may be outdated.

[0024] Data conflict during reconnection: When an offline client reconnects to the LAN, a data update conflict may occur with the main system.

[0025] Limited remote access capabilities: Remote access capabilities are more limited compared to Internet-based solutions.

[0026] These issues affect the data consistency and user experience of LAN-based ERP systems, especially in work scenarios where employees need to leave the office frequently or move between different office locations.

[0027] Therefore, the existing technology needs to be improved. Summary of the invention

[0028] The purpose of the present application is to provide an update prompt method, device, electronic device and storage medium for an ERP system, which has the advantages of prompting users of data update status and improving data consistency and user experience.

[0029] In the first aspect, the present application provides an update prompt method for an ERP system, and the technical solution is as follows:

[0030] The ERP system includes a main system, a client and a cloud server. The main system and the client interact with each other via a local area network.

[0031] The cloud server is connected to the main system and the client in an offline state through the Internet respectively, and a data update log is established and maintained in the cloud server to record the data update status in the ERP system. The method is applied to the cloud server and includes the following steps:

[0032] Receiving query metadata sent by the host system or the client in an offline state when executing a local query instruction;

[0033] Determining an update status of the query target information according to the query metadata and the data update log;

[0034] When it is determined that the update status is updated, update prompt information is sent to the main system or the client that sends the query metadata, so that the main system or the client that executes the local query instruction displays the update status of the target information when obtaining the query result.

[0035] The update prompt method of the ERP system provided in the present application uses the Internet to connect the cloud server and the main system and the client in an offline state respectively, and establishes and maintains a data update log in the cloud server to record the update status of all data objects in the ERP system, which effectively solves the problem of delayed synchronization data faced by the client in an offline state in the ERP system based on the local area network. The cloud server displays the data update status to enable the user to understand whether the target information has been updated, avoid the use of outdated data, improve the user experience, and ensure the consistency and integrity of the data.

[0036] Further, in the present application, the query metadata at least includes a query object identifier and a target timestamp, the query object identifier is used to uniquely identify the target information of the query, and the target timestamp is used to indicate the update time of the target information locally;

[0037] The step of determining the update status of the query target information according to the query metadata and the data update log comprises:

[0038] Retrieving the latest update record of the target information matching the query object identifier from the data update log;

[0039] Comparing the timestamp of the latest update record with the target timestamp;

[0040] When the timestamp of the latest update record is later than the target timestamp, the update status is determined as updated.

[0041] By comparing the timestamp of the latest update record with the target timestamp, it is determined whether the data has been updated, and an update prompt message is sent to the user when the data update status is determined to be updated. This helps users understand whether the information they are viewing is the latest, so that they can make decisions based on the latest data, which helps improve work efficiency, reduce data conflicts and reduce LAN bandwidth pressure, and ensure the real-time and accuracy of query data.

[0042] Further, in the present application, when receiving a connection request sent by the client via the Internet, verifying whether the client is in an offline state;

[0043] When the client is in an offline state, the system is connected to the client in an offline state through the Internet to receive update information involving update objects and update timestamps generated by the client performing operations in an offline state for updating the data update log, and also to receive the query metadata sent by the client in an offline state when executing the local query instruction.

[0044] Furthermore, in the present application, after connecting to the client in an offline state through the Internet, the identity information of the client in an offline state is obtained;

[0045] Obtaining, according to the identity information, associated operation type information corresponding to the identity information;

[0046] The step of retrieving the latest update record of the target information matching the query object identifier from the data update log comprises:

[0047] When the query metadata is sent by the main system, judging whether the target information belongs to the associated operation type information according to the query object identifier;

[0048] When the target information belongs to the associated operation type information, retrieving the latest update record of the target information matching the query object identifier from the data update log;

[0049] When the target information does not belong to the associated operation type information, the update status is determined to be not updated.

[0050] Obtaining data update status based on associated operation type information can ensure data consistency and security, better control data access permissions, and ensure that only authorized users can update related data. At the same time, providing accurate data update status information can also help users understand whether the data they are querying is the latest, so that they can make decisions based on the latest data, help users improve work efficiency, ensure security and accuracy, and enhance user experience.

[0051] Further, in the present application, when the target information belongs to the associated operation type information, the step of retrieving the latest update record of the target information matching the query object identifier from the data update log includes:

[0052] Verify whether the client corresponding to the obtained identity information has undergone data synchronization with the main system;

[0053] When the corresponding client has not undergone data synchronization with the main system, if the target information belongs to the associated operation type information, the latest update record of the target information matching the query object identifier is retrieved from the data update log.

[0054] Further, in the present application, the step of determining the update status of the query target information according to the query metadata and the data update log includes:

[0055] When a plurality of query metadata are received within a preset time, determining a dependency relationship between the plurality of query metadata;

[0056] Adjusting the order of the requests corresponding to the plurality of query metadata according to the dependency relationship;

[0057] According to the adjusted sequence, the update status of the query target information is determined using the corresponding query metadata and the data update log.

[0058] By determining the dependencies of query metadata, the cloud server can ensure that the order of query requests is correct to ensure that subsequent queries use the latest data update status, thereby ensuring data accuracy and consistency, helping to improve the reliability and user experience of remote access to the ERP system, optimize the ERP system data processing thread, and avoid data conflicts.

[0059] Further, in the present application, the step of determining the update status of the query target information using the corresponding query metadata and the data update log according to the adjusted order includes:

[0060] According to the adjusted order, when two adjacent query metadata have a dependency relationship, after using the corresponding earlier query metadata and the data update log to determine the update status of the query target information, the corresponding later query metadata and the data update log are used again after a preset time to determine the update status of the query target information;

[0061] The method further includes:

[0062] A waiting prompt message is sent to the main system or the client corresponding to the query metadata and the data update log that need to be used after a preset time to determine the update status of the query target information.

[0063] By sending a waiting prompt message, users can be informed that data is being updated, avoiding them from repeatedly initiating unnecessary query requests, thereby improving user experience. Reducing unnecessary query requests can reduce system load and improve system performance. Waiting for prompt information can ensure that requests with later dependencies can obtain the latest data, thereby ensuring data consistency. By waiting for a preset time, data conflicts between requests with earlier dependencies and requests with later dependencies can be avoided. Waiting for prompt information can clearly inform users of the progress of data updates and let users understand the status of data updates, which helps to improve the reliability of remote access to the ERP system and improve user experience.

[0064] In a second aspect, the present application provides an update prompt device for an ERP system, the ERP system comprising a main system, a client and a cloud server, the main system and the client perform data interaction via a local area network, the cloud server is respectively connected to the main system and the client in an offline state via the Internet, a data update log is established and maintained in the cloud server, and is used to record the data update status in the ERP system, the device comprising:

[0065] The first module is used to receive query metadata sent by the main system or the client in an offline state when executing a local query instruction;

[0066] The second module is used to determine the update status of the query target information according to the query metadata and the data update log;

[0067] The third module is used to send update prompt information to the main system or the client that sends the query metadata when it is determined that the update status is updated, so that the main system or the client that executes the local query instruction displays the update status of the target information when obtaining the query results.

[0068] According to a third aspect, an electronic device is provided, comprising a processor and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps of the method provided in the first aspect are performed.

[0069] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps in the method provided in the first aspect are performed.

[0070] As can be seen from the above, the present application provides an update prompt method, device, electronic device and storage medium for an ERP system, which utilizes a cloud server to be connected to a main system and an offline client via the Internet, respectively, and establishes and maintains a data update log in the cloud server to record the data update status in the ERP system, and receives query metadata sent by the main system or the offline client when executing a local query instruction; determines the update status of the query target information according to the query metadata and the data update log; and when it is determined that the update status is updated, sends update prompt information to the main system or the client that sent the query metadata, so that the main system or the client that executes the local query instruction displays the update status of the target information when obtaining the query result;

[0071] This application has the following beneficial effects:

[0072] (1) Improving user experience: By updating prompt information, users can understand the update status of the target information and avoid using outdated data. This solves the problem of delayed data query results in offline state and improves user experience.

[0073] (2) Complete data synchronization based on the local area network, with low cost and high security. BRIEF DESCRIPTION OF THE DRAWINGS

[0074] Figure 1 A flow chart of the update prompt method of the ERP system provided in this application.

[0075] Figure 2 A structural schematic diagram of an update prompt device for an ERP system provided in this application.

[0076] Figure 3 A schematic diagram of the structure of the electronic device provided in this application.

[0077] Description of reference numerals: 200, update prompt device of ERP system; 201, first module; 202, second module; 203, third module; 300, electronic device; 301, processor; 302, memory; 303, communication bus. DETAILED DESCRIPTION

[0078] The technical solutions in the present application will be clearly and completely described below in conjunction with the drawings in the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the present application for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0079] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0080] The full name of ERP system is Enterprise Resource Planning, which is a software system that integrates various functions of enterprise management. It can help enterprises optimize resource allocation, improve operational efficiency, reduce costs, and enhance market competitiveness. In the current existing technology, the Internet-based ERP system provides a convenient remote access function, but the security of the data cannot be fully guaranteed. Although the ERP system based on the LAN can ensure the high security of data storage and processing in the enterprise's internal LAN, its remote access capability is limited. Enterprises use ERP systems based on LANs for production planning, material management, business management, etc. In work scenarios where employees need to leave the office frequently or move between different office locations, the need for ERP systems to support remote access is more prominent. As an information management tool for data storage and processing, users expect the ERP system to ensure data security and facilitate remote access. In order to achieve this expectation, the present application provides an update prompt method, device, electronic device and storage medium for an ERP system.

[0081] Among them, the ERP system may include components such as the main system, the client and the cloud server. The main system can be installed on the internal server of the enterprise, responsible for storing and managing enterprise data and processing client requests. The main system is the core component for data processing. The client can be installed on the enterprise employee terminal to access the main system for data operations. Data operations may include data query, data entry, business processing and other operations. The enterprise employee terminal can be a desktop computer, laptop, mobile phone or tablet computer, etc. The main system and the client interact with data through the local area network; the cloud server can be deployed on a public cloud or private cloud platform. The cloud server is connected to the main system and the offline client through the Internet respectively. It is responsible for maintaining the data update log and providing update reminder services, recording the data update status in the ERP system. The data update status includes updated and not updated. The offline client may be an enterprise employee terminal that has left the enterprise local area network and cannot connect to the main system to directly access the data in the ERP system.

[0082] like Figure 1 As shown, Figure 1 A flowchart of an update prompt method for an ERP system provided in an embodiment of the present application, the method is applied to a cloud server, and the update prompt method for an ERP system provided in an embodiment of the present application includes the following steps:

[0083] Step S101: receiving query metadata sent by the main system or the client in an offline state when executing a local query instruction;

[0084] Step S102: determining the update status of the query target information according to the query metadata and the data update log;

[0085] Step S103: When it is determined that the update status is updated, an update prompt message is sent to the main system or the client that sends the query metadata, so that the main system or the client that executes the local query instruction displays the update status of the target information when obtaining the query result.

[0086] Specifically, when a user performs a local data query, the main system or an offline client executes a local data query instruction to access the locally stored data, so that the user can obtain the data query results anytime and anywhere. When the client is offline, it cannot interact with the main system through the local area network, resulting in the data queried by the main system or the offline client may not be the latest data. At this time, the cloud server of the present application receives the query metadata when the main system or the offline client executes the local query instruction, and determines the update status of the query target information accordingly. When it is determined that the update status is updated, an update prompt message is sent to the main system or the client that sent the query metadata, and the update status of the target information is displayed when the query result is obtained. Among them, the data update log can record the update history of all data in the ERP system, which is convenient for data tracing and analysis. The update status of the query target information can be judged according to the data update log, such as whether it has been updated, when it was updated, etc.

[0087] For example, a manufacturing company uses a LAN-based ERP system for production planning, material management, quality management, etc. Employees often need to move between different office locations, such as from the office to the production workshop. Employee A modifies and updates an order A in the office, saves the order A information and synchronizes it to the local database of the main system. When the client in the production workshop is disconnected from the LAN for some reason, the client in the production workshop is offline and does not synchronize the relevant information of the order A modified and updated by employee A in the office in time. Employee B needs to view the detailed information of the order A on the offline client in the production workshop. Employee B executes the local query instruction. The offline client sends the query metadata to the cloud server. The cloud server retrieves the data update log according to the query metadata and finds that the information of order A has been updated. The cloud server returns the update prompt information to the client. The client displays the update prompt information to employee B, so that employee B knows that the information of order A has been updated, avoids the use of wrong and outdated data, and ensures the consistency and accuracy of the data. The offline client connects to the cloud server through the Internet to obtain whether the data has been updated.

[0088] In the prior art, a general ERP system either uses a LAN communication or an Internet communication. Since an ERP system usually involves confidential data within an enterprise, the mainstream practice is to use a LAN communication, which has high security and low data synchronization costs. However, for LAN communication, there are great geographical constraints. If you leave a certain range, the LAN connection will be disconnected. In order to ensure that employees can still work while on a business trip, a certain amount of data can be stored locally on the client, and this data can be accessed locally on the client. However, the disadvantage of this method is the timeliness of data updates. That is, if some data is updated, the client disconnected from the LAN cannot synchronize the data and cannot know whether the data is updated. In this case, outdated data may be used when working.

[0089] It is based on the above-mentioned practical application scenarios that the present application proposes to use a local area network to realize data interaction between the client and the main system, and further proposes to set up a cloud server, establish and maintain a data update log in the cloud server. Specifically, the cloud server is connected to the main system through the Internet, and the cloud server is connected to an offline client through the Internet. Among them, the offline client specifically refers to the client that has disconnected from the local area network connection with the main system. Since the cloud server is connected to the main system and the offline client through the Internet, the data update log can be maintained through the Internet. Specifically, a data update log is established in the cloud server, and the data update log can specifically include the data type name and the last update time. When the main system or the offline client changes the data, it will send the data to the cloud server through the Internet, and the cloud server will maintain the data update log after receiving the data.

[0090] It is worth noting that the cloud server only obtains which data has been updated, but not the specific updated data. For example, the cloud server obtains the updated information of the quotation change of a certain business. At this time, the cloud server only obtains the business type and the updated time information, but does not know the specific updated content. Since the cloud server does not obtain the specific updated content, the burden on the cloud server will be very small. At the same time, since it does not involve the transmission of specific updated content, the security will be very high and there will be no data leakage.

[0091] The core technical concept of this application is actually to use the cloud server as a lightweight data update prompt center: this is the most significant innovation of this solution. Traditional ERP systems usually rely on the main system to directly manage all data synchronization and update notifications, while this solution introduces a cloud server as an independent middle layer that specializes in monitoring and notification of data update status. This design greatly reduces the burden on the main system while improving the response speed and flexibility of the system. In addition, this application combines offline operations with real-time update prompts: conventional ERP systems usually find it difficult to effectively handle data inconsistencies caused by offline operations. This solution uses a cloud server to achieve a seamless combination of offline operations and real-time update prompts, so that even in an offline state, users can promptly know the data update status, which greatly improves the system's availability and data consistency. Separate connection mechanism: LAN data transmission and Internet status monitoring are handled separately, which not only improves the security and efficiency of data transmission, but also enhances the reliability and flexibility of the system and reduces the cost of data synchronization.

[0092] Specifically, in some implementations, the query metadata includes at least a query object identifier and a target timestamp, the query object identifier is used to uniquely identify the queried target information, and the target timestamp is used to indicate the update time of the local target information;

[0093] In the ERP system, query metadata is auxiliary information used to describe the query target and query conditions, and is used to optimize the query process to obtain the target information that the user expects. The query object identifier is used to uniquely identify the target information of the query. It can be a unique order number, customer ID, material code, or any other field that can uniquely identify a specific data item. For example, if a user wants to query the latest status of an order, the order number of the order can be provided as the query object identifier when performing a local data query. Each order has its unique order number, so the order number can be used as a field that uniquely identifies different orders. The target timestamp is used to indicate the update time of the local target information. The target timestamp reflects the last update time when the user records the data in the local system. For example, if a user updates the status of an order in the local system, the timestamp of the last modification of the order is recorded as the target timestamp.

[0094] Furthermore, the step of determining the update status of the query target information according to the query metadata and the data update log includes:

[0095] Retrieving the latest update record of the target information matching the query object identifier from the data update log;

[0096] Compare the timestamp of the latest updated record with the target timestamp;

[0097] When the timestamp of the latest update record is later than the target timestamp, the update status is determined as updated;

[0098] The data update log in the cloud server records the update status of all data objects, including the update object identifier, which is used to uniquely identify the updated object in the ERP system, such as order number, customer number, product number, etc.; it also includes the update record timestamp, which is used to indicate the time when the update operation occurs; and the update type, which indicates the type of update operation, such as adding, modifying, deleting, etc.; and the update content, which indicates the specific content of the update operation, such as the modified data value, etc. When the cloud server receives the query metadata sent from the main system or the client in the offline state, the cloud server will retrieve the latest update record of the target information matching the identifier in the data update log according to the query object identifier, and then compare the timestamp of the retrieved latest update record with the target timestamp contained in the query metadata. If the timestamp of the latest update record is later than the target timestamp, it means that the data update log of the cloud server has been updated after the user last viewed or modified the target information. In this case, the cloud server will determine the update status as updated. If the timestamp of the latest update record is earlier than or equal to the target timestamp, it means that the data of the cloud server has not been updated, or the update occurred before the user last viewed or modified it. At this time, the cloud server will determine the data update status as not updated.

[0099] In this way, it is possible to determine whether the data has been updated and send an update prompt to the user when the data update status is determined to be updated. This helps users understand whether the information they are viewing is the latest and make decisions based on the latest data.

[0100] Specifically, in some embodiments, upon receiving a connection request sent by a client via the Internet, verifying whether the client is in an offline state;

[0101] When the client is in an offline state, it is connected to the offline client through the Internet to receive update information involving update objects and update timestamps generated by the client performing operations in an offline state for updating the data update log, and is also used to receive query metadata sent by the offline client when executing local query instructions.

[0102] When the client sends a connection request to the cloud server via the Internet, the cloud server will first verify the status of the client to ensure the security and effectiveness of the connection. In some embodiments, the method of verifying the status of the client can be connection request analysis. When the cloud server receives the connection request from the client, it analyzes the source and status of the request. If the request is sent via the Internet rather than the local area network, this may indicate that the client is currently not in the local area network and is offline; the verification method can also be network address verification. The cloud server will check the network address of the client, usually by IP address. If the IP address of the client is not within the range of the local area network, it means that the client is offline; the verification method can also be data synchronization status check. The cloud server will check the data synchronization status of the client and the main system. If it is found that the data of the client is inconsistent with the main system, or the data update log of the client shows that the last update time is earlier than the record of the cloud server, this indicates that the client is offline; the cloud server accurately determines whether the client is offline and provides corresponding services and support for the offline client.

[0103] That is, in some specific implementations, the cloud server will only connect to clients that are offline, but not to clients that are online, because clients that are online can complete data synchronization with the main system through the local area network.

[0104] In the ERP system, in order to ensure the real-time update and consistency of data, especially when the client is offline, which means that the client's LAN connection with the main system has been disconnected, but the client can still access the Internet. This connection allows the client to communicate with the cloud server, and the cloud server can receive the data update information generated by the client's offline operations, including the update object and the update timestamp, which are used to update the data update log on the cloud server. When the client reconnects to the LAN, the client will synchronize data with the main system to ensure data consistency. When the client performs operations in an offline state, such as modifying order information, updating inventory quantities, etc., the update object can be, for example, the order amount or material quantity, and the update timestamp is the time point when the user last modified the update object.

[0105] In some embodiments, the cloud server maintains a data update log based on the update information to know what types of information have been updated. At this time, the cloud server can trigger auxiliary operations of data synchronization as needed. Before performing data synchronization, the cloud server can notify the client and the server which data needs to be synchronized. This can avoid verifying all data, thereby improving the data synchronization efficiency between the main system and the client, and ensuring that the data in the main system is consistent with the client.

[0106] Specifically, in some implementations, after connecting to the client in an offline state through the Internet, obtaining the identity information of the client in an offline state;

[0107] Obtaining associated operation type information corresponding to the identity information according to the identity information;

[0108] Among them, identity information refers to the identification used to identify and verify the identity of the client. The identity information obtained by the cloud server from the offline client may include a user name, client ID or other unique identifier. The identity information helps the cloud server distinguish different clients and determine their roles and permissions in the ERP system. Based on the identity information obtained from the offline client, the cloud server can determine the associated operation type information corresponding to the identity information. For example, an employee in a sales department can only maintain data type information such as customer information and order amount of related orders, and an employee in a warehouse management department can only maintain specific data type information such as material information and inventory information. Associated operation type information refers to other data objects or operation types associated with a specific data object. Obtaining the associated operation type information helps the cloud server to control the user's permissions more accurately, prevent users from accessing or modifying data that they should not access or modify, and determine which data objects are related to the operations of a specific client, so as to better achieve the consistency and integrity of data management, and help improve the reliability and user experience of remote access to the ERP system.

[0109] Further, the step of retrieving the latest update record of the target information matching the query object identifier from the data update log includes:

[0110] When the query metadata is sent by the main system, it is determined whether the target information belongs to the associated operation type information according to the query object identifier;

[0111] When the target information belongs to the associated operation type information, the latest update record of the target information matching the query object identifier is retrieved from the data update log;

[0112] When the target information does not belong to the associated operation type information, the update state is determined to be not updated.

[0113] Among them, when the cloud server receives the query metadata of the local query instruction, the cloud server retrieves the latest update record of the target information matching the query object identifier in the query metadata in the data update log to determine the update status of the query target information. If the query metadata is sent by a client in an offline state, the cloud server performs a retrieval of the corresponding data update status according to the identity information of the offline client obtained previously and the corresponding associated operation type information. The identity information of the offline client determines its operation authority and access scope in the ERP system. The associated operation type information is determined based on these operation authorities, which defines the data objects that the client can operate and their related operation types. When the query metadata is sent by an offline client, it is usually because the offline client needs to query data related to its operation authority. The query metadata sent by the client usually contains a data object identifier that matches the offline client's operation authority. The cloud server can directly retrieve the latest update record of the target information matching the identifier in the data update log according to the data object identifier that matches the offline client's operation authority, and return the update status of the target information to the offline client.

[0114] If the target information does not belong to the associated operation type information, this means that the offline client does not have the authority to operate the data object, or the data object is not directly related to the operation of the offline client. Therefore, the cloud server will determine the update status as not updated, that is, the target information has not been updated during the offline period. In this case, the cloud server does not need to further determine whether the target information is really not updated, because the offline client has no authority to operate the data object at all. If the target information belongs to the associated operation type information, the cloud server will retrieve the latest update record of the target information that matches the query object identifier from the data update log. When the target information belongs to the associated operation type information corresponding to the offline client, this means that the target information data object is directly associated with the associated operation type information corresponding to the current offline client, and the client has the authority to operate it, then it is possible that the data update has occurred when executing the offline client's data operation request. The cloud server needs to further retrieve the latest update record of the target information from the data update log and return the update status of the queried target information to the main system.

[0115] In this way, data access rights can be better controlled to ensure that only authorized users can update relevant data, ensure data consistency and security, and provide accurate data update status information. It also helps users understand whether the data they query is the latest, so that they can make decisions based on the latest data, help users improve work efficiency, ensure the real-time and accuracy of data, and enhance user experience and remote access capabilities of ERP systems based on LANs.

[0116] Specifically, in some implementations, when the target information belongs to the associated operation type information, the step of retrieving the latest update record of the target information matching the query object identifier from the data update log includes:

[0117] Verify whether the corresponding client that has obtained the identity information has synchronized data with the main system;

[0118] When the corresponding client has not undergone data synchronization with the main system, if the target information belongs to the associated operation type information, the latest update record of the target information matching the query object identifier is retrieved from the data update log.

[0119] Among them, data synchronization refers to the exchange of data between the client and the main system to ensure that the data on the client is consistent with the data on the main system. Data synchronization helps to avoid data inconsistencies or conflicts, especially when multiple clients operate the same data object at the same time. The cloud server will check whether the corresponding client that has obtained the identity information has completed data synchronization with the main system, and whether the client's data matches the data on the main system to ensure data consistency. If the corresponding client has not completed data synchronization with the main system, the cloud server needs to take measures to deal with this problem. For example, the cloud server can mark the client data as pending synchronization, or prioritize synchronizing the associated operation type information when the client reconnects, and can also handle inconsistent data based on update records and maintain data consistency.

[0120] Furthermore, if data synchronization has not been performed between the offline client and the main system, it proves that the data may have been updated. When the target information belongs to the associated operation type information, it means that the target information data object is directly associated with the associated operation type information corresponding to the current offline client, and the client has the authority to operate it. Then it is possible that the data update status has changed when executing the offline client's data operation request. The cloud server needs to further retrieve the latest update record of the target information from the data update log and return the update status of the queried target information to the offline client.

[0121] By verifying the client's identity information and confirming its data synchronization status with the main system, even if the data of the client is inconsistent with the main system, the cloud server can retrieve the data update log, update and record the data update status to ensure data consistency and accuracy, while improving the reliability and user experience of remote access to the ERP system, ensuring that users can obtain the latest records of data update status and improve work efficiency.

[0122] Specifically, in some implementations, the step of determining the update status of the query target information according to the query metadata and the data update log includes:

[0123] When multiple query metadata are received within a preset time, determining a dependency relationship between the multiple query metadata;

[0124] Adjust the order of requests corresponding to multiple query metadata according to the dependency relationship;

[0125] According to the adjusted sequence, the update status of the query target information is determined using the corresponding query metadata and update log.

[0126] The preset time refers to a time period set by the cloud server. During this time period, if the cloud server receives multiple query metadata, it will trigger a mechanism for processing the dependency relationship between the multiple query metadata. For example, the cloud server may set a time interval of 30 seconds, 1 minute or 3 minutes. If multiple query metadata are received within the preset time, it will trigger a mechanism for processing the dependency relationship. In the ERP system, different query metadata may involve different data objects and operations, and there may be dependencies between different query metadata, that is, the execution of one query instruction may depend on the result of another query. The cloud server needs to analyze the multiple query metadata received and determine the dependency relationship between them. First, check the query object identifier in each query metadata to determine whether they involve the same or related data objects. If it is found that there is a dependency relationship between multiple query metadata, the cloud server needs to adjust the order of the requests corresponding to the query metadata according to these relationships. For example, if query metadata 1 depends on the result of query metadata 2, the cloud server will process query metadata 2 first, and then query metadata 1. Assume a scenario: User A sends a query metadata 1 to query the latest status of order number 12345, user B sends a query metadata 2 to query the production progress of order number 12345, and user C sends a query metadata 3 to query the material quantity of order number 12345. Query metadata 1, 2, and 3 all involve the same order number 12345, but they query different data objects, and there is a dependency relationship between them, because query metadata 3 needs to query the material quantity of order number 12345, and this information depends on the production progress of order number 12345, that is, the result of query metadata 2. Therefore, the query requests are sorted in the order of processing query metadata 2 first, then query metadata 3, and finally query metadata 1. According to the adjusted order, the cloud server uses the corresponding query metadata and data update log to determine the update status of the query target information.

[0127] Specifically, the order is adjusted to ensure the accuracy of the data. Because when the data to be queried are interdependent, the execution of a query instruction may depend on another query result. In other words, another query result may cause the related data to be updated. For example, a user queries the order price and needs to update the order quantity based on the order price, while another user needs to query the order quantity. At this time, although the order quantity data has not been updated, another user may modify and update the order quantity based on the order price. Therefore, when query instructions for querying order price and querying order quantity appear, the order of the two will be adjusted so that the query of order price comes first and the query of order quantity comes later.

[0128] By determining the dependencies of query metadata, the cloud server can ensure that the order of query requests is correct to ensure that subsequent queries use the latest data update status, thereby ensuring data accuracy and consistency, helping to improve the reliability and user experience of remote access to the ERP system, optimize the ERP system data processing thread, and avoid data conflicts.

[0129] Specifically, in some implementations, the step of determining the update status of the query target information using the corresponding query metadata and the data update log according to the adjusted sequence includes:

[0130] According to the adjusted order, when two adjacent query metadata have a dependency relationship, after using the corresponding earlier query metadata and data update log to determine the update status of the query target information, the corresponding later query metadata and data update log are used again after a preset time to determine the update status of the query target information;

[0131] Among them, the cloud server determines that there is a dependency between the query metadata, and then readjusts the query order according to the dependency. The actual query order may be different from the order of receiving the query metadata. For example, the cloud server first receives query metadata 1 and then receives query metadata 2. However, if query metadata 1 depends on the result of query metadata 2, then there is a dependency between the two query metadata. Query metadata 2 is the first query metadata, and query metadata 1 belongs to the later query metadata. When actually retrieving the data update log to obtain the data update status of the target information, it is necessary to first retrieve the data update status of query metadata 2. After determining the data update status of the query metadata, the latest update record of its target information is retrieved according to query metadata 1 to determine the data update status. On this basis, the cloud server will set a preset time interval to determine the processing order between two adjacent query metadata. The setting of the preset time interval needs to consider the system's processing capacity, the amount of data, and the needs of users. For example, the preset time interval can be set to 30 seconds, 1 minute or 3 minutes, which means that within the preset time interval, the cloud server will give priority to processing the first query metadata in the dependency relationship. In the process of the cloud server retrieving the latest update record of the target information, the target data of the first query metadata may be updated. The cloud server will maintain the data update log according to the first query metadata at any time to keep the data stored on the cloud server and the data update log synchronized, thereby ensuring that the data update status is the latest, and then process the subsequent query metadata in the dependency relationship to ensure that the query results obtained by the user are based on the latest data update status.

[0132] Furthermore, it also includes:

[0133] A waiting prompt message is sent to a main system or client corresponding to the query metadata and data update log that need to be used after a preset time to determine the update status of the query target information.

[0134] Among them, when the cloud server prioritizes the processing of the first query metadata in the dependency relationship, in the process of the cloud server retrieving the latest update record of the target information, the cloud server will send a waiting prompt message to the main system or offline client corresponding to the query metadata 1, prompting that the latest update record of the data of the first query metadata is currently being retrieved, and the main system or offline client needs to wait for a period of time to obtain the updated target information. By sending the waiting prompt message, it can be ensured that the initiator of the request in the later dependency relationship understands the progress of the data update and avoids it from repeatedly initiating unnecessary query requests. In actual applications, the method of sending the waiting prompt message can be adjusted according to the specific situation and system design. For example, it can be a pop-up prompt. When the main system or offline client receives the waiting prompt message, a dialog box can be popped up to inform the user that it needs to wait for a period of time to obtain the updated data, and an estimated waiting time is provided. It can also be a status bar display. An icon or text can be displayed in the status bar to indicate that the data is being updated, and a rotating loading animation or progress bar is provided to let the user know the update progress. It can also be a voice prompt, a notification message or a customized prompt, etc., so as to ensure that the user will not miss the prompt of data update.

[0135] By sending a waiting prompt message, users can be informed that data is being updated, avoiding them from repeatedly initiating unnecessary query requests, thereby improving user experience. Reducing unnecessary query requests can reduce system load and improve system performance. Waiting for prompt information can ensure that requests with later dependencies can obtain the latest data, thereby ensuring data consistency. By waiting for a preset time, data conflicts between requests with earlier dependencies and requests with later dependencies can be avoided. Waiting for prompt information can clearly inform users of the progress of data updates and let users understand the status of data updates, which helps to improve the reliability of remote access to the ERP system and improve user experience.

[0136] like Figure 2 As shown, Figure 2 A structural diagram of an update prompt device for an ERP system provided in an embodiment of the present application, the device is applied to the field of ERP technology, the ERP system includes a main system, a client and a cloud server, the main system and the client interact with each other through a local area network, the cloud server is connected to the main system and the client in an offline state through the Internet, a data update log is established and maintained in the cloud server, and is used to record the data update status in the ERP system. The update prompt device 200 of the ERP system provided in the embodiment of the present application includes:

[0137] The first module 201 is used to receive query metadata sent by the main system or the client in an offline state when executing a local query instruction;

[0138] The second module 202 is used to determine the update status of the query target information according to the query metadata and the data update log;

[0139] The third module 203 is used to send update prompt information to the main system or client that sends the query metadata when determining that the update status is updated, so that the main system or client that executes the local query instruction displays the update status of the target information when obtaining the query result.

[0140] As can be seen from the above, the update prompt device of the ERP system provided in the embodiment of the present application is connected to the offline client through the cloud server, and the data update of the offline client can be synchronized to the main system in time, ensuring data consistency and avoiding the loss of data update in the offline state. The user can timely understand the update status of the target information and avoid using outdated data, thereby improving work efficiency, solving the problem of delayed data query results in the offline state, improving user experience, reducing the risk of data conflict when the offline client reconnects to the local area network, ensuring data consistency and accuracy, and enhancing the remote access capability of the ERP system based on the local area network.

[0141] In addition, in some preferred embodiments, the update prompt device of the ERP system proposed in the present application can execute any one of the steps in the above method.

[0142] Please refer to Figure 3 , Figure 3 A structural schematic diagram of an electronic device provided in an embodiment of the present application, the present application provides an electronic device 300, including: a processor 301 and a memory 302, the processor 301 and the memory 302 are interconnected and communicate with each other through a communication bus 303 and / or other forms of connection mechanisms (not marked), the memory 302 stores computer-readable instructions executable by the processor 301, when the electronic device is running, the processor 301 executes the computer-readable instructions to execute the method in any optional implementation of the above embodiment to achieve the following functions: receiving query metadata sent by a main system or an offline client when executing a local query instruction; determining an update status of the query target information according to the query metadata and the data update log; when it is determined that the update status is updated, sending an update prompt message to the main system or the client that sent the query metadata, so that the main system or the client that executes the local query instruction displays the update status of the target information when obtaining the query result.

[0143] An embodiment of the present application provides a computer-readable storage medium. When the computer program is executed by a processor, the method in any optional implementation of the above embodiment is executed to achieve the following functions: receiving query metadata sent by a main system or a client in an offline state when executing a local query instruction; determining the update status of the query target information according to the query metadata and the data update log; when it is determined that the update status is updated, sending update prompt information to the main system or the client that sent the query metadata, so that the main system or the client that executes the local query instruction displays the update status of the target information when obtaining the query result.

[0144] Among them, the computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable red-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0145] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. An update prompt method for an ERP system, wherein the ERP system includes a main system, a client and a cloud server, wherein the main system and the client interact with each other via a local area network, and wherein: The cloud server is connected to the main system and the client in an offline state through the Internet respectively, and a data update log is established and maintained in the cloud server to record the data update status in the ERP system. The method is applied to the cloud server and includes the following steps: Receiving query metadata sent by the host system or the client in an offline state when executing a local query instruction; Determining an update status of the query target information according to the query metadata and the data update log; When it is determined that the update status is updated, an update prompt message is sent to the main system or the client that sends the query metadata, so that the main system or the client that executes the local query instruction displays the update status of the target information when obtaining the query result; The cloud server only obtains which data is updated, but does not obtain the specific updated data.

2. The update prompt method of an ERP system according to claim 1, characterized in that: The query metadata at least includes a query object identifier and a target timestamp, wherein the query object identifier is used to uniquely identify the target information of the query, and the target timestamp is used to indicate the update time of the target information locally; The step of determining the update status of the query target information according to the query metadata and the data update log comprises: Retrieving the latest update record of the target information matching the query object identifier from the data update log; Comparing the timestamp of the latest update record with the target timestamp; When the timestamp of the latest update record is later than the target timestamp, the update status is determined as updated.

3. The update prompt method of an ERP system according to claim 2, characterized in that: The method further includes: When receiving a connection request sent by the client via the Internet, verifying whether the client is in an offline state; When the client is in an offline state, the system is connected to the client in an offline state through the Internet to receive update information involving update objects and update timestamps generated by the client performing operations in an offline state for updating the data update log, and also to receive the query metadata sent by the client in an offline state when executing the local query instruction.

4. The update prompt method of an ERP system according to claim 3, characterized in that: The method further includes: After connecting to the client in an offline state through the Internet, obtaining identity information of the client in an offline state; Obtaining, according to the identity information, associated operation type information corresponding to the identity information; The step of retrieving the latest update record of the target information matching the query object identifier from the data update log comprises: When the query metadata is sent by the main system, judging whether the target information belongs to the associated operation type information according to the query object identifier; When the target information belongs to the associated operation type information, retrieving the latest update record of the target information matching the query object identifier from the data update log; When the target information does not belong to the associated operation type information, the update status is determined to be not updated.

5. The update prompt method of an ERP system according to claim 4, characterized in that: When the target information belongs to the associated operation type information, the step of retrieving the latest update record of the target information matching the query object identifier from the data update log comprises: Verify whether the client corresponding to the obtained identity information has undergone data synchronization with the main system; When the corresponding client has not undergone data synchronization with the main system, if the target information belongs to the associated operation type information, the latest update record of the target information matching the query object identifier is retrieved from the data update log.

6. The update prompt method of an ERP system according to claim 1, characterized in that: The step of determining the update status of the query target information according to the query metadata and the data update log comprises: When a plurality of query metadata are received within a preset time, determining a dependency relationship between the plurality of query metadata; Adjusting the order of the requests corresponding to the plurality of query metadata according to the dependency relationship; According to the adjusted sequence, the update status of the query target information is determined using the corresponding query metadata and the data update log.

7. The update prompt method of an ERP system according to claim 6, characterized in that: The step of determining the update status of the query target information using the corresponding query metadata and the data update log according to the adjusted order includes: According to the adjusted order, when two adjacent query metadata have a dependency relationship, after using the corresponding earlier query metadata and the data update log to determine the update status of the query target information, the corresponding later query metadata and the update log are used again after a preset time to determine the update status of the query target information; The method further includes: A waiting prompt message is sent to the main system or the client corresponding to the query metadata and the data update log that need to be used after a preset time to determine the update status of the query target information.

8. An update prompt device for an ERP system, the ERP system comprising a main system, a client and a cloud server, the main system and the client interact with each other via a local area network, characterized in that: The cloud server is connected to the main system and the client in an offline state through the Internet respectively, and a data update log is established and maintained in the cloud server to record the data update status in the ERP system. The device includes: The first module is used to receive query metadata sent by the main system or the client in an offline state when executing a local query instruction; The second module is used to determine the update status of the query target information according to the query metadata and the data update log; The third module is used to send update prompt information to the main system or the client that sends the query metadata when it is determined that the update status is updated, so that the main system or the client that executes the local query instruction displays the update status of the target information when obtaining the query result; The cloud server only obtains which data is updated, but does not obtain the specific updated data.

9. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores computer-readable instructions. When the computer-readable instructions are executed by the processor, the steps in the method according to any one of claims 1 to 7 are executed.

10. A 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 7 are executed.

Images