Logistics dispatch management method, device and equipment and storage medium

Abstract

The application discloses a logistics dispatching management method, device and equipment and a storage medium, and aims at the problem of delayed wages of express delivery personnel in the mode that the wages of express delivery personnel are settled by express delivery companies to outlets, and the outlets then settle the wages to the express delivery personnel, a setting operation of limit configuration application object in a first subsystem is performed, and a value of limit configuration is transmitted to a second subsystem; the second subsystem acquires monthly bill information of a business terminal, compares the monthly bill with the value of limit configuration, and generates direct bill information to a third subsystem or generates a settlement bill to a prepayment system of the outlet where the business terminal is located according to a comparison result. In a direct dispatching mode, the wages of express delivery personnel within a normal range are directly paid to the express delivery personnel account, and the bill exceeding the normal dispatching range is judged and limited, so that illegal operation of the outlet is avoided, and the hidden danger of delayed wages of the business personnel is eliminated. Therefore, the legal rights and interests of the express delivery company and the express delivery personnel are maintained, and the normal operation of the business is ensured.

Description

Technical Field

[0001] This invention belongs to the technical field of logistics cost management, and particularly relates to a method, device, equipment and storage medium for the control of logistics pickup and delivery. Background Technology

[0002] The express delivery industry implements a piece-rate wage system, and the pickup and delivery fee is an extremely important part of the courier's salary, which is the income that the courier receives for collecting and delivering a package.

[0003] Typically, the courier's (salesperson's) salary is settled by the courier company to the branch, and then the branch settles the salary with the courier.

[0004] However, due to irregularities at the outlets, such as creating virtual salesperson accounts and allocating high-paying jobs to these accounts, when the outlets close down due to poor management, they cannot pay the couriers' salaries on time and in full, leading to labor disputes. Summary of the Invention

[0005] The purpose of this invention is to provide a method, device, equipment, and storage medium for managing logistics pickup and delivery, which directly pays couriers wages within the normal range, judges and restricts bills exceeding the normal range, avoids the potential for wage arrears to couriers due to network violations, and thus protects the legitimate rights and interests of express delivery companies and couriers, ensuring the normal operation of the business.

[0006] To solve the above problems, the technical solution of the present invention is as follows:

[0007] A method for managing logistics pickup and delivery includes:

[0008] The first subsystem is configured to provide an object-oriented rate setting environment in which system users interact with user-defined application objects.

[0009] In response to the setting operation of the limit configuration application object in the first subsystem, the value of the limit configuration application object is transmitted to the second subsystem that uses the fee as a parameter for settlement; the second subsystem obtains the monthly bill information of the salesperson's terminal, compares the monthly bill with the value of the limit configuration application object, and generates direct bill information to the third subsystem for fee payment based on the comparison result, or generates a settlement bill to the prepayment system of the outlet where the salesperson's terminal is located;

[0010] The third subsystem responds to the transmission of direct billing information by the second subsystem, receives the direct billing, and pays the parameters, including the fee, to the corresponding salesperson terminal.

[0011] The prepayment system responds to the second subsystem's transmission of the settlement bill, receives the settlement bill, and allocates the limit-reaching information record to the corresponding salesperson's terminal.

[0012] According to an embodiment of the present invention, the second subsystem obtaining the monthly bill information of the salesperson's terminal further includes:

[0013] Create a data warehouse and import user behavior data and business data from the business system into the ODS layer of the data warehouse to generate order tables, order status tables, outlet tables, province tables, salesperson tables, and expense tables.

[0014] The second subsystem loads the ODS layer data of the data warehouse, and queries the monthly billing information of the salesperson based on the order table, order status table, salesperson table, and expense table, and obtains the corresponding data.

[0015] According to an embodiment of the present invention, the step of importing user behavior data and business data from the business system into the ODS layer of the data warehouse further includes:

[0016] For user behavior data, a startup log table and an event behavior table are created separately, using LZO compression and an LZO index is created;

[0017] For business data, create data tables in the ODS layer that are consistent with the business system database, and use the Sqoop tool to import the data from the business system database into the data warehouse to achieve data loading in the ODS layer.

