A method and apparatus for generating rules for a business system

Abstract

This application provides a rule generation method and apparatus for a business system, relating to the field of data analysis technology. The method includes: obtaining configuration parameters set by a user for an inspection object in transaction information through a database table; the inspection object includes the transaction type and / or process stage of the transaction information, the process stage including any one of a generation stage, a storage stage, and an analysis stage; and generating inspection rules corresponding to the transaction information based on the configuration parameters. Thus, inspection rules for new transaction types can be generated without modifying the code, effectively meeting the inspection needs corresponding to different transaction types and significantly reducing the development cost of the business system.

Description

Technical Field

[0001] This application relates to the field of data analysis technology, and in particular to a method and apparatus for generating rules for a business system. Background Technology

[0002] Banks' trading operations span both domestic and international markets, and encompass a wide variety of transactions. With the development of financial technology and the backdrop of global operations, banks have built intelligent operating systems specifically for their trading activities.

[0003] Before transaction information enters the intelligent operation system and is processed by the back-end business system for clearing and accounting, it needs to undergo compliance checks to ensure data accuracy during subsequent processing. However, the types of transaction information are diverse, requiring the development of separate program code for different types of transaction information to achieve compliance checks. This results in high development costs for the intelligent operation system, and its maintenance is beyond the capabilities of non-professionals.

[0004] Therefore, how to reduce the development cost of intelligent operation systems is an urgent problem to be solved. Summary of the Invention

[0005] This application provides a rule generation method and apparatus for a business system, which reduces the development cost of intelligent operation systems and effectively improves the efficiency of formulating data inspection rules for new transaction information.

[0006] In a first aspect, embodiments of this application provide a rule generation method for a business system. The method includes: obtaining configuration parameters set by a user for an inspection object in transaction information through a database table, wherein the inspection object includes the transaction type and / or process stage of the transaction information, and the process stage includes any one of a generation stage, a storage stage, and an analysis stage; and generating inspection rules corresponding to the transaction information based on the configuration parameters.

[0007] In this embodiment, configuration parameters for the transaction type and / or process stage of the transaction information can be obtained from a database table, thereby generating inspection rules corresponding to the transaction information. In this way, the inspection requirements for different transaction types can be met without modifying the code, effectively reducing system development costs.

[0008] In one possible implementation, before obtaining the configuration parameters set by the user for the inspection object in the transaction information through the database table, the method further includes: obtaining the transaction information; parsing the data structure of the transaction information to determine the data type of each piece of data in the transaction information; and determining the inspection object based on the data type of each piece of data.

[0009] In one possible implementation, before obtaining the configuration parameters set by the user for the inspection object in the transaction information through the database table, the method further includes: obtaining the transaction information; and filtering the inspection object from the transaction information based on user input.

[0010] In one possible implementation, the configuration parameters include multiple inspection items. After obtaining the configuration parameters set by the user for the inspection objects in the transaction information through the database table, the method further includes: verifying the multiple inspection items; when each of the multiple inspection items passes the verification, generating inspection rules corresponding to the transaction information based on the configuration parameters; or, when there are inspection items that fail the verification, displaying a prompt message to prompt the user to reset the configuration parameters.

[0011] In one possible implementation, the inspection items include at least one of the following: transaction object inspection, transaction calendar inspection, transaction account type inspection, transaction product information inspection, transaction review method inspection, settlement and accounting mark inspection, accounting inspection, clearing method inspection, transaction interest inspection, planned cash flow inspection, related remittance route inspection, transaction task inspection, and clearing record inspection.

[0012] In one possible implementation, the inspection items include field information, and the verification of the plurality of inspection items includes: determining that the field information has a preset data instance, and then determining that the field information verification is successful.

[0013] In one possible implementation, the inspection items include business inspection types, and the verification of the plurality of inspection items includes: determining that the function corresponding to the business inspection type is executable, and then determining that the business inspection type verification is successful.

