Express report data statistics method and device

Abstract

The present application discloses a method and device for express report data statistics, which relates to the technical field of data processing. The method comprises: obtaining a waybill report within a historical time period; for each waybill data in the waybill report, detecting whether the waybill corresponding to the waybill data is a co-distributed waybill; and updating the waybill statistical data corresponding to the waybill according to the detection result. The problem in the prior art that after the waybill in the co-distributed area is issued to a third party, there will be data omissions, incomplete marking of co-distributed waybill marks, and incomplete data in the actual operation links such as arrival, delivery, and signing of the outlets, which will result in repeated calculations and inaccurate data report statistics, affecting the express headquarters' control over the co-distribution business and business decision-making. Statistics can be performed for each co-distributed waybill to ensure the accuracy of the data.

Description

Technical Field

[0001] The present application relates to the technical field of data processing, and in particular to a method and device for statistically analyzing express report data. Background Art

[0002] my country has grown into the world's fastest-growing and most dynamic emerging express delivery market, with parcel express volume exceeding the total of developed economies such as the United States, Japan, and Europe. With years of rapid growth, the express delivery industry has become an important infrastructure for Chinese cities.

[0003] However, due to the uneven economic development in various regions, the operation of many grassroots outlets has not kept up with the rapid development of the industry. Especially in remote areas, due to the backward economy and population base, the increase in express delivery orders is still difficult to guarantee the survival of outlets and practitioners. Under the increasingly fierce competition from multiple express delivery companies, the delivery fees continue to decline, resulting in a decrease in the income of front-line outlets and salesmen, and strikes, bankruptcies, and transfers are emerging in an endless stream. This has given rise to a new format of joint delivery of terminal express delivery. The terminal outlets develop in groups and jointly deliver, allowing express delivery to enter the village better. The joint distribution of terminal outlets solves the problem that the density of express delivery in villages and towns is not large enough, and if a single express brand builds a channel alone, the cost is high and the efficiency is low.

[0004] For the express headquarters, the assessment and management of the terminal shared distribution outlets also brings new challenges. The original business statistical methods and assessment indicators need to be innovated to adapt to the characteristics of the shared distribution business. Since the shared distribution business involves the participation of third parties, if the traditional report statistics method is used, there will be data omissions and incomplete marking of shared distribution orders for the waybills issued to the third parties in the shared distribution area, as well as incomplete data on the actual operations of the outlets such as delivery, signing, etc., which will result in repeated calculations and inaccurate data report statistics, affecting the express headquarters' control over the shared distribution business and business decision-making. Summary of the invention

[0005] The purpose of this application is to provide a method and device for express report data statistics, which is used to solve the problems in the prior art that after the waybill in the shared distribution area is issued to a third party, there will be data omissions, incomplete marking of shared distribution orders, and incomplete data in the actual operation links such as arrival, delivery, and signing of the outlets, which will cause repeated calculations and inaccurate data report statistics, affecting the express headquarters' control over the shared distribution business and business decision-making.

[0006] The purpose of this application is achieved by the following technical solutions:

[0007] In a first aspect, the present application provides a method for collecting express report data, the method comprising:

[0008] Get waybill reports within the historical time period;

[0009] For each waybill data in the waybill report, detecting whether the waybill corresponding to the waybill data is a shared waybill;

[0010] According to the detection result, the waybill statistical data corresponding to the waybill is updated.

[0011] By obtaining waybill reports within the historical time period; for each waybill data in the waybill report, detect whether the waybill corresponding to the waybill data is a co-distributed order; based on the detection result, update the waybill statistical data corresponding to the waybill. This solves the problem in the prior art that after waybills in co-distributed areas are issued to third parties, data omissions and incomplete co-distributed order markings will occur, as well as incomplete data in the actual operations of receiving, delivering, and signing for items at outlets, which will result in repeated calculations and inaccurate data report statistics, affecting the express headquarters' control over the co-distribution business and business decision-making. Statistics can be performed on each co-distributed order to ensure data accuracy.

[0012] Optionally, the detecting whether the waybill corresponding to the waybill data is a shared waybill includes:

[0013] Determine the target node where the waybill is currently located; the target node is an initial node or an actual operation node, the initial node is a node for receiving the express, and the actual operation node is each node in the transportation process after receiving the express;

[0014] Detecting whether the waybill is a shared waybill;

[0015] The updating of the waybill statistics data corresponding to the waybill according to the detection result includes:

[0016] According to the detection result and the target node, the waybill statistical data corresponding to the waybill is updated.

[0017] By updating the waybill statistics corresponding to the waybill according to the detection result of the co-matching order and the currently described target node, the accuracy of the waybill data obtained by statistics is further improved.

[0018] Optionally, the detecting whether the waybill corresponding to the waybill data is a shared waybill includes:

[0019] Detecting whether there is a co-distribution mark on the waybill;

[0020] If it exists, it is determined that the waybill is a shared waybill;

[0021] If it does not exist, it is determined that the waybill is a non-shared waybill.

[0022] By detecting whether there is a co-distribution mark on the waybill, whether it is a co-distribution waybill is detected, the detection efficiency of the waybill and the accuracy of the detection results are improved, thereby further improving the accuracy of the waybill data obtained by statistics.

[0023] Optionally, updating waybill statistics corresponding to the waybill according to the detection result and the target node includes:

[0024] When the waybill is a shared order and the target node where the waybill is currently located is the initial node, the total number of waybills is increased by 1, the total number of shared orders is increased by 1, the total number of waybills at the initial node is increased by 1, and the total number of shared orders at the initial node is increased by 1.

[0025] The above scheme can be used to accurately count the shared waybills of the initial node, avoiding the omission or duplication of such waybills, which would lead to incorrect waybill data statistics, thereby achieving the effect of improving the accuracy of data statistics.

[0026] Optionally, updating waybill statistics corresponding to the waybill according to the detection result and the target node includes:

