JP2013182354A - Analysis program, analysis device and analysis method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To accurately grasp situations relating to various tasks.SOLUTION: A monitoring server 70 acquires the setting of the type of attribute items relating to a task. Furthermore, the monitoring server 70 totals the values of numerical items by targeting first task data in which any error code showing an error has not been applied to the attribute items of the type whose setting has been acquired among task data in which the attribute items and numerical items relating to the task are associated with each other. Furthermore, the monitoring server 70 totals the values of the numerical items by targeting second task data in which the error code has been applied to the attribute items of the type whose setting has been acquired among the task data. Furthermore, the monitoring server 70 makes a headquarter terminal 50 display the total result of the numerical items of the first task data and the total result of the numerical items of the second task data.

Description

  The present invention relates to an analysis program, an analysis apparatus, and an analysis method.

  An organization such as a company may have bases such as factories that produce products and dealers that sell products over a plurality of regions and countries. These bases often have different business systems and code systems and languages used by the business systems. For this reason, it is desired to visualize the situation regarding various operations including production, sales and inventory across the boundaries between bases.

JP 2001-195472 A

  As an example of the above visualization, after collecting business data associated with business attribute items and numerical items from the business system introduced at each base, the value of the numerical item included in the business data is set to a predetermined attribute, For example, it is conceivable to tabulate in units such as organization, period, and item.

  However, the business systems introduced at each base are not necessarily the same. For this reason, it is assumed that the code of the attribute item included in the business data collected from the business system is converted into a unified code unified among the bases.

  At this time, if the code of any attribute item among the attribute items is not registered as a unified code, it cannot be determined which other business data should be aggregated with the value of the numerical item corresponding to the code. .

  As described above, when a numerical item of a code that is not in the unified code is excluded from the totalization, the total amount becomes inaccurate, which causes a problem that it is impossible to accurately grasp the situation regarding various business operations.

  The disclosed technology has been made in view of the above, and an object thereof is to provide an analysis program, an analysis apparatus, and an analysis method capable of accurately grasping situations related to various operations.

  The analysis program disclosed in the present application causes a computer to execute processing for acquiring the setting of the type of attribute item related to business. Further, an error indicating an error in the attribute item of the type in which the setting is acquired out of the business data stored in the business data storage unit that stores business data associated with business-related attribute items and numerical items in the computer A process of aggregating the values of the numerical items is executed on the first business data to which no code is assigned. Further, the computer stores the value of the numeric item for the second business data in which the error code is added to the attribute item of the type for which the setting is acquired, among the business data stored in the business data storage unit. Execute the process of aggregation. Furthermore, the computer is caused to execute processing for displaying a total result of numerical items of the first business data and a total result of numerical items of the second business data on a predetermined device.

  According to one aspect of the analysis program disclosed in the present application, there is an effect that it is possible to accurately grasp the situation regarding various business operations.

FIG. 1 is a diagram illustrating the configuration of the monitoring system according to the first embodiment. FIG. 2 is a block diagram illustrating a functional configuration of the master server according to the first embodiment. FIG. 3 is a diagram illustrating an example of slip data. FIG. 4 is a diagram illustrating an example of a unified code master. FIG. 5 is a diagram illustrating an example of totaling data. FIG. 6 is a diagram illustrating an example of conversion history data. FIG. 7 is a diagram illustrating an example of summary level data. FIG. 8 is a diagram illustrating an example of a product type master. FIG. 9 is a diagram illustrating an example of summary data. FIG. 10 is a diagram illustrating an example of data for aggregation. FIG. 11 is a diagram illustrating an example of summary data. FIG. 12 is a diagram illustrating an example of conversion history data. FIG. 13 is a block diagram illustrating a functional configuration of the monitoring server according to the first embodiment. FIG. 14 is a diagram illustrating an example of public data. FIG. 15 is a diagram illustrating an example of a screen displayed on the head office terminal. FIG. 16 is a diagram illustrating an example of a screen displayed on the head office terminal. FIG. 17 is a diagram illustrating an example of a screen displayed on the head office terminal. FIG. 18 is a flowchart illustrating the procedure of the aggregation process according to the first embodiment. FIG. 19 is a flowchart illustrating the analysis processing procedure according to the first embodiment. FIG. 20 is a schematic diagram illustrating an example of a computer that executes an analysis program according to the first and second embodiments.

  Embodiments of an analysis program, an analysis apparatus, and an analysis method disclosed in the present application will be described below in detail with reference to the drawings. Note that this embodiment does not limit the disclosed technology. Each embodiment can be appropriately combined within a range in which processing contents are not contradictory.

