ERP system inspection and monitoring method and device

Abstract

The present disclosure belongs to the field of nuclear power technology, and specifically relates to an ERP system inspection and monitoring method and device. The ERP system inspection and monitoring method provided by the present disclosure can deeply monitor the process processing performance of each application, automatically count the total amount of completed processes of each application within the same time window, and reveal relevant error information, so as to provide data support for evaluating the overall health status of the system. And further refine the mining of abnormal processes to ensure comprehensive monitoring of abnormal processes. In addition, it is also possible to monitor and count to form an alarm list to provide an accurate basis for subsequent troubleshooting. In this way, an integrated inspection report is constructed, and an inspection report with a clear structure and detailed content is automatically generated by intelligently integrating the above-mentioned multi-dimensional data collection and analysis results. This report not only provides a strong basis for operation and maintenance efficiency evaluation, but also can provide an accurate reference for troubleshooting and process optimization, ensuring the comprehensiveness and efficiency of the inspection work.

Description

Technical Field

[0001] The invention belongs to the field of information technology, and in particular relates to an ERP system inspection and monitoring method and device. Background Art

[0002] In the cloud-native MetaERP system, the introduction of microservice architecture has brought high flexibility and modular design, but it is also accompanied by a great complexity of the operation and maintenance system. With the expansion of business functions, the number of microservices has increased rapidly. Each service has its own deployment, logging, monitoring and expansion requirements, resulting in an exponential increase in the difficulty of operation and maintenance of the entire system. The intricate dependencies between services make troubleshooting difficult. The abnormality of a microservice may trigger a chain reaction, affecting the normal operation of other services.

[0003] MetaERP integrates multiple development and operation tools, including APIG, MQS and LiveFlow. However, the page functions of these tools are independent of each other, and the entrances to operation and maintenance monitoring are scattered in different systems. Operation and maintenance personnel need to frequently switch between various tools. The lack of a unified entrance and management platform greatly increases the complexity and workload of operation and maintenance.

[0004] In addition, since the MetaERP system integrates multiple business modules (such as finance, supply chain, sales, projects, human resources, etc.), the synchronization and sharing of data in each module makes the verification of business data consistency very complicated. Different users or roles have different permissions to access data, and different operations will also affect data consistency.

[0005] As the existing system lacks effective automated monitoring and early warning mechanisms, operation and maintenance personnel can only manually switch applications to check the operating status of each system one by one. There are more than 30 applications that need to be monitored in related application scenarios, and the number of applications is growing rapidly as the internal needs of the enterprise expand.

[0006] The complexity of business consistency monitoring has led to many limitations in traditional manual inspection methods. Due to human resource and time constraints, manual inspections can usually only conduct limited sampling inspections and cannot achieve global coverage, which can easily lead to missed detection or delayed discovery of potential problems. In addition, repetitive manual operations not only limit the work efficiency and creativity of staff, but also due to the lack of intelligent data analysis and prediction capabilities, similar problems recur and potential hidden dangers cannot be eliminated. Summary of the invention

[0007] In order to overcome the problems existing in the related art, a method and device for patrol inspection and monitoring of an ERP system are provided.

[0008] According to one aspect of an embodiment of the present disclosure, a method for patrol inspection and monitoring of an ERP system is provided, the method comprising:

[0009] Step 101, traverse each application in the system that belongs to the preset list;

[0010] Step 102, process monitoring, for the traversed application, log in to the overview page of the application, collect and count the process data of the application within a preset time period; the process data includes the total amount of workflow messages of the application and the completion status and error amount of each process;

[0011] Step 103, process tracking. For the traversed application, if the application is configured with an API, the log retrieval function is used to collect and count the process tracking data of the application's API in a preset period of time. The process tracking data includes the response status code and its number of the application in the preset period of time, and the response status code and its number indicating an abnormality or error;

[0012] Step 104, alarm monitoring, for the traversed application, log in to the MQS management page of the application, collect and count the total number of topics, the number of published topics, and the number of subscribed topics of the application; and query the consumption progress of each message in the topic. If accumulated messages are found, record the application name, topic name, and number of accumulated messages corresponding to the accumulated messages;

[0013] Step 105: Generate an inspection report based on the captured data and push it to the associated account. The inspection report includes process data, process tracking data and an alarm list of each application service.

[0014] In a possible implementation, the method further includes:

[0015] Step 106, within a preset period of time, the failed processes, timed-out processes, and successful process instances that took more than a preset execution time in the application in the acquired process data are determined as abnormal processes, and the abnormal processes are pushed to the associated account.

