Cargo rack management method, device, equipment and medium

Abstract

This application relates to the field of logistics management technology, and discloses a method, apparatus, equipment, and medium for cargo sorting management. The method includes: generating a purchase plan document in response to a purchase plan generation operation initiated by a first user, and sharing the purchase plan document with a second user; generating a purchase order document in response to a purchase list generation operation based on the purchase plan document by the second user, and sharing the purchase order document with a third user; generating a shipment plan document in response to a shipment plan generation operation based on the purchase order document by the third user, and sharing the shipment plan document with the first user; and generating a receiving order document in response to a receiving list generation operation based on the shipment plan document by the first user, and sharing the receiving order document with the second user. Embodiments of this application can realize real-time sharing and collaboration of data at all stages of the supply chain, reducing information asymmetry.

Description

Technical Field

[0001] This application relates to the field of logistics management technology, and in particular to a method, apparatus, equipment and medium for cargo container management. Background Technology

[0002] In modern logistics operations, cargo management involves several key stages, including procurement planning, procurement lists, shipping plans, and receiving lists. With the widespread use of computer technology, companies typically deploy multiple business systems to handle these stages. While these systems can store large amounts of business data and improve local informatization levels, they generally suffer from a lack of interconnectivity. These systems operate independently, forming fragmented information silos, preventing real-time data sharing and collaboration across the supply chain. Specifically, after a procurement plan is generated, information is difficult to smoothly transmit to the subsequent procurement list processing stage; when shipping plans are formulated, there is a lack of effective correlation with procurement data, resulting in information gaps; and receiving operations frequently experience verification discrepancies due to the inability to obtain timely shipping details. This prominent information asymmetry leads to a large accumulation of redundant data, frequent inefficient operations such as repetitive data entry and manual coordination in business processes, and a persistently high error rate. This not only prolongs cargo processing cycles but also significantly increases operating costs and weakens the overall supply chain's responsiveness and market adaptability. Summary of the Invention

[0003] The purpose of this application is to provide a cargo container management method, device, equipment and medium that can realize real-time data sharing and collaboration in all links of the supply chain and reduce information asymmetry.

[0004] This application provides a method for managing cargo racking, including: In response to the purchase plan generation operation initiated by the first user, a purchase plan document is generated and shared with the second user; In response to the second user's operation of generating a purchase list for the purchase plan document, a purchase document is generated and shared with the third user; In response to the third user's operation of generating a shipping plan for the purchase order, a shipping plan document is generated and shared with the first user; In response to the first user's operation of generating a receipt list for the shipping plan document, a receipt document is generated and shared with the second user.

[0005] In some embodiments, the first user includes a first requesting user and a first approving user, and the step of generating a purchase plan document in response to the purchase plan generation operation initiated by the first user includes: In response to the first requesting user's request to add a plan, a purchase plan demand table is provided; In response to the first requesting user's request to enter plan information, the purchase plan information entered by the first requesting user is stored in the purchase plan demand table to obtain the purchase plan information table; In response to the plan review request initiated by the first review user, upon receiving the review approval information entered by the first review user, the purchase plan document is generated based on the purchase plan information table.

[0006] In some embodiments, the second user includes a second requesting user and a second approving user. The step of generating a purchase order in response to the second user's purchase list generation operation on the purchase plan document includes: In response to the second requesting user's request to add a list, a purchase list requirement table is provided; In response to the purchase information entry request initiated by the second requesting user, the purchase list information entered by the second requesting user is stored in the purchase list demand table to obtain the purchase list information table; In response to the purchase review request initiated by the second review user, upon receiving the review approval information entered by the second review user, the purchase order is generated based on the purchase list information table.

[0007] In some embodiments, generating a shipping plan document in response to the third user's shipping plan generation operation on the purchase order includes: In response to the list addition request initiated by the third user, a shipping list requirement table is provided; When the third user initiates an information adjustment request, the order number adjustment information and / or order split information entered by the third user are stored in the purchase order to obtain the shipment adjustment order; In response to the information entry request initiated by the third user, the packing information of the target document is adjusted based on the packing change information entered by the third user to obtain a shipping plan confirmation table; when the shipping adjustment document is generated, the target document is the shipping adjustment document, otherwise, the target document is the purchase document; Based on the shipping plan confirmation form, the shipping plan document is generated.

[0008] In some embodiments, adjusting the packing information of the target document based on the packing change information entered by the third user includes: Query the cargo type and quantity information of the target document; Based on the cargo type information and the cargo quantity information, the data field types involved in the changed packing information are analyzed, and the impact level of the change is assessed; the data field types include at least low-sensitivity fields and high-sensitivity fields, and the impact level of the change is dynamically generated based on the combination rules of the data field types, the cargo type information, and the cargo quantity information; Based on the impact level of the change, the corresponding operation path is matched from the preset rule base to configure the packing information of the goods in the target document, and the shipping plan confirmation table is obtained.

[0009] In some embodiments, the first user includes a first requesting user and a first approving user, and the step of generating a receiving document in response to the first user's receiving list generation operation on the shipping plan document includes: In response to the first requesting user's request to add a receipt, a receipt demand table is provided; In response to the first requesting user's request to enter receipt information, the receipt information entered by the first requesting user is stored in the receipt demand table to obtain the receipt information table; In response to the receiving verification request initiated by the first verification user, upon receiving the verification approval information entered by the first verification user, the receiving document is generated based on the receiving information table.

[0010] In some embodiments, the cargo arrangement management method further includes: Upon receiving the ledger query request initiated by the first user, the warehouse ledger is displayed; Upon receiving an information export request initiated by the first user, the target requirement information indicated by the information export request is exported.

[0011] This application embodiment also provides a cargo racking management device, including: The first module is used to respond to the purchase plan generation operation initiated by the first user, generate a purchase plan document, and share the purchase plan document with the second user; The second module is used to generate a purchase order in response to the second user's purchase list generation operation on the purchase plan document, and share the purchase order with the third user; The third module is used to respond to the third user's operation of generating a delivery plan for the purchase order, generate a delivery plan document, and share the delivery plan document with the first user. The fourth module is used to generate a receiving document in response to the first user's receiving list generation operation on the shipping plan document, and to share the receiving document with the second user.

[0012] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described cargo arrangement management method.

[0013] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described cargo arrangement management method.

[0014] The beneficial effects of this application are as follows: By introducing a structured document flow and multi-user collaboration mechanism, starting from the first user generating a purchase plan document and sharing it with the second user, then the second user generating a purchase document and sharing it with the third user, then the third user generating a shipping plan document and sharing it with the first user, and finally the first user generating a receiving document and sharing it with the second user, a complete, closed-loop information flow is formed. This ensures that the documents in each business link serve as the input basis for the next link, guaranteeing the continuity and accuracy of information. Therefore, by sharing documents and circulating them among users, the barriers of "information silos" are broken down, enabling real-time information sharing and efficient flow. This optimizes the operational efficiency of the entire supply chain, reduces operating costs, achieves real-time data sharing and collaboration across all links of the supply chain, reduces information asymmetry, improves cargo handling efficiency, and shortens processing cycles. Attached Figure Description

