JP7240537B2 - Channel-based revenue management device, channel-based revenue management method, and channel-based revenue management program - Google Patents

Description

The present invention relates to a channel-based revenue management device, a channel-based revenue management method, and a channel-based revenue management program.

Patent Literature 1 discloses a configuration in which a warehouse group obtained by grouping a plurality of existing warehouses is regarded as a logical warehouse, and inventory management is executed for each logical warehouse by allocating products for each logical warehouse.

JP-A-2000-215254

However, in the invention described in Patent Document 1, the profit of the company can be managed, but the profit of each distribution channel cannot be managed. was not numerically understood.

The present invention has been made in view of the above problems, and is a channel-by-channel profit management device that enables inventory management by channel by creating a logical warehouse for each distribution channel in a physical warehouse. It is an object of the present invention to provide a channel-based revenue management method and a channel-based revenue management program.

In order to solve the above-described problems and achieve the object, a channel-based revenue management device according to the present invention is a channel-based revenue management device comprising a storage unit and a control unit, wherein the storage unit is a physical warehouse. warehouse storage means for storing a warehouse master in which logical warehouses are set for each distribution channel set in each distribution channel; storage means, wherein the control unit stores purchase acquisition means for acquiring purchase data including the purchase quantity of the product; a distribution means for calculating the distribution quantity of the product for each of the logical warehouses based on the distribution, and creating distributed inventory data by distributing the distribution quantity as the inventory quantity of the product in each of the logical warehouses. characterized by

Further, in the channel-by-channel profit management apparatus according to the present invention, the storage unit further includes order reception storage means for storing order reception data including the order quantity of the unallocated product for each of the logical warehouses, and In the fractional quantity calculation master, a variable relating to whether or not the order quantity is given priority is further set, and in the sorting means, when the variable is set to give priority to the order quantity, the purchase data, the Based on the warehouse master and the distribution quantity calculation master for each channel, the distribution quantity is calculated by distributing the difference quantity obtained by subtracting the order quantity from the purchase quantity to each of the logical warehouses, and calculating the distribution quantity and the distribution quantity The distribution stock data is created by allocating the sum of the order quantity and the quantity of goods ordered as the quantity of stock of the product in each of the logical warehouses.

Further, in the channel-by-channel revenue management apparatus according to the present invention, the control unit further includes sales acquisition means for acquiring sales data of the product for each logical warehouse.

Further, in the channel-based revenue management apparatus according to the present invention, the control unit further includes journal creation means for creating journal data for the product based on the purchase data, the apportioned inventory data, and the sales data. It is characterized by having

Further, in the channel-by-channel revenue management apparatus according to the present invention, the journal creation means further creates profit and loss statement data of the product for each logical warehouse.

Further, in the channel-by-channel revenue management apparatus according to the present invention, the allocation means assigns the allocation ratio to the purchase quantity based on the purchase data, the warehouse master, and the channel-by-channel allocation quantity calculation master. The multiplied distribution quantity for each of the logical warehouses is calculated, and the distributed inventory data is created by distributing the distribution quantity as the inventory quantity of the product in each of the logical warehouses.

Further, in the channel-by-channel profit management apparatus according to the present invention, when the variable is set to give priority to the order quantity, the allocation means includes the purchase data, the warehouse master, and the channel-by-channel allocation quantity calculation. Based on the master, the distribution quantity for each of the logical warehouses is calculated by multiplying the difference quantity by the distribution ratio, and the total of the distribution quantity and the order quantity is calculated as the inventory of the product in each logical warehouse. It is characterized in that the distribution stock data distributed in terms of quantity is created.

Further, in the channel-by-channel profit management device according to the present invention, the logical warehouse is a wholesale warehouse for indirect distribution channels via distributors, a directly managed warehouse for direct distribution channels at directly managed stores, and/or in electronic commerce. It is characterized by being an EC warehouse for direct distribution channels.

Further, a channel-based revenue management method according to the present invention is a channel-based revenue management method to be executed by a channel-based revenue management apparatus having a storage unit and a control unit, wherein the storage unit is set in a physical warehouse. warehouse storage means for storing a warehouse master in which logical warehouses are set for each distribution channel; and channel-by-channel allocation storage means for storing a channel-by-channel allocation quantity calculation master in which a product allocation ratio for each of the above-mentioned logical warehouses is set. and a purchase acquisition step of acquiring purchase data including the purchase quantity of the product, which is executed by the control unit; a distribution step of calculating the distributed quantity of the product for each of the logical warehouses based on the distribution, and creating distributed inventory data in which the distributed quantity is distributed as the inventory quantity of the product in each of the logical warehouses. It is characterized by

