JP2018190381A - Data aggregation device, data aggregation method and data aggregation program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a data aggregation device, a data aggregation method and a data aggregation program capable of efficiently aggregating numerical values with respect to an object even for plural objects having hierarchical structures.SOLUTION: A data aggregation device: (1) acquires lowest layer identification data associated with input hierarchical structure identification data by referring to object management data including hierarchical structure identification data to identify a hierarchical structure with objects organized in lowest and higher layers and the lowest layer identification data to identify an object in the lowest layer; (2) extracts numerical values associated with the acquired lowest layer identification data by referring to aggregation object data including the lowest layer identification data and the numerical values; and (3) aggregates the extracted numerical values.SELECTED DRAWING: Figure 14

Description

  The present invention relates to a data aggregation device, a data aggregation method, and a data aggregation program.

  Patent Document 1 discloses an analysis support processing apparatus that supports analysis of sales, purchases, and other performance data accumulated in a backbone system and a program thereof (see paragraph 0001, etc.).

JP 2011-248435 A

  In the field of management accounting, when a target such as a company has a hierarchical structure as shown in FIGS. 5 to 7, it is difficult to efficiently count numerical values such as sales amounts for the target. there were.

  The present invention has been made in view of the above, and provides a data tabulation apparatus, a data tabulation method, and a data tabulation program capable of efficiently tabulating numerical values of objects even when the objects have a hierarchical structure.

  In order to solve the above-described problems and achieve the object, a data tabulation apparatus according to the present invention is a data tabulation apparatus including a control unit, and the control unit includes a target of a lower layer and a target of an upper layer. Is input with reference to object management data including hierarchical structure identification data for identifying a hierarchical structure formed by forming a hierarchy and lowest layer identification data for identifying the object of the lowest layer Acquisition means for acquiring the lowest layer identification data associated with the hierarchical structure identification data, referring to the aggregation target data including the lowest layer identification data and numerical values, and the lowest layer identification data acquired by the acquisition means; It is characterized by comprising an extracting means for extracting a numerical value to be associated, and a summing means for summing up the numerical values extracted by the extracting means.

  Further, in the data tabulation apparatus according to the present invention, the target management data includes a record having information on a target of each layer from the highest layer to the lowest layer in the hierarchical structure, and the record includes the hierarchical structure Identification data, hierarchical identification data for identifying each hierarchy in the hierarchical structure, target identification data for identifying the object, higher hierarchy identification data for identifying a hierarchy one level higher than each hierarchy, and the object And a lower layer record, which is a record having information about the object of the lowest layer, further includes the lowest layer identification data. The acquisition unit refers to the target management data, acquires a record including the input hierarchical structure identification data, and the record acquisition unit. The lowest layer record acquisition unit that acquires the lowest layer record from the record acquired by the mode acquisition unit, and the upper layer identification data and the upper target identification included in the lowest layer record acquired by the lowest layer record acquisition unit A record including the same hierarchical identification data and target identification data as the data is acquired by referring to the target management data, and the acquired record includes the lowest layer record acquired by the lowest layer record acquisition unit. Hierarchy identification data input with reference to the record creation means for creating a record to which lower layer identification data is added, the lowest layer record acquired by the lowest layer record acquisition means, and the record created by the record creation means To obtain the lowest layer identification data included in the record. Further comprising a lowest layer data acquiring means, and characterized.

  Further, in the data totaling apparatus according to the present invention, the record creating means includes a record including the same hierarchy identification data and target identification data as the upper hierarchy identification data and the upper target identification data included in the record created by the record creation means. , Referring to the target management data, and creating a record in which the lowest layer identification data included in the lowest layer record acquired by the lowest layer record acquisition unit is added to the acquired record, It repeats until it adds the lowest layer identification data contained in the lowest layer record acquired by the lowest layer record acquisition means to the record which has the information about the object of the highest layer.

  Further, in the data tabulation apparatus according to the present invention, the tabulation unit includes the numerical value extracted by the extraction unit, the hierarchical structure identification data, the layer identification data, and the object identification included in the record acquired by the lowest layer data acquisition unit. It is characterized by referring to aggregation key data including a plurality of details including a combination of data, specifying the details having the same combination, and aggregating numerical values included in the specified details.

  In the data tabulation apparatus according to the present invention, the tabulation unit refers to tabulation key data including a plurality of details including the numerical value extracted by the extraction unit and the item identification data, and the item identification data is the same. If there is a detail, only one of the details is left and the other details are deleted to update the aggregation key data, and the numerical values included in the details included in the updated aggregation key data are aggregated It is characterized by this.

  In addition, the data tabulation method according to the present invention is a data tabulation method executed by an information processing apparatus including a control unit, and the lowest layer target and the upper layer target executed by the control unit are hierarchical. Referring to target management data including hierarchical structure identification data for identifying a hierarchical structure formed by forming and lowermost layer identification data for identifying a target of the lowest layer, an input hierarchy The acquisition step for acquiring the lowest layer identification data associated with the structure identification data, and the aggregation target data including the lowest layer identification data and numerical values are referred to and associated with the lowest layer identification data acquired in the acquisition step. It includes an extraction step for extracting numerical values, and a counting step for totaling the numerical values extracted in the extraction step.

  Further, the data totaling program according to the present invention is a data totaling program for causing an information processing apparatus including a control unit to execute, wherein the target of the lowest layer and the target of the upper layer for causing the control unit to execute Is input with reference to object management data including hierarchical structure identification data for identifying a hierarchical structure formed by forming a hierarchy and lowest layer identification data for identifying the object of the lowest layer An acquisition step of acquiring the lowest layer identification data associated with the hierarchical structure identification data, and referring to the aggregation target data including the lowest layer identification data and a numerical value, and the lowest layer identification data acquired in the acquisition step; The method includes an extraction step of extracting a numerical value to be associated, and a counting step of totaling the numerical values extracted in the extraction step.

  According to the present invention, even when the objects have a hierarchical structure, it is possible to efficiently count the numerical values for the objects.

FIG. 1 is a block diagram illustrating an example of the configuration of the information processing apparatus. FIG. 2 is a diagram illustrating a conventional setting example in data when performing data aggregation. FIG. 3 is a diagram showing an outline of the hierarchical object management information. FIG. 4 is a diagram illustrating an example of data in the hierarchical object management information. FIG. 5 is a diagram showing the organization chart (1). FIG. 6 is a diagram showing an organization chart (2). FIG. 7 shows an organization chart (3). FIG. 8 is a diagram illustrating an example of a management number, a hierarchy level, and a node identification code input when performing data aggregation. FIG. 9 is a diagram illustrating a record including the input management number acquired by referring to the hierarchical object management information. FIG. 10 is a diagram illustrating a flow of acquiring a record having a hierarchy level of 2 with reference to the acquired record. FIG. 11 is a diagram illustrating a flow of acquiring a record having a hierarchy level of 1 with reference to the hierarchized object management information based on the acquired record having a hierarchy level of 2. FIG. 12 is a diagram showing a flow of acquiring a record with a hierarchy level of 0 by referring to the hierarchized object management information based on the acquired record with a hierarchy level of 1. FIG. 13 is a diagram illustrating a flow of acquiring a record including an input hierarchy level and a node identification code with reference to records having acquired hierarchy levels of 2, 1, 0. FIG. 14 is a diagram illustrating a flow of extracting the aggregation target value by referring to the aggregation target data based on the association code included in the acquired record. FIG. 15 is a diagram showing a totaling result (when double count is not removed) of the extracted totaling target values. FIG. 16 is a diagram illustrating an example of total key information data. FIG. 17 is a diagram illustrating an example of an aggregation result (when double count is removed) of extracted aggregation target values. FIG. 18 is a diagram illustrating a conventional setting example in data when performing security management. FIG. 19 is a diagram illustrating an example of data in user information and user group information. FIG. 20 is a diagram illustrating an example of data in the user group affiliation information. FIG. 21 is a diagram showing to which user group each user belongs. FIG. 22 is a diagram illustrating an example of data in the authority setting information. FIG. 23 is a diagram illustrating a range of organizations that can be referred to by each user group. FIG. 24 is a diagram showing a range of organizations that can be referred to by each user group in the organization chart (1). FIG. 25 is a diagram showing a range of organizations that can be referred to by each user group in the organization chart (2). FIG. 26 is a diagram showing a range of organizations that can be referred to by each user group in the organization chart (3). FIG. 27 is a diagram illustrating an example of data in the hierarchical object management information. FIG. 28 is a diagram illustrating an example of data in the authority setting information. FIG. 29 is a diagram illustrating an example of data in the user group affiliation information. FIG. 30 is a diagram showing to which user group each user belongs. FIG. 31 is a diagram illustrating an example of a management number and a user ID input when performing data aggregation. FIG. 32 is a diagram illustrating a user group code acquired by referring to the user group affiliation information based on the input user ID. FIG. 33 is a diagram illustrating a hierarchy level and a node identification code acquired by referring to the authority setting information based on the input management number and the acquired user group code. FIG. 34 is a diagram illustrating a record acquired by referring to the hierarchical object management information based on the input management number and the acquired hierarchy level and node identification code. FIG. 35 is a diagram illustrating records further acquired by referring to the hierarchical object management information based on the acquired records. FIG. 36 is a diagram illustrating an example of data in the hierarchical object security development information. FIG. 37 is a diagram illustrating a record acquired by referring to the hierarchical object deployment information based on the hierarchical object security deployment information. FIG. 38 is a diagram illustrating a conventional setting example in data when performing internal transaction determination. FIG. 39 is a conceptual diagram of conventional internal transaction determination. FIG. 40 is a diagram illustrating an example of data in hierarchical object management information that manages a hierarchical structure including virtual organizations. FIG. 41 is a diagram illustrating an example of data in hierarchical object management information for managing a hierarchical structure including virtual segments. FIG. 42 is a diagram illustrating an example of a hierarchical structure including both a virtual organization and a virtual segment. FIG. 43 is a diagram showing an outline of the supplier identification item setting information. FIG. 44 is a diagram illustrating an example of data in the supplier specific pattern setting information. FIG. 45 is a diagram showing transaction contents defined by data examples in the supplier identification pattern setting information. FIG. 46 is a diagram illustrating an example of data in the aggregation target source data. FIG. 47 is a diagram illustrating a flow of updating the aggregation target source data based on the record in the first line of the supplier identification pattern setting information. FIG. 48 is a diagram illustrating a flow of updating the aggregation target source data based on the record in the second line of the supplier identification pattern setting information. FIG. 49 is a diagram illustrating a flow of creating the aggregation target data by updating the aggregation target original data based on the records on and after the third line of the supplier identification pattern setting information. FIG. 50 is a diagram illustrating an example of a management number, a hierarchy level, and a node identification code that are input when internal transaction determination is performed. FIG. 51 is a diagram illustrating an example of data in hierarchical object extraction information for a virtual organization. FIG. 52 is a diagram showing a matching result between the company code and the like included in the hierarchical object extraction information and the company code and the like of the own organization included in the aggregation target data. FIG. 53 is a diagram showing a matching result between the company code and the like included in the hierarchized object extraction information and the partner company code and the like of the partner organization included in the aggregation target data. FIG. 54 is a diagram showing records in which the combination of the management number, the hierarchy level, and the node identification code is the same in the hierarchical object extraction information. FIG. 55 is a diagram showing the result of the internal / external determination made based on the matching result. FIG. 56 is a diagram illustrating an example of a totaling result obtained by counting the numerical values included in the totaling target data in consideration of the result of the internal / external determination. FIG. 57 is a diagram showing an example of data in the hierarchical object extraction information for the virtual segment. FIG. 58 is a diagram showing a matching result between the analysis code included in the hierarchized object extraction information and the analysis code of the own segment included in the aggregation target data. FIG. 59 is a diagram illustrating a matching result between the analysis code included in the hierarchized object extraction information and the partner analysis code of the partner segment included in the aggregation target data. FIG. 60 is a diagram illustrating records in which the combination of the management number, the hierarchy level, and the node identification code is the same in the hierarchical object extraction information. FIG. 61 is a diagram illustrating a result of segment inside / outside determination performed based on the matching result. FIG. 62 is a diagram illustrating an example of a totaling result obtained by counting the numerical values included in the totaling target data in consideration of the result of the segment internal / external determination. FIG. 63 is a diagram showing the results of the tissue internal / external determination and the segment internal / external determination. FIG. 64 is a diagram illustrating an example of a totaling result obtained by counting the numerical values included in the totaling target data in consideration of the result of internal / external determination and the result of internal / external segment determination. FIG. 65 is an image diagram of internal transaction determination according to the present embodiment. FIG. 66 is an image diagram of internal transaction determination according to the present embodiment in consideration of security management. FIG. 67 is a diagram showing an outline of conversion item setting information. FIG. 68 is a diagram illustrating an example of data in the conversion pattern setting information. FIG. 69 is a diagram illustrating an example of data in the conversion target data. FIG. 70 is a diagram showing a flow of converting conversion source data in conversion target data into conversion destination data based on the record in the first line of the conversion pattern setting information. FIG. 71 is a diagram showing a flow of converting conversion source data in conversion target data into conversion destination data based on the record in the second line of the conversion pattern setting information. FIG. 72 is a diagram showing a flow of converting conversion source data in conversion target data into conversion destination data based on the record in the third row of the conversion pattern setting information. FIG. 73 is a diagram illustrating the conversion target data after the conversion of all the conversion source data to the conversion destination data is completed. FIG. 74 is a diagram illustrating an example of how common data (conversion destination data) is allocated to virtual segments. FIG. 75 is a diagram showing the hierarchical structure of the organization before the reorganization and the hierarchical structure of the organization after the reorganization. FIG. 76 is a diagram illustrating an output example of multi-element data.

  Hereinafter, embodiments of a data totaling apparatus, a data totaling method, and a data totaling program according to the present invention will be described in detail with reference to the drawings. In addition, this invention is not limited by this embodiment.

[1. Overview]
In fields such as management accounting, methods for grouping and tabulating data from various perspectives have been devised when tabulating and analyzing data. There is also a method of grouping data in a virtual hierarchy (virtual organization and virtual segment information, etc.), but the type and number of data items assigned to each hierarchy are fixed, inflexible, and the data pattern When the number increases, there is a problem that the setting needs to be changed each time. In addition, if the analysis method is changed, necessary items may be changed, and there is a problem that the program needs to be changed.

  Specifically, three items of “company code”, “office code”, and “department code” are set as aggregation conditions from the journal entry details shown in FIG. If you want to aggregate journal entries, you need to list all company codes, office codes, and department codes that exist in the Hokkaido area that you want to aggregate in the <Linking information with actual organization> shown in Figure 2 . In this way, in the table for managing the virtual organization, when the three types of “company code”, “office code” and “department code” are managed as the association with the real organization, all the association information is included in the association information. There was a need to enumerate the assignments, and there were the following three issues. First, the required number of items was fixed and there was no flexibility. Second, as the number of linked data increases, the setting increases, which is complicated. Thirdly, if the items increase or decrease from the items “Company Code”, “Office Code”, and “Department Code” that you want to use for pegging, it is necessary to change the program.