[0015] Figure 1 This is a diagram illustrating the application environment of the cargo racking management method provided in the embodiments of this application.

[0016] Figure 2 This is a flowchart of the cargo arrangement management method provided in the embodiments of this application.

[0017] Figure 3 This is a flowchart of a method for generating purchase order documents provided in an embodiment of this application.

[0018] Figure 4 This is a flowchart of a method for generating purchase invoices provided in an embodiment of this application.

[0019] Figure 5 This is a flowchart of a method for generating a shipping plan document provided in an embodiment of this application.

[0020] Figure 6 This is a flowchart of a method for generating a receipt document provided in an embodiment of this application.

[0021] Figure 7 This is a schematic diagram of the cargo racking management device provided in the embodiments of this application.

[0022] Figure 8This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0024] It should be noted that although functional modules are divided in the device schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first," "second," etc., in the specification, claims, and drawings are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0025] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application. Furthermore, the information, data, and signals involved in the embodiments of this application are all authorized by relevant parties or have been fully authorized by all parties, and the collection, use, and processing of related data comply with the relevant laws, regulations, and standards of the relevant countries and regions.

[0026] In traditional cargo sorting processes, the lack of data interaction mechanisms between business systems leads to information silos, with information flow breaking at system boundaries. This results in reduced supply chain collaboration efficiency and increased data processing error rates. Furthermore, the root of the problem lies in the lack of a unified data flow framework, exacerbating information asymmetry during business processes. This directly impacts key system performance indicators such as processing timeliness and data consistency, with information redundancy and erroneous data accumulating continuously throughout the supply chain. For example, in actual logistics operations, when the first user generates a purchase plan document through the purchase planning system, this document cannot be automatically transmitted to the second user's purchase list system. The second user must manually obtain information from other channels and re-enter it, leading to frequent data entry errors. When generating a shipping plan, the third user, unable to obtain accurate purchase document data in real time, needs to perform multiple data verification operations, causing delays in the shipping process. Moreover, this information asymmetry directly triggers document mismatch issues in the receiving stage. When the first user generates a receiving list based on the shipping plan document, inconsistent data versions lead to duplicate processing requirements, significantly increasing business complexity.

[0027] If these issues are not addressed, data inconsistencies between systems will continue to spread as business volume increases, and erroneous data will propagate throughout the supply chain, leading to a continuous deterioration in business processing capabilities. Specifically, increased information redundancy and error rates will weaken the overall reliability of the system, and operating costs will increase due to repetitive processing and error correction operations. Consequently, supply chain responsiveness will decline, and it will be difficult to improve the level of enterprise information management.

[0028] Based on this, embodiments of this application provide a cargo sorting management method, apparatus, equipment, and medium. By sharing documents among users, real-time data sharing and collaboration among all links of the supply chain can be achieved, reducing information asymmetry, improving cargo processing efficiency, and shortening the processing cycle.

[0029] Figure 1 This diagram illustrates the application environment of the cargo arrangement management method provided in this embodiment. (See attached diagram.) Figure 1 This method is applied to a cargo sorting management system. The system includes a terminal 110 and a server 120. The terminal 110 and server 120 are connected via a network. The terminal 110 can be at least one of a mobile phone, tablet, laptop, or vehicle-mounted terminal. The server 120 can be a cloud server or an edge server, implemented using a standalone server or a server cluster composed of several servers. The terminal 110 is used for operations such as generating a purchase plan initiated by a first user, generating a purchase list based on a purchase plan document by a second user, generating a shipping plan based on a purchase document by a third user, and / or generating a receiving list based on a shipping plan document by a first user. Server 120 is used to respond to the purchase plan generation operation initiated by the first user, generate a purchase plan document, and share the purchase plan document with the second user; respond to the second user's purchase list generation operation based on the purchase plan document, generate a purchase document, and share the purchase document with the third user; respond to the third user's delivery plan generation operation based on the purchase document, generate a delivery plan document, and share the delivery plan document with the first user; and respond to the first user's receipt list generation operation based on the delivery plan document, generate a receipt document, and share the receipt document with the second user.

[0030] See Figure 2 In one embodiment, a cargo racking management method is provided, wherein the execution subject of the method is the aforementioned server, including but not limited to steps S201 to S204.

[0031] Step S201: In response to the purchase plan generation operation initiated by the first user, a purchase plan document is generated and shared with the second user.

[0032] The first user refers to the user primarily responsible for generating the purchase plan, receiving the shipping plan documents, and generating the receiving list in the goods placement management process. This user can be an internal purchasing or planning department of the enterprise.

[0033] The purchase plan generation operation refers to the process by which the first user initiates the creation of a goods purchase plan based on business needs. The purchase plan document is the product of the purchase plan generation operation, recording information such as the types and quantities of goods to be purchased, and the estimated arrival time, serving as the basis for subsequent processes.

[0034] The first user can manually input their purchasing needs through the system interface provided by the terminal. For example, they can input the name, quantity, supplier information, and expected delivery date of the goods to be purchased. After receiving this information, the executing entity can organize it and generate a preliminary purchasing plan document. Subsequently, this purchasing plan document can be sent or provided to the second user via email attachment, internal messaging system notification, or directly placed in a shared folder. For example, when the planning department (the first user) determines a purchasing plan for a batch of raw materials, it can enter this plan information into the executing entity, which will automatically generate a purchasing plan document and notify the purchasing department (the second user) for review.

[0035] In step S202, in response to the second user's operation of generating a purchase list for the purchase plan document, a purchase document is generated and shared with the third user.

[0036] The second user refers to the user primarily responsible for generating the purchase order and receiving the receiving documents in the goods placement management process. This user can be an internal purchasing department or logistics execution department of the enterprise.

[0037] The purchase order generation operation refers to the process by which a second user initiates the creation of an actual purchase order based on the purchase plan document. The purchase order document is the product of the purchase order generation operation, recording the details of the actual purchased goods, including information such as the type and quantity of the goods that have arrived.

[0038] Upon receiving the purchase order, the second user can manually verify and enter the actual goods information based on the actual arrival status. For example, after receiving the purchase order, the purchasing department (second user) can input the types and quantities of goods from the purchase order into the executing entity, thereby generating a purchase order. This purchase order can then be shared with the supplier (third user) in a similar manner, such as through internal system notifications or shared links, so that the supplier can prepare the goods.

[0039] Step S203: In response to the third user's operation of generating a delivery plan for the purchase order, a delivery plan document is generated and shared with the first user.

[0040] The third user refers to the user primarily responsible for generating the shipping plan in the cargo scheduling management process. This user can be an external supplier.

[0041] The shipment plan generation operation refers to the process by which a third-party user initiates the creation of a shipment plan based on the purchase order. The shipment plan document is the product of the shipment plan generation operation, recording information such as the type and quantity of goods to be shipped, the estimated shipping time, and the destination, serving as a guide for subsequent logistics operations.

[0042] After obtaining the purchase invoice, the third user can manually create a shipping plan based on customer orders and inventory status. For example, the supplier (third user) manually plans the batches, quantities, and estimated delivery times of goods to be shipped based on customer order requirements and current available inventory, and enters this information into the executing entity to generate a shipping plan document. This shipping plan document can then be shared back to the purchasing or planning department (first user) to track order fulfillment progress and make subsequent adjustments to the purchasing plan.

