Order recording method, device, non-volatile storage medium and computer equipment

Abstract

The present invention discloses an order recording method, device, non-volatile storage medium and computer equipment. The method comprises: receiving a target order; determining a target event type corresponding to the target order; determining a target account opening scenario corresponding to the target order according to the target event type, wherein the target account opening scenario represents a scenario in which the target order occurs; updating the content in a record table corresponding to the target account opening scenario according to the order information corresponding to the target order, and obtaining a target record table, wherein the order information includes a transaction object and a transaction account. The present invention solves the technical problem of low update efficiency when there are frequent and large changes in the data involved in the order.

Description

Technical Field

[0001] The present invention relates to the field of information technology, and in particular to an order recording method, device, non-volatile storage medium and computer equipment. Background Art

[0002] At present, the way for finance to generate first-level and second-level accounts is mainly through manual new maintenance by finance, and the probability of change after maintenance is very small. However, the third-level account is the most detailed dimension under the second-level account. For example, the sale of goods in the mall needs to record the main business income account, and the second-level account is the sale of goods. If you want to record the account of each sku at this time, then the second-level account cannot meet the requirement of recording the account of each sku (minimum sales unit) because the second-level account is a summary account. Then you need to generate a third-level account number for each sku (minimum sales unit). However, there are many types of goods. If finance manually maintains all skus (minimum sales units) in the system, the update efficiency is low and it wastes time.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present invention provide an order recording method, apparatus, non-volatile storage medium and computer equipment to at least solve the technical problem of low update efficiency when there are a lot of data involved in an order and there are frequent and large changes.

[0005] According to one aspect of an embodiment of the present invention, an order recording method is provided, including: receiving a target order; determining a target event type corresponding to the target order; determining a target account opening scenario corresponding to the target order according to the target event type, wherein the target account opening scenario represents a scenario in which the target order occurs; and updating the content in a record table corresponding to the target account opening scenario according to order information corresponding to the target order to obtain a target record table, wherein the order information includes a transaction object and a transaction account.

[0006] Optionally, a target account opening scenario corresponding to the target order is determined according to the target event type, including: based on the correspondence between a preset event type and an event identifier, determining the target event identifier corresponding to the target order according to the target event type; based on the correspondence between a preset event identifier and an account opening scenario, determining the target account opening scenario corresponding to the target order according to the target event identifier.

[0007] Optionally, before determining the target account opening scenario corresponding to the target order according to the target event identifier based on the correspondence between the preset event identifier and the account opening scenario, the method includes: setting up multiple account opening scenarios according to preset business needs, wherein any one of the multiple account opening scenarios includes one or more transaction stores; determining the event type corresponding to each of the multiple account opening scenarios; and determining the correspondence between the event identifier and the account opening scenario based on the event type corresponding to each of the multiple account opening scenarios and the correspondence between the event type and the event identifier.

[0008] Optionally, according to the target order, the content in the record table corresponding to the target account opening scenario is updated to obtain the target record table, including: querying whether there is a transaction object corresponding to the target order in the record table; if the transaction object corresponding to the target order does not exist in the record table, adding the transaction object corresponding to the target order and the corresponding object number to the record table, and adding the transaction record to obtain the target record table.

[0009] Optionally, querying whether there is a transaction object corresponding to the target order in the record table also includes: if there is a transaction object corresponding to the target order in the record table, based on the object number corresponding to the transaction object in the record table, updating the transaction record in the record table to obtain the target record table.

[0010] Optionally, the record table corresponding to the target account opening scenario includes multiple account opening elements, and the account opening elements include: transaction object number, transaction account number, and transaction quantity.

[0011] According to another aspect of an embodiment of the present invention, an order recording device is also provided, including: a receiving module for receiving a target order; a type determination module for determining a target event type corresponding to the target order; a scenario determination module for determining a target account opening scenario corresponding to the target order according to the target event type; and a recording module for updating the content in a record table corresponding to the target account opening scenario according to order information corresponding to the target order, to obtain a target record table, wherein the order information includes a transaction object and a transaction account.