[0027] When the waybill is a non-shared waybill and the target node where the waybill is currently located is the initial node, the total number of waybills is increased by 1, and the total number of waybills at the initial node is increased by 1.

[0028] The above scheme can be used to accurately count the non-shared waybills of the initial node, avoiding the omission or repeated counting of such waybills, which would lead to incorrect waybill data statistics, thereby achieving the effect of improving the accuracy of data statistics.

[0029] Optionally, updating waybill statistics corresponding to the waybill according to the detection result and the target node includes:

[0030] When the waybill is a shared waybill and the target node of the waybill is currently an operational node, querying the initial node corresponding to the waybill;

[0031] If the initial node corresponding to the waybill is found, then check whether the found initial node is marked as a shared waybill;

[0032] If the initial node queried is not marked as a shared order, the total number of shared orders on the creation date corresponding to the queried initial node will be increased by 1, the total number of shared orders of the actual operation node will be increased by 1, the total number of waybills of the actual operation node will be increased by 1, and the number of additional shared orders marked will be increased by 1.

[0033] When the current node is an actual operation node, the initial node corresponding to the actual operation node is continuously detected, and different data processing is performed according to different detection results, thereby ensuring the accuracy of data statistics.

[0034] Optionally, the method further includes:

[0035] If the initial node corresponding to the waybill is not found, check whether the waybill exists in the express distribution scanning record;

[0036] If the waybill exists in the distribution scanning record, the total number of shared orders on the scanning date of the distribution scanning record shall be increased by 1, the total number of shared orders at the actual operation node shall be increased by 1, the total number of waybills at the actual operation node shall be increased by 1, the number of supplementary shared order marks shall be increased by 1, and the total number of waybills shall be increased by 1.

[0037] When the current target node is the actual operation node, the system continues to detect whether the waybill exists in the initial node corresponding to the actual operation node and the distribution scanning record, and then performs different data processing according to different detection results, thereby ensuring the accuracy of data statistics.

[0038] Optionally, updating waybill statistics corresponding to the waybill according to the detection result and the target node includes:

[0039] When the waybill is a non-shared waybill and the node where the waybill is currently located is an actual operation node, query the initial node corresponding to the waybill;

[0040] If the initial node corresponding to the waybill is not found, check whether the waybill exists in the distribution scanning record;

[0041] If the waybill exists in the distribution scanning record, the total number of waybills on the scanning date of the distribution scanning record is increased by 1, and the total number of waybills at the actual operation node is increased by 1.

[0042] When the current node is an actual operation node, the system continues to detect whether the waybill exists in the initial node corresponding to the actual operation node and the distribution scanning record, and then performs different data processing according to different detection results, thereby ensuring the accuracy of data statistics.

[0043] Optionally, before obtaining the waybill report within the historical time period, the process further includes:

[0044] Set up scheduled tasks;

[0045] The method of obtaining the waybill report within the historical time period includes:

[0046] When the time of the scheduled task arrives, the waybill report within the historical time period is obtained.

[0047] By setting up scheduled tasks, you can automatically perform data statistics for express reports when the scheduled time arrives, ensuring efficient and accurate data statistics.

[0048] In a second aspect, the present application provides a courier report data statistics device, the device comprising:

[0049] Report acquisition module, used to obtain waybill reports within the historical time period;

[0050] A co-matching detection module, used for detecting, for each waybill data in the waybill report, whether the waybill corresponding to the waybill data is a co-matching waybill;

[0051] The data updating module is used to update the waybill statistical data corresponding to the waybill according to the detection result.

[0052] Optionally, the co-matching detection module is used to:

[0053] Determine the target node where the waybill is currently located; the target node is an initial node or an actual operation node, the initial node is a node for receiving the express, and the actual operation node is each node in the transportation process after receiving the express;

[0054] Detecting whether the waybill is a shared waybill;

[0055] The data updating module is used for:

[0056] According to the detection result and the target node, the waybill statistical data corresponding to the waybill is updated.

[0057] Optionally, the co-matching detection module is used to:

[0058] Detecting whether there is a co-distribution mark on the waybill;

[0059] If it exists, it is determined that the waybill is a shared waybill;

[0060] If it does not exist, it is determined that the waybill is a non-shared waybill.

[0061] Optionally, the data updating module is used to:

[0062] When the waybill is a shared order and the target node where the waybill is currently located is the initial node, the total number of waybills is increased by 1, the total number of shared orders is increased by 1, the total number of waybills at the initial node is increased by 1, and the total number of shared orders at the initial node is increased by 1.

[0063] Optionally, the data updating module is used to:

[0064] When the waybill is a non-shared waybill and the target node where the waybill is currently located is the initial node, the total number of waybills is increased by 1, and the total number of waybills at the initial node is increased by 1.

[0065] Optionally, the data updating module is used to:

[0066] When the waybill is a shared waybill and the target node of the waybill is currently an operational node, querying the initial node corresponding to the waybill;

[0067] If the initial node corresponding to the waybill is found, then check whether the found initial node is marked as a shared waybill;

[0068] If the initial node queried is not marked as a shared order, the total number of shared orders on the creation date corresponding to the queried initial node will be increased by 1, the total number of shared orders of the actual operation node will be increased by 1, the total number of waybills of the actual operation node will be increased by 1, and the number of additional shared orders marked will be increased by 1.

[0069] Optionally, the data updating module is used to:

[0070] If the initial node corresponding to the waybill is not found, check whether the waybill exists in the express distribution scanning record;

[0071] If the waybill exists in the distribution scanning record, the total number of shared orders on the scanning date of the distribution scanning record shall be increased by 1, the total number of shared orders at the actual operation node shall be increased by 1, the total number of waybills at the actual operation node shall be increased by 1, the number of supplementary shared order marks shall be increased by 1, and the total number of waybills shall be increased by 1.