[0018] According to an embodiment of the present invention, the step of generating direct billing information to a third subsystem for payment, or generating a settlement bill to the prepayment system of the branch where the salesperson's terminal is located, further includes:

[0019] In the data warehouse, based on the dimensions of orders, amounts, salespersons, outlets, and provinces, and driven by the logistics pickup and delivery process, a DWD layer is established. The most granular detailed fact table is constructed on the data of the ODS layer, generating tables for direct delivery fees to salespersons, direct delivery fees to outlets, and direct delivery fees to provinces.

[0020] The second subsystem compares the value of the current month's bill with the value of the limit configuration application object. Based on the comparison result, it updates and loads the data in the direct payment to salesperson table, direct payment to outlet table, and direct payment to province table in the data warehouse DWD layer, and generates direct bill information to the third subsystem for payment, or generates a settlement bill to the prepayment system of the outlet where the salesperson's terminal is located.

[0021] According to an embodiment of the present invention, the second subsystem obtaining the monthly bill information of the salesperson's terminal further includes:

[0022] Based on the settlement conditions configured for each business type, extract logistics orders from the business system;

[0023] The settlement amount for the salesperson's pickup and delivery is calculated based on the configured service fee rate and other related fee settlement rules.

[0024] According to an embodiment of the present invention, after retrieving the logistics order from the business system, the method further includes:

[0025] Determine the settlement merchant type corresponding to the logistics order. If the merchant type is an enterprise, execute the enterprise type order settlement process and check whether a settlement period has been set.

[0026] For logistics orders with configured settlement periods, logistics orders that meet the relevant conditions are packaged according to the settlement period rules, and an invoice is generated.

[0027] A logistics pickup and delivery control device, comprising:

[0028] The configuration module is used to configure the first subsystem to provide an object-oriented rate setting environment in which system users interact with user-defined application objects.

[0029] The settlement module is used to respond to the setting operation of the limit configuration application object in the first subsystem, and transmit the value of the limit configuration application object to the second subsystem for settlement with the fee as a parameter; the second subsystem obtains the monthly bill information of the salesperson terminal, compares the monthly bill with the value of the limit configuration application object, and generates direct bill information to the third subsystem for fee payment based on the comparison result, or generates a settlement bill to the prepayment system of the outlet where the salesperson terminal is located;

[0030] The direct module is used by the third subsystem to receive the direct bill information in response to the transmission of direct bill information by the second subsystem, and to pay the parameters including the fee to the corresponding salesperson terminal.

[0031] The feedback module is used by the prepayment system to respond to the transmission of settlement bills by the second subsystem, receive the settlement bills, and allocate the limit information record to the corresponding salesperson terminal.

[0032] According to one embodiment of the present invention, the settlement module is further used to load the ODS layer data of the data warehouse, and query the monthly bill information of the salesperson based on the order table, order status table, salesperson table, and expense table, and obtain the corresponding data;

[0033] The second subsystem compares the value of the current month's bill with the value of the limit configuration application object. Based on the comparison result, it updates and loads the data in the direct payment to salesperson table, direct payment to outlet table, and direct payment to province table in the data warehouse DWD layer, and generates direct bill information to the third subsystem for payment, or generates a settlement bill to the prepayment system of the outlet where the salesperson's terminal is located.

[0034] A logistics pickup and delivery control device includes a memory and a processor. The memory stores computer-readable instructions, which, when executed by the processor, cause the processor to perform the steps in the logistics pickup and delivery control method described in an embodiment of the present invention.

[0035] A storage medium storing computer-readable instructions, which, when executed by one or more processors, cause the one or more processors to perform steps in a logistics pickup and delivery control method according to an embodiment of the present invention.

[0036] Because the present invention adopts the above technical solution, it has the following advantages and positive effects compared with the prior art:

[0037] 1) The logistics pickup and delivery management method in one embodiment of the present invention addresses the problem of wage arrears in the current system where courier wages are settled by the courier company to the outlets, and then by the outlets to the couriers. By implementing a direct payment method for delivery fees, the normal range of courier wages is directly deposited into the courier's account; bills exceeding the normal delivery fee range are judged and restricted to prevent outlets from violating regulations and posing a risk of wage arrears to couriers. This protects the legitimate rights and interests of both the courier company and the couriers, ensuring the normal operation of the business.

