JPH0887545A - Planning support method for commodity sale program - Google Patents

Abstract

PURPOSE: To attain an efficient combination between a commodity program and a sale program by updating a process progress management table when each process is completed at the purchasing or selling side and inhibiting the progress to toe next process unless the result of the opposite side process is received. CONSTITUTION: In a system where a sale program is planned with synchronization of processes secured between a commodity program 301 of the purchasing side 101 and a sale program of the selling side 102, a table information file 302 is provided to manage the progress state of each process. The contents of the file 302 are updated when each process is completed at the side 101 or 102. If the transfer propriety flag of the file 302 shows the necessity of transfer under such conditions, the system transmits the commodity program to the opposite party side. At the same time, the side 101 or 102 is inhibited from proceeding to the next process unless the result of the opposite side process is received. Furthermore an error display is carried out if the state value flag of the precedent process does not show a completion state when the file 302 is updated.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for supporting a product sales plan, and in particular, in order to efficiently carry out the product planning work on the product procuring side and the sales planning work on the selling side in the distribution business of fashion products etc. In the planning process, it relates to a method of supporting the determination of the results while synchronizing them.

[0002]

2. Description of the Related Art In the conventional fashion product field, in the procurement side (producer side) and the sales side sales plan, the production side, the sales plan, etc. are drafted respectively, and after the both sides are coordinated, the procurement side is The production was started. In these planning process stages, information transmission and synchronization work between the two are performed by a meeting of the person in charge, etc., and information is generally exchanged using a telephone or fax. .

[0003] For example, in the fashion industry, the procurement side and the sales side carry out product planning and sales operations by exchanging information and making product type composition plans, product type period development plans, and product item development plans. To do. First, in the product type composition plan, the procurement side prepares a product type composition plan as the first step, the sales side acquires the product type composition plan as the second step, and the relevant information is also obtained as the third step. Based on this, the product type composition plan of the selling side is made, the product type composition plans of both parties are displayed and examined, and as a fourth step, the operator inputs the changed value of the product type composition plan of the selling side. As the fifth step, the procurement side obtains the changed value, the sixth step
As a step, as a result of the examination, the product type composition plan is determined. Similarly, in the following product variety period development plan and further product item development plan, by synchronizing such a process, the synchronization of the product plan and the sales plan is supported.

[0004]

The method of product planning / sales planning in the above-mentioned prior art mainly involves a meeting between persons in charge between different departments (procurement side and sales side). The means for connecting both of them is done manually, and there are omissions of contact and deficiencies in the transmission of information. Sometimes it was difficult to proceed well. In addition, even if you intend to proceed while keeping the two synchronized, information may not be accurately transmitted due to information transmission errors, and it is a major concern that there is no mechanism to verify whether this information was transmitted correctly. It was

The present invention has been made in view of the above circumstances, and an object thereof is to provide a method for supporting the planning of a product sales plan that efficiently links both the product plan and the sales plan.

[0006] Another object of the present invention is, in a product planning process on the procurement side having several processes and a sales planning process on the sales side, one of the procurement side and the sales side proceeds to the next process. It is to provide a method for supporting the planning of a product sales plan that sometimes cannot proceed to the next step unless the result of the partner's process is received.

[0007]

According to the present invention, there are a plurality of steps of a product plan on the procurement side and a step of a sales plan on the sales side, and a system for making a sales plan by synchronizing these steps is used. In order to make sure to take

A table information file for managing the progress of the process is provided in the above system. This table information file may be provided on either the purchasing side or the selling side. In the table information file, a storage area for a transfer necessity flag indicating whether or not to send the product plan to the other party and a status value flag storage area for indicating whether or not each process is completed are set. If these flags are provided for each procedure of each process, fine control can be performed. Then, when each process on the purchasing side or the selling side is completed, the contents of this table information file are updated. At this time, if the transfer necessity flag of the table information file indicates that transfer is necessary, the system sends the product plan to the other party. Further, when either the purchasing side or the selling side does not receive the result of the other process when proceeding to the next process, it is prohibited to proceed to the next process. In addition, if the status value flag of the previous process does not indicate the end when updating the table information file in the table information file,
An error is displayed.

[0009]

