JP2006113728A - Purchase incentive allocation system, server for use therewith, method for allocating purchase incentive, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To accurately evaluate the results of business activities by letting sales representatives or a sales department more appropriately allocate data on the degree of contribution of incentives that wholesalers obtain from suppliers. <P>SOLUTION: A server 1 of a purchase incentive allocation system includes a sales result file 141 for storing data on the sales results of commodities; a sales result reflection process part 113 for totalizing, from the file 141, result data including not only the sale proceeds of the commodities for a certain period of time but also resulting values of the number of sales and the number of stores that sold the commodities, in association with a plurality of organizations within wholesalers, customers, and suppliers; a master for storing standard data about standards for the calculation of incentives based on resulting values of the sale proceeds, the number of commodities, and the number of stores that sold the commodities for a certain period of time that the system and the suppliers agreed upon; and an incentive calculation and allocation process part 114 for calculating incentive data for each organization from the totalized result data based on the standard data and for totalizing data on the incentives to each customer from the incentive data for each organization, so as to allocate the incentives. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a purchase reward distribution system, a server used therefor, a purchase reward distribution method, and a program, and more particularly to a purchase reward distribution system for wholesalers such as pharmaceuticals.

  In the wholesale business of pharmaceuticals, etc., the gross profit, which is the difference between the purchase amount from the supplier and the sale amount to the customer, is small, and the bounty from the supplier is the main source of income. In this case, the wholesaler's earned reward is distributed in proportion to the customer unit according to the sales amount (sales amount). The calculation processing related to the purchase bounty from the supplier to the wholesaler is usually performed by automatic calculation by a computer system (hereinafter referred to as “buy bounty for convenience of the computer system for performing such processing). Called the distribution system).