[System configuration]
First, the configuration of the monitoring system according to the present embodiment will be described. FIG. 1 is a diagram illustrating the configuration of the monitoring system according to the first embodiment. A monitoring system 1 shown in FIG. 1 provides a monitoring service for monitoring the status of various businesses of a company that develops bases 3A to 3C across a plurality of regions and countries.

  As shown in FIG. 1, the monitoring system 1 accommodates a master server 10, base servers 30 </ b> A to 30 </ b> C, a head office terminal 50, and a monitoring server 70. In the example of FIG. 1, three base servers and one head office terminal are illustrated, but the disclosed system is not limited to the illustrated configuration. That is, the monitoring system 1 can accommodate any number of base servers and head office terminals. Hereinafter, the bases 3A to 3C are collectively referred to as “base 3” when collectively referred to, and the base servers 30A to 30C are collectively referred to as “base server 30”. May be described.

  The master server 10, the base server 30, the head office terminal 50, and the monitoring server 70 are connected via the network 9 so that they can communicate with each other. The network 9 can employ any type of communication network such as the Internet, LAN (Local Area Network), and VPN (Virtual Private Network) regardless of wired or wireless.

  Among these, the base server 30 is a server device for business management disposed in the base 3 such as a factory that produces products or a store that sells products. As an example of the base server 30, production, sales, inventory, so-called live sales PSI, and various business data such as finance, procurement, distribution, etc. are managed. Resource Planning) server can be adopted.

  The base server 30 uploads business data related to various business plans or results to the master server 10. At this time, the base server 30 may upload the business data in real time or may upload it by batch processing. In the following, the following description will be given on the assumption that the base server 30 uploads the slip data relating to the product sales plan to the master server 10 as an example.

  Here, the slip data uploaded to the master server 10 by the base server 30 includes an attribute item in which an attribute relating to the sales plan is defined and a numerical item in which a numerical value relating to the sales plan is defined.

  For example, as an example of an attribute item of slip data, a slip number, a base ID, a base item number, a planned sales date, and the like can be given. The “slip number” here refers to a number for identifying slip data. In addition to the identification of the slip, a number that also serves as the identification of the base 3 and the department in the base 3 can be assigned to the slip number. Further, when the identification information of the base 3 or the department in the base 3 is not incorporated in the slip number, the identification information of the department in the base 3 or the base 3 can be individually added to the slip data. “Location ID” is identification information for identifying each location 3A to 3C. The “base item number” indicates a number for identifying a product item in each of the bases 3A to 3C. The “scheduled sales date” indicates a schedule for selling the product. For example, the date can be described by “yyyy / mm / dd”. Of these, the base item number may be assigned a different code system depending on the ERP package installed in the base server 30, and therefore, a code common to the bases 3 is not necessarily assigned. Absent. As described above, a code used locally at the site 3 may be referred to as a “site code” below. Moreover, as an example of the numerical item of the slip data, there is a planned sales indicating a sales planned for the sale of the product.

  The master server 10 is a server device that manages various masters. The master server 10 may be implemented as a Web server or may be implemented as a cloud.

  The master server 10 converts the base code of the attribute item included in the slip data collected from the base server 30 into a unified code unified between the bases 3 by using a unified code master 13b described later. In this way, the reason for converting the base code to the unified code is to comprehensively manage the slip data of each base 3 after absorbing the difference between the ERP package introduced at the base 3 and the code system used by the ERP package. .

  In addition, the master server 10 notifies the monitoring server 70 of data used for monitoring various operations. At this time, the master server 10 immediately transmits the slip data collected from the base servers 30A to 30C just because the code system of the attribute items included in the slip data is unified among the bases 3. I do not. This is because if the slip data that increases with the expansion of the number of business sites and the number of product items is transmitted to the monitoring server 70 as it is, the communication load between the master server 10 and the monitoring server 70 also increases. . Therefore, the master server 10 summarizes the slip data by aggregating the slip data according to the summary level set by the person in charge in the sales department of the head office 5, for example, the organization, the period, and the product name granularity. In addition, the master server 10 notifies the monitoring server 70 of summary data in which the slip data is summarized. As described above, the master server 10 transmits summary data in which the granularity of attribute items such as the organization, period, and product name is larger than the slip data collected from the base server 30, so that the master server 10 and the monitoring server 70 are Reduce the communication load.

  The monitoring server 70 is a server device that provides a monitoring service that publishes summary data of slip data notified from the master server 10 to the head office terminal 50 or the like. The monitoring server 70 may be implemented as a Web server or may be implemented as a cloud.

  The monitoring server 70 can provide the summary data of the slip data as a report as it is, or provide the summary data report after further summarizing the summary data according to the granularity of the report designated from the head office terminal 50. You can also. Further, when the monitoring server 70 receives a request for generating a report for predictive comparison from the headquarters terminal 50, the values of the numerical items are written together so that the numerical comparison with the summary data regarding the sales plan and the sales results is facilitated. You can also generate chart reports such as charts and graphs.

  In addition, the monitoring server 70 releases the monitoring service by focusing on specific members belonging to the organization. For example, the monitoring server 70 receives input of login authentication information such as an account name and a password from the head office terminal 50. Then, the monitoring server 70 performs login authentication of the user of the head office terminal 50 using the login authentication information received from the head office terminal 50. At this time, if the login authentication is successful, the monitoring server 70 authenticates that the user of the head office terminal 50 is a member and releases the monitoring service.

  The head office terminal 50 is a terminal device used by a member of the head office 5 which is a head quarter that supervises the bases 3A to 3C. As an example of the head office terminal 50, a mobile terminal such as a mobile phone, a PHS, and a PDA can be employed in addition to a fixed terminal such as a personal computer. For example, the head office terminal 50 is used by a member of the head office 5, for example, a sales department, a purchasing department, a person in charge of an order receiving department, or the like. Here, it is assumed that the monitoring service is provided to the members of the headquarters 5 through the headquarters terminal 50, but the bases used by the members of the respective bases 3, for example, managers of the sales department, the purchasing department, and the order receiving department. The monitoring service may be provided through the terminal.