[0014] Secondly, embodiments of this application also provide an apparatus for configuring rules in a business system, the apparatus including a module for implementing the method described in the first aspect and any optional implementation of the first aspect.

[0015] For example, the device may include:

[0016] The acquisition module is used to acquire configuration parameters set by the user for the inspection object in the transaction information through a database table. The inspection object includes the transaction type and / or process stage of the transaction information. The process stage includes any one of the generation stage, storage stage and analysis stage.

[0017] The processing module is used to generate inspection rules corresponding to the transaction information based on the configuration parameters.

[0018] In one possible implementation, before obtaining the configuration parameters set by the user for the inspection object in the transaction information through the database table, the acquisition module is further configured to: acquire the transaction information; the processing module is further configured to: parse the data structure of the transaction information to determine the data type of each piece of data in the transaction information; and determine the inspection object based on the data type of each piece of data.

[0019] In one possible implementation, before obtaining the configuration parameters set by the user for the inspection object in the transaction information through the database table, the acquisition module is further configured to: acquire the transaction information; the processing module is further configured to: filter out the inspection object from the transaction information according to the user input.

[0020] In one possible implementation, the above-mentioned device includes a display module. The configuration parameters include multiple inspection items. After obtaining the configuration parameters set by the user for the inspection objects in the transaction information through the database table, the processing module is further configured to: verify the multiple inspection items; when each of the multiple inspection items passes the verification, generate inspection rules corresponding to the transaction information based on the configuration parameters; or, when there are inspection items that fail the verification, control the display module to display a prompt message, the prompt message being used to prompt the user to reset the configuration parameters.

[0021] In one possible implementation, the inspection items include at least one of the following: transaction object inspection, transaction calendar inspection, transaction account type inspection, transaction product information inspection, transaction review method inspection, settlement and accounting mark inspection, accounting inspection, clearing method inspection, transaction interest inspection, planned cash flow inspection, related remittance route inspection, transaction task inspection, and clearing record inspection.

[0022] In one possible implementation, the inspection items include field information, and the processing module is used to verify the plurality of inspection items, specifically: if the field information is found to have a preset data instance, then the field information is determined to have been successfully verified.

[0023] In one possible implementation, the inspection items include business inspection types, and the processing module is used to verify the plurality of inspection items, specifically: if it is determined that the function corresponding to the business inspection type is executable, then the business inspection type is determined to be successfully verified.

[0024] Thirdly, another embodiment of this application also provides an electronic device, including at least one processor; and 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 perform the method of the first aspect provided in the embodiments of this application.

[0025] Fourthly, another embodiment of this application also provides a computer storage medium storing a computer program for causing a computer to execute the method provided in the first aspect of this application.

[0026] Fifth aspect. Another embodiment of this application also provides a computer program, the computer program including computer instructions for causing a computer to perform the method of the first aspect provided in the embodiments of this application. Attached Figure Description

[0027] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 This is a flowchart illustrating a rule generation method for a business system according to an embodiment of this application;

[0029] Figure 2 A schematic diagram of a data table shown in an embodiment of this application;

[0030] Figure 3 This is a schematic diagram of the structure of a rule generation device for a business system, as shown in an embodiment of this application.

[0031] Figure 4 This is a schematic diagram of an electronic device shown in an embodiment of this application. Detailed Implementation

[0032] It should be noted that the collection, dissemination, and use of transaction information in the technical solution of this application all comply with the requirements of relevant national laws and regulations.

[0033] The technical solutions in the embodiments of this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " will mean "or", for example, A / B can mean A or B; "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0034] In the description of the embodiments of this application, unless otherwise stated, the term "multiple" refers to two or more, and other quantifiers are similarly understood. The preferred embodiments described herein are for illustration and explanation only and are not intended to limit this application. Furthermore, the embodiments and features in the embodiments of this application can be combined with each other without conflict.