Therefore, in the present embodiment, a flexible data aggregation setting function and aggregation method using an object (target) having a hierarchical structure is provided. In the present embodiment, in the hierarchical object that groups data, the allocation items to be allocated to the data to be aggregated can be flexibly set by the following methods 1 to 3.
1. The contents of assigned items and the number of assigned items are variable.
2. The required / arbitrary selection of assignment items was made possible.
3. For any assigned item, it is now possible to specify a reserved word that means omitting the assignment condition.

As a result, according to the present embodiment, for example, in the virtual organization / virtual segment structure used in management accounting analysis, as shown in the following 1-3, data can be aggregated in units of free allocation items. became.
1. Company code only Company code + department code 3. Segment Code A specific configuration and operation will be described below.

[2. Constitution]
A configuration of the information processing apparatus 100 including the present invention will be described with reference to FIG. FIG. 1 is a block diagram illustrating an example of the configuration of the information processing apparatus 100.

  The information processing apparatus 100 is a commercially available desktop personal computer. The information processing apparatus 100 is not limited to a stationary information processing apparatus such as a desktop personal computer, but is a portable type such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer. An information processing apparatus may be used.

  As illustrated in FIG. 1, the information processing apparatus 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each unit included in the information processing apparatus 100 is communicably connected via an arbitrary communication path.

  The communication interface unit 104 connects the information processing apparatus 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the information processing apparatus 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that data stored in the storage unit 106 to be described later may be stored in the server 200.

  An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, a speaker (including a home television), a speaker, and a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that realizes a pointing device function in cooperation with the mouse can be used. In the following description, the output device 114 may be described as a monitor 114 as a display unit, and the input device 112 may be described as a keyboard 112 or a mouse 112.

  The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for giving various instructions to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) and a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, and an optical disk can be used.

  The storage unit 106 includes, for example, hierarchical object management information 106a as target management data, hierarchical object expansion information 106b as target expansion data, hierarchical object extraction information 106c as target extraction data, and aggregation target data 106d. Tabulation result data 106e, tabulation key information data 106f as tabulation key data, user group affiliation information 106g as user management data, authority setting information 106h as group management data, authority extraction information 106i, hierarchy Object security deployment information 106j, supplier identification item setting information 106k, supplier identification pattern setting information 106l as transaction pattern setting data, aggregation object source data 106m, aggregation object data 106n, and aggregation result data 106 When comprises a converting item setting information 106p, a conversion pattern setting information 106q as converted pattern setting data, and the converted data 106r, a conversion completion data 106s, the.

  Further, in the present embodiment, the “target (object)” is, for example, a real organization (for example, a real company, a business office, or a department) that is a real organization, or a virtual organization (for example, a real organization) (Organized organization or reorganized organization) for real simulation, real segment that is a real segment (for example, real business segment, area or brand), or virtual segment that is a virtual segment (for example, real segment) It means a segment or segment that has been hierarchized for simulation). Specific examples of the real organization, virtual organization, real segment, and virtual segment are shown in the hierarchical structure of FIG. In the present embodiment, the hierarchical structure means a structure formed by forming the hierarchy of the object of the lowest layer and the object of the upper layer.

  The hierarchical object management information 106a is information for managing the hierarchical structure. As shown in FIG. 3, the hierarchical object management information 106a includes, for example, hierarchical structure identification data (management number), management name, hierarchical identification data (hierarchy level), target identification data (node identification code), node name, upper level It includes hierarchy identification data (upper hierarchy level), upper target identification data (upper node identification code), lower structure classification, lowest layer identification data (linked code), and the like.

  The management number is data for identifying the hierarchical structure. Specifically, the management number of the hierarchical structure shown in FIG. 5 is (1), the management number of the hierarchical structure shown in FIG. 6 is (2), and the management number of the hierarchical structure shown in FIG. 7 is (3). In this way, a management number can be set for each hierarchical structure. The management name is a name corresponding to the management number.

The management number and the management name are collectively referred to as a hierarchical object identification information section as shown in FIG. Here, the recording method of data to be recorded in the hierarchical object management information 106a is based on the following rules 1 and 2 for the hierarchical object identification information part.
1. A unique management number is assigned to each hierarchical object to be managed.
2. A management name that can be identified by the user is set for the unique management number.

  The hierarchy level is data for identifying each hierarchy in the hierarchy structure. The highest hierarchy is the hierarchy level 0, and thereafter, the hierarchy level increases by one each time the hierarchy advances one level lower. For example, in the organization chart (1) shown in FIG. 5, the entire company is at hierarchical level 0 (that is, the highest layer), and the companies 1 to 3 are at hierarchical level 1 (that is, the lowest layer). An example of setting the hierarchical level is shown in FIG.

  The node identification code is data for identifying a target. For example, in the organization chart (1) shown in FIG. 5, the node identification code for the entire company is set to 10000, the node identification code for company 1 is set to 01000, the node identification code for company 2 is set to 02000, and the node identification code for company 3 is set. A node identification code can be set for each object, such as 03000. The node name is a name corresponding to the node identification code. An example of setting the node identification code and the node name is shown in FIG.

  The upper hierarchy level is data for identifying a hierarchy one level higher than each hierarchy. For example, the hierarchical level of the companies 1 to 3 in the organization chart (1) shown in FIG. 5 is 1, but the hierarchical level of the hierarchy one level higher than the companies 1 to 3 is 0. The hierarchy level is 0. An example of setting the upper hierarchy level is shown in FIG.

  The higher-level node identification code is data for identifying the target of the hierarchy one level higher than the target of each hierarchy. For example, in the case of the companies 1 to 3 in the organization chart (1) shown in FIG. 5, since the node identification code of the entire company that is the target of the upper hierarchy is 10000 as described above, the upper nodes for the companies 1 to 3 The identification code is 10,000. An example of setting the upper node identification code is shown in FIG.

  The lower structure classification is a classification indicating whether or not a lower hierarchy exists. For example, in the organization chart (1) shown in FIG. 5, since there is a lower hierarchy when viewed from the entire company, the lower structure classification for the entire company is “0: lower level”. On the other hand, since there is no lower hierarchy as seen from the companies 1 to 3, the lower structure classification for the companies 1 to 3 is “1: No lower”. An example of setting the substructure classification is shown in FIG.

The hierarchy level, the node identification code, the node name, the higher hierarchy level, the higher node identification code, and the lower structure classification are collectively referred to as a hierarchy structure information section as shown in FIG. Here, the recording method of the data to be recorded in the hierarchical object management information 106a is based on the following rules 1 to 5 for the hierarchical structure information part. Note that the upper hierarchy level and the lower structure classification are not essential items in the present invention, but the program processing procedure is simpler if the data is retained in the process of specifying the upper and lower levels of the hierarchical node. It is an item that is being prepared to become.
1. A hierarchy level (0 to N) for identifying the hierarchy of the hierarchized object is set.
2. A unique node identification code is assigned to each same management number / hierarchy level.
3. A node name that can be identified by the user is set for the unique node identification code.
4). For each hierarchical node, the hierarchical level (higher hierarchical level) and the node identification code (higher node identification code) of the parent node to which it belongs are set.
5. For each hierarchical node, a substructure section is set that distinguishes whether it is the lowest node or a child node.

  The lowest layer identification data is data for identifying the target of the lowest layer, and may be called a tied code. Specific examples of the lowest layer identification data include, for example, company identification data (company code) for identifying a company, establishment identification data (establishment code) for identifying an establishment in a company, and a company Department identification data (department code) for identifying the department in the company or business contents identification data (analysis code) for identifying the business contents in a certain company. FIG. 4 and FIG. 40 show setting examples of the hierarchized object management information 106a when the company code, the office code, and the department code are used as the lowest layer identification data. FIG. 41 shows an example of setting the hierarchical object management information 106a when an analysis code is used as the lowest layer identification data.

  Since the lowest layer identification data is data for identifying the object of the lowest layer, as described above, the lowest layer identification data is not assigned to a target higher than the lowest layer. For example, in the hierarchical object management information 106a of FIG. 3, since the companies 1 to 3 (records in the second to fourth lines from the top) are targets of the lowest layer, the association codes 1 to 3 are used as the lowest layer identification data. However, since the entire company (record on the first line from the top) is not the object of the lowest layer, the lowest layer identification data is not assigned, and the column of the association code is “NULL”. "

