Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The purchase order generation method provided by the application can be applied to the application environment shown in fig. 1. The terminal 102 and the server 104 communicate with each other through a network, or the server 104 is deployed in the terminal 102 and performs data interaction through an inter-thread communication mode, which is not limited in the present application. The terminal 102 may be configured to display an interface of the software, where the interface may be a display interface of each function in the software, or a setting interface of the software, and may also display information such as a data report or a service log record, and the terminal 102 may also be configured to send a request to the server 104, such as a new request of a sales order, an edit request of the sales order, an edit request of a purchase order, and the like. Specifically, the server 104 obtains a new request of the sales order through the terminal 102, and obtains a product identifier corresponding to the sales order and a purchase quantity corresponding to the product identifier according to the new request. The server 104 generates a sales order from the product identification, wherein the sales order includes the sales order identification. Server 104 generates a purchase order corresponding to the sales order identifier according to the product identifier and the corresponding purchase quantity, and establishes an association relationship between the sales order and the purchase order through the sales order identifier. The terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. The server 104 may be implemented as a stand-alone server or as a server cluster comprised of multiple servers.
In one embodiment, as shown in FIG. 2, a method for generating a purchase order is provided, which is illustrated by applying the method to the server in FIG. 1, and comprises the following steps:
step 202, a new request for a sales order is obtained.
And step 204, acquiring the corresponding product identification and the purchase quantity corresponding to the product identification according to the new request.
The product identifier may be used to distinguish different products, and the product identifier may be input by a user through a terminal, for example, the product identifier may be a product name, a product code, and the like, which is not limited herein. At least one product identification may be included in a sales order. The purchase quantity may be a quantity that the user corresponding to the product identifier needs to purchase, the purchase quantity may be input by the user through the terminal, may be automatically generated by the server according to the sales quantity corresponding to the product identifier, and may be determined by the server according to the sales quantity corresponding to the product identifier and the inventory quantity corresponding to the product identifier stored in the server, which is not limited herein. Specifically, a user may trigger a new request for a certain sales order through the terminal, and may input information, such as product identifiers, sales quantities, or purchase quantities, included in the sales order through the terminal. The terminal sends the new request of the sales order and the information such as the product identification contained in the sales order to the server, so that the server can acquire the new request of the sales order and the information such as the product identification, and further generate the sales order according to the acquired information such as the product identification.
At step 206, a sales order is generated based on the product identifier, the sales order including a sales order identifier.
The sales order identifier may be used to distinguish different sales orders, the sales order identifier has uniqueness, and the sales order identifier may be sales order ID information, and the like, which is not limited herein. Specifically, after obtaining information such as a product identifier contained in a sales order, a terminal sends the information such as the product identifier to a server, the server generates the sales order according to the obtained information such as the product identifier, the generated sales order includes the sales order identifier, and the sales order identifier is used for uniquely representing the sales order.
And step 208, generating a purchase order corresponding to the sales order identifier according to the product identifier and the corresponding purchase quantity, and establishing an association relationship between the sales order and the purchase order through the sales order identifier.
Specifically, while generating the sales order, the server may also automatically generate the purchase order according to the obtained product identifier and the corresponding purchase quantity, and establish a corresponding relationship between the sales order identifier and the purchase order, thereby generating the purchase order corresponding to the sales order identifier.
According to the purchase order generation method, the new request of the sales order is obtained, and the corresponding product identification and the purchase quantity are obtained according to the new request. Then, generating a sales order according to the product identifier, wherein the sales order comprises a sales order identifier; and generating a purchase order corresponding to the sales order identification according to the product identification and the corresponding purchase quantity. On one hand, the method can realize that a purchase order corresponding to the product identification contained in the sales order is automatically generated by newly creating a sales order, and the system is simple to operate; on the other hand, since the sales order and the purchase order generate an association relationship through the sales order identification, the associated sales order and purchase order are convenient to manage in the system subsequently.
Further, since the sales order may include one or more product identifiers, the server may generate one or more corresponding purchase orders according to the one or more product identifiers, where the one or more purchase orders respectively include the product identifiers and corresponding purchase quantities, and the one or more purchase orders may be associated with the sales order through the same sales order identifier.
In one embodiment, after acquiring the corresponding product identifier and the purchase quantity corresponding to the product identifier according to the new request, the method further includes the following steps:
step 302, determining corresponding supplier information according to the product identifier.
The vendor information is used to distinguish different vendors, and the vendor information may be a vendor name, a vendor code, and the like, which is not limited herein. The supplier information may be automatically generated by the terminal, and the server may store the supplier information corresponding to different product identifiers respectively. After the server acquires the product identifier, the corresponding supplier information can be found according to the acquired product identifier, and the supplier information is returned to the terminal. The provider information may also be manually input by the user through a terminal, which is not limited herein.
In this embodiment, generating a purchase order corresponding to the sales order identifier according to the product identifier and the corresponding purchase quantity specifically includes:
step 304, generating a purchase order corresponding to the sales order identification according to the product identification, the corresponding purchase quantity and the supplier information. Specifically, the server may generate a purchase order corresponding to the sales identification based on the acquired product identification, and the finalized purchase quantity and supplier information. In this embodiment, by adding the provider information to the purchase order corresponding to the sales identifier, the content of the purchase order corresponding to the sales identifier is more comprehensive, and the user can conveniently view and manage the purchase order subsequently.
Further, in this embodiment, if the product identifier includes at least one product identifier, the supplier information corresponding to each product identifier may be different from each other, or one or more products therein may correspond to the same supplier information, which is not limited herein. The user may input the vendor information respectively corresponding to the at least one product identifier through the terminal, or may search the vendor information respectively corresponding to the at least one product identifier in a correspondence relationship between the product identifiers and the vendor information stored in advance. The server may generate one or more purchase orders corresponding to the sales order identification, respectively, based on the provider information. When the supplier information corresponding to the plurality of product identifiers is the same, the plurality of product identifiers and the corresponding purchase quantities may be collectively generated in the same purchase order corresponding to the sales order identifier according to the same supplier information.
Taking a sales order of a certain stationery as an example for explanation, the product identifier may be a product name, the new request of the sales order of the stationery may include information such as product names of a pencil, an eraser, a sign pen, etc., the sales order may be generated according to the information such as the pencil, the eraser, the sign, etc., and the corresponding sales order identifier a1 may be generated according to the information such as the time or the flow when the sales order is generated. Assuming that the server searches the database and obtains supplier information corresponding to the pencil as S1, supplier information corresponding to the eraser as S1, and supplier information corresponding to the sign pen as S2, further generating a purchase order P1 corresponding to the sales order identifier a1 according to the supplier information S1, wherein the P1 includes the supplier information S1, products with product names of pencil and eraser, and corresponding purchase quantity information; meanwhile, a purchase order P2 corresponding to the sales order identification A1 can be generated according to the supplier information S2, wherein the P2 comprises the supplier information S2, a product with the product name of sign pen, the corresponding purchase quantity and the like.
In this embodiment, at least one purchase order corresponding to the sales order identifier is generated according to the provider information corresponding to the product identifier, and when the provider information corresponding to the plurality of product identifiers is the same, one purchase order can be generated according to the same provider information, so that the number of finally generated purchase orders is reduced, and subsequent search and editing of purchase orders under the same provider information are facilitated.
In one embodiment, as shown in FIG. 4, after generating the purchase order corresponding to the sales order identification according to the product identification and the corresponding purchase quantity, the method further comprises the following steps:
at step 402, an edit request for a sales order is obtained.
Specifically, when a user needs to change a stored sales order, an editing request of the sales order can be triggered through the terminal, the terminal sends the editing request of the sales order to the server, and the server obtains the editing request of the sales order.
Step 404, receiving the sales order editing information corresponding to the sales order editing request.
The editing information of the sales order may be input by the user through the terminal, and the editing information of the sales order may refer to information for changing data in the sales order. Modifying the data in the sales order may include adding, modifying, or deleting the data in the sales order, which is not limited herein. Specifically, the user can input edit information of the sales order corresponding to the edit request through the terminal. The terminal sends the editing information to the server, so that the server can modify the data in the sales order according to the editing information of the sales order.
And step 406, updating the sales order and the purchase order corresponding to the sales order identifier according to the editing information of the sales order.
Specifically, after the server obtains the editing information of the sales order, the server modifies the data in the sales order according to the editing information of the sales order. Meanwhile, the server can search the corresponding purchase order through the sales order identification contained in the sales order, and automatically update the purchase order corresponding to the sales order identification according to the editing information of the sales order. Because the editing of the data in the sales order may include adding, modifying, or deleting the data in the sales order, the server may update the purchase order corresponding to the sales identification according to the specific editing type.
Continuing with the description of the stationery sales order as an example, the stationery sales order generated according to the new sales order creation request may include product names of pencil, eraser, sign pen, and 500 corresponding purchase numbers respectively. When the product in the sales order needs to be modified, an editing request for the sales order is obtained, the pencil with the modified product name is obtained as a colored pencil, the product name eraser is deleted, the product name note book is newly added through the editing request, and 300 corresponding purchasing numbers are modified respectively. The modified sales order includes the product name colored pencil, sign-on pen, and note book, and the corresponding purchase quantity 300, respectively. The updated purchase order includes information of product name colored pencil, sign pen, note book and 300 corresponding purchase quantities.
In this embodiment, the terminal updates the sales order according to the editing information and automatically updates the purchase order corresponding to the sales order identifier, so that the purchase information included in the purchase order is consistent with the sales information in the associated sales order, thereby avoiding the problem of erroneous purchase caused by not updating the corresponding purchase order in time due to the change of the sales order, and improving the accuracy of the purchase order.
In one embodiment, as shown in FIG. 5, after generating the purchase order corresponding to the sales order identification according to the product identification and the corresponding purchase quantity, the method further comprises the following steps:
step 502, a sales order deletion request for a sales order is obtained.
Specifically, the user may trigger a delete request for the sales order through the terminal. The terminal acquires a deletion request of the sales order and sends the deletion request to the server.
Step 504, according to the sales order deletion request, a notification is returned whether to delete the purchase order corresponding to the sales order identifier.
Specifically, after acquiring the delete request of the sales order, the server searches for the corresponding purchase order according to the sales order identifier included in the sales order, and returns a notification to the terminal whether to delete the purchase order corresponding to the sales order identifier.
Step 506, if a request for deleting the purchase order corresponding to the sales order identifier is received, the sales order and the purchase order corresponding to the sales order identifier are deleted.
Specifically, if the user triggers a request for deleting the purchase order through the terminal, the terminal sends the request for deleting the purchase order to the server, and the server deletes the sales order and the purchase order corresponding to the sales order identifier according to the acquired request for deleting the purchase order.
Step 508, if a request for not deleting the purchase order corresponding to the sales order identifier is received, deleting the sales order and reserving the purchase order corresponding to the sales order identifier.
Specifically, if the user triggers a request for not deleting the purchase order through the terminal, the terminal sends the request for not deleting the purchase order to the server, the server deletes the sales order according to the acquired request for not deleting the purchase order, and the purchase order corresponding to the sales order identifier is reserved.
In the embodiment, by returning the notice of whether to delete the purchase order corresponding to the sales order identifier, on one hand, the user can quickly send a request of whether to delete the purchase order associated with the sales order to the terminal, the operation is simple, and the unified management in the system is convenient; on the other hand, the problem of wrong purchasing caused by deleting the corresponding purchasing order in a missing mode or a wrong mode can be avoided, and the accuracy of the purchasing order is improved.
In one embodiment, as shown in FIG. 6, after generating the purchase order corresponding to the sales order identification according to the product identification and the corresponding purchase quantity, the method further comprises the following steps:
step 602, acquiring an editing request for a purchase order corresponding to a sales order identifier, where the editing request for the purchase order includes a field to be edited and corresponding editing information.
And step 604, modifying the purchase order corresponding to the sales order identifier according to the editing information corresponding to the field to be edited.
The field to be edited may be an item field included in the purchase order, and the item field may be a supplier, a product name, a purchase quantity, a purchase unit price, and the like, which is not limited herein. The editing information corresponding to the field to be edited may be input by a user through a terminal, and the editing information corresponding to the field to be edited may refer to an updated field value corresponding to the field to be edited. Specifically, a user triggers an editing request of a purchase order through a terminal, wherein the editing request comprises a field to be edited and corresponding editing information. And the terminal sends the editing request of the purchase order, the field to be edited and the corresponding editing information to the server, and the server modifies the purchase order corresponding to the sales order identifier according to the field to be edited and the corresponding editing information.
And step 606, if the field to be edited meets the preset conditions, updating the sales order according to the modification of the purchase order.
Step 608, if the field to be edited does not satisfy the preset condition, canceling the association relationship between the purchase order and the sales order.
The preset condition may refer to a preset item field, and the preset item field may refer to a supplier, a purchase quantity, and a purchase price, which is not limited herein. Specifically, after the server obtains the field to be edited for editing the purchase order and the corresponding editing information, the server can search the sales order associated with the purchase order according to the sales order identifier, and determine whether the obtained field to be edited is within the preset conditions. If the current field is within the preset condition, updating the sales order according to the field to be edited and the corresponding editing information; and if the identification is not in the preset condition, deleting the corresponding relation between the purchase order and the sales order identification, thereby canceling the association relation between the purchase order and the sales order.
Continuing with the description of the stationery sales order as an example, the field to be edited may be an item field, and the preset condition may be a preset item field purchase quantity. The selling order and the corresponding purchasing order of the stationery can both comprise item fields, product names and purchasing quantities, the product names correspond to field values, namely pencils, erasers and sign pens, and the purchasing quantities respectively correspond to the field values of 500. If all the procurement quantities in the modified procurement order are 300, the procurement quantities in the corresponding updated sales order are 300 because the procurement quantities in the item fields are within the preset item fields. If the pencil for modifying the product name in the purchase order is the colored pencil, the product name in the item field is not in the preset item field, so that the purchase order is modified, the sales order identifier is deleted, the association relationship between the purchase order and the sales order is cancelled, and the data in the sales order is not updated.
In the embodiment, whether the field to be edited for editing the purchase order is within the preset condition is judged, and the sales order related to the purchase order is updated according to different judgment results, so that the problem of wrong sales caused by the fact that the related sales order is updated by mistake due to the fact that the purchase order is changed can be avoided, and the accuracy of the sales order is improved.
In one embodiment, as shown in FIG. 7, after generating the purchase order corresponding to the sales order identification according to the product identification and the corresponding purchase quantity, the method further comprises the following steps:
at step 702, a purchase order deletion request for a purchase order corresponding to a sales order identification is obtained.
Step 704, delete the purchase order corresponding to the sales order identification according to the purchase order deletion request.
Specifically, the purchase order corresponding to the sales identification may include one or more purchase orders, and the user may trigger a deletion request of the purchase order through the terminal to select to delete one or more purchase orders, which is not limited herein. And the terminal sends the deletion request of the one or more purchase orders to the server, so that the server can delete the corresponding one or more purchase orders according to the obtained deletion request of the one or more purchase orders. In this embodiment, by obtaining the deletion request for the one or more purchase orders corresponding to the sales order identifier, the corresponding purchase orders are deleted according to the deletion request for the one or more purchase orders, and without affecting the association between other purchase orders corresponding to the sales order identifier and the sales orders, which is convenient for the user to manage the one or more purchase orders corresponding to the sales order identifier in the system.
In one embodiment, as shown in FIG. 8, after generating the purchase order corresponding to the sales order identification according to the product identification and the corresponding purchase quantity, the method further comprises the following steps:
step 802, obtaining a delivery quantity corresponding to the product identifier in the sales order.
The delivery quantity may be a quantity of a product corresponding to the product identifier actually delivered to the customer. The user may input the delivery quantity corresponding to the product identifier in the sales order through the terminal, which is not limited herein.
Step 804, determining whether a rapid receiving is preset for the purchase order corresponding to the sales identification.
Step 806, if it is determined that rapid receiving is preset, generating a receiving quantity of the purchase order corresponding to the sales identification according to the delivery quantity and the purchase quantity.
The fast receiving may be a function of automatically updating the receiving quantity in the purchase order corresponding to the sales order identifier according to the receiving quantity in the sales order and the purchasing quantity in the purchase order. The express delivery function may be, but is not limited to, setup save when a sales order is newly created. Specifically, the server may determine whether a rapid receiving function is preset after acquiring the delivery quantity. If the rapid receiving function is preset, finding the corresponding purchase order according to the sales order identification contained in the sales order, and generating the receiving quantity corresponding to the product identification in the purchase order according to the delivery quantity corresponding to the product identification in the sales order and the purchase quantity in the purchase order.
In this embodiment, generating the receiving quantity of the purchase order corresponding to the sales identifier according to the delivery quantity and the purchase quantity specifically includes: if the delivery quantity corresponding to the product identification is smaller than the purchase quantity, determining the delivery quantity as the receiving quantity in the purchase order corresponding to the sale identification; and if the delivery quantity corresponding to the product identifier is larger than or equal to the purchase quantity, determining the purchase quantity as the receiving quantity in the purchase order corresponding to the sales identifier.
Specifically, the user may input the delivery quantity corresponding to the product identifier in the sales order through the terminal. And after the terminal acquires the delivery quantity, the delivery quantity is sent to the server. And after the server acquires the delivery quantity, the corresponding purchase order is searched according to the sales order identification contained in the sales order. The server compares the delivery quantity corresponding to the product identification with the purchase quantity in the purchase order, and when the delivery quantity corresponding to the product identification is smaller than the purchase quantity, the receiving quantity in the purchase order is automatically updated to be equal to the delivery quantity; and when the delivery quantity corresponding to the product identification is greater than or equal to the purchase quantity, automatically updating the receiving quantity in the purchase order to be equal to the purchase quantity.
Continuing with the description of the above-mentioned stationery sales order as an example, a quick receipt is set in advance for the stationery sales order. The selling order of the stationery comprises product name pencils, erasers and sign pens, and the purchasing order comprises the product name pencils, the erasers and the sign pens and 500 purchasing numbers respectively corresponding to the product name pencils, the erasers and the sign pens. Acquiring the delivery quantity of 400 pencils, the delivery quantity of 500 erasers and the delivery quantity of 600 signpens in a sales order, respectively comparing the delivery quantity and the purchase quantity corresponding to product names, and automatically updating the receiving quantity of 400 pencils in the purchase order according to the delivery quantity if the delivery quantity of 400 pencils is less than the purchase quantity of 500 pencils; if the delivery quantity of the eraser is 500 and the purchase quantity is 500, automatically updating the receiving quantity of the eraser in the purchase order to be 500 according to the purchase quantity; and if the delivery quantity of 600 sign pens is greater than the purchase quantity of 500 sign pens, automatically updating the receiving quantity of 500 sign pens in the purchase order according to the purchase quantity.
Furthermore, the purchase order corresponding to the sales order identifier may further include a receiving state, and when the server determines that the received delivery quantity corresponding to the product identifier is less than the purchase quantity, the receiving state in the purchase order is updated to be a partial receiving state; and when the server judges that the received delivery quantity corresponding to the product identification is greater than or equal to the purchase quantity, updating the receiving state in the purchase order to be all receiving.
In this embodiment, by acquiring the rapid receiving setting request, the receiving quantity in the purchase order can be automatically updated according to the delivery quantity of the acquired sales order and the purchase quantity in the purchase order corresponding to the sales order identifier, so as to simplify the process of updating the associated purchase order, and greatly facilitate the user to timely acquire accurate receiving and delivery information of the product in the purchase order corresponding to the sales identifier.
In one embodiment, before obtaining the new request of the sales order, the method further comprises: and acquiring a preset request of a new request of the sales order, wherein the preset request is used for indicating to generate a purchase order corresponding to the sales order identifier.
The preset request may be a setting request for quickly generating a purchase order according to a sales order. Specifically, the user can quickly generate a purchase order by presetting the order through the terminal. Under the condition of presetting to generate the purchase order rapidly, the sales order generated by the server can comprise a unique sales order identification. When generating a sales order, the server can automatically generate a purchase order according to information such as a product identifier included in the sales order, and establish an association relationship between the sales order and the purchase order through the sales order identifier.
In this embodiment, the purchase order associated with the sales order can be automatically generated according to the preset request, thereby greatly simplifying the process of creating the sales order and the associated purchase order. In addition, when the user does not need to create the associated sales order and purchase order, the user can create the order according to different requirements by canceling the presetting.
In one embodiment, as shown in FIG. 9, the present application provides a method of generating a purchase order, the method further comprising the steps of:
step 901, obtain a preset request for a sales order. According to the preset request, a purchase order related to a sales order can be synchronously generated, the sales order comprises a unique sales order identification, and the sales order and the purchase order are related through the sales order identification.
Step 902, a new request of a sales order is obtained, and a corresponding product identifier and a corresponding purchase quantity are obtained according to the new request.
Step 903, generating a sales order according to the product identifier, wherein the sales order comprises a sales order identifier.
And 904, determining supplier information corresponding to each product identification.
Step 905, generate a purchase order corresponding to the sales order identifier according to the product identifier, and the corresponding purchase quantity and supplier information.
Step 906, obtain an edit request for the sales order and sales order edit information corresponding to the edit request for the sales order.
Step 907, updating the sales order and the purchase order corresponding to the sales order identifier according to the editing information of the sales order.
Step 908, obtain a sales order delete request for the sales order.
Step 909, if a request for deleting the purchase order corresponding to the sales order identifier is received, deleting the sales order and the purchase order corresponding to the sales order identifier; otherwise, the sales order is deleted and the purchase order is retained.
Step 910, obtain an edit request for a purchase order corresponding to the sales order identifier, where the purchase order edit request includes a field to be edited and corresponding edit information.
Step 911, modify the purchase order corresponding to the sales order identification according to the field to be edited and the corresponding editing information.
Step 912, if the field to be edited meets the preset conditions, updating the sales order according to the modification of the purchase order; otherwise, deleting the corresponding sale order mark in the purchase order.
At step 913, a purchase order delete request for the purchase order corresponding to the sales order identification is obtained.
Step 914, delete the purchase order corresponding to the sales order identification according to the purchase order deletion request.
Step 915, obtaining the delivery quantity corresponding to the product identifier in the sales order.
Step 916, determine whether a quick receiving is preset for the purchase order corresponding to the sales identification.
Step 917, when it is judged that quick receiving is preset, generating a receiving quantity of the purchase order according to the delivery quantity and the purchase quantity.
It should be understood that although the various steps in the flow charts of fig. 1-9 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 1-9 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in FIG. 10, there is provided a purchase order generating apparatus including: an acquisition module 1002, a sales order generation module 1004, and a purchase order generation module 1006, wherein:
an obtaining module 1002, configured to obtain a new request for a sales order;
the obtaining module 1002 is further configured to obtain a corresponding product identifier and a purchase quantity corresponding to the product identifier according to the new request;
a sales order generation module 1004 for generating a sales order according to the product identifier, the sales order including a sales order identifier;
and a purchase order generation module 1006, configured to generate a purchase order corresponding to the sales order identifier according to the product identifier and the corresponding purchase quantity, and establish an association relationship between the sales order and the purchase order through the sales order identifier.
In one embodiment, the system further comprises a supplier information confirmation module for determining supplier information according to the product identification.
In one embodiment, the obtaining module 1002 is further configured to obtain an edit request for the sales order. In this embodiment, the system further includes a receiving module, configured to receive editing information of the sales order corresponding to the editing request of the sales order; and the updating module is used for updating the sales order and the purchase order corresponding to the sales order identification according to the editing information of the sales order.
In one embodiment, the obtaining module 1002 is further configured to obtain a sales order deletion request for a sales order. In this embodiment, the system further includes a sending module, configured to return a notification whether to delete the purchase order corresponding to the sales order identifier according to the sales order deletion request; the system further comprises a deleting module for deleting the sales order and the purchase order corresponding to the sales order identifier when a request for deleting the purchase order corresponding to the sales order identifier is received.
In one embodiment, the obtaining module 1002 is further configured to obtain an editing request for a purchase order corresponding to the sales order identifier, where the editing request for the purchase order includes a field to be edited and corresponding editing information. In this embodiment, the updating module is further configured to modify the purchase order corresponding to the sales order identifier according to the editing information corresponding to the field to be edited. If the field to be edited meets the preset condition, updating the sales order according to the modification of the purchase order; and if the field to be edited does not meet the preset condition, deleting the corresponding sales order identification in the purchase order.
In one embodiment, acquisition module 1002 is further configured to acquire a purchase order deletion request for a purchase order corresponding to the sales order identification; the deleting module is further used for deleting the purchase order corresponding to the sales order identification according to the purchase order deleting request.
In one embodiment, the obtaining module 1002 is further configured to obtain a delivery quantity corresponding to the product identifier in the sales order. In this embodiment, the system further includes a determining module, configured to determine whether to preset a fast receiving for the purchase order corresponding to the sales identifier. And if the quick receiving is preset, generating the receiving quantity of the purchase order corresponding to the sales identification according to the delivery quantity and the purchase quantity.
In one embodiment, the system further comprises a setting module, configured to obtain a preset request for a new request of the sales order, where the preset request is used to instruct generation of a purchase order corresponding to the sales order identifier.
For the specific definition of the purchase order generation apparatus, reference may be made to the above definition of the purchase order generation method, which is not described herein again. The modules of the purchase order generating device can be implemented in whole or in part by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 11. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing data such as sales orders and purchase orders. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a purchase order generation method.
Those skilled in the art will appreciate that the architecture shown in fig. 11 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, there is provided a purchase order generation system comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program implementing the steps of:
acquiring a new request of a sales order; acquiring a corresponding product identifier and a purchase quantity corresponding to the product identifier according to the new building request; generating a sales order according to the product identifier, wherein the sales order comprises a sales order identifier; and generating a purchase order corresponding to the sales order identification according to the product identification and the corresponding purchase quantity, and establishing an association relationship between the sales order and the purchase order through the sales order identification.
In one embodiment, after obtaining the corresponding product identifier and the purchase amount corresponding to the product identifier according to the new request, the processor executes the computer program to implement the following steps:
determining corresponding supplier information according to the product identification; and generating a purchase order corresponding to the sales order identification according to the product identification, the corresponding purchase quantity and the supplier information.
In one embodiment, after generating a purchase order corresponding to the sales order identification based on the product identification and the corresponding purchase quantity, the processor when executing the computer program performs the steps of:
acquiring an editing request for a sales order; receiving the editing information of the sales order corresponding to the editing request of the sales order; and updating the sales order and the purchase order corresponding to the sales order identification according to the editing information of the sales order.
In one embodiment, after generating a purchase order corresponding to the sales order identification based on the product identification and the corresponding purchase quantity, the processor when executing the computer program performs the steps of:
obtaining a sales order deletion request for a sales order; returning a notice whether to delete the purchase order corresponding to the sales order identification according to the sales order deletion request; if a request for deleting the purchase order corresponding to the sales order identifier is received, deleting the sales order and the purchase order corresponding to the sales order identifier; and if a request for not deleting the purchase order corresponding to the sales order identifier is received, deleting the sales order and reserving the purchase order corresponding to the sales order identifier.
In one embodiment, after generating a purchase order corresponding to the sales order identification based on the product identification and the corresponding purchase quantity, the processor when executing the computer program performs the steps of:
acquiring an editing request of a purchase order corresponding to a sales order identifier, wherein the editing request of the purchase order comprises a field to be edited and corresponding editing information; modifying the purchase order corresponding to the sales order identification according to the editing information corresponding to the field to be edited; if the field to be edited meets the preset condition, updating the sales order according to the modification of the purchase order; and if the field to be edited does not meet the preset conditions, canceling the association relationship between the purchase order and the sales order.
In one embodiment, after generating a purchase order corresponding to the sales order identification based on the product identification and the corresponding purchase quantity, the processor when executing the computer program performs the steps of:
acquiring a purchase order deletion request for a purchase order corresponding to the sales order identifier; and deleting the purchase order corresponding to the sales order identification according to the purchase order deletion request.
In one embodiment, after generating a purchase order corresponding to the sales order identification based on the product identification and the corresponding purchase quantity, the processor when executing the computer program performs the steps of:
acquiring the delivery quantity corresponding to the product identification in the sales order; judging whether quick receiving is preset for a purchase order corresponding to the sales identification or not; and if the quick receiving is preset, generating the receiving quantity of the purchase order corresponding to the sales identification according to the delivery quantity and the purchase quantity.
In one embodiment, the processor, when executing the computer program, performs the steps of:
if the delivery quantity corresponding to the product identification is smaller than the purchase quantity, determining the delivery quantity as the receiving quantity in the purchase order corresponding to the sale identification; and if the delivery quantity corresponding to the product identifier is larger than or equal to the purchase quantity, determining the purchase quantity as the receiving quantity in the purchase order corresponding to the sales identifier.
In one embodiment, prior to obtaining the new request for the sales order, the processor when executing the computer program performs the steps of:
and acquiring a preset request of a new request of the sales order, wherein the preset request is used for indicating to generate a purchase order corresponding to the sales order identifier.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
acquiring a new request of a sales order; acquiring a corresponding product identifier and a purchase quantity corresponding to the product identifier according to the new building request; generating a sales order according to the product identifier, wherein the sales order comprises a sales order identifier; and generating a purchase order corresponding to the sales order identification according to the product identification and the corresponding purchase quantity, and establishing an association relationship between the sales order and the purchase order through the sales order identification.
In one embodiment, after obtaining the corresponding product identifier and the purchase quantity corresponding to the product identifier based on the new request, the computer program when executed by the processor implements the following steps:
determining corresponding supplier information according to the product identification; and generating a purchase order corresponding to the sales order identification according to the product identification, the corresponding purchase quantity and the supplier information.
In one embodiment, after generating a purchase order corresponding to the sales order identification based on the product identification and the corresponding purchase quantity, the computer program when executed by the processor performs the steps of:
acquiring an editing request for a sales order; receiving the editing information of the sales order corresponding to the editing request of the sales order; and updating the sales order and the purchase order corresponding to the sales order identification according to the editing information of the sales order.
In one embodiment, after generating a purchase order corresponding to the sales order identification based on the product identification and the corresponding purchase quantity, the computer program when executed by the processor performs the steps of:
obtaining a sales order deletion request for a sales order; returning a notice whether to delete the purchase order corresponding to the sales order identification according to the sales order deletion request; if a request for deleting the purchase order corresponding to the sales order identifier is received, deleting the sales order and the purchase order corresponding to the sales order identifier; and if a request for not deleting the purchase order corresponding to the sales order identifier is received, deleting the sales order and reserving the purchase order corresponding to the sales order identifier.
In one embodiment, after generating a purchase order corresponding to the sales order identification based on the product identification and the corresponding purchase quantity, the computer program when executed by the processor performs the steps of:
acquiring an editing request of a purchase order corresponding to a sales order identifier, wherein the editing request of the purchase order comprises a field to be edited and corresponding editing information; modifying the purchase order corresponding to the sales order identification according to the editing information corresponding to the field to be edited; if the field to be edited meets the preset condition, updating the sales order according to the modification of the purchase order; and if the field to be edited does not meet the preset conditions, canceling the association relationship between the purchase order and the sales order.
In one embodiment, after generating a purchase order corresponding to the sales order identification based on the product identification and the corresponding purchase quantity, the computer program when executed by the processor performs the steps of:
acquiring a purchase order deletion request for a purchase order corresponding to the sales order identifier; and deleting the purchase order corresponding to the sales order identification according to the purchase order deletion request.
In one embodiment, after generating a purchase order corresponding to the sales order identification based on the product identification and the corresponding purchase quantity, the computer program when executed by the processor performs the steps of:
acquiring the delivery quantity corresponding to the product identification in the sales order; judging whether quick receiving is preset for a purchase order corresponding to the sales identification or not; and if the quick receiving is preset, generating the receiving quantity of the purchase order corresponding to the sales identification according to the delivery quantity and the purchase quantity.
In one embodiment, the computer program when executed by the processor implements the steps of: if the delivery quantity corresponding to the product identification is smaller than the purchase quantity, determining the delivery quantity as the receiving quantity in the purchase order corresponding to the sale identification; otherwise, determining the purchase quantity as the receiving quantity in the purchase order corresponding to the sales identification.
In one embodiment, prior to obtaining a new request for a sales order, a computer program when executed by a processor performs the steps of:
and acquiring a preset request of a new request of the sales order, wherein the preset request is used for indicating to generate a purchase order corresponding to the sales order identifier.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.