[0012] According to another aspect of an embodiment of the present invention, a non-volatile storage medium is provided, the non-volatile storage medium including a stored program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute any one of the above-mentioned order recording methods.

[0013] According to another aspect of the embodiments of the present invention, a computer device is provided. The computer device includes a processor, and the processor is used to run a program. When the program is run, any one of the above-mentioned order recording methods is executed.

[0014] According to another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, any one of the above-mentioned order recording methods is implemented.

[0015] In an embodiment of the present invention, an order recording method is adopted, by receiving a target order; determining a target event type corresponding to the target order; determining a target account opening scenario corresponding to the target order according to the target event type, wherein the target account opening scenario represents a scenario in which the target order occurs; and updating the content in a record table corresponding to the target account opening scenario according to order information corresponding to the target order to obtain a target record table, wherein the order information includes a transaction object and a transaction account, thereby achieving the purpose of automatically updating the content in the record table, thereby realizing the technical effect of improving the update efficiency, and further solving the technical problem of low update efficiency when there are frequent and large changes in the data involved in the order. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0017] Figure 1 A hardware structure block diagram of a computer terminal for implementing an order recording method is shown;

[0018] Figure 2 is a flowchart of an order recording method provided according to an embodiment of the present invention;

[0019] Figure 3 is a transaction flow chart of an order recording method provided according to an optional embodiment of the present invention;

[0020] Figure 4 It is a structural block diagram of an order recording device provided according to an embodiment of the present invention. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0022] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0023] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following interpretations:

[0024] sku: full name Stock Keeping Unit, the smallest sales unit. For example, a ballpoint pen is a sku, but there is a difference between sku and product. For example, a black ballpoint pen and a red ballpoint pen have different product names but can have the same sku.

[0025] According to an embodiment of the present invention, a method embodiment of an order recording method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0026] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 FIG. 1 shows a hardware structure block diagram of a computer terminal for implementing an order recording method. Figure 1 As shown, the computer terminal 10 may include one or more (102a, 102b, ..., 102n are used to illustrate) processors (the processor may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1Different configurations are shown.

[0027] It should be noted that the one or more processors and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0028] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the order recording method in the embodiment of the present invention. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the order recording method of the above-mentioned application is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0029] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 .

[0030] In the commonly used accounting system, there are first-level accounts, second-level accounts and third-level accounts. Among them, the first-level account is the highest level in the accounting account system and represents the main classification of financial activities in the financial report. The first-level account usually corresponds to the major categories in the financial statements, such as assets, liabilities, owner's equity, income, expenses, etc. Each first-level account represents a type of financial activity. The second-level account is located under the first-level account and is used to further subdivide the financial activities in the first-level account. The second-level account provides a more specific classification and can distinguish different aspects of the same type of financial activities. For example, under "income" (first-level account), there may be several second-level accounts, such as main business income, other business income, investment income, etc. The third-level account is a further subdivision under the second-level account, which is used to record more detailed financial information. For example, the third-level account "main business income" can be set under the second-level account, such as "product A sales income", "product B sales income", etc., to record the specific income of different products or services. The use of third-level accounts enables the recording and analysis of financial information to reach a more micro level of business operations. For third-level accounts, because the data involved is large and detailed, it is difficult to manage and update, and the update efficiency is slow. Based on this technical problem, the present invention proposes an embodiment of an order recording method. Figure 2 is a flow chart of an order recording method according to an embodiment of the present invention. Figure 2 As shown, the method comprises the following steps:

[0031] Step S202, receiving the target order.

[0032] In this step, orders can be received in real time, where the orders can be orders generated by users to purchase items. For example, order information can be received from the sales front end, or order data can be regularly imported from the sales system. The target order can include multiple information, such as order ID, product information (including product ID, quantity, price), customer information, store information, transaction time, payment information (including payment method and bank account number), etc.

[0033] Step S204, determining the target event type corresponding to the target order.