[Configuration of Master Server 10]
Subsequently, a functional configuration of the master server 10 according to the present embodiment will be described. FIG. 2 is a block diagram illustrating a functional configuration of the master server 10 according to the first embodiment. As illustrated in FIG. 2, the master server 10 includes a communication I / F (interface) unit 11, a storage unit 13, and a control unit 15. The master server 10 may include various functional units included in a known server device, for example, functional units such as various input devices and audio output devices, in addition to the functional units illustrated in FIG.

  The communication I / F unit 11 is an interface that performs communication control with other devices, for example, the base servers 30A to 30C, the head office terminal 50, and the monitoring server 70. As an aspect of the communication I / F unit 11, a network interface card such as a LAN card can be employed. For example, the communication I / F unit 11 receives slip data from the base server 30 and transmits summary data of the slip data generated by the master server 10 to the monitoring server 70.

  The storage unit 13 is a storage device that stores various programs such as an OS (Operating System) executed by the control unit 15 and a summary program that generates summary data of slip data by tallying slip data. As one aspect of the storage unit 13, a storage device such as a semiconductor memory element such as a flash memory, a hard disk, and an optical disk can be cited. The storage unit 13 is not limited to the type of storage device described above, and may be a RAM (Random Access Memory) or a ROM (Read Only Memory).

  The storage unit 13 includes slip data 13a, a unified code master 13b, totaling data 13c, conversion history data 13d, and summary level data 13e as an example of data necessary for executing the program executed by the control unit 15. And the product type master 13f are stored.

  Of these, the slip data 13a is data representing a slip relating to a sales plan, which is an aspect of the business data relating to a business plan or actual performance. As an example, the slip data collected from the base server 30 is registered in the slip data 13a by the receiving unit 15a described later. As another example, the slip data 13a is referred to by a conversion unit 15b described later in order to generate summary data from the slip data 13a. As a further example, the slip data 13a is deleted by a later-described notification unit 15e when summary data is notified to the monitoring server 70.

  As an aspect of the slip data 13a, data in which an attribute item in which an attribute related to a sales plan is defined and a numerical item in which a numerical value related to the sales plan is defined can be employed. For example, as an example of the attribute item, there are a slip number, a base ID, a base item number, a planned sales date, and the like. Moreover, as an example of the numerical item, there is a planned sales that indicates a sales planned for the sale of the product.

  FIG. 3 is a diagram illustrating an example of the slip data 13a. In the example of FIG. 3, four slip data collected from the base server 30A is illustrated as an example. The example of the slip data of slip number “D001” shown in FIG. 3 indicates that sales of 1000 yen are expected on April 10, 2012 due to the sale of the product of base item number “L001”. Further, the example of the slip data of the slip number “D002” shown in FIG. 3 indicates that sales of 2000 yen are expected by the sale of the product of the base item number “L002” on April 15, 2012. The example of the slip data with the slip number “D003” shown in FIG. 3 indicates that sales of 3000 yen are expected on August 10, 2012 due to the sale of the product with the base item number “L003”. Further, the example of the slip data of the slip number “D004” shown in FIG. 3 indicates that sales of 4000 yen are expected by the sale of the product of the base item number “L004” on August 30, 2012.

  The unified code master 13b is master data in which the correspondence relationship between the base code and the unified code of the attribute item is defined. As an example, the unified code master 13b is referred to by a conversion unit 15b described later in order to convert a base code of an attribute item included in the slip data 13a into a unified code. As another example, the unified code master 13b is updated by the head office terminal 50 such as new registration, change, or deletion of the unified code.

  As an aspect of the unified code master 13b, data in which a base item number and a unified item number are associated can be employed. FIG. 4 is a diagram illustrating an example of the unified code master 13b. In the example of FIG. 4, the base item numbers “L001” and “M001” used at different bases indicate the same item, and indicate that these item numbers are unified to “S001”. Further, in the example of FIG. 4, the base item numbers “L002” and “M002” used at different bases indicate the same item, and indicate that these item numbers are unified to “S002”. . Note that the unified code does not necessarily have a code system different from the base code, and any one of the base codes can be set as the unified code.

  In the example of FIG. 4, the correspondence between the base code and the unified code related to the product item number is illustrated, but the master in which the correspondence between the base code and the unified code other than the product item number is defined is held. It doesn't matter. For example, when the master server 10 collects ledger data related to business partners, business partner numbers having different code systems may be used between the bases 3. In this case, the disclosed apparatus may hold a master in which the correspondence between the base supplier number and the unified supplier number is defined.

  The aggregation data 13c is data used for aggregation by a later-described aggregation unit 15d. As an example, in the data for aggregation 13c, slip data obtained by converting the base code of the attribute item into a unified code is registered by the generation unit 15c described later. As another example, in the data for aggregation 13c, dummy data obtained by converting the attribute item base code into a unified code without being converted into a unified code is registered by the generation unit 15c described later. As a further example, in the aggregation data 13c, when the slip accepted by the accepting unit 15a is a dummy data correction slip, consumption data for erasing the dummy data is registered by the generation unit 15c described later. As another example, the aggregation data 13c is referred to by the aggregation unit 15d described later in order to generate summary data by aggregating the values of the numerical items included in the aggregation data 13c, and after the summary data is generated It is deleted by a counting unit 15d described later.

  As an aspect of the totaling data 13c, data in which a slip number, a base ID, a slip classification, a unified item number, a planned sales date, and a planned sales amount are associated can be employed. The “slip category” here refers to a category of a slip. Such slip classification includes, for example, a black slip that adds the value of a numeric item and a red slip that erases the value of a numeric item. FIG. 5 is a diagram illustrating an example of the totaling data 13c. In the example of FIG. 5, the four slip data of the slip numbers “D001” to “D004” are all black slips that are added when the numerical items are aggregated. Among these, the slip data of the slip number “D004” indicates that the unified item number is dummy data including a dummy code.

  The conversion history data 13d is data representing the conversion history of the base code of the attribute item. As an example, the conversion history data 13d is generated by a generation unit 15c described later in order to determine whether the slip data 13a that has been able to convert the base code of the attribute item into a unified code is a new slip or a dummy data correction slip. Referenced. As another example, the conversion history data 13d indicates that when summary data is generated from the slip data 13a, the conversion history corresponding to the slip number included in the slip data 13a is updated by the conversion unit 15b described later. Updated.

  The conversion history data 13d can employ data in which a slip number, a base ID, a base item number, a unified item number, a planned sales date, and a planned sales amount are associated. FIG. 6 is a diagram illustrating an example of the conversion history data 13d. Of the conversion histories shown in FIG. 6, the conversion histories of the slip numbers “D001” to “D003” all indicate that the base item number can be converted into the unified item number. On the other hand, the conversion history of the slip number “D004” indicates that the base item number cannot be converted into a unified item number, and the base item number has been converted into a dummy code.

  The summary level data 13e is data in which the granularity of the attribute item after aggregation is defined. As an example, the summary level data 13e is referred to by a later-described aggregation unit 15d when the values of numerical items included in the aggregation data 13c are aggregated. As another example, in the summary level data 13e, the head office terminal 50 executes setting registration and setting change of the type and granularity of attribute items such as organization, period, and product name. As an aspect of the summary level data 13e, data in which the aggregated organization, period, and product name granularity are associated can be employed. FIG. 7 is a diagram illustrating an example of the summary level data 13e. In the example of FIG. 7, the numerical items of the data 13c for aggregation are three units of “organization”, “period”, and “product name” as aggregation keys, and the granularity after aggregation is “base”, “monthly” and This indicates that it is set to be aggregated so as to be “product type”.

  The product master 13f is master data in which a unified product number that is a unified product product code is defined. The “variety” here refers to a group of items in which items having a certain commonality are grouped into a series, and is also called a series item. As an example, the product type master 13f is referred to by a later-described totaling unit 15d in order to total the numerical items linked to the unified item number included in the same product type. As another example, in the product master 13f, the headquarters terminal 50 updates the unified product number such as new registration, change or deletion. As an aspect of the product type master 13f, data in which a unified product number and a unified product number are associated can be employed. FIG. 8 is a diagram illustrating an example of the product type master 13f. In the example of FIG. 8, the products having the unified item numbers “S001” and “S002” are series items.

  The control unit 15 has an internal memory for storing programs defining various processing procedures and control data, and executes various processes using these. As shown in FIG. 2, the control unit 15 includes a reception unit 15a, a conversion unit 15b, a generation unit 15c, a totaling unit 15d, and a notification unit 15e.

  Among these, the reception unit 15 a is a processing unit that receives slip data from the base server 30. As one aspect, the accepting unit 15a stores the slip data uploaded from the base server 10 until a predetermined period elapses after the summary data is generated last time or until a predetermined periodic time is reached. Register with Here, a case will be described in which the slip data stored in the storage unit 13 in the subsequent function unit is batch-processed on a daily basis, but the aggregation process is performed on the condition that a predetermined number of slip data has been stored. It may be activated or the aggregation process may be activated every time slip data is received.

  The conversion unit 15b is a processing unit that converts the base code of the attribute item included in the slip data using the unified code master 13b. As one aspect, when the base item number included in the slip data 13a is registered in the unified code master 13b, the conversion unit 15b converts the base item number into a unified item number. The conversion unit 15b converts the base item number into a dummy code when the base item number included in the slip data 13a is not registered in the unified code master 13b. Thereafter, the conversion unit 15b updates the conversion history corresponding to the slip number included in the slip data 13a in the conversion history data 13d to the latest conversion history. At this time, if the same conversion history as the combination of the slip number and the base item number that has been converted this time is not registered, the conversion unit 15b records the conversion history including the base code and the unified code before and after the conversion. Is newly registered. On the other hand, when the same conversion history as the combination of the slip number and the base item number that has been converted this time has already been registered, the conversion unit 15b records a conversion history record including the base code and the unified code before and after conversion. Overwrite and register.

  The generation unit 15c is a processing unit that generates erase data that erases dummy data. As one aspect, when the base item number is converted into a unified item number by the conversion unit 15b, the generation unit 15c registers the slip data after conversion into the unified item number as the aggregation data 13c. Then, the generation unit 15c reads the conversion history having the same slip number as the slip number included in the slip data converted into the unified item number in the conversion history data 13d and converted into the dummy code. Then, the generation unit 15c determines whether the base item number included in the conversion history read out earlier matches the base item number included in the slip data converted into the unified item number. At this time, if the base item numbers of the two coincide, it can be determined that the slip data uploaded from the base server 30 is a correction slip of dummy data received in the past. In this case, the generation unit 15c includes a numerical item having a value obtained by inverting the value of the numerical item value included in the dummy data in order to erase the value of the numerical item that has been tabulated as dummy data in the past. After generating the consumption data, so-called red slip, the consumption data is registered as the totaling data 13c. If the base item numbers do not match, it is possible to determine that the slip data uploaded from the base server 30 is a new slip, so there is no need to generate consumption data. In addition, the production | generation part 15c registers the dummy data containing a dummy code as the data 13c for aggregation, when the base item number is converted into the dummy code by the conversion part 15b.

  The aggregation unit 15d is a processing unit that aggregates the values of the numerical items included in the aggregation data 13c using the summary level data 13e. As one aspect, the aggregation unit 15d refers to an attribute item whose granularity is set in the summary level data 13e when registration of the aggregation data 13c has been completed for all the slip data 13a, and Specify whether to be used as a summary key. Then, the aggregation unit 15d refers to the granularity of the attribute item as the aggregation key, and groups the aggregation data 13c that aggregates the values of the numerical items. In addition, the totaling unit 15d totals the values of the numerical items of the totaling data 13c for each group of the totaling data 13c determined in advance. In this way, summary data in which the slip data is summarized is generated by summing up the values of the numerical items of the summation data 13c.

  For example, when the granularity is set for all of “organization”, “period”, and “product name” in the summary level data 13e, three attribute items “organization”, “period”, and “product name” are displayed. Identified as a summary key. In this case, the data 13c for aggregation which belong to the same base, belong to the same month and whose unified item number belongs to the same unified product number are grouped. For this reason, the dummy data with the dummy code assigned to the unified item number and the consumption data are not grouped with the slip data having no dummy code.

  More specifically, it is assumed that the summary data 13c shown in FIG. 5 is aggregated using the summary level data 13e shown in FIG. In this case, three attribute items “organization”, “period”, and “product name” are specified as the aggregation key. The data 13c for the slip number “D001” and the slip number “D002” are both slip data collected from the same base 3A, belong to the same April, and have a unified item number. Are set to the same unified product number “A” in the product master 13f. Therefore, the aggregation data 13c of the slip number “D001” and the slip number “D002” is grouped. On the other hand, the data 13c for the slip number “D003” and the slip number “D004” are both slip data collected from the same base 3A, and the sales date belongs to the same August. A dummy code is assigned to the unified product number of “D004”. Therefore, the aggregation data 13c of the slip number “D003” and the slip number “D004” is not grouped. The aggregation data 13c of the slip number “D003” and the slip number “D004” that have not been grouped in this way is not aggregated.

  Therefore, summary data shown in FIG. 9 is generated. FIG. 9 is a diagram illustrating an example of summary data. The example of FIG. 9 indicates that sales of 3000 yen are expected in April 2012 due to the sale of the product of the unified product number “A”. Furthermore, the example of FIG. 9 indicates that sales of 3000 yen are expected in August 2012 due to the sale of the product with the unified item number “B”. In the example of FIG. 9, although the site item number is unknown, it indicates that sales of 3000 yen are expected in August 2012 due to product sales. Further, “*” shown in FIG. 9 is inserted into attribute items that cannot be reproduced with the granularity of the summary data by being aggregated according to the granularity set in the summary level data 13e. For example, in the example of FIG. 9, since the items are not distinguished from each other in the value of the numerical item by being aggregated into the product type, “*” is added to the value of the unified item number at the time of aggregation. In the same manner, since the daily items are not differentiated from each other in the numerical item values, “*” is also given to the scheduled sales date values at the time of aggregation.

  In addition, when “base” and “monthly” are set in the “organization” and “period” in the summary level data 13e, “organization” and “period” are specified as aggregation keys. , It is specified that the granularity of the attribute item as the aggregation key should be “base” and “monthly”. In this case, if the data for aggregation 13c belongs to the same base and the scheduled sales date belongs to the same month, even if the unified item number is different or a dummy code is assigned to the unified item number, it is the same Grouped into groups.

  The notification unit 15e is a processing unit that notifies the monitoring server 70 of the summary data in which the aggregation data 13c is aggregated by the aggregation unit 15d. As one aspect, the notification unit 15e notifies the monitoring server 70 of the summary data aggregated by the aggregation unit 15d. In addition, when the transmission of the summary data to the monitoring server 70 is completed, the notification unit 15e deletes the slip data 13a from the storage unit 13. This suppresses the same summary data from being transmitted to the monitoring server 70 a plurality of times.