[0038] 2) The logistics pickup and delivery control method in one embodiment of the present invention creates a data warehouse to store user behavior data and business data of the logistics business system, and uses the hierarchical performance of the data warehouse to establish a table of direct delivery fee to salesperson, direct delivery fee to outlet, and direct delivery fee to province, so as to make the data structure clearer, facilitate the maintenance of data accuracy, and reduce the impact on business. Attached Figure Description

[0039] Figure 1 This is a flowchart of a logistics pickup and delivery control method according to an embodiment of the present invention;

[0040] Figure 2 This is a flowchart illustrating the control process of direct pickup and dispatch in one embodiment of the present invention;

[0041] Figure 3 This is a block diagram of a logistics pickup and delivery control device according to an embodiment of the present invention;

[0042] Figure 4This is a schematic diagram of a logistics pickup and delivery control device according to an embodiment of the present invention. Detailed Implementation

[0043] The following detailed description, in conjunction with the accompanying drawings and specific embodiments, provides a method, apparatus, device, and storage medium for managing logistics pickup and delivery according to the present invention. The advantages and features of the present invention will become clearer from the following description and claims.

[0044] Example 1

[0045] Typically, a package shipped from location A to a recipient in location B involves three steps: pickup, transportation, and delivery. Location A collects the courier fee, headquarters collects the waybill fee, trunk transportation fee, and other charges, while the branch in location B receives the delivery fee. Industry practice dictates that the delivery fee comes from the courier fee collected by the receiving branch. The delivery fee paid by the sending branch to the delivery branch is generally paid by the sending branch to headquarters, and then by headquarters to the delivery branch. Regarding the income of courier workers, their earnings are calculated based on the number of packages delivered.

[0046] In other words, the wages of deliverymen (salespersons) are settled by the courier company headquarters to the branches, and then the branches settle the wages with the deliverymen. However, due to irregularities by the branches, such as creating virtual salesperson accounts and distributing high-paying jobs to these accounts, when a branch goes bankrupt due to poor management, it cannot pay the deliverymen's wages on time and in full, thus leading to labor disputes.

[0047] To address the aforementioned issues, this embodiment provides a management method for logistics pickup and delivery. This method directly pays couriers wages within the normal range, while judging and restricting invoices exceeding the normal range. This avoids the potential for wage arrears due to irregularities by delivery stations, thereby protecting the legitimate rights and interests of both the courier company and its couriers and ensuring the normal operation of the business.

[0048] Please refer to Figure 1 The management and control methods for this logistics pickup and delivery include the following steps:

[0049] S1: Configure the first subsystem to provide an object-oriented rate setting environment in which system users interact with user-defined application objects;

[0050] S2: In response to the setting operation of the limit configuration application object in the first subsystem, the value of the limit configuration application object is passed to the second subsystem that uses the fee as a parameter for settlement; the second subsystem obtains the monthly bill information of the salesperson's terminal, compares the monthly bill with the value of the limit configuration application object, and generates direct bill information to the third subsystem for fee payment based on the comparison result, or generates a settlement bill to the prepayment system of the outlet where the salesperson's terminal is located;

[0051] S3: The third subsystem responds to the transmission of direct billing information by the second subsystem, receives the direct billing, and pays the parameters, including the fee, to the corresponding salesperson terminal.

[0052] S4: The prepayment system responds to the second subsystem's transmission of settlement bills, receives the settlement bills, and distributes the limit information records to the corresponding salesperson terminals.

[0053] The logistics pickup and delivery control method in this embodiment involves a first subsystem, a second subsystem, a third subsystem, and a prepayment system. Specifically, in step S1, the first subsystem provides an object-oriented rate setting environment where system users interact with user-defined application objects. The first subsystem uses a graphical user interface to display the application object to the user, allowing the user to set, view, and modify the application object.

[0054] The first subsystem can be an object-oriented system developed using any of the following technologies: C#, Smalltalk, EIFFEL, Python, Java, or Objective-C. Object-oriented programming is a method of understanding and abstracting the real world, a product of the development of computer programming technology to a certain stage. An object is anything that people want to study, from the simplest integers to complex airplanes; it can represent not only concrete things but also abstract rules, plans, or events.