[0072] Optionally, the data updating module is used to:

[0073] When the waybill is a non-shared waybill and the target node where the waybill is currently located is an actual operation node, query the initial node corresponding to the waybill;

[0074] If the initial node corresponding to the waybill is not found, check whether the waybill exists in the distribution scanning record;

[0075] If the waybill exists in the distribution scanning record, the total number of waybills on the scanning date of the distribution scanning record is increased by 1, and the total number of waybills at the actual operation node is increased by 1.

[0076] Optionally, the report acquisition module is used to

[0077] Set up scheduled tasks;

[0078] When the time of the scheduled task arrives, the waybill report within the historical time period is obtained.

[0079] In a third aspect, the present application provides an electronic device, comprising a memory and a processor, wherein the memory stores at least one program instruction, and the processor implements the method described in the first aspect by loading and executing the at least one program instruction.

[0080] In a fourth aspect, the present application provides a computer storage medium, wherein at least one program instruction is stored in the computer storage medium, and the at least one program instruction is loaded and executed by a processor to implement the above-described method.

[0081] Compared with the prior art, the technical effects of this application include:

[0082] By obtaining waybill reports within the historical time period; for each waybill data in the waybill report, detect whether the waybill corresponding to the waybill data is a co-distributed order; based on the detection result, update the waybill statistical data corresponding to the waybill. This solves the problem in the prior art that after waybills in co-distributed areas are issued to third parties, data omissions and incomplete co-distributed order markings will occur, as well as incomplete data in the actual operations of receiving, delivering, and signing for items at outlets, which will result in repeated calculations and inaccurate data report statistics, affecting the express headquarters' control over the co-distribution business and business decision-making. Statistics can be performed on each co-distributed order to ensure data accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0083] The present application is further described below in conjunction with the accompanying drawings and embodiments.

[0084] Figure 1 It is a method flow chart of the express report data statistics method provided in the embodiment of the present application;

[0085] Figure 2 It is a method flow chart of another express report data statistics method provided by an embodiment of the present application;

[0086] Figure 3 A specific flow chart for detecting whether a waybill is a shared waybill provided in an embodiment of the present application;

[0087] Figure 4 It is a method flow chart of another express report data statistics method provided by an embodiment of the present application;

[0088] Figure 5 It is a method flow chart of another express report data statistics method provided by an embodiment of the present application;

[0089] Figure 6 It is a flow chart of a method for updating the waybill statistics data corresponding to the waybill provided in an embodiment of the present application;

[0090] Figure 7 It is a flow chart of another method for updating the waybill statistics data corresponding to the waybill provided in an embodiment of the present application;

[0091] Figure 8 It is a method flow chart of another express report data statistics method provided by an embodiment of the present application;

[0092] Fig. 9 It is a method flow chart of another express report data statistics method provided by an embodiment of the present application;

[0093] Fig.10 It is a structural schematic diagram of the express report statistics device provided in an embodiment of the present application;

[0094] Fig.11 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application;

[0095] Fig.12 It is a structural diagram of a program product for implementing a method for statistics of express report data provided in an embodiment of the present application. DETAILED DESCRIPTION

[0096] Below, the present application is further described in conjunction with the accompanying drawings and specific implementation methods. It should be noted that, under the premise of no conflict, the various embodiments or technical features described below can be arbitrarily combined to form a new embodiment.

[0097] First, for ease of understanding, a brief introduction to the application scenarios involved in this application is given.

[0098] The express waybill is generated after the courier receives the express order, and then it is transported to the recipient through outbound scanning, warehouse printing order, warehouse processing, warehouse outbound, loading scanning, distribution scanning, dispatch scanning, etc., among which the node where the courier places the order is the initial node of the waybill, and each subsequent node is the actual operation node of the waybill. That is, the initial node is the node for collecting the express, and the actual operation node is the node in the transportation process after collecting the express. Since there are multiple actual operation nodes in the operation during the transportation process, there can also be multiple corresponding ones, and according to the classification standards of different express companies, the number of actual operation nodes of the waybill data corresponding to each express company can be the same or different. Take 9 actual operation nodes as an example, the initial node can be represented as 00, and the actual operation nodes can be represented as 01 node-09 node in sequence according to the order in the logistics process. If there are 15 actual operation nodes, each actual operation node can be represented as 01 node-15 node according to the operation order in the logistics process, and this embodiment does not limit this.

[0099] In the logistics process, at each node, the operator will scan each express. When the operator finds that the scanned waybill is a shared order, that is, when it is determined that the waybill corresponding to a certain waybill data is a shared order, the operator can mark the waybill as a shared order, and, in actual implementation, when it is marked as a shared order at the 00 node, it can be marked by GP, and when it is marked as a shared order at the actual operation node, it can be marked by GPSC. That is to say, when a certain waybill is set with a corresponding GP mark or GPSC mark, it can be judged that the waybill is a shared order. For example, after a certain express is transported to a township and scanned during delivery, the scanner finds that the area where the recipient of the waybill is located belongs to the shared order area, then the waybill can be marked with the GPSC shared order mark. For another example, a villager in a mountainous area sends a courier, and the courier can mark the waybill of the courier as GP after receiving the courier. In actual implementation, during the data storage process, the GP tag can be stored as 1, the GPSC tag can be stored as 2, and non-shared orders can be stored as 0. That is to say, 0, 1 and 2 can be used to distinguish whether each waybill is a shared order, and when the waybill is a shared order, whether it is marked as a shared order at the initial node or at the actual operation node.

[0100] In addition, in order to understand their own express delivery volume and make corresponding adjustments or decisions, express delivery companies usually count their own express delivery waybills. For example, they count the total data of all waybills, the total number of shared orders, the total number of waybills at each node, the total number of shared orders at each node, the amount of supplementary marking for shared orders at each node, the total number of actual operation nodes, etc. Therefore, in order to facilitate the subsequent description, the various variables that may be involved in the future are first represented, as shown in Table 1.