[0034] In this step, the target event type of the target order can be determined. The event type of an order refers to the specific financial transaction or business operation type associated with the order. Event type is the basis for the financial system to understand and classify order data. Common order event types include sales orders, purchase orders, return orders, refund orders, prepayment orders, etc. There are many ways to determine the event type of an order. For example, business rules are preset in the system to map the order type to the corresponding event type. For example, all customer sales orders are mapped to the "sale of goods" event type, and all supplier purchase orders are mapped to the "purchase of goods" event type. You can also analyze the attributes of the order, such as the direction of the order (income or expenditure), the type of goods or services, the payment method, etc., and determine the event type based on these attributes.

[0035] Step S206, determining the target account opening scenario corresponding to the target order according to the target event type, wherein the target account opening scenario represents the scenario in which the target order occurs.

[0036] In this step, the target account opening scenario corresponding to the target order is determined according to the target event type. The secondary account information related to the target event type can be determined according to the accounting event table. Among them, the accounting event table records the correspondence between various event types and secondary accounts, as well as the debit and credit identifiers. Specifically, the accounting event table records the secondary accounts to which different business operation types belong. The event type + secondary account number + debit and credit identifier can confirm a unique record. Based on the queried secondary account, the account table can be further checked to obtain the account opening scenario information of the account. The account opening scenario is used to define under what conditions it is necessary to generate more detailed tertiary accounts for specific business operations in order to perform refined accounting.

[0037] In financial automation and accounting systems, an account opening scenario refers to a set of specific conditions or dimensions set to more accurately track and record financial transactions. When generating third-level accounts (or more detailed accounting accounts), account opening scenarios are used to determine the level of detail and specific attributes that need to be recorded. Through account opening scenarios, enterprises can refine financial information to specific elements directly related to business operations, thereby achieving more refined financial management. For example, suppose an e-commerce company is dealing with the accounting process of commodity sales in its financial system. In traditional accounting methods, sales of goods may only be recorded under a second-level account such as "main business income", but for an e-commerce company with multiple products and multiple stores, this recording method is too general and not conducive to in-depth analysis of the sales of each product or store. In order to refine the records, an account opening scenario related to the "main business income" account can be set. For example, the scenario can be set to record the sales revenue of each product in each store. For the second-level account "main business income", the system will generate a specific third-level account number based on the product SKU and store ID. For example, when the system processes a specific sales order, it identifies the product SKU and store ID in the order, and then looks up or creates a new third-level account number corresponding to these two elements in the three-level account table, such as "60010001001-00000001", where "60010001001" is the account number of "main business income" and "00000001" is a third-level account number dynamically generated based on the product SKU and store ID.

[0038] Step S208: Update the content in the record table corresponding to the target account opening scenario according to the order information corresponding to the target order to obtain the target record table, wherein the order information includes the transaction object and the transaction account.

[0039] In this step, according to the order information corresponding to the target order, the record table corresponding to the target account opening scenario (usually the three-level account table) is updated to obtain the target record table. Key information can be extracted from the order, including the transaction object (such as product SKU, service type) and the transaction account (such as store ID, bank account number). This information is the basis for determining the specific elements (element values) in the account opening scenario. Then, based on the determined account opening scenario and the specific elements in the order information (such as product SKU, store ID, bank account number, etc.), the three-level account table is queried and the record table is updated. For example, if there is a matching record, this means that the three-level account number of the combination has been created, and the system will directly use the three-level account number without the need for additional generation operations. If there is no matching record, a new three-level account number can be generated according to the rules of the account opening scenario. For example, for account opening scenario 0001 (main business income), if the query finds that there is no third-level account corresponding to the specific product SKU and store ID combination, the system will generate a new third-level account number by adding 1 to the largest third-level account number in the scenario, and register the newly generated third-level account number together with the transaction object and transaction account information in the third-level account table. Once the third-level account number is obtained, the system will use this information, combined with other financial information of the order (such as amount, date, etc.), to create or update a record in the target record table (usually a financial record table or an accounting entry table). This record will reflect the financial impact of the order in detail, including the income, expenditure, cost, etc. related to it. Through the above steps, not only the efficiency of the update is improved, but also human errors are reduced.