[Concrete example]
Here, a specific example of deletion of dummy data will be described with reference to FIGS. FIG. 10 is a diagram illustrating an example of the aggregation data 13c. FIG. 11 is a diagram illustrating an example of summary data. FIG. 12 is a diagram illustrating an example of the conversion history data 13d. Here, a slip having the record of the slip number “D004” shown in FIG. 3 after the correspondence relationship between the base item number “L004” and the unified item number “S004” is added to the unified code master 13b shown in FIG. Assume that data is received as a dummy data correction slip anew.

  As described above, when the correspondence data of the base item number “L004” and the unified item number “S004” is added to the unified code master 13b and the slip data of the slip number “D004” is newly received, the slip of the slip number “D004” is received. The base item number “L004” included in the data is not converted into a dummy code as in the previous case, but is converted into a unified item number “S004”. Then, as shown in FIG. 10, the slip data of the slip number “D004” is registered as the totaling data 13c. Further, referring to the conversion history data 13d shown in FIG. 6, since the conversion history having the slip number “D004” and the base item number “L004” is registered, it is determined that this is a dummy data correction slip at this point. Is done. In this case, as shown in FIG. 10, consumption data including a numerical item having a value “−4000” obtained by inverting the sign of the planned sales value “4000” included in the dummy data is generated. The consumption data is further registered as totaling data 13c.

  Since these data for aggregation 13c are not grouped, the numerical item is not aggregated, but the granularity of the attribute item is changed from item to product as shown in FIG. Therefore, “B”, which is a series item of the unified item number “S004”, is set as the value of the unified product number, and “*” is set as the value of the unified item number. At the same time, the scheduled sales date is changed to the monthly scheduled sales month. Therefore, “August” to which the scheduled sales date “August 30, 2012” belongs is set as the value of the planned sales month and “*” is set as the value of the planned sales date. The summary data generated in this way is transmitted to the monitoring server 70.

  As a result, in the monitoring server 70 to be described later, when the summary data notified this time is added to the summary data in FIG. 9 that was previously notified, the summary data is updated as shown in FIG. 14 to be described later. Become. In other words, a dummy code is added to the unified product number, and a dummy code is included in the unified product number by adding the planned sales “-4000 yen” of the consumption data to the record whose scheduled sales date is August. The dummy sales record is deleted when the planned sales are zero. On the other hand, by adding the planned sales “4000 yen” to the record with the unified product number “B” and the scheduled sale date in August, the unified product number “B” whose planned sales were 3000 yen was added. The planned sales of the record are updated to 7000 yen. In this way, the planned sales value of the slip data that can be converted to the unified code is aggregated again, and the planned sales value aggregated before the unified code update is erased from the aggregated value of the dummy data. Is included. Therefore, it is possible to prevent the planned sales value from being duplicated before and after the update of the unified code.

  Furthermore, the fourth record from the top having the slip number “D004” and the unified item number “S004” in the conversion history shown in FIG. 6 is updated to the conversion history shown in FIG. That is, since the base item number “L004” included in the slip data of the slip number “D004” is converted to the unified item number “S004” instead of the dummy code, the converted value of the conversion history is changed from the dummy code to “S004”. S004 "is updated. For this reason, it is possible to suppress the generation of duplicated data even when a dummy code correction slip is subsequently received.

  Note that various integrated circuits and electronic circuits can be employed for the control unit 15. In addition, a part of the functional unit included in the control unit 15 may be another integrated circuit or an electronic circuit. For example, an ASIC (Application Specific Integrated Circuit) is an example of the integrated circuit. Examples of the electronic circuit include a central processing unit (CPU) and a micro processing unit (MPU).

[Configuration of Monitoring Server 70]
Subsequently, a functional configuration of the monitoring server 70 according to the present embodiment will be described. FIG. 13 is a block diagram illustrating a functional configuration of the monitoring server 70 according to the first embodiment. As illustrated in FIG. 13, the monitoring server 70 includes a communication I / F unit 71, a storage unit 73, and a control unit 75. Note that the monitoring server 70 may include various functional units included in a known server device other than the functional units illustrated in FIG. 13, for example, functional units such as various input devices and audio output devices.

  The communication I / F unit 71 is an interface that performs communication control with other devices such as the master server 10, the base servers 30 </ b> A to 30 </ b> C, and the head office terminal 50. As an aspect of the communication I / F unit 71, a network interface card such as a LAN card can be employed. For example, the communication I / F unit 71 receives summary data from the master server 10, receives login authentication information and a report browsing request from the head office terminal 50, and also displays summary data generated by the monitoring server 70. A report is transmitted to the head office terminal 50.

  The storage unit 73 is a storage device that stores various programs such as an analysis program that generates a report of slip data by aggregating the OS and summary data executed by the control unit 75. As one mode of the storage unit 73, a storage device such as a semiconductor memory element such as a flash memory, a hard disk, and an optical disk can be cited. The storage unit 73 stores public data 73a as an example of data necessary for executing the program executed by the control unit 75. In addition, the memory | storage part 73 is not limited to said kind of memory | storage device, RAM and ROM may be sufficient.

  The public data 73a is summary data for publication. Hereinafter, summary data that is disclosed for monitoring to members of the head office 5 may be referred to as “public data”. As an example, as the public data 73a, summary data transmitted by the master server 10 is registered by a registration unit 75a described later. As another example, the public data 73a is referred to by a later-described aggregation unit 75d in order to generate a report to be monitored by a member of the head office 5.

  As one aspect of the public data 73a, data in which a base ID, a unified product number, a unified item number, a planned sales month, a planned sales date, and a planned sales amount are associated can be adopted. FIG. 14 is a diagram illustrating an example of the public data 73a.

  In the example of FIG. 14, it is assumed that scheduled sales for each day and product type at each of the bases 3A to 3C are summarized as monthly data and product type and then stored as public data. In the example of FIG. 14, the base 3A has a sales of “5000 yen” with a unified product number “A”, a sales “3000 yen” with a unified product number “B”, and a “4000 yen” with unknown product in August 2012. Indicates that it is expected. Further, in the example of FIG. 14, it is assumed that the base 3B is expected to have sales of “8000 yen” for the unified product number “A” and “12,000 yen” for the unified product number “B” in August 2012. Show. Further, in the example of FIG. 14, the base 3C, in August 2012, sold “3600 yen” for the unified product number “A”, “15600 yen” for the unified product number “B”, and “6000 yen” for the unknown product type. "Is expected. The details will be described in the description of the registration unit 75a in the latter stage, but “previous” and “rear” in the column of planned sales in the figure receive summary data including dummy data consumption data shown in FIG. Indicates the value of planned sales before and after.

  The control unit 75 has an internal memory for storing programs defining various processing procedures and control data, and executes various processes using these. As illustrated in FIG. 13, the control unit 75 includes a registration unit 75a, a login processing unit 75b, a setting acquisition unit 75c, a totaling unit 75d, and a display control unit 75e.

  Among these, the registration unit 75 a is a processing unit that registers summary data received from the master server 10 in the storage unit 73. As one aspect, the registration unit 75a searches for public data 73a in which combinations of values of attribute items included in the summary data match. At this time, when there is public data 73a in which the combination of the values of the attribute items included in the summary data matches, the registration unit 75a includes the value of the numeric item included in the public data 73a in the summary data. Update to add the value of the numeric item. On the other hand, when there is no public data 73a in which the combination of the values of the attribute items included in the summary data matches, the registration unit 75a stores the summary data received from the master server 10 as new public data 73a. Register with

  For example, it is assumed that summary data including the erased data of the dummy data shown in FIG. 11 is received in a situation where the planned sales of the public data 73a are in the “previous” state shown in FIG. In this case, the registration unit 75a adds the black slip “4000 yen” to the planned sales value of the record corresponding to the base ID “30A”, the unified product number “B”, and the planned sales month “August 2012”. Add the value. Furthermore, the registration unit 75a sets the value of the red slip “−4000 yen” to the planned sales value of the record corresponding to the base ID “30A”, the unified product number “Dummy”, and the planned sales month “August 2012”. Add. In this case, the planned sales value is zero, so the record is deleted.

  The login processing unit 75b is a processing unit that executes various processes related to login. As one aspect, when the login processing unit 75b receives login authentication information such as an account name and a password from the head office terminal 50, the login processing unit 75b determines whether the account name and the password are legitimate ones registered in advance. To do. Thereby, the login processing unit 75b performs login authentication as to whether or not the user of the head office terminal 50 is a member of the company. The login processing unit 75b releases the monitoring service when the user of the head office terminal 50 is authenticated as a member, that is, when the login authentication is successful. If login authentication fails, an account name and password are input again by prompting a retry, or access to the monitoring server 70 by the head office terminal 50 that failed login authentication is prohibited.

  The setting acquisition unit 75c is a processing unit that acquires the setting of the attribute item type used as the aggregation key when generating a report to be disclosed to the head office terminal 50. As an aspect, the setting acquisition unit 75c receives a report browsing request from the head office terminal 50 that has succeeded in the login authentication, and accepts designation of the type and granularity of the attribute item as the aggregation key. As another aspect, when receiving a report browsing request from the head office terminal 50, the setting acquisition unit 75c reads out setting data (not shown) in which the type and granularity of the attribute item as the aggregation key are defined.

  The aggregation unit 75d is a processing unit that aggregates the values of the numerical items of the public data 73a. As one aspect, the totaling unit 75d sequentially reads the public data 73a stored in the storage unit 73 when the type of the attribute item as the totaling key is received by the setting acquisition unit 75c. Then, the aggregation unit 75d determines whether or not the value of the attribute item that is the aggregation key among the attribute items included in the public data 73a is a dummy code. At this time, if the value of the attribute item used as the aggregation key is not a dummy code, the aggregation unit 75d groups the public data 73a into the first group. On the other hand, when the value of the attribute item used as the aggregation key is a dummy code, the aggregation unit 75d groups the public data 73a into the second group. Thereafter, the aggregation unit 75d repeatedly performs grouping on all the public data 73a to be generated as a report until the above grouping is completed. As a result of such grouping, the public data 73a is grouped into a first group with attribute items as a summary key having a dummy code, that is, no error, and a first group with the attribute item as a summary key having a dummy code. Grouped into

  After that, the totaling unit 75d totals using the value of the attribute item using the value of the numeric item included in the public data 73a grouped in the first group as the totaling key. At this time, the aggregation unit 75d aggregates the values of the numerical items of the public data 73a having the same attribute item value as the aggregation key. For example, when “organization” is specified as the type of the attribute item used as the aggregation key and “base” is specified as the granularity, the value of the numerical item between the public data 73a having the same base ID is set. Tally. At this time, a dummy code may be included in attribute items other than the organization as the aggregation key. Further, the totaling unit 75d totals the values of the numerical items included in the public data 73a grouped into the second group. By executing aggregation by group in this way, if the type of the attribute item as the aggregation key and the attribute item to which the dummy code is assigned are irrelevant, the dummy code is ignored and the two are grouped together Can be aggregated. In addition, when a dummy code is assigned to an attribute item as a total key, it can be totaled as an error.

  The display control unit 75 e is a processing unit that performs display control on the head office terminal 50. As an aspect, the display control unit 75e generates a chart such as a table or a graph including the aggregation result of the first group and the aggregation result of the second group as a report. For example, the display control unit 75e associates the aggregate value of the numeric item with each attribute item value as the aggregate key, and generates a chart in which the aggregate value of the numeric item is associated with the dummy code.

  Here, the first group may have a dummy code added to the value of an attribute item other than the attribute item used as the aggregation key, although the dummy item is not assigned to the value of the attribute item used as the aggregation key. is there. In this case, although the total amount of the total result is an accurate value, a part of the breakdown is unknown due to the dummy data, and there is no change that it is preferable to erase the dummy data. However, just generating a report that associates the value of the attribute item and the numerical value of the numeric item as the aggregation key will cause the report to contain dummy data, and in addition, any attribute item value and numeric item It is not clear whether dummy data is included in the aggregate value.

  From this, the display control unit 75e, when the value of the numeric item of the public data 73a in which the dummy code is added to the attribute item other than the attribute item as the aggregation key is included in the aggregated value of the numeric item as follows A simple report. That is, the display control unit 75e generates a report by distinguishing the display mode from the aggregate value of the numerical item of the public data 73a in which the dummy code is not assigned to the attribute item other than the attribute item as the aggregation key.