[0016] In a possible implementation, the method further includes:

[0017] Step 107, based on the acquired process data of the application and according to consistency verification rules, consistency verification is performed on the associated data of the core business process corresponding to the application;

[0018] Step 108: Push the associated data of the core business that has not passed the consistency check to the associated account.

[0019] In a possible implementation, step 107 includes any one or more of the following steps:

[0020] Step 1071, consistency check of purchase receipt quantity and purchase amount;

[0021] Step 1072, consistency check between the purchase receiving currency and the exchange rate on the purchase date;

[0022] Step 1073, consistency check of purchase order invoice matching type and invoice matching level;

[0023] Step 1074, verifying whether the amount of the purchase order is greater than the sum of the received amount and the cancelled amount;

[0024] Step 1075, consistency check of financial invoice creation, redemption and adjustment;

[0025] Step 1076, whether the moving average cost inventory transaction cost table amount is empty.

[0026] According to another aspect of the embodiment of the present disclosure, there is provided an ERP system inspection and monitoring device, the device comprising:

[0027] A traversal module is used to traverse each application in the system that belongs to the preset list;

[0028] The process monitoring module is used to log in to the overview page of the traversed application, collect and count the process data of the application within a preset time period; the process data includes the total amount of workflow messages of the application and the completion status and error amount of each process;

[0029] The interface monitoring module is used to collect and count the process tracking data of the API of the application in a preset period of time by using the log retrieval function for the traversed application, when the application is configured with an API. The process tracking data includes the response status code and its number of the application in the preset period of time, and the response status code and its number indicating an abnormality or error;

[0030] The message monitoring module is used to log in to the MQS management page of the traversed application, collect and count the total number of topics, the number of published topics, and the number of subscribed topics of the application; and query the consumption progress of each message in the topic. If accumulated messages are found, the application name, topic name, and number of accumulated messages corresponding to the accumulated messages are recorded;

[0031] The report generation module is used to generate an inspection report based on the captured data and push it to the associated account. The inspection report includes process data, process tracking data and an alarm list of each application service.

[0032] In a possible implementation manner, the device further includes:

[0033] The abnormal process monitoring module is used to identify the failed processes, timed-out processes, and successful process instances that take more than a preset time to execute in the acquired process data of the application within a preset time period as abnormal processes, and push the abnormal processes to the associated account.

[0034] In a possible implementation manner, the device further includes:

[0035] A verification module is used to perform consistency verification on the associated data of the core business process corresponding to the application according to the obtained process data of the application and the consistency verification rules;

[0036] The verification push module is used to push the related data of the core business that has not passed the consistency check to the related accounts.

[0037] In a possible implementation, any one or more of the following submodules are included in the verification module:

[0038] The first verification submodule is used for consistency verification of the purchase quantity received and the purchase amount;

[0039] The second verification submodule is used to verify the consistency between the purchase receiving currency and the exchange rate on the day of purchase;

[0040] The third verification submodule is used for consistency verification of purchase order invoice matching type and invoice matching level;

[0041] The fourth verification submodule is used to verify whether the amount of the purchase order is greater than the sum of the received amount and the cancelled amount;

[0042] The fifth verification submodule is used for consistency verification of financial invoice creation, red offset and adjustment.

[0043] The sixth check submodule is used to check whether the amount in the moving average cost inventory transaction cost table is empty.

[0044] According to another aspect of the embodiment of the present disclosure, there is provided an ERP system inspection and monitoring device, the device comprising:

[0045] processor;

[0046] a memory for storing processor-executable instructions;

[0047] Wherein, the processor is configured to execute the above method.

[0048] According to another aspect of an embodiment of the present disclosure, a non-volatile computer-readable storage medium is provided, on which computer program instructions are stored, and the computer program instructions implement the above method when executed by a processor.

[0049] The beneficial effects of the present disclosure are as follows: the ERP system inspection and monitoring method provided by the present disclosure can deeply monitor the process processing performance of each application, automatically count the total amount of completed processes of each application within the same time window, and reveal relevant error information, so as to provide data support for evaluating the overall health status of the system. And further refine the mining of abnormal processes to ensure comprehensive monitoring of abnormal processes. In addition, it is also possible to monitor and count to form an alarm list to provide an accurate basis for subsequent troubleshooting. Thus, an integrated inspection report is constructed, and an inspection report with a clear structure and detailed content is automatically generated by intelligently integrating the above-mentioned multi-dimensional data collection and analysis results. This report not only provides a strong basis for operation and maintenance efficiency evaluation, but also can provide an accurate reference for troubleshooting and process optimization, ensuring the comprehensiveness and efficiency of the inspection work. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 The present invention is a flowchart of an ERP system inspection and monitoring method according to an exemplary embodiment.

