Fare calculation device, method for fare calculation, and fare calculation program

Abstract

To provide a fare calculation device, a method for fare calculation, and a fare calculation program capable of accurately determining whether a small-lot fare is to be generated.SOLUTION: The fare calculation device according to the present embodiment includes: a storage unit configured to store a fare generation condition master, in which at least one key item and a reference value for quantity or amount are registered in association with each other for each definition specifying a small-lot fare generation condition, and to store sales data including a sales number, sales date, supplier, billing destination, customer, delivery destination, product, product subcategory, quantity, sales unit price, and sales amount; and small-lot fare calculation means configured to extract sales data according to an extraction condition, aggregate the reference values defined in the fare generation condition master for each sales number of the extracted sales data, compare the aggregated reference values for each definition with the fare generation condition master, and, when any one definition satisfies the small-lot fare generation condition, generate small-lot fare billing data.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a fare calculation device, a fare calculation method, and a fare calculation program. [Background technology]

[0002] For example, in a product or industry where small lots are delivered to one delivery destination, there is a commercial flow in which the cost increase due to the increase in the number of deliveries is borne by the customer in the form of small lot freight. Conventionally, a system for small lot delivery is known, for example, from Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-75634 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the past, whether or not small-item freight charges were incurred was determined by the person in charge, and the calculation of small-item freight charges was complex, which led to issues such as missed billings and incorrect billing of customers for whom freight charges were not actually incurred due to human error.

[0005] The present invention has been made in consideration of the above, and aims to provide a fare calculation device, a fare calculation method, and a fare calculation program that can accurately determine whether or not small-lot freight charges are incurred. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a freight calculation device that has a control unit and calculates small parcel freight, wherein the control unit is configured to be able to access a freight generation condition master in which one or more key items, quantity or amount standard values ​​are associated with each definition that specifies the small parcel freight generation conditions, and sales data including sales number, sales date, supplier, billing destination, customer, delivery destination, product, product subcategory, quantity, sales price, and sales amount, and is characterized by having a small parcel freight calculation means that extracts the sales data in accordance with extraction conditions, aggregates the standard values ​​for each definition of the freight generation condition master for each sales number of the extracted sales data, compares the aggregated standard values ​​for each definition with the freight generation condition master, and creates small parcel freight billing data if even one definition meets the small parcel freight generation conditions.

[0007] In addition, according to one aspect of the present invention, the control unit is configured to be able to access a freight unit price master in which freight unit prices for small parcel freight are registered, and the small parcel freight billing data may include a freight amount obtained by multiplying the quantity, which is the standard value for each aggregated definition code, by the freight unit price in the freight unit price master.

[0008] According to another aspect of the present invention, the key items of the freight generating condition master may include one or more of product subcategory, customer, delivery destination, and supplier.

[0009] According to another aspect of the present invention, the data of the freight generating condition master may be set by an operator.

[0010] In order to solve the above-mentioned problems and achieve the object, the present invention provides a freight calculation method executed by an information processing device equipped with a control unit, wherein the control unit is configured to be able to access a freight generation condition master in which one or more key items, quantity or amount reference values ​​are associated and registered for each definition that specifies the small-lot freight generation conditions, and sales data including sales number, sales date, supplier, billing destination, customer, delivery destination, product, product subcategory, quantity, sales price, and sales amount, The control unit extracts the sales data in accordance with the extraction conditions, and for each sales number in the extracted sales data, it aggregates the standard values ​​for each definition in the freight generation condition master, compares the aggregated standard values ​​for each definition with the freight generation condition master, and if even one definition satisfies the small parcel freight generation condition, it includes a small parcel freight calculation process that creates small parcel freight billing data.

[0011] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a freight calculation program to be executed by an information processing device equipped with a control unit, wherein the control unit is configured to be able to access a freight generation condition master in which one or more key items, quantity or amount standard values ​​are associated with each definition that specifies the small parcel freight generation conditions, and sales data including sales number, sales date, supplier, billing destination, customer, delivery destination, product, product subcategory, quantity, sales price, and sales amount, and the control unit extracts the sales data in accordance with the extraction conditions, aggregates the standard values ​​for each definition in the freight generation condition master for each sales number of the extracted sales data, compares the aggregated standard values ​​for each definition with the freight generation condition master, and if even one definition meets the small parcel freight generation conditions, executes a small parcel freight calculation process that creates small parcel freight billing data. [Effects of the Invention]