[0035] To further illustrate the technical solutions provided in the embodiments of this application, a detailed description is provided below in conjunction with the accompanying drawings and specific implementation methods. Although the embodiments of this application provide method operation steps as shown in the following embodiments or drawings, more or fewer operation steps may be included in the method based on conventional or non-inventive effort. For steps that do not logically have a necessary causal relationship, the execution order of these steps is not limited to the execution order provided in the embodiments of this application. In actual processing or when the control device executes the method, it may be executed sequentially or in parallel according to the method shown in the embodiments or drawings.

[0036] This application provides a rule generation method and apparatus for a business system. The method involves: obtaining configuration parameters set by a user for inspection objects in transaction information through a database table. The inspection objects include the transaction type and / or process stage of the transaction information, where the process stage includes any one of a generation stage, a storage stage, and an analysis stage. Based on the configuration parameters, inspection rules corresponding to the transaction information are generated. Thus, without modifying the code, the inspection requirements for different transaction types can be met, effectively reducing the development cost of the business system.

[0037] The following describes in detail, with reference to the accompanying drawings, a rule generation method for a business system provided in an embodiment of this application. Specifically, as follows... Figure 1 As shown, it includes the following steps:

[0038] Step 101: Obtain the configuration parameters set by the user for the inspection object in the transaction information through the database table; wherein, the inspection object includes the transaction type and / or process stage of the transaction information, and the process stage includes any one of the generation stage, storage stage and analysis stage.

[0039] For example, the above-mentioned transaction types include, but are not limited to, fund transactions, bond transactions, and foreign exchange transactions.

[0040] It should be noted that the objects of inspection in the above transaction information can be determined in various ways, including but not limited to the following:

[0041] Method 1: Before obtaining the configuration parameters set by the user for the inspection object in the transaction information through the database table, obtain the transaction information, parse the data structure of the transaction information, determine the data type of each data in the transaction information, and determine the inspection object based on the data type of each data.

[0042] For example, the transaction information is "2000 foreign exchange transactions". Parsing the data structure of the transaction information yields the term "foreign exchange transaction". "Foreign exchange transaction" is the transaction type, and foreign exchange transactions are identified as the object of inspection.

[0043] In Method 1, the intelligent operation system can automatically parse the inspection objects in the transaction information, effectively improving the generation efficiency of inspection rules for new transaction types.

[0044] Method 2: Before obtaining the configuration parameters set by the user for the inspection object in the transaction information through the database table, obtain the transaction information and filter out the inspection object from the transaction information according to the user input.

[0045] For example, the transaction information is "500 foreign exchange expiring transactions", where the user sets "foreign exchange expiring transactions" as the object to be inspected.

[0046] In Method 2, users can set the objects to be checked in the transaction information, which makes the rules generated for the transaction information more in line with the user's needs.

[0047] In one possible implementation, the configuration parameters include multiple inspection items. After obtaining the configuration parameters set by the user for the inspection objects in the transaction information through the database table, the multiple inspection items can be verified. When each of the multiple inspection items passes the verification, the inspection rules corresponding to the transaction information are generated based on the configuration parameters. Alternatively, when there are inspection items that fail to pass the verification, a prompt message is displayed to prompt the user to reset the configuration parameters.

[0048] For example, if there are 3 check items in the configuration parameters, the check rules corresponding to the transaction information will be generated based on the configuration parameters only if all 3 check items pass the verification. If any of the 3 check items fail the verification, the user will be prompted to reset the configuration parameters.

[0049] In one possible implementation, the above-mentioned inspection items may include at least one of the following: transaction object inspection, transaction calendar inspection, transaction account type inspection, transaction product information inspection, transaction review method inspection, settlement and accounting mark inspection, accounting inspection, clearing method inspection, transaction interest inspection, planned cash flow inspection, related remittance route inspection, transaction task inspection, and clearing record inspection.

