JP2014032513A - Unit price setting device, unit price setting method, and unit price setting program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To set an appropriate unit price for a commercial article.SOLUTION: A selling management device 10 accepts an application period and unit price specification to be newly inserted into a range of the application period of a unit price master to which the unit price of a commercial article is made to correspond for every application period in which the unit price of the commercial article is applied. With respect to the application period in which the application period that has accepted specification in the application period defined in the unit price master, the selling management device carries out update for segmentation of the inserted application period, having the border between the start date and the end date of the application period that has accepted the specification, and also carries out update such that the application period that has accepted the specification is made to corresponds to a unit price that has accepted specification. The device accepts resetting instruction to reset a unit price of a commercial article on a voucher, for vouchers used for the transactions of corresponding commercial articles during the application period in which a base date subjected to the application of a unit price is accepted. When a resetting instruction is accepted, the unit price of a commercial article corresponding to the application period including the base date among the unit prices of the commercial products defined in the unit price master is set on a voucher.

Description

  The present invention relates to a unit price setting device, a unit price setting method, and a unit price setting program.

  Systematization of sales management, which is the core of wholesale business, is progressing. The sales management of such a wholesale business is diverse, such as orders, shipments, sales, orders, receipts, and purchases. Especially, the unit price setting of products is regarded as important.

  In general, for setting the unit price of a product, master data in which the unit price of the product is associated with the effective period of the unit price is used. For example, when creating a voucher, the shipping date when the product is shipped or the date when the product is accepted is set as the accounting base date, and the effective date corresponding to the base date of the unit price of the product included in the master data The unit price of the product is used for calculating the order amount and the sales amount.

Japanese Patent Laid-Open No. 10-149247 JP 2003-228651 A

  However, as described below, the conventional technology has a problem that an inappropriate unit price may be set for a product.

  In other words, the unit price of the product can be set in the master data only during the period after the last set effective period. For this reason, the unit price of the product in the period in which the validity period is already set in the master data is fixed and cannot be changed. Therefore, even if the product unit price is set in the above master data, it cannot be changed even if the product unit price becomes inappropriate after that. It may be set.

  The disclosed technology has been made in view of the above, and an object thereof is to provide a unit price setting device, a unit price setting method, and a unit price setting program capable of setting an appropriate unit price for a product.

  The unit price setting device disclosed in the present application accepts designation of an application period and a unit price to be newly inserted within the range of the application period of the unit price master associated with the unit price of the product for each application period in which the unit price of the product is applied. For the application period in which the application period in which the designation is accepted is inserted among the application period defined in the unit price master and the designation reception unit, the insertion is performed with the start date and the end date of the application period in which the designation is accepted as a boundary. A master update unit that executes an update that divides the applied period and performs an update that associates the unit price that received the designation with the application period that received the designation, and a reference date that receives the unit price accepts the designation A reset instruction accepting unit that accepts a reset instruction for resetting the unit price of the product in the slip for a slip that deals with a product corresponding to the applied period, When accepting the re-setting instruction, and a bidding unit the unit price associated with the application period included the reference date is the unit price of the bid item master defined to set the slip.

  According to one aspect of the unit price setting device disclosed in the present application, it is possible to set an appropriate unit price for a product.

FIG. 1 is a block diagram illustrating a functional configuration of the sales management apparatus according to the first embodiment. FIG. 2 is a diagram illustrating a configuration example of a product master. FIG. 3 is a diagram illustrating a configuration example of a customer master. FIG. 4 is a diagram illustrating a configuration example of the supplier master. FIG. 5 is a diagram illustrating a configuration example of the system master. FIG. 6 is a diagram illustrating a configuration example of a unit price master for each business unit price group and each product. FIG. 7 is a diagram illustrating a configuration example of a unit price master for each supplier and each product. FIG. 8 is a diagram illustrating a configuration example of a unit price master for each business partner, each delivery destination, and each product. FIG. 9 is a diagram illustrating a configuration example of a unit price master by supplier unit price group, product, and quantity. FIG. 10 is a diagram illustrating a configuration example of the unit price master for each supplier, each product, and each quantity. FIG. 11 is a diagram illustrating a configuration example of a historical unit price master for each business partner, each delivery destination, and each product. FIG. 12 is a diagram illustrating an example of a unit price master update method. FIG. 13 is a diagram illustrating an example of a slip screen. FIG. 14 is a flowchart illustrating the procedure of the sales management process according to the first embodiment. FIG. 15 is a flowchart illustrating the procedure of the unit price setting process according to the first embodiment. FIG. 16 is a flowchart illustrating the procedure of the unit price setting process according to the first embodiment. FIG. 17 is a schematic diagram illustrating an example of a computer that executes a unit price setting program according to the first and second embodiments.

  Embodiments of a unit price setting device, a unit price setting method, and a unit price setting program disclosed in the present application will be described below in detail with reference to the drawings. Note that this embodiment does not limit the disclosed technology. Each embodiment can be appropriately combined within a range in which processing contents are not contradictory.