[0012] According to the present invention, it is possible to accurately determine whether or not small-lot freight charges are incurred. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a fare calculation device. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of the freight generating condition master. [Figure 3] FIG. 3 is a diagram illustrating an example of the configuration of the freight unit price master. [Figure 4] FIG. 4 is a flowchart illustrating an example of the overall processing of the control unit of the fare calculation device according to this embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the processing of the control unit of the fare calculation device in this embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the processing of the control unit of the fare calculation device in this embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the processing of the control unit of the fare calculation device in this embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the processing of the control unit of the fare calculation device in this embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the processing of the control unit of the fare calculation device in this embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the processing of the control unit of the fare calculation device in this embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the processing of the control unit of the fare calculation device in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.

[0015] [1. Overview] The outline of the present invention will be explained in the following order: [1-1. Problem], [1-2. Solution], [1-3. Effects], and [1-4. Functional Overview].

[0016] [1-1. Issues] For example, in industries that deliver small quantities of parcels to a single destination, there are cases where the cost of delivery increases because fewer parcels can be delivered at one time, resulting in an increase in the number of deliveries. The increased freight charges due to such small parcel deliveries are billed to customers as small parcel charges, but because the conditions for incurring small parcel charges vary and are determined by a combination of supplier, customer, delivery destination, product, quantity, and amount, there have been cases where small parcel freight charges have been overlooked due to human error, or where customers who would not normally be charged small parcel freight charges have been billed.

[0017] [1-2. Solution] In this invention, we focus on the fact that the conditions for incurring small parcel fare can be determined according to predetermined rules, although there are many combinations, and by managing the conditions for incurring small parcel fare in a master file, we have created a system that can determine whether or not small parcel fare will be incurred, thereby making it possible to accurately determine whether or not small parcel fare will be incurred.

[0018] [1-3.Effects] By using a master that registers the conditions for generating small parcel freight to determine whether or not small parcel freight will be incurred, it is possible to accurately determine whether or not small parcel freight will be incurred, and it is possible to prevent missed or incorrect billing due to human error.In addition, even if the criteria for determining whether or not small parcel freight will be incurred change, it is now possible to respond quickly by simply changing the master settings.

[0019] [1-4. Functionality Overview] The functional outline of the present invention is as follows. (1) Pre-register the master data that will be used as the criteria for determining whether small-lot freight charges will be incurred. (2) Execute the small parcel freight billing data creation process. The sales generated under the specified conditions are tallied and small parcel freight billing data is created by referencing the master registered in (1).

[0020] The present invention is widely applicable to industries that charge small lot freight rates for small lot deliveries.

[0021] [2. Configuration] An example of the configuration of the fare calculation device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the fare calculation device 100.

[0022] The fare calculation device 100 is a commercially available desktop personal computer. Note that the fare calculation device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0023] The fare calculation device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. The units comprised in the fare calculation device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0024] The communication interface unit 104 communicatively connects the fare calculation device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the fare calculation device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

[0025] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0026] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0027] The storage unit 106 also stores a freight generating condition master 106a, a freight unit price master 106b, sales data, small lot freight billing data, etc. Fig. 2 is a diagram showing an example of the configuration of the freight generating condition master 106a. Fig. 3 is a diagram showing an example of the configuration of the freight unit price master 106b.

[0028] The freight charge generation condition master 106a is a master that sets the small-lot freight charge generation conditions, and can be configured with a table that associates and registers definitions (definition codes and / or definition names), key items 1, 2, 3, and reference values, as shown in Figure 2. The key items may include one or more of the following: product subcategory (e.g., solvent, preservative, etc.), customer, delivery destination, and supplier.