[0043] Step S204: In response to the first user's operation of generating a receipt list for the shipping plan document, a receipt document is generated and shared with the second user.

[0044] The receiving list generation operation refers to the process by which the first user initiates the creation of the actual receiving list based on the shipping plan document. The receiving document is the product of the receiving list generation operation, recording the details of the actual received goods, including information such as the type and quantity of the received goods.

[0045] Upon receiving the shipping plan document, the first user can manually verify and enter the actual received goods information based on the actual receipt. For example, when the planning department (first user) receives the shipping plan document and the goods, it can input the type and quantity of the received goods into the execution entity to generate a receipt document. This receipt document can then be shared with the purchasing department (second user) for subsequent planning and purchasing management.

[0046] The following example will provide a more detailed explanation of the above technical solution: Suppose a large logistics company needs to manage the inbound and outbound processes of goods in its warehouse. Under traditional management models, the company's planning and purchasing departments, along with suppliers, each use independent systems or paper records, leading to information delays and data inconsistencies. The goods placement management method in this embodiment aims to solve this problem.

[0047] Specifically, firstly, the planning department (the first user) needs to purchase a batch of electronic components. The planner initiates a purchase plan generation process within the executing entity, manually entering information such as the purchase order number, electronic component model, quantity, and expected delivery date. Upon receiving this information, the executing entity automatically generates a purchase plan document, for example, "Purchase Plan Document - 20231026-001". This document is then automatically shared by the executing entity to the purchasing department's (the second user's) system interface, and a notification is sent.

[0048] Next, when the electronic components actually arrive, the purchasing department (second user) generates a purchase order for "Purchase Order Document-20231026-001". The purchasing staff verifies the model and quantity of the actual delivered electronic components and enters this information into the executing entity. Based on this information, the executing entity generates a purchase order, such as "Purchase Order Document-20231026-001-Actual". This purchase order is then automatically shared by the executing entity to the supplier's (third user) system interface so that the supplier's personnel can understand the current inventory status.

[0049] Subsequently, the supplier (third user) receives the purchase order and needs to ship a batch of electronic components from the warehouse. The supplier's personnel respond to the order in the executing entity by generating a shipping plan for "Purchase Order-20231026-001-Actual". Based on the customer order and inventory information, the supplier's personnel manually create a shipping plan, for example, planning to ship 1000 units of electronic component model A and 500 units of model B, and enter the estimated shipping time. After receiving this information, the executing entity generates a shipping plan document, such as "Shipping Plan Document-20231027-001". This shipping plan document is then automatically shared back to the planning department's (first user's) system interface by the executing entity so that the planning department can track order fulfillment.

[0050] Finally, once the company actually receives the batch of electronic components, the planning department (first user) responds by generating a receiving list for "Shipping Plan Document-20231027-001" within the executing entity. The planning personnel provide feedback based on the actual received goods and the shipping plan document, manually entering the model and quantity of the electronic components actually received. Upon receiving this information, the executing entity generates a receiving document, such as "Receiving Document-20231027-001-Actual". This receiving document is then automatically shared by the executing entity to the purchasing department's (second user) system interface, allowing the purchasing department to update inventory records and complete the closed-loop management of the entire goods flow.

[0051] In this example, a seamless connection between purchase plans, actual purchases, delivery plans, and actual receipt information is achieved through a systematic document flow and a multi-user sharing mechanism. Document generation at each stage is based on information from the previous stage, ensuring data consistency and accuracy. Information sharing among different users avoids the "information silos" problem of traditional models, making the information flow throughout the supply chain more efficient and transparent.

[0052] Based on the above examples, the cargo arrangement management method of this embodiment demonstrates significant technological contributions. In the prior art, each business system within an enterprise operates independently, resulting in low information transmission efficiency and difficulty in ensuring data consistency, which in turn affects the responsiveness and accuracy of the overall supply chain. For example, the purchasing department's procurement plan may not be synchronized with the warehouse department in a timely manner, leading to insufficient receiving preparation; the sales department's delivery plan may also deviate due to the failure to obtain accurate inventory information in a timely manner.

[0053] This embodiment effectively solves the aforementioned problems by introducing a structured document flow and multi-user collaboration mechanism. Specifically, starting from the first user generating a purchase plan document and sharing it with the second user, then the second user generating a purchase document and sharing it with the third user, then the third user generating a delivery plan document and sharing it with the first user, and finally the first user generating a receiving document and sharing it with the second user, a complete, closed-loop information flow is formed. This design ensures that the documents in each business link serve as the input basis for the next link, guaranteeing the continuity and accuracy of information.

[0054] Compared to existing technologies where each system maintains data independently, this embodiment breaks down the barriers of "information silos" through mandatory document sharing and circulation. For example, once a purchase order document is generated, it is immediately shared with a second user, enabling the warehouse department to prepare for receiving goods in advance and avoiding delays caused by information lag. Similarly, the generation and sharing of a shipping order document allows the first user to monitor the shipping progress in real time, facilitating subsequent plan adjustments. This integrated management approach significantly improves the collaboration efficiency between departments within the enterprise and reduces error rates and redundant operations caused by information asymmetry.

[0055] Therefore, the cargo sorting management method in this embodiment achieves real-time information sharing and efficient flow by constructing an interconnected business process, thereby optimizing the operational efficiency of the entire supply chain, reducing operating costs, and improving the company's responsiveness to market changes.

[0056] See Figure 3 In one embodiment, the first user includes a first requesting user and a first reviewing user, and the method for generating the purchase plan document includes, but is not limited to, steps S301 to S303.

[0057] Step S301: In response to the plan addition request initiated by the first requesting user, provide a purchase plan demand table.

[0058] Step S302: In response to the plan information entry request initiated by the first requesting user, store the purchase plan information entered by the first requesting user into the purchase plan demand table to obtain the purchase plan information table.

[0059] Step S303: In response to the plan review request initiated by the first review user, upon receiving the review approval information entered by the first review user, a purchase plan document is generated based on the purchase plan information table.

[0060] The first requesting user is typically responsible for initiating business processes, entering preliminary information, or making specific requests, such as the planning department. The first reviewing user, on the other hand, is responsible for reviewing, verifying, and making decisions regarding the information or requests submitted by the first requesting user, such as the purchasing department. This can be configured through a user access control module, assigning different role permissions to different user accounts; or it can be done through organizational structure settings, clearly defining the responsibilities of personnel in different departments or positions.

[0061] When the first requesting user initiates a new plan request, the executing entity will provide a purchase plan requirement form to offer the user a standardized data input interface or template, ensuring the completeness and standardization of the required information. The purchase plan requirement form can be a pre-set spreadsheet template containing all necessary fields, such as product name, quantity, specifications, and expected arrival date; or it can be a dynamically generated form that automatically adjusts fields based on business rules or user selection.