[0101] Table 1

[0102]

[0103]

[0104] Based on the above scenario, this application provides a statistical method for express report data. Figure 1 , which shows a method flow chart of a method for statistically analyzing express report data provided by an embodiment of the present application, such as Figure 1 As shown, the method includes:

[0105] Step 101, obtaining a waybill report within a historical time period;

[0106] The historical time period can be a system default time period, or a user-defined time period according to personal needs. In a possible embodiment, the historical time period can be the time period between 00:00:00 of the Nth day in history and 00:00:00 of the N-1st day in history. Wherein, N is an integer greater than 1. Moreover, the above only takes the acquisition of the waybill report of the history of 1 day as an example. In actual implementation, it can also be acquired in units of 2 days or 5 days. For example, taking the acquisition of the waybill report of 2 days as an example, the historical time period can be the time period between 00:00:00 of the Nth day in history and 00:00:00 of the N-2nd day in history. N is an integer greater than 2, and this embodiment does not limit this.

[0107] The waybill report may include the waybill number, generation time, time of each node in the logistics process, current node, next node, co-distribution mark, and remarks, etc. Optionally, the waybill report may be read from a database. Furthermore, the database may be a local database or a cloud database.

[0108] For example, please refer to Table 2, which shows a possible waybill report including n waybill data.

[0109] Table 2

[0110]

[0111] It should be noted that obtaining the waybill report within the historical time period may include: obtaining the waybill report including the waybill data of each waybill whose status has changed within the historical time period.

[0112] Step 102: for each waybill data in the waybill report, detecting whether the waybill corresponding to the waybill data is a shared waybill;

[0113] Step 103: Update the waybill statistics corresponding to the waybill according to the detection result.

[0114] In summary, by obtaining waybill reports within the historical time period; for each waybill data in the waybill report, detect whether the waybill corresponding to the waybill data is a co-distributed order; based on the detection result, update the waybill statistical data corresponding to the waybill. This solves the problem in the prior art that after waybills from co-distributed areas are issued to third parties, data omissions and incomplete co-distributed order markings will occur, as well as incomplete data in the actual operations of receiving, delivering, and signing for items at outlets, which will result in repeated calculations and inaccurate statistics in data reports, affecting the express headquarters' control over the co-distribution business and business decision-making. Statistics can be performed on each co-distributed order to ensure data accuracy.

[0115] It should be noted that in the above embodiments, please refer to Figure 2 , step 102 may include:

[0116] Step 1021, determining the target node where the waybill is currently located; the target node is an initial node or an actual operation node, the initial node is a node for receiving the express, and the actual operation node is each node in the transportation process after receiving the express;

[0117] For each waybill data in the waybill report, the target node where the waybill is currently located can be determined based on the waybill data. For example, if it is detected that the waybill is currently in the distribution node, it can be determined that the waybill is currently in the 05 node corresponding to the distribution node. For another example, if it is detected that the waybill is currently in the loading node, it can be determined that the waybill is currently in the 01 node corresponding to the loading node.

[0118] Step 1022, detecting whether the waybill is a shared waybill;

[0119] Optional, please refer to Figure 3 , step 1022 comprises:

[0120] Step 10221: Check whether the waybill has a co-distribution mark;

[0121] For example, check whether there is a GP mark or GPSC mark on the waybill.

[0122] Step 10222: If it exists, determine that the waybill is a shared waybill;

[0123] When there is a corresponding GP mark or GPSC mark, it can be determined that the waybill is a shared waybill.

[0124] For example, for the waybill corresponding to the first waybill data in Table 2, it can be determined based on the waybill data that the waybill has a corresponding shared bill flag GP, and therefore, it can be determined that the waybill is a shared bill.

[0125] Step 10223: If it does not exist, determine that the waybill is a non-shared waybill.

[0126] On the contrary, if the waybill does not have the corresponding GP mark or GPSC mark, it can be determined that the waybill is a non-shared waybill. For example, for the waybill corresponding to the nth waybill data in Table 2, it can be determined based on the waybill data that the waybill does not have the corresponding shared waybill mark GP or GPSC, so it can be determined that the waybill is a non-shared waybill.

[0127] In actual implementation, if a non-shared bill is marked with 0, a shared bill marked with 1 at the initial node, and a shared bill marked with 2 at the actual operation node, it is possible to detect whether the bill is marked with 1 or 2. The above only uses 0, 1, and 2 as examples for marking. Optionally, it can also be marked with two levels of labels. For example, a shared bill is marked with 1, and a non-shared bill is marked with 0. Among the shared bills, the one marked at the initial node is marked with GP, and the one marked at the actual operation node is marked with GPSC. At this time, when the bill is a shared bill, is_public_deliver = 1, and if the bill is a non-shared bill, is_public_deliver = 0.

[0128] Correspondingly, step 103 includes: updating the waybill statistical data corresponding to the waybill according to the detection result and the target node.

[0129] After detecting whether the waybill is a shared order and determining the current target node, the waybill statistical data corresponding to the waybill can be updated according to the detection result and the target node.

[0130] In actual implementation, since the detection result can be whether the waybill is a shared order or a non-shared order, the target node can be the initial node or the actual operation node, that is, the detection result and the target node can have four combinations. The first is that the waybill is a shared order and the target node is the initial node; the second is that the waybill is a non-shared order and the target node is the initial node; the third is that the waybill is a shared order and the target node is the actual operation node; the fourth is that the waybill is a non-shared order and the target node is the actual operation node. For each of the above situations, the update method of the waybill statistical data corresponding to the waybill is different. Therefore, the following will separately introduce each of the above situations in detail.