[Configuration of sales management device]
FIG. 1 is a block diagram illustrating a functional configuration of the sales management apparatus according to the first embodiment. The sales management apparatus 10 shown in FIG. 1 performs sales management such as ordering, shipping, sales, ordering, receipt and purchase of goods. In particular, the sales management apparatus 10 executes the update for inserting the application period in which the unit price is newly specified in the application period already defined in the unit price master 16, and then the reference date for receiving the application of the unit price is updated. Provide a unit price setting service that resets the unit price of a product in a voucher in which a product corresponding to an application period is a transaction target.

  As one aspect of the sales management apparatus 10, it may be implemented as a Web server that provides the unit price setting service, or may be implemented as a cloud that provides the unit price setting service by outsourcing. As another aspect, it can also be implemented by preinstalling or installing a unit price setting program provided as package software or online software on a desired computer. In this embodiment, it is assumed that the unit price setting program described above is operated on a server device of a wholesaler that sells products purchased from food stores, fruit and vegetable stores, etc. to retail stores such as supermarkets. I do.

  The sales management apparatus 10 shown in FIG. 1 is connected to a client terminal 30 through a desired network so that they can communicate with each other. Any type of communication network such as the Internet (Internet), LAN (Local Area Network), or VPN (Virtual Private Network) can be adopted as such a network, regardless of whether it is wired or wireless.

  The client terminal 30 is a computer that receives the unit price setting service. For example, the client terminal 30 is used by a person involved in a wholesale business. As an aspect of the client terminal 30, a mobile terminal such as a mobile phone, a PHS (Personal Handyphone System), and a PDA (Personal Digital Assistants) can be employed in addition to a fixed terminal such as a personal computer.

  As shown in FIG. 1, the sales management device 10 includes a communication I / F (interface) unit 11, a storage unit 13, and a control unit 17. Note that the sales management apparatus 10 may include various functional units included in a known computer, for example, various input / output devices, in addition to the functional units illustrated in FIG.

  The communication I / F unit 11 is an interface that performs communication control with another device, for example, the client terminal 30. As an aspect of the communication I / F unit 11, a network interface card such as a LAN card can be employed. For example, the communication I / F unit 11 receives a request for browsing various slips and a request for updating the unit price master from the client terminal 30, and notifies the client terminal 30 of the result of the slip screen and the unit price setting for the product.

  The storage unit 13 is a storage device that stores various programs such as an OS (Operating System) executed by the control unit 17 and a unit price setting program. As one aspect of the storage unit 13, a storage device such as a semiconductor memory element such as a flash memory, a hard disk, or an optical disk can be cited. The storage unit 13 is not limited to the above-mentioned types of storage devices, and may be a RAM (Random Access Memory) or a ROM (Read Only Memory).

  The storage unit 13 stores update history information 13a, slip information 13b, master data 14, and the like as an example of data used in a program executed by the control unit 17. In addition to the update history information 13a, the slip information 13b, and the master data 14, electronic data related to sales management, for example, data related to inventory, loading / unloading, inventory, and the like can be stored together.

  Among these, the update history information 13 a is history data regarding the update of the unit price master 16. As an example, in the update history information 13a, when the unit price master 16 is updated by the master update unit 17b, a history related to the update is registered by the master update unit 17b. As another example, the update history information 13a is reset to be described later in order to determine whether the unit price of the product set in the slip is set using the unit price before the update of the unit price master 16 or not. Referenced by the instruction receiving unit 17d.

  As one aspect of the update history information 13a, data associated with items such as history ID (identification), master type code, supplier code, supplier unit price group, delivery destination code, product code, application period, unit price, etc. Can be adopted. “History ID” here refers to an identifier for identifying an update history. The “master type code” refers to a code for identifying the type of the unit price master, and here, means a unit price master that has been updated among a plurality of unit price masters. Further, the “business partner code” refers to a code for identifying a business partner such as a seller or a supplier. The “product unit price group” refers to a group of items in which products of items having a certain commonality are grouped into a series, and is also referred to as a series item. The “delivery destination code” refers to a code for identifying a delivery destination to be delivered to a business partner. “Product code” refers to a code for identifying a product. “Quantity” refers to the quantity of products to be traded, and means, for example, the quantity of products to be sold or the quantity of products to be purchased. The “application period” refers to a period during which the unit price defined in the unit price master 16 is applied. Here, it means an application period in which insertion into the unit price master 16 is designated. For example, the application period can be defined by a start date for starting application of the unit price and an end date for ending application of the unit price. In addition to the above items, other items such as the date and time when the unit price master 16 is updated may be provided. In addition, not all items described above are essential. For example, when one unit price master is used for setting the unit price of a product in a slip, the master type code is not necessarily required. Further, items that do not exist in the unit price master 16 corresponding to the master type code among items such as a supplier code, a supplier unit price group, a delivery destination code, and a product code are not necessarily registered.

  The slip information 13b is data relating to various slips. Examples of such slips include slips related to sales operations such as quotation, order receipt, shipment, and sales, as well as slips related to purchase operations such as ordering, receipt and purchase.

  As an aspect of the slip information 13b, data in which items such as a slip number, a supplier code, a delivery destination code, a product code, a quantity, a reference date, and a master type code are associated can be employed. The “slip number” here refers to a number for identifying a slip, and is used in common among a series of processes included in sales operations, that is, quotation, order receipt, shipment, sales, and the like. In addition, “reference date” refers to a date that is the basis of accounting. For example, an order date when an order is received for a product, a shipment date when the product is shipped, a delivery date when the product is delivered, and an acceptance date when the delivered product is accepted, Business days such as the sales date on which the sales of the product are finalized. Here, the reference date is used to specify which of the unit prices of the product defined in the unit price master 16 is to be applied with the unit price associated with which application period. The above “reference date” is any of the above-mentioned order date, shipping date, delivery date, inspection date, sales date, etc., depending on the slip, product, business partner, delivery destination, quantity, etc. The date can be changed at any time, or the type of business day can be changed.

  The master data 14 is various kinds of master data used in sales management of wholesale trade. For example, as shown in FIG. 1, the master data 14 includes a unit price master 16 in addition to a product master 15a, a customer master 15b, a supplier master 15c, and a system master 15d. In the following, the case where the sales unit price is set in the voucher will be exemplified. However, the value when other supplier is the customer defined in the unit price master 16 to be exemplified later is the value of other items. The same applies to the case where the purchase unit price is set in the slip by changing the value.

  Among these items, the product master 15a is master data in which products are defined. As an aspect of the product master 15a, data in which product codes, product unit price groups, and unit price settings are associated can be employed. FIG. 2 is a diagram illustrating a configuration example of the product master 15a. In the example of FIG. 2, the products with the product code “101010” and the product code “101015” are both classified as sweets, and the unit price is adopted as it is without multiplying the unit price defined in the unit price master 16 by the multiplication rate. Means that. Further, the product with the product code “101020” shown in FIG. 2 is classified as cold food, which means that the unit price is adopted as it is without multiplying the unit price defined in the unit price master 16 by the multiplication rate. Further, the product with the product code “101030” shown in FIG. 2 is classified as other and means that the unit price defined in the unit price master 16 is not used as it is, but is applied after multiplying the multiplication rate.

  The customer master 15b is master data in which a customer who purchases a product to be sold from a wholesaler, that is, a so-called customer is defined. As one aspect of the customer master 15b, data in which a supplier code, a supplier unit price group, and unit price determination information are associated can be employed. The “customer unit price group” here refers to a group of business partners having a certain commonality, and here means a group of customers. “Unit price determination information” refers to various types of information used when determining the unit price of a product. The “unit price determination information” includes a “unit price determination category” in which a unit price determination method is classified. For example, the unit price determination category is roughly divided into a category “1” in which the unit price is acquired by manual input by a wholesaler, and a category “9” in which the unit price is acquired by performing a search on the unit price master 16. Is done. Further, the “unit price determination information” includes “unit price multiplication rate” in the case of applying the rate to the unit price of the customer. Furthermore, “Unit Price Determination Information” includes “Unit Price by Business Partner” in which the unit price is distinguished by business partner, “Unit Price by Product by Product Unit” in which the unit price is classified by product and quantity, and when the product was delivered last time. “Unit price search order” in which the order of starting the search from the unit price master 16 corresponding to which unit price type is included in the “previous delivery unit price”, which is the unit price of.

  FIG. 3 is a diagram illustrating a configuration example of the customer master 15b. In the example of FIG. 3, it is shown that the customers of the supplier code “10101” and the supplier code “10201” are all classified into the supplier unit price group “Super OO”. Further, in the example of FIG. 3, the customers with the supplier code “20101” and the supplier code “30101” both indicate that the supplier unit price group is not set. Further, the example of FIG. 3 shows that the unit price determination category “9” is applied to the customers of the supplier code “10101”, the supplier code “10201”, and the supplier code “30101”. In this case, the unit price is acquired by executing a search for the unit price master 16. On the other hand, in the example of FIG. 3, the unit price determination category “1” is applied to the customer with the supplier code “20101”. In this case, the unit price is set manually by the parties using the client terminal 30 without executing the search for the unit price master 16. The description of the unit price search order shown in FIG. 3 is given in the system master 15d shown in FIG.

  The supplier master 15c is master data in which a supplier who sells products to wholesalers, that is, a so-called supplier is defined. As one aspect of the supplier master 15c, data in which a supplier code, a supplier unit price group, and unit price determination information are associated can be employed. FIG. 4 is a diagram illustrating a configuration example of the supplier master 15c. In the example of FIG. 4, the suppliers with the supplier code “50101” and the supplier code “60201” are both classified into the supplier unit price group “XX food”. Further, in the example of FIG. 4, it is shown that the suppliers with the supplier code “70101” and the supplier code “80101” are all classified into the supplier unit price group “◯ Δ fruits and vegetables”. Further, the example of FIG. 4 shows that the unit price determination category “9” is applied to the suppliers of the supplier code “50101”, the supplier code “60201”, and the supplier code “70101”. In this case, the unit price is acquired by executing a search for the unit price master 16. On the other hand, the example of FIG. 4 shows that the unit price determination category “1” is applied to the customer with the supplier code “80101”. In this case, the unit price is set manually by the parties using the client terminal 30 without executing the search for the unit price master 16. The description of the unit price search order shown in FIG. 4 is also given in the system master 15d shown in FIG.

  The system master 15d is master data in which a unit price type acquired by searching the unit price master 16 executed by the unit price setting system is defined. As an aspect of the system master 15d, data in which the unit price type and the unit price priority are associated can be employed. “Unit price type” here refers to the type of item used as a criterion for distinguishing unit prices, for example, “unit price by business partner” in which unit prices are distinguished by business partners, and unit prices by product and quantity. “Unit price by quantity by product”, and “Unit price by previous delivery” in which the unit price is distinguished according to the history of the previous product delivery. The “unit price priority” refers to the order in which the unit price search order is prioritized.

  FIG. 5 is a diagram illustrating a configuration example of the system master 15d. As shown in FIG. 5, the unit price priority order is set in the order of “unit price by supplier”, “unit price by product quantity”, and “previous delivery unit price”. When the unit price search order is “50”, the search is started from the unit price master 16 corresponding to the “unit price by business partner”, and when the unit price acquisition fails, the “unit price by product quantity” This means that if the search for the unit price master 16 corresponding to is executed and the acquisition of the unit price still fails, the search for the unit price master 16 corresponding to the “previous delivery unit price” is executed. If the unit price search order is “60”, the search is not performed for the unit price master 16 corresponding to “unit price by business partner”, and the search is performed from the unit price master 16 corresponding to “unit price by quantity by product”. This means that if the acquisition of the unit price fails, the search to the unit price master 16 corresponding to the “previous delivery unit price” is executed. Further, when the unit price search order is “70”, the search is not executed in the unit price master 16 corresponding to “unit price by business partner” and “unit price by product quantity”, and corresponds to “previous delivery unit price”. Only the search to the unit price master 16 to be executed is executed.

  The unit price master 16 is master data in which unit prices are defined. For example, the unit price master 16 includes the unit price masters 16a to 16c of the first group as the unit price master 16 corresponding to the unit price type “unit price by business partner” in which the unit price is distinguished by business partner.

  Among these, the unit price master 16a is master data in which a unit price is defined for each business unit price group and each product. As an aspect of the unit price master 16a, data in which a supplier unit price group, a product code, an application period, a contract unit price, and a contract rate are associated can be employed. FIG. 6 is a diagram illustrating a configuration example of the unit price master 16a for each business unit price group and each product. In the example of FIG. 6, the supplier unit price group set in the slip is “Super XX”, the product code is “101010”, and the base date is the application period “2012/3/1 to 2012/3 / In the case of “31”, 1100 yen is searched as the unit price. On the other hand, the supplier unit price group set in the slip is “Super XX”, the product code is “101010”, and the base date is within the applicable period “2012/4/1 to 9999/99/99” In some cases, 900 yen is searched as the unit price.

  The unit price master 16b is master data in which a unit price is defined for each supplier and each product. As an aspect of the unit price master 16b, data in which a supplier code, a product code, an application period, a contract unit price, and a contract rate are associated can be employed. FIG. 7 is a diagram illustrating a configuration example of the unit price master 16b for each supplier and each product. In the example of FIG. 7, the supplier code set in the slip is “10101”, the product code is “101010”, and the base date is within the applicable period “2012/3/1 to 2012/3/31” In this case, 1100 yen is searched as a unit price. On the other hand, when the supplier code set in the slip is “10101”, the product code is “101010”, and the base date is within the applicable period “2012/4/1 to 9999/99/99” Is searched for 1000 yen as a unit price.

  The unit price master 16c is master data in which unit prices are defined for each supplier, each delivery destination, and each product. As one aspect of the unit price master 16c, data in which a supplier code, a delivery destination code, a product code, an application period, a contract unit price, and a contract rate are associated can be employed. FIG. 8 is a diagram illustrating a configuration example of the unit price master 16c for each business partner, each delivery destination, and each product. In the example of FIG. 8, the supplier code set in the slip is “10101”, the delivery destination code is “Store A”, the product code is “101010”, and the reference date is the application period “2012 / In the case of “3/1 to 2012/3/31”, 1100 yen is searched as the unit price. On the other hand, the supplier code set in the slip is “10101”, the delivery destination code is “Store A”, the product code is “101010”, and the base date is the applicable period “Apr. In the case of “9999/99/99”, 900 yen is searched as the unit price.

  The unit price master 16 includes unit price masters 16d to 16e of the second group as unit price masters 16 corresponding to the unit price type "unit price by product quantity" in which unit prices are distinguished by product and quantity.

  Of these, the unit price master 16d is master data in which unit prices are defined by supplier unit price groups, products, and quantities. As one aspect of the unit price master 16d, data in which a customer unit price group, a product code, an application period, a quantity lower limit, a quantity upper limit, a contract unit price, and a contract charge rate are associated can be employed. FIG. 9 is a diagram illustrating a configuration example of the unit price master 16d for each business unit price group, each product, and each quantity. In the example of FIG. 9, the supplier unit price group set in the slip is “Super XX”, the product code is “101010”, and the reference date is the application period “2012/4/1 to 9999/99 / In the case of “99”, different unit prices are searched. That is, the quantity of the product set in the slip, for example, the order quantity, the shipment quantity, the delivery quantity and the inspection quantity is 999 or less, 1000 or more and 4999 or less, or 5000 or more and 9999 or less. Search results vary depending on whether For example, when the number of products set in the slip is 999 or less, 1100 yen is searched as the unit price. Further, when the number of products set in the slip is 1000 or more and 4999 or less, 1050 yen is searched as the unit price. Further, when the quantity of products set in the slip is 5000 or more and 9999 or less, 1000 yen is searched as the unit price.

  The unit price master 16e is master data in which a unit price is defined for each supplier, each product, and each quantity. As one aspect of the unit price master 16e, data in which a supplier code, a product code, an application period, a quantity lower limit, a quantity upper limit, a contract unit price, and a contract rate are associated can be employed. FIG. 10 is a diagram illustrating a configuration example of the unit price master 16e for each supplier, each product, and each quantity. In the example of FIG. 10, the supplier code set in the slip is “10101”, the product code is “101010”, and the reference date is within the applicable period “2012/4/1 to 9999/99/99”. In the case of, different unit prices are searched. That is, similarly to the example of FIG. 9 described above, when the quantity of products set in the slip is 999 or less, 1100 yen is searched as the unit price. Further, when the number of products set in the slip is 1000 or more and 4999 or less, 1050 yen is searched as the unit price. Further, when the quantity of products set in the slip is 5000 or more and 9999 or less, 1000 yen is searched as the unit price.

  In addition, the unit price master 16 includes a historical unit price master 16 f of the third group as the unit price master 16 corresponding to the unit price type “previous delivery unit price” in which the unit price is distinguished according to the history of the previous product delivery.

  The historical unit price master 16f is master data in which a history when a product is delivered is collected. As one aspect of the historical unit price master 16f, data in which a supplier code, a delivery destination code, a product code, a slip date, a sales unit price, a purchase unit price, and an occurrence date and time are associated can be employed. FIG. 11 is a diagram illustrating a configuration example of the historical unit price master 16f for each business partner, each delivery destination, and each product. In the example of FIG. 11, the values of the supplier code, the delivery destination code, and the product code are common between the first record from the top and the second record from the top. Here, the slip date of the second record from the top is newer than the first record from the top. Therefore, 1050 yen is searched for the sales unit price, whereas 1000 yen is searched for the purchase unit price.

  The control unit 17 has an internal memory for storing programs defining various processing procedures and control data, and executes various processes using these. As shown in FIG. 1, the control unit 17 includes a designation receiving unit 17a, a master updating unit 17b, a slip processing unit 17c, a reset instruction receiving unit 17d, and a unit price setting unit 17e.

  The designation receiving unit 17 a is a processing unit that receives designation of an application period and a unit price to be newly inserted within the range of the application period of the unit price master 16. As one aspect, when receiving an update request for the unit price master 16 from the client terminal 30, the specification receiving unit 17a specifies the master type code of the unit price master 16 to be updated among the plurality of unit price masters 16a to 16f. Accept. After that, when receiving the master type code of the unit price master 16 to be updated, the designation receiving unit 17a displays on the client terminal 30 a screen on which the application period and unit price can be specified together with the unit price master 16 corresponding to the master type code. Let For example, the designation receiving unit 17a displays the designated unit price master 16 on the display unit of the client terminal 30 in a table format or the like, and the start date of the application period newly inserted within the range of the application period of the unit price master 16 and A form in which the end date and unit price can be input or a pull-down menu in which these can be selected is displayed. At this time, the designation receiving unit 17a also displays a GUI that can input or select items necessary for uniquely specifying which record of the records included in the unit price master 16 is to be updated. . For example, in the case of the unit price master 16b for each supplier and each product shown in FIG. 7, it is necessary to accept a supplier code and a product code in addition to the application period. In this case, the designation receiving unit 17a causes the client terminal 30 to display a form in which the supplier code and the product code can be input or a pull-down menu in which these can be selected. With this display, the start date and end date of the application period and the unit price are accepted from the client terminal 30.

  The master update unit 17 b is a processing unit that executes update control of the unit price master 16. As one aspect, the master update unit 17b searches for a record in which an application period that has received a designation is inserted among application periods defined in the unit price master 16, using an application period and necessary items as search keys. Then, the master update unit 17b performs an update for dividing the application period to be inserted with respect to the application period of the record obtained as a search result, with the start date and the end date of the application period for which the designation is accepted as a boundary. That is, the master update unit 17b sets a new period in which the period divided by the start date of the application period divided by the insertion of the application period for which the designation has been received and the day before the start date of the application period for which the designation has been accepted is set as the application period. Generate a record. Further, the master update unit 17b sets a new period in which the period divided by the next day of the end date of the application period for which the designation is accepted and the end date of the application period that is divided by the insertion of the application period for which the designation is accepted as the application period. Generate a record. In addition, the master update unit 17b associates the unit price defined before the division with the two records newly generated by the previous division, and also supports the unit price accepted for the designation in the application period for which the designation was accepted. Generate the attached record. At this time, although the application periods are different among the three newly generated records, the values of the original record are copied for the items other than the unit price.

  FIG. 12 is a diagram illustrating an example of a method for updating the unit price master 16. In the example of FIG. 12, it is assumed that the unit price master 16b shown in FIG. 7, that is, the unit price master 16b for each supplier and each product is updated. For example, it is assumed that the supplier code “20101”, the product code “101020”, the application period “2011/4/1 to 2012/3/31”, and the contract unit price “1000” are received from the client terminal 30.

  In this case, the application period “2011/4/1 to 2012/3/31”, the supplier code “20101”, the product code “101020” and the contract unit price “1000” are used as search keys, and the unit price master 16b is set. Search for. As a result, in the unit price master 16b shown in the upper part of FIG. 12, the third record from the top is specified as the record into which the application period in which the designation is accepted is inserted. Then, the start date “1999/1/1” of the application period divided by the insertion of the application period “2011/4/1 to 2012/3/31” that received the specification, and the start date of the application period that received the specification A new record having a period divided by “2011/3/31” the previous day as the application period, that is, the third record from the top of the unit price master 16b shown in the lower part of FIG. Furthermore, it is separated by “2012/4/1” the day after the end date of the application period that accepted the designation and the end date “9999/99/99” of the application period that is divided by the insertion of the application period that accepted the designation. A new record having the period as the application period, that is, the fifth record from the top of the unit price master 16b shown in the lower part of FIG. In addition, the two records newly generated by the previous division are associated with the unit price “900” defined before the division, and the unit price accepted for the designation in the application period for which the designation was accepted. That is, the fourth record (thin fill) from the top of the unit price master 16b shown in the lower part of FIG. 12 is generated. At this time, although the application period is different between the three newly generated records, the values of the original records “20101” and “101020” are copied for the supplier code and product code excluding the unit price. Is taken over. As a result, it is possible to dynamically update the unit price of the product during the period for which the application period has already been defined.

  After updating the unit price master 16b, the history ID is numbered and the application period included in the record generated by accepting the update request among the three records generated earlier, that is, the fourth record from the top (thin fill) "2011/4/1 to 2012/3/31", supplier code "20101", product code "101020", contract unit price "1000", and update history information 13a in association with a master type code indicating the unit price master 16b Is registered in the storage unit 13. In this way, when the unit price master 13b is updated, values are not set in the update history information 13a for items such as the supplier unit price group, the delivery destination code, the product unit price group, and the quantity.

  The slip processing unit 17c is a processing unit that executes various processes related to slips. As one aspect, when the slip processing unit 17c receives a search request for a slip including a slip number from the client terminal 30, the same slip number as the slip number that has received the search request among the slips included in the slip information 13b. Search for vouchers with Then, the slip processing unit 17c causes the client terminal 30 to display a slip screen on which the slip obtained as a search result can be edited. When the slip screen is displayed in this manner, items on the slip screen displayed on the client terminal 30 such as customer information such as a supplier code and a delivery destination code, and transaction content information such as a product code and a quantity are displayed. In addition, reference date information is accepted. As an example of the reference date information, there is a reference date setting indicating which business date is adopted as well as a business date such as an order date, a shipping date, a delivery date, and an inspection date.

  FIG. 13 is a diagram illustrating an example of a slip screen. FIG. 13 shows an order slip screen 200 as an example. When the inquiry button 220 is pressed in a state where the slip number is entered in the text box 210 laid out at the top of the order slip screen 200, a display for displaying “customer information” and “reference date information” at the bottom thereof. Area 230 is displayed. When the “customer information” tab 230A displayed in the display area 230 is selected, a form in which the supplier code and the delivery destination code can be input is displayed. In addition, when the “reference date information” tab 230B is selected, a form in which business days such as an order date, a planned shipping date, a scheduled delivery date, and a planned inspection date can be entered is displayed. Option such as a radio button indicating whether or not to be adopted on the reference date is displayed. Further, a table in which product codes, order quantities, etc. can be input is displayed at the bottom of the display area 230. Further, other slips such as an estimate slip, a shipping slip, an inspection slip, and a sales slip can be called from the slip type pull-down menu 240 displayed on the upper right of the order slip screen 200. On such an order slip screen 200, entry date, for example, customer information such as supplier code and delivery destination code, transaction content information such as product code and quantity, and reference date information are accepted. Thereafter, when the registration button 250 displayed on the order slip screen 200 is pressed, various information input to the order slip screen 200 is registered in the storage unit 13 as slip information 13b.

  Thereafter, when the slip registration operation is executed on the slip screen displayed on the client terminal 30, the slip processing unit 17c determines whether or not the reference date has been changed, for example, the date change or operation on the slip screen. It is determined whether or not the day has been reselected. At this time, if the reference date has not been changed, the slip processing unit 17c determines whether or not a unit price has been set for the slip. At this time, if the unit price has already been set, it can be determined that the unit price does not fluctuate due to input on the slip screen. In this case, in order to determine whether the unit price has fluctuated due to the update of the unit price master 16, the slip processing unit 17c starts with the reference date set in the slip, the supplier code, the delivery destination code. The slip information such as the product code, the product unit price group, and the quantity is output to the reacquisition instruction receiving unit 17d.

  In addition, when the reference date is changed, the unit price of the product may change as the application range to which the unit price is applied changes. In this case, the slip processing unit 17c determines whether or not the slip for which the registration operation has been performed satisfies the unit price setting condition. As an example, when the reference date is set to “order received date”, the slip processing unit 17c determines whether or not the order receiving work has been completed. As another example, when the reference date is set to “shipping date”, the slip processing unit 17c determines whether or not the shipping operation has been completed. As described above, when the sales operation process set as the reference date is completed, the slip processing unit 17c outputs an instruction to set the unit price of the product to the slip to the unit price setting unit 17e.

  On the other hand, when the unit price is not set, the slip processing unit 17c determines whether or not the reference date of the slip is blank, that is, blank. At this time, when the reference date is blank, the slip processing unit 17c displays a screen for prompting the input of the reference date and accepts the setting of the reference date. Even when the setting of the reference date is received in this way, the slip processing unit 17c determines whether or not the slip for which the registration operation has been performed satisfies the unit price setting condition. At this time, when the slip information satisfies the unit price setting condition, the slip processing unit 17c outputs an instruction to set the unit price of the product to the slip to the unit price setting unit 17e.

  The resetting instruction receiving unit 17d is a processing unit that receives a resetting instruction for resetting the unit price of the product in the slip using the update history information 13a. As one aspect, the resetting instruction receiving unit 17d matches the master type code in which the unit price is set in the slip among the records included in the update history information 13a, that is, the code representing the unit price master 16 used when setting the unit price. The records to be extracted. Then, the resetting instruction receiving unit 17d targets each item of the unit price master 16 corresponding to the master type code, and records each piece of slip information output by the slip processing unit 17c among the records of the update history information 13a extracted previously. Extract records whose values match with items. After that, the resetting instruction receiving unit 17d determines whether or not the reference date output by the slip processing unit 17c is within the range of the application period included in the record of the update history information 13a. At this time, if the reference date is within the range of the application period, it can be determined that the unit price set in the slip is set using the unit price before the update of the unit price master 16. Therefore, the resetting instruction receiving unit 17d receives a notification for prompting resetting of the unit price on the slip and receives the resetting instruction. At this time, when a reset instruction is received, the reset instruction receiving unit 17d outputs an instruction to reset the unit price to the slip to the unit price setting unit 17e. Here, the case where the unit price resetting is executed on condition that the resetting instruction is accepted is illustrated, but when the reference date is within the applicable period, the unit price resetting is automatically executed. It doesn't matter if you let them.

  The unit price setting unit 17e is a processing unit that sets a unit price for a slip. As one aspect, the unit price setting unit 17e sets the unit price for the slip when the sales business process set as the reference date is completed. The unit price setting unit 17e resets the unit price for the slip when the reference date output by the slip processing unit 17c is within the range of the application period included in the record information of the update history information 13a previously extracted. . It should be noted that the content of the process is the same except that the unit price setting and the unit price resetting are different in conditions for starting the process.

  The unit price setting unit 17e acquires a record corresponding to the supplier code set in the slip among the records included in the customer master 15b. Then, the unit price setting unit 17e determines whether or not the value of the unit price determination section included in the previously acquired record of the customer master 15b is “9”. At this time, when the value of the unit price determination section is not “9”, that is, when the value of the unit price determination section is “1”, the unit price setting unit 17e manually sets the unit price in the slip.

  On the other hand, if the value of the unit price determination section is “9”, the unit price setting unit 17e determines whether the value of the unit price search order included in the previously acquired record of the customer master 15b is “70”. Determine. At this time, if the value of the unit price search order is not “70”, the unit price setting unit 17e further determines whether or not the value of the unit price search order is “60”.

  Here, when the value of the unit price search order is neither “70” nor “60”, the unit price setting unit 17e corresponds to the unit price type “unit price by business partner” in which the unit price is distinguished by business partner. The search for one group of unit price masters 16a to 16c is started. At this time, the unit price setting unit 17e is configured in the order of the unit price master 16c for each business partner, each delivery destination and each product, the unit price master 16b for each business partner and each product, each unit price group for each business partner, and the unit price master 16a for each product. Perform a search for.

  Specifically, the unit price setting unit 17e has the same value as the business partner code, delivery destination code, and product code set in the slip from the unit price master 16c for each business partner, each delivery destination, and each product. Search for records that have a reference date within the applicable period. At this time, when acquisition of the record from the unit price master 16c fails, the unit price setting unit 17e receives the supplier code, the product code and the value set in the slip from the unit price master 16b for each supplier and each product. Further search is made for records that are identical and whose reference date falls within the range of the application period. And when acquisition of the record from the unit price master 16b fails, the unit price setting unit 17e reads the supplier unit price group and the product code set in the slip from the unit price master 16a for each supplier unit price group and each product. Further search is made for records having the same value and the reference date within the applicable period.

  Here, when acquisition of the record from the unit price master 16 of any of the unit price master 16c, the unit price master 16b, or the unit price master 16a is successful, the contract unit price included in the record acquired from the unit price master 16 is included in the slip. Is set. For example, when the supplier code “10101”, supplier unit price group “Super XX”, supplier code “Store A”, product code “101010” and base date “2012/4/23” are set in the slip Is assumed. At this time, when the unit price master 16c shown in FIG. 8 is searched, since the second record from the top is acquired, the unit price “900 yen” is set in the slip. Further, when the unit price master 16b shown in FIG. 7 is searched, the second record from the top is acquired, so the unit price “1000 yen” is set in the slip. Further, when the unit price master 16a shown in FIG. 6 is searched, the second record from the top is acquired, so the unit price “900 yen” is set in the slip.

  On the other hand, when the unit price setting unit 17e fails to acquire a record from any of the unit price masters 16c, the unit price master 16b, and the unit price master 16a, the unit price type “ The search of the unit price masters 16d to 16e of the second group corresponding to “unit price by product quantity” is started. At this time, the unit price setting unit 17e searches for the unit price in the order of the unit price master 16e for each supplier, each product, and each quantity, and each unit price master 16d for each supplier unit price group, each product, and each quantity. If the value of the unit price search order is “60”, the search to the unit price masters 16a to 16c of the first group is not executed, and the search starts from the unit price masters 16d to 16e of the second group. .

  Specifically, the unit price setting unit 17e has the same value as the supplier code, product code, and quantity set in the slip from the unit price master 16e for each supplier, product, and quantity, and Search for records whose base date falls within the applicable period. At this time, when acquisition of the record from the unit price master 16e fails, the unit price setting unit 17e reads the unit price group set in the slip from the unit price master 16d for each supplier unit price group, each product, and each quantity. Further, a record in which the product code, the quantity, and the value are the same and the reference date is included in the applicable period is further searched.

  Here, when acquisition of the record from the unit price master 16 of either the unit price master 16e or the unit price master 16d is successful, the contract unit price included in the record acquired from the unit price master 16 is set in the slip. For example, when the supplier code “10101”, supplier unit price group “Super XX”, supplier code “Store A”, product code “101010” and base date “2012/4/23” are set in the slip Is assumed. At this time, when the unit price master 16e shown in FIG. 10 is searched, since the first record from the top is acquired, the unit price “1100 yen” is set in the slip. Further, when the unit price master 16d shown in FIG. 9 is searched, the first record from the top is acquired, so the unit price “1100 yen” is set in the slip.

  On the other hand, if the unit price setting unit 17e fails to acquire a record from either the unit price master 16e or the unit price master 16d, the unit price type “last time” in which the unit price is distinguished according to the history of the previous delivery of the product. The search for the historical unit price master 16f of the third group corresponding to “delivery unit price” is started. If the value of the unit price search order is “70”, the search to the unit price masters 16a to 16c of the first group and the unit price masters 16d to 16e of the second group is not executed, and the unit price of the third group. The search starts from the master 16f.

  More specifically, the unit price setting unit 17e has the same value as the business partner code, delivery destination code, and product code set in the slip from the historical unit price master 16f for each business partner, each delivery destination, and each product. And the record with the latest voucher date is retrieved. At this time, when the record acquisition from the unit price master 16f is successful, the contract unit price included in the record acquired from the unit price master 16 is set in the slip. For example, when the supplier code “10101”, supplier unit price group “Super XX”, supplier code “Store A”, product code “101010” and base date “2012/4/23” are set in the slip Is assumed. At this time, when the unit price master 16f shown in FIG. 11 is searched, the second record from the top is acquired, so the unit price “1050 yen” is set in the slip.

  On the other hand, if the acquisition of the record from the unit price master 16f fails, the unit price setting unit 17e has failed to acquire the unit price from all the unit price masters 16, so that the unit price is set manually in the slip.

  Note that various integrated circuits and electronic circuits can be employed for the control unit 17. Further, a part of the functional unit included in the control unit 17 may be another integrated circuit or an electronic circuit. For example, an ASIC (Application Specific Integrated Circuit) is an example of the integrated circuit. Examples of the electronic circuit include a central processing unit (CPU) and a micro processing unit (MPU).

