JP2014048765A - Shipping result information replacement device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a shipping result information replacement device in which even when the number of item is large, erroneous input can be prevented.SOLUTION: A shipping result information replacement device includes: a shipment schedule information database for storing before-correction order intake number, latest order intake number, shipping result number and delivery scheduled date in association with one another; and an operation part for specifying, when among different cases, the before-correction order intake number and the latest order intake number coincide with each other, have the same delivery scheduled data, a case in which the latest order intake number is 0 is specified as a correction order intake case, and a case in which otherwise is specified as a new order intake case, calculating a replacement number by subtracting the shipping result number from the latest order intake number of the correction order intake case in the shipping schedule information database, subtracting the replacement number from the shipping result number of the correction order intake case, and adding the replacement number to a shipping result number of the new order intake case.

Description

  The present invention relates to a technique for supporting replacement of shipment record information in a system for managing a shipment plan.

  In the build-to-order manufacturing, a shipment plan is determined in consideration of order information (shipment item, required delivery date, quantity, etc.), what time, what and where. For example, Japanese Patent Application Laid-Open No. 2011-145722 discloses that a shipment plan is created by automating the association between forecast and order information.

  In a system for managing such a shipping plan, order information, shipping results, etc. are registered and managed for each item. In this system, the order information may be changed in the middle along with the change of the orderer or the change of the contract contents. For example, there is a case where an order once registered in the system is canceled and registered as another order information as a new case, or a case where the number of original orders is reduced and the number of new orders is registered.

JP 2011-145722 A

  The above-mentioned shipment record is recorded when the shipment is actually made. However, when the order information as described above is changed, the number of orders after the change and the number of shipment results do not coincide with each other, resulting in an inconsistent state. Therefore, it is necessary to change the number of shipments later so as to correspond to the actual number of orders received. At present, the distribution of the actual number of shipments is a manual operation by the user. If the order contents before and after the change are confirmed and it is determined that the orders are the same, the actual number of shipments is replaced. Has been implemented. The judgment is made on the basis of experience by comparing various information such as comparing the number of orders received and the number of shipments, and looking at the model name of the ordered product.

  Therefore, when the number of cases is large, it is not easy to find and replace the same order item, and there is a possibility that an erroneous input may occur such that a variety of cases are mistaken as replacement cases. An object of the present invention is to support so as to prevent an erroneous input of the replacement work.

  In order to solve the above problems, the shipping plan information database that stores the number of orders received before correction, the latest number of orders received, the actual number of shipments, and the scheduled delivery date for each case, and the order received before correction among the different cases. If the planned delivery date is the same for an item with the same number of orders as the number of the latest orders, the one with the latest order number of 0 is identified as a corrected order item, and the other is designated as a new order item, and the shipment plan information database Subtract the number of shipments from the latest number of orders received for the corrected order and calculate the number of deliveries, subtract the number of deliveries from the number of deliveries for the corrected order and obtain the number of deliveries for the new order received The calculation unit that adds the number of replacements and performs the replacement process, and if the new order entry is not identified as one even if the scheduled delivery date does not match, each new order entry is displayed as a candidate for replacement And a display unit.

  It is possible to easily perform the replacement process of the shipping record information.