[0040] Through the above steps, the purpose of automatically updating the content in the record table is achieved, thereby realizing the technical effect of improving the update efficiency, and further solving the technical problem of low update efficiency when there are frequent and large changes in the data involved in the order.

[0041] As an optional embodiment, the target account opening scenario corresponding to the target order is determined according to the target event type, including: based on the correspondence between the preset event type and the event identifier, determining the target event identifier corresponding to the target order according to the target event type; based on the correspondence between the preset event identifier and the account opening scenario, determining the target account opening scenario corresponding to the target order according to the target event identifier.

[0042] Optionally, determining the target account opening scenario corresponding to the target order according to the target event type can ensure that each business transaction can be accurately classified into the corresponding accounting account. When the system receives the target order, it first identifies the corresponding financial event type according to the business characteristics of the order. For example, the event type triggered by a commodity sales order may be "commodity sales revenue". Then, based on the correspondence between the preset event type and the event identifier, the system maps the target event type to a specific event identifier. This step is achieved by querying the accounting event table, which records the correspondence between various business operation types and the secondary account numbers and debit and credit identifiers required for financial accounting. After determining the target event identifier, the system can further query the account table to obtain the secondary account information corresponding to the event identifier, and then find out the account opening scenario of the account. The account table records the detailed information of all primary and secondary accounts, including their account numbers, the account opening scenarios to which they belong, etc.

[0043] By using the preset correspondence and configuration information in the database, business events are automatically linked to financial accounting rules, avoiding errors and delays caused by manual processing. Through multi-level configuration of event types, event identifiers, and account opening scenarios, the granularity of financial accounting can be flexibly adjusted to meet different needs and improve efficiency.

[0044] As an optional embodiment, before determining the target account opening scenario corresponding to the target order according to the target event identifier based on the correspondence between the preset event identifier and the account opening scenario, it includes: setting up multiple account opening scenarios according to preset business needs, wherein any one of the multiple account opening scenarios includes one or more transaction stores; determining the event type corresponding to each of the multiple account opening scenarios; and determining the correspondence between the event identifier and the account opening scenario based on the event type corresponding to each of the multiple account opening scenarios and the correspondence between the event type and the event identifier.

[0045] Optionally, before determining the target account opening scenario corresponding to the target order based on the correspondence between the preset event identifier and the account opening scenario, a series of pre-configuration and setting work needs to be performed. A series of account opening scenarios can be defined according to its specific business needs and financial strategies. Each account opening scenario will correspond to one or more business operations, such as commodity sales, service provision, expense expenditure, etc. When setting the account opening scenario, the enterprise should also consider the level of detail and dimensions that need to be recorded in each scenario, such as transaction objects, transaction stores, commodity SKUs, bank accounts, etc., which will serve as account opening elements. Then determine the event types corresponding to each of the multiple account opening scenarios. For each set account opening scenario, it is necessary to clarify which types of financial events it will be applied to. For example, one account opening scenario may focus on recording commodity sales revenue, and another may focus on the expenditure of service fees. This is achieved by associating account opening scenarios with different types of financial transactions, ensuring that each scenario can be accurately applied to the corresponding business operations. Then establish a correspondence between event types and event identifiers, and event types need to be associated with specific event identifiers to facilitate system identification and processing. For example, the event type "goods sales revenue" can be assigned an event identifier, such as "001", so that when the system processes an order, it can quickly determine the event type by identifying the event identifier. After defining the correspondence between the event type and the event identifier, you can configure the link between the event identifier and the account opening scenario. This means that the system will be able to directly determine the corresponding account opening scenario based on the event identifier, that is, determine which account opening elements need to be recorded in a specific financial transaction. For example, the event identifier "001" (goods sales revenue) will be associated with the account opening scenario 0001 (recording product SKU and store ID).