Further, a channel-based revenue management program according to the present invention is a channel-based revenue management program to be executed by a channel-based revenue management apparatus having a storage unit and a control unit, wherein the storage unit is set in a physical warehouse. warehouse storage means for storing a warehouse master in which logical warehouses are set for each distribution channel; and channel-by-channel allocation storage means for storing a channel-by-channel allocation quantity calculation master in which a product allocation ratio for each of the above-mentioned logical warehouses is set. and, in the control unit, a purchase acquisition step of acquiring purchase data including the purchase quantity of the product, and based on the purchase data, the warehouse master, and the distribution quantity calculation master for each channel and a sorting step of calculating the sorted quantity of the product for each of the logical warehouses and creating sorted inventory data in which the sorted quantity is sorted as the stock quantity of the product in each of the logical warehouses. characterized by

According to the present invention, the profit of each distribution channel can be managed, and it is possible to clarify which distribution channel has a good gross profit rate and which part should be improved or increased. play. In addition, according to the present invention, it is possible to automatically create a journal entry, so that there is an effect that speedy management decisions can be made.

FIG. 1 is a block diagram showing an example of the configuration of a revenue management device for each channel. FIG. 2 is a flow chart showing an example of processing of the revenue management device for each channel in this embodiment. FIG. 3 is a flowchart showing an example of revenue management processing by channel in this embodiment. FIG. 4 is a diagram showing an example of distributed inventory data in this embodiment. FIG. 5 is a diagram showing an example of journal data in this embodiment. FIG. 6 is a diagram showing an example of journal data in this embodiment. FIG. 7 is a diagram showing an example of journal data in this embodiment. FIG. 8 is a diagram showing an example of profit and loss statement data in this embodiment. FIG. 9 is a flowchart showing an example of revenue management processing by channel in this embodiment. FIG. 10 is a diagram showing an example of distributed inventory data in this embodiment. FIG. 11 is a diagram showing an example of journal data in this embodiment. FIG. 12 is a diagram showing an example of journal data in this embodiment. FIG. 13 is a diagram showing an example of journal data in this embodiment. FIG. 14 is a diagram showing an example of profit and loss statement data in this embodiment.

An embodiment of the present invention will be described in detail based on the drawings. In addition, this invention is not limited by this embodiment.

[1. composition]
An example of the configuration of the channel-by-channel profit management device 100 according to this embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of the revenue management device 100 for each channel.

The channel-based revenue management device 100 is a commercially available desktop personal computer. Note that the channel-specific revenue management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a commercially available notebook personal computer, PDA (Personal Digital Assistant), smart phone, tablet personal computer, or the like. It may be a portable information processing device.

The channel-by-channel profit management device 100 includes a control section 102 , a communication interface section 104 , a storage section 106 and an input/output interface section 108 . Each unit included in channel-based profit management apparatus 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 communicably connects the revenue management device 100 by channel 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 another device via a communication line. Here, the network 300 has a function of connecting the channel-based revenue management apparatus 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).

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for performing various processes by giving commands to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used. The storage unit 106 includes a warehouse master 106a, a purchase file 106b, a channel-by-channel distribution quantity calculation master 106c, an order file 106d, an inventory file 106e, a sales file 106f, and a journal file 106g.

The warehouse master 106a is a master in which logical warehouses are set for each distribution channel set in the physical warehouse. Here, the logical warehouse is a wholesale warehouse for indirect distribution channels through distributors, a directly managed warehouse for direct distribution channels at directly managed stores, and/or an EC (Electronic Commerce) for direct distribution channels in electronic commerce. It may be a warehouse or the like. Also, the physical warehouse may be a distribution warehouse or the like. The warehouse master 106a may include warehouse names and/or warehouse codes (CD) and the like.

The purchase file 106b stores purchase data. Here, purchase data includes purchase number, purchase date, supplier name, supplier code, purchase warehouse name, purchase warehouse code, product name, product code, purchase quantity, product unit price and/or Alternatively, the purchase price may be included.

The channel-by-channel distribution quantity calculation master 106c is a master in which the distribution ratio of products for each logical warehouse is set. Here, in the channel-by-channel allocation quantity calculation master 106c, a variable (unallocated priority flag) may be set as to whether or not to give priority to the order quantity of unallocated products for each logical warehouse. In addition, the channel-by-channel distribution quantity calculation master 106c includes distribution source (transfer source) warehouse name, distribution source (transfer source) warehouse code, distribution destination (transfer destination) warehouse name and/or distribution destination (transfer destination) ) may include a warehouse code or the like.