[0051] Figure 2 The invention is a block diagram of an ERP system inspection and monitoring device according to an exemplary embodiment. DETAILED DESCRIPTION

[0052] The present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0053] Figure 1 1 is a flowchart of an ERP system inspection and monitoring method according to an exemplary embodiment. The method can be executed by a terminal device, wherein the terminal device can be, for example, a server, a desktop computer, a laptop computer, a tablet computer, etc. The embodiment of the present disclosure does not limit the type of the terminal device. Figure 1 As shown, the method includes:

[0054] Step 101, traverse each application in the system that belongs to a preset list.

[0055] As an example of this embodiment, the terminal device can use digital employee RPA (Robotic Process Automation) to achieve seamless connection with distributed components of the ERP system such as APIG, MQS, and LiveFlow. RPA can automatically traverse each application in the preset list according to the preset list to ensure comprehensive coverage of all applications, thereby achieving a full range of automated inspection operations. It should be noted that other applicable automatic inspection and crawling tools can also be used as needed, and this disclosure does not limit this.

[0056] Step 102, process monitoring, for the traversed application, log in to the overview page of the application, collect and count the process data of the application within a preset time period; the process data includes the total amount of workflow messages of the application and the completion status and error amount of each process.

[0057] For example, in step 102, the terminal device can perform process overview data analysis. The terminal device can use RPA to automatically log in to the overview page of each application within a preset period of time, and quickly capture and determine the process data of each application in the preset period of time according to the pre-set settings. The process data includes the total amount of overall workflow messages and the completion status and error amount of each process, so that the overview of each application process can be presented in a timely manner, effectively improving the efficiency and accuracy of data analysis.

[0058] Step 103, alarm monitoring, for the traversed application, if the application is configured with an API, the process tracking data of the API of the application in a preset period is collected and counted by using the log retrieval function, and the process tracking data includes the response status code and its number of the application in the preset period, and the response status code and its number indicating an abnormality or error;

[0059] For example, in step 103, the terminal device can monitor the API access of the application program and conduct an in-depth inspection of each application's API. For applications with APIs, the terminal device can use the log retrieval function to collect and count the response status codes and the corresponding number of response status codes of various APIs of the application within a specified time range, to ensure real-time monitoring of the API service quality and timely detection of anomalies, errors or other problems.

[0060] Step 104, alarm monitoring, for the traversed application, log in to the MQS management page of the application, collect and count the alarm list of the application, the alarm list includes the total number of topics of the application, the number of published topics, the number of subscribed topics, and the consumption progress of each message in the topic. The alarm list also records the application name, topic name and the number of accumulated messages corresponding to the accumulated messages.

[0061] For example, in step 104, the terminal device uses an RPA robot to simulate logging into the MQS management page of each application, automatically captures and records the number of topics, the number of published topics, and the number of subscribed topics for each application, to ensure comprehensive monitoring of the MQS status. In addition, the terminal device can check the subscription and consumption status: for applications that have subscribed to topics, the terminal device uses an RPA robot to further query the consumption progress of the operation and maintenance visualization interface. Once an accumulated message is found (for example, the consumption progress shows that the accumulated amount is greater than 0), the system will record the specific application name, the relevant topic name, and the number of accumulated messages, providing an accurate basis for subsequent troubleshooting.

[0062] Step 105: Generate an inspection report based on the captured data and push it to the associated account. The inspection report includes process data, process tracking data and an alarm list of each application service.

[0063] The ERP system inspection and monitoring method provided by the present disclosure can deeply monitor the process processing performance of each application, automatically count the total amount of completed processes of each application within the same time window, and reveal relevant error information, so as to provide data support for evaluating the overall health status of the system. And further refine the mining of abnormal processes to ensure comprehensive monitoring of abnormal processes. In addition, it is also possible to monitor and count to form an alarm list to provide an accurate basis for subsequent troubleshooting. Thus, an integrated inspection report is constructed, and an inspection report with a clear structure and detailed content is automatically generated by intelligently integrating the above-mentioned multi-dimensional data collection and analysis results. This report not only provides a strong basis for the evaluation of operation and maintenance efficiency, but also provides an accurate reference for troubleshooting and process optimization, ensuring the comprehensiveness and efficiency of the inspection work.

