Warehouse in-out process automatic arrangement method and system

Abstract

The application relates to a warehouse in-out warehouse process automatic arrangement method and system, the method comprising: creating a allocation management sheet, automatically constructing a related delivery sheet; after a source warehouse node executes a delivery job according to the delivery sheet, changing the state of the delivery sheet into a delivery completion state, and generating a record in the related allocation management sheet; according to a preset period, scanning all records in the allocation management sheet, when the record corresponding delivery sheet is in the delivery completion state and has no corresponding incoming sheet, automatically constructing an incoming sheet associated with the record; after a target warehouse node executes an incoming job according to the incoming sheet, ending the allocation process of the related allocation management sheet. Through the application, the problem that the incoming process cannot be automatically triggered in the related art can be solved.

Description

Technical Field

[0001] This application relates to the field of warehousing and inbound technology, and in particular to a method and system for automatically arranging warehousing and inbound processes. Background Technology

[0002] In the field of warehousing and logistics management, material transfer between different warehousing nodes is a high-frequency business that ensures production continuity. Improving the automation level of the transfer process, shortening the connection time from outbound to inbound, and ensuring the consistency and synchronization efficiency of material data between independent warehousing nodes are key areas for continuous improvement in this field.

[0003] In related technologies, when the source and target warehouse nodes deploy their own independent warehouse management systems, an interface-based interface model is often used. In this model, after completing the outbound operation, the source warehouse node sends the outbound order information to the target warehouse node via the interface. The creation of the inbound order is manually executed by the operator at the target warehouse node after confirming that the goods have actually been shipped. The drawback of this approach is that the triggering of the inbound process relies entirely on manual judgment and operation, and cannot be automatically initiated.

[0004] There is currently no effective solution to the problem that the warehousing process cannot be automatically triggered in related technologies. Summary of the Invention

[0005] This application provides a method and system for automatically arranging warehouse inbound and outbound processes to solve the problem that the inbound process cannot be automatically triggered in related technologies.

[0006] Firstly, this application provides a method for automatically arranging warehouse inbound and outbound processes, including:

[0007] Create a transfer management order and automatically construct the associated outbound order; after the source warehouse node executes the outbound operation based on the outbound order, change the status of the outbound order to the outbound completed state and generate a record in the associated transfer management order;

[0008] According to a preset cycle, all records in the transfer management order are scanned. When the outbound order corresponding to the record is in the outbound completed state and there is no corresponding inbound order, the inbound order associated with the record is automatically constructed.

[0009] After the target storage node performs the receiving operation according to the receiving order, the transfer process of the associated transfer management order ends.

[0010] In some embodiments, the creation of a transfer management order and the automatic construction of an associated outbound order includes:

[0011] Based on the source storage node, the target storage node, and the material details of the materials to be transferred, create the transfer management order;

[0012] Perform compliance verification on the source storage node and the target storage node;

[0013] After the compliance verification is passed, material information pre-synchronization is performed on the material details and the target storage node;

[0014] The outbound order is automatically generated based on the source warehouse node and the material details;

[0015] The outbound type of the outbound order is marked as transfer outbound, and the status is set to pending operation;

[0016] The outbound order number of the outbound order is filled back into the transfer management order to establish the association between the outbound order and the transfer management order.

[0017] In some further embodiments, the method further includes:

[0018] Based on the material category, the material details of the materials to be allocated are grouped.

[0019] Based on the material details of each group, the corresponding source storage node, and the corresponding target storage node, create the transfer management order corresponding to the material details of each group.

[0020] In some further embodiments, the step of performing material information pre-synchronization on the material details and the target warehousing node after the compliance verification is passed includes:

[0021] Iterate through each material record in the material details;

[0022] By querying the material code of the source storage node, the corresponding material master data is retrieved, and the corresponding external code is determined based on the material master data;

[0023] Based on the external code, query the corresponding material information in the target storage node;

[0024] When the corresponding material information is found, the material code corresponding to the material information in the target storage node is obtained;

[0025] If the corresponding material information cannot be found, an external code corresponding to the material information is added to the target storage node;

[0026] In the target storage node, the material information is synchronized according to the material code or the newly added external code to create the material master data corresponding to the material information.

[0027] In some further embodiments, after the source warehouse node executes the outbound operation based on the outbound order, changing the status of the outbound order to the outbound completed state and generating a record in the associated transfer management order includes:

[0028] At the source warehouse node, an outbound operation is performed based on the outbound order;

[0029] After the outbound operation is completed, the status of the outbound order is changed to the outbound completed status;

[0030] Based on the association between the outbound order and the transfer management order, the record is generated in the transfer management order; the record indicates that the outbound order has been changed to the outbound completion state.

[0031] In some embodiments, the step of scanning all records in the transfer management order according to a preset period, and automatically constructing an inbound order associated with the record when the corresponding outbound order is in an outbound completed state and there is no corresponding inbound order, includes:

[0032] The timed scanning orchestrator scans the transfer management order according to the preset cycle, determines the target record, and reads the outbound order and corresponding outbound details associated with the target record; wherein, the timed scanning orchestrator is set independently of the source storage node and the target storage node;

[0033] Based on the outbound order and the outbound details, the inbound order is automatically generated, and the inbound order number corresponding to the inbound order is backfilled into the transfer management order.

[0034] In further embodiments, the timed scanning orchestrator scans the transfer management order according to the preset period, identifies the target record, and reads the outbound order and corresponding outbound details associated with the target record, including:

[0035] The transfer management order is scanned page by page, and each scan retrieves no more than a preset number of records;

[0036] Among the records obtained this time, the records whose corresponding outbound orders are in the outbound completed state and which have no corresponding inbound orders are identified as the target records.

[0037] In some further embodiments, the step of automatically constructing the inbound order based on the outbound order and the outbound details includes:

[0038] Construct the entry header of the entry order, set the entry type of the entry order to transfer entry, set the upstream order number of the entry order to the outbound order number of the outbound order, set the warehouse code of the entry order to the code of the target storage node, and inherit personnel information from the outbound order;

[0039] Based on the outbound details, construct the inbound details of the inbound order, and assign a serial number to each inbound detail.

[0040] In some embodiments, the step of ending the transfer process of the associated transfer management order after the target storage node performs the receiving operation according to the receiving order includes:

[0041] After the target storage node performs the inbound operation according to the inbound order, the status of the inbound order is changed to "inbound".

[0042] Based on the status of the outbound order and the inbound order associated with the transfer management order, the transfer status of the transfer management order is deduced through state machine mapping.