[Concrete example]
Here, a specific example relating to report generation will be described with reference to FIGS. 15 to 17 are diagrams illustrating examples of screens to be displayed on the head office terminal 50. For example, by displaying the total key designation screen 200 shown in FIG. 15 on the head office terminal 50 that has succeeded in the login authentication, designation of attribute items and granularity designation as the total keys are accepted. In the example of the total key designation screen 200, a total key 1 dialog box and a total key 2 dialog box in which attribute items can be selected are laid out so that two types of attribute items to be total keys can be specified. .

  As shown in FIG. 15, when “period” is selected in the dialog box of the summary key 1, the granularity of “monthly”, “semi-period” or “none” is selected in the dialog box for selecting the granularity. Is possible. Further, when “product name” is selected in the dialog box of the aggregation key 2, it is possible to select the granularity of “product type”, “all products”, or “none” in the dialog box for selecting the granularity. .

  As described above, when “Period” and “Product name” are specified as the type of attribute item as the aggregation key and “Monthly” and “Product type” are specified as the granularity, the execution button 200A is pressed. In this case, the sales summary screen 210 for each product shown in FIG. 16 is generated as a report from the public data 73a shown in FIG. When the cancel button 200B is pressed, display control for returning to the top page or the like without executing report generation is executed. In the following, it is assumed that the public data at the time when the planned sales of the public data 73a shown in FIG.

  Explaining this, the first group in which no dummy code is assigned to the attribute items “scheduled sales month” and “unified product number” which are the aggregation keys in the public data 73a shown in FIG. 14 and the dummy code are assigned. Grouped into a second group. That is, since the fourth and ninth records from the top of the public data 73a shown in FIG. 14 are assigned the dummy code “Dummy” to the unified product number as the total key, these two records are the second records. Grouped into groups. The records other than the two are grouped into the first group because the dummy code “Dummy” is not assigned to the unified product number as the total key.

  Then, the planned sales of the records having the same attribute items “scheduled sales month” and “unified product number” in each group are aggregated. For example, in the first group, the sales schedule month and the unified product number of the second, fifth, and seventh records from the top of the public data 73a shown in FIG. 14 are the same, so 5000, 8000, and 3600 are totaled. As a result, the total value “16600” is calculated. Further, in the first group, since the sales schedule month and the unified product number of the third, sixth and eighth records from the top of the public data 73a shown in FIG. 14 are the same, 3000, 12000 and 15600 are added up. As a result, the total value “30600” is calculated. On the other hand, in the second group, since the unified product numbers of the fourth and ninth records from the top of the public data 73a shown in FIG. 14 are both dummy codes and the scheduled sales months are the same, 4000 and 6000 The total value “10000” is calculated by summing.

  After that, a report including the total result of the first group and the total result of the second group is generated and displayed on the head office terminal 50. For example, as shown in FIG. 16, a table in which the scheduled sales month and unified product number values are associated with the aggregate value of the planned sales is generated and displayed on the head office terminal 50. By displaying the sales summary screen 210 by product, the member of the head office 5 can globally grasp the planned sales by product in the first half of 2012. When the return button 210A of the sales summary screen 210 for each product shown in FIG. 16 is pressed, the screen control for returning to the previous aggregation key designation screen 200 is performed.

  In addition, in the total key specification screen 200 shown in FIG. 15, “Period” and “Organization” are specified as the type of attribute item to be the total key, and “Monthly” and “Base” are specified as the granularity. When the button 200A is pressed, the sales summary screen 220 for each base shown in FIG. 17 is generated as a report from the public data 73a shown in FIG.

  Explaining this, the first group in which the dummy code is not assigned to the attribute items “scheduled sales month” and “location ID” which are the aggregation keys in the public data 73a shown in FIG. 14, and the dummy code is assigned. Grouped into a second group. In this case, since no dummy code “Dummy” is assigned to the planned sales month and the base ID that are the aggregation keys in any record, all the public data 73a is grouped into the first group. .

  Then, the planned sales of the records having the same attribute items “scheduled sales month” and “base ID” in the first group are aggregated. For example, since the sales schedule months and base IDs of the second, third, and fourth records from the top of the public data 73a shown in FIG. 14 are the same, the total value “12000” is obtained by summing 5000, 3000, and 4000. Is calculated. Furthermore, since the sales scheduled months and base IDs of the fifth and sixth records from the top of the public data 73a shown in FIG. 14 are the same, the total value “20000” is calculated by adding 8000 and 12000. . Furthermore, since the sales schedule month and base ID of the seventh, eighth and ninth records from the top of the public data 73a shown in FIG. 14 are the same, the total value “25200” is obtained by summing 3600, 15600 and 6000. Is calculated.

  After that, a report including the total result of the first group is generated and displayed on the head office terminal 50. For example, as shown in FIG. 17, a table in which the scheduled sales month and base ID values are associated with the aggregated value of planned sales is generated and displayed on the head office terminal 50. At this time, since the aggregated values of the bases 3A and 3C in August include the aggregated value of the public data whose unified product number is a dummy code, the display mode is distinguished and displayed in the dot fill. With the display of the sales summary screen 220 for each base, the member of the head office 5 can globally grasp the planned sales for each base in the first half of 2012. In addition, the member of the head office 5 can also understand that dummy data is included in the aggregated values of the bases 3A and 3C in August and that a dummy data correction slip should be issued. In addition, when the return button 220A of the sales summary screen 220 for each base shown in FIG. 17 is pressed, screen control for returning to the previous aggregation key designation screen 200 is performed.

