Abnormal order processing method and device, storage medium and electronic equipment

Abstract

The invention provides an abnormal order processing method and device, a storage medium and electronic equipment, and relates to the field of information processing. The abnormal order processing method comprises the following steps: acquiring abnormal information generated when an abnormal order flows in an operation node of an order management system; carrying out classification processing on the abnormal information, and determining an abnormal type corresponding to the abnormal information, the abnormal type including retry abnormity or non-retry abnormity; and based on a target exception type selected by the target user from exception types corresponding to the exception information and a triggering operation of the target user on a control matched with the target exception type, performing adaptive processing on a target exception order belonging to the target exception type. According to the invention, the processing efficiency of the abnormal order can be improved, and the stability and reliability of the system are improved.

Description

Technical Field

[0001] This application relates to the field of information processing, and in particular, to an abnormal order processing method, apparatus, storage medium, and electronic device. Background Art

[0002] Currently, for abnormal orders that occur in the OMS (Order Management System), there is a problem of chaotic management, which is not convenient for users to view and operate on abnormal orders. For example, the OMS system lacks a clear processing flow for abnormal orders, and no retry operation can be performed after an abnormal order appears. Moreover, the abnormal types and descriptions of abnormal orders are also relatively chaotic, making it difficult for users to understand the specific situation and handling methods of the abnormalities. In addition, even if an abnormal order is generated during the execution process, the OMS system still allows the abnormal order to continue to flow, resulting in more problems in subsequent operations. Summary of the Invention

[0003] In view of this, embodiments of the present application provide an abnormal order processing method, apparatus, storage medium, and electronic device.

[0004] In a first aspect, an embodiment of the present application provides an abnormal order processing method applied to an order management system. The method includes: obtaining abnormal information generated when an abnormal order flows through operation nodes in the order management system; classifying the abnormal information to determine the corresponding abnormal type, where the abnormal type includes a retryable abnormal or a non-retryable abnormal; and performing adaptive processing on a target abnormal order belonging to the target abnormal type based on the target abnormal type selected by a target user from the corresponding abnormal types of the abnormal information and the triggering operation of the target user on a control matching the target abnormal type.

[0005] In combination with the first aspect, in some implementation manners of the first aspect, performing adaptive processing on a target abnormal order belonging to the target abnormal type includes: if the target abnormal type is a retryable abnormal, modifying the current status bit of the target abnormal order belonging to the retryable abnormal to a pause status bit, and displaying a processing link, so that after the target user clicks the processing link, the target user enters the abnormal order management interface of the order management system to perform a retry operation on the target abnormal order, where the current status bit of the target abnormal order is flag information used to describe the current state of the target abnormal order.

[0006] In combination with the first aspect, in some implementation manners of the first aspect, the method further includes: if the retry processing on the target abnormal order is successful, automatically sending the target abnormal order to the next operation node of the operation node that generated the abnormal information in sequence, where the retry processing includes a withdrawal processing and / or a cancellation processing.

[0007] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: if the retry processing of the target exception order fails, restoring the suspension status bit of the target exception order to the current status bit, and prompting the target user to manually send the target exception order to the next operation node of the operation node that generates the exception information in sequence.

[0008] In combination with the first aspect, in certain implementations of the first aspect, performing adaptive processing on a target exception order belonging to a target exception type includes: if the target exception type is a non-retryable exception, maintaining the current status bit of the target exception order belonging to the non-retryable exception, and prompting the target user to process it.

[0009] In combination with the first aspect, in certain implementations of the first aspect, after determining the exception type corresponding to the exception information, the method further includes: storing the exception order, the exception information corresponding to the exception order, and the exception type in an exception classification table, so that when the target user selects the target exception type from the exception types, displaying the target exception order and exception information belonging to the target exception type to the target user, and displaying a control matching the target exception type.

[0010] In combination with the first aspect, in certain implementations of the first aspect, obtaining the exception information generated when the exception order flows through the operation nodes of the order management system includes: obtaining, through the exception order management interface in the order management system, the exception information generated when the exception order flows through the operation nodes of the order management system within a specified time.

[0011] In a second aspect, an embodiment of the present application provides an exception order processing device applied to an order management system. The device includes: an obtaining module, configured to obtain the exception information generated when the exception order flows through the operation nodes of the order management system; a first processing module, configured to perform classification processing on the exception information to determine the exception type corresponding to the exception information, where the exception type includes a retryable exception or a non-retryable exception; a second processing module, configured to perform adaptive processing on the target exception order belonging to the target exception type based on the target exception type selected by the target user from the exception types corresponding to the exception information, and the trigger operation of the target user on the control matching the target exception type.

[0012] In a third aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program for executing the exception order processing method described in the first aspect.