As prior art documents related to the present invention, there are the following.
JP 2002-297888 A

  However, in the conventional purchase reward distribution system, it has been difficult to quantitatively evaluate new business development and sales activities sold to many customers. This is because rewards are not simply proportional to the amount of purchases or sales, but the number of customers in a specific region is also used as a basis for calculating new customers, competing with competitors, etc. Because it is. In other words, proper evaluation of sales activities cannot be performed only by the sales amount or gross profit amount of sales representatives or sales departments.

  As a countermeasure, in order to properly evaluate the results of sales activities, the distribution data of the rewards acquired by the wholesalers from the suppliers is appropriately distributed to sales representatives and sales departments within the wholesalers (in-house). It is hoped that.

  In patent document 1, it is an application quantity adjustment server corresponding to business practices such as book transactions that convert profits to purchasers based on rewards or net quantities based on the application quantity, especially when multiple buyers place orders together Proposals have been proposed to facilitate adjustment of the order volume, efficiently secure bounties and discounts, and enable fair distribution. It is not used to evaluate the sales department within the wholesaler.

  The present invention has been made in consideration of such a conventional situation, and the contribution data of the rewards obtained from the supplier by the wholesaler is the sales representative or sales department in charge of the customer in the wholesaler. The purpose is to provide basic data to properly evaluate the results of sales activities.

  In order to achieve the above object, the purchase reward distribution system according to the present invention provides a reward to be obtained from a supplier of a product according to the sales performance of the product from a wholesaler to a plurality of customers over a certain period of time. Is a purchase bounty distribution system for wholesalers that distributes to each of a plurality of organizations in charge of the plurality of customers in the wholesaler, and stores sales result data of the product And associating not only the sales amount of the product for a certain period of time from the sales result file but also the actual data including the actual values of the number of items sold and the number of properties sold to the plurality of organizations, the customer, and the supplier. The reference data relating to the reward calculation standard based on the actual value of the sales amount, the number of sales, and the number of sales houses of the product in the predetermined period determined in advance between the aggregation processing means and the supplier Based on the master file to be delivered and the reference data in the master file, the bounty data for each of the plurality of organizations is calculated from the actual data tabulated by the tabulation means, and the bounty data for each of the plurality of organizations is calculated. An allocation processing unit that aggregates and distributes the bounty data for each of the plurality of customers and a unit that outputs the bounty data in a referable manner are provided.

  In the present invention, the master file includes, as the reference data, an achievement rate evaluation condition based on a ratio of a plan value and an actual value for each of the plurality of organizations, an amount evaluation condition based on a sales amount target value for each of the plurality of organizations, And further storing evaluation data related to each evaluation condition of the performance evaluation condition based on the target number of sales and the number of houses for each of the plurality of organizations, and the allocation processing means is based on the evaluation data by the counting means It is determined for each of the plurality of organizations whether or not the aggregated performance data satisfies each of the evaluation conditions, and reward data for each of the plurality of organizations is calculated for the organization that satisfies the evaluation conditions. May be.

  In the present invention, the master file further stores relief data relating to a predetermined relief condition as the evaluation data, and the allocation processing unit is configured to apply an organization that does not satisfy the evaluation condition based on the relief data. In addition, it may be further determined whether or not the actual data satisfies a predetermined relief condition, and the reward data for each of the plurality of organizations may be calculated for an organization that satisfies the relief condition.

  In the present invention, the aggregation processing means may identify the new customer and the continuous customer for the predetermined period as the customer, and aggregate the performance data in association with the new customer and the continuous customer.

  According to the present invention, the contribution data of rewards acquired by a wholesaler from a supplier is appropriately distributed by a plurality of organizations (salespersons, sales departments, etc.) in charge of customers in the wholesaler. , Provide basic data to correctly evaluate the results of sales activities.

  Next, a purchase reward distribution system according to the present invention, a server used in the system, a purchase reward distribution method, and a best mode for executing a program will be described in detail with reference to the drawings.

  FIG. 1 shows a wholesaler P2 of merchandise (in this embodiment, a medicine, etc.) using a purchase reward distribution system (also referred to as “expansion system”, “measure management system”, etc.) SS of this embodiment, and its Schematic of the relationship between the three suppliers P1 and the suppliers (pharmaceuticals, hospitals, etc. in the present embodiment) P3 as suppliers, and the flow of products and rewards It is shown.

  The wholesaler P2 is composed of a plurality of organizations (sales departments, branches, groups, etc.) P20 assigned to each area (region, prefecture, municipality, etc.), and measures between manufacturers (predetermined products for a predetermined period of time) To the customer P3 in each area according to each organization P20 unit, according to the sales performance (sales amount, number of units sold, number of houses sold) Purchase rewards are received from P1 (the solid line arrows in the figure indicate the flow of goods, and the dotted line arrows indicate the flow of rewards).

  As shown in FIG. 2, the purchase bounty allocation system SS is based on the bounty calculation standard negotiated with the manufacturer P1 as the supplier and the actual bounty data. The contribution degree data is created, and search, aggregation, and analysis are made possible. In this purchase bounty allocation system SS, 1) hold the bounty calculation standard for a certain period agreed with the manufacturer P1, and 2) the bounty calculation standard and actual purchase / sales results. Based on the data, a bounty for a certain period is calculated. 3) Based on the bounty calculation standard, the bounty for each manufacturer P1 is distributed to the unit of customer P20 who contributed to the acquisition. 4) PC for distribution result inquiry (Personal computer) The appropriateness of sales activities for each organization 20 while referring to the sales person in charge of the customer P3 and the contribution data for the acquisition of the rewards for each organization P20 to which the sales person belongs Can be evaluated.

  Here, definitions of terms (“comparison organization”, “evaluation item”, and “calculation item”) used in reward management by the purchase reward distribution system SS of the present embodiment will be described below.

  1) “Comparative organization” refers to an evaluation calculation group, and “evaluation organization” and “relief organization” are defined. "Evaluation organization" is the first comparison organization level, when the actual value and the plan value (planned value of the target organization preset in the evaluation organization level) is compared according to the evaluation item, and the evaluation item is cleared, It is an organizational level that earns rewards according to the calculation items. “Relief organization” refers to the level of the next comparative organization that should be relieved when the evaluation organization cannot clear the evaluation item and fails to achieve it. The actual value and the planned value (pre- When the “evaluation item” is cleared by comparing the set target values (planned values) of the target organization, the reward level is obtained according to the “calculation item”.

  2) “Evaluation item” is a reference value to be compared with the evaluation organization unit, and three items of “achievement rate evaluation”, “money evaluation”, and “result evaluation” are defined. “Achievement rate evaluation” is an evaluation based on an achievement rate represented by a ratio of a planned value and an actual value for each evaluation organization level. “Price evaluation” is an evaluation based on the absolute value target value for each evaluation organization level. “Actual evaluation” is an evaluation based on the actual value (number of buildings, number of houses) target absolute value for each evaluation organization level.

  3) “Calculation item” is the calculated and used value of the incentive award for organizations that have cleared “evaluation item”, and three types are defined: “reward rate calculation”, “reward unit price calculation”, and “additional reward calculation”. The “Reward rate calculation” is to obtain the result totaling result * designated reward rate of the evaluation organization. “Reward unit price calculation” is to acquire the result totaling result * designated reward unit price of the evaluation organization in the organization. “Additional reward calculation” is to acquire an additional reward amount in an organization.

  FIG. 3 is an overall configuration diagram of the purchase reward distribution system SS. The purchase reward distribution system SS shown in FIG. 3 is composed of a computer system that is integrated or individually incorporated in the in-house business processing system of the wholesaler P2, and in this embodiment, a database server (file server) in terms of hardware configuration. And a PC (personal computer) constituting a client machine communicably connected to the server 1 via a communication network such as LAN, WAN, etc. (generically referred to as “LAN3” for convenience in this embodiment). 2).

  FIG. 4 shows the internal configuration of the PC 2, and FIG. 5 shows the internal configuration of the server 1.

  4 includes a CPU 21, a ROM 22, a RAM 23, an HDD (hard disk drive) 24, a display 25 such as a liquid crystal display, a keyboard / mouse 26, and a communication I / F connected to the CPU 21 via a bus. (Interface) 27. The communication I / F 27 is composed of, for example, a LAN interface, and can communicate with the server 1 via the LAN 3. Software (OS, application program, etc.) executed by the CPU 21 is mounted on a recording medium such as the HDD 24. The software used in the present embodiment displays a GUI (Graphical User Interface) screen such as a predetermined designation / setting screen in cooperation with the operation of a database management system (not shown) executed on the server 1, Functions such as inputting sales performance data (see below) and item setting data in the database of the server 1 (see below) and referring to the actual data (distribution data) for acquiring bounty from the server 1 are installed. Yes.

  The server 1 shown in FIG. 5 includes a CPU 11, a ROM 12, a RAM 13, an HDD (Hard Disk Drive Device) 14, a display 15 such as a liquid crystal display, a keyboard / mouse 16, and a communication I / O connected to the CPU 11 via a bus. F (interface) 17. The communication I / F 17 is composed of a LAN interface, for example, and can communicate with the PC 1 via the LAN 3.

  A storage medium such as the HDD 14 stores an OS executed by the server 1 and an application program such as a database management system (DBMS), as well as a database 140 managed by the DBMS.

  As shown in FIG. 5, the database 140 includes a sales record file 141 (see FIG. 16 described later), a master related file 142, a measure totaling related file 143, and a reward totaling related file 144.

  As shown in the figure, the master-related file 142 includes a measure master 1421, a measure target product master 1422, a measure target organization master 1423, a measure target customer master 1424, a measure target evaluation / calculation master 1425, and a plan value master 1426. The FIG. 6 shows an internal configuration of each master of the master related file 1.

  In the measure master 1421, as shown in FIG. 6, items constituting one record include a plan number, a plan name, a manufacturer code, a measure period start month, a measure period end month, a measure result unit, a past record presence, The past performance period start month, past performance period end month, implementation organization, evaluation organization, relief evaluation organization, and allocation processing data are included. As shown in FIG. 6, the measure target product master 1422 includes plan number and product code data as items constituting one record. As shown in FIG. 6, the measure target organization master 1423 includes plan number and organization code data as items constituting one record. As shown in FIG. 6, the measure target customer master 1424 includes each data of a plan number and a customer code as items constituting one record. As shown in FIG. 6, the measure target evaluation / calculation master 1425 includes, as items constituting one record, a plan number, a relief category, an evaluation achievement rate, an evaluation amount, an evaluation result, a reward rate calculation, and a reward amount calculation. , And additional reward amount data. As shown in FIG. 6, the plan value master 1426 includes plan number, organization code, and plan value data as items constituting one record.

  The measure totaling related file 143 includes a measure customer totaling file 1431, a measure GR totaling file 1432, and a measure branch totaling file 1433 as shown in the figure. FIG. 7 shows an internal configuration of each file of the measure totaling related file 143.

  In the measure customer total file 1431, as shown in FIG. 7, items constituting one record include a plan number, a customer code, an employee code, an organization code, a screen number, an amount record, a number record, and a measure. Each data of the aggregation target flag is included. As shown in FIG. 7, the measure GR total file 1432 includes, as items constituting one record, data of a plan number, a group code, an amount record, a number record, and a house number record. As shown in FIG. 7, the measure branch total file 1433 includes, as items constituting one record, data of a plan number, a branch code, an amount record, a number record, and a house number record.

  As shown in the figure, the reward totaling related file 144 includes a measure organization-specific reward file 1441, a measure customer-specific reward file 1442, and a manufacturer customer-specific reward file 1443. FIG. 7 shows an internal configuration of each file of the reward totaling related file 144.

  As shown in FIG. 7, the measure-organization-based reward file 1441 includes plan number, processing branch number, organization code, manufacturer code, and reward amount data as items constituting one record. As shown in FIG. 7, the reward customer-specific reward file 1442 includes, as items constituting one record, plan number, processing branch number, customer code, manufacturer code, and reward amount data. . As shown in FIG. 7, the maker customer-specific reward file 1443 includes maker code, customer code, and reward data as items constituting one record.

  Next, various specification / setting screens on the PC 2 side used for setting each item of the master related file 142 in the database 140 will be described with reference to FIGS.

  FIG. 8 shows the relationship between the various designation / setting screens on the PC 2 side and the master-related files 142 on the server 1 side that are set as items. As shown in FIG. 8, various specification / setting screens displayed on the display 25 on the PC 2 side include target product, target period, totaling unit specification screen W1, target organization (area), target customer (business type) specification screen. W2, a reward acquisition evaluation / reward amount calculation standard designation screen W3 and its evaluation / calculation item definition screen W4, and a plan value setting screen W5 are included. Hereinafter, each screen W1-W5 is demonstrated.

  FIG. 9 shows a display example of the target product, the target period, and the total unit designation screen W1.

  The designation screen W1 shown in FIG. 9 can be displayed by pressing the “main” button A10 among various buttons arranged at the top of the screen, for example. The “plan number” A11 displayed on the lower side of the various buttons is a number (unique key) for uniquely identifying the measure. Measure-related masters related to measures (measure master, measure target product master, measure target organization master, measure target customer master, measure target evaluation / calculation master, plan value master), measure result summary file (measure customer summary file, The measure GR total file, the measure branch total file) and the allocation data (the measure customer-specific reward file, the measure organization-specific reward file, and the manufacturer customer-specific reward file) can all be combined with the plan number. “Plan name” A12 is a measure name corresponding to “Plan number” A11. “Manufacturer code” A13 is the code of the manufacturer that implements the measure. “Measure period” A14 is a target period for measure result aggregation (specified in “FROM” − “TO” on a monthly basis). “Measures performance unit” A15 is the aggregation unit (amount, number, and number of houses) when implementing measure results, and the amount can be counted in multiple price systems (actual price, partition price, desired sales price, etc.) is there. “Past record presence / absence” A16 determines the record presence / absence during the past record period for each customer. Here, “new” customers are those that have no actual customer results in the past performance period and have actual results in the policy period, and “continuous” customers are those who have actual results in both the past performance period and the policy period. It shall refer to each that is present. The “past performance period” A17 is used to designate a past period when the past performance presence / absence determination is performed (designated by “FROM” − “TO” in units of months). “Target code” A18 in the list item at the bottom of the screen is the product code of the product that is the target of the measure.

  The main master related files 142 whose items are set on the designation screen W1 shown in FIG. 9 are a measure master 1411 and a measure target product master 1422 (see FIG. 8).

  FIG. 10 shows a display example of the target organization (area) and target customer (business type) designation screen W2.

  The designation screen W2 shown in FIG. 10 can be displayed by pressing an “organization / customer” button A20 among various buttons arranged at the top of the screen, for example.

  A plan number, a plan name, a manufacturer code, a measure name, and the like designated on the designation screen W1 are displayed on the lower side of the various buttons arranged at the top of the screen. Furthermore, the “implementing organization” A21 displayed on the lower side corresponds to the selected organization level of the organization to be the target of the measure, and in this embodiment, designation is made up to nationwide, local, prefecture, city, branch, group (GR). Is possible. “Organization code” A22 corresponds to the organization that is the target of the measure, and can be designated by the organization code at the organization level designated by the implementing organization. For example, Kanto, Kansai, China, etc. can be set when the implementation organization = 'region', and Tokyo, Kanagawa, Chiba, Osaka, Kyoto, Hiroshima, etc. can be set when the implementation organization = 'prefecture'. The “customer code” A23 corresponds to the customer as the measure target, and the customer can be set by the customer code assigned to each customer.

  Main master-related files 142 whose items are set on the designation screen W2 shown in FIG. 10 are a measure target organization master 1423 and a measure target customer master 1424.

  FIG. 11 shows a display example of an evaluation / calculation item definition screen W4 for setting evaluation / calculation items on the designation screen W3. The designation screen W3 shown in FIG. 11 can be displayed by pressing an “evaluation / calculation” button A30 among various buttons arranged at the top of the screen, for example.

  “Evaluation organization” A31 designates the organization level to be compared with the condition of the evaluation item (national, local, prefecture, city, branch, group (GR)). This is the planned value setting organization level when there is no relief evaluation organization designation.

  The “relief evaluation organization” A32 is designated when the evaluation organization does not achieve the condition of the evaluation item and the evaluation organization is compared with the evaluation organization. This can specify up to GR under the evaluation organization (region, prefecture, city, branch, GR). When a relief evaluation organization is designated, the planned value setting is at the designated organization level.

  “Allocation process” A33 displays a confirmation flag as to whether the allocation process has been automatically calculated by the system.

  Of the list items displayed at the bottom of the screen, “Relief Category” A34 indicates which evaluation / calculation criteria to specify between the evaluation organization and the relief evaluation organization, or the organization level (national, local, prefecture, city, branch). , GR).

