JP2014119821A - Retroaction unit price correction system and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a retroaction unit price correction system capable of appropriating the difference amount between a temporary unit price and a formal unit price without updating the temporary unit price into the formal unit price at the timing at which the formal unit price is determined for a transaction using the temporary unit price.SOLUTION: A retroaction unit price correction method comprises unit price information management processing for setting and managing information associated with unit prices of respective items and unit price information retrieval processing for retrieving information associated with a unit price based upon input contents (item, supplier) and then registering a new chit. A unit price and a term of validity input by a user are received and stored in a unit price information management table. Based upon registration contents of the unit price information management table, relative transaction slips area acquired and the difference amount between a temporary unit price and a formal unit price is calculated. An additional chip for the difference amount is registered.

Description

  The present invention records an additional bill with a difference from a purchase order slip subject to retroactive unit price correction for a transaction that is recorded at a provisional unit price and determines a formal unit price based on the contract in quarter, half year, year, etc. It is related with the countermeasure to register.

  By providing an expiration date for the unit price and associating the unit price with the transaction slip, it is possible to specify a transaction at the provisional unit price and adjust the difference.

  As a related technique, a known technique for performing recalculation on a transaction within the expiration date of a unit price after price determination is made is known (for example, see Patent Document 1).

  In addition, as a related technique, a well-known technique is known in which the unit price information is stored for each product in the retail industry such as a supermarket and the unit price information is settled by using the unit price information on the day at the POS settlement of the day. (For example, refer to Patent Document 2).