[0043] When the status of the outbound order is "outbound completed" and the status of the inbound order is "inbound completed", the transfer status is changed to "transfer completed" and the transfer process of the transfer management order is terminated.

[0044] Secondly, this application provides an automated warehousing inbound and outbound process scheduling system, including: terminal equipment, transmission equipment, and server equipment; wherein, the terminal equipment is connected to the server equipment through the transmission equipment;

[0045] The server device is used to control the terminal device to execute the steps of the warehouse inbound / outbound process automatic orchestration method as described in any one of the first aspects.

[0046] Compared with existing related technologies, the embodiments of this application have the following beneficial effects:

[0047] This embodiment of the application creates a transfer management order and automatically generates an associated outbound order. After the source warehouse node executes the outbound operation based on the outbound order, the status of the outbound order is changed to outbound completed, and a record is generated in the transfer management order. All records in the transfer management order are scanned according to a preset period. When the corresponding outbound order for a record is in the outbound completed state and there is no corresponding inbound order, an inbound order associated with the record is automatically constructed. After executing the inbound operation based on the inbound order, the transfer process of the transfer management order ends. The outbound completed state serves as the sole signal for automatically triggering the inbound process, ensuring that after the source warehouse node completes the outbound operation, the inbound order for the target warehouse node is automatically generated without manual intervention. This eliminates the manual delay between outbound completion and inbound order creation, and avoids the management vacuum state of issued but without inbound orders due to human error. By recording the status changes of linked outbound and inbound orders, the transfer management order can track the outbound and inbound sides of each material transfer in a unified view, thereby solving the problem that the inbound process cannot be automatically triggered by the completion of the outbound process in cross-warehouse node transfer scenarios.

[0048] Details of one or more embodiments of this application are set forth in the following drawings and description to make other features, objects and advantages of this application more readily apparent. Attached Figure Description

[0049] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0050] Figure 1 This is a flowchart of an embodiment of the automatic arrangement method for warehouse inbound and outbound processes provided in this application;

[0051] Figure 2 This is a flowchart of creating a transfer management order and automatically constructing an associated outbound order, provided in one embodiment of this application;

[0052] Figure 3 This is a flowchart of material information and synchronization provided in one embodiment of this application;

[0053] Figure 4 This is a flowchart of a method for generating records in a transfer management order based on the status of completed outbound shipment, provided in one embodiment of this application.

[0054] Figure 5 This is a flowchart of automatically generating an inbound order according to an embodiment of this application;

[0055] Figure 6 This is a hardware structure block diagram of the terminal for an automatic arrangement method of warehouse inbound and outbound processes provided in an embodiment of this application.

[0056] In the diagram: 102, processor; 104, memory; 106, transmission device; 108, input / output device. Detailed Implementation

[0057] To better understand the purpose, technical solution, and advantages of this application, the application is described and explained below in conjunction with the accompanying drawings and embodiments.

[0058] Unless otherwise defined, the technical or scientific terms used in this application shall have the general meaning understood by one of ordinary skill in the art to which this application pertains. Words such as “a,” “an,” “an,” “the,” “the,” and “these” used in this application do not indicate quantitative limitation and may be singular or plural. The terms “comprising,” “including,” “having,” and any variations thereof used in this application are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that comprises a series of steps or modules (units) is not limited to the listed steps or modules (units) but may include steps or modules (units) not listed, or may include other steps or modules (units) inherent to these processes, methods, products, or devices. Words such as “connected,” “linked,” and “coupled” used in this application are not limited to physical or mechanical connections but may include electrical connections, whether direct or indirect. “Multiple” used in this application refers to two or more. “And / or” describes the relationship between related objects, indicating that three relationships may exist; for example, “A and / or B” can represent: A alone, A and B simultaneously, and B alone. Normally, the character " / " indicates that the objects before and after it are in an "or" relationship. The terms "first," "second," "third," etc., used in this application are merely to distinguish similar objects and do not represent a specific order.

[0059] In a multi-warehouse cluster scenario, when materials are transferred between different warehouse nodes, after the source warehouse node completes the outbound operation, the inbound process of the target warehouse node relies on manual triggering, which leads to delays and omissions in the creation of inbound orders.

[0060] This embodiment provides a method for automatically orchestrating warehouse inbound and outbound processes. Figure 1 This is a flowchart of the automatic arrangement method for warehouse inbound and outbound processes in this embodiment, such as... Figure 1 As shown, the process includes the following steps:

[0061] Step S110: Create a transfer management order and automatically construct the associated outbound order; after the source warehouse node executes the outbound operation based on the outbound order, change the status of the outbound order to the outbound completed state and generate a record in the associated transfer management order.

[0062] For example: a transfer management order can refer to a business document that connects the entire process of transferring materials from the source warehouse node to the target warehouse node. An outbound order can refer to a document that drives the source warehouse node to perform outbound operations; an outbound completion status can refer to the state where the outbound operations corresponding to the outbound order have all been completed. Correspondingly, when an outbound order is in the outbound completion status, the corresponding record is generated.

[0063] This step establishes a status linkage between the transfer management order and the outbound order, which can accurately reflect the progress of the outbound operation through the records in the transfer management order; and the outbound completion status of the outbound order can be used as the sole trigger signal for the subsequent inbound process.

[0064] Step S120: According to the preset cycle, scan all records in the transfer management order. When the corresponding outbound order of the record is in the outbound completed state and there is no corresponding inbound order, automatically construct an inbound order associated with the record.

[0065] For example: a preset cycle can refer to a scanning cycle that is executed at fixed time intervals. An inbound order can refer to a document that drives the target warehouse node to perform an inbound operation.

[0066] This step involves scanning the transfer management order at a preset cycle to identify records that meet the conditions of being in the outbound completion state but have no corresponding inbound order, and automatically constructing the associated inbound order. This allows the inbound process to be automatically triggered when the outbound is completed, thereby compressing the time interval between the completion of outbound and the creation of the inbound order from the time level of manual operation to the time level corresponding to the scanning cycle, thus eliminating the risk of delays and omissions in inbound preparation caused by manual judgment and manual operation.

[0067] Step S130: After the target storage node performs the receiving operation according to the receiving order, the transfer process of the associated transfer management order is terminated.

[0068] For example: the target storage node can refer to an independent storage management unit where materials are transferred in; the end of the transfer process can refer to the transfer status of the transfer management order being deduced as transfer completed.

[0069] This step, by ending the transfer process of the transfer management order after the warehousing operation is completed, keeps the transfer status of the transfer management order synchronized with the actual operation status of the warehousing order, forming a complete business closed loop from outbound to inbound.