The “evaluation item” displayed at the bottom of the screen sets a comparison value with the actual value for each relief category, and can be set using the “evaluation item designation” setting area A42 of the definition screen W4 shown in FIG. It has become.
Among these, “Evaluation Achievement Rate” A35 is a value for setting a percentage with respect to the actual value and the target. “Evaluation amount” A36 is used to set a comparison with the actual value as an absolute amount. This is effective when the measure performance unit is a monetary amount. “Evaluation results” A37 is used to set the comparison with the actual values by the absolute value of the number of houses and the number of houses. This is effective when the measure performance unit is the number of houses or the number of houses.

  The “calculation item” displayed at the bottom of the screen sets a reward calculation value that can be obtained when the evaluation item condition is achieved for each relief category. This can be set using the “calculation item designation” setting area A43 on the definition screen W4 shown in FIG. Among these, “reward rate calculation” A38 sets the reward rate with respect to the actual value in%. For example, if the actual value is “1 million” and the reward rate calculation is “10%”, then 100,000 is acquired by the evaluation achievement organization. This is effective when the measure result unit is a monetary amount. “Reward amount calculation” is to set a reward unit price for the actual value. For example, if the actual value is “100 (eaves)” and the reward calculation is “10,000 yen”, 1 million is acquired by the evaluation achievement organization. This is effective when the measure performance unit is the number of houses or the number of houses. “Additional bounty amount” is to set a uniform winning bounty regardless of the actual value.

  The main master-related files 142 whose items are set on the designation screen W3 shown in FIG. 11 and the definition screen W4 shown in FIG. 12 are a measure master 1421 and a measure target evaluation / calculation master 1425.

  FIG. 13 shows a display example of the plan value setting screen W5.

  The designation screen W2 shown in FIG. 13 can be displayed by pressing the “plan” button A50 among various buttons arranged at the top of the screen, for example.

  “Organization code” A51 displayed on the lower side of various buttons arranged at the top of the screen is used when calculating the achievement rate of the above-mentioned designated screen W3 and rewards. Necessary organization codes can be set from organizations and relief organizations. For example, when setting such as implementing organization = region, implementing organization code = China, Shikoku, Kyushu, evaluation organization = national, relief organization = prefecture, etc., the planned value can be set for each prefecture (set for 16 records). . That is, 5 prefectures in China (Tottori, Shimane, Okayama, Hiroshima, Yamaguchi), 4 prefectures in Shikoku (Tokushima, Kagawa, Ehime, Kochi), 7 prefectures in Kyushu (Fukuoka, Saga, Nagasaki, Kumamoto, Oita, Miyazaki, Kagoshima) ).

  Of the items arranged at the bottom of the screen, “Amount” A52 sets a target amount value for each organization when the measure result unit is an amount. “Number” A53 sets a target number for each organization when the measure result unit is the number. “Number of eaves” A54 sets a target eaves value for each organization when the measure result unit is the number of eaves.

  The main master-related file 142 whose items are set on the setting screen W5 shown in FIG. 13 is the plan value master 1426.

  FIG. 14 shows a processing flowchart in the case of setting each item (master content) of the master related file 142 using the screens W1 to W6 in the purchase reward distribution system SS of the present embodiment. In FIG. 14, the operator operates a keyboard / mouse to display a predetermined designation / setting screen among the screens W1 to W6 on the screen of the display 25 on the PC 2 side (step St1), and data is displayed according to this screen. Input / selection is performed (step St2). Based on the input / selected data, setting item data of a predetermined master among the master-related files 142 of the database 140 stored in the HDD 14 on the server 1 side (see above) Is set (step St3).

  FIG. 15 shows a reward acquisition process executed on the server 1 side using the master related file 142 in which the master contents are set in the process shown in FIG. 14 and the actual sales performance data input from the PC 2 side. Is conceptually described.

  As shown in FIG. 15, the server 1 includes a master setting processing unit 111, a sales result data input processing unit 112, a sales result reflection processing unit 113, a reward calculation allocation processing unit 114, and a reward as functional processing units. An aggregation processing unit 115 and a reward acquisition contribution level data reference processing unit 116 are included. Each of these processing units 111 to 116 achieves each function when the CPU 11 shown in FIG. 5 executes the control program, and corresponds to each processing step of the control program executed by the CPU 11. is there. Here, the sales performance reflection processing unit 113 is the main part of the aggregation processing means of the present invention and the processing steps corresponding thereto, and the reward calculation allocation processing unit 114 and the reward aggregation processing unit 115 are the allocation processing of the present invention. The main part of a means and the processing step corresponding to this is comprised, respectively.

  The master setting processing unit 111 sets data (items) of the corresponding master related file 142 based on various item setting data input on the PC 2 side through each of the screens W1 to W6.

  The sales record data input processing unit 112 sells the sales record data (slip number, slip details, slip date, customer code, organization code, product code, quantity, and sales amount) input on the PC 2 side in the database 140. The result file 141 is input and stored.

  The sales record reflection processing unit 113 converts the sales record data stored in the sales record file 141 into the measure information record related master (measure measure master 1421, measure target product master 1422, measure target organization (area) master in the master related file 142. 1423, based on the contents set in the measure target customer master 1424), for each measure (plan number), customer (customer code), organization (organization code), group (group code), branch (branch code) ) Are summed up and the result of the amount of money, the number of records, and the number of houses are reflected in the measure total file (the measure customer file 1431, the measure group total file 1432, and the measure branch count file 1433).

  The reward calculation allocation processing unit 114 calculates the policy information reward related master (measures) from the master related file 142 from each data of the measure total file (measure customer file 1431, measure group total file 1432, measure branch total file 1433). Based on the evaluation contents set in the master 1421, measure target evaluation / calculation master 1425, and plan value master 1426), the reward amount data for each measure (plan number) and organization (organization code) is calculated to give a reward Create a reward file 1441 for each measure / organization in the measure-related file 144 and distribute the reward data calculated for each measure and organization to each measure (plan number) and customer (customer code). A measure customer-specific reward file 1442 of the related file 144 is created.

  The reward aggregation processing unit 115 aggregates the rewards allocated for each measure and customer into the rewards for each manufacturer (manufacturer code) and customer (customer code), and the manufacturer customer in the reward aggregation related file 144 Another reward file 1443 is created. In this case, when data correction occurs in the same measure (same plan number), color-coded data (eg, red and black data) that can visually recognize the correction portion can be generated at the same time.

  The reward acquisition contribution data reference processing unit 116 is related to the contribution data (distribution data) of the earned reward generated as described above on the PC side 2 in response to a reference instruction from the PC 2 side, that is, related to the reward aggregation. Each file data of the file 144 (the measure organization-specific file 1441, the measure customer-specific reward file 1442, the manufacturer customer-specific file 1443) is supplied. Thereby, on the PC side 2, the contents of the file 144 can be displayed on the screen of the display 25 or can be printed out for easy confirmation.