[0062] After the first requesting user enters specific purchase plan information into the purchase plan request form, the executing entity will respond to the entry request, store this information, and form a purchase plan information table, ensuring that the initial purchase plan data is effectively recorded and saved by the executing entity. The storage method can be to write the data into a specific table structure in a database; or to temporarily store the entered information as a temporary file to be processed. The purchase plan information table is the basis for subsequent review and document generation; it contains all the detailed plan content submitted by the first requesting user.

[0063] When the first reviewer initiates a plan review request and enters the approval information, the executing entity generates a formal purchase plan document based on the previously generated purchase plan information table. This ensures that only authorized and confirmed plans can proceed to subsequent stages. The approval information can be a simple confirmation button click, a digital signature, or a text input with review comments. The purchase plan document can be generated either by the executing entity automatically filling data from the purchase plan information table into a preset document template and assigning a unique identifier to the document; or by converting the data from the purchase plan information table into a specific format electronic document, such as a PDF file, and affixing an electronic signature.

[0064] This application's solution refines the original "first user" role into a "first requesting user" and a "first reviewing user," and introduces clearly defined steps for plan addition, information entry, and plan review, constructing a hierarchical and controlled procurement plan generation process. First, the first requesting user initiates the procurement plan and enters detailed information into the procurement plan requirement table, ensuring the initial completeness and accuracy of the data, and generating a procurement plan information table. Subsequently, the first reviewing user examines and verifies this procurement plan information table. Only after receiving approval information will the executing entity generate a formal procurement plan document based on this information table. This mechanism ensures that the procurement plan document undergoes rigorous approval and confirmation before generation, thereby guaranteeing its accuracy, compliance, and authority, providing a reliable foundation for the subsequent sharing of the procurement plan document with second users and the smooth operation of the entire goods placement management process.

[0065] The following is a concrete example to illustrate this. Suppose a company needs to purchase a batch of goods. First, the planner in the planning department (as the first requesting user) logs into the system provided by the executing entity and initiates a "New Purchase Plan" request. A standardized electronic form, namely the Purchase Plan Requirement Form, pops up, which includes mandatory fields such as goods name, model, quantity, supplier, and expected delivery date. The planner enters all the purchase plan information in detail in this form according to the actual needs and submits it. The executing entity saves this entered information as a purchase plan information form pending approval. Subsequently, the purchasing agent in the purchasing department (as the first reviewing user) logs into the system and views this purchase plan information form pending approval. The purchasing agent verifies the goods information, quantity, price, etc., and clicks the "Approved" button after confirming that everything is correct. After receiving the approval information, the executing entity automatically integrates the data in the purchase plan information form, generates a formal purchase plan document with a unique number, and updates its status to "Approved". This purchase plan document is then shared with the warehouse department (the second user) for subsequent purchase list generation operations.

[0066] By employing the aforementioned technical solution, the first user is subdivided into the first requesting user and the first reviewing user, and a process of adding plans, entering information, and reviewing plans is introduced. This application effectively solves the problems of inaccurate data entry, lack of supervision, and insufficient authorization that may occur during the generation of purchase plans. This decentralized and balanced mechanism ensures the accuracy and compliance of purchase plan information, improves the reliability of document generation, and thus lays a solid foundation for subsequent stages such as the generation of purchase lists, delivery plans, and receiving lists, significantly improving the standardization and efficiency of the entire goods placement management process.

[0067] See Figure 4 In one embodiment, the second user includes a second requesting user and a second reviewing user, and the method for generating purchase invoices includes, but is not limited to, steps S401 to S403.

[0068] Step S401: In response to the list addition request initiated by the second requesting user, provide the purchase list requirement table.

[0069] Step S402: In response to the purchase information entry request initiated by the second requesting user, store the purchase list information entered by the second requesting user into the purchase list demand table to obtain the purchase list information table.

[0070] Step S403: In response to the purchase review request initiated by the second review user, upon receiving the review approval information entered by the second review user, a purchase order is generated based on the purchase list information table.

[0071] The second requesting user is primarily responsible for initiating the operation request and entering specific information. For example, the second requesting user could be a purchasing specialist responsible for entering detailed purchase information into the system provided by the executing entity based on the specific content of the purchase plan document. The second reviewing user is primarily responsible for reviewing and approving the information submitted by the second requesting user. For example, the second reviewing user could be a purchasing manager responsible for reviewing the purchase list information entered by the purchasing specialist to ensure that it complies with the purchase contract and company policy.

[0072] This application's solution achieves refined management of purchase order generation by subdividing the second user into a second requesting user and a second reviewing user, and introducing a clear request, input, and review process. Specifically, the second requesting user first initiates a list addition request based on the purchase plan document. The executing entity then provides a purchase list requirement form to guide the user in entering detailed purchase information. This entered purchase list information is stored and forms a purchase list information table as preliminary data pending review. Subsequently, the second reviewing user intervenes and initiates a purchase review request for this purchase list information table. Only when the second reviewing user explicitly enters the approval information will the executing entity generate the final formal purchase order based on the verified purchase list information table. This collaborative model effectively separates the creation of the purchase list from the generation of the final document, ensuring that the content of the purchase order has been checked and confirmed by at least two layers of personnel before its formal generation. This not only improves the accuracy of data entry, but also provides double protection for the compliance and reliability of purchase documents by introducing an audit process. This effectively avoids errors or omissions that may be caused by a single user's operation, making the purchase process in the entire goods placement management process more rigorous and controllable.

[0073] The following is a concrete example. Suppose a large retail company receives a purchase order, and the executing entity triggers the process of generating a purchase list. As the second requesting user, a purchasing agent from the purchasing department logs into the system provided by the executing entity and initiates a list creation request. The executing entity then presents the purchasing agent with a purchase list request form, which may be pre-filled with some information from the purchase order, such as supplier names and expected delivery batches. Based on the actual purchase order and inventory needs, the purchasing agent enters detailed purchase list information in the request form, including the SKU of each product, purchase quantity, unit cost, and expected warehouse. After completion, this information is stored as a purchase list information table and automatically submitted to their superior, the purchasing manager, who acts as the second reviewer. Upon receiving the pending review notification, the purchasing manager logs into the system and views the purchase list information table. The purchasing manager carefully verifies that the product information, quantities, and prices in the list are consistent with the purchase contract and assesses its impact on inventory and sales plans. Once everything is confirmed to be correct, the purchasing manager will initiate a purchase approval request and enter the approval information into the system provided by the executing entity. After receiving this approval information, the executing entity will immediately generate a formal purchase order based on the purchase list information table, update its status to "approved," and then share this purchase order with the third user responsible for the shipping operation.

[0074] The aforementioned technical solution subdivides the second user into a second requesting user and a second reviewing user, and introduces a clear request, input, and review process. This effectively solves the problems of inaccurate purchase list data and lack of effective supervision that may result from single-user operation. This decentralized and balanced mechanism makes the creation of purchase lists and the generation of purchase documents more transparent and controllable, significantly improving the accuracy and reliability of purchase documents. Simultaneously, the mandatory review process ensures that all purchase information is reviewed and approved by professionals before it officially takes effect, thereby reducing the risks caused by human error or non-compliant operations and providing a solid data foundation and process guarantee for the smooth operation of the entire goods placement management process.

[0075] See Figure 5 In one embodiment, the method for generating a shipping plan document includes, but is not limited to, steps S501 to S504.