The order file 106d stores order data. Here, the order file 106d may store order data including order quantities of unallocated products for each logical warehouse. In addition, order data includes order number, order date, shipping (scheduled) date, (distribution destination) warehouse name, (distribution destination) warehouse code, customer name, customer code, delivery destination name, delivery destination code, Product name, product code, order quantity, unallocated quantity, product unit price and/or order amount may be included. Here, the sales amount may include tax-excluded amount, tax amount, and the like.

Inventory file 106e stores inventory data. Here, the inventory file 106e may store distributed inventory data of products for each logical warehouse. Here, sorted inventory data includes purchase number, purchase date, purchase warehouse (source warehouse) name, purchase warehouse (source warehouse) code, product name, product code, purchase quantity, and Destination warehouse name, distribution destination warehouse code, order (slip) number, line number, order date, shipment (scheduled) date, customer name, customer code, delivery destination name, delivery destination code, order quantity, product unit price , purchase amount and/or order amount.

The sales file 106f stores sales data. Here, the sales file 106f may store product sales data for each logical warehouse. In addition, the sales data includes sales date, customer name, customer code, shipping source (distribution destination) warehouse name, shipping source (distribution destination) warehouse code, product name, product code, sales quantity and/or sales amount. etc. may be included.

The journal file 106g stores journal data. Here, the journal file 106g may store journal data of products for each logical warehouse. Also, the journal file 106g may store profit and loss statement data of products for each logical warehouse.

An input device 112 and an output device 114 are connected to the input/output interface section 108 . The output device 114 can be a monitor (including a touch panel), a speaker, or a printer. The input device 112 can be a keyboard, a mouse, a microphone, or a monitor that cooperates with the mouse to provide a pointing device function. Note that, hereinafter, 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 .

The control unit 102 is a CPU or the like that controls the channel-by-channel revenue management apparatus 100 in an integrated manner. The control unit 102 has an internal memory for storing a control program such as an OS, a program defining various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Execute. The control unit 102 functionally conceptually includes a master setting unit 102a, a purchase acquisition unit 102b, an order acquisition unit 102c, an allocation unit 102d, a sales acquisition unit 102e, and a journal creation unit 102f. .

The master setting unit 102a sets a master. Here, the master setting unit 102a may set the warehouse master 106a. Also, the master setting unit 102a may set the allocation amount calculation master 106c for each channel.

The purchase acquisition unit 102b acquires purchase data. Here, the purchase acquisition unit 102b acquires purchase data including the purchase quantity of the product, supplier data, physical warehouse data for moving the product, and/or product data of the product, and stores the purchase data. may be stored in the purchase file 106b.

The order acquisition unit 102c acquires order data. Here, the order acquisition unit 102c includes order quantity of products for each logical warehouse, customer data for each logical warehouse, distribution destination warehouse data, product data, and/or order quantity of unallocated products for each logical warehouse. The received order data may be acquired and stored in the received order file 106d.

Based on the purchase data, the warehouse master 106a, and the channel-by-channel distribution quantity calculation master 106c, the distribution unit 102d calculates the distribution quantity of the product for each logical warehouse, and distributes the distribution quantity to each logical warehouse. Create distribution inventory data distributed as inventory quantity. Here, the allocation unit 102d sets a variable (non-allocation priority flag) regarding whether or not to give priority to the order quantity of unallocated products for each logical warehouse set in the channel-by-channel allocation quantity calculation master 106c. If priority is set, based on the purchase data, the warehouse master 106a, and the distribution quantity calculation master 106c for each channel, the difference quantity obtained by subtracting the order quantity from the purchase quantity is distributed to each logical warehouse. It is also possible to create distribution inventory data in which the sum of the distribution quantity and the order quantity is distributed as the inventory quantity of the product in each logical warehouse. Also, based on the purchase data, the warehouse master 106a, and the channel-by-channel distribution quantity calculation master 106c, the distribution unit 102d calculates the distribution quantity for each logical warehouse by multiplying the purchase quantity by the distribution ratio. Distribution inventory data may be created by distributing the distribution quantity as the inventory quantity of the product in each logical warehouse.