[0055] In this embodiment, the first subsystem is used for rate setting, that is, to stipulate the rate for courier pickup and delivery. This first subsystem can be a courier pickup and delivery system, where the courier pickup and delivery rate is set, and the rate for calculating the number of deliveries is adjusted. Adding a limit configuration to the courier pickup and delivery system allows setting an upper limit for the monthly pickup and delivery fees for each courier.

[0056] When adding a quota configuration parameter to the courier pickup and delivery system, it can be achieved in the following ways: Add a custom parameter, "Quota Configuration," to the pickup and delivery system's configuration file. In the front-end implementation, read the quota configuration parameter from the pickup and delivery system configuration file using Spring Boot, and add the key of the quota configuration parameter to the `@Value` annotation; or use `@ConfigurationProperties` to map the quota configuration parameter to the entity class. See the following code for details:

[0057]

[0058]

[0059] In step S2, in response to the setting operation of the limit configuration application object in the first subsystem, the value of the limit configuration application object is passed to the second subsystem for fee settlement. Please refer to... Figure 2 The second subsystem obtains the salesperson's monthly bill, calculates the bill amount, compares the bill amount with the value of the limit configuration application object, and generates a direct bill to the third subsystem for payment, or generates a settlement bill to the prepayment system of the salesperson's branch.

[0060] Clearly, this second subsystem is a fee settlement system. This system can extract logistics orders from the business system based on the settlement conditions configured for each business type; and calculate the settlement amount for delivery personnel's pickup and delivery based on the configured service fee rate and other relevant fee settlement rules.

[0061] For logistics and transportation, the settlement documents include, but are not limited to, supplier delivery notes, company warehouse receiving notes, relevant inspection and testing reports, highway and bridge toll invoices, and gas station fuel receipts. For courier delivery personnel, the settlement documents include commission for each delivered package, plus a base salary when paying wages. The commission for each package can be set in the pickup and delivery system in step S1. The settlement system can extract logistics orders from the business system according to the settlement conditions configured for each business type. These settlement conditions can be relevant logistics and transportation cost settlement documents, or pickup documents for each package handled by the courier, etc. In this embodiment, the main focus is on calculating the settlement amount for courier delivery personnel. Therefore, based on the courier's ID, all logistics orders delivered by that courier in the current month can be extracted from the business system. The commission for each delivered logistics order is calculated according to the pre-set rate (service fee rate), and then added to the courier's base salary to calculate the courier's wages.

[0062] After retrieving logistics orders from the business system, the payment settlement system needs to determine the merchant type corresponding to the logistics order. If the merchant type is an enterprise, the system executes the enterprise type order settlement process and checks whether a settlement period has been set. For logistics orders with a configured settlement period, the system packages the logistics orders that meet the relevant conditions according to the period rules and generates an invoice.

[0063] When the merchant type is an enterprise, the enterprise type order settlement process further includes:

[0064] The workflow builder, via a second subsystem, responds to the output determining the merchant type, thereby creating a workflow for the output application object. This workflow is a causal structure, identifying the trigger that causes the workflow to be executed, and defining user-specified automatic actions to be performed on or by the output application object in response to the trigger. Furthermore, the workflow engine receives system events including the trigger, and upon the trigger's occurrence, executes the workflow to perform the user-specified automatic actions related to the output application object.

[0065] In this embodiment, the workflow builder creates a settlement workflow for a merchant based on the output of the payment settlement system for the merchant type, i.e., an enterprise merchant. This workflow follows a cause-and-effect structure: when the payment settlement system outputs an enterprise merchant, it triggers the execution of the enterprise merchant's settlement workflow, where the enterprise merchant is the cause, and the execution of the enterprise merchant's settlement workflow is the effect.

[0066] After calculating the settlement amount for each courier, the fee settlement system needs to compare the settlement amount with the value of the limit configuration parameter. When the settlement amount is less than the limit configuration parameter, a direct bill is generated to the third subsystem for fee payment. When the settlement amount is greater than or equal to the limit configuration parameter, a settlement bill is generated to the prepayment system of the courier's branch.