[0013] In a fourth aspect, an embodiment of the present application provides an electronic device including: a processor; a memory for storing processor-executable instructions; the processor is configured to execute the exception order processing method described in the first aspect.

[0014] In this embodiment, through the automated anomaly detection of the OMS system, abnormal orders and the abnormal information generated during the circulation of abnormal orders in the OMS system can be determined, so as to take corresponding processing measures subsequently, avoiding the waste of manual investigation and processing time, and enabling target users to obtain feedback and processing on abnormal orders in a timely manner, enhancing the satisfaction of target users with the processing of abnormal orders, and further improving the loyalty and repurchase rate of target users. By classifying and processing the abnormal information, the processing efficiency of abnormal orders can be greatly improved. By timely discovering and processing abnormal information, the occurrence of system failures and data errors can be prevented, and the stability and reliability of the system can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] By describing the embodiments of the present application in more detail in conjunction with the accompanying drawings, the above and other objects, features, and advantages of the present application will become more obvious. The accompanying drawings are used to provide a further understanding of the embodiments of the present application, and constitute a part of the specification. They are used together with the embodiments of the present application to explain the present application, and do not constitute a limitation to the present application. In the accompanying drawings, the same reference numerals generally represent the same components or steps.

[0016] Figure 1 The following shows a schematic flow chart of an abnormal order processing method provided by an embodiment of the present application.

[0017] Figure 2 The following shows a schematic flow chart of adaptively processing a target abnormal order provided by an embodiment of the present application.

[0018] Figure 3 The following shows a schematic structural diagram of an abnormal order processing device provided by an embodiment of the present application.

[0019] Figure 4 The following shows a schematic structural diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0020] The following will clearly and completely describe the technical solutions in the embodiments of the present application in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0021] Regarding the abnormal orders that appear in the OMS system, there is currently a problem of chaotic management, which is not convenient for users to view and operate on the anomalies. For example, it includes the following three aspects.

[0022] First, the processing flow for order execution anomalies is missing, and there is no retry operation after an abnormal order occurs.

[0023] Specifically, if an exception occurs during the execution of an order in the OMS system, due to the fact that the OMS system did not fully consider the handling of exception situations during its design, or because there is a lack of an effective handling mechanism to deal with different types of exceptions, and there is no option to provide a retry operation, the handling of exception orders is blocked. Due to the absence of a retry operation, users may need to manually resubmit the order, which not only increases the workload of users, but also may prolong the processing time of exception orders, and moreover, reduces customer satisfaction.

[0024] Second, the scenarios corresponding to exception orders are numerous and complex. At the same time, the exception types and descriptions corresponding to exception orders also need to be optimized and sorted out.

[0025] Specifically, in the current OMS system, different scenarios may involve different business areas and operation links, such as insufficient inventory, payment failure, logistics distribution problems, etc. Correspondingly, the handling methods and priorities of exception orders in these scenarios are also different. However, the existing OMS system may not clearly classify and define exception types, or the exception descriptions are too vague, resulting in users having difficulty understanding the specific situation and handling methods of exceptions.

[0026] Third, the generated exception orders can still continue to flow in the OMS system.

[0027] Specifically, there is a problem in the current OMS system that even if an exception occurs during the execution of an order, the OMS system still allows the exception order to continue to flow, which means that exception information may not be captured and processed in a timely manner, resulting in more problems in subsequent operations. In addition, there may be a "Execution Exception" tab page in the OMS system, but due to the fact that the OMS system does not provide sufficient exception information or corresponding operation options, this tab page does not play its due management role, making it impossible for users to effectively manage and handle exception situations through this tab page, thereby affecting the smooth execution of exception orders and customer satisfaction.

[0028] Based on the above, the present application provides a method for handling exception orders. Specifically, in this embodiment, through automated exception detection of the OMS system, exception orders and the exception information generated when the exception orders flow in the OMS system can be determined, so as to take corresponding handling measures subsequently, avoiding the waste of manual investigation and handling time, and also enabling the target users to obtain feedback and handling of exception orders in a timely manner, enhancing the satisfaction of the target users with the handling of exception orders, and thereby improving the loyalty and repurchase rate of the target users. By classifying and processing exception information, the processing efficiency of exception orders can be greatly improved. By timely discovering and handling exception information, the occurrence of system failures and data errors can be prevented, and the stability and reliability of the system can be improved.

[0029] Figure 1 The following is a schematic flowchart of an abnormal order processing method provided by an embodiment of the present application. Exemplarily, the abnormal order processing method in the present application is applied to an order management system. As Figure 1 shown, the abnormal order processing method in this embodiment includes the following steps.