[Function] In the process of the product plan on the procurement side and the process of the sales plan on the sales side, one of the procurement side and the sales side receives the result of the process of the other party, and also based on the result information of the process of the other party,
You can plan your own process, display the results of your own process and the process of your partner on the screen, and examine the results of both. Based on these, the operator inputs the changed value of the result of the own process concerned, and by transmitting the changed value to the other side, the two can be synchronized in the process and the result can be determined. By repeating such a process, it is possible to support the process of the product plan on the procurement side and the process of the sales plan on the sales side in synchronization, so that it is possible to efficiently and accurately prepare a product and a sales plan.

[0010]

An embodiment of the present invention will be described in detail below with reference to the drawings. FIG. 1 is a block diagram of an embodiment of a fashion product management system to which the present invention is applied.

In FIG. 1, the system has a computer system of a purchasing side 101 and a computer system of a selling side 102. The procurement side 101 includes a processing device 1, an input device 2, a display device 3, and a storage device 4. The sales side basically has the same configuration as the procurement side, and includes a processing device 5, an input device 6, a display device 7, and a storage device 8. The processing devices 1 and 5 on the purchasing side and the selling side are communication lines 9
Connected by. In this embodiment, only one set of each of the input devices 2 and 6 and the display devices 3 and 7 is shown, but it goes without saying that in reality, more sets will be connected. Further, each computer system may use a large computer or a small personal computer.

Next, the operation of this embodiment will be described with reference to the flow chart of FIG. FIG. 2 shows a product type composition plan 210 and a product type period development plan 2 while exchanging information between the purchasing side 101 and the selling side 102.
20 shows the case where the item 20 is performed and the product plan is executed. When planning a fashion product,
(Product type composition plan) → (Period development plan of the type) →
(Product item development plan) →… Some steps (stages) are followed and a rough plan to a detailed plan are sequentially drafted. At this time, it is necessary to make plans while exchanging information between the procurement side 101 and the sales side 102 and making adjustments at each stage.

In the following, the present embodiment will be described assuming that the procurement side 101 is the main (side taking the initiative) and the sales side 102 is the sub. The relationship between the procurement side (main) 101 and the sales side (sub) 102 in this embodiment is as follows. The procurement side 101 creates a plan, gives the relevant information to the sales side 102, acquires a change value from the plan of the sales side 102, corrects and confirms the plan of the procurement side 101, and proceeds to the next planning process. is there.

The sales side 102 creates a plan of the sales side 102 for the plan acquired from the procurement side 101, and gives the difference to the sales side 102 as a changed value to the procurement side 101. Here, one point of the present invention is that the selling side 10
2 is to inform the procurement side 101 of the difference in the planned value from the procurement side 101.

Here, an outline of the flow of product sales planning will be described with reference to FIG. In the product type composition plan 210, first, the procurement side 101 creates a product type composition plan for the product. A known method may be used as the method of this creation. Of course, manually created data may be input to the computer system (step 211). At this time, the created data is stored in the storage device 4, and the processing device 1 transmits the created data to the selling-side processing device 5 using the communication line 9.

The selling side 102 acquires the product type composition plan concerned (step 212), and based on the information, makes the product type composition plan of the selling side 102 (step 213).
The product type composition plans of both are displayed on the display device 7. Then, the operator inputs the changed value of the product type composition plan of the selling side 102 (step 214). The changed value is sent to the processing device 1 via the communication line 9 and stored in the table in the storage device 4. This change value sent is step 2
The difference between the data created in 11 and the data created in step 213 is good. If you send the difference, the procurement side 10
With 1, you can easily determine whether to increase or decrease the sales plan. Of course, instead of sending the difference, the planned value itself may be sent.

Next, the procurement side 101 acquires the changed value (step 215) and re-plans and confirms the product type composition plan based on the changed value (step 216). The product type composition plan determined here may be sent to the selling side 102.

Although the plan relating to the product type composition of the product has been completed as described above, the process goes to the planning process of the fixed product period development plan, and the product type period development plan 220 is performed. Procurement side 10 in product type period development plan 220
In 1, create a product variety period development plan (step 2
21). This is to create a weekly sales for the total sales by product type as a budget. Next, the processing device 1 transmits the created data to the processing device 5 on the selling side using the communication line 9. The sales side 102 acquires this product variety period development plan (step 22).
2). The sales side 102 uses the information and the sales side 10
2 product type period development plan (step 223),
Both product type period development plans are displayed on the display device 7.
Then, the operator inputs the changed value of the product type period development plan of the selling side 102 (step 224). The changed value is sent to the processing device 1 via the communication line 9 and stored in the storage device 4. The procurement side 101 acquires the changed value (step 225), and as a result of the examination, establishes the product variety period development plan 220 (step 226).