[0050] The transaction object check can be a check between the front-end business system and the back-end business system. Correspondingly, the process of checking the transaction object can be: each transaction data calls the front-end and back-end counterparty fixed parameter query component to check the front-end and back-end counterparties, determining whether the front-end counterparty can map to the back-end counterparty. Optionally, during the transaction object check, relevant information about the transaction object can be automatically supplemented; for example, if the transaction object is "Agricultural Bank of China," the full name and code of "Agricultural Bank of China" can be completed.

[0051] The process of checking the transaction calendar can be as follows: obtain transaction-related calendar information based on transaction elements, check the currency calendar and the backend calendar, and determine whether the transaction settlement date falls on a holiday.

[0052] The transaction account type check process can be as follows: each transaction data point calls the flexible parameter query component provided by the platform to check the transaction account type and determine whether it can be mapped to the region category code and folder type. Optionally, the transaction account type can be automatically supplemented during the transaction account type check.

[0053] Specifically, the transaction product information check can be a check between the front-end business system and the back-end business system. Correspondingly, the process of checking transaction product information can involve each transaction data point calling the flexible parameter query component provided by the platform to perform a front-end and back-end product mapping check, determining whether a business module, business category, and sub-category can be mapped. Optionally, during the transaction product information check, relevant fields of the transaction product information can be automatically supplemented.

[0054] The process of checking the transaction review method can be as follows: Each transaction data point calls the flexible parameter query component provided by the platform to check the transaction review method, determining whether the transaction was manually reviewed or system-reviewed; if no result is found, it is assumed to be system-reviewed. Optionally, when performing a combined transaction review method check, the relevant fields for the transaction review method can be automatically supplemented.

[0055] The process of checking the settlement and accounting flag can be as follows: each transaction data calls the flexible parameter query component provided by the platform to check the settlement and accounting flag, and determines whether the transaction needs to be settled and accounted for. If the flag cannot be retrieved, it is assumed that settlement and accounting are required. Optionally, the relevant fields of the settlement and accounting flag can be automatically supplemented when checking the settlement and accounting flag.

[0056] Among them, accounting refers to the accounting access check. Accordingly, the accounting process can be: calling the method provided by the accounting module to perform the accounting access check. If the check is successful, the corresponding accounting information will be obtained and the corresponding fields will be filled in.

[0057] The process of checking the settlement method can be as follows: each transaction data calls the flexible parameter query component provided by the platform to check the settlement method, determine the cash flow settlement method and settlement mode, and if it cannot be retrieved, it defaults to bilateral full amount; fill in the corresponding fields and store them.

[0058] The process of checking the entry of reverse interest rates for foreign exchange lending transactions can be as follows: the platform's public module is called to determine whether the transaction is a reverse interest rate transaction and check whether it is an access transaction.

[0059] The process of checking planned cash flow can be as follows: generate planned cash flow data based on transaction information, automatically match the flow path, call the transaction clearing and settlement module component, and store it in the clearing planned cash flow data table.

[0060] The process of checking related remittance routes can be as follows: the foreign exchange lending transaction calls the transaction clearing and settlement module to check related remittance routes, and determines whether the planned cash flow can be linked to the receipt and payment remittance routes. If linked, the data is stored in the clearing and settlement receipt and payment remittance route data table.

[0061] The process of verifying task admission checks can be as follows: according to the transaction check rules, the transaction check is performed by first calling the method provided by the transaction settlement verification module to perform the verification method judgment, and then filling and storing the corresponding fields.

[0062] The process of checking the clearing records can be as follows: read the clearing element parameters, determine whether the clearing elements of the two versions are consistent, call the transaction clearing and settlement module to check the clearing records, and determine whether to clear and recover the delivery cash flow sent in the previous version.

[0063] It should be noted that the above inspection items may include field information and / or business inspection types.