[0131] In the first possible implementation, when the waybill is a shared order and the target node is the initial node, please refer to Figure 4 , the step of updating the waybill statistics data includes: adding 1 to the total waybill quantity, adding 1 to the total number of all-matched orders, adding 1 to the total waybill quantity of the initial node, and adding 1 to the total number of all-matched orders of the initial node. That is, when the node where the waybill is located is the 00 node and is_public_deliver=1, the value of the total data quantity=total_cnt+1; the value of the total number of 00 node orders=order_cnt+1; the value of the total number of all-matched orders=public_cnt+1; the value of the total number of 00 node all-matched orders=order_public_cnt+1.

[0132] The above scheme can be used to accurately count the shared waybills of the initial node, avoiding the omission or duplication of such waybills, which would lead to incorrect waybill data statistics, thereby achieving the effect of improving the accuracy of data statistics.

[0133] In the second possible implementation, if the waybill is not a shared order, the target node is the initial node. Please refer to Figure 5 , the step of updating the waybill statistics includes: adding 1 to the total waybill amount, and adding 1 to the total waybill amount of the initial node. That is, when the node where the waybill is currently located is the 00 node and is_public_deliver=0, the value of the total data amount=total_cnt+1; the value of the total order amount of the 00 node=order_cnt+1.

[0134] The above scheme can be used to accurately count the non-shared waybills of the initial node, avoiding the omission or repeated counting of such waybills, which would lead to incorrect waybill data statistics, thereby achieving the effect of improving the accuracy of data statistics.

[0135] In the third possible implementation, when the waybill is a shared order and the target node is an operation node, please refer to Figure 6 The step of updating the waybill statistics data, i.e., step 103, includes:

[0136] Step 1031, querying the initial node corresponding to the waybill;

[0137] When the current node is any node from 01 to 09 and is_public_deliver=1, query the 00 node corresponding to the waybill according to the waybill number. Optionally, query the 00 node corresponding to the waybill number in the waybill report.

[0138] For example, the current node is node 03, which is the initial node for querying the waybill in the waybill data of the waybill.

[0139] Step 1032: if the initial node corresponding to the waybill is found, then check whether the found initial node is marked as a shared waybill;

[0140] If the 00 node corresponding to the order number can be found, continue to check whether the waybill is marked as a shared order at the 00 node. The detection method for detecting whether it is a shared order is similar to the detection method described above, that is, to detect whether there is a corresponding GP mark at the 00 node. If so, it is determined that the waybill is marked as a shared order at the 00 node. If not, it is determined that the waybill is not marked as a shared order at the 00 node.

[0141] Step 1033, if the queried initial node is not marked as a shared order, then the total number of shared orders on the creation date corresponding to the queried initial node is increased by 1, the total number of shared orders of the actual operation node is increased by 1, the total number of waybills of the actual operation node is increased by 1, and the number of additional shared orders marked is increased by 1.

[0142] If the is_public_delivery of the queried 00 node is 0, that is, the waybill is not marked as a shared order at the 00 node, at this time, since the waybill is a shared order at the target node, in order to ensure accuracy, the waybill needs to be reprinted as a shared order at the 00 node. Therefore, the server can add 1 to the total amount of shared orders on the creation date corresponding to the queried initial node, the total amount of shared orders of the actual operation node, the total amount of waybills of the actual operation node, and the number of reprinted shared order marks. That is, the value of the total amount of shared orders on the day of the creation time (crt_time) of the 00 node = public_cnt+1; the value of the actual operation reprinted mark = oper_public_cnt+1; the total amount of data of the corresponding node (01-09) +1; the number of shared orders of the corresponding node (01-09) +1. For example, still taking the current node as the 03 node as an example, the total amount of data of the 03 node can be +1, and the number of shared orders of the 03 node can be +1.

[0143] Step 1034: if the queried initial node is marked as a shared order, it will not be processed.

[0144] If is_public_delivery=1 of the queried 00 node, that is, the waybill has been marked as a shared delivery order at the 00 node, it means that the waybill has been processed before and will not be processed and counted again.

[0145] Step 1035: If the initial node corresponding to the waybill is not found, check whether the waybill exists in the express distribution scanning record;

[0146] During the transportation process, the express delivery is usually scanned by the scanning personnel at each node, so that the problems can be directly determined at which nodes, so as to prepare for the subsequent query of logistics progress or the query of lost items. If the initial node corresponding to the waybill is not found, the server can continue to check whether the waybill exists in the express distribution scanning record according to the waybill number.

[0147] Step 1036, if the waybill exists in the distribution scanning record, then the total number of shared orders on the scanning date of the distribution scanning record is increased by 1, the total number of shared orders at the actual operation node is increased by 1, the total number of waybills at the actual operation node is increased by 1, the number of supplementary shared order marks is increased by 1, and the total number of waybills is increased by 1.

[0148] If the detection result is that the waybill exists in the distribution scan record, then the date of the distribution scan record of the waybill can be determined first, and the waybill can be counted in the statistical table of that date. The statistical content includes adding 1 to the total amount of shared orders on the scanning date of the distribution scan record, adding 1 to the total amount of shared orders of the actual operation node, adding 1 to the total amount of waybills of the actual operation node, adding 1 to the number of supplementary shared order marks, and adding 1 to the total amount of waybills. That is, the value of the total amount of data = total_cnt+1; the value of the total amount of shared orders = public_cnt+1; the value of the actual operation supplementary mark = oper_public_cnt+1; the total amount of data of the corresponding node (01-09) +1; the number of shared orders of the corresponding node (01-09) +1.

[0149] Step 1037: If the detection result is that the waybill does not exist in the distribution scanning record, it will not be processed. At this time, the processing of the waybill is completed and the next waybill will be processed.

[0150] When the current node is an actual operation node, the system continues to detect whether the waybill exists in the initial node corresponding to the actual operation node and the distribution scanning record, and then performs different data processing according to different detection results, thereby ensuring the accuracy of data statistics.