[0064] In a possible implementation, the method further includes: step 106, within a preset time period, determining the failed processes, timed-out processes, and successful process instances that take more than a preset execution time in the application in the acquired process data as abnormal processes, and pushing the abnormal processes to the associated account.

[0065] The present disclosure can further carry out refined mining of abnormal processes: during the process tracking process, it can carefully filter and record failed processes, timed processes, and successful process instances that take more than 5 seconds to execute in all applications within a specified date, ensuring comprehensive monitoring of abnormal processes.

[0066] In a possible implementation, the method further includes: step 107, according to the obtained process data of the application, according to the consistency verification rules, the associated data of the core business process corresponding to the application is checked for consistency; step 108, the associated data of the core business that has not passed the consistency verification is pushed to the associated account. Wherein, step 107 includes any one or more of the following steps: step 1071, consistency verification of the purchase receipt quantity and the purchase amount; step 1072, consistency verification of the purchase receipt currency and the exchange rate on the day of purchase; step 1073, consistency verification of the purchase order invoice matching type and the invoice matching level; step 1074, verification whether the amount of the purchase order is greater than the sum of the received amount and the canceled amount; step 1075, consistency verification of the creation, red offset and adjustment of the financial invoice; step 1076, whether the amount of the moving average cost inventory transaction cost table is empty.

[0067] For example, the present disclosure can also monitor key businesses, and the terminal device can use RPA to monitor the consistency of MetaERP's core business processes. Specific monitoring business content: purchase receipt quantity_amount consistency check, purchase receipt currency_exchange rate consistency check, purchase order invoice matching type and invoice matching level consistency check, purchase order amount must be greater than the received amount plus the canceled amount consistency check, financial invoice creation, red offset, and adjustment consistency monitoring, moving average cost inventory transaction cost table amount empty abnormal monitoring, etc. to ensure that each step meets the expected business logic and timely discovers and solves potential system problems.

[0068] Figure 2 1900 is a block diagram of an ERP system inspection and monitoring device according to an exemplary embodiment. For example, the device 1900 may be provided as a server. Figure 2 , the apparatus 1900 includes a processing component 1922, which further includes one or more processors, and a memory resource represented by a memory 1932 for storing instructions, such as an application, that can be executed by the processing component 1922. The application stored in the memory 1932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1922 is configured to execute instructions to perform the above method.

[0069] The device 1900 may also include a power supply component 1926 configured to perform power management of the device 1900, a wired or wireless network interface 1950 configured to connect the device 1900 to a network, and an input / output (I / O) interface 1958. The device 1900 may operate based on an operating system stored in the memory 1932, such as Windows Server™, MacOS X™, Unix™, Linux™, FreeBSD™, or the like.

[0070] In an exemplary embodiment, a non-volatile computer-readable storage medium is also provided, such as a memory 1932 including computer program instructions, which can be executed by the processing component 1922 of the device 1900 to perform the above method.

[0071] The present disclosure may be a system, a method and / or a computer program product. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for causing a processor to implement various aspects of the present disclosure.

[0072] A computer-readable storage medium may be a tangible device that can hold and store instructions used by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples of computer-readable storage media (a non-exhaustive list) include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as a punch card or a raised structure in a groove on which instructions are stored, and any suitable combination of the foregoing. As used herein, a computer-readable storage medium is not to be interpreted as a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse through a fiber optic cable), or an electrical signal transmitted through a wire.

[0073] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in the computer-readable storage medium in each computing / processing device.

[0074] The computer program instructions for performing the operation of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages, such as Smalltalk, C++, etc., and conventional procedural programming languages, such as "C" language or similar programming languages. Computer-readable program instructions may be executed completely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer, partially on a remote computer, or completely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., using an Internet service provider to connect via the Internet). In some embodiments, an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may be customized by utilizing the state information of the computer-readable program instructions, and the electronic circuit may execute the computer-readable program instructions, thereby realizing various aspects of the present disclosure.

[0075] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0076] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0077] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0078] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of the module, program segment or instruction includes one or more executable instructions for realizing the specified logical function. In some alternative implementations, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or action, or can be implemented with a combination of special hardware and computer instructions.