Next, the contents of the product plan by the fashion product management system will be further described with reference to FIGS.
FIG. 3 shows a case where the procurement side 101 and the sales side 102 carry out the product type composition plan while exchanging information with each other.

In the product type composition plan, the procurement side 101
Then, the commodity type composition plan 301 on the procurement side is created (step 211). In the product type composition plan 301, the product type (ex. Skirt, suit), composition ratio to sales (sales composition ratio to total sales,%), and average selling price (¥) are determined and stored. This is created on the storage device 4 of FIG. When step 211 ends, the status value flag of the table information 302 is updated (0 → 1). The table information 302 manages the progress of each process in making a product plan, and is provided to confirm the progress of the procurement side and the sales side after the product type composition plan is drafted. It is a thing. In this embodiment, this table information 302 is used for the procurement side 101 and the sales side 1.
It is possible to systematically manage whether or not the contact and approval with 02 has been obtained.

Here, with reference to FIG. 5, table information 302
Will be described in detail. The table information 302 in FIG.
It is divided into a plurality of sections including a table 1, a table 2, and a table 3.

In the table 1, the process name 510 is the name of the process managed by the table, and in this example, it indicates "product type composition plan". Step No. 5
In step 20, the steps included in the process are enumerated, and in this example, the steps include steps 211 to 216, and these steps correspond to the steps in FIGS. 2 and 3. The transfer necessity flag 530 specifies whether or not to transfer the planned value from the procurement side 101 to the sales side 102 or from the sales side 102 to the procurement side 101 when the step is completed. 0 means no transfer. In this example, at step 211 and step 214, it is specified that the changed value is to be transferred. The status value flag 540 stores a flag indicating whether or not the process is completed depending on the progress of the process, where 1 means process completion and 0 means incomplete. The purchasing side 101 sets the respective status value flags in steps 211, 215 and 216 of the table 1, and the selling side 102 sets the respective status value flags in steps 212 to 214. This status value flag 540 can be set from 0 to 1 if
Only if the status value flag of the previous step is set to the correct value.

The table 3 is for managing the setting of the entire system, and the main / sub section 540 is for setting which of the procurement side and the sales side takes the initiative. The main takes the initiative. Is the taker, in this case the procuring side. Here, table information 302 is provided for managing progress of the process on the side that takes the initiative.

Table 2 is a table relating to a product type period development plan which is the next step. The method of setting the transfer necessity flag and the status value flag is the same as in the case of the table 1, and therefore the description thereof is omitted. Here, when the product type composition plan is finalized and the process proceeds to the product type period development plan, it is limited to the case where the correct value indicating the finalization of the product type composition plan is set in the status value flag in step 6 of table 1. good. By using such table information, the process cannot proceed unless the procurement side and the sales side are synchronized in the product type composition plan and the product type period development plan. Therefore, reliable sales plan support can be provided. it can.

Next, the control device 1 on the procurement side 101 transmits the contents of the product type composition plan 301 to the sales side when the status value flag of the table information 302 is changed. This procedure will be described with reference to the flowchart of FIG. To do.

First, the processor 1 confirms the sent table information 302. Here, the status value 540 of step 211 of step No. 510 is updated by "1" (step 61). Next, it is confirmed whether the status value of the previous step is "1". Since step 211 is the first step and there is no step before it, the process proceeds to Yes in this case. After step 212, since there is a previous step, the status value 540 flag of that step is confirmed. If the status value of the previous step is "1", it means that the previous step has been completed normally, so proceed to the next step, and if it is "0", the previous step has been completed. Since there is not, an error is displayed (step 62). Next, the transfer necessity flag 53 of that step
Confirm 0 (step 63). Transfer necessity flag 530
If is "1", the content of the process name 510 is transmitted to the other party (step 64). In this case, the procurement side product type composition plan 301 is sent. When the transfer necessity flag 530 is “1”, the process skips to step 65. When the above steps 61 to 65 are normally completed, the status value flag 54
Set '1' to 0 and end. The procedure of FIG. 6 described above is similarly performed in steps 211 to 216 of FIG. 2 each time the status value flag of the table information 302 is changed.