Here, specific processing examples by the sales performance reflection processing unit 113, the reward calculation allocation processing unit 114, and the reward aggregation processing unit 115 will be sequentially described.
(Sales result reflection processing)
First, with reference to FIGS. 16 and 17, a specific example of the sales performance reflection process by the sales performance reflection processing unit 113 will be described.

  FIG. 16 shows the internal structure of the sales record file 141, and FIG. 17 explains the details of the processing flow of the sales record reflection processing unit 113.

  As shown in FIG. 17, the sales record reflection processing unit 113 performs a sales result reflection process 113-1 and a measure determination process 113-2. Hereinafter, both processes 113-1 and 113-2 will be described.

  First, in the sales record reflecting process 113-1, the data generated by the sales record data input processing unit 112 is read, and if it is data to be measured, the data is output to the measure customer total file 1431 and the measure determination work file 145. To do. As shown in FIG. 17, the measure determination work file 145 includes data of a plan number, a customer code, an employee code, an organization code, and a screen number as items constituting one record.

  Specific processing steps of the sales performance reflecting process 113-1 are as follows.

  Step A1) First, data is fetched from the sales record file 141. As shown in FIG. 16, in the sales record file 141, as shown in FIG. 16, the slip number, slip details, slip date, customer code, organization code, product code, quantity, and sales amount are included. Each data is included.

  Step A2) Next, the operation policy is checked. In this process, the slip date is within the measure period start month to the measure period end month by referring to the slip date data in the sales performance file 141 and the measure period start month and measure period end month data in the measure master 1421. If it is included, plan number data corresponding to the data of the measure period start month and the measure period end month is acquired from the measure master 1421. Similarly, with reference to the slip date data of the sales record file 141 and the past record period start month and past record period end month data of the measure master 1421, the slip date is from the past record period start month to the past record period end month. If it is included, plan number data corresponding to the data of the past performance period start month and the past performance period end month is also acquired from the measure master 1421 for new / continuation determination.

  In addition, when the plan number data corresponding to the data from the measure period start month to the measure period end month is acquired under the condition of step A2), the screen number in the measure customer total file 1431 is set to “1”. When the plan number data corresponding to the data from the past actual period start month to the past actual period end month is acquired under the condition of step A2), the screen number in the measure customer total file 1431 = '2' Set.

  Step A3) Next, the target product is checked. In this process, the measure target product master corresponding to the target plan number and product code using the plan number data acquired in step A2) and the product code data in the sales record file 141. Whether or not data 1422 (plan number and product code) exists is searched, and the target measure of the corresponding product is checked based on the search result.

  Step A4) Next, the target organization is checked. In this process, the plan target organization (corresponding to the target plan number and organization code) using the plan number data acquired in the process of step A3) and the organization code data in the sales record file 141 are used. Area) Whether or not the data (plan number and organization code) of M1423 exists is searched, and the target measure of the corresponding organization is checked based on this search result.

  Step A5) Next, the target customer is checked. In this process, using the plan number data acquired in step A4) and the customer code data in the sales record file 141, the target of the measure corresponding to the target plan number and customer code. Whether or not the data (plan number and customer code) of the customer master 1424 exists is searched, and the target measure of the customer is checked based on the search result.

  Step A6) Next, the measure customer total file 1431 is edited. In this process, the data of the sales record file 141 corresponding to all the conditions of the above steps A2) to A5) are added or corrected to the measure customer total file 1431. That is, referring to each data of the corresponding project number + customer code + screen number, the data of the measure customer total file 1431 corresponding to these data is searched, and when the search data does not exist, the sales record file 141 is searched. Data is added as new data of the measure customer total file 1431. If search data exists, the data of the sales record file 141 is updated as the update data of the measure customer total file 1431 (amount and number are added). To do.

  Further, when the past record presence / absence of the measure master 1421 = “1” (present), a plan number, a customer code, an employee code, an organization code, and a screen number are set in the measure determination work file 145, and determination is necessary. Outputs certain data.

  Next, in the measure determination process 113-2, new or continued data determination is performed on the data output to the measure determination work file 145, and the measure GR total file 1432 and the measure branch count are calculated from the measure target customer count file 1431. Data aggregated in the file 1433 is created.

  Specific processing steps of the measure determination processing 113-2 are as follows.

  Step B1) First, data is taken from the measure determination work file 145.

  Step B2) Next, measure customer tabulation is determined. In this process, the plan number in the data acquired in the process of step B1) is used to search the data of the measure master 1421 corresponding to this, and based on this, the presence / absence of past results is determined.

  As a result, when there is a past record, the plan number and customer code data of the data acquired in the process of step B1) are referred to and the measure customer total file 1431 corresponding to this is searched. As a result, in the data of the measure customer totaling file 1431 corresponding to the target plan number and customer code, if both screen numbers = '1' and '2' exist, measure customer totals as continuous customers If the measure aggregation target flag in the file 1431 is set to “1” and only the screen number = “1” exists, the measure aggregation target flag in the measure customer aggregation file 1431 is set to “2” as a new customer. To do.

  If there is no past record, reference is made to the data of the plan number and customer code of the data acquired in the process of step B1), and the data of the measure customer total file 1431 corresponding thereto is present. If no data is found as a result, “1” is set in the measure aggregation target flag in the measure customer summary file 1431 as a new customer.

  Since a new customer or a continuous customer can be determined based on the value “1” or “2” of the measure aggregation target flag set as described above, the data of the measure customer summary file 1431 described later is thereby obtained. It is possible to perform a process such as tabulation while distinguishing whether the customer is a new customer or a continuous customer during processing using.

  Step B3) Next, measure groups are tabulated. In this process, grouping is performed for each group using the plan number and organization code of the measure customer total file 1431 as a key to create a measure GR total F1432.