[0076] Step S501: In response to the list addition request initiated by the third user, provide a shipping list requirement table.

[0077] Step S502: When a third user initiates an information adjustment request, store the order number adjustment information and / or order split information entered by the third user into the purchase order to obtain the shipment adjustment order.

[0078] Step S503: In response to the information entry request initiated by the third user, the packing information of the target document is adjusted based on the packing change information entered by the third user, and a shipping plan confirmation form is obtained.

[0079] When a shipping adjustment document is generated, the target document is the shipping adjustment document; otherwise, the target document is the purchase document.

[0080] Step S504: Generate a shipping plan document based on the shipping plan confirmation form.

[0081] A new shipment request refers to a third-party user's initiative to create a new shipment manifest. Upon receiving this request, the executing entity provides a shipment manifest request form. This form is a pre-defined template or interface for collecting shipment-related information. Its purpose is to guide the user to input necessary data, ensuring the accuracy of subsequent shipment plans. For example, the shipment manifest request form could be a blank spreadsheet containing fields for goods information, quantity, destination, etc.; or an interactive web interface providing dropdown menus and input boxes for the user to select and fill in.

[0082] An information adjustment request refers to an instruction issued by a third-party user during the shipping plan formulation process when they find that information in the original purchase order needs to be modified or refined. Upon receiving this request, the executing entity stores the order number adjustment information and / or order splitting information entered by the third-party user into the original purchase order, thereby generating a new shipping adjustment document. Order number adjustment information can modify, merge, or associate existing order numbers; for example, merging multiple small orders into one large shipping order number, or splitting a large order into multiple shipping batches. Order splitting information focuses more on splitting goods in an original order into different shipping batches or destinations. In this way, the executing entity can flexibly handle order changes that may occur during actual shipping. For example, when a large order needs to be shipped in batches, it can be split into multiple sub-orders for management; or when multiple small orders need to be combined for shipment to optimize logistics costs, order number adjustments can be made.

[0083] An information entry request refers to an instruction issued by a third-party user after confirming order adjustments (if any), to further plan the specific packing method for the goods. Upon receiving this request, the executing entity will modify the goods packing information in the target document based on the packing change information provided by the third-party user. Packing change information may include the packaging method, box type, stacking method, container type, etc., aiming to optimize space utilization and transportation safety. The target document is dynamically determined: if a shipping adjustment document has already been generated, the adjusted document will be used as the basis for adjusting the packing information; if no order adjustment has been made, the original purchase order will be used directly as the basis. After the packing information is adjusted, the executing entity will generate a shipping plan confirmation form, which records in detail the final shipment list, quantity, packaging, and packing plan, providing an accurate basis for subsequent actual packing and shipping operations.

[0084] The shipping plan confirmation form is the final shipping plan after a series of adjustments and confirmations. Based on all the detailed information in the confirmation form, the executing entity will automatically or semi-automatically generate a shipping plan document. This shipping plan document is a formal document that guides the actual shipping operations. It contains all necessary shipping instructions, such as shipping time, location, carrier, cargo details, and packing details. Its purpose is to standardize the shipping process, ensuring that all relevant parties (such as warehouse operators and transportation companies) receive consistent and accurate shipping information, thereby improving shipping efficiency and accuracy.

[0085] This application's solution introduces a flexible document adjustment and packing information adjustment mechanism, enabling third-party users to fully address various changes in actual business operations when generating shipping plan documents. Specifically, when a third-party user needs to formulate a shipping plan, they first initiate a list addition request to obtain a shipping list requirement table, laying the foundation for subsequent information entry and adjustments. Based on this, considering that actual shipments may differ from the original purchase order, this solution allows third-party users to initiate information adjustment requests, entering order number adjustment information and / or order splitting information, and storing it in the purchase order to obtain a shipping adjustment document. This shipping adjustment document reflects the actual shipping needs at the order level, such as merging multiple small orders for shipment or splitting a large order for shipment. Subsequently, the third-party user can further initiate information entry requests, adjusting the packing information of the target document (i.e., the adjusted shipping adjustment document or the original purchase order) based on the entered packing change information. This adjustment optimizes the packaging and loading methods of goods to adapt to different transportation conditions or container types, ultimately forming a detailed shipping plan confirmation table. Finally, based on this shipping plan confirmation form that has undergone multiple verifications and adjustments, the executing entity generates the final shipping plan document. The entire process, through phased adjustments and confirmations, ensures the accuracy, flexibility, and operability of the shipping plan, effectively connects the information flow between receiving and shipping, and provides precise guidance for subsequent actual logistics operations.

