CN111667334B - Audit failure order processing method and device, computer equipment and storage medium - Google Patents
Audit failure order processing method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111667334B CN111667334B CN202010343351.8A CN202010343351A CN111667334B CN 111667334 B CN111667334 B CN 111667334B CN 202010343351 A CN202010343351 A CN 202010343351A CN 111667334 B CN111667334 B CN 111667334B
- Authority
- CN
- China
- Prior art keywords
- order
- audit
- failure
- target
- preset
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
- G06Q30/0635—Processing of requisition or of purchase orders
Abstract
The application relates to the technical field of internet, in particular to a processing method and device for an audit failure order, computer equipment and a storage medium. The method comprises the following steps: receiving an order auditing failure notice; determining a target order corresponding to the order auditing failure notice; determining the type of the corresponding auditing failure reason of the target order; generating preset notification information, and sending the preset notification information to an order butt-joiner corresponding to the target order; and sending an order auditing success message generated according to the order information of the target order to the first server. The embodiment of the invention can shorten the order placing period of the user and improve the order placing efficiency of the user.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for processing an audit failure order, a computer device, and a storage medium.
Background
Currently, in an order placing process of a B2B (Business-to-Business) trading platform, when a user wants to purchase a commodity, the user needs to submit a request for purchasing the commodity to the trading platform for the commodity, and then the trading platform generates a pre-occupied order based on information (for example, commodity information, commodity receiving information, and the like) in the request and sends the pre-occupied order to the user, and the user reviews the pre-occupied order. The user needs to check information in the pre-occupied order after receiving the pre-occupied order, if the pre-occupied order is confirmed to be correct, the order information which is confirmed to be purchased by the user can be sent to the trading platform, the trading platform can check the order information which is confirmed to be purchased by the user, for example, whether the order information is consistent with the pre-occupied order which is placed by the user before is confirmed, whether a warehouse has a plurality of check items such as stock corresponding to the order information is confirmed, and when all the check items are checked to be passed, the trading platform can generate a formal order, namely, the user can successfully complete placing the order.
However, a certain period of time is required for the whole ordering process, and in an actual scene, the user cannot pass the auditing of the trading platform after confirming the pre-occupied order due to some changes (for example, insufficient stock balance of the trading object to be purchased by the user, error in order amount deduction operation, overtime of some interfaces, and the like). Usually, the order does not pass the audit of the trading platform, the flow node needs to be transferred to the user, the user can audit the pre-occupied order again, and the order placing request is submitted to the trading platform again to indicate the trading platform to audit the order, so that the whole order placing period is prolonged. Even if some problems may not be solved later, the order may not be approved by the trading platform, so that the user needs to submit the order request for many times until the problems are solved.
Disclosure of Invention
Aiming at the defects of the prior art, the invention provides a processing method and device for an audit failure order, computer equipment and a storage medium.
The present invention provides, according to a first aspect, a method for processing an audit failure order, which in one embodiment includes:
receiving an order form auditing failure notice;
determining a target order corresponding to the order auditing failure notification;
generating preset notification information;
sending preset notification information to an order dockee corresponding to the target order;
and sending an order form auditing success message generated according to the order form information of the target order form to the first server.
In one embodiment, generating preset notification information, sending the preset notification information to an order dockee corresponding to a target order, and sending an order audit success message generated according to the order information of the target order to a first server includes:
determining the type of the reason of the failure of the auditing corresponding to the target order;
if the checking failure reason type is determined to belong to the preset failure reason type, generating preset notification information, sending the preset notification information to an order butt-joiner corresponding to the target order, and sending an order checking success message generated according to the order information of the target order to the first server;
and if the checking failure reason type is determined not to belong to the preset failure reason type, sending an order checking failure message generated according to the order information of the target order to the first server.
In one embodiment, generating the preset notification information includes:
obtaining order information, audit failure reason information, audit state and order placing user information corresponding to the target order;
and generating preset notification information according to the order information, the audit failure reason information, the audit state and the order placing user information corresponding to the target order.
In one embodiment, after determining that the audit failure cause type belongs to the preset failure cause type, the method further includes:
generating an automatic order auditing rule corresponding to the target order;
monitoring system time;
and when the system time meets the automatic order auditing rule, generating an order auditing request for indicating the second server to audit the target order, and sending the order auditing request to the second server.
In one embodiment, the step of determining the type of the reason for the failure of the audit corresponding to the target order includes:
judging whether the order audit failure notice is a first audit failure notice corresponding to the target order or not;
if the order audit failure notice is determined to be the first audit failure notice corresponding to the target order, determining the audit failure reason type corresponding to the target order;
if the order form audit failure notice is not determined to be the first audit failure notice corresponding to the target order form, determining a preset order form automatic audit rule corresponding to the target order form;
monitoring the current system time;
and when the current system time meets the preset automatic order auditing rule, sending an order auditing request to the second server to instruct the second server to audit the target order.
In one embodiment, determining a preset order automatic audit rule corresponding to the target order includes:
determining the first failure notification time and the preset auditing retry time corresponding to the target order;
if the time difference between the first failure notification time and the current system time does not exceed the preset examination retry time, determining a preset order automatic examination rule corresponding to the target order;
and if the time difference between the first failure notification time and the current system time exceeds the preset auditing retry time, deleting the preset automatic order auditing rule corresponding to the target order.
In one embodiment, sending the preset notification information to an order dockee corresponding to the target order includes:
receiving an order audit success notice sent by the second server, wherein the order audit success notice is sent after the second server receives an order audit request sent by an order dockee through a third server, the order audit success notice is used for auditing a target order and the target order is confirmed to be successfully audited;
and updating the auditing state corresponding to the target order.
The present invention provides an audit failure order processing apparatus according to a second aspect, in one embodiment, the apparatus includes:
the failure notice receiving module is used for receiving order auditing failure notice;
the target order determining module is used for determining a target order corresponding to the order auditing failure notice;
the notification information generation module is used for generating preset notification information;
the notification information sending module is used for sending the preset notification information to the order dockee corresponding to the target order;
and the success message sending module is used for sending an order auditing success message generated according to the order information of the target order to the first server.
The invention provides according to a third aspect a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of an embodiment of any of the methods described above when executing the computer program.
The present invention provides according to a fourth aspect a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the embodiments of the method of any one of the above.
In the embodiment of the invention, after receiving the order audit failure notification, the foreground system firstly determines a target order corresponding to the order audit failure notification; and then generating preset notification information, sending the preset notification information to an order dockee corresponding to the target order, and sending an order audit success message generated according to the order information of the target order to the first server, so that even if the order audit confirmed by the user fails, the user does not need to audit the order confirmed by the user, the labor cost and time cost for the user to place the order can be reduced, and the foreground system can also inform the order dockee corresponding to the target order to follow up to solve the problem, thereby improving the solution efficiency of the problem causing the order audit failure, and shortening the time from the time when the user submits the order to place the order to the time when the order is successfully converted into the formal order.
Drawings
FIG. 1 is a diagram of an exemplary environment in which a method for processing an audit failure order may be implemented;
FIG. 2 is a diagram of an application environment of a processing method for checking failed orders according to another embodiment;
FIG. 3 is a flowchart illustrating a processing method for an audit failure order according to an embodiment;
FIG. 4 is a flow diagram illustrating a processing method for checking a failed order according to another embodiment;
FIG. 5 is a block diagram of an apparatus for processing an audit failure order according to an embodiment;
FIG. 6 is a diagram of the internal structure of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
Fig. 1 shows an application environment of a processing method for an audit failure order according to an embodiment of the present invention.
The user terminal 10 can interact with the trading platform to effect the placing of pre-emptive orders and the placing of official orders. The trading platform includes a first server 21, a foreground system 22 and a second server 23.
Illustratively, the first server 21 may be a user system and the second server 23 may be a central system. The central system 23 is mainly responsible for auditing order information confirmed by a user. Specifically, the user may send an order placing request for confirming a purchase transaction object to the user system 21 through the user terminal 10 when checking the pre-occupied order information, after receiving the order placing request sent by the user, the user system 21 obtains the order information confirmed by the user and sends the order information to the foreground system 22, and the foreground system 22 sends the order information to the central system 23 again. The central system 23 checks the order information, and then notifies the checking result to the foreground system 22, if the order checking is successful, the central system 23 sends an order checking success notification to the foreground system 22, and if the order checking is failed, the central system 23 sends an order checking failure notification to the foreground system 22.
The conventional foreground system 22, upon receiving the order audit failure notification sent by the foreground system 23, generates an order audit failure message according to the notification and sends the order audit failure message to the user system 21. In this embodiment, the influence factors that cause the order audit failure in the past are summarized and classified to obtain multiple audit failure cause types and solution modes corresponding to the various types, and then the audit failure cause type corresponding to the solution mode that does not need the user to participate in among the multiple solution modes is set as the preset failure cause type, and the business logic of the foreground system 22 is adjusted. Specifically, after receiving the order audit failure notification sent by the middleware system 23, the foreground system 22 analyzes the order corresponding to the notification to determine the audit failure reason type corresponding to the order, and if the audit failure reason type corresponding to the order is the preset failure reason type, that is, the order can pass through the audit of the middleware system 23 without the participation of the user, the foreground system 22 sends an order audit success message generated according to the order information of the target order to the user system 21, and simultaneously generates preset notification information to be sent to the order dockee corresponding to the order to notify the order dockee to solve the problem that the order cannot pass through the audit of the middleware system 23. Therefore, for the user, the order confirmed by the user does not need to be checked again or even for multiple times, the labor cost and the time cost input by the user due to order placing are reduced, in addition, the foreground system 22 can timely inform the relevant order dockee to follow up to solve the problem, the solution efficiency of the problem causing order checking failure can be improved, and the time from the time when the user submits the order to place the order to the time when the order is successfully converted into the formal order is shortened.
In another embodiment, an application environment of the auditing failed order processing method of the present invention may also be as shown in fig. 2. Wherein the trading platform further comprises a third server 24. Illustratively, the third server 24 may be a backend system. After the problem is solved, the order dockee can send an order auditing request to the central station system 23 through the background system 24 in real time to call the central station system 23 to audit the order which is processed by the order dockee. Of course, possibly, the order dockee may also interact with the background system 24 through the smart device to send an order review request to the staging system 23 through the background system 24.
The user terminal 10 may be various intelligent devices, including but not limited to various personal computers, notebook computers, smart phones, tablet computers, desktop computers, and the like, and the user system 21, the foreground system 22, the middle platform system 23, and the background system 24 may be implemented by independent servers or a server cluster formed by a plurality of servers.
Fig. 3 shows a processing method for an order with a failure to be checked according to an embodiment of the present invention, and the following description takes the method as an example applied to the foreground system in fig. 1 or fig. 2. The method comprises the following steps:
step S110: and receiving an order auditing failure notice.
In this embodiment, after receiving the order audit request, the second server may audit the order corresponding to the order audit request, and notify the audit result to the foreground system after the audit, if the order audit is successful, the second server may send an order audit success notification to the foreground system, and if the order audit is failed, the second server may send an order audit failure notification to the foreground system. It should be noted that the order audit request may be from the foreground system or from the third server, but the processing logic is the same after the second server receives the order audit requests from different sources, that is, the order corresponding to the order audit request is audited, and then the audit result is sent to the foreground system.
Step S120: and determining the target order corresponding to the order auditing failure notice.
In this embodiment, after receiving the order audit failure notification sent by the second server, the foreground system determines the order (i.e., the target order) corresponding to the notification.
Specifically, the second server may include the order information of the order with the failure of audit in the order audit failure notification and send the order information to the foreground system, so that the foreground system may obtain the order information of the target order from the notification. In another embodiment, only the order number of the order with the audit failure is in the order audit failure notification, so that the foreground system can obtain the order number of the order with the audit failure from the notification, and then find the order information corresponding to the order number of the order with the audit failure from the locally pre-stored order information.
Step S130: and generating preset notification information.
Specifically, the step of the foreground system generating the preset notification information includes:
obtaining order information, audit failure reason information, audit state and order placing user information corresponding to the target order;
and generating preset notification information according to the order information, the audit failure reason information, the audit state and the order placing user information corresponding to the target order.
The order information may include an order identifier, transaction object type information, transaction object quantity information, receiving information, and the like; the audit failure reason information is used for informing the order receiver of detail information of order audit failure, so that the order receiver can conveniently perform subsequent processing on the order, the audit failure reason information can comprise audit failure reason types of the target order and detail information of the order audit failure of the target order, the detail information corresponding to different audit failure reason types is different, and specifically, which information can be set according to actual conditions, for example, if the inventory is insufficient, the current inventory information of a transaction object to be purchased by a user, the quantity information of the transaction object to be purchased by the user, the supplier information of the transaction object and the like can be used as the detail information of the order audit failure; the order user information may refer to account information and/or contact information of the order user.
Specifically, in order to improve the generation efficiency of the preset notification information, a notification information template may be preset, and it may be understood that if there are multiple types of notification information (e.g., mail notification, communication software notification, short message notification, or the like), one notification information template may be set for each type of notification information, and then the template is filled with the order information, the audit failure reason information, the audit state, and the order placing user information corresponding to the obtained target order, so as to generate the preset notification information.
Step S140: and sending the preset notification information to the order dockee corresponding to the target order.
In this embodiment, the order dockee is a person responsible for processing the order that fails to be audited, and specifically, may be a person who designates a docking order for each order placing user (hereinafter, referred to as a dockee), where the order dockee refers to an intelligent terminal used by the person who places the order (understandably, the foreground system records an association relationship between each dockee and the intelligent terminal), so that all orders of the same order placing user are processed by one dockee after the audit fails. And the preset notification information is used for notifying a corresponding dockee of the target order to process the target order, so that the target order cannot be audited through the second server.
Step S150: and sending an order form auditing success message generated according to the order form information of the target order form to the first server.
In this embodiment, the foreground system generates an order audit success message according to the order information of the target order, and sends the order audit success message to the first server. In this embodiment, the execution order of the foreground system in executing step S140 and step S150 is not limited, and step S140 and step S150 may be executed simultaneously, or may be executed in a sequential order.
In this embodiment, after receiving the order audit failure notification, the foreground system determines the target order corresponding to the notification, and then sends the generated preset notification information to the order dockee corresponding to the target order, and sends the order audit success message generated according to the order information of the target order to the first server, so that even if the order audit confirmed by the user fails, the user does not need to audit the order confirmed by the user, which can reduce the labor cost and time cost input by the user due to order placement, and because the foreground system also informs the order dockee corresponding to the target order to follow up with the problem resolution, the efficiency of resolving the problem that the order audit fails can be improved, and the time from when the order is submitted by the user to the successful conversion into the formal order is shortened.
In one embodiment, generating preset notification information, sending the preset notification information to an order dockee corresponding to a target order, and sending an order audit success message generated according to the order information of the target order to a first server includes:
determining the type of the corresponding auditing failure reason of the target order;
if the checking failure reason type is determined to belong to the preset failure reason type, generating preset notification information, sending the preset notification information to an order dockee corresponding to the target order, and sending an order checking success message generated according to the order information of the target order to the first server;
and if the checking failure reason type is determined not to belong to the preset failure reason type, sending an order checking failure message generated according to the order information of the target order to the first server.
In this embodiment, in some scenarios, the reason of the order audit failure may be internal reasons of the trading platform, and may also be some error operations of the user, so that a developer of the trading platform needs to summarize and classify previous conditions that cause the order audit failure, for example, the user confirms that the purchase order information is inconsistent with the pre-occupied order information, the stock of the trading object to be purchased by the user is insufficient, the order amount deduction fails, and some interfaces such as an audit interface used for invoking the second server to perform order audit is overtime, so as to obtain multiple audit failure reason types and solutions corresponding to the various types, and then the audit failure reason type corresponding to the solution that does not need the user to participate in the multiple solutions is set as the preset failure reason type.
For example, after being summarized, the developer finds 4 types of reasons for the failure of the audit, the order is inconsistent (i.e., the information of the order that the user confirms to purchase is inconsistent with the information of the pre-occupied order), the stock is insufficient (i.e., the stock of the transaction object that the user wants to purchase is insufficient), the deduction of the amount of the order is failed, and the interface is invoked for a time-out (the interface may refer to various interfaces). For the type of the reason of the examination failure of the inconsistent order, the solution can be that the foreground system sends relevant information such as the order information for confirming the purchase by the user and the information of the pre-occupied order to the user, so that the user confirms again; for the type of the reason of the failure of the examination of the insufficient inventory, the user is not required to participate in solving the problem, and the customer manager can be responsible for processing, for example, the customer manager coordinates with the merchant providing the relevant transaction object to replenish the inventory; for two auditing failure reason types, namely, the order amount deduction failure or the interface calling overtime, the problem is not required to be solved by the user, and the problem can be solved by technical personnel usually. After the summary, the 3 types of the audit failure reason, that is, the insufficient stock, the order amount deduction failure, and the interface call timeout, may be set as the preset failure reason types.
Further, after defining the type of the reason for the audit failure, a unique identifier, such as error01, error02, etc., may be allocated to each type of the reason for the audit failure, and the form and the style of the unique identifier are not limited in this embodiment; and after the preset failure reason type is set, storing the comparison information of the set preset failure reason type in a foreground system. Therefore, after the second server finishes order audit, if the order audit is determined to be failed, the unique identifier of the audit failure reason type corresponding to the order is contained in the order audit failure notice and is sent to the foreground system, and the foreground system can determine the audit failure reason type of the order corresponding to the notice and whether the audit failure reason type belongs to the preset failure reason type according to the comparison information of the preset failure reason type.
And if the foreground system determines that the auditing failure reason type of the target order belongs to the preset failure reason type, acquiring related information to generate preset notification information, and sending the generated preset notification information to an order dockee corresponding to the target order. When determining the order receiver, the foreground system may determine the order receiver of the target order according to the type of the reason of the failure of the examination of the target order.
Further, if the foreground system determines that the type of the reason for the failure of the audit corresponding to the target order does not belong to the preset type of the reason for the failure, the foreground system sends an order audit failure message generated according to the order information of the target order to the first server, so as to inform the user that the order audit confirmed by the user fails.
In this embodiment, if the foreground system determines that the audit failure reason type corresponding to the target order belongs to the preset failure reason type, and the solution mode corresponding to the preset failure reason type does not need user participation, the foreground system automatically executes the preset processing logic to perform the solution, so that the foreground system generates an order audit success message according to the order information of the target order, and then sends the order audit success message to the first server. The first server then notifies the user himself that the order it confirms has been reviewed. Therefore, after the order auditing is failed, the user does not need to audit the order confirmed by the user again or even for multiple times, the labor cost and the time cost input by the user due to order placing can be reduced, the foreground system can inform the order dockee corresponding to the target order to follow up to solve the problem, the solution efficiency of the problem of the order auditing failure can be improved, and the time from the time when the user submits the order to place the order to the time when the order is successfully converted into the formal order is shortened.
In an embodiment, as shown in fig. 4, after determining that the audit failure reason type belongs to the preset failure reason type, the method further includes:
step S210: generating an automatic order auditing rule corresponding to the target order;
step S220: monitoring system time;
step S230: and when the system time meets the automatic order auditing rule, generating an order auditing request for indicating the second server to audit the target order, and sending the order auditing request to the second server.
In this embodiment, in order to improve the efficiency of problem solution and further shorten the order placing process cycle, after determining that the audit failure reason type of the target order belongs to the preset failure reason type, the foreground system generates an automatic order audit rule corresponding to the target order, monitors the system time, and generates an order audit request to instruct the second server to audit the target order when the system time meets the automatic order audit rule.
Specifically, the foreground system may formulate a timing task, and send an order audit request to the second server at a timing to invoke the second server to audit the target order. The task trigger time interval corresponding to the timing task is appropriately set and adjusted according to the specific application scenario by a relevant person, such as a developer or a system administrator, for example, in one scenario, the task trigger time interval of the timing task may be set to be 30 minutes, 60 minutes, 90 minutes, and the like.
In one embodiment, the step of determining the type of the reason for the failure of the audit corresponding to the target order includes:
judging whether the order audit failure notice is a first audit failure notice corresponding to the target order or not;
and if the order auditing failure notice is determined to be the first auditing failure notice corresponding to the target order, determining the auditing failure reason type corresponding to the target order.
As can be understood from the foregoing embodiment, for an order that does not pass the audit, the foreground system sends an order audit request to the second server at regular time to indicate that the second server performs the audit again on the order that has been previously audited but not passed the audit, so that the order audit failure notification received by the foreground system may correspond to the order that has been audited for the first time by the second server, or may correspond to an order that has been audited but has not passed the audit, and for the latter, since the type of the cause of the audit failure of the order has been determined, the foreground system does not need to determine the type of the cause of the audit failure of the order again.
Specifically, the foreground system determines whether the order audit failure notification is a first audit failure notification corresponding to the target order before determining the type of the reason of the audit failure corresponding to the target order, and executes an operation of determining the type of the reason of the audit failure corresponding to the target order only after determining that the order audit failure notification is the first audit failure notification corresponding to the target order.
More specifically, after forwarding the order information confirmed by the user from the first server (hereinafter, simply referred to as a user confirmed order) to the second server, the foreground system sets an auxiliary identification associated with the order identifier to the user confirmed order, for example, the auxiliary identification defaults to 0, which represents that the foreground system receives the order audit failure notification corresponding to the order for the first time, and when the auxiliary identification is 1, the foreground system does not receive the order audit failure notification corresponding to the order for the first time. Therefore, after receiving an order audit failure notice of a certain order, the foreground system determines an order identifier corresponding to the order audit failure notice, further determines an auxiliary identification identifier corresponding to the order identifier, and can judge whether the received order audit failure notice is a first audit failure notice corresponding to the order according to the current value of the auxiliary identification identifier. It should be noted that, if the foreground system determines that the order audit failure notification is the first audit failure notification corresponding to the order, that is, the auxiliary identification identifier corresponding to the order is 0, then the value of the auxiliary identification identifier needs to be set to 1; if the foreground system determines that the auxiliary identification mark corresponding to the order is 1, the value of the auxiliary equipment mark does not need to be reset.
Further, the processing method for the order with the audit failure provided by this embodiment further includes:
if the order form audit failure notice is not determined to be the first audit failure notice corresponding to the target order form, determining a preset order form automatic audit rule corresponding to the target order form;
monitoring the current system time;
and when the current system time meets the preset automatic order auditing rule, sending an order auditing request to the second server to instruct the second server to audit the target order.
Specifically, if the foreground system determines that the order audit failure notification is not the first audit failure notification corresponding to the target order, it can be seen from the above embodiment that, after the target order is first audited and fails to be audited by the second server, the foreground system generates a corresponding order automatic audit rule for the target order. Therefore, at this time, the foreground system does not need to execute step S140 and step S150, directly determines the preset automatic order audit rule corresponding to the target order, and sends an order audit request to the second server when the monitored current system time meets the automatic order audit rule, so as to instruct the second server to audit the target order.
Based on the foregoing embodiment, in an embodiment, the step of determining, by the foreground system, the preset order automatic audit rule corresponding to the target order includes:
determining the first failure notification time and the preset auditing retry time corresponding to the target order;
if the time difference between the first failure notification time and the current system time does not exceed the preset checking retry time, determining a preset order automatic checking rule corresponding to the target order;
and if the time difference between the first failure notification time and the current system time exceeds the preset auditing retry time, deleting the preset automatic order auditing rule corresponding to the target order.
Generally, when the target order is not checked by the second server due to insufficient inventory, failure of order amount deduction, or timeout of interface call, the target order can be checked by the order receiver in a short time (for example, three days, one week, ten days, and the specific time length may be different in different scenes). However, in a practical application scenario, the problem that the order cannot be checked may not be solved in a short time, and if the foreground system still sends an order checking request for instructing the second server to check the order at regular time, both the foreground system and the second server need to consume some computing resources to process the related transactions of the order (for example, sending an order checking request for the order, checking the order, and the like), which may affect the processing efficiency of other orders. Therefore, in this embodiment, a preset review retry time is set for each order that does not pass the review of the second server, and only when the time difference between the first failure notification time corresponding to the order and the current system time does not exceed the preset review retry time, the foreground system determines the preset automatic order review rule corresponding to the order and executes the subsequent operation; otherwise, the foreground system deletes the preset automatic order audit rule corresponding to the order, that is, the foreground system does not send an order audit request at regular time any more to call the second server to audit the order. The preset review retry time may be set and appropriately adjusted by the relevant personnel according to the specific application scenario, for example, may be set to 10 days, 15 days, and the like.
In one embodiment, after the step of sending the preset notification information to the order dockee corresponding to the target order by the foreground system, the method includes:
receiving an order auditing success notice sent by the second server, wherein the order auditing success notice is sent after the second server receives an order auditing request sent by an order dockee through a third server, and the order auditing success notice is sent after the order dockee determines that the order auditing is successful;
and updating the auditing state corresponding to the target order.
Specifically, a third server in the trading platform may provide a real-time processing function for the order dockee, and after the order dockee has processed the problem related to the target order, an order review request may be sent to the second server through the third server in real time to instruct the second server to review the target order. When the second server receives an order auditing request sent by the third server, the second server audits the order corresponding to the order auditing request, and sends an order auditing success notification to the foreground system after the order auditing success is determined, and after the foreground system receives the notification, the auditing state corresponding to the order is only required to be updated to be auditing success or processed.
Further, considering that the preset order automatic audit rule generated by the foreground system for the order is still in an effective state (for example, a time difference between the first failure notification time corresponding to the order and the current system time does not exceed a preset audit retry time), in order to avoid that the foreground system further sends an order audit request to the second server, the order system determines and deletes the preset order automatic audit rule corresponding to the order after (or before or simultaneously with) updating the audit state corresponding to the order.
In one embodiment, as shown in fig. 5, there is provided an audit failure order processing apparatus, including the following modules:
a failure notification receiving module 110, configured to receive an order audit failure notification;
a target order determination module 120, configured to generate preset notification information;
a notification information generating module 130, configured to determine an audit failure reason type corresponding to the target order;
a notification information sending module 140, configured to send preset notification information to an order dockee corresponding to the target order;
and a success message sending module 150, configured to send an order audit success message generated according to the order information of the target order to the first server.
In one embodiment, the audit failure order processing device further comprises a reason type determining module, a failure message sending module and a processing module.
The reason determining module is used for determining the type of the reason of the failure of the auditing corresponding to the target order.
The failure message sending module is used for sending an order auditing failure message generated according to the order information of the target order to the first server.
The processing module is configured to, when the cause determining module determines that the audit failure cause type belongs to the preset failure cause type, invoke the notification information generating module 130 to generate preset notification information, invoke the notification information sending module 140 to send an order audit success message generated according to the order information of the target order to the first server, and invoke the success message sending module 150 to send the order audit success message generated according to the order information of the target order to the first server; and when the reason determining module determines that the audit failure reason type does not belong to the preset failure reason type, calling a failure message sending module to send an order audit failure message generated according to the order information of the target order to the first server.
In one embodiment, the notification information sending module includes:
the information acquisition submodule is used for acquiring order information, audit failure reason information, audit state and order placing user information corresponding to the target order;
and the notification information generation sub-module is used for generating preset notification information according to the order information, the audit failure reason information, the audit state and the order placing user information corresponding to the target order.
In one embodiment, the audit failure order processing apparatus further comprises:
the audit rule generating module is used for generating an automatic order audit rule corresponding to the target order after the audit failure reason type is determined to belong to the preset failure reason type;
the time monitoring module is used for monitoring system time;
and the auditing request sending module is used for generating an order auditing request for indicating the second server to audit the target order when the system time meets the automatic order auditing rule, and sending the order auditing request to the second server.
In one embodiment, the cause type determination module includes:
the judging submodule is used for judging whether the order auditing failure notice is a first auditing failure notice corresponding to the target order or not;
and the reason type determining submodule is used for determining the audit failure reason type corresponding to the target order when the order audit failure notice is determined to be the first audit failure notice corresponding to the target order.
In one embodiment, the cause type determining module further includes:
the auditing rule determining submodule is used for determining a preset order automatic auditing rule corresponding to the target order when the order auditing failure notice is determined not to be the first auditing failure notice corresponding to the target order;
the current time monitoring submodule is used for monitoring the current system time;
and the auditing request sending module is also used for sending an order auditing request to the second server when the current system time meets the preset automatic order auditing rule so as to indicate the second server to audit the target order.
In one embodiment, the audit rule determination sub-module includes:
the time information determining unit is used for determining the first failure notification time and the preset auditing retry time corresponding to the target order;
the auditing rule determining unit is used for determining a preset order automatic auditing rule corresponding to the target order when the time difference between the first failure notification time and the current system time does not exceed the preset auditing retry time;
and the auditing rule deleting unit is used for deleting the preset automatic auditing rule of the order corresponding to the target order when the time difference between the first failure notification time and the current system time exceeds the preset auditing retry time.
In one embodiment, the audit failure order processing apparatus further comprises:
the successful notification receiving module is used for receiving an order audit success notification sent by the second server, wherein the order audit success notification is sent after the second server receives an order audit request sent by an order dockee through a third server, the order audit request is used for auditing a target order, and the target order is confirmed to be successfully audited;
and the auditing state updating module is used for updating the auditing state corresponding to the target order.
For specific limitations of the audit failure order processing apparatus, reference may be made to the above limitations on the audit failure order processing method, which is not described herein again. All or part of the modules in the above-mentioned audit failure order processing device can be realized by software, hardware and their combination. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, the internal structure of which may be as shown in FIG. 6. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operating system and the computer program to run on the non-volatile storage medium. The database of the computer equipment is used for storing at least one piece of order information, order automatic audit rule and other data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of audit failure order processing.
Those skilled in the art will appreciate that the architecture shown in fig. 6 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
receiving an order form auditing failure notice; determining a target order corresponding to the order auditing failure notice; generating preset notification information, and sending the preset notification information to an order butt-joiner corresponding to the target order; and sending an order form auditing success message generated according to the order form information of the target order form to the first server.
In one embodiment, a processor executes a computer program to generate preset notification information, send the preset notification information to an order dockee corresponding to a target order, and send an order audit success message generated according to order information of the target order to a first server, including: the following steps are also implemented:
determining the type of the corresponding auditing failure reason of the target order;
if the checking failure reason type is determined to belong to the preset failure reason type, generating preset notification information, sending the preset notification information to an order butt-joiner corresponding to the target order, and sending an order checking success message generated according to the order information of the target order to the first server;
and if the checking failure reason type is determined not to belong to the preset failure reason type, sending an order checking failure message generated according to the order information of the target order to the first server.
In one embodiment, the processor executes the computer program to generate the preset notification information, and further performs the following steps:
obtaining order information, audit failure reason information, audit state and order placing user information corresponding to the target order; and generating preset notification information according to the order information, the audit failure reason information, the audit state and the ordering user information corresponding to the target order.
In one embodiment, the processor executes the computer program to perform the following steps after determining that the audit failure cause type belongs to the preset failure cause type:
generating an automatic order auditing rule corresponding to the target order; monitoring system time; and when the system time meets the automatic order auditing rule, generating an order auditing request for indicating the second server to audit the target order, and sending the order auditing request to the second server.
In one embodiment, when the processor executes the computer program to determine the type of the reason for the failure of the audit corresponding to the target order, the following steps are further implemented:
judging whether the order auditing failure notice is a first auditing failure notice corresponding to the target order or not; if the order audit failure notice is determined to be the first audit failure notice corresponding to the target order, determining the audit failure reason type corresponding to the target order; if the order form audit failure notice is not determined to be the first audit failure notice corresponding to the target order form, determining a preset order form automatic audit rule corresponding to the target order form; monitoring the current system time; and when the current system time meets a preset automatic order auditing rule, sending an order auditing request to the second server to indicate the second server to audit the target order.
In one embodiment, when the processor executes the computer program to implement the determination of the preset order automatic audit rule corresponding to the target order, the following steps are further implemented:
determining the first failure notification time and the preset auditing retry time corresponding to the target order; if the time difference between the first failure notification time and the current system time does not exceed the preset examination retry time, determining a preset order automatic examination rule corresponding to the target order; and if the time difference between the first failure notification time and the current system time exceeds the preset auditing retry time, deleting the preset automatic order auditing rule corresponding to the target order.
In one embodiment, after the processor executes the computer program and sends the preset notification information to the order dockee corresponding to the target order, the following steps are further implemented:
receiving an order auditing success notice sent by the second server, wherein the order auditing success notice is sent after the intermediate system receives an order auditing request sent by an order butt-joiner through the third server, and the order auditing success notice is sent after the order auditing success is determined; and updating the auditing state corresponding to the target order.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, performs the steps of:
receiving an order form auditing failure notice; determining a target order corresponding to the order auditing failure notification; generating preset notification information, and sending the preset notification information to an order butt-joiner corresponding to the target order; and sending an order auditing success message generated according to the order information of the target order to the first server.
In one embodiment, when the computer program is executed by the processor, generates preset notification information, sends the preset notification information to an order dockee corresponding to the target order, and sends an order audit success message generated according to the order information of the target order to the first server, the following steps are further implemented:
determining the type of the reason of the failure of the auditing corresponding to the target order;
if the checking failure reason type is determined to belong to the preset failure reason type, generating preset notification information, sending the preset notification information to an order dockee corresponding to the target order, and sending an order checking success message generated according to the order information of the target order to the first server;
and if the checking failure reason type is determined not to belong to the preset failure reason type, sending an order checking failure message generated according to the order information of the target order to the first server.
In one embodiment, the computer program when executed by the processor, when generating the preset notification information, further implements the steps of:
obtaining order information, audit failure reason information, audit state and order placing user information corresponding to the target order; and generating preset notification information according to the order information, the audit failure reason information, the audit state and the order placing user information corresponding to the target order.
In one embodiment, after the computer program is executed by a processor and the auditing failure cause type is determined to belong to a preset failure cause type, the following steps are also implemented:
generating an automatic order auditing rule corresponding to the target order; monitoring system time; and when the system time meets the automatic order auditing rule, generating an order auditing request for indicating the second server to audit the target order, and sending the order auditing request to the second server.
In one embodiment, the computer program is executed by a processor, and when determining the type of the reason for the failure of the audit corresponding to the target order, further implements the following steps:
judging whether the order auditing failure notice is a first auditing failure notice corresponding to the target order or not; if the order audit failure notice is determined to be the first audit failure notice corresponding to the target order, determining the audit failure reason type corresponding to the target order; if the order form audit failure notice is not determined to be the first audit failure notice corresponding to the target order form, determining a preset order form automatic audit rule corresponding to the target order form; monitoring the current system time; and when the current system time meets the preset automatic order auditing rule, sending an order auditing request to the second server to instruct the second server to audit the target order.
In one embodiment, the computer program is executed by a processor, and when determining the preset order automatic audit rule corresponding to the target order, further implements the following steps:
determining the first failure notification time and the preset auditing retry time corresponding to the target order; if the time difference between the first failure notification time and the current system time does not exceed the preset checking retry time, determining a preset order automatic checking rule corresponding to the target order; and if the time difference between the first failure notification time and the current system time exceeds the preset auditing retry time, deleting the preset automatic order auditing rule corresponding to the target order.
In one embodiment, after the computer program is executed by the processor and sends the preset notification information to the order dockee corresponding to the target order, the following steps are further implemented:
receiving an order audit success notice sent by the second server, wherein the order audit success notice is sent after the intermediate platform system receives an order audit request sent by an order dockee through the third server, and the order audit success notice is sent after the target order audit is determined to be successful; and updating the auditing state corresponding to the target order.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above may be implemented by hardware instructions of a computer program, which may be stored in a non-volatile computer-readable storage medium, and when executed, may include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), rambus (Rambus) direct RAM (RDRAM), direct Rambus Dynamic RAM (DRDRAM), and Rambus Dynamic RAM (RDRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, and these are all within the scope of protection of the present application. Therefore, the protection scope of the present patent application shall be subject to the appended claims.
Claims (9)
1. A processing method for an audit failure order is characterized by comprising the following steps:
receiving an order form auditing failure notice;
determining a target order corresponding to the order auditing failure notice;
generating preset notification information;
sending the preset notification information to an order butt-joiner corresponding to the target order;
sending an order auditing success message generated according to the order information of the target order to a first server;
the generating preset notification information, sending the preset notification information to an order dockee corresponding to the target order, and sending an order audit success message generated according to the order information of the target order to the first server includes:
determining the type of the corresponding auditing failure reason of the target order;
if the checking failure reason type is determined to belong to a preset failure reason type, generating preset notification information, sending the preset notification information to an order dockee corresponding to the target order, and sending an order checking success message generated according to the order information of the target order to a first server;
and if the checking failure reason type is determined not to belong to the preset failure reason type, sending an order checking failure message generated according to the order information of the target order to the first server.
2. An audit failure order processing method according to claim 1,
the generating of the preset notification information includes:
obtaining order information, audit failure reason information, audit state and order placing user information corresponding to the target order;
and generating preset notification information according to the order information, the audit failure reason information, the audit state and the order placing user information corresponding to the target order.
3. The review failure order processing method of claim 1,
after determining that the audit failure reason type belongs to a preset failure reason type, the method further includes:
generating an automatic order auditing rule corresponding to the target order;
monitoring system time;
and when the system time meets the automatic order auditing rule, generating an order auditing request for indicating a second server to audit the target order, and sending the order auditing request to the second server.
4. The review failure order processing method of claim 3,
the step of determining the type of the reason for the failure of the audit corresponding to the target order includes:
judging whether the order audit failure notice is a first audit failure notice corresponding to the target order or not;
if the order audit failure notice is determined to be the first audit failure notice corresponding to the target order, determining the type of the audit failure reason corresponding to the target order;
if the order audit failure notice is determined not to be the first audit failure notice corresponding to the target order, determining a preset order automatic audit rule corresponding to the target order; monitoring the current system time; and when the current system time meets the preset automatic order auditing rule, sending an order auditing request to the second server to indicate the second server to audit the target order.
5. An audit failure order processing method according to claim 4 wherein,
the determining of the preset order automatic audit rule corresponding to the target order comprises the following steps:
determining the first failure notification time and the preset auditing retry time corresponding to the target order;
if the time difference between the first failure notification time and the current system time does not exceed the preset checking retry time, determining a preset order automatic checking rule corresponding to the target order;
and if the time difference between the first failure notification time and the current system time exceeds the preset auditing retry time, deleting the preset automatic order auditing rule corresponding to the target order.
6. An audit failure order processing method according to claim 1,
the sending the preset notification information to the order dockee corresponding to the target order includes:
receiving an order audit success notification sent by a second server, wherein the order audit success notification is sent after the second server receives an order audit request sent by an order dockee through a third server, the order audit success notification is to audit the target order and the target order is sent after the target order audit success is determined;
and updating the auditing state corresponding to the target order.
7. An apparatus for implementing the audit failure order processing method of claim 1, comprising:
a failure notice receiving module for receiving order auditing failure notice;
the target order determining module is used for determining a target order corresponding to the order auditing failure notice;
the notification information generation module is used for generating preset notification information;
the notification information sending module is used for sending the preset notification information to the order dockee corresponding to the target order;
and the success message sending module is used for sending an order auditing success message generated according to the order information of the target order to the first server.
8. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 6 are implemented when the computer program is executed by the processor.
9. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010343351.8A CN111667334B (en) | 2020-04-27 | 2020-04-27 | Audit failure order processing method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010343351.8A CN111667334B (en) | 2020-04-27 | 2020-04-27 | Audit failure order processing method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111667334A CN111667334A (en) | 2020-09-15 |
| CN111667334B true CN111667334B (en) | 2022-11-18 |
Family
ID=72382807
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010343351.8A Active CN111667334B (en) | 2020-04-27 | 2020-04-27 | Audit failure order processing method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111667334B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112214527A (en) * | 2020-09-25 | 2021-01-12 | 桦蓥(上海)信息科技有限责任公司 | Financial object abnormal factor screening and analyzing method based on failure response code |
| CN112333239B (en) * | 2020-10-10 | 2023-07-18 | 百度(中国)有限公司 | Business audit notification method, gateway, electronic equipment and readable medium |
| EP4009611A4 (en) * | 2020-10-10 | 2022-09-14 | Baidu (China) Co., Ltd. | Service auditing notification method, gateway, electronic device, and readable medium |
| CN112348442A (en) * | 2020-11-10 | 2021-02-09 | 东方航空物流股份有限公司 | Logistics service method and platform |
| CN112486719B (en) * | 2020-12-14 | 2023-07-04 | 上海万物新生环保科技集团有限公司 | Method and equipment for RPC interface call failure processing |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017063518A1 (en) * | 2015-10-12 | 2017-04-20 | 阿里巴巴集团控股有限公司 | Data processing method, device, and system |
| CN110826964A (en) * | 2019-11-01 | 2020-02-21 | 政采云有限公司 | Order creation method, device, equipment and computer readable storage medium |
-
2020
- 2020-04-27 CN CN202010343351.8A patent/CN111667334B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017063518A1 (en) * | 2015-10-12 | 2017-04-20 | 阿里巴巴集团控股有限公司 | Data processing method, device, and system |
| CN110826964A (en) * | 2019-11-01 | 2020-02-21 | 政采云有限公司 | Order creation method, device, equipment and computer readable storage medium |
Non-Patent Citations (2)
| Title |
|---|
| COORDINATING ORDER PROCESSING IN DECENTRALIZED PRODUCTION UNITS;Dip1.-Ing. W. E. Lulay 等;《Proceedings of the 1998 Winter Simulation Conference 》;20020806;全文 * |
| 电子商务平台结算系统的研究与设计;李佳佳 等;《西北民族大学学报(自然科学版)》;20170315;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111667334A (en) | 2020-09-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111667334B (en) | Audit failure order processing method and device, computer equipment and storage medium | |
| CN111666162B (en) | Distributed message transmission method, device, computer equipment and storage medium | |
| CN108573371B (en) | Data approval method, device, computer equipment and storage medium | |
| CN110633160A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN108446172B (en) | Data calling method and device, computer equipment and storage medium | |
| CN111709794A (en) | Abnormal order processing method and device, computer equipment and storage medium | |
| CN112817995B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN110555769A (en) | Block chain transaction data processing method and device, computer equipment and storage medium | |
| CN113268471A (en) | Method, proxy connection pool, system, device, and medium for processing distributed transactions | |
| CN108366132B (en) | Method and device for managing service between servers, computer equipment and storage medium | |
| CN111222821A (en) | Goods supplementing method and device, computer equipment and storage medium | |
| CN113467824A (en) | Data processing method, device, equipment and storage medium | |
| CN109885382A (en) | The system of cross-system distributed transaction processing method and distributing real time system | |
| CN115544044A (en) | Data consistency keeping method, device, equipment and storage medium | |
| WO2020253045A1 (en) | Configured supplementary processing method and device for data of which forwarding has abnormality, and readable storage medium | |
| CN110941622A (en) | Data processing method and device | |
| TW201941121A (en) | Accounting hotspot prediction method and apparatus | |
| CN112561506A (en) | Live broadcast data processing method, system, device and medium based on virtual currency | |
| CN109245941B (en) | Service compensation method and device | |
| CN111667335B (en) | Order auditing method and device, computer equipment and storage medium | |
| CN113810379B (en) | Exception handling method and multi-service system | |
| CN113051008A (en) | Interface request processing method and device, computer equipment and storage medium | |
| CN109711809B (en) | Merchant attribute setting method and device, computer equipment and storage medium | |
| CN111311102A (en) | Resource ratio adjusting method, device, equipment and computer readable storage medium | |
| CN112990902A (en) | Service processing method, device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |