Fuel oil sales unit price management device, fuel oil sales unit price management method, and fuel oil sales unit price management program

Abstract

To provide a device, method, and program for managing fuel oil sales unit price, which allow for automatically compute customer sales unit prices by registering a unit price increase or decrease for each customer using a market unit price for each region announced by the Agency for Natural Resources and Energy every week as a standard unit price.SOLUTION: A unit price difference representing a difference between a sales unit price and a market unit price of a sales product for each client is obtained to derive a sales unit price of the sales product for each client based on a client master, market unit price master, sales data, and unit price differences.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a fuel oil sales unit price management device, a fuel oil sales unit price management method, and a fuel oil sales unit price management program. [Background technology]

[0002] Patent Document 1 discloses a configuration in which, when leasing or renting a car for a price that includes the price of gasoline, the monthly fuel supply price is calculated by multiplying the fuel price held by the Agency for Natural Resources and Energy at the time the contract begins by the monthly fuel supply amount, and the difference between the monthly fuel supply price and the estimated monthly fuel cost is refunded to the fuel wholesaler or fuel retailer. [Prior art documents] [Patent documents]

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

[0004] However, in the invention described in Patent Document 1, a monthly fuel unit price is used to calculate the fuel supply price for that month, which poses a problem in that it is not possible to set a sales unit price that corresponds to fluctuations in market unit prices for fuel oil transactions that occur each time due to fluctuations in crude oil prices.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a fuel oil sales price management device, a fuel oil sales price management method, and a fuel oil sales price management program that can register unit price increases or decreases for each customer using the market unit price for each region announced weekly by the Agency for Natural Resources and Energy as the base unit price, and automatically calculate the customer sales price. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the objective, the fuel oil sales unit price management device of the present invention is a fuel oil sales unit price management device equipped with a memory unit and a control unit, wherein the memory unit comprises: a customer memory means for storing a customer master set by linking the customer's region and the week within the month in which the unit price for fuel oil transactions is used; a market unit price means for storing a market unit price master set by linking the fuel oil product type, the region, the market unit price of the fuel oil, and the week; and a sales memory means for storing sales data set by linking the customer, sales date, sold product, and sales quantity, and the control unit comprises: a unit price difference acquisition means for acquiring the unit price difference, which is the difference between the sales unit price of the product sold to the customer and the market unit price, and a sales price acquisition means for acquiring the sales unit price of the product sold for each customer based on the customer master, the market unit price master, the sales data, and the unit price difference.

[0007] In addition, in the fuel oil sales price management device of the present invention, the control unit is characterized by further comprising a sales amount acquisition means for acquiring the sales amount of the sold product to the business partner based on the sales data and the sales price.

[0008] In addition, in the fuel oil sales price management device of the present invention, the sales amount acquisition means is further characterized by displaying sales price simulation table data that sets the sales department, the customer, the sales date, the sold product, the sales quantity, and the sales amount.

[0009] In addition, in the fuel oil sales price management device of the present invention, the sales amount acquisition means is further characterized in that it displays the monthly total sales quantity and monthly total sales amount of each sales product for each sales department based on the sales price simulation table data.

[0010] In addition, in the fuel oil sales unit price management device of the present invention, the unit price difference acquisition means is further characterized in that when the unit price difference of the product sold to the business partner is input, the unit price difference and a record setting an approval status of unapproved are set in the unit price application approval master.

[0011] In addition, in the fuel oil sales unit price management device of the present invention, the unit price difference acquisition means is further characterized in that, when an approval instruction for the unit price difference is input, the approval status of the record set in the unit price application approval master is updated from unapproved to approved.

[0012] In addition, in the fuel oil sales price management device of the present invention, the sales price acquisition means acquires the sales price of the sold product for each customer by adding the unit price difference to the market unit price of the customer's region for the week set in the customer master for the month including the sales date, based on the customer master, the market unit price master, the sales data, and the unit price difference.