[0086] The following is a concrete example to illustrate this. Suppose a company receives a purchase order containing 1000 units of product A and 500 units of product B. A third user (e.g., the company's supplier), while preparing to ship the goods, discovers that the shipment needs to be sent to two different destinations. One destination requires that products A and B be packed separately, while the other destination requires that some products A be combined with another small order for shipment. First, the third user initiates a shipment list addition request through the system provided by the executing entity, which then provides a blank shipment list request form. Next, the third user initiates an information adjustment request. They split the 1000 units of product A from the original purchase order into two parts: 500 units of product A are sent to destination one, and the other 500 units of product A are combined with a separate order for product C and sent to destination two. At the same time, all 500 units of product B are sent to destination one. The executing entity stores these tracking number adjustments and order splitting information into the original purchase invoice, generating a shipping adjustment document that specifies the goods list destined for destination one (500 units of product A, 500 units of product B) and the goods list destined for destination two (500 units of product A, and an order for product C). Subsequently, a third user initiates an information entry request, entering packing change information based on the actual container dimensions and cargo characteristics. For example, for goods destined for destination one, product A is specified to be packaged in standard cardboard boxes, and product B to be stacked on pallets; for goods destined for destination two, products A and C are specified to be mixed in boxes, and the stacking method is optimized to maximize container utilization. Based on these packing change information, the executing entity adjusts the packing information in the shipping adjustment document, obtaining a detailed shipping plan confirmation table, including specific cargo details, packaging methods, box types, quantities, and loading schemes for each destination. Finally, based on this shipping plan confirmation table, the executing entity automatically generates two independent shipping plan documents for different destinations and shares them with the first user.

[0087] Through the aforementioned technical solution, this application introduces flexible document adjustment and packing information adjustment functions during the process of generating shipping plan documents by third-party users. This allows the shipping plan to fully consider the complexity and variability of actual shipping scenarios, such as order merging, splitting, and optimization of packing methods. Compared to generating shipping plans directly based on original purchase invoices, this solution significantly improves the accuracy and operability of shipping plans, effectively avoiding logistics delays or errors caused by information mismatches. Simultaneously, through refined packing information adjustments, transportation space utilization can be optimized, logistics costs reduced, and cargo transportation security improved. This flexible adjustment mechanism makes the entire cargo placement management process more aligned with actual business needs, improving overall operational efficiency and response speed.

[0088] In some embodiments, based on packing change information entered by a third user, the packing information of the target document is adjusted, including: querying the goods type information and goods quantity information of the target document; based on the goods type information and goods quantity information, parsing the data field types involved in the changed packing information and assessing the impact level of the change; based on the impact level of the change, matching the corresponding operation path from a preset rule base to configure the packing information of the goods in the target document and obtaining a shipping plan confirmation table. The data field types include at least low-sensitivity fields and high-sensitivity fields, and the impact level of the change is dynamically generated based on a combination rule of the data field types, goods type information, and goods quantity information.

[0089] Querying the goods type and quantity information of the target document aims to obtain the basic attributes of the goods in the document to be adjusted, providing foundational data for subsequent analysis and evaluation. Specifically, the executing entity can retrieve the corresponding goods type (e.g., fragile items, liquids, large items, small items, etc.) and quantity from the goods master data table by calling the database interface based on the unique identifier of the target document. Alternatively, it can synchronize data with a warehouse management system (WMS) or enterprise resource planning (ERP) system to obtain the detailed type classification and specific quantity of each item in the target document in real time.

[0090] Analyzing the data field types involved in the changed packing information and assessing the impact level of the change are crucial steps in identifying the specific content of the user's requested change and comprehensively judging the potential impact of the change based on the sensitivity of the field, as well as the characteristics and quantity of the goods. Data field types include at least low-sensitivity fields and high-sensitivity fields. The impact level of the change is dynamically generated based on a combination rule of data field type, goods type information, and goods quantity information. For example, a field sensitivity dictionary can be preset, defining "box type" and "packaging material" as low-sensitivity fields, and "packing quantity," "volume," and "weight" as high-sensitivity fields. When a change request is received, the executing entity first identifies the fields involved in the change, and then dynamically calculates the impact level of the change by combining preset combination rules (e.g., high-sensitivity field change + fragile items + large quantity = high impact level; low-sensitivity field change + ordinary goods + small quantity = low impact level). As another implementation method, the executing entity can use a machine learning model to learn and predict the impact level of changes under different combinations of data field types, goods type information, and goods quantity information by analyzing historical change data, goods attributes, and the final packing results. For example, changes in the packing method for hazardous materials, even seemingly low-sensitivity fields, may be assessed as having a high impact level.

[0091] Based on the impact level of the change, the corresponding operation path is matched from a pre-set rule base to configure the packing information of the goods in the target document, resulting in a shipping plan confirmation form. This ensures that, based on the assessed impact level, the executing entity can automatically select or recommend the most appropriate processing flow or operation instructions, guaranteeing that the adjustment of packing information is both compliant and efficient. The rule base stores operation paths corresponding to different impact levels. For example, low-impact level changes can directly and automatically update packing information; medium-impact level changes may require triggering a manual review process; high-impact level changes may require reverting to an earlier stage of the shipping plan for replanning and notifying relevant personnel. This rule base can be a decision tree or expert system, containing detailed operation guidelines for different change impact levels, goods characteristics, and business scenarios. For example, when the impact level is "high" and the goods are "fragile," the operation path might include "mandatory use of specific shockproof packaging," "recalculation of box filling," and "generation of special packing instructions," etc.

[0092] This application's solution, when a third user initiates an information adjustment request, first queries the target document's cargo type and quantity information, providing foundational data for subsequent intelligent decision-making. Subsequently, the executing entity parses the data field types involved in the changed packing information and, combined with the cargo type and quantity information, dynamically generates a change impact level. This impact level comprehensively considers the sensitivity of the changed content and the inherent characteristics of the cargo, thereby quantifying the potential risks. Finally, based on this change impact level, the executing entity matches the corresponding operation path from a pre-set rule base to intelligently configure the cargo packing information in the target document and generate a shipping plan confirmation table. This mechanism transforms the adjustment of packing information from a simple information update into an integration of risk assessment and intelligent decision-making, ensuring the accuracy and compliance of the adjustment process. In this way, this application effectively solves the problem of how to efficiently and accurately adjust according to packing change information during the shipping plan generation process, while fully considering the characteristics of different goods and the sensitivity of changes, thereby improving the reliability of the shipping plan.

[0093] The following is a concrete example. Suppose a third user needs to adjust the packing information on a shipping document. The executing entity first queries the target document to obtain the information on the type of goods (e.g., "precision instruments", "general merchandise") and the quantity of goods (e.g., "10 pieces", "1000 units"). If the user requests to change the "packing box size" and "quantity per box", the executing entity will identify "packing box size" as a low-sensitivity field and "quantity per box" as a high-sensitivity field. When the type of goods is "precision instruments" and the quantity is "10 pieces", and the user changes the "quantity per box" (a high-sensitivity field), the executing entity will dynamically generate a "high-impact level" according to preset combination rules, because changes to sensitive goods and high-sensitivity fields may pose significant risks. Based on this "high-impact level", the executing entity will match the corresponding operation path from the rule base. For example, this path might include: automatically triggering the quality department's review process, mandating the use of shockproof packaging materials, recalculating and verifying whether the new packing scheme meets transportation safety standards, and marking this item as "requires special handling" in the shipping plan confirmation table. Conversely, if the goods type is "general merchandise," the quantity is "1000 units," and the user only changes the "packaging box size" (a low-sensitivity field), the executing entity might generate a "low-impact level." In this case, the corresponding operation path might only be: automatically update the packing box size information, automatically recalculate the total volume and weight, and directly update the shipping plan confirmation form. In this way, the executing entity can intelligently select the appropriate processing flow based on the specific changes and characteristics of the goods, ultimately generating an accurate shipping plan confirmation form.

[0094] Through the above technical solution, this application enables intelligent risk assessment and processing of packing change information, significantly reducing the risk of errors or improper operations during packing information adjustments. This ensures that sensitive changes or changes involving critical goods receive thorough review and appropriate processing, while routine changes are completed efficiently. Consequently, the accuracy and reliability of shipping plans are improved, the potential for damage or misdelivery during transportation is minimized, and the overall logistics process is optimized by applying customized processing procedures based on specific scenarios.

[0095] See Figure 6 In one embodiment, the first user includes a first requesting user and a first reviewing user, and the method for generating a receipt document includes, but is not limited to, steps S601 to S603.

[0096] Step S601: In response to the new receipt request initiated by the first requesting user, provide a receipt demand table.

[0097] Step S602: In response to the receiving information entry request initiated by the first requesting user, store the receiving information entered by the first requesting user into the receiving demand table to obtain the receiving information table.

[0098] Step S603: In response to the receiving verification request initiated by the first verification user, upon receiving the verification approval information entered by the first verification user, a receiving document is generated based on the receiving information table.

[0099] When the first requesting user needs to initiate a goods receipt operation, the executing entity will respond to their new goods receipt request and provide a goods receipt request form. The goods receipt request form is an interface or template used to collect and record relevant goods receipt information. It guides the user to input the necessary data according to a preset format, ensuring the completeness and standardization of the information. For example, the executing entity can display a preset electronic form containing fields to be filled in, such as the shipping plan document number, expected receipt date, goods type, and quantity; alternatively, the executing entity can automatically pre-fill some information based on the shipping plan document and provide editable fields for the first requesting user to confirm or modify.

[0100] After the user enters the actual received goods information in the receipt request form, the executing entity will respond to the entry request, store this information, and form a receipt information table. The receipt information table is a data set containing actual receipt details, and it forms the basis for subsequent review and generation of receipt documents. For example, after the user completes the form on the interface and clicks the "Save" button, the executing entity writes the data into the corresponding receipt information record in the database; alternatively, the user's input data can be saved in real time, and a temporary receipt information table can be automatically generated after the user completes all necessary fields.

[0101] When the first reviewer initiates a goods receipt review request, the executing entity retrieves the goods receipt information form previously entered by the requesting user for review. Once the first reviewer confirms the information is correct and enters the approval information, the executing entity will officially generate a goods receipt document based on this information form. The goods receipt document is a formal document serving as a business voucher, marking the completion of the goods receipt process. For example, after logging into the system provided by the executing entity, the first reviewer finds the goods receipt information form to be reviewed in the to-do list, views the details, selects "Approve" or "Reject," and enters their review comments. Upon receiving the "Approve" instruction, the executing entity triggers the goods receipt document generation logic; alternatively, a review interface can be provided, displaying the various contents of the goods receipt information form and allowing the reviewer to annotate or modify it. After approval, the executing entity automatically converts the data in the goods receipt information form into a standard format goods receipt document and archives it.

[0102] This application's solution implements a mechanism that separates the roles of the first requesting user and the first reviewing user, thereby enabling refined management of the receipt document generation process. First, the first requesting user initiates a new receipt request, and the executing entity provides a standardized receipt requirement form to ensure the accurate entry of receipt information. After the first requesting user enters the actual receipt information, the executing entity stores it as a receipt information table. Subsequently, the first reviewing user independently reviews this receipt information table. Only after the first reviewing user confirms the information is accurate and enters the approval information will the executing entity formally generate the receipt document based on the reviewed receipt information table. This step-by-step collaboration and dual-confirmation mechanism effectively avoids errors and risks that may arise from single-user operations, significantly improving the accuracy, reliability, and compliance of receipt information and processes. By decomposing the receipt process into request, entry, storage, and review stages, and clearly defining the responsible parties for each stage, the entire process from information collection to final document generation is ensured to be traceable and controllable.

[0103] In one specific implementation, when a batch of goods arrives at the warehouse, the planner (as the first requesting user) initiates a new receiving request. The executing entity then presents them with an electronic receiving request form, pre-filled with goods information from the shipping plan document, such as supplier, order number, and expected quantity. The warehouse manager, based on the actual arrival, enters detailed information such as the actual received quantity, batch number, and quality inspection results into the receiving request form and submits it. The executing entity saves this entered information as a receiving information form awaiting review. Subsequently, the planning manager (as the first reviewing user) views this receiving information form in their to-do list. The planning manager carefully verifies that the receiving information matches the shipping plan and the actual goods; after confirming accuracy, they click the "Approved" button. Upon receiving the approval instruction, the executing entity automatically generates a formal receiving document, updates its status to "Completed," and shares the receiving document with a second user (e.g., the purchasing or finance department) for further processing.

[0104] The aforementioned technical solution subdivides the first user into a first requesting user and a first reviewing user, and introduces a mechanism that separates the entry and review of receipt information. This makes the entry and confirmation process of receipt information more rigorous and standardized, effectively avoiding the risks of errors or fraud that may arise from single-user operations. The generation of receipt documents is no longer a simple information entry, but rather a process that undergoes double confirmation, significantly improving the accuracy and reliability of receipt data and the compliance of the entire goods management process. This decentralized and balanced design ensures the quality of key data in the receipt process, providing a solid foundation for subsequent processes such as inventory management and financial settlement, thereby improving overall operational efficiency and data security.

[0105] In some embodiments, the cargo arrangement management method further includes: displaying the warehouse ledger when a ledger query request initiated by a first user is received; and exporting the target demand information indicated by the information export request when an information export request initiated by the first user is received.

[0106] This application's solution introduces ledger query and information export functions, enabling primary users to proactively acquire and utilize key data. When a primary user initiates a ledger query request, the executing entity will summarize and display detailed warehouse inventory information in real time, including the current quantity, location, and historical flow records of various goods. This allows primary users to monitor warehouse dynamics at any time and promptly identify and resolve potential inventory issues. Simultaneously, when a primary user initiates an information export request, the executing entity will accurately filter the required information from the vast amount of business data according to the user's specified needs and export it in a standard format. For example, a primary user can export all shipping plan documents for a specific time period for sales analysis or reconciliation with the financial system. The introduction of these functions allows primary users not only to participate in each stage of the goods placement process but, more importantly, to comprehensively monitor and deeply analyze the operation of the entire supply chain, thereby assisting them in making more scientific and timely decisions.

[0107] The following example illustrates this. Assume the above-described goods placement management method operates within an integrated supply chain management platform. The first user, as the head of the planning department, needs to regularly monitor the current warehouse inventory and analyze historical shipping data. Upon logging into the platform, this user can click the "Warehouse Ledger Query" button under the "Inventory Management" module. The system will then display a real-time table containing details of all in-stock goods, listing the name, SKU, current inventory, warehouse location, most recent inbound date, and most recent outbound date for each item. The user can then filter the data to view inventory for specific product categories. Furthermore, for monthly sales analysis, the user needs to retrieve all shipping plan documents from the previous month. This user can access the "Data Reports" module, select the "Export Shipping Plan Documents" option, and set the export time range to the previous month. Upon receiving this request, the system will quickly extract all matching document information from the database, including shipping order number, customer name, goods details, quantity, and shipping date, and generate an Excel file for the user to download.

[0108] Through the aforementioned technical solution, this application provides the first user with crucial data query and export capabilities based on the existing cargo arrangement management process. Specifically, by responding to the first user's ledger query request and displaying the warehouse ledger, the first user can grasp the warehouse's inventory dynamics and cargo status in real time and intuitively, greatly improving information transparency and avoiding decision-making errors caused by information lag or inaccuracy. Simultaneously, by responding to the first user's information export request and exporting target demand information, the first user can flexibly obtain the necessary business data, facilitating data analysis, report generation, or data interaction with other systems, thereby significantly improving data utilization efficiency and management flexibility. The introduction of these functions not only enables efficient execution of various business processes but also provides the first user with powerful data support and decision-making assistance, optimizing the overall operational efficiency and responsiveness of the supply chain.

[0109] See Figure 7 This application also provides a cargo racking management device that can implement the above-mentioned cargo racking management method. The device includes: The first module 701 is used to respond to the purchase plan generation operation initiated by the first user, generate a purchase plan document, and share the purchase plan document with the second user; The second module 702 is used to respond to the second user's operation of generating a purchase list for the purchase plan document, generate a purchase document, and share the purchase document with the third user; The third module 703 is used to respond to the third user's operation of generating a delivery plan for the purchase order, generate a delivery plan document, and share the delivery plan document with the first user. The fourth module 704 is used to respond to the first user's operation of generating a receipt list for the shipping plan document, generate a receipt document, and share the receipt document with the second user.

[0110] The specific implementation method of the cargo racking management device is basically the same as the specific implementation method of the cargo racking management method described above, and will not be repeated here.

[0111] Figure 8 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application.

[0112] The following reference Figure 8 To describe an electronic device 800 according to such an embodiment of the present disclosure. Figure 8 The electronic device 800 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

[0113] like Figure 8As shown, the electronic device 800 is presented in the form of a general-purpose computing device. The components of the electronic device 800 may include, but are not limited to: at least one processing unit 810, at least one storage unit 820, a bus 830 connecting different system components (including storage unit 820 and processing unit 810), a display unit 840, etc.

[0114] The storage unit stores program code, which can be executed by the processing unit 810, causing the processing unit 810 to perform the steps described in the above-described cargo arrangement management method section of this specification according to various exemplary embodiments of this disclosure.

[0115] Storage unit 820 may include a readable medium in the form of a volatile storage unit, such as random access memory (RAM) 8201 and / or cache memory 8202, and may further include a read-only memory (ROM) 8203.

[0116] The storage unit 820 may also include a program / utility 8204 having a set (at least one) of program modules 8205, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0117] Bus 830 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0118] Electronic device 800 can also communicate with one or more external devices 800' (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 800, and / or with any device that enables electronic device 800 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 850. Furthermore, electronic device 800 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 860. Network adapter 860 can communicate with other modules of electronic device 800 via bus 830. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0119] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.