[0151] In the fourth possible implementation, when the waybill is a non-shared order and the target node is an operational node, please refer to Figure 7 The step of updating the waybill statistics data, i.e., step 103, includes:

[0152] Step 1031', querying the initial node corresponding to the waybill;

[0153] Optionally, similar to the above steps, the initial node corresponding to the express waybill can be queried according to the express waybill report, which will not be repeated here.

[0154] Step 1032', if the initial node corresponding to the waybill is not found, check whether the waybill exists in the distribution scanning record;

[0155] During the transportation process, the express delivery is usually scanned by the scanner at each node, so that the problem can be determined intuitively at which nodes the express delivery has occurred for subsequent inquiries. If the initial node corresponding to the waybill is not found, the server can continue to check whether the waybill exists in the express distribution scanning record based on the waybill number.

[0156] Step 1033': if the waybill exists in the distribution scanning record, the total number of waybills on the scanning date of the distribution scanning record is increased by 1, and the total number of waybills at the actual operation node is increased by 1.

[0157] If the query result shows that the waybill exists in the distribution scan record, the scan date of the waybill in the distribution scan record is determined, and the waybill is counted in the statistical table of that date. The statistical data includes adding 1 to the total number of waybill on the scan date and the total number of waybill at the actual operation node. That is, the total amount of data in the statistical report at that time = total_cnt+1, and the total amount of data of the corresponding node (01-09) +1;

[0158] Step 1034', if the waybill does not exist in the distribution scan record, no processing will be performed at this time.

[0159] Step 1035': if the initial node corresponding to the waybill is found, no processing is performed.

[0160] When the current node is an actual operation node, the system continues to detect whether the waybill exists in the initial node corresponding to the actual operation node and the distribution scanning record, and then performs different data processing according to different detection results, thereby ensuring the accuracy of data statistics.

[0161] It should be noted that each step can be executed by the server under the user's trigger, or it can be executed automatically according to the scheduled task. When it is executed automatically according to the scheduled task, please refer to Figure 8 Before the step of obtaining the waybill report within the historical time period, the method further includes:

[0162] Step 100, setting a scheduled task;

[0163] The user can set it in the terminal, for example, set it to get the waybill report between 00:00:00 of the Nth day and 00:00:00 of the N-1st day at 00:00 every day on the computer. For another example, set it to get the waybill report between 00:00:00 of the Nth day and 00:00:00 of the N-1st day at 12:00 every day, which will not be repeated here. After the user submits his settings, the server can receive the user's settings accordingly and set the scheduled tasks according to the user's settings.

[0164] Step 101 includes:

[0165] When the time of the scheduled task arrives, the waybill report within the historical time period is obtained.

[0166] After that, the server can execute the scheduled tasks according to the settings. For example, at 00:00 every day, the waybill report between 00:00:00 on the Nth day and 00:00:00 on the N-1th day in history is obtained.

[0167] By setting up scheduled tasks, you can automatically perform data statistics for express reports when the scheduled time arrives, ensuring efficient and accurate data statistics.

[0168] In a possible embodiment of the present application, please refer to Fig. 9 , which shows a complete method flow chart of a possible express report data statistics method of the present application, such as Fig. 9 As shown, the method includes:

[0169] Step 901, scheduled task at 00:30 every day.

[0170] Step 902, fetch the data of the shared data information table from 00:00:00 yesterday to 00:00:00 the next day in batches.

[0171] Step 903: Check whether delivery_status is 00 node.

[0172] Step 904: if delivery_status is 00, check whether is_public_deliver is 1.

[0173] Step 905, is_public_deliver is 0, then total_cnt is +1; the value of the total order quantity of node 00 is order_cnt+1.

[0174] Step 906, is_public_deliver is 1, then total_cnt total amount + 1; the value of the total order quantity of 00 nodes is order_cnt 00 nodes total amount + 1; public_cnt total amount + 1; the value of the total number of distributed orders of 00 nodes is order_public_cnt 00 nodes total distribution amount + 1.

[0175] Step 907: if delivery_status is not 00, check whether is_public_deliver is 1.

[0176] Step 908, is_public_deliver is 0, then check whether the 00 node corresponding to the order number can be found based on the order number.

[0177] Step 909: If the corresponding 00 node cannot be found, check whether the waybill exists in the distribution scan record (scantype=18).

[0178] Step 910: If no query is found, no processing is performed.

[0179] Step 911, if found, update the total amount of total_cnt in the statistics table of scantime on that day +1, and the corresponding node total amount +1.

[0180] Step 912: If the corresponding 00 node can be found, no processing will be done.

[0181] Step 913, is_public_deliver is 1, and the 00 node corresponding to the order number is checked based on the order number.

[0182] Step 914: If the corresponding 00 node cannot be found, check whether the waybill exists in the distribution scan record (scantype=18).

[0183] Step 915: If no query is found, no processing is performed.

[0184] Step 916, query and update the statistics table of scantime on the day, total_cnt total amount +1; public_cnt total allocation amount +1; oper_public_cnt actual operation supplementary marking +1; corresponding node data total amount +1; corresponding node total allocation order amount +1.

[0185] Step 917, check the corresponding 00 node and see whether is_public_deliver corresponding to the 00 node is 1.

[0186] Step 918, the is_public_deliver corresponding to the 00 node is 0, the total public_cnt allocation on the day of crt_time corresponding to the 00 node is +1; the oper_public_cnt actual operation mark is +1; the total amount of data of the corresponding node is +1; the total allocation order quantity of the corresponding node is +1.

[0187] In step 919, if is_public_deliver corresponding to node 00 is 1, no processing is performed.

[0188] Please refer to Fig.10 The present application also provides a device for collecting express report data, the device comprising:

[0189] The report acquisition module 1010 is used to acquire the waybill report within the historical time period;