[0013] In addition, the fuel oil sales unit price management method of the present invention is a fuel oil sales unit price management method to be executed by a fuel oil sales unit price management device having a memory unit and a control unit, wherein the memory unit comprises a customer memory means for storing a customer master set by linking the customer's region and the week within the month in which the unit price for fuel oil transactions is used, a market unit price means for storing a market unit price master set by linking the fuel oil product type, the region, the market unit price of the fuel oil, and the week, and a sales memory means for storing sales data set by linking the customer, sales date, sold product, and sales quantity, and is characterized by including: a unit price difference acquisition step executed by the control unit, which acquires a unit price difference, which is the difference between the sales unit price of the product sold to the customer and the market unit price, and a sales price acquisition step for acquiring the sales unit price of the product sold for each customer based on the customer master, the market unit price master, the sales data, and the unit price difference.

[0014] In addition, the fuel oil sales unit price management program of the present invention is a fuel oil sales unit price management program to be executed by a fuel oil sales unit price management device having a memory unit and a control unit, wherein the memory unit comprises a trading partner memory means for storing a trading partner master set by linking the trading partner's region and the week within the month in which the unit price for fuel oil transactions is used, a market unit price means for storing a market unit price master set by linking the fuel oil product type, the region, the market unit price of the fuel oil, and the week, and a sales memory means for storing sales data set by linking the trading partner, sales date, sold product, and sales quantity, and is characterized in that the control unit executes a unit price difference acquisition step for acquiring a unit price difference, which is the difference between the sales unit price of the product sold to the trading partner and the market unit price, and a sales unit price acquisition step for acquiring the sales unit price of the product sold for each trading partner based on the trading partner master, the market unit price master, the sales data, and the unit price difference. [Effects of the Invention]

[0015] The present invention provides the following advantages: By automatically calculating unit prices, the efficiency of the decision-making process is improved, time is saved, and sales results can be confirmed in real time after unit prices are determined. Furthermore, the present invention enables unit price strategies for the following month, whereas previously, department managers could only determine unit prices for the following month based on sales results. This allows instructions to be given to sales representatives one month earlier, thereby enabling earlier management decisions. The present invention also provides the advantage of multiplying sales volume by the latest master unit price to calculate sales results on a report and displaying them by department. The present invention also provides the advantage of providing a system that can reflect forecast unit prices in addition to the unit prices announced by the Agency for Natural Resources and Energy. Furthermore, in businesses that are dependent on market unit prices, such as fuel oil, sales results could only be tracked by volume until the closing date. However, the present invention provides the advantage of reflecting market unit prices in sales results in a timely manner, thereby enabling early understanding of sales results on a monetary basis. Furthermore, according to the present invention, it is possible to grasp actual sales results using the latest sales unit price, which is the latest market unit price plus the increase / decrease in the wholesale unit price determined by the sales department relative to the market unit price, based on the latest market unit price information and the increase / decrease in the wholesale unit price. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 is a diagram showing an example of conventional fuel oil sales management. [Figure 2] FIG. 2 is a diagram showing an example of fuel oil sales management in this embodiment. [Figure 3] FIG. 3 is a block diagram showing an example of the configuration of a fuel oil sales unit price management device in this embodiment. [Figure 4] FIG. 4 is a diagram showing an example of supplier master settings in this embodiment. [Figure 5] FIG. 5 is a diagram showing an example of sales registration in this embodiment. [Figure 6] FIG. 6 is a flowchart showing an example of the processing of the fuel oil sales price management device in this embodiment. [Figure 7]FIG. 7 is a diagram showing an example of the fuel oil sales unit price management process in this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of the fuel oil sales unit price management process in this embodiment. [Figure 9] FIG. 9 is a diagram showing an example of the fuel oil sales price management process in this embodiment. [Figure 10] FIG. 10 is a diagram showing an example of the fuel oil sales price management process in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0017] 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.

[0018] [1. Overview] First, an overview of the present invention will be described with reference to Figures 1 and 2. Figure 1 is a diagram showing an example of conventional fuel oil sales management. Figure 2 is a diagram showing an example of fuel oil sales management in this embodiment.

[0019] In the oil industry, fluctuations in crude oil prices cause unit prices for fuel oil transactions to change on a regular basis. In the past, in credit sales transactions, unit prices were often determined after the transaction, and when registering sales data, provisional registration was made at the previous unit price, and sales were recalculated at the latest unit price after the unit price was determined. As a result, in the past, sales results could not be captured as accurate figures until the recalculation.