The lowest layer identification data (correlation code) is referred to as an association information part as shown in FIG. Here, the recording method of data to be recorded in the hierarchical object management information 106a is based on the following rules 1 to 5 for the association information part. The character strings of <NULL> meaning no setting and <ALL> meaning all are not limited to this, and may be other character strings.
1. The system assumes the maximum number of items that are the aggregation keys for the data to be aggregated. 2. In each node, when the lower structure classification is “with lower”, since there is no need to hold the association information, the reserved word <NULL> meaning no setting is held.
3. When the lower structure classification is “no lower”, each code to be linked is retained. At this time, the following rules 4 and 5 are applied.
4). An item that is indispensable as a tied item always holds a tied code.
5. For items that are optional as linked items, a code is specified when a breakdown is set, and a reserved word <ALL> meaning all is stored when a breakdown is not specified.

  Here, FIG. 4 shows a data example of the hierarchical object management information 106a in which specific information is set. In FIG. 4, a maximum of three items of “company CD (company code)” (required), “office CD” (optional), and “department CD” (optional) are employed as the association information. In addition, “company CD” which is an essential item is all designated in the organization charts (1) to (3) of the data example. In the organization charts (1) and (2), since only the organization in the company unit is assigned, the “establishment CD” and “department CD” are all designated reserved words <ALL>. It is in the state. Further, in the organization chart (3), since the organization allocation in the unit of company + establishment is included, the “department CD” is in a state where the reserved word <ALL> meaning all is designated, Since the company 3 does not need to assign the “establishment CD”, the reserved word <ALL> meaning all is designated. In FIG. 4, the organization chart number is synonymous with the management number, the organization chart name is synonymous with the management name, the organization level is synonymous with the hierarchy level, and the organization CD is synonymous with the node identification code. The name is synonymous with the node name, the upper organization level is synonymous with the upper hierarchy level, and the upper organization CD is synonymous with the upper node identification code.

  Organizational charts (1) to (3) represented by data examples of the hierarchical object management information 106a in FIG. 4 are shown in FIGS.

  Here, the hierarchized object management information 106a may include a record having information on targets of each hierarchy from the highest layer to the lowest layer in the hierarchical structure. The record is information on one horizontal line in the table of the hierarchical object management information 106a shown in FIG. As shown in FIG. 3, the record includes, for example, hierarchical structure identification data (management number), management name, hierarchy identification data (hierarchy level), object identification data (node identification code), node name, upper hierarchy identification data (upper hierarchy) Hierarchy level), upper target identification data (upper node identification code), lower structure classification, and the like. Further, the lowest layer record (three records having a hierarchical level of 1 in FIG. 3) that is a record having information about the lowest layer further includes, for example, lowest layer identification data (correlation code).

  The hierarchized object development information 106b, which will be described in detail later, is a record having information on the target of the layer one higher than the lowest layer in the layered object management information 106a. It is the information which expanded. As shown in FIG. 12, the hierarchical object development information 106b includes, for example, hierarchical structure identification data (management number), hierarchical identification data (hierarchy level), target identification data (node identification code), upper hierarchy identification data (upper hierarchy) Level), upper level object identification data (upper node identification code), and lowest level layer identification data (correlation code).

  Although the details will be described later, the hierarchized object extraction information 106c is information obtained by extracting only the records including the hierarchy level input by the user from the records included in the hierarchized object expansion information 106b. As shown in FIG. 13, the hierarchical object extraction information 106c includes, for example, hierarchical structure identification data (management number), hierarchical identification data (hierarchy level), target identification data (node identification code), upper hierarchy identification data (upper hierarchy) Level), upper level object identification data (upper node identification code), and lowest level layer identification data (correlation code).

  The aggregation target data 106d is data to be aggregated. As shown in FIG. 14, the aggregation target data 106d includes the lowest layer identification data (correlation code) and a numerical value (aggregation target value). Information on one horizontal line in the aggregation target data 106d is referred to as a detail. Therefore, the aggregation target data 106d may further include detailed identification data (detail ID) for each detail as shown in FIG.

  The aggregation result data 106e is data indicating a result obtained by aggregating the aggregation target data 106d. As shown in FIGS. 15 and 17, the aggregation result data 106e includes, for example, hierarchical structure identification data (management number), hierarchy identification data (hierarchy level), target identification data (node identification code), and aggregation results.

  Although details will be described later, the total key information data 106f is data indicating a list of a plurality of details extracted by the extraction unit 102b. As shown in FIG. 16, the plurality of details are, for example, hierarchical structure identification data (management number), hierarchical identification data (hierarchy level), target identification data (node identification code), detailed identification data (detail ID), and aggregation target Including values.

  The user information is information for managing IDs and names that uniquely identify users. The user information includes, for example, user identification data (user ID or user name) as shown in the upper table of FIG.

  The user group information is information for managing a unit for grouping users. The user group information includes, for example, user group identification data (user group code or user group name) as shown in the lower table of FIG.

  The user group affiliation information 106g is information for managing users belonging to the user group. As shown in FIG. 20, the user group affiliation information 106g includes, for example, user group identification data (user group code) and user identification data (user ID). Here, when the user group affiliation information 106g is set as shown in FIG. 20, which user group each user belongs to is shown in FIG. Note that a single user can belong to a plurality of user groups, as shown in FIG. 21, such as UserC and UserD.

  The authority setting information 106h is information that holds a reference authority to the user group for the hierarchical object. As shown in FIG. 22, the authority setting information 106h includes, for example, hierarchical structure identification data (management number), hierarchical identification data (hierarchy level), target identification data (node identification code), and user group identification data (user group code). Etc. In the authority setting information 106h, a plurality of user group codes can be associated with one node identification code.

  Here, when the authority setting information 106h is set as shown in FIG. 22, it is shown in FIG. 23 which organization information each user group can refer to. As shown in FIG. 23, since the full authority group (UserA) can refer to the information of the entire company, it can also refer to the information of the companies 1 to 3 which are the lower layers of the entire company (the upper viewing authority is changed). Because the person who has it automatically has all subordinate browsing rights). On the other hand, the group 1 authority group (UserB and UserC) can only refer to the information of the company 1, the group 2 authority group (UserC and UserD) can refer only to the information of the company 2, and the group 3 authority group (UserD) can refer to the company. Only information 3 can be referenced. A person who belongs to a plurality of authority groups has the authority to view both companies.

  In the present embodiment, a flag for switching whether to manage the authority setting of the hierarchical object may be held in order to set whether or not the authority (security) setting is to be performed. Examples of the flag include a “use” flag which means that authority is set and a “not use” flag which means that authority is not set.

  Here, in the present embodiment, what kind of data setting is specifically performed and what kind of data reference authority management can be performed will be described with reference to FIGS.

  First, the hierarchical structure of the organization can be set by the hierarchical object management information 106a. A case where the hierarchical object management information 106a is set as shown in FIG. 27 will be described. As shown in FIG. 24, the hierarchical structure represented by the record indicated by MA5 in FIG. As shown in FIG. 25, the hierarchical structure represented by the record denoted by MA6 in FIG. As shown in FIG. 26, the hierarchical structure represented by the record indicated by MA7 in FIG.

  The reference authority for the target in the hierarchical structure can be managed by the user group affiliation information 106g and the authority setting information 106h. When the user group affiliation information 106g is set as shown in FIG. 29 (which group each user belongs to is shown in FIG. 30), and the authority setting information 106h is set as shown in FIG. The range of information that can be referred to by each user group is as shown in the next paragraph. Note that a record indicated by MA8 in FIG. 28 is a record for managing browsing of objects in a virtual organization in which all companies are arranged under the entire company shown in FIG. 24, and a record indicated by MA9 in FIG. 28 is the entire company in FIG. , The core company tier by business, and the hierarchy of each individual company, the record that manages the browsing of the target in the three levels, the record indicated by MA10 in FIG. 29 is the target browsing in the virtual organization of the sales department by area It is a record to be managed.

  That is, as shown in FIG. 24, User A belonging to the user group “Full” can refer to information of all of the companies 100 to 300 that are lower layers of the entire company. Although not shown in FIG. 24, UserB and UserC belonging to the user group “Company1” can refer to the information of the company 100, and UserC and UserD belonging to the user group “Company2” can refer to the information of the company 200. User D belonging to the user group “Company 3” can refer to the information of the company 300. Then, as shown in FIG. 25, User A belonging to the user group “Full” can refer to all the information of the companies 100 to 400 that are lower layers of the entire company, and User B belonging to the user group “KougiGroup” is the construction business group. User D belonging to the user group “Seizou Group” can refer to information of the companies 300 and 400 which are lower layers of the manufacturing business group. As indicated by MA4 in FIG. 25, these three groups have different visible target ranges depending on the ranges in which reference is permitted. Further, as shown in FIG. 26, UserA belonging to the user group “Full” is a lower layer of the entire company (company 100, Tokyo head office, sales department), (company 200, Tokyo head office, sales department), (company 100). , Osaka Branch, Sales Department) and (Company 200, Osaka Branch, Sales Department), and UserE belonging to the user group “KantouGroup” is a lower layer of the Kanto Group (Company 100, Tokyo Head Office, UserD belonging to the user group “KansaiGroup” is a subordinate layer of the Kansai group (company 100, Osaka branch office, sales department) and (company). 200, Osaka branch office, sales department). In FIGS. 24 to 26, any user who is not permitted cannot access any data (cannot see any target information).

  As described above with reference to FIGS. 24 to 30, according to the present embodiment, the viewing authority can be set at an arbitrary place according to the hierarchical level of the hierarchical object, and flexible with the minimum necessary settings. It is possible to respond.

  Although details will be described later, the authority extraction information 106i is information extracted with reference to the authority setting information 106h based on the management number input by the user and the user group code acquired by the group identification data acquisition unit 102d1. As shown in FIG. 33, the authority extraction information 106i includes, for example, hierarchical structure identification data (management number), hierarchical identification data (hierarchy level), target identification data (node identification code), and user group identification data (user group code). Etc.

  The layered object security development information 106j is information acquired by referring to the layered object management information 106a based on the authority extraction information 106i, details of which will be described later. As shown in FIG. 36, the hierarchized object security deployment information 106j includes, for example, hierarchical structure identification data (management number), hierarchy identification data (hierarchy level), object identification data (node identification code), and the like.

  The supplier specific item setting information 106k defines the combination of the use item of the company's transaction contents (customer code, item code, business office code, etc.) and the use item of the partner information to be specified (business office code, department code, etc.) It is information to do. Specifically, as shown in FIG. 43, as the use items of the company's transaction content, for example, “use” or five items of supplier code, subject code, establishment code, department code, and analysis code are used. “Do not use” can be set. Also, as shown in FIG. 43, for example, “use” or “do not use” is set for the three items of partner office code, partner department code, and partner analysis code as the use items of partner information to be specified. be able to.

  The supplier specific pattern setting information 106l is information for specifying a trading partner, in other words, information for defining pattern information to be specified in accordance with the supplier specific item setting information 106k. The customer specific pattern setting information 106l shown in FIG. 44 is an example of data when “use” is set for all items in the customer specific item setting information 106k described in the previous paragraph. As shown in FIG. 44, the supplier specific pattern setting information 106l includes subject lowest layer identification data (company code, establishment code, department) which is the lowest layer identification data for identifying the subject subject that is the subject of the transaction. Code or analysis code), item identification data (account code) for identifying the account subject to the transaction, customer identification data (customer code) for identifying the subject customer, Partner lower layer identification data (partner company code, partner office code, partner department code or partner analysis code) which is the lowest layer identification data for identifying a certain partner object. The supplier specific pattern setting information 106l may further include a determination order as shown in FIG. The significance of the determination order will be described later.

  In the supplier specific pattern setting information 106l, the character string of the reserved word <ALL> meaning all is not limited to this, and may be another character string. If the code, subject code, establishment code, department code or analysis code) is set in <ALL>, the same transaction has multiple counterparty attribute information (partner company code, partner office code, partner department code or Since it may be associated with the partner analysis code), it is determined uniquely by the order of determination.

  Here, what kind of transaction is defined by the supplier identification pattern setting information 106l shown in FIG. 44 will be described with reference to FIG. First, the transaction defined by the records in the first and second lines (two records with the company code of 100) in the table of FIG. 44 is shown in FIG. As shown in FIG. 45A, the purchase transaction partner of company 100 (company code) / Tokyo (office code) / Eigyo (department code) / product sales business (analysis code) is company 300 (partner company). Code) / Osaka (partner office code) / Hanbai1 (partner department code) / retail business (partner analysis code), the sales partner of the company 100 / Tokyo / Eigyo / product sales business is the company 200 / Tokyo / Seizou1 / Manufacturing business. Next, the transaction defined by the records in the 5th to 6th lines from the top in the table of FIG. 44 (two records with company code 300) is shown in FIG. As shown in FIG. 45 (B), the sales partner of the company 300 / Osaka / Hanbai1 / retail business is the company 100 / Tokyo / Eigyo / product sales business and the company 200 / Osaka / Seizou2 / manufacturing business. Finally, the transaction defined by the records in the 3rd to 4th rows from the top in the table of FIG. 44 (two records with a company code of 200) is shown in FIG. As shown in (C) of FIG. 45, the purchase transaction and sales transaction partners of all the offices, departments, and business fields of the company 200 are the company 100 / Tokyo / Eigyo / product sales business and the company 300 / Osaka / Hanbai1. / Retail business. In addition, business transactions, divisions, and segments are uniquely determined for each business partner in transactions that occur in the manufacturing division.

  The aggregation target source data 106m is data that is the basis for creating the aggregation target data 106n. As shown in FIG. 46, the aggregation target source data 106m includes subject lowest layer identification data (company code, establishment code, department code or analysis code), item identification data (subject code), and customer identification data (customer). Code). On the other hand, the aggregation target original data 106m does not include the partner lowest layer identification data (partner company code, partner office code, partner department code or partner analysis code), and these items are as shown in FIG. "Not set". As shown in FIG. 46, the aggregation target source data 106m further includes the occurrence date (occurrence date) and the numerical value (amount) of the details (the term means information on one horizontal line in the table of the aggregation target source data 106m). Etc. may be included.

  The aggregation target data 106n is data to be aggregated. As shown in FIG. 49, the aggregation target data 106n includes the subject lowest layer identification data (company code, establishment code, department code or analysis code) and the partner lowest layer identification data (partner company code, partner office code, Partner code or partner analysis code). As shown in FIG. 49, the aggregation target data 106n further includes the occurrence date (occurrence date) of the details (the term means information on one horizontal line in the table of the aggregation target data 106n), subject identification data (subject code) ), Supplier identification data (customer code), numerical value (amount), and the like.

  The aggregation result data 106o is data indicating a result obtained by aggregating the aggregation target data 106n. As shown in FIG. 56, the total result data 106o includes, for example, hierarchical structure identification data (management number), hierarchical identification data (hierarchy level), object identification data (node identification code), subject identification data (subject code), group External transaction amount that is the amount of transactions between them, internal transaction amount that is the transaction amount within the group, and total amount that is the total amount of external transaction amount and internal transaction amount.

  The conversion item setting information 106p is used to define a combination of items used in the transaction contents of each company (customer code, item code, establishment code, etc.) and items used for information to be converted (common segment code, etc.). Information. Specifically, as shown in FIG. 67, as the use items of the transaction contents of each company, for example, “use” is made for five items of a supplier code, a subject code, a business establishment code, a department code, and an analysis code. Or “not used” can be set. As shown in FIG. 67, for example, “use” or “not use” can be set for the item of common segment code as the use item of information to be converted.

  The conversion pattern setting information 106q is information for specifying a combination of conversion source data and conversion destination data. In other words, the conversion pattern setting information 106q is information for defining pattern information to be specified in accordance with the conversion item setting information 106p. The conversion pattern setting information 106q shown in FIG. 68 is an example of data when “use” is set for all items in the conversion item setting information 106p described in the previous paragraph. The conversion pattern setting information 106q includes conversion source data and conversion destination data.

  The conversion source data consists of a plurality of data. The multiple data items are: Item identification data (account code) for identifying the account subject, establishment identification data (office code) for identifying the establishment in a company, department for identifying a department in a company Preferably, the data is at least two data selected from the group consisting of identification data (department code) and business content identification data (analysis code) for identifying business content in a certain company. The plurality of data includes at least one of at least two data, company identification data (company code) for identifying a company, and customer identification data (client code) for identifying a company's business partner. And more preferably. Conversion pattern setting information 106q shown in FIG. 68 is an example including all six items of subject code, office code, department code, analysis code, company code, and customer code as conversion source data.

  The conversion destination data is, for example, data held in common by certain objects. For example, the objects in the first line, the second line, and the fifth line from the top in FIG. Therefore, it has conversion destination data (common segment code) called “G_Hanbai”. As shown in FIG. 68, only one common segment code (common segment code 1) may be used, or two or more (common segment codes 2, 3,...) May be used.

  As shown in FIG. 68, the conversion pattern setting information 106q may further include extraction order designation data (determination order) and the like. The significance of the extraction order designation data will be described later.

  As shown in FIG. 68, the character string of the reserved word <ALL> meaning all is not limited to this, and may be another character string. In addition, if the conversion source individual company attribute part (customer code, subject code, business office code, department code or analysis code) is set in <ALL>, the same transaction will have multiple conversion destination common attribute parts (common Segment code), it may be uniquely determined by the order of determination. And, by setting the attribute other than the company code to <ALL> to the lowest order, the remaining conversion target data that is not converted in the higher order judgment order can be used for general purposes such as “Other”. Specific codes can be assigned.

  The conversion target data 106r is data including conversion source data to be converted. As shown in FIG. 69, the conversion target data 106r includes conversion source data (subject code, company code, business partner code, establishment code, department code, or analysis code). For the description of the conversion source data included in the conversion target data 106r, the description of the conversion source data of the conversion pattern setting information 106q can be used. As shown in FIG. 69, the conversion target data 106r further includes an occurrence date (occurrence date), a numerical value (amount), and the like of the details (details mean information on one horizontal line in the table of the conversion target data 106r). May be included.

  The conversion completion data 106s is data that has been completely converted from the conversion source data included in the conversion target data 106r into the conversion destination data. As shown in FIG. 73, the conversion completion data 106s includes, for example, conversion source data (subject code, company code, business partner code, establishment code, department code or analysis code), conversion destination data (common segment code), details. The details include the occurrence date (occurrence date) and the numerical value (amount) of the horizontal completion information in the table of the conversion completion data 106s.

  The control unit 102 is a CPU or the like that comprehensively controls the information processing apparatus 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, and necessary data, and performs various information processing based on these stored programs. Run.

  The control unit 102 is functionally conceptually, for example, (1) hierarchical structure identification data for identifying a hierarchical structure formed by forming a hierarchy of a lower layer target and an upper layer target and the lowest layer An acquisition unit 102a as an acquisition unit that acquires the lowest layer identification data associated with the input hierarchical structure identification data with reference to target management data including the lowest layer identification data for identifying the target of the layer; (2) With reference to the target management data, the record acquisition unit 102a1 as a record acquisition unit for acquiring a record including the input hierarchical structure identification data, and (3) from the record acquired by the record acquisition unit, The lowest layer record acquisition unit 102a2 as the lowest layer record acquisition unit for acquiring the lowest layer record, and (4) acquired by the lowest layer record acquisition unit A record including the same hierarchy identification data and target identification data as the upper hierarchy identification data and upper target identification data included in the lower layer record is acquired with reference to the target management data, and the lowermost layer is included in the acquired record. A record creation unit 102a3 as a record creation unit for creating a record to which the lowest layer identification data included in the lowest layer record acquired by the record acquisition unit is added; and (5) the lowest record acquired by the lowest layer record acquisition unit. Referring to the lower layer record and the record created by the record creating means, by obtaining the record including the input hierarchy identification data, the lowest layer data acquisition for obtaining the lowest layer identification data included in the record The lowest layer data acquisition unit 102a4 as means, and (6) lowest layer identification data and number And an extraction unit 102b serving as an extraction unit that extracts a numerical value associated with the lowest layer identification data acquired by the acquisition unit, and (7) totaling the numerical values extracted by the extraction unit And (8) hierarchical structure identification data for identifying a hierarchical structure formed by forming a hierarchy between the object of the lowest layer and the object of the upper layer, and each of the hierarchy structures Referring to object management data including hierarchy identification data for identifying a hierarchy and object identification data for identifying the object, obtain hierarchy identification data and object identification data associated with the input hierarchical structure identification data The first acquisition unit 102d as the first acquisition means for performing the input and the user management data including (9) user group identification data and user identification data A group identification data acquisition unit 102d1 as group identification data acquisition means for acquiring user group identification data associated with the user identification data, (10) hierarchical structure identification data, hierarchy identification data, target identification data, and user group identification data The hierarchical management data including the hierarchical management data including the input hierarchical structure identification data and the hierarchical identification data associated with the user group identification data acquired by the group identification data acquisition means and the target identification data is acquired. A hierarchy identification data acquisition unit 102d2 as means, and (11) the hierarchical management identification data and target identification data acquired by the input hierarchical structure identification data and the hierarchy identification data acquisition means with reference to the target management data As a record acquisition means to acquire records containing The record acquisition unit 102d3, and (12) a record including the same upper hierarchy identification data and upper target identification data as the hierarchy identification data and target identification data included in the record acquired by the record acquisition means, with reference to the target management data And acquiring a record including the same upper hierarchy identification data and upper target identification data as the hierarchical identification data and target identification data included in the acquired record with reference to the target management data, A repetition unit 102d4 as a repetition unit that repeats until acquiring the lowest layer record until the hierarchical identification data and the target identification data included in the lowest layer record are acquired; and (13) hierarchical structure identification data and hierarchy Identification data, object identification data, and lowest layer for identifying the object of the lowest layer A second acquisition unit that obtains the input hierarchical structure identification data, the hierarchical identification data acquired by the first acquisition unit, and the lowest layer identification data associated with the target identification data with reference to target expansion data including different data; A second acquisition unit 102e as an acquisition unit; and (14) referring to the target management data, acquires a record including the input hierarchical structure identification data, and acquires the lowest layer record from the acquired record Then, by using the acquired lowest layer record as the target expansion data, the expansion data creation unit 102f as expansion data generation means for generating the target expansion data, and (15) acquired by the second acquisition means The same hierarchy identification data as the upper hierarchy identification data and upper target identification data included in the lowermost layer record including the lowest hierarchy identification data, and As a record creation means for obtaining a record including target identification data by referring to the target management data, and creating a record obtained by adding the lowest layer identification data obtained by the second obtaining means to the obtained record The record creating unit 102g, (16) including the lowest layer record including the lowest layer identification data acquired by the second acquisition unit and the record generated by the record generation unit, including the input hierarchy identification data By acquiring the record, the lowest layer data acquisition unit 102h as the lowest layer data acquisition means for acquiring the lowest layer identification data included in the record, and (17) including the lowest layer identification data and a numerical value Extraction means for extracting the numerical value associated with the lowest layer identification data acquired by the lowest layer data acquisition means with reference to the data to be aggregated The extraction unit 102i, (18) the totaling unit 102j as a totaling unit for totaling the numerical values extracted by the extraction unit, and (19) the target of the lowest layer and the target of the upper layer form a hierarchy Hierarchical structure identification data for identifying the hierarchical structure to be formed, hierarchical identification data for identifying each hierarchy in the hierarchical structure, object identification data for identifying the object, and objects of the lowest layer are identified Referring to the target extraction data including the lowest layer identification data for the purpose, the lowest level layer identification data that is the lowest level identification data for identifying the main subject that is the subject of the transaction and the other party that is the counterpart of the transaction Hierarchical structure identification data and hierarchical identification associated with the subject lowest layer identification data included in the aggregation target data including the partner lowest layer identification data which is the lowest layer identification data for identifying the target A subject acquisition unit 102k as subject acquisition means for acquiring data and target identification data, and (20) a hierarchical structure associated with the partner lowest layer identification data included in the tabulation target data with reference to the target extraction data Partner acquisition unit 102l as partner acquisition means for acquiring identification data, hierarchy identification data, and object identification data; (21) hierarchical structure identification data, hierarchy identification data, object identification data, and partner acquisition acquired by the subject acquisition means; Determination means for determining that the transaction between the subject and the other party is an internal transaction within the group when the hierarchical structure identification data, the hierarchy identification data, and the target identification data acquired by the means are the same And (22) the subject lowest layer identification data included in the aggregation target data when the same as the determination unit 102m as A totaling unit 102n as a totaling means for totaling the numerical values to be associated, (23) subject lowermost layer identification data, subject identification data for identifying the subject of the transaction, and the subject of the subject Referring to the data to be aggregated including the business partner identification data, the entity main data included in the transaction pattern setting data including the subject lowest layer identification data, the item identification data, the business partner identification data, and the partner lowest layer identification data. The same subject lowest layer identification data, subject identification data, and customer identification data as the lower layer identification data, subject identification data, and customer identification data are extracted, and the subject lowest layer identification data, subject identification data, and customer are extracted. By adding the partner lowest layer identification data included in the transaction pattern setting data associated with the identification data to the aggregation target source data, (24) Referring to the target management data, a record including the input hierarchical structure identification data is acquired, and the acquired record The lowermost layer record is acquired from the above, and the record including the same hierarchy identification data and target identification data as the upper layer identification data and upper target identification data included in the acquired lowermost layer record is referred to the target management data A record obtained by adding the lowest layer identification data included in the acquired lowest layer record to the acquired record, and refer to the acquired lowest layer record and the created record. , Acquiring a record including the input hierarchy identification data, and using the acquired record as the target extraction data With reference to the target extraction creation unit 102p as target extraction creation means for creating the target extraction data, and (25) conversion target data including conversion source data composed of a plurality of data, the conversion source data and the conversion destination An extraction unit 102q serving as an extraction unit that extracts the same conversion source data as the conversion source data included in the conversion pattern setting data including the data, and (26) converting the conversion source data extracted by the extraction unit into the conversion source data A conversion unit 102r as conversion means for converting into conversion destination data included in the conversion pattern setting data associated with the conversion pattern setting data. The details of the processing executed by each unit are described in [3. Specific Example of Processing] will be described.