[0070] Existing technologies rely on manual confirmation of goods shipment to determine the timing of inbound order creation, with operators at the target warehouse node manually creating the inbound order. Unlike existing technologies, this embodiment completes the outbound operation at the source warehouse node and changes the outbound order status to "outbound completed." Through pre-set periodic scanning, it automatically detects records in the transfer management order. When a record indicates an outbound order is in the "outbound completed" state and no corresponding inbound order exists, an inbound order is automatically created. This eliminates the need for manual judgment and operation in triggering the inbound process; instead, it is automatically driven by the "outbound completed" event, thus eliminating delays and omissions caused by manual operation. Therefore, this embodiment solves the problem of the inbound process not being automatically triggered in cross-warehouse node transfer scenarios.

[0071] In some feasible embodiments, the aforementioned method steps are based on the allocation management order as the main line, with outbound and inbound branches as dual branches, and a timed scanning orchestrator as the automatic orchestration layer. The allocation management order serves as the main business line, running through the entire process from material issuance from the source warehouse node to receipt by the target warehouse node. When the allocation management order is created, an outbound order for the source warehouse node is automatically constructed, and the allocation status of the allocation management order is set to pending execution. At this time, the inbound order number field is empty, indicating that the inbound process at the target warehouse node has not yet started. The outbound branch is independently managed by the source warehouse node's Warehouse Management System (WMS system). The source warehouse node executes outbound operations based on the outbound order, and the outbound order status changes accordingly. When the outbound order status reaches the outbound completion state, the outbound branch operation is completed. The inbound branch is automatically triggered by the timed scan orchestrator. The timed scan orchestrator scans all transfer management orders with an outbound order status of "outbound completed" and an empty inbound order number field according to a preset cycle. For each record, it executes the automatic inbound order creation logic. After the inbound order is created, the inbound order number field of the transfer management order is filled in, and the inbound branch officially enters the operation state. The inbound branch is independently managed by the target warehouse node's WMS system. The target warehouse node executes inbound operations based on the inbound order, and the inbound order status progresses accordingly. When the inbound order status reaches "inbound," the entire lifecycle of the transfer management order ends.

[0072] In some of these embodiments, Figure 2 This embodiment provides a flowchart for creating a transfer management order and automatically constructing the associated outbound order. Step S110, which involves creating a transfer management order and automatically constructing the associated outbound order, specifically includes the following steps:

[0073] Step S111: Create a transfer management order based on the source storage node, target storage node, and material details of the materials to be transferred;

[0074] Step S112: Perform compliance verification on the source and target storage nodes;

[0075] Step S113: After compliance verification is passed, perform pre-synchronization of material information for material details and target storage nodes;

[0076] Step S114: Automatically generate an outbound order based on the source warehouse node and material details;

[0077] Step S115: Mark the outbound type of the outbound order as transfer outbound and set the status to pending operation;

[0078] Step S116: Fill the outbound order number of the outbound order back into the transfer management order to establish the association between the outbound order and the transfer management order.

[0079] For example: "Materials to be transferred" refers to materials that need to be transferred from the source warehouse node to the target warehouse node. "Materials details" refers to a detailed list of materials to be transferred; in practical scenarios, this may include information such as material code, name, and quantity. "Materials information" refers to the basic data of the materials in the warehouse node; in practical scenarios, this may include material master data, material category, and Standard Product Unit (SPU). "Compliance verification" refers to compliance checks between the target warehouse node and the source warehouse node; "Materials information pre-synchronization" refers to the process of pre-establishing material information in the target warehouse node; "Outbound type" refers to the business classification identifier of the outbound order, where "transfer outbound" indicates that the outbound operation corresponding to this outbound order is a material transfer; "Pending operation" refers to the initial state of the outbound order waiting for the outbound operation to be executed.

[0080] This embodiment, through the above steps, enables the allocation management order to be bound to the outbound order of the source warehouse node during the creation stage, and to pre-synchronize the material information in the target warehouse node after compliance verification, ensuring that the target warehouse node has the corresponding basic material data before the outbound order is generated, providing a complete data foundation for the smooth execution of subsequent outbound operations and the automatic triggering of the inbound process.

[0081] In some further embodiments, when multiple transfer management orders need to be generated, the method further includes the following steps:

[0082] Group the material details of the materials to be transferred according to the material category;

[0083] Based on the material details of each group, the corresponding source storage node, and the corresponding target storage node, create transfer management orders corresponding to each group of material details.

[0084] For example: Material category can refer to the category into which materials are divided according to their attribute characteristics. In this embodiment, when multiple transfer management orders need to be generated, the material details of the materials to be transferred are first grouped according to the material category. Then, corresponding transfer management orders are created according to the source storage node and target storage node corresponding to each group of material details. This allows materials of different categories to be automatically allocated to the matching target storage node, realizing the automatic splitting and generation of multiple transfer management orders. This provides a structured grouping basis for the subsequent independent execution of compliance verification, material information pre-synchronization, and outbound order generation for each transfer management order.

[0085] In some feasible embodiments, step S112 involves performing compliance verification on both the source and target storage nodes, specifically including:

[0086] Verify that the target storage node is different from the source storage node;

[0087] Verify that the purpose and type of the target storage node are consistent with those of the source storage node;

[0088] If the verification fails, prevent the creation of the transfer management order.

[0089] For example: Purpose type can refer to the classification identifier of the storage node at the business level; in actual scenarios, material transfer is only allowed between storage nodes with the same purpose type.

[0090] This embodiment ensures, through the above verification conditions, that the target storage node and the source storage node are different but of the same type of use when creating a transfer management order. This avoids materials being mistakenly transferred to the same storage node or storage nodes with mismatched uses, thereby ensuring the compliance and accuracy of the transfer business.

[0091] In some further embodiments, Figure 3 This is a flowchart of material information and synchronization provided in this embodiment. Please refer to it. Figure 3 Step S113, which is the step of pre-synchronizing material information between the material details and the target warehousing node after the compliance verification is passed, specifically includes the following steps:

[0092] Iterate through each material record in the material details;

[0093] By querying the material code of the source warehouse node, the corresponding material master data is retrieved, and the corresponding external code is determined based on the material master data;

[0094] Based on the external code, query the corresponding material information in the target storage node;

[0095] When the corresponding material information is found, obtain the material code corresponding to the material information in the target storage node;

[0096] If the corresponding material information cannot be found, add an external code corresponding to the material information in the target warehouse node;

