Cost monthly settlement check definition method, device, equipment and medium
By defining and storing cost monthly checking strategies, decoupling business logic and code, the problem of high code coupling in traditional cost monthly checking methods is solved, and flexibility and accuracy are improved, and the controllability of the system is enhanced. and reliability.
Patent Information
- Application Number
- CN202411286742.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-13
- Publication Date
- 2025-01-03
AI Technical Summary
The traditional cost monthly check method is highly coupled with the business logic and code, resulting in poor maintainability and scalability of the code, which cannot flexibly respond to the diversified needs of different enterprises, and the code is low reusable, so it is impossible to effectively customize the cost accounting configuration.
By defining a monthly inspection policy, including checking policy names, control methods, conditions and inputs and outputs, parsing and executing policies to generate inspection results, and storing policies for reuse in different scenarios, supporting forced control or warning prompts, Couple business logic and code to improve flexibility and reusability.
It improves the flexibility and accuracy of cost monthly checks, reduces the difficulty of code maintenance and expansion, enhances the controllability and reliability of the system, reduces manual intervention and errors, and improves work efficiency and resource utilization efficiency.
Smart Images
Figure CN119250724A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a method, device, equipment and medium for defining monthly cost check. Background Art
[0002] In today's enterprise management, ERP enterprise management software plays a vital role. However, the cost accounting demand scenarios of different enterprises are significantly different, resulting in different cost accounting configurations.
[0003] Traditional cost monthly check usually relies on hard-coded program to execute check logic before cost accounting. This method has a high degree of coupling between business logic and code, which limits the maintainability and scalability of the code. At the same time, due to the low reusability of the code, it is impossible to flexibly respond to the diverse needs of different enterprises. Summary of the invention
[0004] One or more embodiments of the present specification provide a method, device, equipment and medium for defining monthly cost check, which are used to solve the technical problems raised by the background technology.
[0005] One or more embodiments of this specification adopt the following technical solutions:
[0006] One or more embodiments of this specification provide a method for defining a monthly cost check, the method comprising:
[0007] For different cost monthly check scenarios, the cost monthly check strategy corresponding to each cost monthly check scenario is defined, and the cost monthly check strategy includes the check strategy name, check strategy control mode, check strategy condition, check strategy input and check strategy output; wherein,
[0008] The inspection strategy control method is to perform mandatory control or warning prompts for the corresponding strategy execution results in each cost monthly check scenario;
[0009] The inspection strategy condition is that, when the corresponding strategy in each cost monthly settlement inspection scenario is executed, there is data that passes or there is data that fails;
[0010] The inspection strategy input is the monthly inspection content preset by the system or predefined by the user, the monthly inspection content is parsed, and the monthly inspection content after parsing is executed based on the inspection strategy control mode and the inspection strategy conditions to obtain the inspection result of the strategy execution;
[0011] The inspection strategy output is the inspection result of the execution of the strategy;
[0012] The monthly cost settlement inspection strategies corresponding to each monthly cost settlement inspection scenario are stored so as to perform the monthly cost settlement inspection in the corresponding monthly cost settlement inspection scenario.
[0013] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0014] Improve flexibility: By defining different monthly cost review strategies, you can customize them according to specific business needs and scenarios to better meet the diverse needs of different companies.
[0015] Reduced coupling: Decoupling business logic from code makes code maintenance and expansion easier. Inspection strategies can be modified and adjusted independently without large-scale modifications to the entire system.
[0016] Improve reusability: System preset or user predefined monthly cost check content can be reused in different monthly cost check scenarios, reducing the workload of repeated development and improving development efficiency.
[0017] Enhanced controllability: Checking the policy control method can enforce control or warnings on the policy execution results, which helps to discover and solve problems in a timely manner and improve the accuracy and reliability of monthly cost settlement.
[0018] Improve efficiency: Parsing the monthly check content and executing the corresponding check logic can quickly and accurately complete the cost monthly check, reduce manual intervention and errors, and improve work efficiency.
[0019] Easy to manage and maintain: The monthly cost check strategy is stored for easy management and maintenance. The strategy can be viewed and modified at any time to ensure the continued effectiveness of the monthly cost check.
[0020] Further, if the inspection strategy control mode is the mandatory control, and the corresponding strategy execution result in each cost monthly check scenario is no, the execution of the remaining strategies is terminated;
[0021] If the inspection strategy control mode is the warning prompt, and the corresponding strategy execution result in each cost monthly settlement inspection scenario is no, a warning prompt is issued and the remaining strategies continue to be executed.
[0022] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0023] Improved accuracy: By judging the results of strategy execution, it is possible to more accurately determine whether the remaining strategies need to be continued, thus improving the accuracy of the results.
[0024] Easy to manage: By defining the inspection strategy control method, the cost monthly inspection process can be better managed and controlled, improving management efficiency and accuracy.
[0025] Improve reliability: By promptly terminating the execution of remaining policies or issuing warning prompts, the reliability and stability of the system can be improved, avoiding problems such as system crashes or data loss caused by errors.
[0026] Furthermore, if the inspection policy condition is that the data exists, the policy execution is determined to be yes if there is data when the corresponding policy is executed in each cost monthly check scenario, and no if there is no data when the policy is executed;
[0027] If the inspection policy condition is that the existence of data does not pass, the policy execution judgment is no if there is data when the corresponding policy is executed in each cost monthly inspection scenario, and is yes if there is no data when the policy is executed.
[0028] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0029] Improve accuracy: Data judgment based on different inspection strategy conditions can more accurately determine the results of strategy execution and avoid erroneous judgments caused by unclear data.
[0030] Enhanced flexibility: By setting different inspection policy conditions, you can flexibly configure according to specific business needs and scenarios to meet the diverse needs of different enterprises.
[0031] Optimize resource utilization: Determine the results of policy execution based on whether data exists, which can avoid unnecessary calculations and processing and improve resource utilization efficiency.
[0032] Reduce error rate: Clear data judgment standards help reduce the impact of human factors on strategy execution results, reduce error rates, and improve the accuracy and reliability of monthly cost checks.
[0033] Further, the monthly check content is parsed, and the monthly check content after parsing is executed based on the inspection policy control mode and the inspection policy conditions to obtain the inspection result of the policy execution, including:
[0034] Parsing the monthly check content by using a designated parsing tool to obtain the parsed monthly check content;
[0035] If the check policy control mode is mandatory control, when the policy execution result is no, the execution of the remaining policies is terminated;
[0036] If the check policy control mode is a warning prompt, when the policy execution result is no, a warning prompt is issued and the remaining policies continue to be executed;
[0037] If the check policy condition is that data exists, when the policy is executed, there is data, the policy execution judgment is yes, and when there is no data, the policy execution judgment is no;
[0038] If the check policy condition is that the data exists and is not passed, when the policy is executed, there is data, the policy execution judgment is no, and when there is no data, the policy execution judgment is yes.
[0039] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0040] Improve accuracy: By specifying parsing tools to parse the monthly check content, the accuracy and consistency of the analysis can be ensured, avoiding errors that may be caused by manual analysis.
[0041] Enhanced controllability: According to different inspection strategy control methods, when the strategy execution result is negative, corresponding measures are taken, such as terminating the execution of the remaining strategies or issuing a warning prompt. This can better control the cost monthly check process and ensure the accuracy and completeness of the check.
[0042] Improve flexibility: By setting different inspection policy conditions, you can flexibly configure according to specific business needs and scenarios to meet the diverse needs of different enterprises.
[0043] Optimize resource utilization: Determine the results of policy execution based on whether there is data when the policy is executed, which can avoid unnecessary calculations and processing and improve resource utilization efficiency.
[0044] Furthermore, in the cost monthly settlement inspection scenario that is a monthly settlement inventory scenario, the inspection strategy conditions of the monthly settlement inventory scenario include: whether the inventory period is closed, whether there is an incorrect incoming order from the incoming department, whether there is an incorrect outgoing order from the issuing department, whether there is an incoming voucher that has not been provisionally confirmed, and whether the outgoing cost calculation has been configured; the inspection strategy control method of the monthly settlement inventory scenario is executed based on the inspection strategy conditions of the monthly settlement inventory scenario.
[0045] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0046] Improve the accuracy of inventory management: By checking whether the inventory period is closed, whether the warehousing and issuing departments are correct, whether there are unestimated warehousing vouchers, and whether the outbound cost calculation is configured, you can ensure the accuracy and completeness of inventory data and improve the quality of inventory management.
[0047] Optimize inventory costing: Checking whether outbound costing is configured can ensure the accuracy of costing and avoid inaccurate financial statements caused by costing errors.
[0048] Discover and solve problems in a timely manner: By checking whether there are incorrect incoming orders from the receiving department and incorrect outgoing orders from the issuing department, problems in inventory management can be discovered and solved in a timely manner to avoid the expansion of problems.
[0049] Strengthen internal control: By checking whether the inventory period is closed, whether the warehousing and issuing departments are correct, etc., internal control can be strengthened to prevent fraud and errors in inventory management.
[0050] Provide support for decision-making: Accurate inventory data and cost accounting can provide support for corporate decision-making and help companies formulate reasonable inventory strategies and cost control measures.
[0051] Furthermore, the inspection strategy control method includes:
[0052] When the inventory period is closed, the check whether there is an incorrect stock-in order of the stock-in department and the check whether there is an incorrect stock-out order of the receiving department are executed;
[0053] When the inventory period is not closed, the enforcement ends;
[0054] If there is no incorrect stock-in document of the stock-in department and there is no incorrect stock-out document of the receiving department, execute the check whether there is any stock-in voucher that has not been temporarily estimated and confirmed;
[0055] If there is an incorrect incoming order from the incoming department, and / or there is no incorrect outgoing order from the receiving department, the forced execution ends;
[0056] When there is no incoming voucher that has not been provisionally confirmed, the outgoing cost calculation is performed to see if it has been configured;
[0057] If there are incoming vouchers that have not been provisionally confirmed, the forced execution ends;
[0058] When the outbound cost calculation is configured, or the outbound cost calculation is not configured, the execution ends, and the inspection result of the policy execution corresponding to the monthly inventory scenario is obtained.
[0059] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0060] Improve the accuracy of inventory management: By executing the inspection strategy in a specific order, you can ensure the accuracy and completeness of inventory data. For example, first check whether the inventory period is closed, then check whether the storage and withdrawal departments are correct, and finally check whether there are unestimated storage documents and whether the outbound cost calculation has been configured. This way, possible errors can be gradually eliminated.
[0061] Discover problems promptly: During the implementation of the inspection strategy, if any problems are found, such as incorrect incoming orders from the receiving department or incorrect outgoing orders from the issuing department, or incoming vouchers that have not been tentatively confirmed, the system can issue warnings or error prompts in a timely manner so that relevant personnel can take timely measures to solve the problems.
[0062] Optimize inventory costing: Checking whether outbound costing is configured ensures the accuracy and consistency of costing. If outbound costing is not configured, the system can prompt relevant personnel to configure it in time to avoid costing errors.
[0063] Strengthen internal control: Implementing inspection strategies can strengthen the internal control of the enterprise and ensure the compliance and security of inventory management. By checking whether the inventory period is closed, whether the warehousing and issuing departments are correct, etc., fraud and errors in inventory management can be prevented.
[0064] Furthermore, the monthly check content is the monthly check content stored in SQL.
[0065] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0066] Improve data processing efficiency: SQL is a language specifically used to manage relational databases and has efficient data processing capabilities. Storing the monthly inspection content in SQL can make use of database indexing, query optimization and other features to quickly retrieve and process data and improve inspection efficiency.
[0067] One or more embodiments of this specification provide a cost monthly check definition device, including:
[0068] The definition unit defines the cost monthly settlement inspection strategy corresponding to each cost monthly settlement inspection scenario for different cost monthly settlement inspection scenarios, wherein the cost monthly settlement inspection strategy includes an inspection strategy name, an inspection strategy control method, an inspection strategy condition, an inspection strategy input, and an inspection strategy output; wherein,
[0069] The inspection strategy control method is to perform mandatory control or warning prompts for the corresponding strategy execution results in each cost monthly check scenario;
[0070] The inspection strategy condition is that, when the corresponding strategy in each cost monthly settlement inspection scenario is executed, there is data that passes or there is data that fails;
[0071] The inspection strategy input is the monthly inspection content preset by the system or predefined by the user, the monthly inspection content is parsed, and the monthly inspection content after parsing is executed based on the inspection strategy control mode and the inspection strategy conditions to obtain the inspection result of the strategy execution;
[0072] The inspection strategy output is the inspection result of the execution of the strategy;
[0073] The storage unit stores the monthly cost settlement inspection strategies corresponding to each monthly cost settlement inspection scenario, so as to perform the monthly cost settlement inspection in the corresponding monthly cost settlement inspection scenario.
[0074] One or more embodiments of this specification provide a cost monthly check definition device, including:
[0075] at least one processor; and,
[0076] a memory communicatively connected to the at least one processor; wherein,
[0077] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:
[0078] For different cost monthly check scenarios, the cost monthly check strategy corresponding to each cost monthly check scenario is defined, and the cost monthly check strategy includes the check strategy name, check strategy control mode, check strategy condition, check strategy input and check strategy output; wherein,
[0079] The inspection strategy control method is to perform mandatory control or warning prompts for the corresponding strategy execution results in each cost monthly check scenario;
[0080] The inspection strategy condition is that, when the corresponding strategy in each cost monthly settlement inspection scenario is executed, there is data that passes or there is data that fails;
[0081] The inspection strategy input is the monthly inspection content preset by the system or predefined by the user, the monthly inspection content is parsed, and the monthly inspection content after parsing is executed based on the inspection strategy control mode and the inspection strategy conditions to obtain the inspection result of the strategy execution;
[0082] The inspection strategy output is the inspection result of the execution of the strategy;
[0083] The monthly cost settlement inspection strategies corresponding to each monthly cost settlement inspection scenario are stored so as to perform the monthly cost settlement inspection in the corresponding monthly cost settlement inspection scenario.
[0084] One or more embodiments of this specification provide a non-volatile computer storage medium storing computer executable instructions, which can achieve the following when executed by a computer:
[0085] For different cost monthly check scenarios, the cost monthly check strategy corresponding to each cost monthly check scenario is defined, and the cost monthly check strategy includes the check strategy name, check strategy control mode, check strategy condition, check strategy input and check strategy output; wherein,
[0086] The inspection strategy control method is to perform mandatory control or warning prompts for the corresponding strategy execution results in each cost monthly check scenario;
[0087] The inspection strategy condition is that, when the corresponding strategy in each cost monthly settlement inspection scenario is executed, there is data that passes or there is data that fails;
[0088] The inspection strategy input is the monthly inspection content preset by the system or predefined by the user, the monthly inspection content is parsed, and the monthly inspection content after parsing is executed based on the inspection strategy control mode and the inspection strategy conditions to obtain the inspection result of the strategy execution;
[0089] The inspection strategy output is the inspection result of the execution of the strategy;
[0090] The monthly cost settlement inspection strategies corresponding to each monthly cost settlement inspection scenario are stored so as to perform the monthly cost settlement inspection in the corresponding monthly cost settlement inspection scenario.
[0091] At least one of the above technical solutions adopted in the embodiments of this specification can achieve the following beneficial effects:
[0092] Improve flexibility: By defining different monthly cost review strategies, you can customize them according to specific business needs and scenarios to better meet the diverse needs of different companies.
[0093] Reduced coupling: Decoupling business logic from code makes code maintenance and expansion easier. Inspection strategies can be modified and adjusted independently without large-scale modifications to the entire system.
[0094] Improve reusability: System preset or user predefined monthly cost check content can be reused in different monthly cost check scenarios, reducing the workload of repeated development and improving development efficiency.
[0095] Enhanced controllability: Checking the policy control method can enforce control or warnings on the policy execution results, which helps to discover and solve problems in a timely manner and improve the accuracy and reliability of monthly cost settlement.
[0096] Improve efficiency: Parsing the monthly check content and executing the corresponding check logic can quickly and accurately complete the cost monthly check, reduce manual intervention and errors, and improve work efficiency.
[0097] Easy to manage and maintain: The monthly cost check strategy is stored for easy management and maintenance. The strategy can be viewed and modified at any time to ensure the continued effectiveness of the monthly cost check. BRIEF DESCRIPTION OF THE DRAWINGS
[0098] In order to more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art description. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative labor. In the drawings:
[0099] Figure 1 A flowchart of a cost monthly check definition method provided for one or more embodiments of this specification;
[0100] Figure 2 A schematic diagram of an execution tree provided for one or more embodiments of this specification;
[0101] Figure 3 A system architecture diagram provided for one or more embodiments of this specification;
[0102] Figure 4 A schematic diagram of the structure of a cost monthly check definition device provided in one or more embodiments of this specification;
[0103] Figure 5 A schematic diagram of the structure of a cost monthly check definition device provided for one or more embodiments of this specification. DETAILED DESCRIPTION
[0104] The embodiments of this specification provide a method, device, equipment and medium for defining monthly cost check.
[0105] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.
[0106] Figure 1 A schematic diagram of a cost monthly check definition method provided in one or more embodiments of this specification, the process can be executed by a cost monthly check definition system. Certain input parameters or intermediate results in the process allow manual intervention and adjustment to help improve accuracy.
[0107] The method steps of the embodiment of this specification are as follows:
[0108] S102, for different cost monthly settlement inspection scenarios, define the cost monthly settlement inspection strategy corresponding to each cost monthly settlement inspection scenario, wherein the cost monthly settlement inspection strategy includes an inspection strategy name, an inspection strategy control method, an inspection strategy condition, an inspection strategy input, and an inspection strategy output.
[0109] In the embodiments of this specification, regarding the above S102, the following specific implementation scheme can be adopted:
[0110] Define monthly cost check scenarios: Different monthly cost check scenarios need to be clarified, such as monthly purchase cost check, monthly production cost check, monthly sales cost check, etc.
[0111] Define inspection strategies: For each cost monthly check scenario, define the corresponding inspection strategy, including inspection strategy name, inspection strategy control method, inspection strategy conditions, inspection strategy input, and inspection strategy output.
[0112] S104, storing the monthly cost settlement inspection strategies corresponding to the monthly cost settlement inspection scenarios, so as to perform monthly cost settlement inspections in the corresponding monthly cost settlement inspection scenarios.
[0113] In the embodiments of the present specification, the inspection strategy control method may be to perform mandatory control or warning prompts for the corresponding strategy execution results in each cost monthly settlement inspection scenario.
[0114] Furthermore, if the inspection strategy control mode is the mandatory control, and the corresponding strategy execution result in each cost monthly settlement inspection scenario is no, the execution of the remaining strategies can be terminated; if the inspection strategy control mode is the warning prompt, and the corresponding strategy execution result in each cost monthly settlement inspection scenario is no, a warning prompt can be issued and the execution of the remaining strategies can continue.
[0115] It should be noted that the inspection strategy control method can be implemented through the following specific implementation plans:
[0116] Determine the control method of the inspection strategy: According to the specific situation, determine whether the control method of each inspection strategy is mandatory control or warning prompt.
[0117] Execute inspection strategy: During the cost monthly settlement process, the inspection is performed in the order of the defined inspection strategies. For each inspection strategy, the corresponding processing is carried out according to its control method.
[0118] For mandatory control, if the check policy control mode is mandatory control, when the corresponding policy execution result is no, the execution of the remaining policies is terminated immediately.
[0119] For warning prompts, if the check policy control mode is a warning prompt, when the corresponding policy execution result is no, a warning prompt is issued, but the remaining policies continue to be executed.
[0120] Processing inspection results: According to the output of the inspection strategy, the inspection results are processed accordingly. For example, if the inspection result is passed, the subsequent cost monthly settlement steps can be continued; if the inspection result is not passed, appropriate measures need to be taken according to the specific situation, such as adjustment or recalculation.
[0121] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0122] Improved accuracy: By judging the results of strategy execution, it is possible to more accurately determine whether the remaining strategies need to be continued, thus improving the accuracy of the results.
[0123] Easy to manage: By defining the inspection strategy control method, the cost monthly inspection process can be better managed and controlled, improving management efficiency and accuracy.
[0124] Improve reliability: By promptly terminating the execution of remaining policies or issuing warning prompts, the reliability and stability of the system can be improved, avoiding problems such as system crashes or data loss caused by errors.
[0125] In the embodiment of the present specification, the inspection policy condition is that when the corresponding policy in each cost monthly settlement inspection scenario is executed, there is data that passes or there is data that fails.
[0126] Furthermore, if the inspection policy condition is that the data exists, the policy execution is determined to be yes if there is data when the corresponding policy is executed in each cost monthly check scenario, and no if there is no data when the policy is executed;
[0127] If the inspection policy condition is that the existence of data does not pass, the policy execution judgment is no if there is data when the corresponding policy is executed in each cost monthly inspection scenario, and is yes if there is no data when the policy is executed.
[0128] It should be noted that the inspection policy conditions can be implemented through the following specific implementation plans:
[0129] Data collection: Before performing the monthly cost review, collect data related to each monthly cost review scenario. This data can come from the company's financial system, business system, or other data sources.
[0130] Execute inspection strategy: Inspect each cost monthly check scenario according to the defined inspection strategy sequence.
[0131] For the inspection policy conditions where there is data passing:
[0132] If relevant data exists when the policy is executed, the policy execution result is determined to be "yes".
[0133] If no relevant data exists when the policy is executed, the policy execution result is determined to be "no".
[0134] For check policy conditions where data does not pass:
[0135] If relevant data exists when the policy is executed, the policy execution result is determined to be "no".
[0136] If no relevant data exists when the policy is executed, the policy execution result is determined to be "yes".
[0137] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0138] Improve accuracy: Data judgment based on different inspection strategy conditions can more accurately determine the results of strategy execution and avoid erroneous judgments caused by unclear data.
[0139] Enhanced flexibility: By setting different inspection policy conditions, you can flexibly configure according to specific business needs and scenarios to meet the diverse needs of different enterprises.
[0140] Optimize resource utilization: Determine the results of policy execution based on whether data exists, which can avoid unnecessary calculations and processing and improve resource utilization efficiency.
[0141] Reduce error rate: Clear data judgment standards help reduce the impact of human factors on strategy execution results, reduce error rates, and improve the accuracy and reliability of monthly cost checks.
[0142] In an embodiment of the present specification, the inspection strategy input is system preset or user predefined monthly inspection content, the monthly inspection content is parsed, and the parsed monthly inspection content is executed based on the inspection strategy control method and the inspection strategy conditions to obtain the inspection result of the policy execution.
[0143] Further, the monthly check content is parsed, and the monthly check content after parsing is executed based on the inspection policy control mode and the inspection policy conditions to obtain the inspection result of the policy execution, including:
[0144] Parsing the monthly check content by using a designated parsing tool to obtain the parsed monthly check content;
[0145] If the check policy control mode is mandatory control, when the policy execution result is no, the execution of the remaining policies is terminated;
[0146] If the check policy control mode is a warning prompt, when the policy execution result is no, a warning prompt is issued and the remaining policies continue to be executed;
[0147] If the check policy condition is that data exists, when the policy is executed, there is data, the policy execution judgment is yes, and when there is no data, the policy execution judgment is no;
[0148] If the check policy condition is that the data exists and is not passed, when the policy is executed, there is data, the policy execution judgment is no, and when there is no data, the policy execution judgment is yes.
[0149] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0150] Improve accuracy: By specifying parsing tools to parse the monthly check content, the accuracy and consistency of the analysis can be ensured, avoiding errors that may be caused by manual analysis.
[0151] Enhanced controllability: According to different inspection strategy control methods, when the strategy execution result is negative, corresponding measures are taken, such as terminating the execution of the remaining strategies or issuing a warning prompt. This can better control the cost monthly check process and ensure the accuracy and completeness of the check.
[0152] Improve flexibility: By setting different inspection policy conditions, you can flexibly configure according to specific business needs and scenarios to meet the diverse needs of different enterprises.
[0153] Optimize resource utilization: Determine the results of policy execution based on whether there is data when the policy is executed, which can avoid unnecessary calculations and processing and improve resource utilization efficiency.
[0154] In the embodiment of the present specification, the inspection strategy output is the inspection result of the execution of the strategy.
[0155] Furthermore, in the cost monthly settlement inspection scenario that is a monthly settlement inventory scenario, the inspection strategy conditions of the monthly settlement inventory scenario include: whether the inventory period is closed, whether there is an incorrect incoming order from the incoming department, whether there is an incorrect outgoing order from the issuing department, whether there is an incoming voucher that has not been provisionally confirmed, and whether the outgoing cost calculation has been configured; the inspection strategy control method of the monthly settlement inventory scenario is executed based on the inspection strategy conditions of the monthly settlement inventory scenario.
[0156] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0157] Improve the accuracy of inventory management: By checking whether the inventory period is closed, whether the warehousing and issuing departments are correct, whether there are unestimated warehousing vouchers, and whether the outbound cost calculation is configured, you can ensure the accuracy and completeness of inventory data and improve the quality of inventory management.
[0158] Optimize inventory costing: Checking whether outbound costing is configured can ensure the accuracy of costing and avoid inaccurate financial statements caused by costing errors.
[0159] Discover and solve problems in a timely manner: By checking whether there are incorrect incoming orders from the receiving department and incorrect outgoing orders from the issuing department, problems in inventory management can be discovered and solved in a timely manner to avoid the expansion of problems.
[0160] Strengthen internal control: By checking whether the inventory period is closed, whether the warehousing and issuing departments are correct, etc., internal control can be strengthened to prevent fraud and errors in inventory management.
[0161] Provide support for decision-making: Accurate inventory data and cost accounting can provide support for corporate decision-making and help companies formulate reasonable inventory strategies and cost control measures.
[0162] Furthermore, the inspection strategy control method includes:
[0163] When the inventory period is closed, the check whether there is an incorrect stock-in order of the stock-in department and the check whether there is an incorrect stock-out order of the receiving department are executed;
[0164] When the inventory period is not closed, the enforcement ends;
[0165] If there is no incorrect stock-in document of the stock-in department and there is no incorrect stock-out document of the receiving department, execute the check whether there is any stock-in voucher that has not been temporarily estimated and confirmed;
[0166] If there is an incorrect incoming order from the incoming department, and / or there is no incorrect outgoing order from the receiving department, the forced execution ends;
[0167] When there is no incoming voucher that has not been provisionally confirmed, the outgoing cost calculation is performed to see if it has been configured;
[0168] If there are incoming vouchers that have not been provisionally confirmed, the forced execution ends;
[0169] When the outbound cost calculation is configured, or the outbound cost calculation is not configured, the execution ends, and the inspection result of the policy execution corresponding to the monthly inventory scenario is obtained.
[0170] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0171] Improve the accuracy of inventory management: By executing the inspection strategy in a specific order, you can ensure the accuracy and completeness of inventory data. For example, first check whether the inventory period is closed, then check whether the storage and withdrawal departments are correct, and finally check whether there are unestimated storage documents and whether the outbound cost calculation has been configured. This way, possible errors can be gradually eliminated.
[0172] Discover problems promptly: During the implementation of the inspection strategy, if any problems are found, such as incorrect incoming orders from the receiving department or incorrect outgoing orders from the issuing department, or incoming vouchers that have not been tentatively confirmed, the system can issue warnings or error prompts in a timely manner so that relevant personnel can take timely measures to solve the problems.
[0173] Optimize inventory costing: Checking whether outbound costing is configured ensures the accuracy and consistency of costing. If outbound costing is not configured, the system can prompt relevant personnel to configure it in time to avoid costing errors.
[0174] Strengthen internal control: Implementing inspection strategies can strengthen the internal control of the enterprise and ensure the compliance and security of inventory management. By checking whether the inventory period is closed, whether the warehousing and issuing departments are correct, etc., fraud and errors in inventory management can be prevented.
[0175] Furthermore, the monthly check content is the monthly check content stored in SQL.
[0176] It should be noted that the embodiments of this specification have the following beneficial effects through the above contents:
[0177] Improve data processing efficiency: SQL is a language specifically used to manage relational databases and has efficient data processing capabilities. Storing the monthly inspection content in SQL can make use of database indexing, query optimization and other features to quickly retrieve and process data and improve inspection efficiency.
[0178] It should be noted that in ERP enterprise management software, different enterprises often have different cost accounting demand scenarios, and the cost accounting configurations are also different. In traditional cost accounting systems, the monthly cost check is to identify and refine the inspection content of known business scenarios, and execute the inspection logic before cost accounting through hard coding of the program. The business logic and code are highly coupled, the code reusability is low, and the inspection conditions cannot be flexibly defined. Different enterprises often require customized development, which increases the development and maintenance costs of the system.
[0179] The embodiments of this specification solve the problems of poor flexibility, high code coupling, and low reusability of existing cost monthly check. By introducing a rule engine, different check contents and check logic are defined as rules, reducing the cost and risk of hard-coded business rules, and flexibly configuring monthly check rules, reducing system development and maintenance costs, and effectively improving the efficiency and quality of enterprise cost management. It should be noted that the rules of the embodiments of this specification are the same as the above-mentioned strategies.
[0180] Biggest advantages:
[0181] The greatest advantages of the embodiments of this specification are mainly the following aspects:
[0182] 1. Business inspection rules and application code are decoupled, which enhances code maintainability and reusability;
[0183] 2. The inspection rules can be modified without changing the source code. The rules take effect immediately without redeployment, which reduces the development and maintenance costs of the system;
[0184] 3. Easy-to-write rules allow business and implementation personnel to easily customize the inspection rules to meet the enterprise cost accounting scenarios;
[0185] 4. Support the arrangement of different inspection rules, support different inspection rule control methods, and support customized inspection result output.
[0186] The embodiments of this specification relate to the field of ERP enterprise management software. During the cost management process, it is necessary to obtain the data such as material and labor costs required for cost accounting through various business modules, and calculate the cost of the product through a series of processes such as collection, allocation, and calculation. Since the cost monthly settlement data may be abnormal due to business personnel input errors, parameter configuration errors, operational problems, etc., users need to repeatedly check the data and configuration to find out the cause of the problem, which not only affects the efficiency of the cost monthly settlement, but also affects the accuracy of the final cost accounting. Therefore, it is necessary to check the relevant data before and after the cost monthly settlement to ensure the accuracy of the cost monthly settlement.
[0187] The embodiments of this specification propose a cost monthly settlement checking method based on a rule engine. By flexibly defining the checking rules and rule outputs, the rule code is extracted from the business, the maintainability and reusability of the code are enhanced, the development and maintenance costs in the cost monthly settlement scenario are reduced, and the cost monthly settlement efficiency is improved.
[0188] The specific technical solutions are as follows:
[0189] 1. Define the cost monthly check rules
[0190] a) Define different cost monthly check rules for different check business scenarios;
[0191] b) Rules include rule name, rule control method, rule condition, rule input and rule output;
[0192] c) The rule control mode is mandatory control or warning prompt. In mandatory control, if the rule execution result is false, the execution of the remaining rules will be terminated. In warning prompt, the rule execution result does not affect the execution of the remaining rules.
[0193] d) The rule condition is that there is data passing or data not passing. When there is data passing, the rule execution judgment is true if there is data when the rule is executed, otherwise it is false; when there is data not passing, the rule execution judgment is false if there is data when the rule is executed, otherwise it is true;
[0194] e) The rule input is the monthly check content stored in SQL format, which is preset by the system or defined by the user. When the rule is executed, the SQL is parsed and executed, the query results are analyzed, and the rule conditions are judged;
[0195] f) The rule output is the inspection result of the rule execution. If the data does not pass, the data that does not pass the inspection is output. The user can view and confirm the specific data content. If the data passes, the output is empty.
[0196] 2. The defined rules are entered into the rule base for rule management
[0197] The rule base is used to store and manage rules. The data is stored in the database and the rules can be expanded and modified as needed.
[0198] 3. Arrange the order of rule execution by configuring rules
[0199] Arrange the existing rules to determine the preconditions and post-actions of rule execution. The preconditions are generally the execution results of a certain rule, and the post-actions are generally the execution of a certain rule or the end of execution. Through rule arrangement, determine the rule execution process during the cost monthly check.
[0200] Taking the inventory and stock checking rules as an example, define the following rules:
[0201] (1) Whether the inventory period is closed, if closed, returns true, otherwise returns false;
[0202] (2) Whether there is an incorrect incoming order from the incoming department. If there is no data, it returns true; otherwise, it returns false.
[0203] (3) Whether there is an incorrect delivery order from the receiving department. If there is no data, true is returned; otherwise, false is returned.
[0204] (4) Whether there is an unestimated storage voucher. If there is no data, it returns true; otherwise, it returns false.
[0205] (5) Whether the outbound cost calculation has been configured. If configured, it returns true; otherwise, it returns false.
[0206] The rules can be organized as follows:
[0207] When the result of rule (1) is true, rules (2) and (3) are executed, otherwise the execution ends;
[0208] When the results of rules (2) and (3) are both true, rule (4) is executed, otherwise the execution ends;
[0209] When the result of rule (4) is true, rule (5) is executed, otherwise the execution ends;
[0210] When the result of rule (5) is true or false, the execution ends. Figure 2 shown.
[0211] 4. Perform monthly cost check
[0212] When the user triggers the cost monthly check operation, the rule engine starts and loads the rule base data, parses, compiles and executes the applied cost monthly check rules, obtains data as fact input according to the rule definition, and determines and outputs the rule execution results according to the rule conditions.
[0213] Figure 3 This is the system architecture diagram. When the user performs the monthly cost check, the rule engine is called. The rule engine includes rule dependency analysis, rule parsing and rule execution. The rule engine obtains rules from the database and stores the output results of the rule engine in the database. In addition, the user configures the rules in advance to obtain the monthly cost check rules. The monthly cost check rules include rule name, control method, rule condition, rule input and rule output. The database includes rule base, business data and result data.
[0214] Figure 4 A schematic diagram of the structure of a cost monthly check definition device provided for one or more embodiments of this specification includes: a definition unit 402 and a storage unit 404.
[0215] The definition unit 402 defines the cost monthly settlement inspection strategy corresponding to each cost monthly settlement inspection scenario for different cost monthly settlement inspection scenarios, wherein the cost monthly settlement inspection strategy includes an inspection strategy name, an inspection strategy control method, an inspection strategy condition, an inspection strategy input, and an inspection strategy output; wherein,
[0216] The inspection strategy control method is to perform mandatory control or warning prompts for the corresponding strategy execution results in each cost monthly check scenario;
[0217] The inspection strategy condition is that, when the corresponding strategy in each cost monthly settlement inspection scenario is executed, there is data that passes or there is data that fails;
[0218] The inspection strategy input is the monthly inspection content preset by the system or predefined by the user, the monthly inspection content is parsed, and the monthly inspection content after parsing is executed based on the inspection strategy control mode and the inspection strategy conditions to obtain the inspection result of the strategy execution;
[0219] The inspection strategy output is the inspection result of the execution of the strategy;
[0220] The storage unit 404 stores the monthly cost settlement inspection strategies corresponding to each monthly cost settlement inspection scenario, so as to perform monthly cost settlement inspection in the corresponding monthly cost settlement inspection scenario.
[0221] Figure 5 A schematic diagram of a cost monthly check definition device provided for one or more embodiments of this specification includes:
[0222] at least one processor; and,
[0223] a memory communicatively connected to the at least one processor; wherein,
[0224] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:
[0225] For different cost monthly check scenarios, the cost monthly check strategy corresponding to each cost monthly check scenario is defined, and the cost monthly check strategy includes the check strategy name, check strategy control mode, check strategy condition, check strategy input and check strategy output; wherein,
[0226] The inspection strategy control method is to perform mandatory control or warning prompts for the corresponding strategy execution results in each cost monthly check scenario;
[0227] The inspection strategy condition is that, when the corresponding strategy in each cost monthly settlement inspection scenario is executed, there is data that passes or there is data that fails;
[0228] The inspection strategy input is the monthly inspection content preset by the system or predefined by the user, the monthly inspection content is parsed, and the monthly inspection content after parsing is executed based on the inspection strategy control mode and the inspection strategy conditions to obtain the inspection result of the strategy execution;
[0229] The inspection strategy output is the inspection result of the execution of the strategy;
[0230] The monthly cost settlement inspection strategies corresponding to each monthly cost settlement inspection scenario are stored so as to perform the monthly cost settlement inspection in the corresponding monthly cost settlement inspection scenario.
[0231] One or more embodiments of this specification provide a non-volatile computer storage medium storing computer executable instructions, which can achieve the following when executed by a computer:
[0232] For different cost monthly check scenarios, the cost monthly check strategy corresponding to each cost monthly check scenario is defined, and the cost monthly check strategy includes the check strategy name, check strategy control mode, check strategy condition, check strategy input and check strategy output; wherein,
[0233] The inspection strategy control method is to perform mandatory control or warning prompts for the corresponding strategy execution results in each cost monthly check scenario;
[0234] The inspection strategy condition is that, when the corresponding strategy in each cost monthly settlement inspection scenario is executed, there is data that passes or there is data that fails;
[0235] The inspection strategy input is the monthly inspection content preset by the system or predefined by the user, the monthly inspection content is parsed, and the monthly inspection content after parsing is executed based on the inspection strategy control mode and the inspection strategy conditions to obtain the inspection result of the strategy execution;
[0236] The inspection strategy output is the inspection result of the execution of the strategy;
[0237] The monthly cost settlement inspection strategies corresponding to each monthly cost settlement inspection scenario are stored so as to perform the monthly cost settlement inspection in the corresponding monthly cost settlement inspection scenario.
[0238] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
Claims
1. A method for defining monthly cost check, characterized in that: include: For different cost monthly check scenarios, the cost monthly check strategy corresponding to each cost monthly check scenario is defined, and the cost monthly check strategy includes the check strategy name, check strategy control mode, check strategy condition, check strategy input and check strategy output; wherein, The inspection strategy control method is to perform mandatory control or warning prompts for the corresponding strategy execution results in each cost monthly check scenario; The inspection strategy condition is that, when the corresponding strategy in each cost monthly settlement inspection scenario is executed, there is data that passes or there is data that fails; The inspection strategy input is the monthly inspection content preset by the system or predefined by the user, the monthly inspection content is parsed, and the monthly inspection content after parsing is executed based on the inspection strategy control mode and the inspection strategy conditions to obtain the inspection result of the strategy execution; The inspection strategy output is the inspection result of the execution of the strategy; The monthly cost settlement inspection strategies corresponding to each monthly cost settlement inspection scenario are stored so as to perform the monthly cost settlement inspection in the corresponding monthly cost settlement inspection scenario.
2. The method according to claim 1, characterized in that If the inspection strategy control mode is the mandatory control, the corresponding strategy execution result in each cost monthly check scenario is no, then the execution of the remaining strategies is terminated; If the inspection strategy control mode is the warning prompt, and the corresponding strategy execution result in each cost monthly settlement inspection scenario is no, a warning prompt is issued and the remaining strategies continue to be executed.
3. The method according to claim 1, characterized in that If the inspection policy condition is that the data exists, the policy execution is determined to be yes if there is data when the corresponding policy is executed in each cost monthly check scenario, and no if there is no data when the policy is executed; If the inspection policy condition is that the existence of data does not pass, the policy execution judgment is no if there is data when the corresponding policy is executed in each cost monthly inspection scenario, and is yes if there is no data when the policy is executed.
4. The method according to claim 1, characterized in that: The parsing of the monthly check content and executing the parsed monthly check content based on the check policy control mode and the check policy conditions to obtain the check result of the policy execution include: Parsing the monthly check content by using a designated parsing tool to obtain the parsed monthly check content; If the check policy control mode is mandatory control, when the policy execution result is no, the execution of the remaining policies is terminated; If the check policy control mode is a warning prompt, when the policy execution result is no, a warning prompt is issued and the remaining policies continue to be executed; If the check policy condition is that data exists, when the policy is executed, there is data, the policy execution judgment is yes, and when there is no data, the policy execution judgment is no; If the check policy condition is that the data exists and is not passed, when the policy is executed, there is data, the policy execution judgment is no, and when there is no data, the policy execution judgment is yes.
5. The method according to claim 1, characterized in that In the cost monthly settlement inspection scenario, which is the monthly settlement inventory scenario, the inspection strategy conditions of the monthly settlement inventory scenario include: whether the inventory period is closed, whether there is an incorrect incoming order from the incoming department, whether there is an incorrect outgoing order from the issuing department, whether there is an incoming voucher that has not been provisionally confirmed, and whether the outgoing cost calculation has been configured; the inspection strategy control method of the monthly settlement inventory scenario is executed based on the inspection strategy conditions of the monthly settlement inventory scenario.
6. The method according to claim 5, characterized in that The inspection strategy control method includes: When the inventory period is closed, the check whether there is an incorrect stock-in order of the stock-in department and the check whether there is an incorrect stock-out order of the receiving department are executed; When the inventory period is not closed, the enforcement ends; If there is no incorrect stock-in document of the stock-in department and there is no incorrect stock-out document of the receiving department, execute the check whether there is any stock-in voucher that has not been temporarily estimated and confirmed; If there is an incorrect incoming order from the incoming department, and / or there is no incorrect outgoing order from the receiving department, the forced execution ends; When there is no incoming voucher that has not been provisionally confirmed, the outgoing cost calculation is performed to see if it has been configured; If there are incoming vouchers that have not been provisionally confirmed, the forced execution ends; When the outbound cost calculation is configured, or the outbound cost calculation is not configured, the execution ends, and the inspection result of the policy execution corresponding to the monthly inventory scenario is obtained.
7. The method according to claim 1, characterized in that The monthly check content is the monthly check content stored in SQL.
8. A cost monthly check definition device, characterized in that: include: The definition unit defines the cost monthly settlement inspection strategy corresponding to each cost monthly settlement inspection scenario for different cost monthly settlement inspection scenarios, wherein the cost monthly settlement inspection strategy includes an inspection strategy name, an inspection strategy control method, an inspection strategy condition, an inspection strategy input, and an inspection strategy output; wherein, The inspection strategy control method is to perform mandatory control or warning prompts for the corresponding strategy execution results in each cost monthly check scenario; The inspection strategy condition is that, when the corresponding strategy in each cost monthly settlement inspection scenario is executed, there is data that passes or there is data that fails; The inspection strategy input is the monthly inspection content preset by the system or predefined by the user, the monthly inspection content is parsed, and the monthly inspection content after parsing is executed based on the inspection strategy control mode and the inspection strategy conditions to obtain the inspection result of the strategy execution; The inspection strategy output is the inspection result of the execution of the strategy; The storage unit stores the monthly cost settlement inspection strategies corresponding to each monthly cost settlement inspection scenario, so as to perform the monthly cost settlement inspection in the corresponding monthly cost settlement inspection scenario.
9. A cost monthly check definition device, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: For different cost monthly check scenarios, the cost monthly check strategy corresponding to each cost monthly check scenario is defined, and the cost monthly check strategy includes the check strategy name, check strategy control mode, check strategy condition, check strategy input and check strategy output; wherein, The inspection strategy control method is to perform mandatory control or warning prompts for the corresponding strategy execution results in each cost monthly check scenario; The inspection strategy condition is that, when the corresponding strategy in each cost monthly settlement inspection scenario is executed, there is data that passes or there is data that fails; The inspection strategy input is the monthly inspection content preset by the system or predefined by the user, the monthly inspection content is parsed, and the monthly inspection content after parsing is executed based on the inspection strategy control mode and the inspection strategy conditions to obtain the inspection result of the strategy execution; The inspection strategy output is the inspection result of the execution of the strategy; The monthly cost settlement inspection strategies corresponding to each monthly cost settlement inspection scenario are stored so as to perform the monthly cost settlement inspection in the corresponding monthly cost settlement inspection scenario.
10. A non-volatile computer storage medium, characterized in that: Computer executable instructions are stored, and when the computer executable instructions are executed by a computer, the following can be achieved: For different cost monthly check scenarios, the cost monthly check strategy corresponding to each cost monthly check scenario is defined, and the cost monthly check strategy includes the check strategy name, check strategy control mode, check strategy condition, check strategy input and check strategy output; wherein, The inspection strategy control method is to perform mandatory control or warning prompts for the corresponding strategy execution results in each cost monthly check scenario; The inspection strategy condition is that, when the corresponding strategy in each cost monthly settlement inspection scenario is executed, there is data that passes or there is data that fails; The inspection strategy input is the monthly inspection content preset by the system or predefined by the user, the monthly inspection content is parsed, and the monthly inspection content after parsing is executed based on the inspection strategy control mode and the inspection strategy conditions to obtain the inspection result of the strategy execution; The inspection strategy output is the inspection result of the execution of the strategy; The monthly cost settlement inspection strategies corresponding to each monthly cost settlement inspection scenario are stored so as to perform the monthly cost settlement inspection in the corresponding monthly cost settlement inspection scenario.