[0120] The cargo sorting management method, apparatus, equipment, and medium provided in this application introduce a structured document flow and multi-user collaboration mechanism. Starting with the first user generating a purchase plan document and sharing it with the second user, then the second user generating a purchase document and sharing it with the third user, then the third user generating a shipping plan document and sharing it with the first user, and finally the first user generating a receiving document and sharing it with the second user, a complete, closed-loop information flow is formed. This ensures that documents from each business link serve as input for the next link, guaranteeing information continuity and accuracy. Therefore, by sharing documents and circulating them among users, the barriers of "information silos" are broken down, achieving real-time information sharing and efficient flow. This optimizes the operational efficiency of the entire supply chain, reduces operating costs, enables real-time data sharing and collaboration across all links of the supply chain, reduces information asymmetry, improves cargo handling efficiency, and shortens processing cycles.

[0121] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, or network device, etc.) to execute the methods described above according to the embodiments of this disclosure.

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

[0123] Computer-readable storage media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable storage medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transfer a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0124] Those skilled in the art will understand that the above modules can be distributed in the device as described in the embodiments, or they can be modified accordingly and placed in one or more devices that are unique to this embodiment. The modules in the above embodiments can be combined into one module, or they can be further divided into multiple sub-modules.

[0125] Exemplary embodiments of this disclosure have been specifically shown and described above. It should be understood that this disclosure is not limited to the detailed structures, arrangements, or implementations described herein; rather, this disclosure is intended to cover various modifications and equivalent arrangements contained within the spirit and scope of the appended claims.