[0046] As an optional embodiment, according to the target order, the content in the record table corresponding to the target account opening scenario is updated to obtain the target record table, including: querying whether there is a transaction object corresponding to the target order in the record table; if the transaction object corresponding to the target order does not exist in the record table, adding the transaction object corresponding to the target order and the corresponding object number to the record table, and adding the transaction record to obtain the target record table.

[0047] As an optional embodiment, querying whether there is a transaction object corresponding to the target order in the record table also includes: when there is a transaction object corresponding to the target order in the record table, based on the object number corresponding to the transaction object in the record table, updating the transaction record in the record table to obtain the target record table.

[0048] Optionally, the target account opening scenario corresponding record table (usually the third-level account table or the relevant transaction record table) is updated according to the target order to generate or maintain the target record table. This process can ensure that the financial information of each order can be accurately recorded. It can be queried whether there is a transaction object corresponding to the target order in the record table (usually the third-level account table or the transaction record table). The transaction object may include specific elements such as product SKU, store ID, bank account number, etc., depending on the setting of the target account opening scenario. For example, if the target account opening scenario is for product sales revenue, it can be checked whether there is a third-level account record corresponding to the combination of product SKU and store ID in the order. If the query result shows that there is already a record matching the transaction object of the target order in the record table, the system will directly use the object number (third-level account number) to register the transaction record without adding a new operation. This means that for the transaction object that has been recorded before, its related financial information will be reused, avoiding duplication of work and data redundancy. If there is no record matching the transaction object of the target order in the record table, the system will perform a new operation. This includes generating a new object number (e.g., a new third-level account number) for the transaction object and registering it in the record table together with the transaction object information (such as product SKU, store ID, etc.). After determining or adding the object number, the system will create or update a detailed transaction record based on the financial information of the target order (such as transaction amount, transaction date, etc.) and the determined third-level account number. This record will be registered in the target record table, thus completing the financial processing of the target order.

[0049] Through such automated processing, financial personnel can reduce manual entry errors, improve data processing efficiency, and ensure the accuracy and completeness of these records.

[0050] As an optional embodiment, the record table corresponding to the target account opening scenario includes multiple account opening elements, and the account opening elements include: transaction object number, transaction account number, and transaction quantity.

[0051] Optionally, when the record table (usually a three-level account table) corresponding to the target account opening scenario is designed to include multiple account opening elements, such a configuration can further refine the record. Specifically, the account opening elements include the transaction object number, transaction account number, transaction quantity, etc., then when the system processes the target order, it will be able to generate a three-level account record containing these detailed information. In addition to the above account opening elements, other information in the order transaction can also be included, such as customer information, transaction time, etc.

[0052] Here is a specific example: Figure 3 is a transaction flow chart of an order recording method according to an optional embodiment of the present invention, such as Figure 3 As shown:

[0053] Step 1: The system receives real-time orders.

[0054] Step 2: Query the accounting event table based on the event type of the order to find out which accounting entries need to be recorded for the current business order.

[0055] Step 3: Query the account table according to the secondary account configured in the accounting event to obtain the current account opening scenario.

[0056] Step 4: Query the scenario table to obtain account opening elements based on the account opening scenario.

[0057] Step 5. Check whether the third-level account number exists based on the account opening scenario + factors. If it exists, reuse the current third-level account number. If it does not exist, query the largest third-level account number + 1 in the current account opening scenario based on the account opening scenario and register the third-level account table, and then register the account table.