[0020] For example, as shown in Figure 1, in the past, when the unit price was not yet determined, provisional sales amounts (sales data) calculated using the previous month's unit price were registered, and the final sales recalculation was performed at the beginning of the following month.As a result, during the period leading up to the sales recalculation, actual sales could only be captured using provisional sales amounts calculated using the previous month's unit price.

[0021] Therefore, in this embodiment, the unit price increase / decrease amount managed on a base date for each customer is registered in a master, the market unit price for each region announced weekly by the Agency for Natural Resources and Energy is taken in as the base unit price, the sales unit price is automatically calculated from the base unit price and the unit price increase / decrease amount, and the sales quantity is multiplied by the latest unit price to display sales results by department.

[0022] For example, as shown in Fig. 2, in this embodiment, the process of determining unit prices is automated, thereby improving work efficiency and reducing time, and making it possible to check actual sales on a ledger without waiting for sales to be recalculated. In this way, in this embodiment, unit price calculation is automated, and even before sales are recalculated, actual sales based on the latest calculated unit price are output on a ledger, making it possible to quickly check accurate actual sales.

[0023] [2. Configuration] An example of the configuration of the fuel oil unit sales price management device 100 according to this embodiment will be described with reference to Fig. 3 to Fig. 5. Fig. 3 is a block diagram showing an example of the configuration of the fuel oil unit sales price management device 100 according to this embodiment.

[0024] 3, the fuel oil sales unit price management device 100 is a commercially available desktop personal computer. Note that the fuel oil sales unit price management device 100 is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0025] The fuel oil sales price management 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 fuel oil sales price management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0026] The communication interface unit 104 communicably connects the fuel oil sales price management 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 fuel oil sales price management 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).

[0027] 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.

[0028] The memory unit 106 stores various databases, tables, files, etc. The memory unit 106 stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The memory unit 106 may be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The memory unit 106 includes a supplier master 106a, a market unit price master 106b, a unit price application approval master 106c, a sales database 106d, and a supplier unit price master 106e.

[0029] The supplier master 106a is a master set by linking the region of the supplier (customer) and the week of the month in which the unit price of the fuel oil transaction is adopted. Here, the supplier master 106a may be set by linking the supplier (customer), region, and / or week number indicating the week of the month in which the unit price of the fuel oil transaction is adopted.

[0030] The market unit price master 106b is a master set by linking the fuel oil product type, region, market unit price of fuel oil, and the week of the month in which the unit price of fuel oil trading is adopted. Here, the market unit price master 106b may be set by linking the product, application start date, region, market unit price, and / or week number indicating the week of the month in which the unit price of fuel oil trading is adopted.

[0031] The unit price application approval master 106c is a master that is set by linking the unit price difference, which is the difference between the sales unit price of the product sold to the supplier and the market unit price, and the approval status. Here, the unit price application approval master 106c may be set by linking the supplier (customer), application start date, product, unit price difference, and / or approval status.

[0032] The sales database 106d stores sales data. Here, the sales database 106d may store sales data that is set by linking together business partners, sales dates, sold products, and sales quantities. The sales database 106d may also store sales data that is set by linking together sales departments, business partners (customers), sales dates, sold products, sales quantities, sales prices, and / or sales amounts.

[0033] The supplier unit price master 106e is a master that associates supplier (customer), product, application start date, sales unit price, region, week number, market unit price, and / or unit price difference.

[0034] The control unit 102 is a CPU or the like that comprehensively controls the fuel oil sales unit price management 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. Functionally, the control unit 102 conceptually includes a master setting unit 102a, a unit price difference acquisition unit 102b, a sales unit price acquisition unit 102c, and a sales amount acquisition unit 102d.

[0035] The master setting unit 102a sets the master. When data setting the region and week number of a customer is input, the master setting unit 102a may set a record corresponding to the data in the customer master 106a. Furthermore, when the master setting unit 102a downloads the results of a petroleum product price survey from the Agency for Natural Resources and Energy, it may set a record corresponding to the survey results in the market unit price master 106b. Furthermore, the master setting unit 102a may register sales data in the sales database 106d based on sales registrations from each department.

[0036] An example of supplier master settings in this embodiment will now be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of supplier master settings in this embodiment.

[0037] As shown in FIG. 4, the master setting unit 102a may set a record in which the region and the week number for which the unit price is adopted are set in the supplier master (customer master) 106a.

[0038] An example of sales registration in this embodiment will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of sales registration in this embodiment.

[0039] 5, the master setting unit 102a may register sales data for each product for each business partner (customer) based on sales registration from each department during daily business operations. Here, the unit sales price and sales amount in the sales data in this embodiment may be the unit sales price and sales amount existing at the time of registration.

[0040] Returning to FIG. 3, the unit price difference acquisition unit 102b acquires the unit price difference, which is the difference between the sales unit price of the product sold to the business partner and the market unit price. Here, when the unit price difference acquisition unit 102b receives an input of the unit price difference of the product sold to the business partner, the unit price difference acquisition unit 102b may set a record in the unit price request approval master 106c that sets the unit price difference and an approval status of "unapproved." Furthermore, when an approval instruction for the unit price difference is input, the unit price difference acquisition unit 102b may update the approval status of the record set in the unit price request approval master 106c from "unapproved" to "approved."

[0041] The unit sales price acquisition unit 102c acquires the unit sales price of the product sold for each supplier based on the supplier master data 106a, the market unit price master data 106b, the sales data, and the unit price difference. Here, the unit sales price acquisition unit 102c may acquire the unit sales price of the product sold for each supplier based on the supplier master data 106a, the market unit price master data 106b, the sales data, and the unit price difference. Furthermore, the unit sales price acquisition unit 102c may acquire the unit sales price of the product sold for each supplier based on the supplier master data 106a, the market unit price master data 106b, the sales data, and the unit price difference by adding the unit price difference to the market unit price for the supplier's region for the week set in the supplier master data 106a for the month (or monthly period) including the sales date. Furthermore, the unit sales price acquisition unit 102c may update the sales data stored in the sales database 106d with the acquired unit sales price of the product sold.

[0042] The sales amount obtaining unit 102d obtains the sales amount of the products sold to the customer based on the sales data and the unit sales price. Here, the sales amount obtaining unit 102d may obtain the sales amount of the products sold to the customer based on the sales data and the unit sales price. The sales amount obtaining unit 102d may also display unit sales price simulation table data that sets the sales department, customer, sales date, products sold, sales quantity, and sales amount. The sales amount obtaining unit 102d may also display the monthly total sales quantity and monthly total sales amount of each product sold for each sales department based on the unit sales price simulation table data. The sales amount obtaining unit 102d may also update the sales data stored in the sales database 106d with the obtained sales amounts of the products sold.

[0043] [3. Specific Examples] A specific example of this embodiment will be described with reference to FIGS.

[0044] [Fuel oil sales unit price management processing] An example of fuel oil sales unit price management processing in this embodiment will now be described with reference to Fig. 6. Fig. 6 is a flowchart showing an example of processing by the fuel oil sales unit price management device 100 in this embodiment.

[0045] 6, when a sales record is made in each field department, the master setting unit 102a registers the sales data in the sales database 106d by linking the sales department, the customer, the sales date, the sold product, and the sales quantity (step SA-1). For example, in this embodiment, the sales data may be registered in each department.

[0046] Then, when a sales representative inputs a unit price difference, which is the difference between the sales unit price of the product sold to a business partner and the market unit price, via the input device 112, the unit price difference acquisition unit 102b sets a record in which the unit price difference and an approval status of "unapproved" are set in the unit price application approval master 106c (step SA-2). For example, in this embodiment, a sales representative may register and apply for a unit price difference, which is the difference from the market unit price, for each customer.

[0047] Then, when the sales manager inputs an approval instruction for the unit price difference via the input device 112, the unit price difference acquisition unit 102b updates the approval status of the record set in the unit price application approval master 106c from unapproved to approved (step SA-3). For example, in this embodiment, the sales manager may approve the application content.

