Method for solving functional operation conflict inside management software by configuring conflict matrix

Abstract

The invention provides a method for solving functional operation conflict inside management software by configuring a conflict matrix. The method can avoid the conditions such as data inconformity, different calculation results and the like caused by mutual interference between functions or operations due to the conflict by assisting an operator in effectively solving the conflict produced between different functions or different operations with the same function in the management software due to service reasons through the conflict matrix so that the management software has strict services and accurate data.

Description

technical field [0001] The invention relates to the technical field of computer application, in particular to a method for solving internal function operation conflicts of management software by configuring a conflict matrix. Background technique [0002] In management software, there are often certain constraint conflicts between different functions, or between different operations of the same function, such as financial monthly closing and voucher preparation. At this time, another user logs in to the system and makes a voucher for the month-end month; another example is that an operator is modifying a reimbursement form with a document number of 001, and at this time another operator logs in to the system and approves this document with a number of 001 reimbursement form, the possible result is that the reimbursement amount seen by the approver is different from the revised one, the reimbursement that could not have been approved or the document that could have been reimb...

AI Technical Summary

Problems solved by technology

[0002] In management software, there are often certain constraint conflicts between different functions, or between different operations of the same function, such as financial monthly closing and voucher preparation. If the system is performing monthly closing for a certain month and At this time, another user logs in to the system and makes a voucher for the month-end month; another example is that an operator is modifying a reimbursement form with a document number of 001, and at this time another operator logs in to the system and approves this number. 001 reimbursement form, the possible result is that the reimbursement amount seen by the approver is different from the revised one, the reimbursement that could not have been approved or the document that could have been reimbursed was rejected, etc. These will lead to the final data calculation of the system The results are different or the business logic control is not strict, resulting in business errors

In order to control these, many softwares rely on the data lock mechanism of the database itself for control, but there are two serious disadvantages in this way. One is that sometimes an operation may need to lock multiple tables and data, not only locking It is troublesome and some data tables are multi-purpose, which will restrict other business documents from being able to perform some operations; the second is that when a conflict occurs, the prompt is not friendly, and it may be the data lock information directly from the database, such as the second reimbursement form approval above. For example, through the processing of this technical solution, the second operator can prompt a message similar to this when entering the approval process: "XX is currently modifying the current document. Now you can only view but not approve this document", so as to avoid At the same time as the error, the prompt is friendly and easy to understand