[0067] The value of this limit configuration parameter can be determined based on the maximum historical salary of the courier company's employees, or it can be set to an unattainable value, such as 20,000 yuan, based on the courier company's business volume and service fee rate.

[0068] In addition to the above implementation methods, this embodiment also provides another implementation method for step S2, as follows:

[0069] Create a data warehouse and import user behavior data and business data from the business system into the ODS layer of the data warehouse to generate order tables, order status tables, outlet tables, province tables, salesperson tables, and expense tables.

[0070] The second subsystem loads the ODS layer data from the data warehouse, and queries the monthly billing information of the salespersons based on the order table, order status table, salesperson table, and expense table, and obtains the corresponding data.

[0071] When importing user behavior data and business data from the business system into the ODS layer of the data warehouse, for user behavior data, a startup log table and an event behavior table are created, LZO compression is used, and LZO indexes are created. For business data, data tables consistent with those in the business system database (such as MySQL) are created in the ODS layer, and the data in the business system database is imported into the data warehouse using the Sqoop tool to achieve data loading in the ODS layer.

[0072] In the data warehouse, a Data Warehouse (DWD) layer is established based on the dimensions of orders, amounts, salespersons, outlets, and provinces, driven by the logistics pickup and delivery process. This layer constructs the finest-grained detailed fact tables from the data in the Data ODS layer, generating tables for direct delivery fees to salespersons, outlets, and provinces. The second subsystem compares the salesperson's monthly bill with the value of the limit configuration application object. Based on the comparison result, it updates and loads the data in the DWD layer of the data warehouse into the direct delivery fee to salesperson, outlet, and province tables, generating direct billing information for the third subsystem used for payment, or generating settlement bills for the prepayment system of the outlet where the salesperson's terminal is located.

[0073] The startup log table ods_start_log is created as follows:

[0074] CREATE DATABASE gmall;

[0075] Use gmall;

[0076] DROP TABLE IF EXISTS ods_start_log;

[0077] CREATE EXTERNAL TABLE ods_start_log(line string)

[0078] partitioned by(dt string)

[0079] STOREDASINPUTFORMAT"com.hadoop.mapred.

[0080] DeprecatedLzoTextInputFormat"OUTPUTFORMAT

[0081] "org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat"

[0082] LOCATION' / warehouse / gamll / ods / ods_start_log';

[0083] LOAD DATA INPATH' / origin_data_cdh / gmall / log / topic_start / 2020-11-19'INTO TABLE ods_start_log PARTITION(dt='2020-11-19');

[0084] LOAD DATA INPATH' / origin_data_cdh / gmall / log / topic_start / 2020-11-20'INTO TABLE ods_start_log PARTITION(dt='2020-11-20');

[0085] SELECT*FROM ods_start_log WHERE dt='2020-11-19'LIMIT 2;

[0086] The implementation of the event behavior table is similar, and its related code is not shown here.

[0087] Importing user behavior logs from the ODS layer is implemented as follows:

[0088]

[0089] The loading of business data in the ODS layer involves importing data from the business system database into the data warehouse using the Sqoop tool; specific code examples are not shown here.

[0090] The DWD layer parses user log behavior and remodels business data using a dimensional model. The DWD layer is driven by business processes, constructing the finest-grained fact table based on the characteristics of each specific business process. Its modeling process includes: selecting a business process → declaring granularity → confirming dimensions → confirming facts.

[0091] Specifically, in this embodiment, the business process is the pickup and delivery process of logistics orders. The fact tables involved are the "Delivery Fee Directly to Salesperson Fact Table," the "Delivery Fee Directly to Outlet Fact Table," and the "Delivery Fee Directly to Province Fact Table." The content represented by each row of data in each fact table is confirmed to ensure the smallest possible granularity of the fact tables. Based on the dimensions of order, amount, salesperson, outlet, and province, the above fact tables are created, and the metrics for each fact table are confirmed. The final implementation of each fact table is not shown here.

[0092] The above-mentioned data warehouse is used to store user behavior data and business data of the logistics business system. The hierarchical performance of the data warehouse is used to establish tables for direct delivery of fees to salespersons, direct delivery of fees to outlets, and direct delivery of fees to provinces. This makes the data structure clearer, facilitates the maintenance of data accuracy, and reduces the impact on business, thereby facilitating the implementation of direct delivery of fees in this embodiment.