Step B4) Then, measure branch offices are tabulated. In this processing, the measure branch total file 1431 is created by grouping each branch with the plan number and organization code data as keys from the measure GR total F1432 created in the process of step B3).
(Reward calculation allocation process)
Next, a specific example of reward calculation allocation processing by the reward calculation allocation processing unit 114 will be described.

  The reward calculation allocation processing unit 114 branches the process according to the measure type (plan number), branches the processing pattern according to each item content of the measure target evaluation / calculation master 1425, and rewards for the evaluation calculation group unit (alloance). Get the amount earned. As a result, if different achievement ratios and volumes are mixed within the same evaluation calculation group, the evaluation / calculation process will be performed according to the following procedure.

  That is, the reward calculation allocation processing unit 114 obtains evaluation data (evaluation conditions: achievement rate evaluation, monetary evaluation, performance evaluation) for each evaluation calculation group from the measure target evaluation / calculation master 1425 and meets the evaluation conditions. In such a case, the bounty acquisition process is performed only once in the target evaluation calculation group. If the evaluation conditions are met, the data of the next evaluation calculation group is used. If the evaluation conditions are not met, check based on the conditions of the relief category (recovery for achievement rate, relief for volume, etc.). Specifically, the following processing is performed.

  Step C1) First, the evaluation organization based on the measure master 1421 is tabulated, the evaluation conditions are confirmed, the reward is calculated in the achievement organization that satisfies the evaluation conditions (calculation is performed for each unit of the result of the corresponding measure), and the achievement organization Remuneration calculation in the subordinate group (calculation is performed for each result aggregation unit of the corresponding measure) and reward calculation in the customer under the achievement organization (calculation is performed for each result calculation unit of the corresponding measure) respectively (normally achieved) Check each item).

  Step C2) Next, if the evaluation condition is not achieved in each organization, the organization under the corresponding organization performs the check under the condition of the next relief category, and performs relief processing up to the relief assessment organization level based on the measure master 1421. To implement. In this case as well, check the evaluation conditions, calculate the rewards for the achievement organization that meets the conditions of the relief category (calculation is performed for each unit of actual results of the corresponding measure), and calculate the rewards for the group under the achievement organization (for the relevant measure) Calculations are made for each result aggregation unit), and rewards are calculated for the customers under the organization that achieves it (calculation is performed for each result calculation unit of the relevant measure) (recovery achievement items confirmed).

  Step C3) Finally, the evaluation condition of the volume is confirmed (confirmation at the volume) for the organization that does not meet the evaluation condition even in the relief.

  Here, regarding the steps C1) to C3), a more specific procedure of the evaluation process will be described.

  Here, achievement rate relief is 100% and 90%, there is organization relief, and there is volume relief, and the master (M) content is measure M: evaluation organization = 4 (part), measure M: relief evaluation organization = 6 (Group) As an organizational form, one department (A sales department: 11AA00000), three branches (A-1 branch: 11AA01000, A-2 branch: 11AA02000, A-3 branch: 11AA03000), seven groups (A -1-1GR: 11AA01010, A-1-2GR: 11AA02020, A-1-3GR: 11AA03030, A-2-1GR: 11AA02010, A-2-2GR: 11AA02020, A-3-1GR: 11AA03010, A-3 -2GR: 11AA03020) will be described.

  Step D1) First, it is confirmed whether or not the achievement rate in the A sales department satisfies the condition of 100%. As a result, when the condition of the achievement rate of 100% is satisfied, the bounty of the corresponding record in the bounty total calculation related file 144 is acquired and the existence of the next evaluation calculation group is checked.

  Step D2) When the condition of the achievement rate 100% is not satisfied in the A sales department in the processing of the above step D1), it is checked whether or not the condition of the achievement ratio 80% is satisfied in the A sales department. If the achievement rate of 80% is satisfied, the bounty of the corresponding record in the bounty total calculation related file 144 is acquired and the existence of the next evaluation calculation group is checked.

  Step D3) Whether or not the condition of the achievement rate of 80% is not satisfied in the A sales department in the processing of the above step D2), whether or not the condition of the achievement rate of 100% is satisfied in the An branch under the A sales department (Intermediate organization relief assessment). As a result, when the An branch office data exists and the An branch satisfies the condition of the achievement rate of 100%, the bounty of the corresponding record in the bounty total calculation related file 144 is acquired, The achievement rate of the next branch (A- (n + 1) branch) is checked in the process of D3). If there is no An branch office data, the presence of the next evaluation calculation group is checked.

  Step D4) When the condition of the achievement rate 100% is not satisfied at the An branch in the processing of the above step D3), it is checked whether or not the condition of the achievement rate 80% is satisfied at the An branch ( Intermediate organization relief assessment). As a result, when the achievement rate of 80% is satisfied, the bounty for the corresponding record in the bounty total calculation related file 144 is acquired, and the process returns to the above 3) to return to the next branch (A- (n + 1) branch ) Check the achievement rate.

  Step D5) If the condition of the achievement rate 80% is not satisfied at the An branch in the processing of the above step D4), the condition of the achievement rate 100% is satisfied at the Anm group under the An branch. Check if it is. As a result, when the An branch office data exists and the condition of the achievement rate of 100% is satisfied in the Anm group, the bounty of the corresponding record in the bounty total calculation related file 144 is acquired, In the process of step D5), the achievement rate of the next group (A−n− (m + 1) group) is checked. If there is no A-n branch data, the achievement rate of the next branch (A- (n + 1) branch) is checked.

  Step D6) Whether or not the condition of the achievement rate of 100% is satisfied in the Anm group when the condition of the achievement rate of 100% is not satisfied in the Anm group in the process of Step D5) above. Confirm. As a result, when the achievement rate of 80% is satisfied, the bounty for the corresponding record in the bounty totaling file 144 is acquired, and the process returns to the above step D5) to return to the next group (An- ( m + 1) Check the achievement rate of group).

  Step D7) If the condition of the achievement rate of 80% is not satisfied in the Anm group in the process of Step D6), the volume of the Anm group is checked, and the volume value is calculated. Returning to the process of step D5), the achievement rate of the next group (A−n− (m + 1) group) is checked.

  Next, a specific example of the calculation process after the evaluation process will be described.

  Here, achievement rate relief is 100% and 90%, there is organization relief, there is volume relief, and the master (M) contents are measure M: evaluation organization = 4 (part), measure M: relief evaluation organization = 6 ( Group), measure evaluation / calculation M: reward rate calculation plan number branch number = 01, measure evaluation / calculation M: reward rate calculation item group = 01, measure evaluation / calculation M: reward rate calculation aggregation code = 1, Measure target evaluation / calculation M: Reward rate = 3, Measure target evaluation / calculation M: Reward amount calculation plan number branch number 02, Measure target evaluation / calculation M: Reward amount calculation item group = 01, Measure target evaluation / calculation M : Reward amount calculation aggregation code = 1, measure target evaluation / calculation M: reward unit price = 100, measure target evaluation / calculation M: additional reward amount = 1,000,000, one organization (A sales department: 11AA00000) Two branches (A- 1 branch: 11AA01000, A-2 branch: 11AA02000), 5 groups (A-1-1GR: 11AA01010, A-1-2GR: 11AA02020, A-1-3GR: 11AA03030, A-2-1GR: 11AA02010, A 2-2GR: 11AA02020) will be described.

  Here, as a result of the evaluation process, a case will be described in which one section (A sales department) has not achieved the evaluation condition, and the branch A-1 has achieved the evaluation condition by branch relief.

  Step E1) First, a reward amount (allowance) acquisition amount of the branch that has been achieved is calculated.

  In this calculation, if the reward rate designation is set in the measure evaluation / calculation master 1425, the plan number, item group (hereinafter referred to as item GR), and aggregation code (aggregation CD) designated for calculation at the corresponding branch are accordingly determined. The measure branch total file 1433 is searched for, and the value obtained by multiplying the acquired amount actual value by the reward is output to the measure organization-specific reward file 1441 (organization-acquired amount total file).

  If the reward unit price designation is set in the measure evaluation / calculation master 1425, the measure branch total file 1433 is searched by designating the plan number, item GR, and aggregation CD designated for calculation at the corresponding branch. Then, a value obtained by multiplying the acquired actual number of buildings and actual number of houses by the reward unit price is output to a measure organization-specific reward file 1441 (organization-based earned amount totaling file).

  Furthermore, if additional reward designation is set in the measure evaluation / calculation master 1425, the measure branch summary file will be created using the plan number, item GR, and consolidated CD as a key in the organization that cleared the conditions if there are evaluation conditions. After searching 1433, the amount of acquisition of the corresponding branch is calculated, and then output to the measure organization-specific reward file 1441 (measure organization-specific total file).

  Step E2) Next, the amount of award (allowance) earned for each group under the branch that has been achieved is calculated.

  In this calculation, if the reward target designation is set in the measure evaluation / calculation master 1425, the plan group, item GR, and aggregation CD designated for calculation are designated for the group under the corresponding branch, and the measure group is aggregated. The file 1432 is searched, and a value obtained by multiplying the acquired amount actual value by the reward is output to a measure organization-specific reward file 1441 (group-acquired amount total file).

  In addition, if the reward unit price designation is set in the measure evaluation / calculation master 1425, the measure group total file 1432 is designated by designating the plan number, the item GR, and the aggregate CD designated for calculation in the group under the branch. And the value obtained by multiplying the acquired actual value and the actual number of houses by the reward unit price is output to the reward file 1441 for each measure organization (acquired total file for each group).

  In addition, if additional reward designation is set in the measure evaluation / calculation master 1425, the measure group total file with the plan number, item GR, and consolidated CD as the key in the organization that cleared the conditions if there are evaluation conditions. 1432 is searched, the amount of acquisition of the corresponding group is calculated, and it outputs to the measure organization reward file 1441 (group acquisition amount total file).

  Step E3) Next, the amount of award (alloonce) earned by each customer under the branch that has been achieved is calculated.

  In this calculation, if the reward rate designation is set in the measure evaluation / calculation master 1425, the plan specialty, the item GR, and the aggregated CD are designated by the customer under the branch according to this, and the measure specialty is designated. The destination total file 1431 is searched, and the value obtained by multiplying the acquired actual money value by the reward is totaled and output to the measure customer reward file 1442 (CO total work file).

  In addition, when the reward unit price designation is set in the measure target evaluation / calculation master 1425, the measure customer total file 1431 is specified by designating the plan number, item GR, and aggregation CD designated for calculation at the customer under the branch. A value obtained by multiplying the acquired actual number value and the actual number of houses by the reward unit price is totalized and output to a measure customer-specific reward file 1442 (CO total work file).