[0030] Step S110: Obtain the abnormal information generated when the abnormal order flows through the operation nodes in the order management system.

[0031] The operation nodes in the OMS system can be designed differently according to business requirements, but usually include the following general nodes. For example, order generation: when a user places an order, the OMS system generates a corresponding order according to the selected products by the user; order review: the OMS system reviews the newly generated order to determine the validity and accuracy of the order; inventory check: after the order is generated, the OMS system checks whether the product inventory is sufficient to determine whether normal delivery is possible; order delivery: when the inventory is sufficient, the OMS system executes the delivery operation according to the order and sends the products from the warehouse; logistics distribution: the OMS system manages the logistics distribution link to ensure that the products can be delivered to the customer on time; order completion: when the user receives the products and confirms receipt, the OMS system marks the order as completed.

[0032] In addition, there are some other operation nodes adapted to business requirements, such as allocating a carrier, splitting / merging orders, generating an execution order, etc. Among them, allocating a carrier means that the OMS system selects the most suitable carrier for delivery according to factors such as the delivery address, goods weight, and volume of the order to ensure that the order can be delivered to the destination on time and safely; splitting / merging orders means that during the order management process, an order needs to be split into multiple sub-orders or multiple orders need to be merged into one order for processing, and the splitting / merging order node is to complete this operation. Through the splitting / merging order operation, orders can be split or merged to better meet the requirements of logistics distribution and inventory management; the execution order is an intermediate file generated during the order processing process, which is used to record the processing status and operation records of the order, for example, recording the product name, quantity, specification, delivery address, etc. of the order, as well as the processing status of the order, such as confirmed, shipped, received, etc. By generating the execution order, the order information can be converted into the execution order format to facilitate the subsequent order processing and logistics distribution work to proceed smoothly.

[0033] In the OMS system, when an order is flowing through the above operation nodes, it may generate an exception due to reasons such as incorrect order information, insufficient inventory, logistics problems, payment problems, etc., and then determine the exception order in the order. The exception information in this embodiment refers to the specific information describing the exception situation of the exception order. Exemplarily, the exception information corresponding to the exception order includes: the number, date, and time of the exception order; or, it also includes the specific reasons for the exception, such as the information errors, insufficient inventory, logistics problems, payment problems, etc. mentioned above; or, it also includes the operation node where the exception order is located; or, it also includes the records and results of processing the exception order, such as manual intervention processing, refund, re-delivery, etc.; or, it also includes the impact of the exception order on customer satisfaction, such as customer feedback and complaints, etc.

[0034] Step S120, classify and process the exception information to determine the exception type corresponding to the exception information.

[0035] The exception types include retryable exceptions or non-retryable exceptions. Specifically, a retryable exception refers to an exception that may fail due to temporary reasons (such as network problems, database connection problems, etc.) during the operation of the OMS system, but can be resolved or recovered by re-trying. It can be understood that such exceptions usually have the ability to self-repair or can be processed by simple repeated operations. Therefore, in the classification of some exception information, retryable exceptions and system exceptions can be used simultaneously to characterize the exception type to which an order belongs. A non-retryable exception refers to a serious problem that occurs during the program operation, resulting in an exception where the program cannot continue to execute or cannot be recovered. Such exceptions usually involve the core logic of the program, resource limitations, or security issues, etc.

[0036] Further, it is possible to determine whether an exception message is a retryable exception by examining aspects such as the exception message, exception type, and exception handling logic. For example, check whether the exception message contains a description of a transient problem, such as network timeout, database connection failure, etc. These messages can help determine whether a retry is possible. Or, if the exception type is a known retryable exception type, such as IOException, TimeoutException, etc., then it can be determined as a retryable exception. Or, search for the exception handling logic in the program. If there is a retry mechanism or timeout handling mechanism, then it can be determined that this exception message is a retryable exception. Correspondingly, check whether the exception message contains a description of a serious problem, such as null pointer access, type conversion exception, etc. These messages can help determine whether it is non-retryable. Or, if the exception type is a known non-retryable exception type, such as NullPointerException, ClassCastException, etc., then it can be determined as a non-retryable exception. Or, search for the exception handling logic in the program. If there is a specific error handling mechanism or logging mechanism, then it can be determined that this exception is a non-retryable exception.

[0037] In addition to the retryable exceptions and non-retryable exceptions exemplified above, exception types can also be divided into business exceptions and system exceptions. Among them, system exceptions are usually caused by problems or technical failures within the system itself, such as system crashes, server outages, network failures, etc. These exceptions are usually related to aspects such as the system's hardware and software configurations, system security, and stability. System exceptions may lead to abnormal order processing, data loss, or errors, causing losses to the enterprise. Business exceptions are usually caused by errors or abnormal situations in business operations or business processes, such as incorrect order information, insufficient product inventory, invalid delivery addresses, etc. These exceptions are usually related to aspects such as the enterprise's business processes, operation specifications, and quality control. Business exceptions may lead to delayed order processing, decreased customer satisfaction, or damaged enterprise reputation.