[0093] In step S3, the third subsystem responds to the transmission of direct billing information by the second subsystem, receives the direct bill, and pays the parameters, including the fee, to the corresponding salesperson terminal.

[0094] In step S2, after determining the settlement amount for the courier, the request is pushed to different subsystems for processing based on the determination result. In this step, the third subsystem is a payment system, such as the courier wallet system on the courier's terminal. This third subsystem can directly pay the fees (salary) to the corresponding courier based on the received direct invoice. That is, the salary amount is directly transferred to the courier's account.

[0095] In step S4, the prepayment system responds to the second subsystem's transmission of the settlement bill, receives the settlement bill, and allocates the limit-reaching information record to the corresponding salesperson terminal.

[0096] In this step, the branch's prepayment system receives settlement bills from salespersons whose settlement amounts exceed the limit configuration parameters. For such settlement bills, a mark indicating that the monthly limit has been reached needs to be added, and the salesperson's ID and the status of reaching the monthly limit should be output to the business monitoring system and payment system.

[0097] The business monitoring system stores tables for direct payment to salespersons, direct payment to service outlets, and direct payment to provinces / regions. The creation and modification of these tables are based on whether the monthly limit has been reached, as shown below:

[0098]

[0099] The salesperson number and its tag for the settlement bill that has reached the monthly limit are transmitted to the fourth subsystem, which is used for business monitoring. This allows the fourth subsystem to locate the salesperson number in the direct payment salesperson table and record whether the monthly limit has been reached in order to respond.

[0100] At the same time, the salesperson number and its markings for settlement bills that have reached the monthly limit are transmitted to the third subsystem, so that the third subsystem can locate the salesperson number in the payment list, mark it as having reached the monthly limit, and then conduct further review before making direct payment.

[0101] Through the above steps and Figure 2It can be seen that there are two processing paths for the settlement amount of the courier. Data processing path one:

[0102] If the settlement amount is less than 20,000 yuan (the value of the limit configuration parameter), a direct bill will be generated;

[0103] At the same time, the data is pushed to the courier's package collection and delivery system for processing;

[0104] The payment is pushed to the salesperson's wallet system (payment system), the payment is processed normally, and the business process ends. Data processing path two:

[0105] If the settlement amount is greater than or equal to 20,000 yuan, the delivery fee settlement will enter the branch prepayment system;

[0106] Then output a status indicating whether the monthly limit has been reached;

[0107] Then send the data to the pickup and delivery real-time monitoring system (headquarters delivery fee direct report). Add a field to the salesperson table: whether the monthly limit has been reached.

[0108] At the same time, the data is sent to the salesperson's wallet system for processing. If the delivery fails to be successful due to reaching the monthly limit, the courier's pickup and delivery system adds a tag: "Monthly direct delivery limit reached," and the business process ends.

[0109] This embodiment uses a direct payment method to directly deposit delivery fees into the courier's account for deliveries within the normal range; it also identifies and restricts bills exceeding the normal delivery fee range to prevent branch irregularities and potential wage arrears for delivery personnel. This protects the legitimate rights and interests of both the courier company and its delivery personnel, ensuring the normal operation of the business.

[0110] Example 2

[0111] This embodiment provides a logistics pickup and delivery control device; please refer to [link / reference]. Figure 3 The logistics pickup and delivery control device includes:

[0112] Configuration module 1 is used to configure the first subsystem to provide an object-oriented rate setting environment in which system users interact with user-defined application objects;

[0113] Settlement module 2 is used to respond to the setting operation of the limit configuration application object in the first subsystem, and transmit the value of the limit configuration application object to the second subsystem that uses the fee as a parameter for settlement; the second subsystem obtains the monthly bill information of the salesperson terminal, compares the monthly bill with the value of the limit configuration application object, and generates direct bill information to the third subsystem for fee payment based on the comparison result, or generates a settlement bill to the prepayment system of the outlet where the salesperson terminal is located;

[0114] Direct module 3 is used by the third subsystem to respond to the transmission of direct billing information by the second subsystem, receive the direct billing, and pay the parameters including the fee to the corresponding salesperson terminal.