In addition, the allocation unit 102d sets a variable (non-allocation priority flag) regarding whether or not to prioritize the order quantity of unallocated products for each logical warehouse set in the channel-by-channel allocation quantity calculation master 106c. Then, if it is set, based on the purchase data, the warehouse master 106a, and the distribution quantity calculation master 106c for each channel, the distribution quantity for each logical warehouse is calculated by multiplying the difference quantity by the distribution ratio, and the distribution is performed. Distribution inventory data may be created by distributing the sum of the quantity and the order quantity as the inventory quantity of the product in each logical warehouse. In addition, the distribution unit 102d calculates the distribution quantity of products for each logical warehouse based on the purchase data, the warehouse master 106a, and the channel-specific distribution quantity calculation master 106c, and distributes ( (Movement) data may be generated, and based on the distribution (movement) data, distribution inventory data may be generated by distributing the distribution quantity as the inventory quantity of the product in each logical warehouse. Here, the sorting (moving) data includes sorting (moving) date and time, sorting (moving) source warehouse data, sorting (moving) destination warehouse data, product data, and/or product sorting for each logical warehouse. It may also include the total quantity of products distributed to each logical warehouse and the quantity of orders received. Also, the distribution unit 102d may store (register) the distribution inventory data in the inventory file 106e. Also, the distribution unit 102d may store the distribution (movement) data in the inventory file 106e.

The sales acquisition unit 102e acquires sales data. Here, the sales acquisition unit 102e may acquire product sales data for each logical warehouse. In addition, the sales acquisition unit 102e acquires sales data including sales dates, customer data, shipment source (distribution destination) warehouse data, product data and/or sales volume, etc., and stores the sales data in the sales file 106f. You may

The journal creation unit 102f creates journal data. Here, the journal creation unit 102f may create the journal data of the product based on the purchase data, the apportioned inventory data, and the sales data. Moreover, the journal creation unit 102f may create profit and loss statement data for a product. Moreover, the journalizing section 102f may store the journalizing data in the journalizing file 106g. Also, the journalizing section 102f may store the income statement data in the journalizing file 106g.

[2. Concrete example]
A specific example of this embodiment will be described with reference to FIGS. 2 to 14. FIG.

[Revenue management processing by channel]
Here, with reference to FIG. 2, an example of channel-by-channel revenue management processing according to the present embodiment will be described. FIG. 2 is a flow chart showing an example of processing of the channel-by-channel profit management device 100 in this embodiment.

As shown in FIG. 2, when the user inputs the name of the distribution channel used by the user through the input device 112, the master setting unit 102a assigns a logical warehouse for each distribution channel to the user's distribution warehouse. When the warehouse master 106a including the set warehouse name and warehouse code is set, and the user inputs the distribution ratio of the product for each logical warehouse via the input device 112, the distribution source is determined based on the warehouse master 106a. The distribution quantity calculation master 106c for each channel including the warehouse code, distribution destination warehouse code, non-allocation priority flag and the distribution ratio is set (step SA-1).

Then, the purchase acquisition unit 102b inputs the purchase date, the name of the supplier, the name of the product, and the quantity of purchase through the input device 112 by the user when the product is delivered from the ordering party to the distribution warehouse. If so, purchase data including the name of the supplier, the name of the product, the quantity of purchase, the date of purchase, and the warehouse code of the distribution warehouse are obtained, and the purchase data are stored in the purchase file 106b (step SA- 2).

Then, the distribution unit 102d determines whether or not order data including order quantity of unallocated products for each logical warehouse is registered in the order file 106d (step SA-3).

Then, when the distribution unit 102d determines that the order data including the order quantity of unallocated products for each logical warehouse is not registered (step SA-3: No), the process proceeds to step SA-5. .

On the other hand, when the distribution unit 102d determines that order data including order quantity of unallocated products for each logical warehouse is registered (step SA-3: Yes), the process proceeds to step SA-4. .

Then, the allocation unit 102d sets the unallocated priority flag regarding whether or not to give priority to the order quantity of unallocated products for each logical warehouse set in the channel-by-channel allocation quantity calculation master 106c. (the non-allocation priority flag is set) (step SA-4).

When the allocation unit 102d determines that the unallocated priority flag is not set (step SA-4: No), the process proceeds to step SA-5.

Then, based on the purchase data registered in the purchase file 106b, the warehouse master 106a, and the distribution quantity calculation master 106c for each channel, the distribution unit 102d multiplies the purchase quantity by the distribution ratio for each logical warehouse. Calculate the distribution quantity, create distribution inventory data by distributing the distribution quantity as the inventory quantity of the product in each logical warehouse, register the distribution inventory data in the inventory file 106e (step SA-5), and process. to step SA-7.

On the other hand, when the allocation unit 102d determines that the non-allocation priority flag is set (step SA-4: Yes), the process proceeds to step SA-6.

Based on the purchase data registered in the purchase file 106b, the order data registered in the order receipt file 106d, the warehouse master 106a, and the distribution quantity calculation master 106c for each channel, the allocation unit 102d deallocates the purchase quantity from the unallocated quantity. Calculate the distribution quantity for each logical warehouse by multiplying the difference quantity obtained by subtracting the order quantity of the logical warehouse with the priority flag set by the distribution ratio, and the distribution quantity of each logical warehouse without the priority flag not set, And/or create distributed inventory data by distributing the sum of the distributed quantity and the order quantity of each logical warehouse with the unallocated priority flag as the inventory quantity of the product in the logical warehouse, and store the distributed inventory data as the inventory. It is registered in the file 106e (step SA-6).

When the user inputs the sales date, the customer name, and the sales quantity through the input device 112 when the product is sold, the sales acquisition unit 102e acquires the sales date, the customer name, and the distribution destination. The sales data including the warehouse code, product name and sales quantity are acquired and stored in the sales file 106f (step SA-7).

Then, based on the purchase data, distribution inventory data, and sales data, the journal creation unit 102f generates journal data for products related to purchase, distribution (transfer), and sales, and product data for each logical warehouse (distribution channel). and stores the journal data and the profit and loss statement data in the journal file 106g (step SA-8), and terminates the process.

[Revenue management process by channel without considering unallocated orders]
Details of channel-by-channel profit management processing that does not take into account unallocated orders in this embodiment will now be described with reference to FIGS. 3 to 8. FIG. FIG. 3 is a flowchart showing an example of revenue management processing by channel in this embodiment.

As shown in FIG. 3, in the present embodiment, a warehouse master 106a including warehouse codes and warehouse names, in which distribution warehouses and logical warehouses (wholesale warehouses, directly managed warehouses, and EC warehouses) for each distribution channel are set, is set. (Step SB-1).

In the present embodiment, settings are made for calculating recommended values for allocating inventory at the time of allocating by distribution channel. A channel-by-channel distribution quantity calculation master 106c including the priority flag, the distribution destination warehouse CD and the distribution ratio is set (step SB-2).

In this embodiment, when the user inputs an order for a product (T-shirt) to each manufacturer, order data summarizing the products to be purchased is transmitted to each manufacturer (step SB-3).

In this embodiment, when the product is delivered from the ordering party to the distribution warehouse, if the user registers the purchase (inventory) with the purchase warehouse as "100: distribution warehouse", Purchase data including purchase date, supplier name, (purchase) warehouse CD, product name and purchase quantity are registered in the purchase file 106b (step SB-4).

In this embodiment, based on the purchase data, the warehouse master 106a, and the distribution quantity calculation master 106c for each channel, the distribution quantity for each channel (logical warehouse) is automatically calculated by multiplying the purchase quantity by the distribution ratio. Calculations are made, and movement data including the distribution quantity is created (step SB-5).

In this embodiment, based on the automatically calculated distribution quantity for each channel, the final distribution quantity is adjusted, the determined distribution quantity is captured, and the inventory is moved (distributed). By carrying out the movement take-in process, the apportioned inventory data obtained by distributing the apportionment quantity as the product inventory quantity of each channel is registered in the inventory file 106e (step SB-6).

Here, with reference to FIG. 4, an example of distributed inventory data in this embodiment will be described. FIG. 4 is a diagram showing an example of distributed inventory data in this embodiment.

FIG. 4 shows the purchase number, product code, product name, purchase date, purchase warehouse CD, and Distribution inventory data including purchase warehouse name, purchase quantity, transfer destination warehouse CD, transfer destination warehouse name, and distribution quantity are shown.

Returning to FIG. 3, in this embodiment, when the user registers sales (inputs sales) for each distribution channel, the sales date, customer name, (Distribution destination) The sales data including the warehouse CD, product name and sales quantity are registered in the sales file 106f (step SB-7).

Then, in this embodiment, the journal entry linking process to accounting is executed from the purchase data, movement data and sales data (step SB-8), and the process ends.

Here, an example of the journalizing cooperation processing in this embodiment will be described with reference to FIGS. 5 to 8. FIG. 5 to 7 are diagrams showing an example of journal data in this embodiment. FIG. 8 is a diagram showing an example of profit and loss statement data in this embodiment.

FIG. 5 shows journal data relating to purchase recording when 2,000 items of 1,000 yen each are purchased in the channel-by-channel revenue management process without taking into account unallocated orders shown in FIG. In addition, FIG. 6 divides the purchase quantity into 1,000 pieces for wholesale, 400 pieces for direct sales, and 600 pieces for EC in the revenue management process by channel that does not consider unallocated orders shown in FIG. It shows journal data related to distribution of products by channel at the time of transfer). Figure 7 shows 1,000 items of 3,000 yen per item from wholesale warehouses, 400 from directly managed warehouses, and 600 from EC warehouses in the revenue management process by channel that does not consider unallocated orders shown in Figure 3. It shows the journal entry data related to recording the sales at the time of sales. Also, FIG. 8 shows profit and loss statement data for products for each distribution channel (wholesale channel, retail (directly managed) channel, and EC channel) in the revenue management process by channel that does not consider unallocated orders shown in FIG. showing.

[Revenue management process by channel taking into account unallocated orders]
Further, the details of channel-by-channel revenue management processing that takes into account unallocated orders in this embodiment will be described with reference to FIGS. 9 to 14 . FIG. 9 is a flowchart showing an example of revenue management processing by channel in this embodiment.

As shown in FIG. 9, in this embodiment, a warehouse master 106a including warehouse codes and warehouse names is set in which distribution warehouses and logical warehouses (wholesale warehouses, directly managed warehouses, and EC warehouses) for each distribution channel are set. (Step SC-1).

In the present embodiment, settings are made for calculating recommended values for allocating inventory at the time of allocating by distribution channel. A channel-by-channel distribution quantity calculation master 106c including the priority flag, distribution destination warehouse CD and distribution ratio is set (step SC-2).

In this embodiment, when the user inputs an order for a product (T-shirt) from each customer, the order date, customer name, (allocation destination) warehouse code, product name, and order quantity are entered. and the order data including the unallocated quantity is registered in the order file 106d (step SC-3).

In this embodiment, when the user inputs an order for products to each maker, order data summarizing the products to be procured is transmitted to each maker (step SC-4).

In this embodiment, when the product is delivered from the ordering party to the distribution warehouse, if the user registers the purchase (inventory) with the purchase warehouse as "100: distribution warehouse", Purchase data including purchase date, supplier name, (purchase) warehouse CD, product name and purchase quantity are registered in the purchase file 106b (step SC-5).

In the present embodiment, the channel is obtained by multiplying the difference quantity obtained by subtracting the order quantity from the purchase quantity by the distribution ratio based on the purchase data, the order data, the warehouse master 106a, and the distribution quantity calculation master 106c for each channel. (Logical Warehouse) Automatically calculate another distribution quantity and create movement data including the distribution quantity (Step SC-6).

Then, in this embodiment, the final allocation quantity is adjusted based on the distribution quantity for each channel that is automatically calculated taking into account the number of unallocated orders, and the confirmed distribution quantity is taken in, By carrying out the movement acquisition process for moving (allocation) the inventory, the allocation quantity is registered in the stock file 106e as the stock quantity of the product of each channel (step SC-7).

Here, with reference to FIG. 10, an example of distributed inventory data in this embodiment will be described. FIG. 10 is a diagram showing an example of distributed inventory data in this embodiment.

FIG. 10 shows the purchase number, product code, product name, purchase date, purchase warehouse CD, and Purchase warehouse name, purchase quantity, destination warehouse CD, destination warehouse name, total order quantity, order quantity, distribution quantity, slip (order) number, line number, customer code, customer name, order date, Shows apportionment inventory data including shipping dates and backorder quantities.

Returning to FIG. 9, in this embodiment, when the user registers sales (inputs sales) for each distribution channel, the sales date, customer name, (Distribution destination) The sales data including the warehouse CD, product name and sales quantity are registered in the sales file 106f (step SC-8).

Then, in this embodiment, the journal entry linking process to accounting is executed from the purchase data, movement data and sales data (step SC-9), and the process ends.

Here, an example of the journalizing cooperation processing in this embodiment will be described with reference to FIGS. 11 to 14. FIG. 11 to 13 are diagrams showing an example of journal data in this embodiment. FIG. 14 is a diagram showing an example of profit and loss statement data in this embodiment.