[0190] A co-matching detection module 1020 is used to detect, for each waybill data in the waybill report, whether the waybill corresponding to the waybill data is a co-matching waybill;

[0191] The data updating module 1030 is used to update the waybill statistical data corresponding to the waybill according to the detection result.

[0192] Optionally, the co-matching detection module 1020 is used to:

[0193] Determine the target node where the waybill is currently located; the target node is an initial node or an actual operation node, the initial node is a node for receiving the express, and the actual operation node is each node in the transportation process after receiving the express;

[0194] Detecting whether the waybill is a shared waybill;

[0195] The data updating module 1030 is used for:

[0196] According to the detection result and the target node, the waybill statistical data corresponding to the waybill is updated.

[0197] Optionally, the co-matching detection module 1020 is used to:

[0198] Detecting whether there is a co-distribution mark on the waybill;

[0199] If it exists, it is determined that the waybill is a shared waybill;

[0200] If it does not exist, it is determined that the waybill is a non-shared waybill.

[0201] Optionally, the data updating module 1030 is used to:

[0202] When the waybill is a shared order and the target node where the waybill is currently located is the initial node, the total number of waybills is increased by 1, the total number of shared orders is increased by 1, the total number of waybills at the initial node is increased by 1, and the total number of shared orders at the initial node is increased by 1.

[0203] Optionally, the data updating module 1030 is used to:

[0204] When the waybill is a non-shared waybill and the target node where the waybill is currently located is the initial node, the total number of waybills is increased by 1, and the total number of waybills at the initial node is increased by 1.

[0205] Optionally, the data updating module 1030 is used to:

[0206] When the waybill is a shared waybill and the target node of the waybill is currently an operational node, querying the initial node corresponding to the waybill;

[0207] If the initial node corresponding to the waybill is found, then check whether the found initial node is marked as a shared waybill;

[0208] If the initial node queried is not marked as a shared order, the total number of shared orders on the creation date corresponding to the queried initial node will be increased by 1, the total number of shared orders of the actual operation node will be increased by 1, the total number of waybills of the actual operation node will be increased by 1, and the number of additional shared orders marked will be increased by 1.

[0209] Optionally, the data updating module 1030 is used to:

[0210] If the initial node corresponding to the waybill is not found, check whether the waybill exists in the express distribution scanning record;

[0211] If the waybill exists in the distribution scanning record, the total number of shared orders on the scanning date of the distribution scanning record shall be increased by 1, the total number of shared orders at the actual operation node shall be increased by 1, the total number of waybills at the actual operation node shall be increased by 1, the number of supplementary shared order marks shall be increased by 1, and the total number of waybills shall be increased by 1.

[0212] Optionally, the data updating module 1030 is used to:

[0213] When the waybill is a non-shared waybill and the target node where the waybill is currently located is an actual operation node, query the initial node corresponding to the waybill;

[0214] If the initial node corresponding to the waybill is not found, check whether the waybill exists in the distribution scanning record;

[0215] If the waybill exists in the distribution scanning record, the total number of waybills on the scanning date of the distribution scanning record is increased by 1, and the total number of waybills at the actual operation node is increased by 1.

[0216] Optionally, the report acquisition module 1010 is used to

[0217] Set up scheduled tasks;

[0218] When the time of the scheduled task arrives, the waybill report within the historical time period is obtained.

[0219] In summary, by obtaining waybill reports within the historical time period; for each waybill data in the waybill report, detect whether the waybill corresponding to the waybill data is a co-distributed order; based on the detection result, update the waybill statistical data corresponding to the waybill. This solves the problem in the prior art that after waybills from co-distributed areas are issued to third parties, data omissions and incomplete co-distributed order markings will occur, as well as incomplete data in the actual operations of receiving, delivering, and signing for items at outlets, which will result in repeated calculations and inaccurate statistics in data reports, affecting the express headquarters' control over the co-distribution business and business decision-making. Statistics can be performed on each co-distributed order to ensure data accuracy.

[0220] See also Fig.11 The embodiment of the present application further provides an electronic device 200, which includes at least one memory 210, at least one processor 220, and a bus 230 connecting different platform systems.

[0221] The memory 210 may include a readable medium in the form of a volatile memory, such as a random access memory (RAM) 211 and / or a cache memory 212 , and may further include a read-only memory (ROM) 213 .

[0222] The memory 210 also stores a computer program, which can be executed by the processor 220, so that the processor 220 performs the steps of the express report data statistics method in the embodiment of the present application (such as Figure 1 Memory 210 may also include a program / utility 214 having a set (at least one) of program modules 215, such program modules including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include the implementation of a network environment.

[0223] Accordingly, the processor 220 may execute the above-mentioned computer programs, and may execute the program / utility 214 .

[0224] The bus 230 may be a bus representing one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures.

[0225] The electronic device 200 may also communicate with one or more external devices 240 such as keyboards, pointing devices, Bluetooth devices, etc., and may also communicate with one or more devices that can interact with the electronic device 200, and / or communicate with any device (such as a router, a modem, etc.) that enables the electronic device 200 to communicate with one or more other computing devices. Such communication may be performed through an input / output (I / O) interface 250. In addition, the electronic device 200 may also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN) and / or a public network, such as the Internet) through a network adapter 260. The network adapter 260 may communicate with other modules of the electronic device 200 through the bus 230. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 200, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage platforms.

[0226] The present application also provides a computer-readable storage medium for storing a computer program, which, when executed, implements the steps of the express report data statistics method in the present application embodiment (such as Figure 1 shown). Fig.12The program product 300 provided in this embodiment for implementing the above method is shown, which can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product 300 of the present application is not limited to this. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it. The program product 300 can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of readable storage media (non-exhaustive list) include: an electrical connection with 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.