[3. Specific example of processing]
Hereinafter, a specific example of processing according to the present embodiment will be described. Note that the processing according to the present embodiment is roughly divided into five processes, that is, data aggregation processing, data reference authority management processing, internal transaction determination processing, data conversion processing, and other processing. Describe the items.

[3-1. Data aggregation process]
First, the data tabulation process will be described in detail mainly with reference to FIGS. The data aggregation process is roughly divided into three processes, ie, an acquisition process, an extraction process, and an aggregation process, and will be described below in this order.

(1) Acquisition Process The acquisition unit 102a refers to the hierarchical object management information 106a including the management number and the association code, and acquires the association code associated with the input management number. Specific processing is as shown in the following (1-1) to (1-4).

(1-1) Record Acquisition Processing The record acquisition unit 102a1 refers to the hierarchical object management information 106a and acquires a record including the input management number. That is, the hierarchical object management information 106a is queried based on the input management number.

  Specifically, as shown in FIG. 8, it is assumed that the organization chart (3) is input as a record acquisition condition. In this case, the record acquisition unit 102a1 acquires only the record including the organization chart (3) as shown in FIG. 9 from the hierarchical object management information 106a including records having various management numbers. In FIG. 9, the portion surrounded by a thick frame is data specified based on the input organization chart (3).

  Subsequently, as shown in the following (1-2) to (1-4), for the records extracted from the hierarchical object management information 106a, the hierarchical objects are arranged in descending order of the hierarchical level (the hierarchy is deep). Development information 106b is created.

(1-2) Lowest Layer Record Acquisition Processing The lowest layer record acquisition unit 102a2 acquires the lowest layer record from the records acquired by the record acquisition unit 102a1.

  Specifically, as shown in FIG. 10, the lowest layer record acquisition unit 102a2 selects four records including the hierarchy level 2 (that is, the lowest layer record) from the records acquired by the record acquisition unit 102a1. It is acquired and stored in the hierarchical object development information 106b.

  Thus far, as shown in FIG. 10, the creation of the hierarchized object expansion information 106b including the record having the hierarchy level 2 is completed.

(1-3) Record Creation Processing The record creation unit 102a3 includes a record including the same hierarchy level and node identification code as the upper hierarchy level and upper node identification code included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2. Is acquired with reference to the hierarchized object management information 106a, and a record is created by adding the association code included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 to the acquired record.

  That is, for the hierarchy above the end layer (the lowest layer), the hierarchical object management information 106a and the hierarchical object development information 106b of the higher hierarchy from the hierarchical object development information 106b created in (1-2). Create

  Specifically, two records including the upper hierarchy level 1 and the upper node identification code 11000 among the four lowest layer records acquired by the lowest layer record acquisition unit 102a2 will be described. A record including the same hierarchy level and node identification code as the upper hierarchy level 1 and the upper node identification code 11000 is a record on the second line from the top in the hierarchical object management information 106a in FIG. 11 (indicated by a thick frame). Therefore, the record creation unit 102a3 first acquires this record. Next, the record creation unit 102a3 adds the association code (1, 001, ALL) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 to the acquired record and the acquired record. A record to which the association code (1, ALL, A) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 is added is created. The two created records are stored in the hierarchical object development information 106b.

  Among the four lowest layer records acquired by the lowest layer record acquisition unit 102a2, two records including the upper layer level 1 and the upper node identification code 12000 are processed in the same manner as in the previous paragraph, thereby performing FIG. Records obtained by acquiring the fifth line record (indicated by a thick frame) from the top in the hierarchical object management information 106a and adding the association code (2, 001, ALL) to the acquired record and the acquired record A record in which the association code (3, ALL, ALL) is added to is created. The two created records are stored in the hierarchical object development information 106b.

  The four records created in the preceding paragraph and the previous paragraph and stored in the hierarchical object development information 106b in this way are indicated by MA1 in FIG. As indicated by MA1 in FIG. 11, the expansion information at the hierarchical level 1 is in a state where all the association information at the hierarchical level 2 included in the lower level (terminal) is expanded.

  Thus far, as shown in FIG. 11, the creation of the hierarchized object expansion information 106b including the record having the hierarchy level 2 and the record having the hierarchy level 1 has been completed.

  Here, when the layered object management information 106a includes only the hierarchy levels 0 and 1 (that is, when the hierarchy is two layers), the processing performed by the record creation unit 102a3 ends here. As described above, when the hierarchy level is 2 or higher (that is, when the hierarchy is 3 or higher), the record creation unit 102a3 continues the following processing.

  That is, the record creation unit 102a3 refers to the hierarchical object management information 106a for a record including the same hierarchy level and node identification code as the upper hierarchy level and the upper node identification code included in the record created by the record creation unit 102a3. The record having the information on the target of the highest layer is created by adding the pegging code included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 to the acquired record. The process is repeated until the association code included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 is added.

  Specifically, the record including the same hierarchy level and node identification code as the upper hierarchy level 0 and the upper node identification code 10000 in the four records (indicated by MA1 in FIG. 11) created by the record creation unit 102a3 is the hierarchy of FIG. The record in the first line from the top in the generalized object management information 106a (indicated by a thick frame). For this reason, the record creation unit 102a3 first acquires this record. Next, the record creation unit 102a3 adds the association code (1, 001, ALL) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 to the acquired record, and the acquired record Record obtained by adding the association code (1, ALL, A) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2, and the lowest layer record acquired by the lowest layer record acquisition unit 102a2 to the acquired record Add the association code (3, ALL, ALL) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 to the record added with the association code (2, 001, ALL) included in Create a record. Then, the four created records are stored in the hierarchical object expansion information 106b.

  In this way, the four records created in the previous paragraph and stored in the hierarchical object development information 106b are indicated by MA2 in FIG. As shown in FIG. 12, the hierarchical level 1 expansion information is in a state where all the association information of the hierarchical level 2 included in the lower level (terminal) is expanded, and the hierarchical level 0 expansion information includes the lower level (terminal). All the association information of the hierarchy levels 1 and 2 included in is expanded.

  Thus far, as shown in FIG. 11, the creation of the hierarchized object expansion information 106b including the record having the hierarchy level 2, the record having the hierarchy level 1, and the record having the hierarchy level 0 is completed. The information 106b is completed.

  Although not shown in this example, the record creation unit 102a3 has information on the target of the highest layer in the process described in this item (1-3) when there is a higher layer. The process may be repeated until the associated data included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 is added to the record (that is, the record at hierarchy level 0).

(1-4) Lowest Layer Data Acquisition Processing The lowest layer data acquisition unit 102a4 is input with reference to the lowest layer record acquired by the lowest layer record acquisition unit 102a2 and the record created by the record creation unit 102a3. By acquiring a record including the hierarchical level, the association code included in the record is acquired.

  Specifically, as shown in FIG. 8, it is assumed that the hierarchy level 1 is input as a record acquisition condition. In this case, the lowest layer data acquisition unit 102a4 refers to the hierarchical object development information 106b shown in FIG. 13 and acquires the record including the hierarchical level 1, that is, four records indicated by MA3 in FIG. , Four sets of association codes (1, 001, ALL), (1, ALL, A), (2, 001, ALL) and (3, ALL, ALL) included in the record are acquired. As shown in FIG. 13, the lowest layer data acquisition unit 102a4 may store the acquired four records in the hierarchical object extraction information 106c. As shown in FIG. 8, a node identification code may be input as a condition for acquiring a record (whether or not the range of the node identification code is specified), but if it is not input, all node identification codes are It is an acquisition target of the lowest layer data acquisition unit 102a4.

  As described above, the acquisition unit 102a uses the four association codes (1, 001, ALL) shown in the hierarchical object extraction information 106c in FIG. 13 as the association codes associated with the input organization chart (3). (1, ALL, A), (2, 001, ALL) and (3, ALL, ALL) can be obtained.

(2) Extraction Processing The extraction unit 102b refers to the aggregation target data 106d including the association code and the aggregation target value, and extracts the aggregation target value associated with the association code acquired by the acquisition unit 102a.