[0079] The embodiments of the present disclosure have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. An ERP system inspection and monitoring method, characterized in that: The method comprises: Step 101, traverse each application in the system that belongs to the preset list; Step 102, process monitoring, for the traversed application, log in to the overview page of the application, collect and count the process data of the application within a preset time period; the process data includes the total amount of workflow messages of the application and the completion status and error amount of each process; Step 103, process tracking. For the traversed application, if the application is configured with an API, the log retrieval function is used to collect and count the process tracking data of the application's API in a preset period of time. The process tracking data includes the response status code and its number of the application in the preset period of time, and the response status code and its number indicating an abnormality or error; Step 104, alarm monitoring. For the traversed application, log in to the MQS management page of the application, collect and count the alarm list of the application, which includes the total number of topics of the application, the number of published topics, the number of subscribed topics, and the consumption progress of each message in the topic. The alarm list also records the application name, topic name and number of accumulated messages corresponding to the accumulated messages; Step 105: Generate an inspection report based on the captured data and push it to the associated account. The inspection report includes process data, process tracking data and an alarm list of each application service.

2. The method according to claim 1, characterized in that The method further comprises: Step 106, within a preset period of time, the failed processes, timed-out processes, and successful process instances that took more than a preset execution time in the application in the acquired process data are determined as abnormal processes, and the abnormal processes are pushed to the associated account.

3. The method according to claim 1, characterized in that The method further comprises: Step 107, based on the acquired process data of the application and according to consistency verification rules, consistency verification is performed on the associated data of the core business process corresponding to the application; Step 108: Push the associated data of the core business that has not passed the consistency check to the associated account.

4. The method according to claim 5, characterized in that Step 107 includes any one or more of the following steps: Step 1071, consistency check of purchase receipt quantity and purchase amount; Step 1072, consistency check between the purchase receiving currency and the exchange rate on the purchase date; Step 1073, consistency check of purchase order invoice matching type and invoice matching level; Step 1074, verifying whether the amount of the purchase order is greater than the sum of the received amount and the cancelled amount; Step 1075, consistency check of financial invoice creation, redemption and adjustment; Step 1076, whether the moving average cost inventory transaction cost table amount is empty.

5. An ERP system inspection and monitoring device, characterized in that: The device comprises: A traversal module is used to traverse each application in the system that belongs to the preset list; The process monitoring module is used to log in to the overview page of the traversed application, collect and count the process data of the application within a preset time period; the process data includes the total amount of workflow messages of the application and the completion status and error amount of each process; The interface monitoring module is used to collect and count the process tracking data of the API of the application in a preset period of time by using the log retrieval function for the traversed application, when the application is configured with an API. The process tracking data includes the response status code and its number of the application in the preset period of time, and the response status code and its number indicating an abnormality or error; The message monitoring module is used to log in to the MQS management page of the traversed application, collect and count the total number of topics, the number of published topics, and the number of subscribed topics of the application; and query the consumption progress of each message in the topic. If accumulated messages are found, the application name, topic name, and number of accumulated messages corresponding to the accumulated messages are recorded; The report generation module is used to generate an inspection report based on the captured data and push it to the associated account. The inspection report includes process data, process tracking data and an alarm list of each application service.

6. The device according to claim 5, characterized in that The device also includes: The abnormal process monitoring module is used to identify the failed processes, timed-out processes, and successful process instances that take more than a preset time to execute in the acquired process data of the application within a preset time period as abnormal processes, and push the abnormal processes to the associated account.

7. The device according to claim 5, characterized in that The device also includes: A verification module is used to perform consistency verification on the associated data of the core business process corresponding to the application according to the obtained process data of the application and the consistency verification rules; The verification push module is used to push the related data of the core business that has not passed the consistency check to the related accounts.

8. The device according to claim 5, characterized in that In the validation module, any one or more of the following submodules: The first verification submodule is used for consistency verification of the purchase quantity received and the purchase amount; The second verification submodule is used to verify the consistency between the purchase receiving currency and the exchange rate on the day of purchase; The third verification submodule is used for consistency verification of purchase order invoice matching type and invoice matching level; The fourth verification submodule is used to verify whether the amount of the purchase order is greater than the sum of the received amount and the cancelled amount; The fifth verification submodule is used for consistency verification of financial invoice creation, red offset and adjustment. The sixth check submodule is used to check whether the amount in the moving average cost inventory transaction cost table is empty.

9. An ERP system inspection and monitoring device, characterized in that: The device comprises: processor; a memory for storing processor-executable instructions; The processor is configured to execute the method according to any one of claims 1 to 4.

10. A non-volatile computer-readable storage medium having computer program instructions stored thereon, characterized in that: When the computer program instructions are executed by a processor, the method according to any one of claims 1 to 4 is implemented.

Images