[0097] In the target warehouse node, material information is synchronized based on the material code or newly added external code to create the material master data corresponding to the material information.

[0098] For example: Material master data refers to the basic data describing the fundamental attributes of materials in a warehousing node; in practical scenarios, it may include information such as material code, material name, basic unit, weight, specifications, and color code. External code refers to the unified identification code of a material; in practical scenarios, the same material shares the same external code in different warehousing nodes, and the external code is the key anchor point for material information matching and synchronization across warehousing nodes. Material code refers to the unique identifier of a material within a warehousing node. Material record refers to a single record in the material details, corresponding to a material to be transferred.

[0099] This embodiment uses external codes as anchors to match material information in the target warehouse node. When a match is successful, the existing material codes in the target warehouse node are directly obtained. When a match fails, an external code is automatically added to the target warehouse node and the material information is synchronized to create material master data. No manual intervention is required during the pre-synchronization of material information. The automatic establishment and alignment of basic material data in the target warehouse node is completed automatically, thereby eliminating the workload and error risk of manually supplementing material files. This provides an accurate and consistent material data foundation for the subsequent generation of outbound orders and the automatic construction of inbound orders.

[0100] In some further embodiments, setting the status of the outbound order to "pending work" in step S115 also includes:

[0101] Set the priority of the outbound order to medium.

[0102] For example: priority can refer to the processing order level of the outbound order in the job scheduling; in actual scenarios, it can include high, medium and low levels, and the outbound order for transfer is set to medium priority by default.

[0103] This embodiment sets the priority of the outbound transfer order to medium, so that the outbound transfer operation has a reasonable processing order in the operation scheduling of the source warehouse node, which neither excessively seizes the resources of urgent orders, nor is it shelved for a long time due to too low priority.

[0104] In some feasible embodiments, the self-generation of material information is performed according to the following steps:

[0105] By querying the material master data in the source warehouse node using the material code, the external code, material category name, and color code can be obtained.

[0106] Using the external code as the anchor point, query the material master data in the target warehouse node;

[0107] Determine if there is material master data with the same external code in the target warehouse node; if so, directly obtain the material code and material attributes in the target warehouse node and jump to step eight; if not, call the serial number generator to generate a new material code that does not conflict in the target warehouse node.

[0108] In the target warehouse node, query the material category by material category name; if the material category does not exist, copy the material category record from the source warehouse node, clear the original identifier, set the warehouse code of the target warehouse node, and insert it into the category table of the target warehouse node;

[0109] In the target warehouse node, count the number of SPU records by color code; when the number is zero, copy the SPU record from the source warehouse node, clear the original identifier, set the warehouse code of the target warehouse node, and insert it into the SPU table of the target warehouse node.

[0110] Copy all attributes from the material master data of the source warehouse node, clear the original identifier, set the new material code, the warehouse code of the target warehouse node, and the new category code, and insert them into the material master data table of the target warehouse node;

[0111] Returns the material code and material attributes in the target warehouse node, which are used to construct the inbound details.

[0112] This embodiment fully demonstrates the sequential process of material information self-generation, from obtaining source material information, retrieving target storage nodes, determining whether they exist, generating new codes, synchronizing material categories and SPUs, creating material master data, to returning results. It automatically establishes a complete material file when material information is missing from the target storage node.

[0113] In some feasible embodiments, the material matching result and material coverage rate are determined in the material information pre-synchronization process in step S113 in the following manner:

[0114] Let the set of materials in the source storage node be . For each element Its external encoding is ,in, , For any integer. Define the material matching function. For target warehousing nodes External encoding is Material master data.

[0115] Material coverage for: ;

[0116] Among them, When a material is not matched, the material information is automatically generated. This indicates the total number of materials in the material set; This indicates the quantity of materials matched in the target warehouse node.

[0117] Let the set of unmatched materials be... for: ;

[0118] right Each element in Generate new material codes to The corresponding material master data is created by copying material attributes from a template, setting a new material code and the warehouse code of the target warehouse node, and then creating the material master data in the target warehouse node.

[0119] This embodiment defines a material matching function, using external codes as anchors, to search for material master data at the target warehouse node and calculate the material coverage rate to quantify the degree of completion of material information pre-synchronization. When the coverage rate does not reach 100%, it automatically identifies the set of unmatched materials and performs self-generation of material information. Thus, this embodiment can achieve quantitative and automated closed-loop control of the material synchronization process.

[0120] In some feasible embodiments, the process of material information self-generation is illustrated by taking the transfer of materials from source storage node W1 to target storage node W2 as an example:

[0121] Enter material code MAT-001, source warehouse node is W1, and target warehouse node is W2.

[0122] In the source warehouse node W1, query the material master data corresponding to material code MAT-001. The material name is steel plate A, the external code is EXT-001, the material category is metal material, the color code is COLOR-001, and the basic unit is kilogram.

[0123] The query for material master data in the target warehouse node W2 using the external code EXT-001 returned an empty result, indicating that no corresponding material was found.

[0124] Generate a new material code MAT-W2-0001 in the target warehouse node W2.

[0125] Query the material category "metal materials" in the target warehouse node W2. If the query result is empty, copy the material category "metal materials" from the source warehouse node W1, clear the original identifier, set the warehouse code of the target warehouse node W2, insert it into the category table of the target warehouse node W2, and generate a new category code CAT-W2-001.

[0126] In the target warehouse node W2, count the number of SPUs corresponding to the color code COLOR-001. If the count result is zero, copy the corresponding SPU record from the source warehouse node W1, clear the original identifier, set the warehouse code of the target warehouse node W2, and insert it into the SPU table of the target warehouse node W2.

[0127] Copy the material attributes from the material master data of the source warehouse node W1, set the new material code MAT-W2-0001, the warehouse code of the target warehouse node W2, and the new category code CAT-W2-001, and insert them into the material master data table of the target warehouse node W2.

[0128] Output the newly created material information in the target warehouse node W2: Material code MAT-W2-0001, material name steel plate A, material category CAT-W2-001, basic unit kilogram.

[0129] This embodiment demonstrates the complete sequential process of material information self-generation through a specific example.

[0130] In some further embodiments, Figure 4 This is a flowchart provided in this embodiment for generating records in the transfer management order based on the outbound completion status. Please refer to it. Figure 4 In step S110, after the source warehouse node executes the outbound operation based on the outbound order, the status of the outbound order is changed to the outbound completed state, and a record is generated in the associated transfer management order. This sub-step specifically includes the following steps:

[0131] Step S117: At the source warehouse node, execute the outbound operation according to the outbound order;

[0132] Step S118: After the outbound operation is completed, change the status of the outbound order to the outbound completed state;

[0133] Step S119: Based on the association between the outbound order and the transfer management order, generate a record in the transfer management order; the record indicates that the outbound order has been changed to the outbound completion state.

[0134] For example: Outbound operations can refer to the material picking, destocking, loading and shipping confirmation operations performed by the source warehouse node based on the outbound order; in actual scenarios, the status change of each outbound operation is recorded on the outbound order.

[0135] In this embodiment, after the outbound operation is completed at the source warehouse node, the status of the outbound order is changed to the outbound completed state. Based on the association between the outbound order and the transfer management order, a record is generated in the transfer management order, which can accurately reflect the actual operation status of the warehouse order through the record in the transfer management order.

[0136] In some further embodiments, the status of the outbound order in step S117 flows along the following path: pending work, unprocessed, in work, and outbound completed.

[0137] For example: "Pending Operation" can refer to the initial state where an outbound order is awaiting the execution of an outbound operation. "Unprocessed" can refer to the intermediate state where the outbound order has been received but the operation has not yet started. "In Operation" can refer to the state where the outbound operation corresponding to the outbound order is being executed. "Outbound Completed" can refer to the state where all outbound operations have been completed.

[0138] This embodiment defines the flow path of the outbound order status from pending operation to outbound completion, so that each stage of the outbound operation has a clear status identifier. Each status change is triggered by the operation of the source warehouse node operator and recorded on the outbound order, providing a clear and reliable status basis for the subsequent timed scanning orchestrator to identify the outbound completion status.

[0139] In some of these embodiments, Figure 5 This is a flowchart of the automatic creation of an inbound order provided in this embodiment. Please refer to it. Figure 5 Step S120, which involves scanning all records in the transfer management order according to a preset cycle, and automatically constructing an inbound order associated with the record when the corresponding outbound order is in an outbound completed state and there is no corresponding inbound order, specifically includes the following steps:

[0140] Step S121: The timed scanning orchestrator scans the transfer management order according to a preset cycle, determines the target record, and reads the outbound order and corresponding outbound details associated with the target record; wherein, the timed scanning orchestrator is set independently of the source storage node and the target storage node.

[0141] Step S122: Automatically construct an inbound order based on the outbound order and outbound details, and backfill the corresponding inbound order number to the transfer management order.

[0142] For example: A scheduled scan orchestrator can refer to a background task executor independent of the source and target warehouse nodes; in actual scenarios, the scheduled scan orchestrator periodically executes scan tasks at fixed time intervals, automatically triggering the inbound process. A target record can refer to a record that is determined to meet the outbound completion status during the scanning process and has no corresponding inbound order conditions. Outbound details can refer to the material issuance details recorded in the outbound order; in actual scenarios, this can include fields such as material code, notification quantity, weight, and volume. An inbound order number is the unique identifier of the inbound order.

[0143] This embodiment uses the above methods to automatically create inbound orders through outbound completion events and timed scanning orchestrators, achieving automated orchestration of the inbound process without manual judgment or operation; at the same time, it establishes a link between inbound orders and transfer management orders, forming a complete closed-loop document system from outbound to inbound.

[0144] In some feasible embodiments, the process of automatically constructing the inventory receipt in step S120 can be performed according to the following steps:

[0145] The timed scan orchestrator starts scanning tasks according to a preset cycle and records the task start time.

[0146] Using the outbound order status as "outbound completed" and the inbound order number field as the filter condition, query the transfer management order records from the database in pages;

[0147] Determine if the query result is empty. If the query result is empty, record the task end time and exit the current scan. If the query result is not empty, proceed to step four.

[0148] For each transfer management record retrieved, read the associated outbound order and outbound details, construct the inbound order header and inbound details, perform material information matching, and automatically generate material information when matching fails, and save the inbound order;

[0149] The generated inbound order number will be filled back into the corresponding transfer management order record;

[0150] Update the transfer management records completed in this scan to the database in batches;

[0151] Record the number of scans processed and the task completion time for this scan.

[0152] This embodiment fully demonstrates the complete closed loop of automatic triggering from task initiation, paginated query, item-by-item processing, backfilling and updating to task completion.

[0153] In some further embodiments, step S121, which is the step of the timed scanning orchestrator scanning the transfer management order according to a preset cycle, determining the target record, and reading the outbound order and corresponding outbound details associated with the target record, specifically includes the following steps:

[0154] Perform paginated scanning on the transfer management order, with each scan acquiring no more than a preset number of records.

[0155] In this acquisition, the records whose corresponding outbound orders are in the outbound completed state and which have no corresponding inbound orders are identified as target records.

[0156] For example: paginated scanning can refer to a scanning method that retrieves transfer management records in batches; in actual scenarios, each scan retrieves a batch of records, and the number of records in each batch does not exceed a preset number. The preset number can refer to the upper limit of records retrieved in a single scan; in actual scenarios, it can be set to 100 records.

[0157] This embodiment uses the above methods to control the amount of data processed in each scan, avoiding loading too many records at once and consuming too many resources. At the same time, batch processing can ensure the stability and scalability of the scan arrangement process, providing accurate processing objects for subsequent construction of warehouse entry orders and batch backfilling of warehouse entry order numbers.

[0158] In some further embodiments, step S122, which involves automatically constructing an inbound order based on the outbound order and outbound details, specifically includes the following steps:

[0159] Construct the inbound header of the inbound order, set the inbound type to transfer inbound, set the upstream order number of the inbound order to the outbound order number of the outbound order, set the warehouse code of the inbound order to the code of the target storage node, and inherit personnel information from the outbound order.

[0160] Based on the outbound details, construct the inbound details for the inbound order and assign a serial number to each inbound detail.

[0161] For example: The "Inbound Order Header" refers to the header information of the inbound order; in actual scenarios, it may include fields such as inbound type, upstream order number, warehouse code, and personnel information. The inbound type refers to the business classification identifier of the inbound order, where "transfer inbound" indicates that the corresponding inbound operation is material transfer receipt. The upstream order number refers to the order number of the source document associated with the inbound order; in actual scenarios, it is set as the outbound order number of the outbound order, used to trace the origin of the inbound materials. Personnel information refers to the information of the operators related to the document; in actual scenarios, it may include fields such as creator, updater, and shipper, inherited and copied from the outbound order to ensure the integrity of the business traceability chain. The inbound details refer to the detailed material inbound information recorded in the inbound order; in actual scenarios, it may include fields such as material code, notification quantity, weight, and volume, copied verbatim from the outbound details. The sequence number refers to the sequential number assigned to each inbound detail.