That is, the extraction unit 102b performs a matching search on the aggregation target data 106d based on the association code of the hierarchical object extraction information 106c. As conditions for matching with the aggregation target data 106d, evaluation is performed according to the following procedures 1 to 4.
1. Regarding the determination of the linking code 1, if the linking code 1 is an essential item, the matching code 1 in the aggregation target data 106d = matching code 1 in the hierarchical object extraction information 106c is searched, and the linking code 1 is an optional item. In this case, the matching code 1 of the hierarchized object extraction information 106c = reserved word <ALL> or the matching that the association code 1 of the aggregation target data 106d = the association code 1 of the hierarchical object extraction information 106c is searched.
2. Regarding the determination of the linking code 2, if the linking code 2 is an essential item, the matching code 2 of the aggregation target data 106d = matching code 2 of the hierarchical object extraction information 106c is searched, and the linking code 2 is an optional item. In this case, the matching code 2 of the hierarchized object extraction information 106c = reserved word <ALL> or the matching that the association code 2 of the aggregation target data 106d = the association code 2 of the hierarchical object extraction information 106c is searched.
3. Regarding the determination of the linking code 3, if the linking code 3 is an essential item, the matching code 3 of the aggregation target data 106d = matching code 3 of the hierarchical object extraction information 106c is searched, and the linking code 3 is an optional item. In this case, the matching code 3 of the hierarchized object extraction information 106c = reserved word <ALL> or the matching of the association code 3 of the aggregation target data 106d = the association code 3 of the hierarchized object extraction information 106c is searched.
4). Then, evaluation is executed for the number of tied codes used by the system (that is, when the tied code 4 and the subsequent codes exist, processing similar to the tied codes 1 to 3 is executed).

  Specifically, as shown in the aggregation target data 106d in FIG. 14, the details including the association code (1, 001, ALL) of the condition (1) are details with the detail ID = 1 (aggregation target value = 1,000). ). Similarly, the details including the associating code (1, ALL, A) of the condition (2) are the details of the details ID = 1 (counting target value = 1,000) and the details of the detail ID = 4 (counting target value = 4). , 000). <ALL> means that any information may be entered. Similarly, the details including the associating code (2, 001, ALL) of the condition (3) are the details of the details ID = 2 (aggregation target value = 2,000). Similarly, the details including the associating code (3, ALL, ALL) in the condition (4) include details with detail ID = 3 (aggregation target value = 3,000), details with detail ID = 6 (aggregation target value = 6) , 000), details with detail ID = 9 (aggregation target value = 9,000) and details with detail ID = 12 (aggregation target value = 12,000). In this way, the extraction unit 102b has a total of eight aggregation target values (1,000, 1,000, 4,000, 2,000, 3,000, 6,000, 9,000, and 12,000). Can be extracted.

  Here, when the search target to be searched matches a plurality of pegging conditions, it is necessary to consider that the same row (same details) is counted (double count) (detail ID = 1). The details apply). The detail ID is key information that can uniquely identify the row (detail) of the aggregation target data 106d, and can be either a single item or a combination of complex items. In this example, an example of a single item is used. It is described.

(3) Aggregation processing The aggregation unit 102c aggregates the aggregation target values extracted by the extraction unit 102b.

  Specifically, the totaling unit 102c simply sums the eight target values extracted by the extraction unit 102b, and totals 1,000 + 1,000 + 4,000 + 2,000 + 3,000 + 6,000 + 9,000 + 12,000 = 38,000. However, it is preferable to perform aggregation in units of hierarchies and aggregation without double counting as follows.

  Here, the contents of the aggregation key information data 106f necessary when performing aggregation in a hierarchy unit and aggregation without the double count will be described. As shown in FIG. 16, the aggregation key information data 106f includes, for example, the aggregation target value extracted by the extraction unit 102b and the management number, hierarchy level, and node included in the four records acquired by the lowest layer data acquisition unit 102a4. A plurality of items including combinations of identification codes and item IDs are included.

(3-1) Aggregation by Hierarchy First, aggregation by hierarchy will be described. As shown on the left side of FIG. 16, the aggregation unit 102c includes a combination of the aggregation target value extracted by the extraction unit 102b, the management number, the hierarchy level, and the node identification code included in the four records acquired by the acquisition unit 102a4. Referring to the total key information data 106f including a plurality of details including, the specification having the same combination is specified, and the numerical values included in the specified specification are totaled.

  Specifically, as shown on the left side of FIG. 16, the details in the first to third lines from the top of the total key information data 106f are all combinations of organization chart (3), hierarchy level 1 and node identification code 11000. Including. For this reason, the counting unit 102c identifies the details of the first to third rows as the details of the same combination, and sets the numerical values included in the identified details of the first to third rows to 1,000 + 1,000 + 4. , 000 = 6,000. On the other hand, as shown on the left side of FIG. 16, the details of the 4th to 8th lines from the top of the total key information data 106f all include a combination of organization chart (3), hierarchy level 1 and node identification code 12000. For this reason, the totaling part 102c totalizes the numerical value contained in the detail of the said 4th-8th line with 2,000 + 3,000 + 6,000 + 9,000 + 12,000 = 32,000. The total result is shown in the total result data 106e in FIG.

  As described above, in this embodiment, the aggregation target values are aggregated in a hierarchy unit of hierarchy level 1. That is, the totaling result for “company 1: Tokyo head office and company 1: Kanto sales department” belonging to the hierarchical object management information 106a in FIG. 9 is 6,000, and “company 2: affiliated with Kansai area: Aggregation that the aggregation result for “Osaka Branch and Company 3” was 32,000 was performed (aggregation by region). However, when the hierarchy level 0 or the hierarchy level 2 is input by the user, the following aggregation can be performed. That is, when the hierarchical level 0 is input, the total result for “company” shown in the hierarchical object management information 106a in FIG. 9 is 38,000 (the company-wide unit) by the same method as described above. Aggregation). When the hierarchy level 2 is input, the total result of “Company 1: Tokyo head office” shown in the hierarchical object management information 106a in FIG. 9 becomes 1,000 by the same method as described above. , The total result for “Company 1: Kanto Sales Department” is 1,000 + 4,000 = 5,000, the total result for “Company 2: Osaka Branch” is 2,000, and the total result for “Company 3” Is 3,000 + 6,000 + 9,000 + 12,000 = 30,000 (aggregation in terminal units). As described above, according to the information processing apparatus 100 according to the present embodiment, it is possible to perform aggregation in different hierarchical units (company-wide unit, regional unit, or terminal unit) depending on the hierarchy input by the user.

  Here, in the counting method described in this item, the details (both with the specification ID = 1) in the first and second rows from the top of the counting key information data 106f shown on the left side of FIG. It is counted). There is no need to remove such double counts when the aggregation target does not correspond to multiple pegging settings on the pegging setting pattern, or when the aggregation target is on multiple pegging settings on the pegging setting pattern. This may be the case when it is determined that there is no problem even if double counting is performed, or that it is necessary to double cant.

  However, there is a case where it may be determined that the counting target may correspond to a plurality of pegging settings on the pegging setting pattern and should not be double counted. In this case, the unique key information (detail ID) of the detail that matches the pegging setting is specified, and the aggregation is performed after the duplicate rows are removed. That is, as shown in (3-2) below, the double count is performed. It is preferable to perform the tabulated data.

(3-2) Tabulation with Double Count Removed Next, tabulation with double count removed will be described. The aggregation unit 102c, when there is a specification with the same item ID in the aggregation key data 106f including a plurality of items including the aggregation target value extracted by the extraction unit 102b and the item ID, only one item is included in the item The total key data 106f is updated by deleting other details while leaving the numerical value included in the details included in the updated total key data 106f.

  Specifically, as shown on the left side of FIG. 16, since the detail IDs included in the details of the first and second lines from the top of the total key information data 106f are both 1, the totaling unit 102c Is deleted (the specification of the first row may be deleted instead of the specification of the second row), and the aggregate key data 106f is updated. The updated total key data 106f is shown on the right side of FIG. Then, the totaling unit 102c totals the numerical values included in the details (seven details shown on the right side of FIG. 16) included in the updated total key data 106f, thereby obtaining 1,000 + 4,000 + 2,000 + 3,000 + 6,000 + 9. , 1,000 + 12,000 = 37,000.

  The tabulation unit 102c may perform tabulation in units of hierarchies described in (3-1) together with the removal of the double count, and the tabulation result in this case is shown in tabulation result data 106e in FIG. .

  As described above, according to the information processing apparatus 100 according to the present embodiment, even when the objects have a hierarchical structure, the numerical values for the objects can be efficiently aggregated.

  Further, according to the information processing apparatus 100 according to the present embodiment, the contents of the tied code and the number of items can be freely set, so that flexible tabulation can be performed. In the present embodiment, the aggregation based on the three tied codes has been described, but other aggregations such as aggregation considering only the company code, aggregation considering the company code and department code, and only the segment code are included. Aggregation in consideration can also be performed.

[3-2. (Data reference authority management)
Next, the data reference authority management process will be described in detail mainly with reference to FIGS. Since the data reference authority management process is roughly divided into two processes, a first acquisition process and a second acquisition process, items will be described below in this order. In this item [3-2], User B can refer only to the information of the company 100 and the company 200 belonging to the construction business group in the hierarchical structure shown in FIG. 25 (that is, the company 300 and the company 400 belonging to the manufacturing business group). The data reference authority management that can not be referred to) will be explained.

  Note that the processing performed in this item is the pre-processing (1-2) in [3-1].

  Further, as described above, when the authority setting of the hierarchical object is “not used”, the processing in this item is not performed. That is, the security narrowing is not performed on the extracted hierarchical object expansion information 106b described in (1-2) of [3-1].

(1) First Acquisition Process The first acquisition unit 102d refers to the hierarchical object management information 106a including the management number, the hierarchical level, and the node identification code, and the hierarchical level and node identification associated with the input management number Get the code. Specific processing is as shown in the following (1-1) to (1-4).

(1-1) Group identification data acquisition process The group identification data acquisition unit 102d1 refers to the user group affiliation information 106g including a user group code and a user ID, and acquires a user group code associated with the input user ID. To do. That is, the user group affiliation information 106g is inquired based on the input user ID.

  Specifically, as shown in FIG. 31, it is assumed that UserB is input as the user ID. In this case, the group identification data acquisition unit 102d1 acquires Company1 and KoujiGroup as user group codes associated with UserB as indicated by MA11 and MA12 in FIG.

(1-2) Hierarchy Identification Data Acquisition Process The hierarchy identification data acquisition unit 102d2 refers to the authority setting information 106h including the management number, the hierarchy level, the node identification code, and the user group code, and is input the management number The hierarchical level and the node identification code associated with the user group code acquired by the group identification data acquisition unit 102d1 are acquired. That is, the authority setting information 106h is inquired based on the input management number and the user group code extracted in (1-1).

  Specifically, as shown in FIG. 31, it is assumed that the organization chart (2) is input as the management number. The user group codes acquired by the group identification data acquisition unit 102d1 are Company1 and KoujiGroup as described above. In this case, the hierarchy identification data etc. acquiring unit 102d2 acquires 1 and 21000 as the hierarchy level and node identification code associated with the organization chart (2) and KoujiGroup, as indicated by MA13 in FIG.

  The hierarchy identification data etc. acquiring unit 102d2 extracts the authority including the acquired hierarchy level 1, the acquired node identification code 21000, the input organization chart (2), and the group code KoujiGroup acquired by the group identification data acquiring unit 102d1. The information 106i may be created as shown in FIG. Note that if one user belongs to a plurality of user groups and has authority, the authority extraction information 106i may have a plurality of lines.

(1-3) Record Acquisition Processing The record acquisition unit 102d3 refers to the hierarchical object management information 106a including the management number, the hierarchy level, and the node identification code, and acquires the input management number and hierarchy identification data etc. acquisition unit 102d2. Acquires the record that includes the hierarchy level and node identification code acquired in step 1. That is, the record acquisition unit 102d3 inquires the hierarchical object management information 106a based on the management number, the hierarchical level, and the node identification code of the authority extraction information 106i.

  Specifically, the input management number is the organization chart (2) as described above. The hierarchy levels and node identification codes acquired by the hierarchy identification data etc. acquiring unit 102d2 are 1 and 21000 as described above. In this case, the record acquisition unit 102d3 acquires a record including information surrounded by a thick frame in FIG. 34 as a record including the organization chart (2) and 1 and 21000.

(1-4) Repetition Processing The repetition unit 102d4 performs hierarchical object management on a record including the same upper hierarchy level and higher node identification code as the hierarchy level and node identification code included in the record acquired by the record acquisition unit 102d3. The information 106a is acquired with reference to the information, and a record including the same upper hierarchy level and higher node identification code as the hierarchical level and node identification code included in the acquired record is acquired with reference to the hierarchical object management information 106a. This is repeated until the hierarchical level and the node identification code included in the lowest layer record are obtained by obtaining the lowest layer record. That is, the repetition unit 102d4 acquires a lower node list having its own node as an upper hierarchy level and an upper node identification code when the subordinate structure classification of the corresponding node is <with substructure>, and restarts this process. Call. Then, if the subordinate structure classification of the corresponding node is <no substructure>, its own node is held as hierarchical object security deployment information 106j.

  Specifically, the hierarchy level and the node identification code included in the record acquired by the record acquisition unit 102d3 are 1 and 21000, respectively, as described above. In this case, the repetition unit 102d4 acquires two rows of records including information surrounded by a thick frame in FIG. 35 as records including the same upper hierarchy level and upper node identification code as 1 and 21000. Further, the repetition unit 102d4 may repeat the same processing to acquire a lower layer record. In this example, the acquired two-row record includes the lowest hierarchical level 2. Since this is the lowest layer record, the process is terminated here.

  The iterative unit 102d4 creates hierarchical object security deployment information 106j including the input organization chart (2), the acquired hierarchy level 2, and the acquired node identification codes 21100 and 21200 as shown in FIG. May be. In the hierarchized object security deployment information 106j, there is a possibility that the lines detected when the authority is set for both the upper and lower levels may be duplicated. In this case, the duplicated lines are removed. .

  As described above, the first acquisition unit 102d can acquire “hierarchy level 2 and node identification code 21100” and “hierarchy level 2 and node identification code 21200” as shown in FIG.