[Process flow]
Next, the flow of processing according to the present embodiment will be described. Here, after (1) the totalization process executed by the master server 10 is described, (2) the analysis process executed by the monitoring server 70 will be described.

(1) Aggregation Process FIG. 18 is a flowchart illustrating the procedure of the aggregation process according to the first embodiment. This counting process is started when a predetermined period elapses after the summary data is generated last time or when a predetermined periodic time is reached.

  As shown in FIG. 13, the conversion unit 15b reads the slip data 13a from the storage unit 13 (step S101). Then, the conversion unit 15b searches the unified code master 13b for a unified item number corresponding to the base item number included in the slip data 13a (step S102).

  At this time, if the unified item number cannot be retrieved from the unified code master 13b (No at Step S103), the conversion unit 15b converts the base item number into a dummy code (Step S104). Then, the generation unit 15c registers the dummy data including the dummy code in the storage unit 13 as the aggregation data 13c (Step S105).

  On the other hand, when the unified item number can be retrieved from the unified code master 13b (Yes at Step S103), the conversion unit 15b converts the base item number into the unified item number (Step S106). Then, the generation unit 15c registers the slip data after conversion into the unified item number in the storage unit 13 as the aggregation data 13c (step S107).

  Thereafter, the generation unit 15c reads the conversion history having the same slip number as the slip number included in the slip data converted into the unified item number in the conversion history data 13d and converted into the dummy code (step S108). .

  Then, the generation unit 15c determines whether or not the base item number included in the conversion history read out earlier matches the base item number included in the slip data converted into the unified item number (step S109). .

  At this time, if the base item numbers of the two match (Yes in step S109), it can be determined that the slip data uploaded from the base server 30 is a correction slip of dummy data received in the past. Therefore, the generation unit 15c generates consumption data including a numerical item having a value obtained by inverting the value of the numerical item included in the dummy data, and then registers the consumption data as the aggregation data 13c ( Step S110).

  On the other hand, if the base item numbers do not match (No at Step S109), it can be determined that the slip data uploaded from the base server 30 is a new slip, and thus the process proceeds to Step S111 without generating consumption data. .

  Thereafter, the processes from step S101 to step S110 are repeatedly executed until the registration of the total data 13c is completed for all the slip data 13a (No in step S111).

  When the registration of the totaling data 13c is completed for all the slip data 13a (Yes at Step S111), the values of the numerical items included in the totaling data 13c are totaled using the summary level data 13e (Step S112).

  Subsequently, the notification unit 15e notifies the monitoring server 70 of the summary data in which the totaling data 13c is totaled by the totaling unit 15d (step S113). Thereafter, the conversion unit 15b updates the conversion history corresponding to the slip number included in the slip data 13a in the conversion history data 13d to the latest conversion history (step S114). Finally, the notification unit 15e deletes the slip data 13a from the storage unit 13 (step S115) and ends the process.

(2) Analysis Processing FIG. 19 is a flowchart illustrating the analysis processing procedure according to the first embodiment. This analysis process is started when a report generation request is received from the head office terminal 50 that has succeeded in the login authentication.

  As illustrated in FIG. 19, the setting acquisition unit 75 c receives designation of the attribute item type as the aggregation key from the head office terminal 50 that has succeeded in the login authentication (step S <b> 301). Then, the totalization unit 75d sequentially reads the public data 73a stored in the storage unit 73 (Step S302). Then, the aggregation unit 75d determines whether or not the value of the attribute item that is the aggregation key among the attribute items included in the public data 73a is a dummy code (step S303).

  At this time, if the value of the attribute item used as the aggregation key is not a dummy code (Yes at Step S303), the aggregation unit 75d groups the public data 73a into the first group (Step S304). On the other hand, when the value of the attribute item used as the aggregation key is a dummy code (No at Step S303), the aggregation unit 75d groups the public data 73a into the second group (Step S305).

  Thereafter, the grouping is repeatedly performed on all the public data 73a to be generated as a report until the grouping is completed (No at step S306). Then, when the grouping is completed for all the public data 73a to be generated as a report (Yes in step S306), the counting unit 75d displays the numerical items included in the public data 73a grouped in the first group. Aggregation is performed using the value of the attribute item whose value is the aggregation key (step S307). Subsequently, the totaling unit 75d totals the values of the numerical items included in the public data 73a grouped in the second group (Step S308).

  Then, the display control unit 75e generates, as a report, a chart such as a table or a graph including the aggregation result of the first group and the aggregation result of the second group that are aggregated by the aggregation unit 75d (step S309). Finally, the display control unit 75e transmits the report generated in step S309 to the head office terminal 50 (step S310), and ends the process.

[Effect of Example 1]
As described above, the monitoring server 70 according to the present embodiment separately counts numerical data items of business data having no error and business data having an error in the code of the attribute item of the type specified as the total key. Each count result is displayed. Therefore, the monitoring server 70 according to the present embodiment can perform aggregation including numerical items of codes that are not included in the unified code. As a result, it is possible to accurately present the total amount of numerical values of numerical items related to various operations. Therefore, according to the monitoring server 70 concerning a present Example, the situation regarding various operations can be grasped correctly.

  Although the embodiments related to the disclosed apparatus have been described above, the present invention may be implemented in various different forms other than the above-described embodiments. Therefore, another embodiment included in the present invention will be described below.