[Process flow]
Next, the process flow of the sales management apparatus according to the present embodiment will be described. Here, after (1) sales management processing executed by the sales management apparatus 10 is described, (2) unit price setting processing will be described.

(1) Sales Management Processing FIG. 14 is a flowchart illustrating the procedure of sales management processing according to the first embodiment. This sales management process is a process that is repeatedly executed as long as the power of the sales management apparatus 10 is ON. The process is started when a search request for a slip including a slip number is received from the client terminal 30.

  As illustrated in FIG. 14, the slip processing unit 17 c searches for a slip having the same slip number as the slip number that has received the search request from the slips included in the slip information 13 b and obtains the slip obtained as a result of the search. Is displayed on the client terminal 30 (step S101).

  Then, the slip processing unit 17c, through the slip screen displayed on the client terminal 30, stores customer information such as supplier code and delivery destination code, transaction content information such as product code and quantity, for example. In addition, reference date information is received (step S102).

  Subsequently, when the slip registration operation is performed on the slip screen, the slip processing unit 17c determines whether the reference date has been changed, for example, whether the date has been changed again or the business day has been reselected on the slip screen. It is determined whether or not (step S103).

  At this time, if the reference date has not been changed (No at Step S103), the slip processing unit 17c determines whether or not the unit price has been set for the slip (Step S104). If the unit price is not set (Yes at Step S104), the slip processing unit 17c determines whether or not the reference date of the slip is blank, that is, blank (Step S105).

  Subsequently, when the reference date is blank (Yes at Step S105), the slip processing unit 17c displays a screen for prompting the input of the reference date and accepts the setting of the reference date (Step S106). If the reference date is not blank (No at Step S105), the process at Step S106 is skipped and the process proceeds to Step S107.

  In addition, when the reference date is changed (Yes in step S103), the unit price of the product may change as the application range to which the unit price is applied changes. Also in this case, the process from step S104 to step S106 is skipped, and the process proceeds to step S107.

  Thereafter, the slip processing unit 17c determines whether or not the slip for which the registration operation has been performed satisfies a unit price setting condition (step S107). For example, when the reference date is set to “order received date”, the slip processing unit 17c determines whether or not the order receiving work has been completed. As another example, when the reference date is set to “shipping date”, the slip processing unit 17c determines whether or not the shipping operation has been completed.

  When the slip satisfies the unit price setting condition (Yes at Step S107), the unit price setting unit 17e executes a “unit price setting process” for setting the unit price in the slip (Step S108), and the slip processing unit 17c receives the slip. Is registered in the storage unit 13 (step S109), and the process is terminated.

  On the other hand, when the slip does not satisfy the unit price setting condition (No at Step S107), the slip processing unit 17c skips Step S108 and registers the slip information set in the slip in the storage unit 13 (Step S109). ), The process is terminated.

  If the unit price has been set (No at Step S104), the reset instruction receiving unit 17d is a record that matches the master type code in which the unit price is set in the slip among the records included in the update history information 13a. In the range of the application period included in the record whose value matches with each item of the slip information output by the slip processing unit 17c for the item included in the unit price master 16 corresponding to the master type code, It is determined whether or not the reference date output by the slip processing unit 17c is included (step S110).

  At this time, if the reference date is within the range of the application period (Yes at Step S110), it can be determined that the unit price set in the slip is set using the unit price before the update of the unit price master 16. Accordingly, the resetting instruction receiving unit 17d waits for a resetting instruction to be made by notifying the resetting of the unit price to the slip (step S111).

  At this time, if a reset instruction is accepted (Yes at step S111), the unit price setting unit 17e executes a “unit price setting process” for setting the unit price in the slip (step S108), and the slip processing unit 17c adds the unit price to the slip. The set slip information is registered in the storage unit 13 (step S109), and the process ends.

  On the other hand, when the reference date is not within the range of the application period or when the reset instruction is not accepted (No at Step S110 or No at Step S111), the slip processing unit 17c stores the slip information set in the slip. Registered in the unit 13 (step S109), and the process ends.