Japanese Laid-Open Patent Publication No. 1-109472 JP 2006-350405 A

  There is a transaction where the contracted unit price is recorded at the time of ordering / acceptance, and the official unit price is fixed again in quarterly, semi-annual and annual units. This is because, such as crude oil / naphtha-linked raw materials, the purchase unit price is fixed at various fixed rates every quarter, the purchase unit price is determined based on the total purchase quantity, and price negotiation is continued by continuing price negotiations. This is because there are cases where the order is not confirmed by the time of order placement / acceptance. In this case, it is necessary to make a retroactive unit price correction to record the difference from the official unit price for the provisional unit price transaction at the timing when the official unit price is fixed, but it is necessary to correct the retroactive unit price for which transaction and for which period. However, since it is difficult to specify the target, there is a possibility that the difference may be missed or misrecorded. In addition, the provisional unit price is corrected at the timing when the official unit price is fixed, and the unit price information is constantly updated with the latest unit price.

  In order to solve the above problem, Patent Document 1 attempts to solve the above problem by comparing the purchase amount with respect to the application period of the new unit price with respect to the provisional unit price and calculating the difference. Further, Patent Document 2 attempts to solve the above-mentioned problem by providing unit price information on a daily basis and paying the price for the product at the unit price on that day.

  However, the following points are not considered in the above patent document. In the above patent document, the unit price information is updated to calculate the difference from the pre-update, and the purchase price of the product is compared and output. Therefore, the previous transaction unit price cannot be confirmed.

  It is an object of the present invention to provide a retroactive unit price correction system for performing retroactive unit price correction by specifying target transactions and target periods without directly updating unit price information in retroactive unit price correction operations.

  Unit price information is registered for each valid period, and a transaction slip is registered by referring to the unit price for each valid period at the time of ordering / acceptance. When the provisional unit price at the time of ordering / acceptance is confirmed as the official unit price, enter the valid period and unit price of the official unit price, and update only the unit price information or retroactive unit price correction process, update the unit price information, Whether to perform both retroactive unit price correction processing is selected, and based on the input information (procurement person's processing selection instruction), the unit price information is updated and the retroactive unit price correction processing is performed. In the unit price information update, the unit price information table is overwritten based on the input contents (new unit price information of the item). The retroactive unit price correction process extracts a transaction slip that is subject to retroactive unit price correction based on the input contents (item, supplier). From the extracted transaction slip, the transaction quantity and the transaction amount are aggregated in the unit of the transaction slip, and the difference is calculated. Other expenses are calculated by summing up the transaction amount for each transaction slip. An additional bill is registered using the difference calculated above.

According to the present invention, retroactive unit price correction can be performed without updating the unit price, and the unit price before correction and the unit price after correction can be confirmed after the retroactive unit price correction. In addition, it is possible to speed up retroactive unit price correction work and improve the ease of checking related slips.

1 is a diagram illustrating an example of the overall configuration of a computer network system 100 according to the present embodiment. 2 is a diagram illustrating a hardware configuration example of an AP server 102. FIG. 2 is a diagram illustrating an example of a hardware configuration of a DB server 103. FIG. 2 is a diagram illustrating an exemplary hardware configuration of a client 104. FIG. It is a figure which shows the data structural example of the item master 310 which DB server 103 comprises. It is a figure which shows the data structural example of the supplier master 311 which DB server 103 comprises. It is a figure which shows the data structural example of the unit price information table 312 which the DB server 103 comprises. It is a figure which shows the data structural example of the order slip table 313 which DB server 103 comprises. It is a figure which shows the example of a data structure of the entering / exiting slip table 314 which DB server 103 comprises. It is a figure which shows the data structural example of the bill slip table 315 which DB server 103 comprises. It is a figure which shows the data structural example of the unit price information management table 316 which DB server 103 comprises. It is a figure which shows the unit price information search screen example 411 which the client 104 comprises. It is a figure which shows the unit price information update screen example 412 which the client 104 comprises. It is a figure which shows the unit price information management data search screen example 413 which the client 104 comprises. 10 is a flowchart showing processing of a unit price information search condition transmission function 411 provided in the client 104. It is a flowchart which shows the process of the unit price information search function 211 with which AP server 102 is provided. It is a flowchart which shows the process of the unit price information reception display function 412 which the client 104 comprises. 10 is a flowchart showing processing of a unit price information update data transmission function 413 provided in the client 104. It is a flowchart which shows the process of the unit price information update function 212 with which AP server 102 is provided. 10 is a flowchart showing processing of a unit price information management data search condition transmission function 414 provided in the client 104. It is a flowchart which shows the unit price information management data process of the additional bill slip registration function 213 which the AP server 102 has. It is a flowchart which shows the process for every order slip specification of the additional claim slip registration function 213 which AP server 102 comprises. It is a flowchart which shows the process for every order slip of the additional claim slip registration function 213 which AP server 102 comprises. It is a flowchart which shows the completion | finish determination processing of the additional claim slip registration function 213 which AP server 102 comprises. It is a figure which shows the processing content at the time of checking each of the check box retroactive correction and unit price information update of the unit price information search screen which the client 104 comprises. It is a figure which shows the data structural example of the various management table 317 which DB server 103 comprises.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

(System configuration)
FIG. 1 is a diagram showing an example of the overall configuration of a computer network system 100 according to the present embodiment. The retroactive unit price correction system 100 is configured by connecting an AP server 102, a DB server 103, and a plurality of clients 104 to a network 101. The AP server 102 and the DB server 103 are installed indoors such as a data center. The client 104 is a terminal such as a personal computer, for example, and inputs unit price information determined by a purchaser.

  FIG. 2 is a diagram illustrating a hardware configuration example of the AP server 102. The AP server 102 includes a controller (control unit) 202, a memory 203, a communication control unit 204, a program 210 in the storage unit 201, a unit price information search function 211, a unit price information update function 212, and an additional billing slip registration function. 213. Each unit is connected by a bus (BUS).

  The unit price information search function 211 has a function of receiving a search condition from the client 104, searching a unit price information table based on the information, and transmitting the acquired unit price information to the client 104. The unit price information update function 212 has a function of receiving fixed unit price information from the client 104 and updating the unit price information management table based on the information. Further, the additional billing slip registration function 213 has a function of searching the order slip table and billing slip table based on the registration contents of the unit price information management table, calculating the difference, and registering the additional billing slip.

  FIG. 3 is a diagram illustrating a hardware configuration example of the DB server 103. The DB server 103 includes a controller (control unit) 302, a memory 303, a communication control unit 304, a storage unit 301, an item master 310, a supplier master 311, a unit price information table 312, and an order slip table 313. , A loading / unloading slip table 314, a billing slip table 315, a unit price information management table 316, and a charge management table 317 are provided. Each unit is connected by a bus (BUS).

  The item master 310 stores item codes, item names, and item types in association with each other. The supplier master 311 stores a supplier code and a supplier name in association with each other. The unit price information table 312 stores a unit price number, a supplier, an item, an effective start date, an effective end date, and a unit price in association with each other. The order slip table 313 stores an order number, order details, a supplier, an item, an order quantity, and a unit price number in association with each other. The entry / exit slip table 314 stores an entry / exit number, entry / exit details, posting date, order number, receipt quantity, and receipt amount in association with each other. The billing slip table 315 stores billing slips, posting dates, order numbers, ordering details, billing quantities, billing amounts, debit / credit, and charge categories in association with each other. The unit price information management table 316 stores a status, a unit price number, a supplier, an item, an effective start date, an effective end date, and a unit price in association with each other. The hook management table 317 stores the hook classification, the hook name, the supplier, the quantity, the quantity unit, the hook amount, and the passage in association with each other.

  FIG. 4 is a diagram illustrating a hardware configuration example of the client 104. The client 104 includes a display unit 402, a controller (control unit) 403, a memory 404, a communication control unit 405, and a program 410 in the storage unit 401 as a unit price information search condition transmission function 411 and a unit price information reception display function 412. A unit price information update data transmission function 413 and a unit price information management data search condition transmission function 414.

  The unit price information search condition transmission function 411 has a function of displaying a unit price information search screen on the display unit 402 of the client 104 and a function of transmitting the input search condition. The unit price information reception display function 412 receives the unit price information acquired from the DB server 103 by the unit price information search function 211 based on the search condition input by the unit price information search condition transmission function 411, and displays the unit price information on the display unit 402 of the client 104. It has a function to display. The unit price information update data transmission function 413 has a function of transmitting the input unit price information update data. The unit price information management data search condition transmission function 414 has a function of displaying a unit price information management table data selection screen on the display unit 402 of the client 104.

(Various data)
FIG. 5 is a diagram illustrating a data configuration example of the item master 310 included in the DB server 103. The item master 310 is a table that stores item codes, item names, and item types for transactions, and is updated when the item names and item types are changed. As shown in FIG. 5, the item code 501, the item name 502, and the item type 503 are stored in association with each other. The item code 501 is a number that uniquely identifies an item. The item name 502 is the name of the item code 501. Item type 503 manages the nature of the item.

  FIG. 6 is a diagram illustrating a data configuration example of the supplier master 311 included in the DB server 103. The supplier master 311 is a table that stores supplier codes and supplier names for transactions, and is updated when the supplier name is changed. As shown in FIG. 6, a supplier code 601 and a supplier name 602 are stored in association with each other. The supplier code 601 is a number that uniquely identifies the supplier. The supplier name 602 is the name of the supplier code 601.

  FIG. 7 is a diagram illustrating a data configuration example of the unit price information table 312 included in the DB server 103. The unit price information table 312 stores a transaction contract unit price with the supplier, and is updated when the unit price is changed during the unit price contract. As shown in FIG. 7, the unit price number 701, the supplier 702, the item 703, the valid start date 704, the valid end date 705, and the unit price 706 are stored in association with each other. The unit price number 701 is a number that uniquely identifies unit price information. The supplier 702 represents a supplier who has made a procurement contract for the item. An item 703 represents an item for which a procurement contract has been made. The effective start date 704 and the effective end date 705 represent the unit price effective period. A unit price 706 represents a unit price within the effective period.

  FIG. 8 is a diagram showing a data configuration diagram of the order slip table 313 provided in the DB server 103. The order slip table 313 is a table for storing order slips, and is updated when an order slip for a supplier is registered. As shown in FIG. 8, an order number 801, order details 802, supplier 803, item 804, order quantity 805, and unit price number 806 are stored in association with each other. The order slip 801 is a number for uniquely identifying the order slip. The order details 802 is a number that uniquely identifies the details of the order slip. The supplier 803 represents the procurement source of the item. Item 804 represents an item to be procured. The order quantity 805 represents the quantity of items procured from the supplier. A unit price number 806 represents a unit price number referred to by the ordering slip.

  FIG. 9 is a diagram illustrating a data configuration diagram of the entry / exit slip table 314 included in the DB server 103. The entry / exit slip table 314 is a table for storing the entry / exit slip, and is updated when the goods received from the supplier are accepted and the entrance / exit slip is registered. As shown in FIG. 9, the store / receive number 901, store / departure details 902, posting date 903, order number 904, store quantity 905, and store amount 906 are stored in association with each other. The entry / exit number 901 is a number that uniquely identifies the entry / exit slip. The entry / exit details 902 is a number that uniquely identifies the details of the entry / exit slip. A posting date 903 represents a date for accounting posting. The order slip 904 represents an order number referred to by the entry / exit number. The receipt quantity 905 represents the inspection quantity for the receipt from the business partner. The warehousing amount 906 represents the amount with respect to the warehousing quantity.

  FIG. 10 is a diagram illustrating a data configuration diagram of the billing slip table 315 included in the DB server 103. The billing slip table 315 is a table for storing billing slips, and is updated when the bill slip is registered based on the bill from the supplier. As shown in FIG. 10, an invoice number 1001, a posting date 1002, an order number 1003, an order detail 1004, an invoice quantity 1005, an invoice amount 1006, a debit / credit 1007, and a charge category 1008 are stored in association with each other. A billing number 1001 is a number for uniquely identifying a billing slip. A posting date 1002 represents a date for accounting posting. An order number 1003 represents an order number referred to by a billing number. An order detail 1004 represents an order detail referred to by a billing number. A billing quantity 1005 represents a billing quantity for billing from a business partner. A billing amount 1006 represents a billing amount. A debit / credit 1007 represents a loan to the billed amount. The hook category 1008 manages the contents of the hook.

  FIG. 11 is a diagram showing a data configuration diagram of the unit price information management table 316 provided in the DB server 103. The unit price information management table 316 is updated by executing the unit price information update function 211 included in the AP server 102 when the unit price information is input from the unit price information update screen display function 412 included in the client 104. As shown in FIG. 12, status 1101, unit number 1102, supplier 1103, item 1104, valid start date 1105, valid end date 1106, and unit price 1107 are stored in association with each other. The status 1101 represents the processing status of the target record, and is updated when the processing of the target record is executed. The unit price number 1102 represents a unit price number subject to retroactive unit price correction. The supplier 1103, the item 1104, the effective start date 1105, the effective end date 1106, and the unit price 1107 represent detailed information on the unit number of the retroactive unit price correction target.

  FIG. 26 is a diagram illustrating a data configuration diagram of the miscellaneous management table 317 included in the DB server 103. It is a table for storing a charge amount 2601, a charge amount 2606 per quantity for the supplier 2603, and a currency 2607, and is updated when the charge category and the charge for the supplier are changed. As shown in FIG. 26, a charge category 2601, a charge name 2602, a supplier 2603, a quantity 2604, a quantity unit 2605, a charge amount 2606, and a currency 2607 are stored in association with each other.

(Display screen example)
A unit price information search screen 1200 shown in FIG. 12 shows an example of a screen that is displayed on the display unit 402 of the client 104 and for which the user inputs search conditions for unit price information that the user wants to update. In the unit price information search screen 1200 shown in FIG. 12, a supplier is entered in the input unit 1204, an item is entered in 1205, a unit price number is entered in 1206, an effective start date is entered in 1207, an effective end date is entered in 1208, and an execution button 1201 is pressed. Thus, the unit price information search function 211 shown in FIG. 15 is started, and the screen changes to the unit price information update screen 1300 shown in FIG. When performing retroactive correction processing on the input unit 1202, a check is set, and when updating unit price information, a check is set on 1203. The contents of processing when checking each are as shown in FIG.

  A unit price information update screen 1300 shown in FIG. 13 shows an example of a screen that is displayed on the display unit 402 of the client 104 and that allows the user to input unit price information after contract determination. In the unit price information update screen 1300 shown in FIG. 13, the unit price information update function shown in FIG. 16 is entered by inputting the valid start date in the input unit 1312, the valid end date in 1313, and the unit price in 1314 and pressing the registration button 1301. 212 is started. When the check is set for the retroactive correction 1304, the unit price information management table 316 is updated, and when the check is set for the unit price information update 1305, the unit price information table 316 is updated. By depressing the previous detail button 1302, the data before the displayed data is displayed among the unit price information extracted by the unit price information search function 211. By depressing the next detail button 1303, the data next to the displayed data among the unit price information extracted by the unit price information search function 211 is displayed.

  A unit price information management data search screen 1400 shown in FIG. 14 shows an example of a screen for inputting a unit price information management data search status, unit number, supplier, and item displayed on the display unit 402 of the client 104. . In the unit price information management data search screen 1400 shown in FIG. 14, by inputting the status, 1403 unit number, 1404 supplier, and 1405 items in the input unit 1402 and pressing the execute button 1401, the addition shown in FIG. The bill slip registration function 213 is started.

(Description of processing flow)
(Outline of processing)
The retroactive unit price correction method according to the present invention includes a unit price information management process for setting and managing information related to the unit price of each item, and searches for information related to the unit price based on input contents (items, suppliers) to create a new billing slip. And unit price information search processing to be registered. The numbers in parentheses are the numbers of the related drawings and the codes of the functions that execute the processing.

1. Unit price information management processing:
(1) The client transmits information related to the item input on the screen to the AP server. (Fig. 15, 411)
(2) The AP server searches for unit price information based on information from the client and transmits it to the client. (Fig. 16, 211)
(3) The client displays the information from the AP server on the screen. (Fig. 17, 412)
(4) The client sends the expiration date and unit price entered on the screen to the AP server. (Fig. 18, 413)
(5) The AP server updates unit price information for items that need retroactive correction. (Fig. 19, 212)
2. Unit price information search processing:
(1) The client transmits information related to the item input on the screen to the AP server. (Fig. 20, 413)
(2) The AP server searches the unit price information based on information from the client, and repeats the following processes (3) to (5) for the related order slip for each unit price information. (Figs. 21 and 213)
(3) The AP server calculates the difference based on the new unit price for all records of the order slip. (Fig. 22, 213)
(4) The AP server calculates the difference based on the invoiced quantity for all the records in the order slip. (Fig. 23, 213)
(5) The AP server updates the status of the unit price information. (Fig. 24, 213)

(1. Unit price information management process)
FIG. 15 is a flowchart showing the processing of the unit price information search condition transmission function 411 provided in the client 104. The unit price information search condition transmission function 411 includes a supplier 1204, an item 1205, a unit price number 1206, an effective start date input from the unit price information search screen 1200 (FIG. 12) displayed on the display unit 402 of the client 104. 1207, the effective end date 1208 is acquired and transmitted to the AP server 102 (step S1501).

  FIG. 16 is a flowchart showing processing of the unit price information search function 211 provided in the AP server 102. The unit price information search function 211 receives the unit price number, supplier, item, valid start date, and valid end date values transmitted from the client 104 (step S1601). Next, with the received unit price number, supplier, item, effective start date, and effective end date as keys, the unit price number 701 of the unit price information table 312, the supplier 702, the item 703, and the effective start date 704 The effective end date 705 is searched, and the unit price number of the corresponding record is extracted (step S1602). Next, the item code 501 of the item master 310 is searched using the item associated with the extracted unit number 701 as a key, the item name is extracted, and the supplier master 311 is purchased using the supplier as a key. The destination code 601 is searched, and the supplier name is extracted (step S1603). Next, unit price information with various names added is transmitted to the client (step S1604).

  FIG. 17 is a flowchart showing the processing of the unit price information reception display function 412 provided in the client 104. The unit price information reception display function 412 includes a retroactive correction flag 1304, unit price information update flag 1305, supplier 1306, item 1307, unit number 1308, valid start date 1309, valid end date 1310, and unit price transmitted from the AP server 102. 1311 is received (step S1701) and displayed on the display unit 402 (unit price information update screen 1300). In this case, the received unit price information is displayed in ascending order of the supplier code and in ascending order of the effective start date (step S1702).

FIG. 18 is a flowchart showing the processing of the unit price information update data transmission function 413 provided in the client 104. The unit price information update data transmission function 413 is input from the unit price information update screen 1300 (FIG. 13) displayed on the display unit 402 of the client 104.
The retroactive correction flag 1304, the unit price information update flag 1305, the unit price number 1308, the valid start date 1312, the valid end date 1313, and the unit price 1314 are acquired and transmitted to the AP server 102 (step S1801).

  FIG. 19 is a flowchart showing the processing of the unit price information update function 212 provided in the AP server 102. The unit price information update function 212 receives the retroactive correction flag, unit price information update flag, supplier, item, unit price number, valid start date, valid end date, and unit price values transmitted from the client 104 (step S1901). To do. Next, when the retroactive correction flag is ON, the unit price information management table 316 is updated with the received unit price number, supplier, item, valid start date, valid end date, and unit price (step S1902). Next, when the unit price information update flag is ON, the unit price information table is updated with the received unit price number, valid start date, valid end date, and unit price (step S1903).

(2. Unit price information search processing)
FIG. 20 is a flowchart showing the processing of the unit price information management data search condition transmission function 414 provided in the client 104. The unit price information management data search condition transmission function 414 has a status 1402, a unit number 1403, and a supplier 1404 input from the unit price information management data search screen 1400 (FIG. 14) displayed on the display unit 402 of the client 104. The item 1405 is acquired and transmitted to the AP server 102 (step S2001).

  FIG. 21 is a flowchart showing processing for each unit price information management data of the additional billing slip registration function 213 provided in the AP server 102. The additional billing slip registration function 213 receives the status, unit number, supplier, and item values transmitted from the client 104 (step S2101). Next, using the received status, unit price number, supplier, and item as keys, the status 1101 of the unit price information management table 316, the unit price number 1102, the supplier 1103, the item 1104, the effective start date 1104, The effective end date 1105 is searched, and the corresponding record is extracted (step S2102). Next, for each piece of data in the extracted unit price information management table, the supplier 803, the item 804, and the unit number 806 of the order slip table 313 are searched using the supplier, item, and unit number as keys. Are extracted (step S2103).

  FIG. 22 is a flowchart showing processing for each order slip details of the additional bill slip registration function 213 provided in the AP server 102. The billing slip table 315 with the order date and order details for each order slip details in the order slip table 313 extracted in step S2103 as keys, and the valid start date and valid end date of the unit price information management table data 316 extracted in step S2102. The retrieval date 1002, the order number 1003, the order details 1004, and the multi-item category 1008 (no setting) are searched, and the corresponding record is extracted (step S2201). Next, for the billing slip extracted in step S2201, a new billing amount is calculated from the unit price 706 extracted in step S2102 and the billing quantity 1004 extracted in step S2201 (step S2202). Next, a difference is calculated from the new charged amount calculated in step S2202 and the charged amount 1005 extracted in step S2201 (step S2203).

  Next, if the difference calculated in step S2203 is other than 0, an additional billing slip for the calculated difference is registered in the billing slip table 315 (step S2204). Steps S2201 to S2204 are repeated until the final record of the order slip details. In the case of the last record of the order slip details, the processing of FIG. 23 is performed.

  FIG. 23 is a flowchart showing processing for each order slip of the additional bill slip registration function 213 included in the AP server 102. The posting date 1002 of the billing slip table 315 using the valid start date and valid end date of the unit price information management table data 316 extracted in step S2102 and the order number for each order slip in the order slip table 313 extracted in step S2103 as a key. Then, the order number 1003 and the charge category 1008 (with setting) are searched, and the corresponding record is extracted (step S2301). Next, for the billing slip extracted in step S2301, a billing quantity and a billing amount with the same charge category are calculated from the billing slips as targets (step S2302). Next, using the vendor of the ordering slip, the charge category of the billing slip, and the billed quantity calculated in step S2302, the charge category 2601 of the charge management table 317, the supplier 2603, and the quantity 2604 are searched. The corresponding record is extracted (step S2303). Next, a difference is calculated from the amount charged in step S2302 and the amount charged in various amounts extracted in step S2303 (step S2304).

  Next, if the difference calculated in step S2304 is other than 0, an additional bill for the calculated difference is registered in the table 315 (step S2305). Steps S2301 to S2305 are repeated until the final record of the order slip is reached. If the record is the last record of the ordering slip, the process of FIG. 24 is performed.

  FIG. 24 is a flowchart showing an end determination process of the additional billing slip registration function 213 provided in the AP server 102. The status of the target record (step S2103) in the unit price information management table 316 is updated (step S2401). Steps S2103 to S2401 are repeated until the last record of the unit price information management table 316 is reached. In the case of the last record of the unit price information management table 316, the process ends.

(Specific example of input data)
FIG. 25 is a diagram showing processing branches corresponding to checks on the unit price information search screen 1200, the input unit retroactive correction 1202, and the unit price information update 1203. That is, FIG. 25 shows the correspondence between the presence / absence of the check of the two check items 1202 and 1203 shown in FIG. 12 and the update of the unit price information management table 316 and the unit price information table 312 as a summary of the description of each processing described above. Is shown. When there is a check only for retroactive correction, only the unit price information management table is updated. When there is a check for retroactive correction and unit price information update, the unit price information management table and unit price information are updated, and only the unit price information update is checked. Only the unit price information is updated, and if neither retroactive correction nor unit price information update is checked, no processing is performed.

  The embodiment of the present invention has been described above. According to the above-described embodiment, a certain effect can be obtained regardless of the software to be used, and prompt failure handling of the field worker can be realized. Furthermore, the present invention is not limited to this, and various modifications can be made without departing from the scope of the invention.

101: Network, 102: AP server, 103: DB server, 104: Client, 201, 301, 401: Storage unit, 202, 302, 403: Controller (control unit), 203, 303, 404: Memory, 402: Display Unit, 204, 304, 405: communication control unit

Claims (5)

A retroactive unit price correction system in which a client terminal and an AP server are connected via a network,
The client terminal has unit information management means for setting and managing information related to the unit price of each item,
The AP server includes unit price information search means for searching for information about a unit price based on input contents including an item and a supplier and registering a new billing slip.
A retroactive unit price correction system characterized by this. The unit price information management means includes:
The client terminal is a unit price information search condition transmitting means for transmitting information related to the item input on the screen to the AP server,
Unit price information reception display means for receiving the unit price information searched by the AP server based on information from the client terminal and displaying it on a screen;
Unit price information update data transmission means for transmitting the expiration date and unit price entered on the screen to the AP server,
The AP server has unit price information updating means for updating unit price information for items that need retroactive correction,
The unit price information search means includes:
The unit price information is retrieved based on the information regarding the item input on the screen received from the client terminal, and the following processes (a) to (c) are repeated for the related order slip for each unit price information.
(A) The AP server calculates a difference based on the new unit price for all records of the order slip,
(B) The AP server calculates the difference based on the invoiced quantity for all records of the order slip,
(C) The AP server updates the status of the unit price information.
2. The retroactive unit price correction system according to claim 1, further comprising additional bill slip registration means. A retroactive unit price correction method in a network system in which a client terminal and an AP server are connected via a network,
The client terminal executes unit price information management processing for setting and managing information related to the unit price of each item,
The AP server performs a unit price information search process for searching for information about a unit price based on input contents including an item and a supplier and registering a new billing slip. The unit price information management process includes:
The client terminal transmits information on the item input on the screen to the AP server,
The AP server searches for unit price information based on information from the client terminal and transmits it to the client terminal,
The client terminal displays information from the AP server on a screen,
The client terminal sends the expiration date and unit price entered on the screen to the AP server,
The AP server updates unit price information for items that need retroactive correction.
The retroactive unit price correction method according to claim 3. The unit price information search process includes:
The client terminal transmits information on the item input on the screen to the AP server,
The AP server searches for unit price information based on information from the client terminal, and repeats the following processes (a) to (c) for related order slips for each unit price information.
(A) The AP server calculates a difference based on the new unit price for all records of the order slip,
(B) The AP server calculates the difference based on the invoiced quantity for all records of the order slip,
(C) The AP server updates the status of the unit price information.
The retroactive unit price correction method according to claim 3.

Images