(2) Second acquisition process The second acquisition unit 102e refers to the hierarchical object expansion information 106b including the management number, the hierarchy level, the node identification code, and the association code, and inputs the management number and the first acquisition unit. The linking code associated with the hierarchy level and node identification code acquired in 102d is acquired. That is, the second acquisition unit 102e narrows down the information having the hierarchical level of the hierarchical object expansion information 106b by using the hierarchical object security expansion information 106j, and sets only the referenceable data as expansion data.

  Specifically, the input management number is the organization chart (2) as described above. Further, the hierarchy levels and node identification codes acquired by the first acquisition unit 102d are “2 and 21100” and “2 and 21200” as described above. In this case, the second acquisition unit 102e acquires (100, ALL, ALL) in the hierarchical object expansion information 106b in FIG. 37 as the association code associated with the organization chart (2), 2 and 21100. Further, the second acquisition unit 102e acquires (200, ALL, ALL) in the hierarchical object expansion information 106b of FIG. 37 as the association code associated with the organization chart (2), 2 and 21200. In this way, only the data matching the hierarchical object security development information 106j is narrowed down from the original hierarchical object development information 106b.

  The hierarchical object expansion information 106b referred to by the second acquisition unit 102e is not the hierarchical object expansion information 106b including the records of the hierarchy levels 2 to 0, but the hierarchical object expansion information 106b including only the records of the hierarchy level 2. It is. The hierarchized object development information 106b including only the record of the hierarchy level 2 can be created by the development data creation unit 102f. The specific creation method is the record acquisition unit 102a1 and the lowest layer record of [3-1]. Since it is the same as the process which the acquisition part 102a2 performs, description is abbreviate | omitted.

  As described above, UserB refers only to the association code (100, ALL, ALL) of the company 100 belonging to the construction business group and the association code (200, ALL, ALL) of the company 200 in the hierarchical structure shown in FIG. can do.

  Thus, according to the information processing apparatus 100 according to the present embodiment, the range of target information that can be referred to by the user can be limited.

  Further, according to the information processing apparatus 100 according to the present embodiment, for example, the position of the hierarchy that can be referred to by the user and the number of the hierarchy can be flexibly set.

  For example, in the example of the organization chart (2) in FIG. 25, setting of the position of the hierarchy sets the range that can be referred to by the user to the entire company level (that is, refers to all information of the companies 100 to 400). Can be set to the core company level (can refer to the information of the construction business group or the manufacturing business group), or can be set to the level of the individual company (can refer to the information of any one of the companies 100-400) ).

  For example, in the case of the core company layer in the example of the organization chart (2) in FIG. 25, is it possible to refer only to information on either the construction business group or the manufacturing business group? In other words, either one of the hierarchies that can be referred to) or the information of both the construction business group and the manufacturing business group can be referred to (that is, two hierarchies can be referred to). By being able to refer to both groups, for example, it is possible to efficiently set reference authority for a person (concurrent person) who is in a position to concurrently serve both a construction business and a manufacturing business.

  Subsequently, the record creation unit 102g and the lowest layer data acquisition unit 102h create a hierarchy level 2 based only on the upper two rows of records surrounded by a thick frame in the hierarchical object development information 106b in FIG. Hierarchical object expansion information that has been expanded from 1 to 0 may be created. A specific creation method is the same as the process performed by the record creation unit 102a3 and the lowest layer data acquisition unit 102a4 in [3-1], and thus description thereof is omitted. Note that records in the lower two lines not surrounded by a thick frame in the hierarchical object expansion information 106b in FIG. 37 are not expanded. In other words, the expansion information is created only for the upper two rows of records for which User B has reference authority, while the expansion information is not generated for the lower two rows of records for which User B does not have reference authority.

  Furthermore, the extraction unit 102i may extract numerical values by referring to the aggregation target data based on the hierarchical object expansion information that has been expanded to the end, and the aggregation unit 102j The extracted numerical values may be aggregated. A specific processing method is the same as the processing performed by the extraction unit 102b and the totaling unit 102c in [3-1], and thus description thereof is omitted.

  In this item [3-2], the case where there is one analysis axis (virtual organization) has been described, but multi-axis analysis using a plurality of combinations of hierarchical objects (for example, a combination of a virtual organization and a virtual segment) When it is desired to perform the processing, the processing of this item [3-2] can be performed for each layered object (virtual organization, virtual segment) to narrow down the reference data range.

The points of this item [3-2] are summarized as shown in 1-4 below.
1. By setting the authority for the management number / hierarchy level / node identification code of the hierarchized object, the viewable data range can be flexibly set.
2. Since one user can belong to a plurality of user groups, the setting at the time of concurrent appointment becomes easy.
3. By performing the processing procedure according to the following flows a to c, it is possible to obtain all the upper nodes to be aggregated for the lower nodes having the reference authority.
a. List all end nodes belonging to the hierarchy level and node identification code for which authority is set.
b. The upper hierarchical object expansion data is expanded only from the enumerated hierarchical level and node identification code.
c. Aggregate the matching information that matches the hierarchical object expansion data.
4). Even with multiple analysis axes, it can be easily extended.

[3-3. Internal transaction judgment processing)
Next, the internal transaction determination process will be described in detail mainly with reference to FIGS. In this item [3-3], the following flow will be described. First, a procedure for creating the aggregation target data 106n will be described mainly with reference to FIGS. Next, the internal transaction determination process for the virtual organization will be described mainly using FIGS. 50 to 56. And the internal transaction determination process about a virtual segment is mainly demonstrated using FIGS. Finally, internal transaction determination processing using two axes of a virtual organization and a virtual segment will be described with reference to FIGS. The process performed in this item [3-3] is a process obtained by further subdividing (3-1) of [3-1].

(1) Creation of Aggregation Target Data Aggregation target data 106n is created based on the aggregation target original data 106m in which the counterpart attribute information in the aggregation target data 106n is initialized to be unset.

  The aggregation object creation unit 102o refers to the aggregation object source data 106m, and the entity lowest-layer identification data, the same item as the entity lowest-layer identification data, the item code, and the customer code included in the supplier specific pattern setting information 106l. The code and supplier code are extracted, and the partner lowest layer identification data included in the supplier specific pattern setting information 106l that is associated with the extracted subject lowest layer identification data, subject code and supplier code By adding to the data 106m, the aggregation target data 106n is created.

That is, the aggregation target creation unit 102o extracts the aggregation target data based on the supplier specific item setting information 106k and the supplier specific pattern setting information 106l, and updates the specified partner information. At this time, the processing order is preferably performed in ascending order of determination for each company. In addition, as a condition for matching with the aggregation target original data 106m, evaluation is performed according to the following procedures 1 to 3. In the following description, the company attribute means a supplier code, a subject code, a business office code, a department code, or an analysis code.
1. Regarding the determination of company attribute 1, if company attribute 1 is an indispensable item, a search for company attribute 1 = aggregation of source data 106m, company attribute 1 of supplier specific pattern setting information 106l, and company attribute 1 is optional In the case of an item, the company attribute 1 of the supplier specific pattern setting information 106l = reserved word <ALL> or the company attribute 1 of the aggregation target source data 106m = the company attribute 1 of the supplier specific pattern setting information 106l. Perform a matching search.
2. Regarding the determination of company attribute 2, if company attribute 2 is an indispensable item, the company attribute 2 in the aggregation target source data 106m is searched for a match of company attribute 2 in the supplier specific pattern setting information 106l, and the company attribute 2 is optional. In the case of the item, the company attribute 2 of the supplier specific pattern setting information 106l = reserved word <ALL> or the company attribute 2 of the aggregation target source data 106m = the company attribute 2 of the supplier specific pattern setting information 106l. Perform a matching search.
3. Thereafter, evaluation is performed for the number of company attributes used by the system (that is, when the company attributes 3 and later exist, the same processing as the company attributes 1 and 2 is performed).

  Specifically, when the contents of the supplier specific pattern setting information 106l are as shown in FIG. 44 and the contents of the aggregation target source data 106m are as shown in FIG. Whether to create the aggregation target data 106n will be described.

  First, the aggregation target creation unit 102o starts from the record with the lowest determination order (record on the first line from the top) of the two records including the company code 100 in the supplier specific pattern setting information 106l shown in FIG. In order, the following extraction process and addition process are performed.

(Extraction process)
The extraction process will be described. As shown in FIG. 47, in the record (indicated by an arrow) in the first line from the top of the supplier specific pattern setting information 106l, the entity lowest layer identification data includes the company code 100, the office code Tokyo, the department code Eigyo, and The analysis code is Buppan, the subject code is 1000: sales, and the supplier code is T1001. Here, referring to the aggregation target source data 106m in FIG. 47, a record including this combination (company code 100, business office code Tokyo, department code Eigyo, analysis code Buppan, item code 1000: sales and business partner code T1001) , Two records (indicated by arrows) in the first and second lines from the top. Therefore, the aggregation object creation unit 102o is included in the two records of the aggregation object source data 106m (company code 100, business office code Tokyo, department code Eigyo, analysis code Buppan, item code 1000: sales and business partner code. T1001) is extracted.

(Additional processing)
The additional process will be described. In the supplier specific pattern setting information 106l shown in FIG. 47, the partner most closely associated with the extracted (company code 100, establishment code Tokyo, department code Eigyo, analysis code Buppan, item code 1000: sales and supplier code T1001). The lower layer identification data is a combination of (partner company code 200, partner office code Tokyo, partner department code Seizou1 and partner analysis code Seizou). Therefore, as shown in FIG. 47, the tabulation target creation unit 102o adds the combination to the records (indicated by arrows) on the first and second rows from the top of the tabulation source data 106m.

  Next, as shown in FIG. 48, the aggregation target creating unit 102o has the second youngest determination order (2 from the top) in the two records including the company code 100 in the supplier specific pattern setting information 106l. The extraction process and the addition process are performed in the same manner for the record on the line). Thereby, as shown in FIG. 48, the tabulation target creation unit 102o sets the partner company code 300, the partner office code Osaka, the partner department code Hanbai1, and the partner analysis code Kouri from the top of the tabulation target source data 106m. Add to the record on the line (indicated by an arrow).

  Then, as illustrated in FIG. 49, the aggregation target creating unit 102o has the youngest record (the third row from the top) in the two records including the company code 200 in the supplier specific pattern setting information 106l. In the same manner, the extraction process and the addition process are performed on the record. Thereby, as shown in FIG. 49, the tabulation target creation unit 102o sets (counter company code 100, partner office code Tokyo, partner department code Eigyo and partner analysis code Buppan) from the top of the tabulation target source data 106m. Add to the record on the line (indicated by an arrow).

  Further, the aggregation target creation unit 102o performs the extraction process and the addition process on the fourth to sixth lines from the top of the supplier specific pattern setting information 106l in the same manner, and finally the aggregation target shown in FIG. Data 106n is created.

  In this way, the aggregation object creation unit 102o performs the extraction process and the addition process up to the last line of the supplier specific pattern setting information 106l, so that all the partner codes determined as intra-group transactions are filled. On the other hand, a transaction specified by a line that remains unset is a transaction with an external general company that is not an intra-group transaction.

(2) Internal Transaction Determination Process for Virtual Organization Next, an internal transaction determination process for the virtual organization will be described. In this item, among the hierarchical structure shown in FIG. 42, internal transaction determination processing in the middle hierarchy (that is, the company 100 Tokyo sales and company 200 manufacturing 1 part belonging to the Kanto area are determined as internal transactions, A description will be given of how the process of determining that the company 300 Osaka sales 1 part and the company 200 manufacturing 2 part belonging to the Kansai area are internal transactions) can be realized.

  In this item, it is assumed that the aggregation target data 106n is created in (1).

  Further, in this item, the hierarchical object extraction information 106c is created by the target extraction creation unit 102p based on the hierarchical object management information 106a shown in FIG. 40 and the input pattern (1) shown in FIG. Suppose there is. Since the specific creation method is the same as (1-1) to (1-4) in [3-1], the description is omitted. FIG. 51 shows the hierarchized object extraction information 106c created by the target extraction creation unit 102p.

  Here, the internal transaction determination process is roughly divided into three processes: a subject acquisition process, a partner acquisition process, and a determination process. Further, the aggregation process can be performed based on the result of the determination process. For this reason, hereinafter, these four processes will be described in order in this order.

(2-1) Subject Acquisition Processing The subject acquisition unit 102k refers to the hierarchical object extraction information 106c including the management number, the hierarchy level, the node identification code, and the lowest layer identification data, A management number, a hierarchy level, and a node identification code associated with the subject lowest layer identification data included in the aggregation target data 106n including the partner lowest layer identification data are acquired.

  Specifically, in the specification of the first to fifth lines from the top of the aggregation target data 106n shown in FIG. 52, the subject lowest layer identification data is a combination of (company code 100, establishment code Tokyo, and department code Eigyo). is there. Here, referring to the hierarchized object extraction information 106c shown in FIG. 51, the association (management number, hierarchy level and node identification code) associated with this combination is included in the record with A (organization chart (4), 1, 31000). Therefore, the subject acquisition unit 102k acquires (organization chart (4), 1, 31000) as information associated with the subject lowest layer identification data included in the description of the first to fifth lines from the top of FIG. To do. In the same way, the subject acquisition unit 102k associates with the subject lowest layer identification data (company code 200, business location code Tokyo, and department code Seizou1) included in the details of the sixth to seventh lines from the top of FIG. 51 is acquired (organization chart (4), 1, 31000) included in the record with B in FIG. 51, and the subject lowest layer identification data ( As information associated with the company code 200, the office code Osaka, and the department code Seizou2), the information (organization chart (4), 1, 32000) included in the record with D in FIG. As information associated with the subject lowest layer identification data (company code 300, establishment code Osaka and department code Hanbai1) included in the details of the 10th to 13th lines, Included in the record marked with 1 C (organizational chart (4), 1,32000) acquires. In the records with B and D in FIG. 51, the office code is <ALL>, which means that any information can be entered. Specifically, in this example, In the case, it means Tokyo or Osaka.

  Here, in the “own organization” column of the organization matching result in FIG. 52, the correspondence between each detail in FIG. 52 and each record in FIG. 51 is shown by A to D. Therefore, the aggregation target data 106n may not include the organization matching result.

  In this manner, the subject acquisition unit 102k can perform matching with the own organization information of the aggregation target data 106n based on the hierarchized object extraction information 106c, and obtain a matching result regarding the own organization.

(2-2) Partner Acquisition Process The partner acquisition unit 102l refers to the hierarchical object extraction information 106c including the management number, the hierarchy level, the node identification code, and the lowest layer identification data, A management number, a hierarchy level, and a node identification code associated with the partner lowest layer identification data included in the aggregation target data 106n including the partner lowest layer identification data are acquired.

  Specifically, in the details of the sixth and tenth lines from the top of the aggregation target data 106n shown in FIG. 53, the partner lowest layer identification data is (partner company code 100, partner office code Tokyo and partner department code). Eigyo). Here, referring to the hierarchized object extraction information 106c shown in FIG. 51, the association (management number, hierarchy level and node identification code) associated with this combination is included in the record with A (organization chart (4), 1, 31000). For this reason, the partner acquisition unit 102l uses (Organization chart (4), 1, 31000) as information associated with the partner lowest layer identification data included in the first and sixth lines from the top of FIG. get. In a similar manner, the partner acquisition unit 102l receives the partner lowest layer identification data (partner company code 200, partner office code Tokyo and partner department code Seizou1) included in the details of the first and second lines from the top of FIG. As the information to be associated, the information (organization chart (4), 1, 31000) included in the record with B in FIG. 51 is acquired, and the other party included in the details of the fourth and eighth lines from the top of FIG. As information associated with lower layer identification data (partner company code 300, partner office code Osaka and partner department code Hanbai1), the information (organization chart (4), 1, 32000) included in the record with C in FIG. The partner lowermost layer identification data (partner company code 200, partner office code Osaka, and partner department code acquired in the 12th line from the top of FIG. 53) As a link attached information Eizou2), included in the record marked with D in FIG. 51 (organizational chart (4), 1,32000) acquires.

  Here, in the “partner organization” column of the organization matching result in FIG. 53, the correspondence between each detail in FIG. 53 and each record in FIG. 51 is shown by A to D. This notation is for convenience of explanation. Therefore, the aggregation target data 106n may not include the organization matching result.

  In this way, the partner acquisition unit 102l can perform matching with the partner organization information of the aggregation target data 106n based on the hierarchized object extraction information 106c, and obtain a matching result related to the partner organization.