[0227] Computer-readable storage media may include data signals propagated in baseband or as part of a carrier wave, wherein readable program codes are carried. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The readable storage medium may also be any readable medium other than the readable storage medium, which may send, propagate, or transmit a program used by or in combination with an instruction execution system, an apparatus, or a device. The program code contained on the readable storage medium may be transmitted with any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the above. The program code for performing the operation of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and also conventional procedural programming languages ​​such as "C" language or similar programming languages. The program code may be executed entirely on a user computing device, partially on a user device, as an independent software package, partially on a user computing device, partially on a remote computing device, or entirely on a remote computing device or server. Where a remote computing device is involved, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0228] This application is explained from the perspectives of purpose of use, effectiveness, progress and novelty. The practical progress it has is in line with the functional enhancement and usage requirements emphasized by the Patent Law. The above description and drawings of this application are only the preferred embodiments of this application, and are not intended to limit this application. Therefore, all structures, devices, features, etc. that are similar or identical to those of this application, that is, all equivalent replacements or modifications made in accordance with the scope of the patent application of this application, should fall within the scope of protection of the patent application of this application.

Claims

1. A method for statistically analyzing express report data, characterized in that: The method comprises: Get waybill reports within the historical time period; For each waybill data in the waybill report, detecting whether the waybill corresponding to the waybill data is a shared waybill; According to the detection result, updating the waybill statistical data corresponding to the waybill; Wherein, the detecting whether the waybill corresponding to the waybill data is a shared waybill includes: Determine the target node where the waybill is currently located; the target node is an initial node or an actual operation node, the initial node is a node for receiving the express, and the actual operation node is each node in the transportation process after receiving the express; detect whether the waybill is a shared order; The updating of the waybill statistics data corresponding to the waybill according to the detection result includes: According to the detection result and the target node, updating the waybill statistical data corresponding to the waybill; including: When the waybill is a shared order and the target node where the waybill is currently located is the initial node, the total number of waybills is increased by 1, the total number of shared orders is increased by 1, the total number of waybills at the initial node is increased by 1, and the total number of shared orders at the initial node is increased by 1; When the waybill is a non-shared waybill and the target node where the waybill is currently located is the initial node, the total amount of the waybill is increased by 1, and the total amount of the waybill of the initial node is increased by 1; When the waybill is a shared waybill and the target node of the waybill is currently an operational node, querying the initial node corresponding to the waybill; If the initial node corresponding to the waybill is found, then check whether the found initial node is marked as a shared waybill; If the initial node queried is not marked as a shared order, the total number of shared orders on the creation date corresponding to the queried initial node will be increased by 1, the total number of shared orders of the actual operation node will be increased by 1, the total number of waybills of the actual operation node will be increased by 1, and the number of additional shared orders marked will be increased by 1.

2. The express report data statistics method according to claim 1, characterized in that: The detecting whether the waybill corresponding to the waybill data is a shared waybill includes: Detecting whether there is a co-distribution mark on the waybill; If it exists, it is determined that the waybill is a shared waybill; If it does not exist, it is determined that the waybill is a non-shared waybill.

3. The express report data statistics method according to claim 1, characterized in that: The method further comprises: If the initial node corresponding to the waybill is not found, check whether the waybill exists in the express distribution scanning record; If the waybill exists in the distribution scanning record, the total number of shared orders on the scanning date of the distribution scanning record shall be increased by 1, the total number of shared orders at the actual operation node shall be increased by 1, the total number of waybills at the actual operation node shall be increased by 1, the number of supplementary shared order marks shall be increased by 1, and the total number of waybills shall be increased by 1.

4. The express report data statistics method according to claim 1, characterized in that: The updating of waybill statistics data corresponding to the waybill according to the detection result and the target node includes: When the waybill is a non-shared waybill and the target node where the waybill is currently located is an actual operation node, query the initial node corresponding to the waybill; If the initial node corresponding to the waybill is not found, check whether the waybill exists in the distribution scanning record; If the waybill exists in the distribution scanning record, the total number of waybills on the scanning date of the distribution scanning record is increased by 1, and the total number of waybills at the actual operation node is increased by 1.

5. The express report data statistics method according to any one of claims 1 to 4, characterized in that: Before obtaining the waybill report within the historical time period, the following steps are also included: Set up scheduled tasks; The method of obtaining the waybill report within the historical time period includes: When the time of the scheduled task arrives, the waybill report within the historical time period is obtained.

6. A device for collecting express report data, characterized in that: The device comprises: Report acquisition module, used to obtain waybill reports within the historical time period; A co-matching detection module, used for detecting, for each waybill data in the waybill report, whether the waybill corresponding to the waybill data is a co-matching waybill; A data updating module, used for updating the waybill statistical data corresponding to the waybill according to the detection result; Wherein, the co-matching detection module is used for: Determine the target node where the waybill is currently located; the target node is an initial node or an actual operation node, the initial node is a node for receiving the express, and the actual operation node is each node in the transportation process after receiving the express; detect whether the waybill is a shared order; The data updating module is used for: According to the detection result and the target node, updating the waybill statistical data corresponding to the waybill; When the waybill is a shared order and the target node where the waybill is currently located is the initial node, the total number of waybills is increased by 1, the total number of shared orders is increased by 1, the total number of waybills at the initial node is increased by 1, and the total number of shared orders at the initial node is increased by 1; When the waybill is a non-shared waybill and the target node where the waybill is currently located is the initial node, the total amount of the waybill is increased by 1, and the total amount of the waybill of the initial node is increased by 1; When the waybill is a shared waybill and the target node of the waybill is currently an operational node, querying the initial node corresponding to the waybill; If the initial node corresponding to the waybill is found, then check whether the found initial node is marked as a shared waybill; If the initial node queried is not marked as a shared order, the total number of shared orders on the creation date corresponding to the queried initial node will be increased by 1, the total number of shared orders of the actual operation node will be increased by 1, the total number of waybills of the actual operation node will be increased by 1, and the number of additional shared orders marked will be increased by 1.

Images