[0115] Feedback module 4 is used by the prepayment system to respond to the second subsystem's transmission of settlement bills, receive settlement bills, and allocate the limit information record to the corresponding salesperson terminal.

[0116] The settlement module 2 is further used to load data from the ODS layer of the data warehouse. Based on the order table, order status table, salesperson table, and expense table, it queries the monthly bill information of the salesperson and obtains the corresponding data. It is also used by the second subsystem to compare the monthly bill of the salesperson with the value of the limit configuration application object. Based on the comparison result, it updates and loads the data in the direct payment to salesperson table, direct payment to outlet table, and direct payment to province table in the DWD layer of the data warehouse, and generates direct bill information to the third subsystem for payment, or generates a settlement bill to the prepayment system of the outlet where the salesperson's terminal is located.

[0117] The functions and implementation methods of the above configuration module 1, settlement module 2, direct access module 3 and feedback module 4 are as described in the above embodiment 1, and will not be repeated here.

[0118] Example 3

[0119] This embodiment provides a control device for logistics pickup and delivery. Please refer to... Figure 4 The logistics pickup and delivery control device 500 can vary significantly due to differences in configuration or performance. It may include one or more central processing units (CPUs) 510 (e.g., one or more processors) and memory 520, and one or more storage media 530 (e.g., one or more mass storage devices) for storing application programs 533 or data 532. The memory 520 and storage media 530 can be temporary or persistent storage. The program stored in the storage media 530 may include one or more modules (not shown in the diagram), each module including a series of instruction operations on the logistics pickup and delivery control device 500.

[0120] Furthermore, the processor 510 can be configured to communicate with the storage medium 530 and execute a series of instructions stored in the storage medium 530 on the logistics pickup and delivery control device 500.

[0121] The logistics pickup and delivery control equipment 500 may also include one or more power supplies 540, one or more wired or wireless network interfaces 550, one or more input / output interfaces 560, and / or one or more operating systems 531, such as Windows Server, Vista, etc.

[0122] Those skilled in the art will understand that Figure 4 The illustrated control equipment structure for logistics pickup and delivery does not constitute a limitation on the control equipment for logistics pickup and delivery. It may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0123] Another embodiment of the present invention also provides a computer-readable storage medium.

[0124] The computer-readable storage medium can be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the steps of the logistics pickup and delivery control method in Embodiment 1.

[0125] If the logistics pickup and delivery management method is implemented in the form of program instructions and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in software. This computer software is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0126] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific identification content executed by the system and device described above can be referred to the corresponding process in the foregoing method embodiments.

[0127] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings, but the present invention is not limited to the above embodiments. Even if various changes are made to the present invention, if these changes fall within the scope of the claims of the present invention and their equivalents, they shall still fall within the protection scope of the present invention.

Claims

1. A method for managing logistics pickup and delivery, characterized in that, include: The first subsystem is configured to provide an object-oriented rate setting environment in which system users interact with user-defined application objects. In response to the setting operation of the limit configuration application object in the first subsystem, the value of the limit configuration application object is transmitted to the second subsystem that uses the fee as a parameter for settlement; the second subsystem obtains the monthly bill information of the salesperson's terminal, compares the monthly bill with the value of the limit configuration application object, and generates direct bill information to the third subsystem for fee payment based on the comparison result, or generates a settlement bill to the prepayment system of the outlet where the salesperson's terminal is located; The third subsystem responds to the transmission of direct billing information by the second subsystem, receives the direct billing, and pays the parameters, including the fee, to the corresponding salesperson terminal. The prepayment system responds to the second subsystem's transmission of the settlement bill, receives the settlement bill, and allocates the limit-reaching information record to the corresponding salesperson's terminal.

2. The logistics pickup and delivery control method as described in claim 1, characterized in that, The second subsystem further includes obtaining the monthly billing information from the salesperson's terminal, including: Create a data warehouse and import user behavior data and business data from the business system into the ODS layer of the data warehouse to generate order tables, order status tables, outlet tables, province tables, salesperson tables, and expense tables. The second subsystem loads the ODS layer data of the data warehouse, and queries the monthly billing information of the salesperson based on the order table, order status table, salesperson table, and expense table, and obtains the corresponding data.