(2-3) Determination Processing In the determination unit 102m, the management number, hierarchy level, and node identification code acquired by the subject acquisition unit 102k are the same as the management number, hierarchy level, and node identification code acquired by the partner acquisition unit 102l. In this case, it is determined that the transaction between the subject and the other party is an internal transaction within the group.

  Specifically, for example, for the details of the first row from the top of the aggregation target data 106n in FIG. 55, the management number, hierarchy level, and node identification code acquired by the subject acquisition unit 102k are (organization chart (4), 1, 31000). On the other hand, the management number, the hierarchy level, and the node identification code acquired by the partner acquisition unit 102l are also combinations (organization chart (4), 1, 31000). Exactly the same. In this case, the determination unit 102m determines that the transaction in the details of the first row is an internal transaction within the group.

  This content will be described below using the tissue matching result of FIG. That is, the organization matching result in the first row from the top of FIG. 55 is A for the own organization and B for the partner organization. Here, referring to the hierarchized object extraction information 106c in FIG. 54, the record to which A is attached and the record to which B is attached are in an internal transaction relationship as shown by MA14 (that is, management number, hierarchy) The combination of level and node identification code is exactly the same). As described above, since the transaction specified in the first line from the top of FIG. 55 can be determined to be an internal transaction, the “internal / external determination” column of the organization matching result is appended with the characters “internal”. ing.

  In a similar manner, the determination unit 102m determines that the second, sixth, eighth, and twelfth transactions from the top of FIG. 55 are internal transactions, while the third to fifth lines, The transactions on the seventh line, the 9th to 11th lines, and the 13th line are determined as external transactions.

  In this way, the determination unit 102m determines that the combination of the own organization and the partner organization is the internal transaction when the layered object extraction information 106c has the same “hierarchy level” and “node identification code”, and the other is an external transaction. judge. It should be noted that a transaction specified by a line in which the partner organization is not set is determined as an external transaction.

  Thus, according to the information processing apparatus 100 according to the present embodiment, it is possible to automatically determine whether or not the transaction between the objects is an internal transaction within the group. In this example, the internal transaction determination process in the “middle hierarchy” in the virtual organization (that is, in FIG. 42, the transaction between the company 100 Tokyo sales belonging to the Kanto area and the company 200 manufacturing part 1 is an internal transaction). In the same manner, the transaction between the company 300 Osaka sales 1 part and the company 200 manufacture 2 part belonging to the Kansai area is described as an internal transaction). "Hierarchy" or "lower hierarchy" may be used.

  In the case of the internal transaction determination process in the “upper hierarchy”, when the hierarchical object extraction information 106c is created, by inputting the hierarchy level “0”, the management number, hierarchy level, and node identification code are (organization chart (4 ), 0, 30000) can be created. Therefore, the combination of the management number, the hierarchy level, and the node identification code acquired by the subject acquisition unit 102k with reference to the hierarchized object extraction information 106c, and the partner acquisition unit 102l acquires with reference to the hierarchized object extraction information 106c. The combination of the management number, hierarchy level, and node identification code is always the same. For this reason, in the aggregation target data 106n, all details corresponding to the supplier specific pattern setting information 106l (details in the first and second lines from the top of the aggregation target data 106n, details in the fourth line, details in the sixth line) , 8th line details, 10th line details, and 12th line details) are internal transactions. On the other hand, details that do not correspond to the customer specific pattern setting information 106l (details of the third row, details of the fifth row, details of the seventh row, details of the ninth row, details of the ninth row, 11th row) Details and details on the 13th line) are external transactions.

  On the other hand, in the case of the internal transaction determination process in the “lower hierarchy”, when the hierarchical object extraction information 106c is created, by inputting the hierarchy level “2”, the management number, the hierarchy level, and the node identification code are (Organization chart (4), 2, 31100), (Organization chart (4), 2, 3200), (Organization chart (4), 2, 32100) and (Organization chart (4), 2, 32200), respectively. Hierarchical object extraction information 106c composed of four records can be created. Therefore, the combination of the management number, the hierarchy level, and the node identification code acquired by the subject acquisition unit 102k with reference to the hierarchized object extraction information 106c, and the partner acquisition unit 102l acquires with reference to the hierarchized object extraction information 106c. Since the combination of the management number, the hierarchy level, and the node identification code is always different, transactions in all the details of the aggregation target data 106n are external transactions.

  FIG. 65 shows an image diagram of the internal transaction determination process in each of the “upper hierarchy”, “middle hierarchy”, and “lower hierarchy”. As shown in FIG. 65, the amount of internal transactions increases as the internal transaction determination process is performed at a higher level. This is because the internal transaction determination processing in this item (2) is a procedure in which nodes having the same higher level organization at the same level are inside, so the hierarchical level to be extracted is higher (close to 0). This is because when extracted, the data determined as internal transactions will increase. As a result, when the nodes at the hierarchical level to be extracted are virtually regarded as one company / one segment, it is possible to determine a transaction between the inner nodes as an internal transaction and cancel the offset.

  Further, according to the information processing apparatus 100 according to the present embodiment, for example, an internal transaction determination process (that is, security management is performed) that combines the content described in [3-2] and the content described in this item (2). Considering internal transaction determination processing) can be performed. An image diagram of this internal transaction determination process is shown in FIG. As shown in FIG. 66, by incorporating the contents of [3-2], it is possible to distinguish and count internal transactions and external transactions in a company in which the user has reference authority. In-group companies that do not have reference authority for the user (in FIG. 66, the manufacturing business group and company 300 and company 400 belonging thereto) are regarded as the same “external” transaction for the user as other business partners outside the group. It is.

  Then, according to the information processing apparatus 100 according to the present embodiment, for example, the contents and number of items of the subject lowest layer identification data and the partner lowest layer identification data can be arbitrarily set. It can be carried out. Specifically, conventionally, only internal transaction determination processing (for example, processing for determining that a transaction between the company 100 and the company 200 is an internal transaction) can be performed in general units such as a company unit and a segment unit. On the other hand, according to the information processing apparatus 100 according to the present embodiment, if three codes of company code, office code, and department code are set as company information and partner information, internal transactions with fine granularity are set. Determination processing (for example, processing for determining that the transaction of “Company 100, Tokyo head office, sales department” and “Company 200, Osaka head office, manufacturing department 2” is an internal transaction) can be performed.

  Here, in this item (2), the internal transaction determination process can be performed according to the contents described in (2-1) to (2-3), but the counting unit 102n determines the result of the internal transaction determination process. The following (2-4) tabulation processing may be performed using.

(2-4) Aggregation processing The aggregation unit 102n aggregates numerical values associated with the subject lowest layer identification data included in the aggregation target data 106n when they are the same.

  Specifically, the same case means that the combination of the management number, hierarchy level and node identification code acquired by the subject acquisition unit 102k and the combination of the management number, hierarchy level and node identification code acquired by the partner acquisition unit 102l And are the same. In the aggregation target data 106n in FIG. 55, when the inside / outside organization determination is internal and the details of the first row, the second row, the sixth row, the eighth row and the twelfth row from the top are the same as above. Applicable. Referring to FIG. 55, the amounts associated with the subject lowest layer identification data (company code, establishment code, and department code) included in these details are 10,000 yen, 15,000 yen, and 50,000, respectively. Yen, 70,000 yen and 110,000 yen. The totaling unit 102n may total all these amounts and calculate 255,000 yen. However, as described below, the combination of the management number, the hierarchy level, the node identification code, and the subject code is the same. It is preferable to sum up the amount of money every time.

  That is, in FIG. 55, since the details in the first and second lines from the top are the combination of the management number, the hierarchy level, the node identification code, and the subject code (organization chart (4), 1, 31000, sales), The tabulating unit 102n tabulates the amount included in the details of the first and second lines as 10,000 + 15,000 = 25,000 yen. Similarly, in FIG. 55, the details in the sixth line from the top are a combination of the management number, the hierarchy level, the node identification code, and the subject code (organization chart (4), 1, 31000, purchase). The totaling unit 102n totalizes the amount included in the details of the sixth row as 50,000 yen. Similarly, in FIG. 55, the description in the eighth line from the top is a combination of the management number, the hierarchy level, the node identification code, and the subject code (organization chart (4), 1, 32000, purchase). The totaling unit 102n totalizes the amount included in the details of the eighth row as 70,000 yen. Similarly, in FIG. 55, the details in the twelfth line from the top are the combination of the management number, the hierarchy level, the node identification code, and the subject code (organization chart (4), 1, 32000, sales). The part 102n totals the amount of money included in the details of the 12th row as 110,000 yen. As described above, the tabulation unit 102n, as shown in the tabulation result data 106o of FIG. 56, for each item having the same combination of management number, hierarchy level, node identification code, and subject code, 25,000 yen, 50, Internal transaction amounts of 000 yen, 110,000 yen and 70,000 yen can be calculated.

  The tabulation unit 102n may also tabulate amounts for each item having the same combination of the management number, the hierarchy level, the node identification code, and the subject code even for the item whose external / internal determination is external. Thereby, the totaling unit 102n, for each item having the same combination of management number, hierarchical level, node identification code, and subject code, as shown in the totaling result data 106o in FIG. 56, is 20,000 yen, 130,000. External transaction amounts of Yen, 310,000 Yen and 80,000 Yen can be calculated.

  Then, the totaling unit 102n determines whether the internal / external determination is for both the internal details and the external details (that is, for all details regardless of the internal / external determination), the management number, the hierarchy level, the node identification code, and the subject code. Amounts may be aggregated for each item with the same combination. Thereby, the totaling unit 102n can calculate the total total amount of 45,000 yen, 180,000 yen, 420,000 yen and 150,000 yen as shown in the aggregation result data 106o of FIG. The totaling unit 102n may calculate the total amount by adding the internal transaction amount and the external transaction amount.

(3) Internal Transaction Determination Process for Virtual Segment This item is different from the following item only, and the process itself is the same as (2), and detailed description thereof is omitted. First, the lowest layer identification data included in the hierarchized object extraction information 106c is not “company code, business office code, and department code” but “analysis code” as shown in FIG. This is because the hierarchized object extraction information 106c is created based on the hierarchized object management information 106a (including “analysis code”) shown in FIG. 41 and the input pattern (2) shown in FIG. In addition, in the aggregation target data 106o, an item used for matching related to the own organization is not “company code, business office code, and department code” but “analysis code” as shown in FIG. In the aggregation target data 106o, the item used for matching with the partner organization is not “partner company code, partner office code, and partner department code” but “partner analysis code” as shown in FIG. As described above, by using the “analysis code” included in the hierarchical object extraction information 106c, the “analysis code” and the “partner analysis code” included in the aggregation target data 106o, the same processing as in (2) is performed. It is possible to perform internal transaction determination processing and totalization based on this result. The contents of the internal transaction determination process are shown in FIGS. 57 to 61, and the result of the aggregation is shown in FIG.

  By the processing in this item (3), in the hierarchical structure shown in FIG. 42, the sales department of the Tokyo head office of the company 100 that conducts product sales (real segment) belonging to the sales business (virtual segment) hierarchy, and the sales business (virtual business) It is possible to determine that the transaction between the first branch of the Osaka branch of the company 300 that performs the retail (actual segment) belonging to the (segment) hierarchy is an internal transaction within the group.

(4) Internal transaction determination processing using two axes of virtual organization and virtual segment The internal transaction determination processing using two axes is combined with the organization matching result of (2) and the segment matching result of (3) as follows: Can be done as follows.

  FIG. 63 shows both the tissue matching result (2) and the segment matching result (3). Referring to FIG. 63, three types of aggregation results of “total total amount”, “internal transaction amount (within segment)”, and “internal transaction amount (outside segment)” are obtained in consideration of internal / external determination and internal / external determination. be able to. The “total total amount” is a simple total amount that does not depend on internal / external determination and segment determination. “Internal transaction amount (within segment)” is the total amount of “inside” for internal / external determination and “internal” for internal / external determination. “Internal transaction amount (outside segment)” is a total amount of “inside” and “outside” inside / outside judgment of the organization.

  In the table of FIG. 63, when calculating the “total amount”, the amounts are totaled for all the details. Here, the “total total” process is performed for each item having the same combination of the management number of the virtual organization, the hierarchy level and the node identification code and the management number of the virtual segment, and the combination of the hierarchy level and the node identification code and the subject code. May be. That is, the following aggregation may be performed for all the details in the table in FIG. In FIG. 64, the total total amount of 45,000 yen is the total value of the amounts included in the details of the first to third lines from the top of FIG. 63, and the total total amount of 70,000 yen is 4 from the top of FIG. The total value of the amount included in the details of the 5th line and the total total amount of 110,000 yen is the total value of the amount included in the details of the 6th to 7th lines from the top of FIG. 420,000 yen is the total value of the amounts included in the details of the 10th to 13th lines from the top of FIG. 63, and the total total amount of 150,000 yen is the details of the 8th to 9th lines from the top of FIG. The total value of the included amount.

  In the table of FIG. 63, when calculating “internal transaction amount (within segment)”, there is no item with an internal / external determination of “internal” and an internal / external determination of “internal”, so there is an aggregated amount. do not do.

  In the table of FIG. 63, when calculating the “internal transaction amount (outside segment)”, the internal / external determination is “internal” and the internal / external determination is “external”. The amount of money is totaled for the details of the 8th and 12th lines. Here, in the process of “internal transaction (outside segment)”, the combination of the management number of the virtual organization, the hierarchy level and the node identification code, the management number of the virtual segment, the hierarchy level, the node identification code and the subject code is the same. It may be performed for each specification. That is, for the details of the first, second, sixth, eighth and twelfth lines from the top of the table of FIG. 63, the following aggregation may be performed. In FIG. 64, the internal transaction amount (outside the segment) 25,000 yen is the total value of the amounts included in the details of the first and second lines from the top of FIG. 63, and the internal transaction amount (outside the segment) 50,000 yen Is the aggregate value of the amount included in the details of the sixth line from the top of FIG. 63, and the internal transaction amount (outside the segment) 110,000 yen is the amount of money included in the details of the twelfth line from the top of FIG. The total value and the internal transaction amount (outside the segment) 70,000 yen is the total value of the amount included in the details of the eighth line from the top in FIG.

  In addition, in the total result data 106o of FIG. 64, regarding “external transaction amount”, “total amount” = “external transaction amount” + “internal transaction amount (within segment)” + “internal transaction amount (outside segment)” The description is omitted because it can be calculated by the following formula.