[0064] In one possible implementation, the inspection items include field information. The process of verifying the multiple inspection items can be as follows: if a preset data instance is found for the field information, then the field information is determined to have been successfully verified. It should be understood that the field information is a required field in the configuration parameters.

[0065] For example, please refer to Table 1. In Table 1, the user sets up a data table (i.e., transaction contract check configuration information) for the current transaction information, as shown in Table 1. Configuration parameters can then be obtained through this data table. The check items in these configuration parameters include the field information shown in Table 1, namely, check rule ID code, information item name, financial market business type list value, check item name, and remarks. It should be understood that the field content corresponding to the check item name is the content associated with the aforementioned check rule ID code, and the field content corresponding to the remarks is an abbreviation of the content associated with the aforementioned check item name.

[0066] Table 1

[0067] Check configuration information for trading contracts That is, check the rule ID code Information item name List of Financial Market Business Types Inspection Item Name Remarks

[0068] This allows for a non-empty check on the data instance corresponding to the field information. The query revealed that the field information contained, for example... Figure 2 If the data example shown is valid, then the field information has passed the verification.

[0069] For example, taking the check rule ID code (CHK_RULE_ID_CD) as an example, if the data instances corresponding to the check rule ID code (CHK_RULE_ID_CD) are: 140001, 140002, 140003, 140004, 230001, 230002, 230003, 230004, 240004, 240003, 240002, and 240001, then the check rule ID code (CHK_RULE_ID_CD) has a data instance, and the check rule ID code (CHK_RULE_ID_CD) is confirmed to have passed the verification.

[0070] For example, if the field information is the information item name (IFITNM), and the data instances corresponding to the information item name (IFITNM) are 01, 02, and 04, then the information item name (IFITNM) has a data instance, and the information item name (IFITNM) is confirmed to have passed the verification.

[0071] For example, if the field information is the Financial Market Business Type List Value (FNMKT_BSN_TP_LIST_VAL), and the data instance corresponding to the Financial Market Business Type List Value (FNMKT_BSN_TP_LIST_VAL) is the business type code of the transaction: 19-Foreign Exchange Swap, 21-Foreign Exchange Option, and 22-Precious Metals Spot, then the Financial Market Business Type List Value (FNMKT_BSN_TP_LIST_VAL) has a data instance, then the verification of the Financial Market Business Type List Value (FNMKT_BSN_TP_LIST_VAL) is confirmed to be successful.

[0072] For example, taking the field information as an example of the check item name (CHKITM_NM), the data instances corresponding to the check item name (CHKITM_NM) are: Foreign Exchange Swap - Required Item Check, Foreign Exchange Swap - Information Completion Check, Foreign Exchange Swap - Accounting Related Check, Foreign Exchange Swap - Clearing Related Check, Foreign Exchange Option - Required Item Check, Foreign Exchange Option - Information Completion Check, Foreign Exchange Option - Accounting Related Check, Foreign Exchange Option - Clearing Related Check, Precious Metals Spot - Required Item Check, Precious Metals Spot - Information Completion Check, Precious Metals Spot - Accounting Related Check, and Precious Metals Spot - Clearing Related Check; if the check item name (CHKITM_NM) has a data instance, then the check item name (CHKITM_NM) is determined to have passed the verification.

[0073] For example, taking the memo information (RMRK_INF) as an example, the data instance corresponding to the memo information (RMRK_INF) is: mandatory field check, information completion check, accounting related check, and settlement related check; if the memo information (RMRK_INF) has a data instance, then the memo information (RMRK_INF) is confirmed to have passed the verification.

[0074] In one possible implementation, the inspection items include business inspection types, and the process of verifying the multiple inspection items may be: if it is determined that the function corresponding to the business inspection type is executable, then the business inspection type is determined to have been successfully verified. It should be understood that each business inspection type corresponds to a specific function.