[0029] The freight unit price master 106b is a master that sets the unit price of small-lot freight, and can be composed of a table that associates and registers the delivery company, supplier, warehouse, delivery destination, application start date, application end date, and freight unit price, as shown in Figure 3.

[0030] Sales data may include sales number, line, sales date, business establishment, supplier, billing address, customer, delivery address, delivery company, product, product subcategory, quantity (units), sales price, and sales amount.

[0031] The small parcel freight billing data may include the small parcel freight billing number, line, sales date, customer, expense item, quantity (units), freight unit price, and freight amount.

[0032] The control unit 102 is a CPU or the like that comprehensively controls the fare calculation device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs.

[0033] The control unit 102 is configured to be able to access the freight generating condition master 106a, the freight unit price master 106b, sales data, small lot freight billing data, etc. stored in the memory unit 106. Note that the freight generating condition master 106a, the freight unit price master 106b, sales data, small lot freight billing data, etc. may be stored in another location (for example, the server 200) as long as the control unit 102 is able to access them.

[0034] The control unit 102 conceptually includes a data registration unit 102a, a master maintenance unit 102b, a small parcel fare calculation unit 102c, and a screen display control unit 102d.

[0035] The data registration unit 102a inputs sales data in response to an operation by an operator or the like on a sales input screen (not shown) displayed on the monitor 114, and registers the data in the storage unit 106, for example.

[0036] The master maintenance unit 102b is for editing, such as inputting, adding, or changing data to the freight generating condition master 106a and the freight unit price master 106b, in response to operations by an operator or the like on a master maintenance screen (not shown) displayed on the monitor 114. In this way, the operator can arbitrarily set the contents of the freight generating condition master 106a and the freight unit price master 106b.

[0037] The small parcel freight calculation unit 102c extracts sales data registered in the storage unit 106 according to extraction conditions specified by the operator's operation on the freight billing data creation processing screen (see Figure 6) displayed on the monitor 114, calculates the standard values ​​for each definition code in the freight generating condition master 106a for each sales number in the extracted sales data, compares the calculated standard values ​​for each definition code with the freight generating condition master 106a, and creates small parcel freight billing data if even one definition code meets the small parcel freight generating condition. The small parcel freight billing data may include a freight amount calculated by multiplying the quantity, which is the standard value for each calculated definition code, by the freight unit price in the freight unit price master 106b.

[0038] The screen display control unit 102d controls the display of various screens (for example, a sales input screen, a freight billing data creation processing screen, a master maintenance screen, etc.) displayed on the monitor 114 and the inputs thereto.

[0039] [3. Specific examples of processing] A specific example of the processing of the fare calculation device 100 in this embodiment will be described with reference to Figures 1 to 11. Figures 4 to 11 are diagrams for explaining a specific example of the processing of the fare calculation device 100 in this embodiment.

[0040] [3-1. Overall processing] An overview of the overall processing of the control unit 102 of the fare calculation device 100 in this embodiment will be described with reference to Figure 4. Figure 4 is a diagram showing a flow for explaining an example of the overall processing of the control unit 102 of the fare calculation device 100 in this embodiment.

[0041] The master maintenance unit 102b executes a master registration process (step S1). Specifically, in the master registration process, the master maintenance unit 102b sets data for the freight generation condition master 106a and the freight unit price master 106b in response to an operation by an operator or the like on a master maintenance screen (not shown) displayed on the monitor 114, for example.

[0042] The small parcel freight calculation unit 102c executes the freight billing data creation process (step S2). Specifically, in the freight billing data creation process, the small parcel freight calculation unit 102c extracts sales data registered in the storage unit 106 according to extraction conditions specified by the operator's operation on the freight billing data creation process screen (see Figure 6) displayed on the monitor 114, for example, and for each sales number of the extracted sales data, it aggregates the reference values ​​for each definition code, compares the aggregated reference values ​​for each definition code with the freight generation condition master 106a, and creates small parcel freight billing data if even one definition code satisfies the small parcel freight generation condition.

[0043] [3-2. Sample data] 5 to 11 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the fare calculation device 100 in this embodiment. A specific example of the processing by the control unit 102 of the fare calculation device 100 in this embodiment will be explained with reference to FIGS. 5 to 11.