[3-4. Data conversion process]
Next, the data conversion process will be described in detail mainly with reference to FIGS. In this item [3-4], the conversion completion data 106s (shown in FIG. 73), which is the data after the completion of the data conversion process, is the conversion target in which the conversion destination attribute information in the conversion completion data 106s is set unset. Based on the data 106r (shown in FIG. 69), it is created by the following procedure.

  The extraction unit 102q refers to the conversion target data 106r including the conversion source data, extracts the same conversion source data as the conversion source data included in the conversion pattern setting information 106q including the conversion source data and the conversion destination data, The conversion unit 102r converts the conversion source data extracted by the extraction unit 102q into conversion destination data included in the conversion pattern setting information 106q associated with the conversion source data.

That is, the extraction unit 102q extracts conversion target data based on the conversion item setting information 106p and the conversion pattern setting information 106q, and the conversion unit 102r updates the specified conversion destination attribute information. At this time, the processing order is preferably performed in ascending order of determination order of company. In addition, as a condition for matching with the conversion target data 106r, evaluation is performed according to the following procedures 1 to 3. In the following description, the conversion source attribute indicates a supplier code, a subject code, a business office code, a department code, and an analysis code.
1. Regarding the determination of the conversion source attribute 1, when the conversion source attribute 1 is an essential item, a search is made for a matching of conversion source attribute 1 of the conversion target data 106r = conversion source attribute 1 of the conversion pattern setting information 106q. Is the conversion source attribute 1 of the conversion pattern setting information 106q = reserved word <ALL>, or the conversion source attribute 1 of the conversion target data 106r = the conversion source attribute 1 of the conversion pattern setting information 106q. Search for a match.
2. Regarding the determination of the conversion source attribute 2, if the conversion source attribute 2 is an indispensable item, the matching of the conversion source attribute 2 of the conversion target data 106r = the conversion source attribute 2 of the conversion pattern setting information 106q is searched. Is the conversion source attribute 2 of the conversion pattern setting information 106q = reserved word <ALL>, or the conversion source attribute 2 of the conversion target data 106r = the conversion source attribute 2 of the conversion pattern setting information 106q. Search for a match.
3. Thereafter, evaluation is performed for the number of conversion source attributes used by the system (that is, when there are conversion source attributes 3 and later, the same processing as the conversion source attributes 1 and 2 is executed).

  Specifically, when the content of the conversion pattern setting information 106q is as shown in FIG. 68 and the content of the conversion target data 106r is as shown in FIG. Whether conversion source data in the data 106r is converted and the conversion completion data 106s is created will be described.

  68. In the conversion pattern setting information 106q shown in FIG. 68, the extraction unit 102q and the conversion unit 102r sequentially start from the conversion source data associated with the higher-order determination order among the conversion source data included in the three records of the company code 100. It is preferable to perform extraction. That is, the extraction unit 102q first converts the conversion source data (company code 100, supplier code ALL, item code 1000: sales, establishment code Tokyo, department code) included in the first line record including the determination order 1. The following extraction process and conversion process are performed for Eigyo and the analysis code Buppan).

(Extraction process)
As shown in FIG. 70, in the record on the first line from the top of the conversion pattern setting information 106q (indicated by an arrow), the conversion source data is (company code 100, supplier code ALL, item, as described in the previous paragraph). Code 1000: a combination of sales, establishment code Tokyo, department code Eigyo, and analysis code Buppan). Here, referring to the conversion target data 106r in FIG. 70, records including this combination are two records (indicated by arrows) in the first and third rows from the top. For this reason, the extraction unit 102q includes the two records of the conversion target data 106r (company code 100, supplier code T1001, item code 1000: sales, establishment code Tokyo, department code Eigyo, and analysis code Buppan). Extract.

(Conversion processing)
Next, processing performed by the conversion unit 102r will be described. In the conversion pattern setting information 106q shown in FIG. 70, the conversion destination data associated with the extracted (company code 100, supplier code T1001, item code 1000: sales, establishment code Tokyo, department code Eigyo, and analysis code Buppan) is , (G_Hanbai). Therefore, the conversion unit 102r, as shown in the first and third lines (indicated by arrows) from the top of the conversion target data 106r in FIG. 70, the conversion source code (company code 100, transaction) acquired by the extraction unit 102q. Previous code T1001, subject code 1000: sales, establishment code Tokyo, department code Eigyo, and analysis code Buppan) are converted into conversion destination data (G_Hanbai).

  Then, as shown in FIG. 71, the extraction unit 102q and the conversion unit 102r are connected to the second lowest determination order in the conversion source data included in the three records of the company code 100 in the conversion pattern setting information 106q. The extraction process and the conversion process are similarly performed on the attached conversion source data (that is, the conversion source data included in the record in the second row from the top of the conversion pattern setting information 106q). As a result, the conversion unit 102r converts the conversion source data extracted by the extraction unit 102q into the conversion destination data (shown in the fourth and fifth lines (indicated by arrows) from the top of the conversion target data 106r in FIG. G_Hanbai).

  Further, as shown in FIG. 72, the extraction unit 102q and the conversion unit 102r are connected to the third lowest determination order in the conversion source data included in the three records of the company code 100 in the conversion pattern setting information 106q. The extraction process and the conversion process are similarly performed on the attached conversion source data (that is, the conversion source data included in the record on the third line from the top of the conversion pattern setting information 106q). Thereby, the conversion unit 102r converts the conversion source data extracted by the extraction unit 102q into conversion destination data (G_Sonota) as shown in the second line (indicated by the arrow) from the top of FIG.

  Furthermore, the extraction unit 102q and the conversion unit 102r similarly perform the extraction process and the conversion process on the conversion source data included in the records in the fourth to sixth lines from the top of the conversion pattern setting information 106q. Conversion completion data 106s shown in 73 is created.

  In addition, in the case where the offices and departments of each company can be directly linked as a hierarchical structure as in a virtual organization, it is not necessary to perform the processing of this item [3-4]. On the other hand, when it is desired to perform aggregation using a common analysis axis for the entire group, such as a virtual segment, the setting becomes complicated if the association with codes of individual companies is managed. Therefore, by converting to a common segment code once by the processing of this item [3-4] and then assigning the common segment code to the virtual segment, it becomes possible to easily set analysis axes at various angles. .

  Specifically, assigning a common segment code to a virtual segment means, for example, the following processing. As shown in FIG. 74, a common segment code of “system business” is set for the SI business and PKG development of company A and the development business unit of company B, while “ Set a common segment code for “Support Business”. As shown in FIG. 74, the common segment code “system business” is assigned to the virtual system “system development business”, while the common segment code “support business” is assigned to the virtual segment “support business”. If so, management analysis can be conducted focusing on the point of view of business.

  Thus, according to the information processing apparatus 100 according to the present embodiment, a combination of a plurality of data (conversion source data) can be converted into common data (conversion destination data). As a result, for example, as described in the previous paragraph, each target can be classified into a common segment code “system development business” and “support business”, and management analysis can be performed focusing on the business content. Also, for example, transactions between the three targets of “Company A's SI business and PKG development and Company B's development division” belonging to the common segment code “System Development Business” are judged to be internal transactions and eliminated. Thus, transactions between the three targets belonging to the common segment code “system development business” and the support division of Company B belonging to the common segment code “support business” are judged as external transactions and are not eliminated. Can also be done.

  Further, according to the information processing apparatus 100 according to the present embodiment, for example, the contents and number of conversion source data and conversion destination data can be arbitrarily set, so that flexible and free data conversion can be performed.

[3-5. Processing other than these]
Finally, processes other than those described in [3-1] to [3-4] will be described in detail with reference to FIG. 75 and FIG.

  According to the information processing apparatus 100 according to the present embodiment, it is possible to simulate the reorganization of a group company. Specifically, when the information processing apparatus 100 according to the present embodiment handles a corporate group, when an external company is acquired under an organizational reorganization or an M & A (merger / acquisition) through an absorption-type merger of companies within the group It is necessary to take into account changes in the company. At this time, according to the information processing apparatus 100 according to the present embodiment, as shown in FIG. 75, the organization chart is copied and the organization is changed, so that the organization is changed (organization before organization change (2) in FIG. 75). Can be compared with the organization after organization reorganization (organization after reorganization (2) ′ in FIG. 75). In FIG. 75, the company 2 is a company belonging to the group core 1 before the organizational change, but is a company belonging to the group core 2 after the organizational change.

  Further, according to the information processing apparatus 100 according to the present embodiment, it is possible to perform management analysis by summing up the amounts of money in three axes of organization × segment × subject according to a combination of functions of organization information and segment information. Specifically, according to the information processing apparatus 100 according to the present embodiment, as shown in FIG. 76, the vertical axis indicates products / brands, the horizontal axis indicates information about stores, and the data on the balance is calculated as the balance. By visualizing with, multiple data can be created. By creating such multi-factor data, it is possible to grasp the current status of store-by-brand balance. Thereby, the sales strategy of each brand can be made for every store.

[4. Other Embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

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

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

  Further, regarding the information processing apparatus 100, each illustrated component is functionally conceptual and does not necessarily need to be physically configured as illustrated.

  For example, the processing functions provided in the information processing apparatus 100, in particular, the processing functions performed by the control unit 102, are realized entirely or arbitrarily by a CPU and a program interpreted and executed by the CPU. It may also be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the processing described in the present embodiment, and the information processing apparatus as necessary. 100 mechanically read. In other words, in a storage unit such as a ROM or a HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into the RAM, and constitutes a control unit in cooperation with the CPU.

  The computer program may be stored in an application program server connected to the information processing apparatus 100 via an arbitrary network, and may be downloaded in whole or in part as necessary. is there.

  In addition, a program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the “recording medium” refers to a memory card, USB (Universal Serial Bus) memory, SD (Secure Digital) card, flexible disk, magneto-optical disk, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (registration). Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Digital, Trademark) Any “portable physical media It is intended to include. Therefore, a recording medium storing a program for executing the processing or processing method described in this specification also constitutes the present invention.

  The “program” is a data processing method described in an arbitrary language or description method, and may be in any form such as source code or binary code. Note that the “program” is not necessarily limited to a single configuration, and functions are achieved in cooperation with a separate configuration such as a plurality of modules and libraries or a separate program represented by the OS. Including things. In addition, a well-known structure and procedure can be used about the specific structure and reading procedure for reading a recording medium in each apparatus shown to embodiment, the installation procedure after reading, etc.

  Various databases and the like stored in the storage unit 106 are storage devices such as a memory device such as a RAM and a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk. Programs, tables, databases, web page files, and the like.

  Further, the information processing apparatus 100 may be configured as an information processing apparatus such as a known personal computer or workstation, or may be configured as the information processing apparatus to which an arbitrary peripheral device is connected. The information processing apparatus 100 may be realized by installing software (including a program or data) that realizes the processing described in this embodiment in the apparatus.

  Furthermore, the specific form of distribution / integration of the devices is not limited to that shown in the figure, and all or a part of them may be functionally or physically in arbitrary units according to various additions or according to functional loads. It can be configured to be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and may be selectively implemented.

  The present invention is useful in all industries, but is particularly useful in the management accounting field, the consolidated accounting field, the group management accounting field, and the like.

100 Information processing apparatus
102 Control unit
102a acquisition unit
102a1 record acquisition unit
102a2 lowest layer record acquisition part
102a3 record creation part
102a4 lowest layer data acquisition unit
102b Extractor
102c totaling department
102d first acquisition unit
102d1 group identification data acquisition unit
102d2 Hierarchy identification data acquisition unit
102d3 record acquisition unit
102d4 repeater
102e second acquisition unit
102f Development data creation unit
102g Record creation part
102h Lowermost layer data acquisition unit
102i extraction unit
102j counting section
102k Subject acquisition unit
102l partner acquisition unit
102m judgment part
102n counting section
102o Aggregation target creation department
102p Target extraction and creation unit
102q extraction unit
102r converter
104 Communication interface
106 Storage unit
106a Hierarchical object management information
106b Hierarchical object expansion information
106c Hierarchical object extraction information
106d Data subject to aggregation
106e Total result data
106f Total key information data
106g User group affiliation information
106h Authority setting information
106i Authority extraction information
106j Hierarchical object security deployment information
106k Supplier specific item setting information
106l Supplier specific pattern setting information
106m Source data for aggregation
106n Data for aggregation
106o Total result data
106p Conversion item setting information
106q Conversion pattern setting information
106r Data to be converted
106s Conversion completion data
108 Input / output interface
112 Input device
114 Output device 200 Server 300 Network

Claims (1)

A data totaling device including a control unit,
The controller is
Object management data including records having information on objects of each layer from the highest layer to the lowest layer in a hierarchical structure formed by forming a hierarchy of objects of the lowest layer and objects of the upper layer ,
The record includes hierarchical structure identification data for identifying the hierarchical structure, hierarchical identification data for identifying each hierarchy in the hierarchical structure, target identification data for identifying the object, and one level higher than each hierarchy. Higher hierarchy identification data for identifying the hierarchy of the above and higher object identification data for identifying the object of the hierarchy one level higher than the object,
The lowest layer record, which is a record having information about the object of the lowest layer, further includes lowest layer identification data for identifying the object of the lowest layer,
With reference to the target management data,
A record acquisition means for acquiring a record including the input hierarchical structure identification data;
From the record acquired by the record acquisition means, the lowest layer record acquisition means for acquiring the lowest layer record,
A record including the same hierarchy identification data and target identification data as the upper hierarchy identification data and upper target identification data included in the lowest layer record acquired by the lowest layer record acquisition means is acquired with reference to the target management data A record creation means for creating a record obtained by adding the lowest layer identification data included in the lowest layer record acquired by the lowest layer record acquisition means to the acquired record;
Referring to the lowest layer record acquired by the lowest layer record acquisition means and the record created by the record creation means, by acquiring the record including the input hierarchy identification data, the lowest level included in the record Lowest layer data acquisition means for acquiring layer identification data;
An extraction means for extracting a numerical value associated with the lowest layer identification data acquired by the lowest layer data acquisition means with reference to aggregation target data including the lowest layer identification data and a numerical value;
Tally means for tallying the numerical values extracted by the extracting means;
Providing
A data aggregation device characterized by

Images