[0058] Among them, the accounting event table records the secondary accounts of different business operation types, and the event type + secondary account number + debit and credit identifier confirm a unique record. The account table records all the primary and secondary accounts of the company and confirms their account opening scenarios. The primary account number + secondary account number confirms a unique record, and the account opening scenario is associated with the account opening scenario in the scenario table. The account opening scenario table records the account opening scenarios of all secondary accounts, and the account opening scenario number confirms a unique record. (For example: the account opening scenario number of the main business income is 0001, so a record with the account opening scenario number 0001 is generated in the account opening scenario table. At the same time, the account of the main business income is confirmed with the finance department. The finance department must be accurate to the product details of each store. Therefore, it can be confirmed that the account opening element 1 of the 0001 account opening scenario is the product detail code, i.e. skuId, the account opening element 2 is the store code shopId, and the account opening element 3 is empty). The third-level account table records the third-level account codes of the account opening elements that are not available in each account opening scenario, and the third-level account numbers of the same scenario are accumulated.

[0059] Correspondingly, the system pages can be configured, for example, the accounting event configuration page, which is mainly used to maintain the basic data of user accounting events. Before going online, the business confirms which business scenarios are involved, and the finance confirms the first-level and second-level accounts to which the accounting entries of each business scenario belong, and the initial data is registered on this interface. The account configuration page, this page is mainly used by the finance to confirm the account numbers of all first-level and second-level accounts involved in the company, and the initialization parameters are maintained on this page after going online. The account opening scenario maintenance page, this page is used by the finance to confirm the latitude to which each second-level account needs to be recorded, and the key of the account opening scenario is configured based on this maintenance. It is maintained on this page after going online.

[0060] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence, because according to the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

[0061] Through the description of the above implementation methods, those skilled in the art can clearly understand that the order recording method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0062] According to an embodiment of the present invention, an order recording device for implementing the above order recording method is also provided. Figure 4 is a structural block diagram of an order recording device provided according to an embodiment of the present invention. Figure 4 As shown, the order recording device includes: a receiving module 42, a type determination module 44, a scene determination module 46 and a recording module 48. The order recording device is described below.

[0063] The receiving module 42 is used to receive the target order.

[0064] The type determination module 44 is connected to the receiving module 42 and is used to determine the target event type corresponding to the target order.

[0065] The scenario determination module 46 is connected to the type determination module 44 and is used to determine the target account opening scenario corresponding to the target order according to the target event type.

[0066] The recording module 48 is connected to the scenario determination module 46, and is used to update the content in the record table corresponding to the target account opening scenario according to the order information corresponding to the target order, so as to obtain the target record table, wherein the order information includes the transaction object and the transaction account.

[0067] Optionally, the type determination module is used to determine the target account opening scenario corresponding to the target order according to the target event type, including: an identifier determination unit, used to determine the target event identifier corresponding to the target order according to the target event type based on the correspondence between the preset event type and the event identifier; a scenario determination unit, used to determine the target account opening scenario corresponding to the target order according to the target event identifier based on the correspondence between the preset event identifier and the account opening scenario.

[0068] Optionally, before the scenario determination unit is used to determine the target account opening scenario corresponding to the target order based on the correspondence between preset event identifiers and account opening scenarios and according to the target event identifier, it includes: a setting unit, used to set multiple account opening scenarios according to preset business requirements, wherein any one of the multiple account opening scenarios includes one or more transaction stores; a type determination unit, used to determine the event type corresponding to each of the multiple account opening scenarios; and a relationship determination unit, used to determine the correspondence between the event identifier and the account opening scenario based on the event type corresponding to each of the multiple account opening scenarios and the correspondence between the event type and the event identifier.

[0069] Optionally, the recording module is used to update the content in the record table corresponding to the target account opening scenario according to the target order to obtain the target record table, including: a query unit is used to query whether there is a transaction object corresponding to the target order in the record table; an adding unit is used to add the transaction object corresponding to the target order and the corresponding object number to the record table if the transaction object corresponding to the target order does not exist in the record table, and add the transaction record to obtain the target record table.

[0070] Optionally, the query unit is used to query whether there is a transaction object corresponding to the target order in the record table, and also includes: when there is a transaction object corresponding to the target order in the record table, the update unit is used to update the transaction record in the record table based on the object number corresponding to the transaction object in the record table to obtain the target record table.

[0071] Optionally, the record table corresponding to the target account opening scenario includes multiple account opening elements, and the account opening elements include: transaction object number, transaction account number, and transaction quantity.