[0048] Then, when the master setting unit 102a downloads the results of the petroleum product price survey published weekly by the Agency for Natural Resources and Energy, it sets a record corresponding to the survey results in the market unit price master 106b (step SA-4). For example, in this embodiment, a list of the survey results of the petroleum product price survey published weekly by the Agency for Natural Resources and Energy may be downloaded, and the market unit prices may be acquired.

[0049] Then, based on the sales data and unit price difference stored in the supplier master 106a, the market unit price master 106b, and the sales database 106d, the sales unit price acquisition unit 102c acquires the sales unit price of the product sold for each supplier by adding the unit price difference to the market unit price for the supplier's region for the week having the week number set in the supplier master 106a for the month including the sales date (step SA-5). For example, in this embodiment, the unit price for each customer may be calculated from the unit price difference and the market unit price in the customer unit price calculation process.

[0050] Then, the sales amount acquisition unit 102d acquires the sales amount of the product sold to the business partner based on the sales quantity stored in the sales database 106d and the sales unit price of the product acquired by the sales unit price acquisition unit 102c (step SA-6).

[0051] The sales amount obtaining unit 102d then displays on the output device 114 the sales price simulation table data, which sets the sales department, customer, sales date, sales item, sales quantity, and sales amount, and further displays on the output device 114 the monthly sales performance data, which sets the sales department, sales month, sales item, and monthly total sales quantity and monthly total sales amount of each sales item for each sales department, based on the sales price simulation table data (step SA-7), and then ends the processing. For example, in this embodiment, the sales performance for each department may be confirmed by multiplying the sales quantity by the latest unit price.

[0052] An example of the fuel oil sales unit price management process in this embodiment will now be described with reference to Figures 7 to 10. Figures 7 to 10 are diagrams showing an example of the fuel oil sales unit price management process in this embodiment.

[0053] As shown in FIG. 7, in this embodiment, when a sales representative registers the unit price difference (unit price increase / decrease) for a product for each customer, the unit price difference and the approval status of "unapproved" are set in the unit price application approval master 106c (step SB-1).

[0054] Then, as shown in FIG. 7, in this embodiment, if the superior checks and approves the application content, the approval status set in the unit price application approval master 106c is updated from unapproved to approved (step SB-2).

[0055] As shown in Figure 8, in this embodiment, as a market unit price import process, Excel (registered trademark) data of the list of survey results of the petroleum product price survey downloaded from the website of the Agency for Natural Resources and Energy is imported, and the market unit price master 106b is updated (step SB-3).

[0056] As shown in FIG. 9, in this embodiment, in calculating the customer unit price, the customer unit price (sales price) is calculated based on the conditions in the supplier master 106a, the market unit price master 106b, and the unit price difference (step SB-4).

[0057] 10, in this embodiment, the sales amount is calculated from the latest unit price in the unit price simulation table and is compiled by department, and a sales performance report at the latest unit price is output (step SB-5). That is, in this embodiment, in the unit sales price simulation spreadsheet step (1), the market unit price is reacquired from the master and the sales amount is recalculated, and in the unit sales price simulation spreadsheet step (2), the details calculated in the unit sales price simulation spreadsheet step (1) may be compiled by month, by department, and by product.

[0058] [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.

[0059] 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.

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

[0061] 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.

[0062] 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.

[0063] 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.

[0064] Furthermore, with regard to the fuel oil sales price management 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.

[0065] For example, all or any part of the processing functions of the fuel oil sales price management 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 an information processing device to execute the processes described in this embodiment, and is mechanically read by the fuel oil sales price management device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). The computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0066] In addition, this computer program may be stored in an application program server connected to the fuel oil sales price management device 100 via any network, and all or part of it may be downloaded as needed.

[0067] 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.

[0068] 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.

[0069] 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.

[0070] The fuel oil sales price management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device connected to any peripheral device. The fuel oil sales price management device 100 may be realized by installing software (including programs or data) that causes the device to perform the processing described in this embodiment.

[0071] 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. [Industrial Applicability]

[0072] The present invention is useful in the petroleum industry, which handles fuel oil. [Explanation of symbols]