[0075] For example, please refer to Table 2. The user has set up a data table as shown in Table 2 (i.e., transaction contract inspection configuration details) for the current transaction information. Configuration parameters can then be obtained through this data table. The inspection items in these configuration parameters include field information as shown in Table 2, namely, inspection rule ID code, record number, inspection stage level name, function call confirmation flag, and program interface name. It should be understood that the inspection stage level name is the business inspection type. In other words, the inspection items in this configuration parameter include both field information and the business inspection type.

[0076] Table 2

[0077] Transaction contract check configuration details Check rule ID code Record Number Inspection process level names Function call confirmation flag Program Interface Name

[0078] This allows for non-empty validation of the data instances corresponding to the field information in Table 2, as well as checks on the functional functions corresponding to the business check types.

[0079] Please refer to Table 3. In Table 3, the data instances corresponding to the check rule ID code (CHK_RULE_ID_CD) are 140001 and 140002. Since there are data instances for the check rule ID code (CHK_RULE_ID_CD), the check rule ID code (CHK_RULE_ID_CD) is verified successfully. The data instances corresponding to the record numbers (RCRD_ID) are 140001024, 140001025, 140001026, 140001027, 140001028, 140002001, 140002002, 140002003, 140002004, 140002005, 140002006, and 140002007. Since there are data instances for the record numbers (RCRD_ID), the record numbers (RCRD_ID) are verified successfully. The inspection stage level name (CHK_LNK_HIER_NM) is the name of the inspection item. The function call confirmation flag (FUNC_CALL_CFM_IND) includes Y and N. If the function call confirmation flag (FUNC_CALL_CFM_IND) is Y, it indicates that the inspection item is a business inspection type, and the corresponding function associated with its program interface name (PRGM_INTF_NM) needs to be called. If the function call confirmation flag (FUNC_CALL_CFM_IND) is N, it indicates that the inspection item is field information and there is no corresponding program interface name (PRGM_INTF_NM). Accordingly, when inspecting an inspection item of a business inspection type, the corresponding function of the business inspection type is required, and the executableness of the function is verified. If the function is executable, a corresponding mapping relationship is established between the business inspection type and the function, so that the configuration parameters set by the user for the transaction information take effect.

[0080] Please refer to Table 3. In Table 3, the inspection stage level name (CHK_LNK_HIER_NM) takes Currency 2 (remote) amount, spot exchange rate, swap type, swap point, near-end price, far-end price, information completion check, front-end and back-end counterparty check, transaction calendar check, transaction account type check, front-end and back-end product mapping check, transaction review method check, and settlement accounting flag check as examples. Among them, Currency 2 (remote) amount, spot exchange rate, swap type, swap point, near-end price, far-end price, and information completion check are field information and do not have function functions. Front-end and back-end counterparty check, transaction calendar check, transaction account check type, front-end and back-end product mapping check, transaction review method check, and settlement accounting flag check are business type checks and require calling the corresponding function functions. When it is determined that the corresponding function function can be executed, the check item of the business check type is determined to have passed the test, and a corresponding mapping relationship is established between the business check type and the function function, so that the configuration parameters set by the user for the transaction information take effect.

[0081] Table 3

[0082]

[0083]

[0084] Step 102: Generate inspection rules corresponding to the transaction information based on the configuration parameters.

[0085] It should be understood that after multiple checks in the configuration parameters set by the user for transaction information have been successfully verified, check rules corresponding to the transaction information are generated based on the configuration parameters. This makes the generated check rules more effective.

[0086] exist Figure 1 In the illustrated method embodiment, configuration parameters set by the user for the inspection objects in the transaction information are obtained through a database table. The inspection objects include the transaction type and / or process stage of the transaction information, where the process stage includes any one of the generation, storage, and analysis stages. Based on the configuration parameters, inspection rules corresponding to the transaction information are generated. Thus, without modifying the code, the inspection requirements corresponding to different transaction types can be met, effectively reducing the development cost of the business system.

[0087] Based on the same inventive concept, this application also provides a rule generation device 300 for a business system, specifically as follows: Figure 3 As shown, it includes:

[0088] The acquisition module 301 is used to acquire configuration parameters set by the user for the inspection object in the transaction information through the database table. The inspection object includes the transaction type and / or process stage of the transaction information. The process stage includes any one of the generation stage, storage stage and analysis stage.

[0089] The processing module 302 is used to generate inspection rules corresponding to the transaction information based on the configuration parameters.

[0090] In one possible implementation, before obtaining the configuration parameters set by the user for the inspection object in the transaction information through the database table, the acquisition module 301 is further configured to: acquire the transaction information; the processing module 302 is further configured to: parse the data structure of the transaction information to determine the data type of each data in the transaction information; and determine the inspection object according to the data type of each data.

[0091] In one possible implementation, before obtaining the configuration parameters set by the user for the inspection object in the transaction information through the database table, the acquisition module 301 is further configured to: acquire the transaction information; the processing module 302 is further configured to: filter out the inspection object from the transaction information according to the user input.

[0092] Optionally, the above-mentioned device 300 includes a display module 303. The configuration parameters include multiple inspection items. After obtaining the configuration parameters set by the user for the inspection objects in the transaction information through the database table, the processing module 302 is further configured to: verify the multiple inspection items; when each of the multiple inspection items passes the verification, generate inspection rules corresponding to the transaction information based on the configuration parameters; or, when there are inspection items that fail the verification, control the display module 303 to display a prompt message, the prompt message being used to prompt the user to reset the configuration parameters.

[0093] In one possible implementation, the inspection items include at least one of the following: transaction object inspection, transaction calendar inspection, transaction account type inspection, transaction product information inspection, transaction review method inspection, settlement and accounting mark inspection, accounting inspection, clearing method inspection, transaction interest inspection, planned cash flow inspection, related remittance route inspection, transaction task inspection, and clearing record inspection.

[0094] In one possible implementation, the inspection items include field information, and the processing module 302 is used to verify the plurality of inspection items, specifically: if the field information is found to have a preset data instance, then the field information is determined to have been successfully verified.

[0095] In one possible implementation, the inspection items include business inspection types, and the processing module 302 is used to verify the plurality of inspection items, specifically: if it is determined that the function corresponding to the business inspection type is executable, then the business inspection type is determined to be successfully verified.

[0096] The following reference Figure 4 To describe an electronic device 130 according to this embodiment of the present application. Figure 4 The electronic device 130 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0097] like Figure 4 As shown, the electronic device 130 is presented in the form of a general-purpose electronic device. The components of the electronic device 130 may include, but are not limited to: at least one processor 131, at least one memory 132, and a bus 133 connecting different system components (including memory 132 and processor 131).

[0098] Bus 133 represents one or more of several bus structures, including a memory bus or memory controller, peripheral bus, processor, or local bus using any of the various bus structures.

[0099] The memory 132 may include a readable medium in the form of volatile memory, such as random access memory (RAM) 1321 and / or cache memory 1322, and may further include read-only memory (ROM) 1323.

[0100] The memory 132 may also include a program / utility 1325 having a set (at least one) of program modules 1324, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0101] Electronic device 130 can also communicate with one or more external devices 134 (e.g., keyboard, pointing device, etc.), and with one or more devices that enable a user to interact with electronic device 130, and / or with any device that enables electronic device 130 to communicate with one or more other electronic devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 135. Furthermore, electronic device 130 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 136. As shown, network adapter 136 communicates with other modules used in electronic device 130 via bus 133. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 130, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0102] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 132 including instructions, which can be executed by a processor 131 of the device 300 to perform the above-described method. Optionally, the computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0103] In an exemplary embodiment, a computer program product is also provided, including a computer program / instructions that, when executed by a processor 131, implement any of the rule generation methods of the business system provided in this application.