[0044] (S1: Master registration process) A specific example of the master registration process will be described with reference to Fig. 5. The master maintenance unit 102b sets data for the freight generation condition master 106a and the freight unit price master 106b in response to, for example, an operation by an operator or the like on a master maintenance screen (not shown) displayed on the monitor 114.

[0045] Figure 5(A) is a diagram showing the settings and determination method of the freight generation condition master 106a. The small parcel freight calculation unit 102c holds the data shown in Figure 5(A) and uses it when determining whether or not small parcel freight will be incurred in the freight generation condition master 106a.

[0046] In the example shown in the figure, the first line has definition code "100," key item 1 "subcategory of products," reference value "subcategory of products base quantity," and judgment method "subcategory of products base quantity > sales number + quantity of sales data aggregated by key item," the second line has definition code "200," key item 1 "customer," key item 2 "delivery destination," reference value "customer base quantity," and judgment method "customer base quantity > sales number + quantity of sales data aggregated by key item," and the third line has definition code "300," key item 1 "customer," key item 2 "delivery destination," key item 3 "subcategory of products," and judgment method "key items match by sales number."

[0047] The fourth line has definition code "400", key item 1 "subcategory of product", reference value "subcategory of product standard amount", and judgment method "subcategory of product standard amount > sales number + amount of sales data aggregated using key item". The fifth line has definition code "500", key item 1 "supplier", key item 2 "subcategory of product", reference value "supplier standard amount", and judgment method "supplier standard amount > sales number + amount of sales data aggregated using key item".

[0048] Figure 5(B) is a diagram showing an example of the settings for the freight generating condition master 106a. The freight generating condition master 106a is a master that sets the conditions for generating small-lot freight, and can be composed of a table that associates and registers definition codes, key items 1, 2, and 3, and reference values. Key items may include one or more of the following: product subcategory (e.g., solvents, preservatives, etc.), customer, delivery destination, and supplier. The reference value is the actual value of the "reference value" specified in Figure 5(A) using the definition code as a key. If the condition of the "determination method" specified in Figure 5(A) is met, it is determined that small-lot freight is incurred. In this example, there are three key items, but there may be more or fewer.

[0049] In the example shown in the figure, the first line has definition code "100," key item 1 "preservative," and reference value "10," the second line has definition code "100," key item 1 "solvent," and reference value "15," and the third line has definition code "200," key item 1 "Customer A," key item 2 "Delivery destination A," and reference value "13."

[0050] The fourth line has definition code "200", key item 1 "Customer A", key item 2 "Delivery destination A", and base value "30". The fifth line has definition code "300", key item 1 "Customer A", key item 2 "Delivery destination A", and key item 3 "Solvent". The sixth line has definition code "400", key item 1 "Preservative", and base value "1000". The seventh line has definition code "500", key item 1 "Supplier A", key item 1 "Solvent", and base value "2000".

[0051] (S2: fare data creation process) A specific example of the freight data creation process will be described with reference to Figures 6 to 11. The small parcel freight calculation unit 102c extracts sales data registered in the storage unit 106 according to extraction conditions specified by the operator's operation on the freight billing data creation processing screen (see Figure 6) displayed on the monitor 114, for example, and aggregates the reference values ​​for each definition code for each sales number in the extracted sales data. It compares the aggregated reference values ​​for each definition code with the freight generation condition master 106a, and creates small parcel freight billing data if even one definition code satisfies the small parcel freight generation condition.

[0052] 6 is a diagram showing an example of the display of the freight billing data creation processing screen 400. The freight billing data creation processing screen 400 includes fields for specifying extraction conditions such as the base date (the current date is automatically set), business establishment, billing closing date, closing date, and billing recipient, as well as a search button, a cancel button, and a register button. When the operator specifies the extraction conditions of the business establishment, billing closing date, closing date, and billing recipient and presses the search button, sales data registered in the storage unit 106 is extracted according to the extraction conditions, small parcel freight billing data is created for the extracted sales data, and when the register button is pressed, the created small parcel freight billing data is registered in the storage unit 106.

[0053] In the example shown in the figure, the extraction conditions specified are the base date "2024 / 2 / 2", business establishment "ZG001 Business establishment A", billing closing date "2024 / 02 / 29", closing date "31", and billing destination "Billing destination A". Below, we will explain the processing when these extraction conditions are specified as an example.

[0054] 7 is a diagram showing an example of sales data. The sales data has the following fields: sales number, row, sales date, business establishment, supplier, billing destination, customer, delivery destination, delivery company, product, product subcategory, quantity (units), sales price, and sales amount. In the example shown in the figure, the first row has sales number "U001," row "1," sales date "2024 / 2 / 10," business establishment "Business A," supplier "Supplier A," billing destination "Billing Destination A," customer "Customer A," delivery destination "Delivery Destination A," delivery company "Delivery Company A," product "Product A," product subcategory "Preservative," quantity (units) "5," sales price "300," and sales amount "1500."

[0055] (2)-1: Target data is extracted from the sales data according to the extraction conditions on the freight billing data creation processing screen 400. Figure 8 shows an example of extracted sales data. Lines 6 to 8 are not extracted because the billing destination is different. Lines 9 and 10 are not extracted because the sales date is after the billing closing date on the screen.

[0056] (2)-2: The quantity / amount is tallied for each sales number and definition code of the freight generation condition master 106a. Figure 9 shows an example of the sales data after the talliation.

[0057] (2)-3: Compare the results of the aggregation in (2)-2 with the freight generating condition master 106a, and if any of the conditions for the small parcel freight generation are met, create small parcel freight billing data. Figure 10(A) is a diagram showing an example of data from the freight generating condition master 106a. For comparison, Figure 10(B) is a diagram in which the reference numerical values ​​from the freight generating condition master 106a have been added to the aggregated sales data of Figure 9(B). The reference quantities of the freight generating condition master 106a shown in Figure 10(A) are as follows: lines 1 to 4 show the quantity, line 5 has no numerical value set, and lines 6 and 7 show the amount (see Figure 5(A)).

[0058] As shown in Figure 10 (B), for the sales data after aggregation, small parcel freight billing data is created for sales number "U0001" because it meets the conditions of definition codes "100" and "200." For sales number "U0001" in the first line, small parcel freight billing data is created because it meets the conditions of definition codes "100" and "200." For sales number "U0002" in the second line, small parcel freight billing data is created because it meets the condition of definition code "300." For sales number "U0003" in the third line, small parcel freight billing data is created because it meets the condition of definition code "500." For sales number "U0004" in the fourth line, small parcel freight billing data is not created because it does not meet the conditions of the definition code.

[0059] (2)-4: Create small lot freight billing data based on the results obtained in (2)-3 (the freight amount is calculated by multiplying the quantity by the freight unit price in the freight unit price master 106b).

[0060] 11(A) is a diagram showing an example of data in the freight unit price master 106b. The freight unit price master 106b is a master that sets the unit price of small parcel freight, and includes fields for delivery company, supplier, warehouse, delivery destination, application start date, application end date, and freight unit price. In the example shown in the figure, the first line contains the delivery company "Delivery Company A," the supplier "Supplier A," the delivery destination "Delivery Destination A," the start date of application "2024 / 2 / 1," the end date of application "2024 / 2 / 29," and the freight unit price "50."

[0061] Figure 11(B) is a diagram showing an example of the created small parcel freight billing data. The small parcel freight billing data has the following fields: small parcel freight billing number, line, sales date, customer, expense item, quantity (units), freight unit price (unit sales price), and freight amount (sales amount). The "freight unit price" is obtained from the freight unit price master 106b using the supplier and delivery destination as keys. The "freight amount" is calculated by multiplying the quantity by the obtained freight unit price. In the example shown in the figure, the first line contains the small parcel freight billing number "SNY001," line "1," sales date "2024 / 2 / 12," customer "Customer A," expense item "small parcel freight," quantity (units) "5," freight unit price "50," and freight amount "250."