Furthermore, when additional reward designation is set in the measure evaluation / calculation master 1425, measure groups are aggregated using the plan number, item GR, and consolidated CD as a key in an organization that has cleared the conditions if there are evaluation conditions. After searching the file 1432 and calculating the acquisition amount of the corresponding group, calculate the actual ratio for each customer with the measure customer actual result file for the customers under the corresponding group, and propose the ratio from the total amount of the earned amount of the entire group The divided values are totaled and output to a measure customer incentive file 1442 (CO totalization work file).
(Bonus collection process)
Next, a specific example of the reward aggregation processing by the reward aggregation processing unit 115 will be described.

  FIG. 18 explains the details of the processing flow of the reward aggregation processing unit 115.

  As shown in FIG. 18, the reward aggregation processing unit 115 executes a measure customer reward difference aggregation process 115-1 and a reward manufacturer aggregation process 115-2. Hereinafter, both processes 115-1 and 115-2 will be described.

  First, in the policy customer reward difference totaling process 115-1, the policy customer information to be aggregated into the data of the manufacturer customer specific reward F1443 is extracted from the data of the policy customer specific reward file 1443 that has been aggregated as described above. If a reward amount for the measure customer is the same as the previous one, the difference is output to the measure customer-specific reward summary WKF (work file) 147 if not. As shown in FIG. 18, this measure customer-specific reward summary WKF 147 includes data of a plan number, customer code, employee code, organization code, and screen number.

  Specific processing steps of the measure customer reward difference totaling process 115-1 are as follows.

  Step F1) First, the value of the processing branch number (in this example, “numerical value 1”) which is the reward processing target data is acquired from the parameter master (M) 146. In the parameter master 146, as shown in FIG. 18, a key and a numerical value 1 (processing branch number) are set in advance in association with each other.

  Step F2) Next, the data of the measure customer-specific reward file 1443 having the numerical value 1 acquired in the process of Step F1) as the process branch number is acquired. Here, if there is data smaller than the numerical value 1 of the processing branch number (F1) in the corresponding measure (plan number), the reward amount for the previous portion and the current portion is acquired, and the previous reward amount (processing smaller than the numerical value 1) is acquired. The difference between the branch number data) and the current reward amount (the same processing branch number data as the numerical value 1) is obtained, and is output to the measure customer-specific reward summary WKF 147 for each measure (plan number), customer, and manufacturer. This process ends when all the policy customer-specific reward files 1443 smaller than the numerical value 1 acquired in the process of step F1) with the same process branch number + same process branch number (plan number) are processed.

  Next, in the bounty manufacturer totaling process 115-2, data is collected for each manufacturer from the per-customer-specific reward totaling WKF 147, and the data is output to the manufacturer-customer-specific reward file 1443.

  The specific processing steps of the bounty maker aggregation processing 115-2 are as follows.

  Step G1) First, the data in the measure-customer-based reward aggregation WKF 147 are grouped and summed using the manufacturer code and customer code to obtain the total value of the reward amount.

  Step G2) Next, the current processing branch number is added to the data acquired in Step G1) and output to the manufacturer customer-specific reward file 1443.

  Therefore, according to the present embodiment, the following effects can be obtained.

  1) As a measure result totaling unit, not only “amount” but also “number” and “number of houses” can be totaled. It is also possible to aggregate new customers and continue customers during a specific period.

  2) As a reward acquisition aggregation unit, it is possible to aggregate “reward rate: ratio to actual results”, “number: unit price per house”, and “uniform reward amount”. It is possible to specify a certain award that is not related to the actual value, as well as to collect the award amount according to the actual aggregation unit.

  3) Allocation of the reward amount can be managed up to the total value of customer + manufacturer. This purchase bounty allocation system can manage customers + measures. Allocation data can be used as a judgment for manufacturers with large profits, organizations with high corporate contributions, and employees.

  4) As an allocation method from the corresponding organization to the customer for the rewards, the apportionment can be carried out according to the results and the reward aggregation unit, not just the apportionment method based on sales. Thus, by implementing a more accurate apportionment method corresponding to the actual value, it is possible to improve the reliability as valid evaluation data.

  5) Evaluation units can be evaluated by “achievement rate evaluation”, “amount absolute value evaluation”, and “number absolute value evaluation”.

  In the above embodiment, a case has been described in which the purchase reward distribution system is configured by a network system having a plurality of PCs and one server connected to the network. For example, a plurality of servers may be used. In addition to a network system, a stand-alone computer machine can be used. In addition, various modifications can be made within the scope of the present invention, and these modifications are also included in the scope of the present invention.

  The present invention relates to a purchase reward distribution system for a wholesaler of pharmaceuticals and other wholesalers that obtains purchase rewards from suppliers of products in accordance with the same business practice, and a server using the same It can also be applied to purchase reward distribution methods and programs.