[0073] 100 Fuel oil sales unit price management device 102 Control section 102a Master setting section 102b Unit Price Difference Acquisition Department 102c Sales Unit Price Acquisition Department 102d Sales Amount Acquisition Section 104 Communication interface unit 106 Storage section 106a Customer Master 106b Market Price Master 106c Unit Price Application Approval Master 106d Sales Database 106e Customer Unit Price Master 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A fuel oil sales price management device having a memory unit and a control unit, The storage unit is A supplier storage means for storing a supplier master set by linking the supplier's region with the week in the month in which the unit price of fuel oil transactions is adopted; a market unit price means for storing a market unit price master set by linking the product type of fuel oil, the region, the market unit price of the fuel oil, and the week; a sales storage means for storing sales data that is set by linking the business partner, the sales date, the sold product, and the sales quantity; Equipped with The control unit is a unit price difference acquisition means for acquiring a unit price difference when a unit price difference between the sales unit price of the product sold to the trading partner and the market unit price is input; a sales unit price acquisition means for acquiring the sales unit price of the sold item for each of the suppliers by adding the unit price difference to the market unit price of the region of the supplier for the week set in the supplier master for the month including the sales date, based on the supplier master, the market unit price master, the sales data, and the unit price difference; A fuel oil sales price management device comprising:

2. The control unit is a sales amount acquisition means for acquiring the sales amount of the product to the business partner based on the sales data and the unit price of the product; The fuel oil sales price management device according to claim 1, further comprising:

3. The sales amount acquisition means is The fuel oil sales price management device as described in claim 2, characterized in that the sales amount is calculated by multiplying the sales quantity by the sales price which is the latest unit price, and displays sales price simulation table data which sets the sales department, the client, the sales date, the sold product, the sales quantity, and the sales amount.

4. The sales amount acquisition means is The fuel oil sales price management device as described in claim 3, further characterized in that it displays the monthly total sales quantity and monthly total sales amount of each sales product for each sales department based on the sales price simulation table data.

5. The unit price difference acquisition means A fuel oil sales unit price management device as described in any one of claims 1 to 4, further characterized in that when the unit price difference of the product sold to the business partner is input, a record setting the unit price difference and an approval status of unapproved is set in the unit price application approval master.

6. The unit price difference acquisition means The fuel oil sales unit price management device as described in claim 5, further characterized in that when an approval instruction for the unit price difference is input, the approval status of the record set in the unit price application approval master is updated from unapproved to approved.

7. A fuel oil sales unit price management method to be executed by a fuel oil sales unit price management device having a memory unit and a control unit, The storage unit is A supplier storage means for storing a supplier master set by linking the supplier's region with the week in the month in which the unit price of fuel oil transactions is adopted; a market unit price means for storing a market unit price master set by linking the product type of fuel oil, the region, the market unit price of the fuel oil, and the week; a sales storage means for storing sales data that is set by linking the business partner, the sales date, the sold product, and the sales quantity; Equipped with The control unit executes a unit price difference acquisition step of acquiring a unit price difference when a unit price difference between the sales unit price of the product sold to the trading partner and the market unit price is input; a sales unit price acquisition step of acquiring the sales unit price of the sold product for each of the suppliers by adding the unit price difference to the market unit price of the region of the supplier for the week set in the supplier master for the month including the sales date, based on the supplier master, the market unit price master, the sales data, and the unit price difference; A method for managing fuel oil sales prices, comprising:

8. A fuel oil sales unit price management program to be executed by a fuel oil sales unit price management device having a memory unit and a control unit, The storage unit is A supplier storage means for storing a supplier master set by linking the supplier's region with the week in the month in which the unit price of fuel oil transactions is adopted; a market unit price means for storing a market unit price master set by linking the product type of fuel oil, the region, the market unit price of the fuel oil, and the week; a sales storage means for storing sales data that is set by linking the business partner, the sales date, the sold product, and the sales quantity; Equipped with In the control unit, a unit price difference acquisition step of acquiring a unit price difference when a unit price difference between the sales unit price of the product sold to the trading partner and the market unit price is input; a sales unit price acquisition step of acquiring the sales unit price of the sold product for each of the suppliers by adding the unit price difference to the market unit price of the region of the supplier for the week set in the supplier master for the month including the sales date, based on the supplier master, the market unit price master, the sales data, and the unit price difference; A fuel oil sales price management program to implement the above.

Images