[0038] When dealing with abnormal orders, different measures need to be taken for different types of exceptions. For system exceptions, improvements and optimizations need to be made in aspects such as strengthening the system's hardware and software configurations and enhancing the system's security and stability. For business exceptions, improvements and optimizations need to be made in aspects such as strengthening the enterprise's business processes, operation specifications, and quality control to improve the enterprise's business execution ability and service quality.

[0039] It can be understood that in some cases, the exception type is not absolute, and there may be a certain overlap between retryable exceptions and non-retryable exceptions. Therefore, when determining the exception type, multiple factors need to be comprehensively considered and judged in combination with the specific business scenario and requirements.

[0040] Step S130 , adaptively processing the target exception order belonging to the target exception type based on the target exception type selected by the target user from the exception types corresponding to the exception information and the triggering operation of the target user on the control matching the target exception type.

[0041] Controls generally refer to operable elements on the user interface, such as buttons, input boxes, drop-down menus, etc. In the OMS system, users can trigger corresponding controls to take corresponding processing measures for different types of abnormal orders.

[0042] Exemplarily, the controls in this embodiment include retry, cancel or pause, etc. Among them, for retryable exceptions, the user can resubmit the abnormal order or re-execute related operations by triggering the retry control. By retrying, the OMS system will retry to process the abnormal order in order to resolve the abnormal problem. If the user believes that the abnormal order cannot be resolved or does not need to be processed, the cancel control can be triggered to cancel the order. After cancellation, the OMS system will stop processing the abnormal order and the order will be marked as canceled. For abnormal orders that need to be temporarily stopped, the user can trigger the pause control to suspend the processing of the order. After the pause, the OMS system will stop processing the abnormal order until the user triggers the recovery control again or manually intervenes.

[0043] It is understandable that the specific controls and operation methods may vary depending on the design and implementation of the OMS system. Therefore, the specific operation and processing methods should be determined according to the actual situation of the OMS system.

[0044] In this embodiment, the OMS system's automated anomaly detection can identify abnormal orders and the abnormal information generated when abnormal orders flow through the OMS system, allowing for subsequent appropriate processing measures. This avoids manual investigation and waste of processing time, and enables target users to receive timely feedback and processing regarding abnormal orders, thereby enhancing their satisfaction with the handling of abnormal orders and, in turn, improving their loyalty and repurchase rate. By categorizing and processing abnormal information, the efficiency of abnormal order processing can be greatly improved. By promptly detecting and processing abnormal information, system failures and data errors can be prevented, thereby improving system stability and reliability.

[0045] Combine Figure 1 As described, in other embodiments of the present application, after determining the type corresponding to the exception information, it also includes: storing the abnormal order, the exception information corresponding to the abnormal order, and the exception type in an exception classification table, so that when the target user selects the target exception type from the exception types, the target exception order and exception information belonging to the target exception type are displayed to the target user, and controls matching the target exception type are displayed.

[0046] The exception classification table in this embodiment is a data table used to store exception orders, exception information, and exception types. This table can be designed as a table in a relational database, containing relevant columns and fields for storing information about exception orders and their corresponding exception types.

[0047] Further, when storing exception orders, exception information, and exception types in the exception classification table, first, the structure of the exception classification table needs to be determined, and then other operations such as inserting data, associating data, updating data, or querying data are performed. For example, according to actual requirements, design the structure of the exception classification table, including column names, data types, constraints, etc., which can also include columns such as order ID, order status, exception type, and exception information. Then insert data of exception orders, exception information, and exception types into the exception classification table. The specific insertion method depends on the database and programming language used. If the exception classification table has an association relationship with other relevant tables, such as user tables, product tables, etc., relevant data can be associated through foreign keys or other association fields for subsequent querying and processing. When the status or exception information of an exception order changes, the relevant data in the exception classification table needs to be updated further. In addition, data of exception orders, exception information, and exception types can be retrieved from the exception classification table through query statements and displayed to the target user.

[0048] It should be noted that when storing and querying the exception classification table, attention needs to be paid to issues such as data consistency, integrity, performance, and security. The processing efficiency and security of data can be improved by establishing indexes, optimizing query statements, and using database transactions.