[0072] It should be noted that the receiving module 42, the type determination module 44, the scene determination module 46 and the recording module 48 correspond to steps S202 to S208 in the embodiment, and the examples and application scenarios implemented by the multiple modules and the corresponding steps are the same, but are not limited to the contents disclosed in the above embodiment. It should be noted that the above modules, as part of the device, can be run in the computer terminal 10 provided in the embodiment.

[0073] An embodiment of the present invention may provide a computer device. Optionally, in this embodiment, the computer device may be located in at least one network device among multiple network devices of a computer network. The computer device includes a memory and a processor.

[0074] Among them, the memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the order recording method and device in the embodiment of the present invention. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, the above-mentioned order recording method is realized. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory may further include a memory remotely arranged relative to the processor, and these remote memories can be connected to the computer terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0075] The processor can call the information and application stored in the memory through the transmission device to execute the following steps: receive a target order; determine the target event type corresponding to the target order; determine the target account opening scenario corresponding to the target order based on the target event type, wherein the target account opening scenario represents the scenario in which the target order occurs; based on the order information corresponding to the target order, update the content in the record table corresponding to the target account opening scenario to obtain the target record table, wherein the order information includes the transaction object and the transaction account.

[0076] Optionally, the processor may also execute the program code of the following steps: determining the target account opening scenario corresponding to the target order according to the target event type, including: determining the target event identifier corresponding to the target order according to the target event type based on the correspondence between the preset event type and the event identifier; determining the target account opening scenario corresponding to the target order according to the target event identifier based on the correspondence between the preset event identifier and the account opening scenario.

[0077] Optionally, the processor may also execute program code for the following steps: based on the correspondence between preset event identifiers and account opening scenarios, determining a target account opening scenario corresponding to a target order according to a target event identifier, including: setting a plurality of account opening scenarios according to preset business requirements, wherein any one of the plurality of account opening scenarios includes one or more transaction stores; determining event types corresponding to each of the plurality of account opening scenarios; and determining a correspondence between event identifiers and account opening scenarios based on event types corresponding to each of the plurality of account opening scenarios and the correspondence between event types and event identifiers.

[0078] Optionally, the processor may also execute the program code of the following steps: according to the target order, updating the content in the record table corresponding to the target account opening scenario to obtain the target record table, including: querying whether there is a transaction object corresponding to the target order in the record table; if there is no transaction object corresponding to the target order in the record table, adding the transaction object corresponding to the target order and the corresponding object number to the record table, and adding the transaction record to obtain the target record table.

[0079] Optionally, the processor may also execute the program code of the following steps: query whether there is a transaction object corresponding to the target order in the record table, and also include: when there is a transaction object corresponding to the target order in the record table, based on the object number corresponding to the transaction object in the record table, updating the transaction record in the record table to obtain the target record table.

[0080] Optionally, the processor may also execute program code of the following steps: the record table corresponding to the target account opening scenario includes multiple account opening elements, and the account opening elements include: transaction object number, transaction account number, and transaction quantity.

[0081] An embodiment of the present invention provides an order recording method, which includes receiving a target order; determining a target event type corresponding to the target order; determining a target account opening scenario corresponding to the target order according to the target event type, wherein the target account opening scenario represents a scenario in which the target order occurs; and updating the content in a record table corresponding to the target account opening scenario according to order information corresponding to the target order to obtain a target record table, wherein the order information includes a transaction object and a transaction account, thereby achieving the purpose of automatically updating the content in the record table, thereby realizing the technical effect of improving the update efficiency, and further solving the technical problem of low update efficiency when there are frequent and large changes in the data involved in the order.

[0082] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a non-volatile storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0083] The embodiment of the present invention further provides a non-volatile storage medium. Optionally, in this embodiment, the non-volatile storage medium can be used to store the program code executed by the order recording method provided in the above embodiment.