(2) Unit Price Setting Process FIGS. 15 and 16 are flowcharts illustrating the procedure of the unit price setting process according to the first embodiment. This unit price setting process is a process corresponding to step S108 shown in FIG. 14, and is started when step S107 is affirmative or step S111 is affirmative.

  As shown in FIG. 15, the unit price setting unit 17e acquires a record corresponding to the supplier code set in the slip among the records included in the customer master 15b (step S301).

  Then, the unit price setting unit 17e determines whether or not the value of the unit price determination section included in the record of the customer master 15b acquired in step S301 is “9” (step S302). When the value of the unit price determination category is not “9”, that is, when the value of the unit price determination category is “1” (No in step S302), the unit price setting unit 17e causes the slip to be manually set to the unit price. (Step S303), the process ends.

  On the other hand, when the value of the unit price determination section is “9” (Yes at Step S302), the unit price setting unit 17e determines whether the value of the unit price search order included in the record of the customer master 15b is “70”. Is determined (step S304). If the value of the unit price search order is “70” (Yes at Step S304), the process from Step S305 to Step S315 described below is skipped, and the process proceeds to Step S316.

  At this time, if the value of the unit price search order is not “70” (No at Step S304), the unit price setting unit 17e further determines whether or not the value of the unit price search order is “60” (Step S305). . If the value of the unit price search order is “60” (Yes at Step S305), the processing from Step S306 to Step S311 below is skipped, and the process proceeds to Step S312.

  Here, when the value of the unit price search order is not “60”, that is, when the value of the unit price search order is “50” (No in step S305), the unit price setting unit 17e determines the value for each business partner and each delivery destination. In addition, from the unit price master 16c for each product, a record that has the same value as the supplier code, the delivery destination code, and the product code set in the slip and includes the reference date within the range of the application period is searched (step S306). ).

  At this time, when acquisition of the record from the unit price master 16c has failed (Yes in step S307), the unit price setting unit 17e receives the supplier code set in the slip from the unit price master 16b for each supplier and each product. Further search is made for a record having the same value as the product code and having the reference date within the range of the application period (step S308).

  If acquisition of the record from the unit price master 16b has failed (Yes at step S309), the unit price setting unit 17e determines the supplier unit price set in the slip from the unit price master 16a for each supplier unit price group and each product. Further search is made for a record having the same value as that of the group and the product code and having the reference date within the range of the application period (step S310).

  Here, when acquisition of the record from the unit price master 16 of any of the unit price master 16c, the unit price master 16b, or the unit price master 16a is successful (No at Step S307, No at Step S309, or No at Step S311), the unit price setting unit 17e Sets the contract unit price included in the record acquired from the unit price master 16 in the slip (step S318), and ends the process.

  If acquisition of the record from the unit price master 16a has failed (Yes in step S311), the unit price setting unit 17e determines the transaction set in the slip from the unit price master 16e for each supplier, product, and quantity. A record having the same value as the destination code, product code, quantity, and the reference date within the applicable period is searched (step S312).

  At this time, if acquisition of the record from the unit price master 16e has failed (Yes in step S313), the unit price setting unit 17e is set in the slip from the unit price master 16d for each business unit price group, product, and quantity. Further search is made for a record that has the same value as the supplier unit price group, product code, quantity, and the reference date is within the range of the application period (step S314).

  Here, when the record acquisition from either the unit price master 16e or the unit price master 16d is successful (No in step S313 or No in step S315), the unit price setting unit 17e acquires the record from the unit price master 16. The contract unit price included in the recorded record is set in the slip (step S318), and the process ends.

  On the other hand, if acquisition of the record from the unit price master 16d also fails (Yes at step S315), the supplier code and delivery set in the slip from the historical unit price master 16f for each supplier, each delivery destination, and each product. A record having the same value as the destination code and the product code and having the latest slip date is searched (step S316).

  At this time, if acquisition of the record from the unit price master 16f is successful (Yes at Step S317), the unit price setting unit 17e sets the contract unit price included in the record acquired from the unit price master 16 in the slip (Step S317). S318), the process ends.

  On the other hand, if the acquisition of the record from the unit price master 16f fails (No at Step S317), the unit price setting unit 17e has failed to acquire the unit price from all the unit price masters 16, so It is set by input (step S303), and the process is terminated.