[0049] In this embodiment, by storing exception orders, exception information, and exception types in the exception classification table, the data can be organized orderly. This structured data storage method makes the data easier to manage and query. Specifically, when the target user needs to select a target exception type from the exception types, the OMS system can quickly retrieve relevant exception orders and information from the exception classification table. Through appropriate indexing and query optimization, the query efficiency can be greatly improved, enabling the target user to quickly obtain the required data. In the exception classification table, new exception types, exception orders, and exception information can also be added conveniently without making large-scale modifications to the entire OMS system. This scalability and flexibility enable the system to adapt to possible future changes and requirements. In addition to facilitating user querying, by storing exception orders, information, and types in the database, data maintenance and management can also be carried out conveniently. For example, statistical analysis can be performed on exception data to further optimize the system or improve business processes.

[0050] Combined with Figure 1As shown, in some other embodiments of the present application, abnormal information generated when an abnormal order flows through the operation nodes of the order management system is obtained, including: through the abnormal order management interface in the order management system, abnormal information generated when an abnormal order flows through the operation nodes of the order management system within a specified time is obtained.

[0051] In the OMS, the abnormal order management interface is a specific functional module for monitoring, managing, and processing abnormal orders. This interface usually provides a series of tools and functions so that operators or administrators can identify, track, and analyze abnormal orders, thereby taking appropriate measures to solve or prevent problems.

[0052] Exemplarily, the abnormal order management interface in this embodiment has functions of abnormal detection, abnormal classification, order tracking, and data analysis. Among them, in the abnormal detection function, through real-time monitoring of order data, threshold setting, rule matching, etc., abnormal orders can be automatically or manually detected, and the abnormal order items can be identified. In the abnormal classification function, abnormal orders can be classified according to different types, such as quantity error, price error, system failure, etc. In the order tracking function, a complete historical record of the order can be provided, including the flow information in the operation nodes. In the data analysis function, the abnormal order data can be statistically analyzed to provide key indicators and trends to help managers make decisions.

[0053] Furthermore, in this embodiment, all abnormal information within a specified time is obtained through the abnormal order management interface, which can ensure the integrity and timeliness of the data. Specifically, by limiting the time range, it is possible to better understand the abnormal situations that occurred within a specific time period, thereby better analyzing problems, finding causes, and taking improvement measures. In addition, the setting of the time range also helps to compare the abnormal data in different time periods, identify trends and patterns, and provide support for future decisions.

[0054] Figure 2 The following shows a schematic flow chart of adaptively processing a target abnormal order provided by an embodiment of the present application. In Figure 1 Based on the embodiment shown, Figure 2 The embodiment shown is extended, Figure 2 The differences between the embodiment shown and Figure 1 The embodiment shown are emphasized below, and the same parts will not be elaborated.

[0055] As Figure 2 shown, in the embodiment of the present application, adaptively processing a target abnormal order belonging to a target abnormal type includes the following steps.

[0056] Step S210, determine whether the target abnormal type is a retryable abnormal type.

[0057] In the actual execution process, if the execution result of step S210 is yes, that is, the target exception type is a retryable exception, then step S220 is executed; otherwise, step S230 is executed.

[0058] In the OMS system, to determine whether the target exception type is a retryable exception, it is first necessary to clarify the definition and common types of retryable exceptions. Briefly, retryable exceptions are usually caused by temporary problems or conditions that may disappear or be resolved after a period of time, so they can be resolved by retrying. For a detailed elaboration on retryable exceptions, reference can be made to that described in the foregoing embodiments. In the OMS system, when an order has an exception, the OMS system can determine whether it belongs to a retryable exception based on the type and nature of the exception.

[0059] Furthermore, to implement the judgment and handling of retryable exceptions, the OMS system can configure corresponding retry mechanisms and strategies. For example, parameters such as the number of retries and the interval time can be set to balance the reliability and availability of the system. In addition, the OMS system should also have appropriate logging and monitoring mechanisms to facilitate tracking the handling of exceptions and the operating status of the system.

[0060] It should be noted that although retryable exceptions can be handled through the retry mechanism, in some cases, retrying may increase the burden on the system or cause other problems. Therefore, when implementing the retry mechanism, various factors need to be comprehensively considered to avoid the adverse consequences caused by excessive retrying.

[0061] Step S220: Modify the current status bit of the target exception order belonging to the retryable exception to the suspended status bit, and display a processing link.

[0062] The current status bit of the target exception order is a flag information used to describe the current status of the target exception order. The suspended status bit in this embodiment is also a flag information used to describe the current status of the target exception order. In the order management system, each order has an associated status bit to indicate the current status of the order, such as "pending processing", "paid", "cancelled", etc. When an exception order is identified as a retryable exception, the system can modify the status bit of the order to the "suspended" status bit to indicate that the order is currently in a suspended state and waiting for retry processing. By viewing the status bit of the order, the target user and the administrator can clearly understand the current status of each order and the corresponding processing method.