[0104] In an exemplary embodiment, various aspects of the rule generation method for a business system provided in this application can also be implemented in the form of a program product, which includes program code. When the program product is run on a computer device, the program code is used to cause the computer device to perform the steps in the rule generation method for a business system according to various exemplary embodiments of this application described above.

[0105] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0106] The program product for displaying the front-end interface of a multi-tenant system according to embodiments of this application can be a portable compact disc read-only memory (CD-ROM) and include program code, and can run on an electronic device. However, the program product of this application is not limited thereto. In this document, the readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0107] A readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code. This propagated data signal may take many forms, including—but not limited to—electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0108] The program code contained on the readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wired, fiber optic, RF, etc., or any suitable combination thereof.

[0109] Program code for performing the operations of this application can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as "Like" or similar programming languages. The program code can execute entirely on the user's electronic device, partially on the user's device, as a standalone software package, partially on the user's electronic device and partially on a remote electronic device, or entirely on a remote electronic device or server. In cases involving remote electronic devices, the remote electronic device can be connected to the user's electronic device via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external electronic device (e.g., via the Internet using an Internet service provider).

[0110] It should be noted that although several units or sub-units of the device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this application, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided and embodied by multiple units.

[0111] Furthermore, although the operations of the method of this application are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0112] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0113] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable image scaling device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable image scaling device, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0114] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable image scaling device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0115] These computer program instructions can also be loaded onto a computer or other programmable image scaling device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0116] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0117] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A rule generation method for a business system, characterized in that, The method includes: The configuration parameters set by the user for the inspection objects in the transaction information are obtained through the database table. The inspection objects include the transaction type and / or process stage of the transaction information. The process stage includes any one of the generation stage, storage stage, and analysis stage. The configuration parameters include at least one of the following inspection items: transaction object inspection, transaction calendar inspection, transaction account type inspection, transaction product information inspection, transaction review method inspection, settlement accounting flag inspection, accounting inspection, clearing method inspection, transaction interest inspection, planned cash flow inspection, related remittance route inspection, transaction task inspection, and clearing record inspection. Based on the preset inspection process, the inspection items included in the configuration parameters are verified accordingly. When each inspection item included in the configuration parameters passes the verification, the inspection rules corresponding to the inspection items included in the transaction information are generated based on the configuration parameters.

2. The method according to claim 1, characterized in that, Before retrieving the configuration parameters set by the user for the inspection object in the transaction information from the database table, the method further includes: Obtain the transaction information; The data structure of the transaction information is parsed to determine the data type of each piece of data in the transaction information; The inspection object is determined based on the data type of each piece of data.

3. The method according to claim 1, characterized in that, Before retrieving the configuration parameters set by the user for the inspection object in the transaction information from the database table, the method further includes: Obtain the transaction information; The objects to be inspected are selected from the transaction information based on user input.

4. The method according to any one of claims 1-3, characterized in that, After obtaining the configuration parameters set by the user for the inspection object in the transaction information through the database table, the method further includes: When multiple inspection items fail to pass inspection, a prompt message is displayed to remind the user to reset the configuration parameters.

5. The method according to claim 4, characterized in that, The inspection items include field information, and the validation of multiple inspection items includes: If a preset data instance is found to exist for the field information, then the field information verification is considered successful.

6. The method according to claim 4, characterized in that, The inspection items include business inspection types, and the verification of multiple inspection items includes: If the function corresponding to the business inspection type is determined to be executable, then the business inspection type is determined to have been successfully verified.

7. A rule configuration device for a business system, characterized in that, Includes a module for performing the method as described in any one of claims 1 to 6.

8. An electronic device, characterized in that, The method includes at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method as described in any one of claims 1-6.

9. A computer storage medium, characterized in that, The computer storage medium stores a computer program that causes the computer to perform the method as described in any one of claims 1-6.

10. A computer program product, characterized in that, The computer program product includes computer instructions that perform the method as described in any one of claims 1-6.

Images