[Business data]
For example, in the above-described first embodiment, a case where slip data related to a sales plan is collected as an example of business data is illustrated, but the disclosed system can be similarly applied to a case where business data other than a sales plan is collected. . As an example, the disclosed apparatus can collect business data such as a product procurement schedule or a procurement record as business data related to a sales department, in addition to a sales plan. As another example, the disclosed apparatus can also collect business data relating to production schedules, production results, consumption material use schedules, consumption material use results, defect results, and the like as business data related to the production department. As a further example, the disclosed apparatus can collect business data related to the budget and balance of each account item as business data related to the finance department. As another example, the disclosed apparatus can collect business data related to inventory, inventory adjustment, cost, etc. as business data related to the inventory management department.

[Consumption data generation timing]
In the first embodiment described above, the case has been described where dummy data consumption data is generated on condition that a dummy data correction slip is issued from the base server 30. However, dummy data correction is not necessarily required for generation of consumption data. No voucher is required. For example, the disclosed apparatus can also generate consumption data for the conversion history data 13d having the base code when the base code and the unified code are newly associated with the unified code master 13b. . In this case, it is not always necessary to accept a dummy data correction slip.

[Distribution and integration]
In addition, each component of each illustrated apparatus does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured.

  For example, the reception unit 15a, the conversion unit 15b, the generation unit 15c, the aggregation unit 15d, or the notification unit 15e may be connected as an external device of the master server 10 via a network. In addition, the functions of the master server 10 described above are realized by having a receiving unit 15a, a converting unit 15b, a generating unit 15c, a totaling unit 15d, or a notifying unit 15e, which are connected to a network and cooperate with each other. You may do it.

  Further, the registration unit 75a, the login processing unit 75b, the setting acquisition unit 75c, the totaling unit 75d, or the display control unit 75e may be connected as an external device of the monitoring server 70 via a network. In addition, the log-in processing unit 75b, the setting acquisition unit 75c, the totaling unit 75d, or the display control unit 75e are provided in different devices, and the functions of the monitoring server 70 are realized by being connected to the network and cooperating. It may be.

[Analysis program]
The various processes described in the above embodiments can be realized by executing a prepared program on a computer such as a personal computer or a workstation. In the following, an example of a computer that executes an analysis program having the same function as that of the above-described embodiment will be described with reference to FIG.

  FIG. 20 is a schematic diagram illustrating an example of a computer that executes an analysis program according to the first and second embodiments. As illustrated in FIG. 20, the computer 100 includes an operation unit 110 a, a speaker 110 b, a camera 110 c, a display 120, and a communication unit 130. Further, the computer 100 includes a CPU 150, a ROM 160, an HDD 170, and a RAM 180. These units 110 to 180 are connected via a bus 140.

  As shown in FIG. 20, the HDD 170 stores in advance an analysis program 170a that exhibits the same functions as the login processing unit 75b, the setting acquisition unit 75c, the totaling unit 75d, and the display control unit 75e described in the first embodiment. Is done. The analysis program 170a may be integrated or separated as appropriate, like the respective components of the login processing unit 75b, the setting acquisition unit 75c, the totaling unit 75d, and the display control unit 75e shown in FIG. In other words, all data stored in the HDD 170 need not always be stored in the HDD 170, and only data necessary for processing may be stored in the HDD 170.

  Then, the CPU 150 reads the analysis program 170 a from the HDD 170 and expands it in the RAM 180. Accordingly, as shown in FIG. 20, the analysis program 170a functions as an analysis process 180a. The analysis process 180a expands various data read from the HDD 170 in an area allocated to itself on the RAM 180 as appropriate, and executes various processes based on the expanded data. The analysis process 180a includes processing executed by the login processing unit 75b, the setting acquisition unit 75c, the totaling unit 75d, and the display control unit 75e shown in FIG. 13, for example, the processing shown in FIG. In addition, each processing unit virtually realized on the CPU 150 does not always require that all processing units operate on the CPU 150, and only a processing unit necessary for the processing needs to be virtually realized.

  Note that the analysis program 170a is not necessarily stored in the HDD 170 or the ROM 160 from the beginning. For example, each program is stored in a “portable physical medium” such as a flexible disk inserted into the computer 100, so-called FD, CD-ROM, DVD disk, magneto-optical disk, or IC card. Then, the computer 100 may acquire and execute each program from these portable physical media. In addition, each program is stored in another computer or server device connected to the computer 100 via a public line, the Internet, a LAN, a WAN, etc., and the computer 100 acquires and executes each program from these. It may be.

1 monitoring system 3A, 3B, 3C base 5 head office 9 network 10 master server 11 communication I / F unit 13 storage unit 13a slip data 13b unified code master 13c data for aggregation 13d conversion history data 13e summary level data 13f product type master 15 control unit 15a reception unit 15b conversion unit 15c generation unit 15d aggregation unit 15e notification unit 30A, 30B, 30C base server 50 head office terminal 70 monitoring server 71 communication I / F unit 73 storage unit 73a public data 75 control unit 75a registration unit 75b login processing unit 75c Setting acquisition unit 75d Totaling unit 75e Display control unit

Claims (4)

On the computer,
Get the setting of attribute item type related to business,
Of the business data stored in the business data storage unit that stores business data associated with business-related attribute items and numerical items, no error code indicating an error is assigned to the attribute item of the type for which the setting has been acquired. Aggregate the values of numeric items for the first business data,
Aggregating the value of the numeric item for the second business data in which the error code is assigned to the attribute item of the type from which the setting is acquired among the business data stored in the business data storage unit,
An analysis program for executing processing for causing a predetermined device to display a tabulation result of numeric items of the first business data and a tabulation result of numeric items of the second business data. As a process for displaying the total result,
Of the attribute items included in the first business data, other tabulation results including the first business data in which the error code is assigned to an attribute item of a type other than the type for which the setting has been acquired The analysis program according to claim 1, wherein the analysis program is displayed separately from the result display mode. A business data storage unit that stores business data associated with business-related attribute items and numerical items;
A setting acquisition unit that acquires settings of attribute item types related to business;
Aggregating the values of numerical items for the first business data to which no error code indicating an error is assigned to the attribute item of the type from which the setting is acquired among the business data stored in the business data storage unit, A counting unit that counts the value of the numeric item for the second business data in which the error code is assigned to the attribute item of the type for which the setting is acquired;
An analysis apparatus comprising: a display control unit that causes a predetermined device to display a total result of numerical items of the first business data and a total result of numerical items of the second business data. Computer
Get the setting of attribute item type related to business,
Of the business data stored in the business data storage unit that stores business data associated with business-related attribute items and numerical items, no error code indicating an error is assigned to the attribute item of the type for which the setting has been acquired. Aggregate the values of numeric items for the first business data,
Aggregating the value of the numeric item for the second business data in which the error code is assigned to the attribute item of the type from which the setting is acquired among the business data stored in the business data storage unit,
An analysis method for executing processing for displaying a total result of numerical items of the first business data and a total result of numerical items of the second business data on a predetermined device.

Images