[0063] The purpose of step S220 is that after the target user clicks the processing link, they can enter the abnormal order management interface of the order management system to retry the target abnormal order. Here, the processing link refers to a specific link. When the target user clicks this link, they can directly enter the abnormal order management interface of the order management system. This interface usually provides detailed information and operation options for abnormal orders, including viewing the order status, retrying, etc. Through this interface, users can conveniently perform corresponding processing operations on abnormal orders.

[0064] In one implementation, if the retry processing of the target abnormal order is successful, the target abnormal order will be automatically sent to the next operation node of the operation node that generated the abnormal information in sequence. Here, the retry processing includes recall processing and / or cancellation processing.

[0065] Specifically, recall processing means restoring the abnormal order to the previous state, which involves canceling all previous operations and returning the order to the previous state. Cancellation processing means completely terminating the abnormal order and no longer performing subsequent processing, which involves marking the order as canceled and stopping all subsequent operations.

[0066] In the above implementation, the OMS system performs corresponding retry processing according to the selection of the target user. If recall processing is selected, the OMS system will revoke all previous operations and return the order to the previous state; if cancellation processing is selected, the system will stop all subsequent operations and mark the order as canceled.

[0067] After performing the retry processing, the OMS system will check whether the processing is successful. If the retry processing is successful, the OMS system will automatically send the target abnormal order to the next operation node of the operation node that generated the abnormal information. This can ensure that the order can continue to be processed until it is completed or encounters an exception again. At the next operation node, the OMS system will continue to process the order. If an exception is encountered again, the above process can be repeated; if there is no exception, the order will continue to be processed until it is completed. Through such a process, the OMS system can effectively process abnormal orders and ensure the smooth completion of orders.

[0068] In another implementation, if the retry processing of the target abnormal order fails, the pause status bit of the target abnormal order will be restored to the current status bit, and the target user will be prompted to manually send the target abnormal order to the next operation node of the operation node that generated the abnormal information in sequence.

[0069] Specifically, the OMS system will prompt the target users through the interface or the corresponding notification mechanism to inform them that the retry processing of the abnormal order has failed. Then, it will check the current status bit of the target abnormal order to confirm whether it is in the "paused" status. If it is in the "paused" status, the order status will be modified back to the original status, such as "pending processing", "paid", etc. The purpose of this step is to restore the order status to the state before the retry processing for subsequent further processing. After that, the OMS system will prompt the target users that they need to manually send it to the next operation node of the operation node where the abnormal information is generated in sequence. During this process, the OMS system usually provides the corresponding operation guide or step description to instruct the target users on how to send the abnormal order to the next operation node. Further, according to the system prompt and operation guide, the target users manually send the target abnormal order to the next operation node of the operation node where the abnormal information is generated in sequence.

[0070] Through the above steps, when the retry processing of the target abnormal order fails, the OMS system can restore the original order status and prompt the user for manual operation to ensure that the abnormal order can be correctly processed. Such a processing process can improve the accuracy and efficiency of order processing and avoid order processing delays or errors caused by system failures or abnormalities.

[0071] Step S230: Keep the current status bit of the target abnormal order belonging to the non-retryable abnormality and prompt the target user for processing.

[0072] Specifically, if the abnormality type is a non-retryable abnormality, the OMS system will keep the current status bit of the abnormal order unchanged. That is to say, the OMS system will not make any modification to the order status and keep its current status unchanged. Further, the OMS system will prompt the target user to process the abnormal order through an appropriate prompt or notification mechanism (such as pop-up window, email, SMS, etc.). The prompt information usually includes the detailed information of the abnormal order and the corresponding processing suggestions so that the user can better understand and process the abnormality.

[0073] After receiving the system prompt, the target user will take corresponding measures to process the abnormal order according to the provided abnormal information and processing suggestions. These measures include contacting the supplier, adjusting the order status, conducting return and refund, etc. The specific processing method depends on the specific situation of the abnormality and business requirements. After the target user processes the abnormal order, they will confirm the processing result and record it to track the processing situation of the abnormal order and ensure that the problem is properly solved.

[0074] In this way, when the target exception type is a non-retryable exception, the OMS system can keep the current status bit of the exception order unchanged and prompt the target user to handle it in a timely manner. The user takes corresponding measures according to the prompt of the OMS system to ensure that the exception order is properly handled, which helps to improve the accuracy and efficiency of exception order processing and reduce the losses and risks caused by order exceptions.

[0075] As described above in conjunction with Figure 1 and Figure 2 , the embodiments of the method for processing exception orders of the present application have been described in detail. Next, in conjunction with Figure 3 , the embodiments of the apparatus for processing exception orders of the present application will be described in detail. It should be understood that the description of the embodiments of the method for processing exception orders corresponds to the description of the embodiments of the apparatus for processing exception orders. Therefore, for the parts not described in detail, reference can be made to the previous method embodiments.