It is a conceptual diagram which illustrates typically the relationship between the wholesaler using the purchase reward distribution system which concerns on embodiment of this invention, a supplier, and a customer. It is a figure explaining the outline | summary of the purchase reward distribution system which concerns on embodiment of this invention. It is the schematic explaining the whole structure of the purchase reward distribution system which concerns on embodiment of this invention. It is a schematic block diagram which shows the internal structure of PC shown in FIG. It is a schematic block diagram which shows the internal structure of the server shown in FIG. It is a figure which shows the internal structure of the master relevant file shown in FIG. It is a figure which shows the internal structure of the measure totaling related file and bounty totaling related file (allocation data) shown in FIG. It is a figure explaining the relationship between a PC screen and a master relevant file. It is a figure explaining the example of a display of the object goods, object period, and total unit designation screen which are shown in FIG. It is a figure explaining the example of a display of the object organization (area) and object customer (business condition) designation screen shown in FIG. It is a figure explaining the example of a display of the reward acquisition evaluation and reward amount calculation reference | standard designation | designated screen shown in FIG. It is a figure explaining the example of a display of the evaluation and calculation item definition screen which sets the evaluation and calculation item in FIG. It is a figure explaining the example of a display of the plan value setting screen shown in FIG. It is a process flowchart for setting the master content of a master related file. It is a conceptual diagram explaining the flow of the reward acquisition process by a server. It is a figure which shows the internal structure of a sales performance file. It is a figure explaining the detail of the sales performance process part shown in FIG. It is a figure explaining the detail of the reward collection process part shown in FIG.

Explanation of symbols