[Effect of Example 1]
As described above, the sales management apparatus 10 according to the present embodiment accepts designation of an application period and a unit price to be newly inserted within the range of the application period of the unit price master 16, and sets the application period defined in the unit price master 16. For the application period in which the application period for which the designation is accepted is inserted, an update is performed to divide the application period to be inserted on the boundary of the start date and the end date of the application period for which the designation is accepted, and the designation is accepted. Execute the update that associates the specified unit price with the application period, and apply the unit price of the product to the voucher that deals with products that fall within the application period for which the base date for applying the unit price has received the specification. When a reset instruction for resetting is received and the resetting instruction is received, the product associated with the application period including the reference date among the unit prices of the products defined in the unit price master 16 is received. To set the unit price in the document.

  For this reason, in the sales management apparatus 10 according to the present embodiment, the unit price master can be dynamically updated even if the unit price of the product in the period for which the application period has already been defined. The unit price can be changed even if the unit price of the product becomes inappropriate. Furthermore, in the sales management device 10 according to the present embodiment, if the unit price set in the slip is set using the unit price before update of the unit price master 16, the unit price can be reset in the slip. Therefore, according to the sales management device 10, it is possible to set an appropriate unit price for the product.

  Although the embodiments related to the disclosed apparatus have been described above, the present invention may be implemented in various different forms other than the above-described embodiments. Therefore, another embodiment included in the present invention will be described below.

