JPH07175860A - Automatically updating device for sales data base - Google Patents

Abstract

PURPOSE:To perform management with a high efficiency by saving labor with minimum data base(DB) resources by automatically updating the managing cycle of a sales DB. CONSTITUTION:This automatically updating device 1 for the sales DB is constituted of plural sales DBs 11-14 formed classified by every managing cycle of a product and on which sales information is recorded at every product, a management reference read-in means 3 set at every product, a means 5 which decides the managing cycle of the product at every product by comparing the sales information 4 in the sales DB with management reference 3 and decides the change of the managing cycle when a decided managing cycle is different from the present managing cycle, and a means 6 which changes the sales DB on which the sales information of the product is recorded to the sales DB of decided managing cycle.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a device for automatically updating a management cycle of a sales database (hereinafter, "database" is abbreviated as "DB") in which sales information is recorded.

[0002]

2. Description of the Related Art Sales information is important information mainly for determining the order quantity of products and the appropriate stock quantity. However, since the number of products handled in the retail business exceeds 10,000, and that of large stores such as department stores exceeds one million, the amount of sales information data for each product is enormous. In order to manage such a huge amount of sales information, a DB is formed for each different management cycle such as daily or monthly, and the sales information is recorded in the DB of an appropriate management cycle according to the characteristics of each product. Is done. With this, for example, fresh food can be managed in a short cycle by time of day or day, and clothing can be managed in a long cycle of week or month.
There is no need to increase the size of DB more than necessary,
DB resources can be saved.

FIG. 5 shows an example of conventional sales DB management.
Will be explained. Center 21 that manages the sales DB
Collects product-specific sales information from a plurality of retailers 22, 23 ... The collected sales information by product is recorded in the sales DB for each product by using the DB update program 26.

The sales DB is composed of four kinds of DBs having different management cycles, such as a time zone sales DB 11, a daily sales DB 12, a weekly sales DB 13, and a monthly sales DB 14. FIG. 6 shows an example of the data structure of the daily sales DB 12, and FIG. 7 shows an example of the data structure of the monthly sales DB 14. As is clear from these figures, the shorter the management cycle, the larger the DB size, and the longer the management cycle, the smaller the DB size.

Now, the reason why the sales DB is configured with different management cycles will be described. If total sales D
If B is managed at the same level, for example, the daily sales DB 12, the amount recorded on the DB becomes enormous and the size of the sales DB becomes large. Also, it is not necessary to manage perishable food items that cannot be sold within a few days and clothing items, etc., whose sales quantity changes seasonally in the same cycle. Therefore, if fresh food is managed in a short cycle such as hourly sales DB 11 or daily sales DB 12, and clothing is managed in a long cycle such as weekly sales DB 13 or monthly sales DB 14, DB resources can be saved, and Product management can be done reasonably.

By the way, in the system using the DBs having different management cycles described above, it may be necessary to update the management cycle of the product due to changes in the characteristics of the product or the sales quantity. For example, books or CDs,
Initially when it was released as a new publication or new song, the sales volume was large, but over the years, the sales volume tends to decrease. Therefore, it is necessary to manage a product having such characteristics in a short cycle at the beginning of sale, but it is preferable to manage it in a long cycle when the product is not sold well.

In the conventional system, such a management cycle is updated by using the data update registration program 27, and the operator updates the management cycle of the sales DB from the terminal 8 for each product that needs updating. Was there.

[0008]

As described above, in the conventional system, in order to update the DB management cycle for each product, the data update registration process is performed for each product by the operation of the operator, which is very difficult. Labor was needed. On the other hand, an object of the present invention is to make it possible to automatically update the management cycle of the sales DB and to realize efficient management with minimum DB resources and labor saving.

[0009]

In order to achieve the above object, the present invention has a plurality of sales DBs, which are formed for each product management cycle and record sales information for each product, and a management standard set for each product. Then, for each product, the sales information in the sales DB is compared with the management standard to determine the management cycle of the product. If the determined management cycle and the current management cycle are different, the management cycle is changed. And a means for changing the sales DB for recording the sales information of the product to the sales DB for the determined management cycle, thereby constituting an automatic sales DB updating device.

[0010]

With the operation of the automatic updating device, the sales information and the management standard are compared for each product, and the optimum management cycle of the product is determined. When the determined management cycle is different from the current management cycle, the sales DB of the product
Will be changed to this decided management cycle. Therefore, the management cycle of the sales DB can be automatically updated. Further, since the sales information for each product is always recorded in the sales DB of the optimum management cycle, the size of the sales information recorded in the sales DB is the minimum necessary size. Therefore, efficient management can be realized with a minimum of DB resources and labor saving.

[0011]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 shows the system configuration for updating the sales DB. In the automatic update device 1, the management reference reading unit 3 that reads the individual product code and the sales DB management table for each product from the product master file 2, and the sales information corresponding to the single product code read by the management reference reading unit 3 from the monthly sales DB 14. It is necessary to compare the sales information of the sales information reading unit 4 and the management standard reading unit 3 to be read with the sales DB management table of the sales information reading unit 4, determine the management cycle of the product, and update the management cycle of the product. When the update determining unit 5 to determine and the update determining unit 5 determine to update, the updating unit 6 that updates the sales DB for the product is provided.

Further, the automatic update device 1 is provided with an extraction file 7 for storing data necessary for determining a management cycle of a product for which the sales DB needs to be updated manually by an operator. .
The operator confirms the data stored in the extracted file 7 with the terminal 8 and determines whether or not to update the management cycle. The determination result is input from the terminal 8, and when updating is executed, the update determining unit 5 issues a command to the updating unit 6.

In the present embodiment, the sales DB includes a time zone sales DB 11, a daily sales DB 12, a weekly sales DB 13, and a monthly sales DB 14. As described above, the sales DBs 11 to 14 store data in the formats shown in FIGS. 6 and 7. The contents of the data read by the management standard reading means 3 are shown in FIG. This data includes a single item code which is a key for reading the sales information of the product from the sales DB, and a sales DB management table for managing the cycle of the sales DB for the product. Sales D
In the B management table, "attribute""presence or absence of automatic change""weekly target quantity""daily target quantity""time zone target quantity"
An item “presence or absence of notification to operator” is provided.

The flowchart of FIG. 3 shows a process of setting the sales DB management table in the product master. In step S1, as a new product registration process for the product master 2, information such as a single product code, a classification code, a product name, and a price is registered for a product to be newly registered.
Note that these items are items that have been registered in the past. In step S2, each item of the above-mentioned sales DB management table is set. In step S3, the above items are added to the product master file.

The sales DB management table of FIG. 2 will be described in more detail. In the "attribute" item, the management cycle of the product is set. "1" is set for products whose management cycle is monthly, "2" is set for weekly, "3" is set for daily, and "4" is set for hourly. When the data of the product is first registered in the sales DBs 11 to 14, the sales DB to be registered is determined according to the setting of this "attribute". In the example of FIG. 2, the sales information of the product for which “1” is set is registered in the monthly sales DB 14, the sales information for the product of “2” is registered in the weekly sales DB 13 and the monthly sales DB 14, and the sales information of “3” is registered. Product sales information is registered in the daily sales DB 12, weekly sales DB 13 and monthly sales DB 14, and is “4”.
Sales information for the product is sales DB11 by time zone, sales D by day
B12, the weekly sales DB 13 and the monthly sales DB 14 are registered.

In the item "presence / absence of automatic change", "1" is set for products that are not automatically updated, and "0" is set for other products. "Target quantity by week"
Reference quantities for determining the sales information management cycle of the product are set in the “daily target quantity” and the “time zone target quantity”. Monthly sales quantity is used as this quantity,
When the monthly sales quantity of the product recorded in the monthly sales DB 14 exceeds the quantity set for each item, the sales information of the product is recorded in the sales DB of the management cycle corresponding to the item.

"Presence or absence of notification to operator" is set to "1" for products for which it is determined that the management cycle needs to be updated, and those that need to be updated after the operator approves. For other products, "0" is set. Next, the operation of the automatic update device configured as described above will be described with reference to the flowchart of FIG.