[0162] This embodiment, through the above steps, sets the inbound type to transfer inbound and associates it with the upstream outbound order number when constructing the inbound order. It inherits personnel information from the outbound order, copies the notification quantity, weight, and volume from the outbound details, and assigns a serial number. This enables the inbound order to accurately inherit the business information, material information, and responsibility information of the outbound order, ensuring the consistency and traceability of data between the inbound and outbound orders.

[0163] In some feasible embodiments, the inbound details of the inbound order are constructed based on the outbound details, specifically including:

[0164] For each material record in the outbound details, query the corresponding material master data through the material code of the source warehouse node to obtain the corresponding external code;

[0165] Query material master data in the target warehouse node using external codes;

[0166] When the query is successful, retrieve the material code, basic unit, weight, category code, category name, color code, material name, and specifications of the material in the target warehouse node;

[0167] If the information cannot be found, the material information is automatically generated to obtain the generated material code, basic unit, weight, category code, category name, color code, material name, and specifications.

[0168] Fill the obtained material code, basic unit, weight, category code, category name, color code, material name, specifications, and the quantity, weight, and volume of the notification copied from the outbound details into the inbound details.

[0169] For example: Basic unit refers to the basic unit of measurement for materials; in practical scenarios, this may include kilograms, pieces, meters, etc. Gram weight refers to the unit weight of the material. Category code and category name refer to the code and name of the material category. Color code refers to the color identification of the material in the SPU. Material name refers to the standardized name of the material. Specification refers to the specification description of the material.

[0170] This embodiment obtains complete attribute information of materials in the target storage node when constructing the inbound details through the above steps, and copies the business data from the outbound details exactly, so that the inbound details have both accurate material attribute information and business data.

[0171] In some feasible embodiments, after automatically generating the inbound order in step S122, the following steps are also included:

[0172] Set the transfer flag on the receiving slip to true;

[0173] Based on the inbound order, a receiving slip is automatically generated. The receiving slip is used to guide the receiving operations at the target warehousing node.

[0174] For example: A transfer flag can refer to a field on an inbound receipt that identifies the inbound receipt as originating from a material transfer. In practice, a true transfer flag indicates that the inbound receipt is a transfer receipt, distinguishing it from other inbound types such as purchase receipts and production receipts. A receiving slip can refer to a task document automatically generated after the inbound receipt is created, used to guide warehouse receiving personnel in their physical operations. In practice, a receiving slip may include a suggested receiving location and a list of expected incoming materials.

[0175] This embodiment distinguishes between transfer-in and other inbound types by setting a transfer flag and automatically generating a receiving slip after the inbound slip is constructed. At the same time, it enables the data preparation of the inbound slip and the operation preparation of the receiving slip to be completed in one step. The receiving personnel at the target warehouse node can obtain complete receiving operation guidance without performing any additional operations.

[0176] In some feasible embodiments, the scanning window and processing quantity are determined for the process of automatically constructing the inventory receipt in step S120 as follows:

[0177] Define the set of transfer management orders as The corresponding element is and , For any integer. Scan window. for: ;in, express The corresponding outbound order status is "outbound completed"; express The inbound order number field is empty.

[0178] right Each of them Calculate the completeness of the inbound order creation. This represents the percentage of successfully mapped materials relative to the total number of materials in the outbound details. The inbound order was created successfully. Maximum batch size for a single scan. The preset quantity, the total amount processed in a single scan. for: ;in, Indicates the scanning window The number of transfer management orders in the central government. This indicates the number of transfer management orders actually processed in this scan.

[0179] This embodiment defines a scanning window. All transfer management orders that meet the conditions of completed outbound status and empty inbound order number field are filtered out. The inbound order creation completeness of each transfer management order is calculated. When the completeness reaches 100%, the creation is confirmed as successful. The total amount of processing in a single scan is determined according to the window size and batch limit, realizing quantitative control of the scan orchestration process and ensuring the efficiency and completeness of batch processing.

[0180] In some feasible embodiments, taking the acquisition of 3 transfer management orders in a single scan as an example, the process of creating a batch inbound order is illustrated:

[0181] Set the current scanning window Preset quantity Then the total amount processed Three transfer management orders are processed in parallel:

[0182] Article 1 Transfer Management Form The associated outbound order is OUT-001. The outbound details include material A and material B. By matching the material information, the corresponding material codes in the target warehouse node are obtained, and an inbound order IN-001 is constructed. The completeness of the inbound order creation is calculated. Save the receiving slip and fill in the receiving slip number IN-001. .

[0183] Article 2 Transfer Management Form The associated outbound order is OUT-002. The outbound details include material X. Material X was not found in the target warehouse node, triggering the automatic generation of material information. After generating a new material code, the material master data is created, and an inbound order IN-002 is constructed. The completeness of the inbound order creation is calculated. Save the receiving slip and fill in the receiving slip number IN-002. .

[0184] Article 3 Transfer Management Form The associated outbound order is OUT-003. The outbound details include material A and material D. Material A already exists in the target warehouse node, while material D does not exist in the target warehouse node. Material information is automatically generated for material D, creating an inbound order IN-003. The completeness of the inbound order creation is calculated. Save the receiving slip and fill in the receiving slip number IN-003. .

[0185] After all three transfer management orders have been processed, batch updates are performed. , and The corresponding inbound order number indicates that a total of 3 records were processed in this scan, and all were successfully processed.

[0186] This embodiment demonstrates, through specific examples, the complete process of a timed scanning orchestrator processing multiple transfer management orders in parallel during a single scan. It includes two branch path processing methods: direct material matching and self-generation of material information. It also shows a verification mechanism that calculates the completeness of the inbound order creation after each transfer management order is processed to confirm the processing result, thus verifying the feasibility and completeness of the batch processing flow.

[0187] In some embodiments, step S130, which is the step of ending the transfer process of the associated transfer management order after the target storage node performs the receiving operation according to the receiving order, specifically includes:

[0188] Step S131: After the target warehouse node performs the inbound operation based on the inbound order, the status of the inbound order is changed to "inbound".

[0189] Step S132: Based on the status of the outbound order and the status of the inbound order associated with the transfer management order, the transfer status of the transfer management order is deduced through state machine mapping.

[0190] Step S133: When the status of the outbound order is "outbound completed" and the status of the inbound order is "inbound received", change the transfer status to "transfer completed" and end the transfer process of the transfer management order.