[0076] Figure 3 FIG. shows a schematic structural diagram of an apparatus for processing exception orders provided by an exemplary embodiment of the present application. As shown in Figure 3 , the apparatus 30 for processing exception orders provided by the embodiments of the present application includes:

[0077] An acquisition module 310, configured to acquire exception information generated when an exception order flows through operation nodes in an order management system;

[0078] A first processing module 320, configured to classify and process the exception information to determine the exception type corresponding to the exception information, where the exception type includes a retryable exception or a non-retryable exception;

[0079] A second processing module 330, configured to perform adaptive processing on a target exception order belonging to the target exception type based on the target exception type selected by the target user from the exception types corresponding to the exception information and the trigger operation of the target user on a control matching the target exception type.

[0080] In some embodiments of the present application, the second processing module 330 is further configured to, if the target exception type is a retryable exception, modify the current status bit of the target exception order belonging to the retryable exception to a suspended status bit, and display a processing link, so that after the target user clicks the processing link, the target user can enter the exception order management interface of the order management system to perform a retry operation on the target exception order, where the current status bit of the target exception order is a flag information used to describe the current state of the target exception order.

[0081] In some embodiments of the present application, the second processing module 330 is further configured to, if the retry processing on the target exception order is successful, automatically send the target exception order sequentially to the next operation node of the operation node that generates the exception information, where the retry processing includes a withdrawal process and / or a cancellation process.

[0082] In some embodiments of the present application, the second processing module 330 is further configured to, if the retry processing of the target abnormal order fails, restore the suspension status bit of the target abnormal order to the current status bit, and prompt the target user to manually issue the target abnormal order to the next operation node of the operation node that generates the abnormal information in sequence.

[0083] In some embodiments of the present application, the second processing module 330 is further configured to, if the target abnormal type is a non-retryable abnormal type, maintain the current status bit of the target abnormal order belonging to the non-retryable abnormal type, and prompt the target user to process it.

[0084] In some embodiments of the present application, the first determination module 320 is further configured to store the abnormal order, the abnormal information corresponding to the abnormal order, and the abnormal type in an abnormal classification table, so that when the target user selects the target abnormal type from the abnormal types, display the target abnormal order and abnormal information belonging to the target abnormal type to the target user, and display a control matching the target abnormal type.

[0085] In some embodiments of the present application, the acquisition module 310 is further configured to obtain, through the abnormal order management interface in the order management system, the abnormal information generated when the abnormal order flows through the operation nodes of the order management system within a specified time.

[0086] Next, refer to Figure 4 to describe the electronic device according to the embodiments of the present application. Figure 4 The following shows a schematic structural diagram of an electronic device provided by an exemplary embodiment of the present application.

[0087] As Figure 4 shown, the electronic device 40 includes one or more processors 401 and a memory 402.

[0088] The processor 401 may be a central processing unit (CPU) or other form of processing unit with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 40 to perform desired functions.

[0089] The memory 402 may include one or more computer program products, and the computer program products may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory, etc. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage media, and the processor 401 may run the program instructions to implement the abnormal order processing method of each embodiment of the present application described above and / or other desired functions. Various contents such as abnormal information, abnormal types, abnormal orders, etc. may also be stored in the computer-readable storage media.

[0090] In one example, the electronic device 40 may further include: an input device 403 and an output device 404, and these components are interconnected through a bus system and / or other forms of connection mechanisms (not shown).

[0091] The input device 403 may include, for example, a keyboard, a mouse, and the like.

[0092] The output device 404 may output various information to the outside, including abnormal information, abnormal types, abnormal orders, etc. The output device 404 may include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.

[0093] Of course, for simplicity, Figure 4 only some of the components related to the present application in the electronic device 40 are shown, and components such as a bus, an input / output interface, etc. are omitted. In addition, according to specific application scenarios, the electronic device 40 may further include any other appropriate components.

[0094] In addition to the above methods and devices, the embodiments of the present application may also be computer program products, which include computer program instructions that, when run by a processor, cause the processor to execute the steps in the abnormal order processing method according to various embodiments of the present application described above in this specification.

[0095] The computer program product may be written in any combination of one or more programming languages for executing the program code of the operations of the embodiments of the present application. The programming languages include object-oriented programming languages such as Java, C++, etc., and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, executed as a stand-alone software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0096] In addition, an embodiment of the present application may also be a computer-readable storage medium having computer program instructions stored thereon. When the computer program instructions are run by a processor, the processor is caused to execute the steps in the abnormal order processing method according to various embodiments of the present application described above in this specification.

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