1 Server 2 PC
111 Master Setting Processing Unit 112 Sales Result Data Input Processing Unit 113 Sales Result Reflection Processing Unit 114 Reward Calculation Allocation Processing Unit 115 Reward Reimbursement Aggregation Processing Unit 116 Reward Acquisition Contribution Data Reference Processing Unit 141 Sales Result File 142 Master Related File 143 Measure aggregation related file 144 Bounty calculation related file (allocation data)
145 Measure determination work file 146 Parameter master 147 Measures customer-specific reward summary work file 1421 Measure master 1422 Measure target product master 1423 Measure target organization (area) master 1424 Measure target customer master 1425 Measure target evaluation / calculation master 1426 Plan value master 1431 Measure Customer Total File 1432 Measure Group Total File 1433 Measure Branch Total File 1441 Measures Organization Reward File 1442 Measure Customer Reward File 1443 Manufacturer Customer Reward File SS Purchase Reward Distribution System W1 Target Product, Target Period , Total unit designation screen W2 Target organization (area), target customer (business category) designation screen W3 Bounty acquisition evaluation / reward amount calculation criteria designation screen W4 Evaluation / calculation item definition screen W5 Plan value setting screen

Claims (10)

A reward to be obtained from a supplier of the product according to the sales performance of the product from a wholesaler to a plurality of customers over a certain period, for each of a plurality of organizations in charge of the plurality of customers in the wholesaler A purchase bounty distribution system for wholesalers to distribute,
A sales record file for storing the sales record data of the product;
From the sales record file, not only the sales price of the product for a certain period, but also the actual data including the actual value of the number of units sold and the number of units sold are associated with the plurality of organizations, the customers, and the suppliers. Aggregation processing means to
A master file for storing reference data relating to a bounty calculation standard based on each actual value of the sales amount, the number of sales, and the number of sales houses of the product in the predetermined period that is negotiated with the supplier;
Based on the reference data in the master file, the bounty data for each of the plurality of organizations is calculated from the actual data tabulated by the counting means, and the plurality of customers are calculated from the bounty data for the plurality of organizations. An allocation processing means that aggregates and distributes the bounty data of
A purchase reward distribution system comprising: means for outputting the reward data in a referable manner. The master file includes, as the reference data, an achievement rate evaluation condition based on a ratio of a plan value and an actual value for each of the plurality of organizations, an amount evaluation condition based on a sales amount target value for each of the plurality of organizations, and the plurality of Store further evaluation data on each evaluation condition of performance evaluation conditions based on the target number of sales and number of houses for each organization,
The allocation processing means determines, based on the evaluation data, for each of the plurality of organizations whether or not the actual data aggregated by the aggregation means satisfies the evaluation conditions, and satisfies the evaluation conditions 2. The system of claim 1 according to claim 1, wherein reward data for each of the plurality of organizations is calculated with respect to an organization. The master file further stores relief data relating to predetermined relief conditions as the evaluation data,
The allocation processing means further determines, based on the repair data, whether or not the actual data satisfies a predetermined repair condition for an organization that does not satisfy the evaluation condition, and satisfies the repair condition. 3. The purchase reward distribution system according to claim 2, wherein the reward data for each of the plurality of organizations is calculated for an organization.   2. The tabulation processing unit identifies a new customer and a continuous customer for the predetermined period as the customer, and tabulates the actual data in association with the new customer and the continuous customer. The described purchase bounty distribution system. A reward to be obtained from a supplier of the product according to the sales performance of the product from a wholesaler to a plurality of customers over a certain period, for each of a plurality of organizations in charge of the plurality of customers in the wholesaler A server used in a purchase bounty distribution system for wholesalers to distribute,
A sales record file for storing the sales record data of the product;
From the sales record file, not only the sales price of the product for a certain period, but also the actual data including the actual value of the number of units sold and the number of units sold are associated with the plurality of organizations, the customers, and the suppliers. Aggregation processing means to
A master file for storing reference data relating to a bounty calculation standard based on each actual value of the sales amount, the number of sales, and the number of sales houses of the product in the predetermined period that is negotiated with the supplier;
Based on the reference data in the master file, the bounty data for each of the plurality of organizations is calculated from the actual data tabulated by the counting means, and the plurality of customers are calculated from the bounty data for the plurality of organizations. An allocation processing means that aggregates and distributes the bounty data of
And a means for outputting the bounty data in a referable manner. A reward to be obtained from a supplier of the product according to the sales performance of the product from a wholesaler to a plurality of customers over a certain period, for each of a plurality of organizations in charge of the plurality of customers in the wholesaler A purchase bounty distribution method for wholesalers to distribute,
Storing the sales record data of the product in a sales record file;
From the sales record file, not only the sales price of the product for a certain period, but also the actual data including the actual value of the number of units sold and the number of units sold are associated with the plurality of organizations, the customers, and the suppliers. And steps to
Storing, in a master file, reference data relating to a bounty calculation standard based on actual values of the sales amount, the number of sales, and the number of sales houses of the product in the predetermined period that is negotiated with the supplier;
Based on the reference data in the master file, the bounty data for each of the plurality of organizations is calculated from the actual data tabulated by the counting means, and the plurality of customers are calculated from the bounty data for the plurality of organizations. A step to aggregate and distribute the bounty data for
And a step of outputting the bounty data so that the bounty data can be referred to. The step of storing the reference data includes, as the reference data, an achievement rate evaluation condition based on a ratio of a plan value and an actual value for each of the plurality of organizations, an amount evaluation condition based on a sales amount target value for each of the plurality of organizations, And further storing evaluation data related to each evaluation condition of the performance evaluation condition based on the target value of the number of sales and the number of sales eaves for each of the plurality of organizations,
The step of allocating the reward data determines, for each of the plurality of organizations, whether or not the actual data aggregated by the aggregation means satisfies the evaluation conditions based on the evaluation data, The method of claim 6, wherein reward data for each of the plurality of organizations is calculated for an organization that satisfies the evaluation condition. The step of storing the reference data further stores relief data relating to a predetermined relief condition as the evaluation data,
The step of allocating the reward data further determines, based on the relief data, whether or not the actual data satisfies a predetermined relief condition for an organization that does not satisfy the evaluation condition, 8. The purchase reward distribution method according to claim 7, wherein the reward data for each of the plurality of organizations is calculated for an organization that satisfies a condition.   The step of aggregating the performance data includes identifying the new customer and the continuous customer for the predetermined period as the customer, and aggregating the performance data in association with the new customer and the continuous customer. The purchase reward distribution method according to claim 6. A reward to be obtained from a supplier of the product according to the sales performance of the product from a wholesaler to a plurality of customers over a certain period, for each of a plurality of organizations in charge of the plurality of customers in the wholesaler A program used in a purchase bounty distribution system for wholesalers to distribute,
On the computer,
Storing the sales record data of the product in a sales record file;
From the sales record file, not only the sales price of the product for a certain period, but also the actual data including the actual value of the number of units sold and the number of units sold are associated with the plurality of organizations, the customers, and the suppliers. And steps to
Storing, in a master file, reference data relating to a bounty calculation standard based on actual values of the sales amount, the number of sales, and the number of sales houses of the product in the predetermined period that is negotiated with the supplier;
Based on the reference data in the master file, the bounty data for each of the plurality of organizations is calculated from the actual data tabulated by the counting means, and the plurality of customers are calculated from the bounty data for the plurality of organizations. A step to aggregate and distribute the bounty data for
And a step of outputting the bounty data in a referable manner.

Images