[Distribution and integration]
In addition, each component of each illustrated apparatus does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, the instruction receiving unit 17a, the master updating unit 17b, the slip processing unit 17c, the resetting instruction receiving unit 17d, or the unit price setting unit 17e may be connected as an external device of the sales management device 10 via a network. In addition, each device has an instruction receiving unit 17a, a master updating unit 17b, a slip processing unit 17c, a resetting instruction receiving unit 17d, or a unit price setting unit 17e, and is connected to the network to cooperate with the above sales. You may make it implement | achieve the function of the management apparatus 10. FIG.

[Unit price setting program]
The various processes described in the above embodiments can be realized by executing a prepared program on a computer such as a personal computer or a workstation. In the following, an example of a computer that executes a unit price setting program having the same function as that of the above embodiment will be described with reference to FIG.

  FIG. 17 is a schematic diagram illustrating an example of a computer that executes a unit price setting program according to the first and second embodiments. As illustrated in FIG. 17, the computer 100 includes an operation unit 110a, a speaker 110b, a camera 110c, a display 120, and a communication unit 130. Further, the computer 100 includes a CPU 150, a ROM 160, an HDD 170, and a RAM 180. These units 110 to 180 are connected via a bus 140.

  As shown in FIG. 17, the HDD 170 has the same functions as those of the instruction receiving unit 17a, the master updating unit 17b, the slip processing unit 17c, the resetting instruction receiving unit 17d, and the unit price setting unit 17e described in the first embodiment. A unit price setting program 170a to be exhibited is stored in advance. The unit price setting program 170a is appropriately integrated, as with each component of the instruction receiving unit 17a, the master updating unit 17b, the slip processing unit 17c, the resetting instruction receiving unit 17d, and the unit price setting unit 17e shown in FIG. Or you may isolate | separate. In other words, all data stored in the HDD 170 need not always be stored in the HDD 170, and only data necessary for processing may be stored in the HDD 170.

  Then, the CPU 150 reads the unit price setting program 170 a from the HDD 170 and expands it in the RAM 180. Thus, as shown in FIG. 17, the unit price setting program 170a functions as a unit price setting process 180a. The unit price setting process 180a expands various data read from the HDD 170 in an area allocated to itself on the RAM 180, and executes various processes based on the expanded data. The unit price setting process 180a is a process executed by the instruction receiving unit 17a, the master updating unit 17b, the slip processing unit 17c, the resetting instruction receiving unit 17d, and the unit price setting unit 17e shown in FIG. The process shown in FIG. 16 is included. In addition, each processing unit virtually realized on the CPU 150 does not always require that all processing units operate on the CPU 150, and only a processing unit necessary for the processing needs to be virtually realized.

  Note that the unit price setting program 170a is not necessarily stored in the HDD 170 or the ROM 160 from the beginning. For example, each program is stored in a “portable physical medium” such as a flexible disk inserted into the computer 100, so-called FD, CD-ROM, DVD disk, magneto-optical disk, or IC card. Then, the computer 100 may acquire and execute each program from these portable physical media. In addition, each program is stored in another computer or server device connected to the computer 100 via a public line, the Internet, a LAN, a WAN, etc., and the computer 100 acquires and executes each program from these. It may be.