It is a related figure of order information input-shipment plan input-member ordering. It is a system configuration figure of this embodiment. This is order database information of the present embodiment. It is the shipping database information of this embodiment. It is the shipping plan database information of this embodiment. It is a flowchart of the shipping result distribution automation of this embodiment. It is the shipping plan database information after the delivery performance replacement of this embodiment.

  As an embodiment of the present invention, a shipping result information allocating device for automatically allocating shipping results will be described. The shipment result information allocating device may exist as a single device or may be on each server side to be described below, and is not limited.

  FIG. 1 is a system related diagram from order information input to shipping plan input to ordering of parts. The order information input / output terminal 101 is connected to the in-house network 102, and inputs / outputs data to / from the order information management unit 103 that manages the order information from the order information input / output terminal 101. The shipping record information input from the shipping information input / output terminal 110 connected to the in-house network 102 is input / output to / from the shipping record information management unit 104 that manages the shipping record information. The data managed by the order information management unit 103 and the shipping result information management unit 104 is distributed to the shipping plan management unit 105 that manages the shipping plan information and is connected to the in-house network 102. 109 as release plan information. In the shipping plan input / output terminal 109, the user searches for order information and shipping record information, registers data, and distributes the number of shipping plans to the production plan management unit 106, which is a subsequent process. The production plan management unit 106 devises a production plan based on the number of shipment plans received from the shipment plan management unit 105, distributes the number of production plans calculated here to the backbone system 107, and after ordering the required parts, parts ordering is performed. For necessary items, order data is distributed to the supplier 108.

  FIG. 2 shows a system configuration diagram of the present invention. A Web server 201 that controls input / output of order information includes a control unit and a communication unit, and communicates with the order information input / output terminal (client PC) 205 and the AP server 202 via the communication unit. The AP server 202 includes a receiving unit that receives order information, a calculation unit, a communication unit, and a display unit for displaying replacement candidates. The AP server 202 communicates with the DB server 204 via the communication unit. The shipping information management server 203 includes a calculation unit and a communication unit. The shipping information registered by the shipping information input / output terminal (client PC) 207 communicates with the DB server 204 via the communication unit, and the DB server Delivery result information is distributed to 204.

  The DB server 204 includes a storage unit that stores order information, shipment plan information, and shipment record information, and a communication unit. These pieces of information include the Web server 201, the AP server 202, the shipment information management server 203, and the shipment plan information. It is registered from the input / output terminal (client PC) 206. The configuration here is not limited to this. For example, the database may be in a separate device such as the AP server 202 without dividing the DB server 204.

  In addition, the replacement process is performed in the calculation unit of the AP server 202, but is not limited to this, and may be processed by the AP server 202 or may be processed by the calculation unit of the shipping information management server. It is not limited.

  FIG. 3 shows an order information database used in the present invention. The order information database in FIG. 3 assigns the sales department code assigned to each sales department to determine the department in charge, the final customer code that identifies the company of the customer to be delivered last, and the order received for each sales department. It includes an order number, an orderer code for identifying an ordering company, a Rev for managing the history of order information, an order model name for identifying a product, a scheduled delivery date to the customer for the order, and an order quantity ordered by the customer.

  FIG. 4 shows a shipping information database used in the present invention. The shipping information database in FIG. 4 assigns the sales department code assigned to each sales department to determine the department in charge, the final customer code that identifies the company of the customer to be delivered last, and the order received for each sales department. Order number, orderer code identifying the ordering company, order name identifying the product, number of shipments indicating the number of shipments, shipment date indicating the date of shipment, numbering for each shipment case when shipping Shipping NO is provided.

  FIG. 5 is a diagram showing a shipping plan information database used in the present invention. The shipping plan information database shown in FIG. 5 assigns the sales department code assigned to each sales department in order to determine the sales department in charge, the final customer code that identifies the company of the customer to be delivered last, and the number of orders received for each sales department. Order number to identify the ordering company, Rev to manage the history of the order information, order name to identify the product, scheduled delivery date to the customer for the order, change to indicate the number of orders in the previous history information It includes a previous order quantity, an order quantity ordered from a customer with the latest history, a shipment record number indicating the number of shipments for the order, and a latest Rev flag indicating the latest order history. The number of actual shipments here means the actual number of shipments, and is 0 immediately after the order is received. When the shipment is confirmed, the data of the number of shipments is updated. This database may be created based on the information in the order information database and the shipping information database.

  FIG. 6 is a flowchart in the case where the automatic replacement of the shipping record number for the corrected order information and the new order information according to the order change of the present invention and the determination of the candidate for replacement. In step 601, via the order information input / output terminal (client PC) 205, as shown in FIG. 3, sales department code, order number, orderer code, final customer code, order name, scheduled delivery date, latest order quantity, etc. The information is input by the user, and the input content is received by the communication unit of the AP server 202 and stored in the order information storage unit of the DB server 204. Based on this stored content, the data reception is completed by writing to the shipping plan information storage unit of the DB server 204 (step 602), and the sales department code, received order number, orderer code, and final customer code of the received data are already present. If there is a case that is the same as the registered order information, the order information is updated with the already registered order information as the past Rev information, and the shipping plan information storage unit is updated with the order information received this time as the latest Rev information. (Step 603).

  More specifically, the case where the sales department code, the final customer code, the order receipt NO, the orderer code, and the Rev in FIG. 5 are already present in the shipping plan information storage unit is A001-000100-0001-000100-001. Sales department code-final customer code-order received NO-order owner code-When Rev receives data of A001-000100-0001-000100-002, sales department code-final customer code-order received NO-order owner code-Rev For the order item A001-000100-0001-000100-001, the latest Rev flag is updated to OFF as past Rev information, and the latest Rev flag is set to ON with the order item A001-000100-0001-000100-002 as the latest Rev information. The shipping plan information storage unit is updated.

  Next, in step 604, the shipping information (FIG. 4) input from the shipping information input / output terminal (client PC) 207 is written into the DB server 204 via the communication unit of the shipping information management server 203. Next, in step 605, the number of actual shipments and the latest number of orders are compared with the order information of the corrected case, and the order information with the actual number of shipments larger than the latest number of orders is received (specifically, sales department code-final in FIG. 5). Customer code-order received NO-order owner code A001-000100-0001-000100 has 8 orders received and 10 actual shipments, so A001-000100-0001-000100 is a candidate for replacement.