[0191] For example: State machine mapping can refer to establishing a correspondence between the transfer status of a transfer management order and the status of the outbound and inbound orders; in actual scenarios, the transfer status of a transfer management order is derived from the combination of the status of the outbound and inbound orders, without the need for separate maintenance. Transfer status can refer to the stage of the transfer management order in the entire lifecycle of material transfer; in actual scenarios, it can include stages such as pending execution, pending transfer out, pending transfer in, and transfer completed.

[0192] This embodiment ensures that the allocation status of the allocation management order is always synchronized with the actual operational status of the outbound and inbound orders through the above steps, avoiding the lag and inconsistency caused by manual status updates.

[0193] In some further embodiments, the status of the inbound order in step S131 flows along the following path: pending work, in work, and already inbound.

[0194] For example: "Pending Operation" can refer to the initial state of an inbound order awaiting inbound operation. "In Operation" can refer to the state where the inbound operation corresponding to the inbound order is being executed. "Already Inbound" can refer to the state where all inbound operations have been completed.

[0195] This embodiment defines the flow path of the inbound order status from pending operation to already inbound, so that each stage of the inbound operation has a clear status identifier. Each status change is triggered by the operation of the operator at the target warehouse node and recorded on the inbound order, providing a clear and reliable status basis for the state machine to map and deduce the transfer status of the transfer management order.

[0196] In some feasible embodiments, step S132, which derives the allocation status of the allocation management order through state machine mapping, specifically includes the following steps:

[0197] When the status of the outbound order is pending operation, unprocessed, or returned, the transfer status will be deduced to pending execution.

[0198] When the status of the outbound order is "in operation", the transfer status will be deduced to "pending transfer".

[0199] When the status of the outbound order is "outbound completed" and the inbound order has not yet been generated, the transfer status will be deduced to "pending transfer in".

[0200] When the status of the inbound order is pending or in operation, the transfer status will be deduced to pending transfer in.

[0201] When the status of the receiving order is "received", the transfer status will be deduced to "transfer completed".

[0202] This embodiment uses the above correspondence to accurately map the transfer status of the transfer management order to the status of the outbound order and the inbound order, so that the transfer status can reflect the real progress of material transfer in real time. Warehouse managers can grasp the stage of each transfer management order in a single view without having to check the status of the outbound order and the inbound order separately.

[0203] This application provides an automated orchestration system for warehouse inbound and outbound processes, including: terminal equipment, transmission equipment, and server equipment; wherein, the terminal equipment is connected to the server equipment through the transmission equipment;

[0204] The server device is used to control the terminal device to execute the aforementioned method embodiments and their feasible implementation methods.

[0205] In some embodiments, the server device is deployed with a timed scanning orchestrator, which is independent of the WMS system settings of the source warehouse node and the WMS system of the target warehouse node. It is used to scan transfer management orders according to a preset period and automatically construct an inbound order when the associated outbound order is in an outbound completed state and there is no corresponding inbound order.

[0206] For example: The scheduled scanning orchestrator can refer to the background task execution entity that is independent of the WMS system of each warehouse node; in actual scenarios, the scheduled scanning orchestrator obtains the status information of the transfer management order through database query and generates the inbound order through interface call, without relying on the internal logic of the WMS system of the source warehouse node or the target warehouse node.

[0207] This embodiment deploys the timed scanning orchestrator independently outside the WMS system of each warehouse node, enabling it to act as an automatic orchestration layer to coordinate the flow of documents between the source and target warehouse nodes. The outbound and inbound branches operate independently without blocking each other, and system maintenance and upgrades of any warehouse node do not affect the normal operation of other warehouse nodes.

[0208] In some further embodiments, the timed scanning orchestrator is used to perform paginated scanning of the transfer management order. Each scan acquires no more than a preset number of records. Among the acquired records, the target record with the associated outbound order in the outbound completion state and no corresponding inbound order is selected. The outbound order and outbound details associated with the target record are read one by one. The inbound order is automatically constructed based on the outbound order and outbound details, and the inbound order number of the inbound order is batch-filled back into the corresponding transfer management order.

[0209] This embodiment uses a timed scanning arranger to perform a serial arrangement process of page scanning, filtering target records, constructing inbound orders one by one, and batch filling in inbound order numbers. This makes the amount of data processed in a single scan controllable, the processing of each record independent, and the batch update method for filling in inbound order numbers, thus ensuring the stability and execution efficiency of the automatic arrangement process.

[0210] In some embodiments, the terminal device includes a source warehouse node terminal and a target warehouse node terminal. The source warehouse node terminal is used to receive outbound operation instructions and report the outbound operation status; the target warehouse node terminal is used to receive inbound operation instructions and report the inbound operation status.

[0211] This embodiment distinguishes the terminal devices into source warehouse node terminals and target warehouse node terminals, which correspond to the operation execution and status reporting of the outbound and inbound branches, respectively. This allows outbound and inbound operations to be carried out independently at each warehouse node, and status changes are reported to the server device in real time through the terminal devices, providing accurate status detection basis for the timed scanning orchestrator.

[0212] The method embodiments provided in this example can be executed on a terminal, computer, or similar computing device. For example, it can run on a terminal. Figure 6 This is a hardware structure block diagram of the terminal for the automatic orchestration method of warehouse inbound and outbound processes in this embodiment. For example... Figure 6 As shown, a terminal may include one or more ( Figure 6Only one is shown in the diagram. A processor 102 and a memory 104 for storing data are also included. The processor 102 may be, but is not limited to, a microprocessor (MCU) or a programmable logic device (FPGA). The terminal may also include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that… Figure 6 The structure shown is for illustrative purposes only and does not limit the structure of the terminal described above. For example, the terminal may also include components that are larger than... Figure 6 The more or fewer components shown, or having the same Figure 6 The different configurations shown are illustrated.

[0213] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the automatic arrangement method for warehouse inbound and outbound processes in this embodiment. The processor 102 executes various functional applications and data processing by running the computer programs stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0214] The transmission device 106 is used to receive or send data via a network. This network includes a wireless network provided by the terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 can be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0215] This embodiment also provides a computer device, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0216] Optionally, the computer device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0217] It should be noted that the specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated in this embodiment.

[0218] Furthermore, in conjunction with the automatic warehousing inbound and outbound process arrangement method provided in the above embodiments, this embodiment can also provide a storage medium for implementation. The storage medium stores a computer program; when executed by a processor, the computer program implements any of the automatic warehousing inbound and outbound process arrangement methods in the above embodiments.