DESCRIPTION OF SYMBOLS 10 Sales management apparatus 11 Communication I / F part 13 Storage part 13a Update history information 13b Document information 14 Master data 15a Merchandise master 15b Customer master 15c Supplier master 15d System master 16, 16a, 16b, 16c, 16d, 16e, 16f unit price master 17 control unit 17a designation receiving unit 17b master updating unit 17c slip processing unit 17d resetting instruction receiving unit 17e unit price setting unit

Claims (6)

A designation receiving unit that accepts designation of an application period and a unit price to be newly inserted within a range of an application period of a unit price master associated with a unit price of the product for each application period in which the unit price of the product is applied;
Of the application period defined in the unit price master, the application period that is inserted with the start date and the end date of the application period that receives the designation as a boundary with respect to the application period in which the application period that has accepted the designation is inserted. A master update unit that executes an update that divides and executes an update that associates the unit price that received the designation with the application period that accepted the designation;
A reset instruction accepting unit for accepting a reset instruction for resetting the unit price of a product in the slip for a slip whose target is a product corresponding to the application period for which the reference date for accepting the unit price is accepted. When,
A unit price setting unit configured to set, in the slip, a unit price of a product associated with an application period including the reference date among unit prices of products defined in the unit price master when the reset instruction is received; A unit price setting device characterized by that. The slip is set based on a business partner, a delivery destination delivered by the business partner, the quantity of products traded with the business partner, or a combination thereof,
The unit price setting unit refers to correspondence information in which a correspondence relationship between a plurality of unit price masters in which different unit prices are defined for the same product and a category of the slip is defined, and the reset instruction among a plurality of unit price masters 2. The unit price setting apparatus according to claim 1, wherein the unit price of the product is set in the slip by using a unit price master corresponding to the category of the slip that received the item.   The unit price setting unit refers to order information in which the order of each unit price master included in a plurality of unit price masters in which different unit prices are defined for the same product, and the unit price master according to the order defined in the order information. 3. The unit price setting apparatus according to claim 1, wherein the process of searching for the unit price of the product is repeatedly executed until the unit price of the product is obtained by the search.   The unit price setting unit, when the reference date set in the slip is changed, of the product associated with the application period including the changed reference date among the unit price of the product defined in the unit price master 4. The unit price setting apparatus according to claim 1, wherein the unit price is set in the slip. Computer
Accept the designation of the application period and unit price to be newly inserted within the range of the application period of the unit price master associated with the unit price of the product for each application period to which the unit price of the product is applied,
Of the application period defined in the unit price master, the application period that is inserted with the start date and the end date of the application period that receives the designation as a boundary with respect to the application period in which the application period that has accepted the designation is inserted. While performing an update to divide, execute an update that associates the unit price that received the designation with the application period that accepted the designation,
Accepting a reset instruction for resetting the unit price of the product in the slip for a slip whose target is a product corresponding to the application period in which the reference date receiving the unit price is applied,
Executing the process of setting the unit price of the product associated with the application period including the reference date in the unit price of the product defined in the unit price master when the reset instruction is received, to the slip A characteristic unit price setting method. On the computer,
Accept the designation of the application period and unit price to be newly inserted within the range of the application period of the unit price master associated with the unit price of the product for each application period to which the unit price of the product is applied,
Of the application period defined in the unit price master, the application period that is inserted with the start date and the end date of the application period that receives the designation as a boundary with respect to the application period in which the application period that has accepted the designation is inserted. While performing an update to divide, execute an update that associates the unit price that received the designation with the application period that accepted the designation,
Accepting a reset instruction for resetting the unit price of the product in the slip for a slip whose target is a product corresponding to the application period in which the reference date receiving the unit price is applied,
When the reset instruction is received, the unit price of the product associated with the application period including the reference date among the unit prices of the product defined in the unit price master is set in the slip. A unique unit price setting program.

Images