[0084] Optionally, in this embodiment, the non-volatile storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0085] Optionally, in this embodiment, the non-volatile storage medium is configured to store program codes for executing the following steps: receiving a target order; determining a target event type corresponding to the target order; determining a target account opening scenario corresponding to the target order based on the target event type, wherein the target account opening scenario represents a scenario in which the target order occurs; and updating the content in a record table corresponding to the target account opening scenario based on order information corresponding to the target order to obtain a target record table, wherein the order information includes a transaction object and a transaction account.

[0086] An embodiment of the present invention also provides a computer program product, including a computer program. Optionally, in this embodiment, when the computer program is executed by a processor, it can achieve: receiving a target order; determining a target event type corresponding to the target order; determining a target account opening scenario corresponding to the target order based on the target event type, wherein the target account opening scenario represents a scenario in which the target order occurs; and updating the content in a record table corresponding to the target account opening scenario based on the order information corresponding to the target order to obtain a target record table, wherein the order information includes a transaction object and a transaction account.

[0087] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0088] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0089] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0090] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0091] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0092] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a non-volatile storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0093] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. An order recording method, characterized in that: include: Receive target orders; Determine the target event type corresponding to the target order; Determining a target account opening scenario corresponding to the target order according to the target event type, wherein the target account opening scenario represents a scenario in which the target order occurs; According to the order information corresponding to the target order, the content in the record table corresponding to the target account opening scenario is updated to obtain a target record table, wherein the order information includes a transaction object and a transaction account.

2. The method according to claim 1, characterized in that The determining, according to the target event type, a target account opening scenario corresponding to the target order includes: Based on the preset correspondence between the event type and the event identifier, determine the target event identifier corresponding to the target order according to the target event type; Based on the correspondence between the preset event identifier and the account opening scenario, the target account opening scenario corresponding to the target order is determined according to the target event identifier.

3. The method according to claim 2, characterized in that Before determining the target account opening scenario corresponding to the target order according to the target event identifier based on the correspondence between the preset event identifier and the account opening scenario, the method includes: According to preset business requirements, multiple account opening scenarios are set, wherein any one of the multiple account opening scenarios includes one or more transaction stores; Determining the event type corresponding to each of the multiple account opening scenarios; Based on the event types corresponding to the multiple account opening scenarios and the correspondence between the event types and the event identifiers, the correspondence between the event identifiers and the account opening scenarios is determined.

4. The method according to claim 1, characterized in that The updating of the content in the record table corresponding to the target account opening scenario according to the target order to obtain the target record table includes: Check whether there is a transaction object corresponding to the target order in the record table; In the case that the transaction object corresponding to the target order does not exist in the record table, the transaction object corresponding to the target order and the corresponding object number are added to the record table, and the transaction record is added to obtain the target record table.

5. The method according to claim 4, characterized in that The querying whether there is a transaction object corresponding to the target order in the record table also includes: In the case that the transaction object corresponding to the target order exists in the record table, the transaction record in the record table is updated based on the object number corresponding to the transaction object in the record table to obtain the target record table.

6. The method according to any one of claims 1 to 5, characterized in that: The record table corresponding to the target account opening scenario includes multiple account opening elements, and the account opening elements include: transaction object number, transaction account number, and transaction quantity.

7. An order recording device, characterized in that: include: A receiving module, used for receiving a target order; A type determination module, used to determine the target event type corresponding to the target order; A scenario determination module, used to determine a target account opening scenario corresponding to the target order according to the target event type; The recording module is used to update the content in the record table corresponding to the target account opening scenario according to the order information corresponding to the target order to obtain the target record table, wherein the order information includes the transaction object and the transaction account.

8. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored program, wherein when the program is executed, the device where the non-volatile storage medium is located is controlled to execute the order recording method described in any one of claims 1 to 6.

9. A computer device, characterized in that: include: Memory and processor, The memory stores a computer program; The processor is used to execute the computer program stored in the memory, and when the computer program is run, the processor executes the order recording method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the order recording method according to any one of claims 1 to 6 is implemented.

Images