The order information is displayed in the following format: XXXX-XXXXXXX-XXXX-XXXXXXX. If the actual number of shipments is less than the latest number of orders, the process proceeds to the determination process for the next order item without being subject to replacement. Next, in step 606, a new order receiving matter having the same sales department code as the order receiving information that has become a replacement candidate in step 605 is matched. If there is a reconciliation target, then in step 607, it is compared whether the same final customer code matches using the order information and the new order item in which the number of shipments up to the above is greater than the latest order number. Next, in step 608, it is compared whether the order form names match.
Next, in step 609, when the latest order number before the change is 0 and the order number before the change and the latest order number of the new order matter are compared and matched, the matter of the order number before the change is corrected, The item with the latest number of orders is identified as a new order item, and in step 610, the scheduled delivery date of the order information before change is compared with the scheduled delivery date of the new order item. Here, the case where the number of the latest orders before the change is 0 means that the orders have been canceled once. Conversely, when it is not 0, this is the case where the number of orders has changed. In this embodiment, the candidate for replacement is selected from the four types of codes that match the sales department code, the final customer code, the order number, and the orderer code. However, the present invention is not limited to this. If it is found that the same department has received an order for the same product, the number of orders received and the actual number of shipments are compared for that matter.

  Specifically, the sales department code C001, the final customer code 000100, the order name YY0001, YY0002, the order quantity before change 50, the estimated delivery date 2011/03/22 of the case of the order information C001-000100-0010-000100 in FIG. Are compared, and C001-000100-0010-X00100 is extracted as a replacement candidate.

  The data determined to be the same in the above determination processing determines that the order information before change and the new order item are the same item, and subtracts the latest order number from the actual shipment number of the corrected order item in step 611. The remaining number is calculated as the number of replacements (number of comparisons for replacement). In the present embodiment, all are the same. However, the present invention is not limited to this, and it is sufficient if it is determined to be the same case. We just need to be able to confirm.

  Specifically, 50 is calculated by subtracting the shipment actual number 50 from the latest order number 0 of C001-000100-0010-000100 of the corrected order information in FIG. Next, the number of distributions 50 calculated in step 611 is added as the number of actual shipments of new order information as a candidate for replacement, and the actual number of shipments of the pre-correction item is updated by subtracting the number of actual shipments allocated. . In other words, the number of replacements 50 is added to the number of actual shipments of new order information C001-000100-0010-X00100 as replacement candidates in FIG. As a result of the addition, the actual number of orders is 50 with respect to the latest number of orders 50. Next, the shipping actual number of the corrected order information C001-000100-0010-000100 is subtracted from the added 50, and the actual shipping number becomes zero. As a result of the replacement, the number of actual shipments is 0 with respect to the latest number of orders received. The replacement process is now complete, and a specific example of the processed result is shown in FIG.

  On the other hand, if it is determined in step 610 that the scheduled delivery dates do not match, in step 613, if there is one new order information that matches in the determination up to step 609, it is determined as an order replacement target. Next, a replacement process is performed in steps 611 and 612 described above. There are two or more pieces of new order information that coincide in the determination up to step 609 (specifically, C001-000100-0010-X00100, C001-000100-0020-X00100, C001-000100-0030- of the order information in FIG. 5). In the case of X00100, C001-000100-0040-X00100), the allocation accuracy when displaying on the allocation candidate selection screen in step 614 is the accuracy of the allocation candidates in the order of A (A → B → C → D). The number of shipments is to be distributed by selecting a target from the candidate selection screen at the discretion of the user, and automatic distribution is not performed.

  If it is determined in step 609 that the number of latest orders before the change is other than 0, or if the number of orders received before the change in the corrected order and the latest number of orders in the new order are not the same, the number of actual shipments of the corrected order received in step 615 Subtract the latest number of orders and calculate the number of comparisons for replacement. Specifically, the latest order number 2 is subtracted from the shipment result number 10 of A001-000100-1200-000100 in the order information shown in FIG.

  Next, in step 616, the number of shipment comparisons calculated from the above-mentioned step 615 (if the remaining number of replacements is greater than 0, the remaining number of replacements may be compared) and the latest number of orders received for a new order received. Are compared (specifically, the shipment actual number 0 is subtracted from the latest order number 15 of A001-000100-1203-000100 in the order information of FIG. 5 to calculate 15).

  If the quantities match in the comparison process in step 616, the number of comparisons for replacement (if the number of remaining replacements is greater than 0, the number of remaining replacements may be set) as the number of replacements in step 617. Next, in step 618, 0 is set as the remaining number of replacements, and B is set as the replacement accuracy. This is because the probability of replacement is high even if the date is the same even if the quantity is different, so it is set here as B. In step 609, it is determined whether or not there is a new order number that is the same as the corrected order number, and in step 616, the number of delivery replacements is compared. For example, if the order quantity before change of the corrected order item is 50, the latest order quantity is 10, and the actual shipment quantity is 50 (the original order was received at 50 but the order was changed to 10 and the shipment has already been made 50), The order quantity before change is 0, the latest order quantity is 40, and the actual shipment quantity is 0 (a new order that has 10 new orders and the shipment is unconfirmed).

  Subsequently, in step 619, a comparison process of the scheduled delivery date is performed. If the scheduled delivery dates match in the comparison processing in step 619, the number of actual shipments is replaced in step 612 described above. If the scheduled delivery dates do not match in step 619, if there is one new order information that matches in the determination up to step 616 in step 620, it is determined as an order replacement target, and the replacement process in step 612 described above. I do. If there are two or more pieces of new order information that match in the determinations up to step 616, they are displayed on the replacement candidate selection screen in step 621, and the target is selected from the candidate selection screen according to the user's judgment, and the number of actual shipments is determined. It will be distributed, and automatic distribution will not be implemented.

  Next, in the comparison process in step 616, the quantity is the comparison number (if the remaining number is larger than 0, it may be the remaining number). The quantity obtained by subtracting the actual number of shipments from the latest number of orders for new orders. If larger, in step 622, the replacement number is set as the replacement comparison number.

  Next, in step 623, 0 is set as the remaining number of replacements, and C is set as the replacement accuracy. Thereafter, the determination process in step 619 and the determination process in step 620 described above are performed, and the replacement process in step 612 or the replacement candidate selection screen in step 621 is displayed. Specifically, the example in which the replacement process is performed is the replacement to the new order information E001-000100-0003-000100 in which items other than the quantity match the E001-000100-2200-000100 of the order information shown in FIG. A quantity of 10 is distributed. A specific example of the attached processing result is shown in FIG.

  In addition, in the comparison process in step 616, the quantity is the comparison number (if the remaining number is less than 0, it may be the remaining number), the quantity obtained by subtracting the actual number of shipments from the latest number of orders for new orders. If it is smaller, in step 624, subtract the latest order quantity and the actual number of shipments of the new order from the comparison comparison number (if the remaining number is larger than 0, it may be the remaining number). Calculate the number. Next, in step 625, the number of replacements calculated in step 624 is subtracted from the number of comparisons for replacement (the number of remaining replacements may be used if the number of remaining replacements is greater than 0). (Remaining number) is calculated. Next, in the comparison process in step 626, if the scheduled delivery dates match, an exchange process is performed in step 627. In step 627, replacement is performed in the same process as step 612 described above. If the scheduled delivery dates do not match in step 627, if there is one new order information that matches in the determinations up to step 616, it is determined as an order replacement target, and the replacement process is performed in step 627 described above. If there are two or more pieces of new order information that match in the determinations up to step 616, they are displayed on the replacement candidate selection screen as replacement accuracy D in step 629, and the target is selected from the candidate selection screen according to the user's judgment. The number of actual shipments will be distributed, and automatic distribution will not be implemented. The new order information that does not match the results of comparison in step 606, step 607, and step 608 is set as data to be displayed on the replacement candidate selection screen in step 630, and automatic replacement is not performed.

  In this case, the number of replacements is smaller than the number of comparisons for replacement, and one project is replaced with a plurality of projects. Therefore, a plurality of candidate projects are narrowed down by looping the replacement process. In FIG. 5, after the replacement process is completed in step 627, the process returns to step 606 to sequentially identify replacement cases.