FIG. 11 shows journal data relating to recording of purchases when 2,000 items of 1,000 yen each are purchased in the channel-by-channel revenue management process that takes into account unallocated orders shown in FIG. In addition, FIG. 12 divides the purchase quantity into 1,100 pieces for wholesale, 360 pieces for direct sales, and 540 pieces for EC in the profit management process by channel taking into account unallocated orders shown in FIG. It shows journal data related to distribution of products by channel at the time of transfer). In FIG. 13, in the revenue management process by channel taking into account the unallocated orders shown in FIG. 9, 500 items of 3,000 yen per item were sold from the wholesale warehouse, 200 from the directly managed warehouse, and 300 from the EC warehouse. It shows the journal entry data related to recording sales at the time. Also, FIG. 14 shows profit and loss statement data of products for each distribution channel (wholesale channel, retail (directly managed) channel, and EC channel) in the channel-by-channel revenue management processing that takes into account unallocated orders shown in FIG. showing.

Thus, in this embodiment, a logical warehouse may be created for each distribution channel (wholesale, direct management, EC) in the distribution warehouse, and inventory management may be performed for each channel. In addition, in this embodiment, when placing an order, instead of placing an order with the same manufacturer for each distribution channel, the company may place an order for items that the company wants to place an order for, specifying a physical warehouse. In addition, in this embodiment, after accounting for purchases, according to the rule of unallocated orders and master setting values, an index for sorting by distribution channel is output and adjusted, and the result of the adjustment is It may be imported as movement data from the physical warehouse where the purchase was recorded to the warehouse for each distribution channel. In addition, in this embodiment, based on the movement data, each channel code is set to the channel code to perform journal entry linkage and manage the cost for each channel in order to make accounting judgments as purchases for each distribution channel. may

[3. Other embodiments]
The present invention may be implemented in various different embodiments other than the embodiments described above within the scope of the technical idea described in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or all of the processes described as being manually performed Alternatively, some can be done automatically by known methods.

In addition, unless otherwise specified, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed arbitrarily.

Also, with respect to the channel-by-channel profit management apparatus 100, each component shown in the figure is functionally conceptual, and does not necessarily need to be physically configured as shown in the figure.

For example, all or any part of the processing functions provided by the channel-specific profit management apparatus 100, particularly each processing function performed by the control unit 102, is realized by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be implemented as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing apparatus to execute the processing described in this embodiment, and may It is mechanically read by the management device 100 . That is, a storage unit such as a ROM or HDD (Hard Disk Drive) stores a computer program for giving commands to the CPU in cooperation with the OS to perform various processes. This computer program is executed by being loaded into the RAM and constitutes a control section in cooperation with the CPU.

In addition, this computer program may be stored in an application program server connected to the channel-based revenue management apparatus 100 via any network, and may be downloaded in whole or in part as necessary. It is possible.