Claims

1. A method for managing cargo arrangement in containers, characterized in that, include: In response to the purchase plan generation operation initiated by the first user, a purchase plan document is generated and shared with the second user; In response to the second user's operation of generating a purchase list for the purchase plan document, a purchase document is generated and shared with the third user; In response to the third user's operation of generating a shipping plan for the purchase order, a shipping plan document is generated and shared with the first user; In response to the first user's operation of generating a receipt list for the shipping plan document, a receipt document is generated and shared with the second user.

2. The cargo arrangement management method according to claim 1, characterized in that, The first user includes a first requesting user and a first approving user. The step of generating a purchase plan document in response to the purchase plan generation operation initiated by the first user includes: In response to the first requesting user's request to add a plan, a purchase plan demand table is provided; In response to the first requesting user's request to enter plan information, the purchase plan information entered by the first requesting user is stored in the purchase plan demand table to obtain the purchase plan information table; In response to the plan review request initiated by the first review user, upon receiving the review approval information entered by the first review user, the purchase plan document is generated based on the purchase plan information table.

3. The cargo arrangement management method according to claim 1, characterized in that, The second user includes a second requesting user and a second approving user. The step of generating a purchase order in response to the second user's purchase plan document includes: In response to the second requesting user's request to add a list, a purchase list requirement table is provided; In response to the purchase information entry request initiated by the second requesting user, the purchase list information entered by the second requesting user is stored in the purchase list demand table to obtain the purchase list information table; In response to the purchase review request initiated by the second review user, upon receiving the review approval information entered by the second review user, the purchase order is generated based on the purchase list information table.

4. The cargo arrangement management method according to claim 1, characterized in that, The step of generating a shipping plan document in response to the third user's shipping plan generation operation on the purchase order includes: In response to the list addition request initiated by the third user, a shipping list requirement table is provided; When the third user initiates an information adjustment request, the order number adjustment information and / or order split information entered by the third user are stored in the purchase order to obtain the shipment adjustment order; In response to the information entry request initiated by the third user, the packing information of the target document is adjusted based on the packing change information entered by the third user to obtain a shipping plan confirmation table; when the shipping adjustment document is generated, the target document is the shipping adjustment document, otherwise, the target document is the purchase document; Based on the shipping plan confirmation form, the shipping plan document is generated.

5. The cargo arrangement management method according to claim 4, characterized in that, The adjustment of packing information on the target document based on the packing change information entered by the third user includes: Query the cargo type and quantity information of the target document; Based on the cargo type information and the cargo quantity information, the data field types involved in the changed packing information are analyzed, and the impact level of the change is assessed; the data field types include at least low-sensitivity fields and high-sensitivity fields, and the impact level of the change is dynamically generated based on the combination rules of the data field types, the cargo type information, and the cargo quantity information; Based on the impact level of the change, the corresponding operation path is matched from the preset rule base to configure the packing information of the goods in the target document, and the shipping plan confirmation table is obtained.

6. The cargo arrangement management method according to claim 1, characterized in that, The first user includes a first requesting user and a first approving user. The step of generating a receiving document in response to the first user's receiving list generation operation on the shipping plan document includes: In response to the first requesting user's request to add a receipt, a receipt demand table is provided; In response to the first requesting user's request to enter receipt information, the receipt information entered by the first requesting user is stored in the receipt demand table to obtain the receipt information table; In response to the receiving verification request initiated by the first verification user, upon receiving the verification approval information entered by the first verification user, the receiving document is generated based on the receiving information table.

7. The cargo arrangement management method according to any one of claims 1 to 6, characterized in that, The cargo arrangement management method also includes: Upon receiving the ledger query request initiated by the first user, the warehouse ledger is displayed; Upon receiving an information export request initiated by the first user, the target requirement information indicated by the information export request is exported.

8. A cargo sorting and management device, characterized in that, include: The first module is used to respond to the purchase plan generation operation initiated by the first user, generate a purchase plan document, and share the purchase plan document with the second user; The second module is used to generate a purchase order in response to the second user's purchase list generation operation on the purchase plan document, and share the purchase order with the third user; The third module is used to respond to the third user's operation of generating a delivery plan for the purchase order, generate a delivery plan document, and share the delivery plan document with the first user. The fourth module is used to generate a receiving document in response to the first user's receiving list generation operation on the shipping plan document, and to share the receiving document with the second user.

9. An electronic device, characterized in that, The electronic device includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the cargo arrangement management method according to any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the cargo container management method according to any one of claims 1 to 7.

Images