101: Order information input / output terminal, 102: Internal network, 103: Order information management unit, 104: Shipment record information management unit, 105: Shipment plan information management unit, 106: Production plan management unit, 107: MRP to order processing unit 108: Supplier companies, 109: Shipment plan input / output terminal, 110: Shipment information input / output terminal, 201: Web server for controlling input / output of order information, 202: DB registration processing server for order information, 203: Shipment information DB registration processing server, 204: server for receiving order information, shipment plan information, shipment record information, 205: order information input / output terminal (client PC), 206: shipment plan information input / output terminal (client PC), 207: Shipping information input / output terminal (client PC), 301: Sales department code, 302: Final customer code, 303: Order number NO, 30 : Order owner code, 305: Rev, 306: Order model name, 307: Expected delivery date, 308: Latest order quantity, 401: Sales department code, 402: Final customer code, 403: Order number, 404: Order owner code, 405: Order model name, 406: Shipment actual quantity, 407: Shipment date, 408: Shipment number, 501: Sales department code, 502: Final customer code, 503: Order number, 504: Order owner code, 505: Rev, 506 : Order model name, 507: Scheduled delivery date, 508: Order quantity before change, 509: Latest order quantity, 510: Actual shipment quantity, 511: Latest Rev flag, 601: Order information input process, 602: Order information reception process, 603: Order information fetch processing, 604: Shipment record information reception process, 605: Order number / shipment record number determination process, 606: Same office code determination process, 07: Same customer determination process, 608: Same order form determination process, 609: Same order number determination process, 610: Same delivery date determination process, 611: Replacement number calculation process, 612: Shipment actual number replacement process, 613: Replacement candidate number determination processing, 614: Replacement candidate setting processing, 615: Replacement comparison number calculation processing, 616: Replacement number determination processing, 617: Replacement number setting processing, 618: Replacement remaining number, accuracy Setting process, 619: Same scheduled delivery date determination process, 620: Replacement candidate number determination process, 621: Replacement candidate setting process, 622: Replacement number calculation process, 623: Replacement remaining number, accuracy setting process, 624: Replacement number calculation processing, 625: Replacement remaining number calculation processing, 626: Same delivery date determination processing, 627: Shipment actual number replacement processing, 628: Replacement candidate number determination processing, 629: Replacement candidate setting processing, 630: Replacement candidate setting process, 701: Sales department code, 702: Final customer code, 703: Order received NO, 704: Order owner code, 705: Rev, 706: Order model name, 707: Scheduled delivery date, 708: Order quantity before change, 709: Latest order received Quantity, 710: Shipment actual quantity, 711: Latest Rev flag, 801: Sales department code, 802: Final customer code, 803: Order receipt NO, 804: Order owner code, 805: Rev, 806: Order model name, 807: Delivery Scheduled date, 808: Order quantity before change, 809: Latest order quantity, 810: Actual shipment quantity, 811: Latest Rev flag