Also, the program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to memory cards, USB (Universal Serial Bus) memories, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (registered (trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Versatile Disk), and Disc (registered trademark) such as Blu- shall include any "portable physical medium".

A "program" is a data processing method written in any language or writing method, regardless of the format such as source code or binary code. In addition, the "program" is not necessarily limited to a single configuration, but is distributed as multiple modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. It should be noted that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the present embodiment, the installation procedure after reading, and the like.

The various databases and the like stored in the storage 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 are used for various processing and website provision. programs, tables, databases, and files for web pages.

Further, channel-based profit management apparatus 100 may be configured as an information processing apparatus such as a known personal computer or workstation, or may be configured as the information processing apparatus to which any peripheral device is connected. Further, the channel-specific profit management apparatus 100 may be realized by installing software (including programs, data, etc.) for realizing the processing described in this embodiment.

Furthermore, the specific forms of distribution and integration of devices are not limited to those shown in the figures, and all or part of them can be functionally or physically arranged in arbitrary units according to various additions or functional loads. It can be distributed and integrated. In other words, the embodiments described above may be arbitrarily combined and implemented, or the embodiments may be implemented selectively.

INDUSTRIAL APPLICABILITY The present invention is useful in industries such as distribution and retail businesses that require management of income and expenditure for each distribution channel.

100 channel-by-channel profit management device 102 control unit 102a master setting unit 102b purchase acquisition unit 102c order acquisition unit 102d distribution unit 102e sales acquisition unit 102f journal creation unit 104 communication interface unit 106 storage unit 106a warehouse master 106b purchase file 106c channel Different allocation quantity calculation master 106d Order file 106e Inventory file 106f Sales file 106g Journal file 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (9)

A channel-by-channel profit management device comprising a storage unit and a control unit,
The storage unit
Warehouse storage means for storing a warehouse master in which a logical warehouse is set for each distribution channel set in a physical warehouse;
an order storage means for storing order data including an order quantity of unallocated products for each of the logical warehouses;
channel-by-channel allocation storage means for storing a channel-by-channel allocation quantity calculation master in which the allocation ratio of the product to each of the logical warehouses is set;
with
The control unit
purchase acquisition means for acquiring purchase data including the purchase quantity of the product ;
The product for each of the logical warehouses, which is obtained by allocating the difference quantity obtained by subtracting the order quantity from the purchase quantity based on the purchase data, the warehouse master, and the distribution quantity calculation master for each channel, to each of the logical warehouses. a distribution means for creating distributed inventory data by calculating the distribution quantity of and distributing the sum of the distribution quantity and the order quantity as the inventory quantity of the product in each of the logical warehouses;
A revenue management device for each channel, characterized by comprising: The distribution quantity calculation master for each channel is
Furthermore, a variable is set as to whether or not the order quantity is given priority,
The sorting means is
Further, if the variable is set so that the order quantity is not prioritized, the purchase quantity is multiplied by the distribution ratio based on the purchase data, the warehouse master, and the distribution quantity calculation master for each channel. and calculating the distribution quantity of the product for each of the logical warehouses, and creating distribution inventory data by distributing the distribution quantity as the inventory quantity of the product in each of the logical warehouses. Channel-specific revenue management device as described. The control unit
sales acquisition means for acquiring sales data of the product for each logical warehouse;
3. The channel-based revenue management device according to claim 1 or 2 , further comprising: The control unit
journal creation means for creating journal data for the product based on the purchase data, the apportioned inventory data, and the sales data;
4. The per-channel revenue management apparatus of claim 3 , further comprising: The journal creation means
5. The channel-by-channel profit management device according to claim 4 , further comprising generating profit and loss statement data for the product for each logical warehouse. The sorting means is
Based on the purchase data, the warehouse master, and the distribution quantity calculation master for each channel, calculate the distribution quantity for each logical warehouse by multiplying the difference quantity by the distribution ratio, and calculate the distribution quantity 2. The revenue management device for each channel according to claim 1, wherein the distributed inventory data is created by allocating the total of the order quantity and the order quantity as the inventory quantity of the product in each of the logical warehouses. The logical warehouse is
Claim 1 characterized by being a wholesale warehouse for indirect distribution channels through distributors, a directly managed warehouse for direct distribution channels at directly managed stores, and/or an EC warehouse for direct distribution channels in electronic commerce. 7. The revenue management device for each channel according to any one of 6 . A channel-based revenue management method to be executed by a channel-based revenue management device comprising a storage unit and a control unit, comprising:
The storage unit
Warehouse storage means for storing a warehouse master in which a logical warehouse is set for each distribution channel set in a physical warehouse;
an order storage means for storing order data including an order quantity of unallocated products for each of the logical warehouses;
channel-by-channel allocation storage means for storing a channel-by-channel allocation quantity calculation master in which the allocation ratio of the product to each of the logical warehouses is set;
with
to be executed by the control unit;
a purchase acquisition step of acquiring purchase data including the purchase quantity of the product ;
The product for each of the logical warehouses, which is obtained by allocating the difference quantity obtained by subtracting the order quantity from the purchase quantity based on the purchase data, the warehouse master, and the distribution quantity calculation master for each channel, to each of the logical warehouses. a distribution step of calculating the distribution quantity of and creating distribution inventory data by distributing the sum of the distribution quantity and the order quantity as the inventory quantity of the product in each of the logical warehouses;
A revenue management method for each channel, characterized by comprising: A channel-specific profit management program to be executed by a channel-specific profit management device comprising a storage unit and a control unit, comprising:
The storage unit
Warehouse storage means for storing a warehouse master in which a logical warehouse is set for each distribution channel set in a physical warehouse;
an order storage means for storing order data including an order quantity of unallocated products for each of the logical warehouses;
channel-by-channel allocation storage means for storing a channel-by-channel allocation quantity calculation master in which the allocation ratio of the product to each of the logical warehouses is set;
with
In the control unit,
a purchase acquisition step of acquiring purchase data including the purchase quantity of the product ;
The product for each of the logical warehouses, which is obtained by allocating the difference quantity obtained by subtracting the order quantity from the purchase quantity based on the purchase data, the warehouse master, and the distribution quantity calculation master for each channel, to each of the logical warehouses. a distribution step of calculating the distribution quantity of and creating distribution inventory data by distributing the sum of the distribution quantity and the order quantity as the inventory quantity of the product in each of the logical warehouses;
Channel-specific revenue management program for executing

Images