[0062] As explained above, according to this embodiment, the system is equipped with a freight generation condition master 106a in which one or more key items, quantity or amount standard values ​​are associated with each definition that specifies the petty freight generation conditions and registered, and a petty freight calculation unit 102c which extracts sales data registered in the memory unit 106 according to the extraction conditions, aggregates the standard values ​​for each definition in the freight generation condition master 106a for each sales number of the extracted sales data, compares the aggregated standard values ​​for each definition with the freight generation condition master 106a, and creates petty freight billing data if even one definition meets the petty freight generation conditions, making it possible to accurately determine whether or not petty freight will be incurred.

[0063] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

[0064] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0065] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0066] 5. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0067] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0068] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0069] Furthermore, with regard to the fare calculation device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0070] For example, all or any part of the processing functions of the fare calculation device 100, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the fare calculation device 100 as needed. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to issue instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to form the control unit.

[0071] In addition, this computer program may be stored in an application program server connected to the fare calculation device 100 via any network, and all or part of it may be downloaded as needed.

[0072] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0073] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0074] The various databases stored in the memory unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0075] The fare calculation device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as an information processing device connected to any peripheral device. The fare calculation device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform the processing described in this embodiment.

[0076] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]

[0077] 100 Fare calculation device 102 Control section 102a Data Registration Section 102b Master Maintenance Department 102c Small-lot Fare Calculation Department 102d Screen display control unit 104 Communication interface unit 106 Storage section 106a Freight generation condition master 106b Freight unit price master 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A fare calculation device that includes a control unit and calculates small-lot fares, The control unit A freight generation condition master in which one or more key items, quantity or amount reference values ​​are associated and registered for each definition that specifies the small freight generation condition; Sales data including sales number, sales date, supplier, billing address, customer, delivery address, product, product subcategory, quantity, sales price, and sales amount; It is configured to be accessible to A freight calculation device characterized by comprising a small parcel freight calculation means that extracts the sales data in accordance with extraction conditions, aggregates the standard values ​​for each definition in the freight generation condition master for each sales number in the extracted sales data, compares the aggregated standard values ​​for each definition with the freight generation condition master, and creates small parcel freight billing data if even one definition meets the small parcel freight generation condition.

2. The control unit It is configured to be accessible to the freight unit price master that registers the freight unit prices for small parcels.

2. The freight calculation device according to claim 1, wherein the small lot freight billing data includes a freight amount obtained by multiplying the quantity, which is a reference value for each aggregated definition code, by the freight unit price in the freight unit price master.

3. 2. The freight calculation device according to claim 1, wherein key items of the freight generating condition master include one or more of product subcategory, customer, delivery destination, and supplier.

4. 4. The fare calculation device according to claim 1, wherein the data of the fare generation condition master can be set by an operator.

5. A fare calculation method executed by an information processing device equipped with a control unit, The control unit A freight generation condition master in which one or more key items, quantity or amount reference values ​​are associated and registered for each definition that specifies the small freight generation condition; Sales data including sales number, sales date, supplier, billing address, customer, delivery address, product, product subcategory, quantity, sales price, and sales amount; It is configured to be accessible to The control unit executes A freight calculation method characterized by including a small parcel freight calculation step of extracting the sales data in accordance with extraction conditions, aggregating the standard values ​​for each definition in the freight generation condition master for each sales number in the extracted sales data, comparing the aggregated standard values ​​for each definition with the freight generation condition master, and creating small parcel freight billing data if even one definition meets the small parcel freight generation condition.

6. A fare calculation program to be executed by an information processing device having a control unit, The control unit A freight generation condition master in which one or more key items, quantity or amount reference values ​​are associated and registered for each definition that specifies the small freight generation condition; Sales data including sales number, sales date, supplier, billing address, customer, delivery address, product, product subcategory, quantity, sales price, and sales amount; It is configured to be accessible to The control unit A freight calculation program for extracting the sales data in accordance with extraction conditions, aggregating the standard values ​​for each definition of the freight generation condition master for each sales number of the extracted sales data, comparing the aggregated standard values ​​for each definition with the freight generation condition master, and executing a small parcel freight calculation process to create small parcel freight billing data if even one definition meets the small parcel freight generation condition.

Images