In step S11, the individual product code and the sales DB management table are read from the product master 2 to the management reference reading means 3 for each product. In step S12, the reading of all the records of all the product masters is completed, and when there are no more records, the automatic update process is completed. Normally, the process proceeds to step S13.

In step S13, "presence or absence of automatic change" in the sales DB management table is checked, and if it is "1", automatic update processing is not performed and the process returns to step S11 to read the next product master. . If "0", step S
Proceed to 14. In step S14, the sales information of the product corresponding to the single item code is read into the sales information reading means 4 from the monthly sales DB 14.

In step S15, the monthly sales quantity of the read sales information is compared with the quantities set in the "target quantity by time period", the "target quantity by day" and the "target quantity by week" in the sales DB management table, and is read. However, when the sales quantity exceeds any set quantity, the management cycle corresponding to the set quantity is determined as the management cycle of the product. Step S
At 16, the determined management cycle is compared with the actual management cycle to determine whether the management cycle needs to be changed. Sales D if both management cycles match
It is determined that the updating process of the management cycle of B is unnecessary, and the process returns to step S11 to read the next product master. If they do not match, the process proceeds to step S17.

In step S17, "presence or absence of notification to operator" is checked, and if "1", that is, a product requiring notification to the operator, proceeds to step S18.
For "0", that is, for products that do not require notification, the process proceeds to step S20. In step S18, necessary information is stored in the management cycle change data extraction file 7 and an alert is issued.

In step S19, the operator confirms the information stored in the extraction file 7 on the terminal 8 and determines whether to update the management cycle. The operator inputs the determination result from the terminal 8. When the operator approves the update of the management cycle, the process proceeds to step S20. When the operator does not approve the update, the process of updating the sales DB is not performed and the process returns to step S11 to read the next product master.

At step S20,
Automatically update the sales DB management cycle. When changing the management cycle from a long management cycle to a short management cycle, the sales information of the product is added to the sales DB of the short management cycle. Further, when the management cycle is changed from the short management cycle to the long management cycle, the sales information of the product is deleted from the sales DB of the unnecessary short management cycle.

With the sales DB automatic updating apparatus described above, the sales information of the products is always managed in the optimum management cycle, and the management is performed in an unnecessarily short cycle, that is, the sales DB data becomes unnecessary. There is no need to make it bigger. Therefore, efficient management can be performed with a minimum of DB resources. Further, since the automatic updating process is performed completely automatically, labor saving of the automatic updating process is achieved.

In the product master, even if products that are automatically updated and products that are not automatically updated, and products that require operator approval and products that do not require operator approval when the management cycle is changed are mixed, It is possible to automatically perform processing according to the attributes of each product.

[0026]

According to the present invention, the management cycle of the sales DB is automatically updated, and efficient management can be realized with minimum DB resources and labor saving.

[Brief description of drawings]

FIG. 1 is a system configuration diagram of an automatic updating device according to an embodiment of the present invention.

FIG. 2 is a diagram showing data contents of a product master of FIG.

FIG. 3 is a flowchart showing a product master setting process of FIG.

FIG. 4 is a flowchart illustrating an operation of the automatic updating device in FIG.

FIG. 5 is a system configuration diagram showing a conventional sales DB management device.

FIG. 6 is a diagram showing a data structure of a daily sales DB.

FIG. 7 is a diagram showing a data structure of a monthly sales DB.

[Explanation of symbols]

 1 ... Sales DB automatic updating device 2 ... Product master file 3 ... Management standard reading means 4 ... Sales information reading means 5 ... Update determining means 6 ... Update means 7 ... Extraction file 8 ... Terminal 11 ... Sales DB by time zone 12 ... Day Separate sales DB 13 ... Weekly sales DB 14 ... Monthly sales DB

Claims (1)

[Claims] 1. A plurality of sales databases that are formed for each product management cycle and record sales information for each product, management standards set for each product, and sales information and management for each product in the sales database. A database that records the sales information of the product, by comparing the standards to determine the management cycle of the product, and when the determined management cycle and the current management cycle are different, the management cycle is changed. To a sales database of the determined management cycle.