[0098] The basic principles of the present application have been described above in conjunction with specific embodiments. However, it should be noted that the advantages, benefits, effects, etc. mentioned in the present application are only examples and not limitations, and it cannot be considered that these advantages, benefits, effects, etc. are essential for each embodiment of the present application. In addition, the above-disclosed specific details are only for the purposes of illustration and easy understanding, and not for limitation. The above details do not limit the present application to necessarily adopt the above specific details for implementation.

[0099] The block diagrams of the devices, apparatuses, equipment, and systems involved in the present application are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, equipment, and systems can be connected, arranged, and configured in any manner. Words such as "comprising," "including," "having," etc. are open-ended terms that mean "including but not limited to" and can be used interchangeably with each other. The word "or" and "and" used herein refer to the word "and / or" and can be used interchangeably with it, unless the context clearly indicates otherwise. The phrase "such as" used herein refers to the phrase "such as but not limited to" and can be used interchangeably with it.

[0100] It should also be noted that in the devices, equipment, and methods of the present application, each component or each step can be decomposed and / or recombined. These decompositions and / or recombinations should be regarded as equivalent solutions of the present application.

[0101] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects without departing from the scope of the present application. Therefore, the present application is not intended to be limited to the aspects shown herein, but rather to the broadest scope consistent with the principles and novel features disclosed herein.

[0102] The above description has been given for purposes of illustration and description. In addition, this description is not intended to limit the embodiments of the present application to the forms disclosed herein. Although multiple example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions, and sub-combinations thereof.

Claims

1. An abnormal order processing method, characterized in that, Applied to an order management system, the method includes: Obtaining exception information generated when an exception order flows through the operation nodes in the order management system; Classifying and processing the exception information to determine the exception type corresponding to the exception information, where the exception type includes retryable exceptions or non-retryable exceptions; Based on the target exception type selected by the target user from the exception types corresponding to the exception information, and the trigger operation of the target user on the control matching the target exception type, adaptively process the target exception order belonging to the target exception type.

2. The abnormal order processing method according to claim 1, wherein The adaptively processing the target exception order belonging to the target exception type includes: If the target exception type is a retryable exception, modify the current status bit of the target exception order belonging to the retryable exception to a suspended status bit, and display a processing link, so that after the target user clicks the processing link, enter the exception order management interface of the order management system to retry the target exception order, where the current status bit of the target exception order is flag information used to describe the current state of the target exception order.

3. The abnormal order processing method according to claim 2, wherein It further includes: If the retry processing of the target exception order is successful, automatically send the target exception order to the next operation node of the operation node that generated the exception information in sequence, where the retry processing includes withdrawal processing and / or cancellation processing.

4. The abnormal order processing method according to claim 2, wherein It further includes: If the retry processing of the target exception order fails, restore the suspended status bit of the target exception order to the current status bit, and prompt the target user to manually send the target exception order to the next operation node of the operation node that generated the exception information in sequence.

5. The abnormal order processing method according to any one of claims 1 to 4, characterized in that The adaptively processing the target exception order belonging to the target exception type includes: If the target exception type is a non-retryable exception, keep the current status bit of the target exception order belonging to the non-retryable exception, and prompt the target user to process it.

6. The abnormal order processing method according to any one of claims 1 to 4, characterized in that, After determining the exception type corresponding to the exception information, it further includes: Storing the exception order, the exception information corresponding to the exception order, and the exception type in an exception classification table, so that when the target user selects the target exception type from the exception types, display the target exception order and exception information belonging to the target exception type to the target user, and display the control matching the target exception type.

7. The abnormal order processing method according to any one of claims 1 to 4, characterized in that The obtaining the exception information generated when the exception order flows through the operation nodes in the order management system includes: Through the exception order management interface in the order management system, obtain the exception information generated when the exception order flows through the operation nodes in the order management system within a specified time.

8. An abnormal order management device, characterized in that, Applied to an order management system, the device includes: An obtaining module, configured to obtain exception information generated when an exception order flows through the operation nodes in the order management system; A first processing module, configured to classify and process the exception information to determine the exception type corresponding to the exception information, where the exception type includes retryable exceptions or non-retryable exceptions; A second processing module, configured to perform an adaptive processing on a target exception order belonging to the target exception type based on the target exception type selected by the target user from the exception types corresponding to the exception information, and a trigger operation of the target user on a control matching the target exception type.

9. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, and the computer program is used to execute the exception order processing method according to any one of claims 1 to 7 above.

10. An electronic device, characterized in that, Comprising: A processor; A memory for storing executable instructions of the processor; The processor is configured to execute the exception order processing method according to any one of claims 1 to 7 above.

Images