Claims (4)

A shipment plan information database that stores the number of orders before correction, the latest number of orders, the actual number of shipments, and the estimated delivery date for each case,
Among the different cases, if the planned delivery date is the same for the case where the pre-correction order number and the latest order number are the same, the case where the latest order number is 0 is the corrected order case, and the other case is the new order case Identify and calculate the number of deliveries by subtracting the number of actual shipments from the latest number of orders received for the corrected order item in the shipping plan information database, subtract the number of deliveries from the number of actual shipments of the corrected order item, The calculation unit that adds the number of replacements to the actual number of shipments of the new order item and the replacement process, and the new order item is not identified as one even if the planned delivery date does not match And a display section for displaying as a candidate for replacement. Each of the shipping result information allocating device according to claim 1,
The computing unit is
If the number of orders received before correction of the corrected order received item does not match the latest number of received orders of the new order received item, or if the latest number of received orders of the corrected order received item is not 0, the actual number of shipments of the corrected order received item and new orders received The difference between the cases is specified as the number of comparisons for comparison, and the difference between the number of comparisons for distribution, the actual number of shipments of the new order received and the number of new orders received is compared. In this case, the number of comparisons for distribution is specified as the number of distributions, and if the number of comparisons for replacement is larger, the difference between the number of actual shipments of the new order received and the number of new orders received is calculated from the number of comparisons for replacement. When the delivery date is the same or a candidate for replacement, the subtracted number is specified as the number of replacements, and the number of replacement comparisons is subtracted from the number of replacement comparisons as the new number of replacement comparisons. Will be sequentially transferred when one is identified Shipment result information changing device characterized by that. It is the shipping result information allocating device according to claim 2,
Information for determining the priority of the accuracy of replacement for each case when the difference between the replacement comparison number, the number of actual shipments of the new order received item and the new order received item is small, equal, or large Are associated with each other and display replacement candidates based on the priority order. Storing the number of orders before correction, the latest number of orders, the number of actual shipments, and the estimated delivery date in association with each case,
Among the different cases, if the planned delivery date is the same for the case where the pre-correction order number and the latest order number are the same, the case where the latest order number is 0 is the corrected order case, and the other case is the new order case Identify and calculate the number of deliveries by subtracting the number of actual shipments from the latest number of orders received for the corrected order item in the shipping plan information database, subtract the number of deliveries from the number of actual shipments of the corrected order item, If the number of replacements is added to the actual number of shipments of the new order received and the delivery process is not coincident with the scheduled delivery date, the new order received A delivery result information allocating method comprising the steps of: displaying as a replacement candidate item.

Images