Returning to FIG. 2 again, the sales side 102 acquires the product type composition plan 301 concerned and updates the status value flag of the table information 302 according to the procedure of FIG. This update is for ensuring that the content of the product type composition plan 301 has been sent to the selling side 102. Next, the sales side 102 creates a product type composition plan for the sales side 102 based on this information as well, and updates the status value flag of the table information 302 (step 213). And the procurement side 101
The product type composition plan of the sales side 102 is displayed on the display device 7, and after examination, the operator inputs the changed value of the sales side product type composition plan, and the status value flag 540 of the table information 302 is set. Update (step 214). As a method of inputting this change value, the difference between the procurement side product type composition plan 301 and the product type composition plan created on the selling side may be input.
Here, if the status value flag of the table information 102 is changed, the changed value is transmitted to the procurement side 101 according to the flowchart of FIG. As a result of the examination, the processing device 1 on the procurement side 101, which has obtained the changed value, makes a correction based on the result of the adjustment with the sales side 302 to fix the product type composition plan, and updates the status value flag of the table information 302 (step 21
6).

FIG. 4 shows the case where the procurement side 101 and the sales side 102 carry out the product type period development plan, which is the next planning stage, based on the product type composition plan created in synchronization. Is. The basic processing flow is the same.

In the product variety period development plan, first, the procurement side 101 prepares a product variety period development plan 401 consisting of product types (ex. Skirt, suit) and weekly sales (unit: million yen) (step. 221). Step 221
When is finished, the status value flag of the table information 302 is updated. Next, when the status value flag of the table information 302 is changed, the control device 1 on the procurement side 101 transmits the contents of the product type composition plan 301 to the sales side by the procedure shown in the flowchart of FIG.

The selling side 102 acquires the relevant product type period development plan 401 (step 222), and the table information 3
The status value flag of 02 is updated. Next, based on this information as well, a product type period development plan for the sales side 102 is created (step 223) and the status value flag of the table information 302 is updated. After displaying and examining both product type period development plans, the operator inputs the changed value of the product type period development plan to the procurement side, and updates the status value flag of the table information 302. The procurement side 101 acquires the changed value (step 225) and updates the status value flag of the table information 302. Then, corrections are made according to the result of adjustment with the sales side 102, the product type period development plan is confirmed, and table information 3
The status value flag of 02 is updated.

In this way, the synchronized product composition plan of the procurement side and the sales side, and the products and sales plan of the entire product variety period development plan are fixed.

[0032]

As described above, according to the present invention, in the merchandise management system, in the merchandise plan on the procurement side and the sales plan on the sales side, information transmission and synchronization between both parties at each planning process stage are performed. Can be efficiently supported. As a result, the product plan on the procurement side and the sales plan on the sales side can be synchronized, and the accuracy of each plan can be significantly improved.

[Brief description of drawings]

FIG. 1 is a system configuration block diagram showing an embodiment of the present invention.

[Figure 2] Flow chart showing the procedure of product planning

FIG. 3 is a data structure diagram of the product type composition plan in FIG.

FIG. 4 is a data block diagram of a product type period development plan in FIG.

5 is a data configuration diagram of table information 302 in FIG.

FIG. 6 is a flowchart showing a synchronization support operation based on table information 302.

[Explanation of symbols]

 1, 5 Processing device 2, 6 Input device 3, 7 Display device 4, 8 Storage device

Claims (3)

[Claims] 1. A table information file for managing the progress status of a process in a system in which there are a plurality of processes of a product plan on the purchasing side and a process of a sales plan on the selling side, and a sales plan is prepared while synchronizing these processes. The table information is updated when each process on the procurement side or the sales side is completed, and if either side of the procurement side or the sales side does not receive the result of the other process when proceeding to the next process, A method for supporting the planning of a product sales plan, which is characterized by prohibiting proceeding to the process. 2. A storage area for a transfer necessity flag indicating whether or not to send a product plan to the other party is set in the table information file, and the transfer necessity flag is set when the table information file is updated. In case of the above, the system transmits the product plan to the other party, and the method for supporting the product sales plan planning according to claim 1. 3. A status value flag storage area indicating whether or not each process is completed is set in the table information file,
The method for supporting the planning of a merchandise sales plan according to claim 1, wherein an error is displayed when the status value flag of the previous process does not indicate the end when updating the table information file.