[0219] It should be noted that all information and data involved in this application are authorized by the user or fully authorized by all parties and will be used legally.

[0220] It should be understood that the specific embodiments described herein are merely illustrative of the application and not intended to limit it. All other embodiments derived by those skilled in the art based on the embodiments provided in this application without inventive effort are within the scope of protection of this application.

[0221] Obviously, the accompanying drawings are merely some examples or embodiments of this application. Those skilled in the art can apply this application to other similar situations based on these drawings without any creative effort. Furthermore, it is understood that although the work done in this development process may be complex and lengthy, for those skilled in the art, certain design, manufacturing, or production modifications made based on the technical content disclosed in this application are merely conventional technical means and should not be considered as insufficient disclosure of this application.

[0222] The term "embodiment" in this application refers to a specific feature, structure, or characteristic described in connection with an embodiment that may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily imply the same embodiment, nor does it imply that it is mutually exclusive with or independent of other embodiments. It will be clearly or implicitly understood by those skilled in the art that the embodiments described in this application may be combined with other embodiments without conflict.

[0223] The above embodiments merely illustrate several implementation methods of this application, and their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of patent protection. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the scope of protection of this application.

Claims

1. A method for automatically arranging warehouse inbound and outbound processes, characterized in that, include: Create a transfer management order and automatically generate the associated outbound order; After the source warehouse node executes the outbound operation according to the outbound order, the status of the outbound order is changed to the outbound completed state, and a record is generated in the associated transfer management order; According to a preset cycle, all records in the transfer management order are scanned. When the outbound order corresponding to the record is in the outbound completed state and there is no corresponding inbound order, the inbound order associated with the record is automatically constructed. After the target storage node performs the receiving operation according to the receiving order, the transfer process of the associated transfer management order ends.

2. The automatic arrangement method for warehouse inbound and outbound processes according to claim 1, characterized in that, The creation of the transfer management order, which automatically constructs the associated outbound order, includes: Based on the source storage node, the target storage node, and the material details of the materials to be transferred, create the transfer management order; Perform compliance verification on the source storage node and the target storage node; After the compliance verification is passed, material information pre-synchronization is performed on the material details and the target storage node; The outbound order is automatically generated based on the source warehouse node and the material details; The outbound type of the outbound order is marked as transfer outbound, and the status is set to pending operation; The outbound order number of the outbound order is filled back into the transfer management order to establish the association between the outbound order and the transfer management order.

3. The automatic arrangement method for warehouse inbound and outbound processes according to claim 2, characterized in that, The method further includes: Based on the material category, the material details of the materials to be allocated are grouped. Based on the material details of each group, the corresponding source storage node, and the corresponding target storage node, create the transfer management order corresponding to the material details of each group.

4. The automatic arrangement method for warehouse inbound and outbound processes according to claim 2, characterized in that, After the compliance verification is passed, the material information pre-synchronization is performed on the material details and the target warehousing node, including: Iterate through each material record in the material details; By querying the material code of the source storage node, the corresponding material master data is retrieved, and the corresponding external code is determined based on the material master data; Based on the external code, query the corresponding material information in the target storage node; When the corresponding material information is found, the material code corresponding to the material information in the target storage node is obtained; If the corresponding material information cannot be found, an external code corresponding to the material information is added to the target storage node; In the target storage node, the material information is synchronized according to the material code or the newly added external code to create the material master data corresponding to the material information.

5. The automatic arrangement method for warehouse inbound and outbound processes according to claim 2, characterized in that, After the source warehouse node executes the outbound operation based on the outbound order, the status of the outbound order is changed to outbound completed, and a record is generated in the associated transfer management order, including: At the source warehouse node, an outbound operation is performed based on the outbound order; After the outbound operation is completed, the status of the outbound order is changed to the outbound completed status; Based on the association between the outbound order and the transfer management order, the record is generated in the transfer management order; the record indicates that the outbound order has been changed to the outbound completion state.

6. The automatic arrangement method for warehouse inbound and outbound processes according to claim 1, characterized in that, The process involves scanning all records in the transfer management order according to a preset period. When the outbound order corresponding to a record is in an outbound completed state and there is no corresponding inbound order, an inbound order associated with the record is automatically constructed, including: The timed scanning orchestrator scans the transfer management order according to the preset cycle, determines the target record, and reads the outbound order and corresponding outbound details associated with the target record; wherein, the timed scanning orchestrator is set independently of the source storage node and the target storage node; Based on the outbound order and the outbound details, the inbound order is automatically generated, and the inbound order number corresponding to the inbound order is backfilled into the transfer management order.

7. The automatic arrangement method for warehouse inbound and outbound processes according to claim 6, characterized in that, The timed scanning orchestrator scans the transfer management order according to the preset cycle, identifies the target record, and reads the outbound order and corresponding outbound details associated with the target record, including: The transfer management order is scanned page by page, and each scan retrieves no more than a preset number of records; Among the records obtained this time, the records whose corresponding outbound orders are in the outbound completed state and which have no corresponding inbound orders are identified as the target records.

8. The automatic arrangement method for warehouse inbound and outbound processes according to claim 6, characterized in that, The automatic construction of the inbound order based on the outbound order and the outbound details includes: Construct the entry header of the entry order, set the entry type of the entry order to transfer entry, set the upstream order number of the entry order to the outbound order number of the outbound order, set the warehouse code of the entry order to the code of the target storage node, and inherit personnel information from the outbound order; Based on the outbound details, construct the inbound details of the inbound order, and assign a serial number to each inbound detail.

9. The automatic arrangement method for warehouse inbound and outbound processes according to claim 1, characterized in that, The step of ending the transfer process of the associated transfer management order after the receiving operation is performed at the target storage node according to the receiving order includes: After the target storage node performs the inbound operation according to the inbound order, the status of the inbound order is changed to "inbound". Based on the status of the outbound order and the inbound order associated with the transfer management order, the transfer status of the transfer management order is deduced through state machine mapping. When the status of the outbound order is "outbound completed" and the status of the inbound order is "inbound completed", the transfer status is changed to "transfer completed" and the transfer process of the transfer management order is terminated.

10. An automated warehousing inbound and outbound process scheduling system, characterized in that, include: Terminal equipment, transmission equipment, and server equipment; wherein the terminal equipment is connected to the server equipment through the transmission equipment; The server device is used to control the terminal device to execute the steps of the automatic arrangement method for warehouse inbound and outbound processes as described in any one of claims 1 to 9.

Images