3. The logistics pickup and delivery control method as described in claim 2, characterized in that, The process of importing user behavior data and business data from the business system into the ODS layer of the data warehouse further includes: For user behavior data, a startup log table and an event behavior table are created separately, using LZO compression and an LZO index is created; For business data, create data tables in the ODS layer that are consistent with the business system database, and use the Sqoop tool to import the data from the business system database into the data warehouse to achieve data loading in the ODS layer.

4. The logistics pickup and delivery control method as described in claim 1, characterized in that, The generation of direct billing information to the third subsystem for payment, or the generation of settlement bills to the prepayment system of the branch where the salesperson's terminal is located, further includes: In the data warehouse, based on the dimensions of orders, amounts, salespersons, outlets, and provinces, and driven by the logistics pickup and delivery process, a DWD layer is established. The most granular detailed fact table is constructed on the data of the ODS layer, generating tables for direct delivery fees to salespersons, direct delivery fees to outlets, and direct delivery fees to provinces. The second subsystem compares the value of the current month's bill with the value of the limit configuration application object. Based on the comparison result, it updates and loads the data in the direct payment to salesperson table, direct payment to outlet table, and direct payment to province table in the data warehouse DWD layer, and generates direct bill information to the third subsystem for payment, or generates a settlement bill to the prepayment system of the outlet where the salesperson's terminal is located.

5. The logistics pickup and delivery control method as described in claim 1, characterized in that, The second subsystem further includes obtaining the monthly billing information from the salesperson's terminal, including: Based on the settlement conditions configured for each business type, extract logistics orders from the business system; The settlement amount for the salesperson's pickup and delivery is calculated based on the configured service fee rate and other related fee settlement rules.

6. The logistics pickup and delivery control method as described in claim 5, characterized in that, After retrieving logistics orders from the business system, the process also includes: Determine the settlement merchant type corresponding to the logistics order. If the merchant type is an enterprise, execute the enterprise type order settlement process and check whether a settlement period has been set. For logistics orders with configured settlement periods, logistics orders that meet the relevant conditions are packaged according to the settlement period rules, and an invoice is generated.

7. A control device for logistics pickup and delivery, characterized in that, include: The configuration module is used to configure the first subsystem to provide an object-oriented rate setting environment in which system users interact with user-defined application objects. The settlement module is used to respond to the setting operation of the limit configuration application object in the first subsystem, and transmit the value of the limit configuration application object to the second subsystem for settlement with the fee as a parameter; the second subsystem obtains the monthly bill information of the salesperson terminal, compares the monthly bill with the value of the limit configuration application object, and generates direct bill information to the third subsystem for fee payment based on the comparison result, or generates a settlement bill to the prepayment system of the outlet where the salesperson terminal is located; The direct module is used by the third subsystem to receive the direct bill information in response to the transmission of direct bill information by the second subsystem, and to pay the parameters including the fee to the corresponding salesperson terminal. The feedback module is used by the prepayment system to respond to the transmission of settlement bills by the second subsystem, receive the settlement bills, and allocate the limit information record to the corresponding salesperson terminal.

8. The logistics pickup and delivery control device as described in claim 7, characterized in that, The settlement module is further used to load the ODS layer data of the data warehouse, and query the monthly bill information of the salesperson based on the order table, order status table, salesperson table, and expense table, and obtain the corresponding data. The second subsystem compares the value of the current month's bill with the value of the limit configuration application object. Based on the comparison result, it updates and loads the data in the direct payment to salesperson table, direct payment to outlet table, and direct payment to province table in the data warehouse DWD layer, and generates direct bill information to the third subsystem for payment, or generates a settlement bill to the prepayment system of the outlet where the salesperson's terminal is located.

9. A logistics pickup and delivery control device, characterized in that, include: A memory and a processor, wherein the memory stores computer-readable instructions that, when executed by the processor, cause the processor to perform the steps in the logistics pickup and delivery control method as described in any one of claims 1 to 6.

10. A storage medium storing computer-readable instructions, characterized in that, When the computer-readable instructions are executed by one or more processors, the one or more processors perform the steps in the logistics pickup and delivery control method as described in any one of claims 1 to 6.

Images