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

Description

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

  Patent Document 1 discloses an analysis support processing device and a program for supporting the analysis of sales, purchases and other performance data accumulated in a core system (see paragraph 0001, etc.).

JP, 2011-248435, A

  In such a field of management accounting, when an object such as a company has a hierarchical structure as shown in FIG. 5 to FIG. there were.

  The present invention has been made in view of the above, and provides a data totaling device, a data totaling method, and a data totaling program that can efficiently aggregate numerical values of objects even when the objects have a hierarchical structure.

  In order to solve the above-mentioned problems and achieve an object, a data aggregating apparatus according to the present invention is a data aggregating apparatus including a control unit, wherein the control unit includes a target of the lowest layer and a target of the upper layer. Is input with reference to target management data including hierarchical structure identification data for identifying a hierarchical structure formed by forming a hierarchy and lowest layer identification data for identifying a target of the lowest layer. Acquisition means for acquiring the lowest layer identification data associated with the hierarchical structure identification data and 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 the associated numerical values and an aggregating means for totalizing the numerical values extracted by the extracting means.

  Further, in the data aggregation device according to the present invention, the target management data includes a record having information about a target of each layer from the highest layer to the lowest layer in the hierarchical structure, and the record has the hierarchical structure. Identification data, layer identification data for identifying each layer in the layered structure, target identification data for identifying the target, upper layer identification data for identifying a layer one level higher than each layer, and the target A lowermost layer record, which is a record having information about the object of the lowermost layer, including upper object identification data for identifying an object of the next higher layer, further includes the lowest layer identification data. The acquisition unit refers to the target management data, acquires the record including the input hierarchical structure identification data, and acquires the lowest layer record from the records acquired by the record acquisition unit. And a record including the same layer identification data and target identification data as the upper layer identification data and the upper target identification data included in the lowest layer record acquired by the lowest layer record acquisition unit, Record creating means for creating a record obtained by referring to the target management data and adding to the obtained record the lowest layer identification data included in the lowest layer record obtained by the lowest layer record obtaining means, By referring to the lowest layer record acquired by the lowest layer record acquisition means and the record created by the record creation means, and acquiring the record including the inputted layer identification data, the lowest layer included in the record is acquired. And lowest layer data acquisition means for acquiring layer identification data.

  Further, in the data aggregating apparatus according to the present invention, the record creating means stores 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 creating means. Obtaining a record by referring to the target management data and adding the lowest layer identification data included in the lowest layer record obtained by the lowest layer record obtaining means to the obtained record, The process is repeated until the lowest layer identification data included in the lowest layer record acquired by the lowest layer record acquisition means is added to the record having information about the object of the highest layer.

  Further, in the data aggregating apparatus according to the present invention, the aggregating means includes the numerical values extracted by the extracting means, and the hierarchical structure identification data, the hierarchical identification data and the target identification included in the record obtained by the lowest layer data obtaining means. It is characterized in that by referring to aggregation key data including a plurality of specifications including a combination of data, the specifications having the same combination are specified, and the numerical values included in the specified specifications are totaled.

  Further, in the data aggregating apparatus according to the present invention, the aggregating unit refers to aggregating key data including a plurality of items including numerical values extracted by the extracting unit and item identifying data, and the item identifying data is the same. When the item exists, only one item of the item is left and the other items are deleted to update the aggregate key data, and the numerical values included in the item contained in the updated aggregate key data are aggregated. It is characterized by

  Further, a data totaling method according to the present invention is a data totaling method executed by an information processing apparatus including a control unit, wherein a target of a lowest layer and a target of an upper layer which are executed by the control unit are hierarchical. The hierarchy input by referring to the target management data including the hierarchical structure identification data for identifying the hierarchical structure formed by the above and the lowest layer identification data for identifying the target of the lowest layer The acquisition step of acquiring the lowest layer identification data associated with the structure identification data, and the aggregation target data including the lowest layer identification data and a numerical value are referred to, and the lowest layer identification data acquired in the acquisition step is associated. It is characterized by including an extraction step of extracting a numerical value and a totaling step of totalizing the numerical values extracted in the extraction step.

  A data totaling program according to the present invention is a data totaling program to be executed by an information processing apparatus including a control unit, and includes a target of the lowest layer and a target of an upper layer for execution by the control unit. Is input with reference to target management data including hierarchical structure identification data for identifying a hierarchical structure formed by forming a hierarchy and lowest layer identification data for identifying a target of the lowest layer. An acquisition step of acquiring the lowest layer identification data associated with the hierarchical structure identification data, the reference data for aggregation including the lowest layer identification data and numerical values, and the lowest layer identification data acquired in the acquisition step. It is characterized by including an extracting step of extracting the associated numerical values and a totaling step of totalizing the numerical values extracted in the extracting step.

  According to the present invention, even when the objects have a hierarchical structure, the numerical value of the objects can be efficiently aggregated.

FIG. 1 is a block diagram showing an example of the configuration of an information processing device. FIG. 2 is a diagram showing a conventional setting example of data when data is aggregated. FIG. 3 is a diagram showing an outline of the hierarchical object management information. FIG. 4 is a diagram showing an example of data in the hierarchical object management information. FIG. 5 is a diagram showing an organization chart (1). FIG. 6 is a diagram showing an organization chart (2). FIG. 7 is a diagram showing an organization chart (3). FIG. 8 is a diagram showing an example of a management number, a hierarchy level, and a node identification code that are input when data is totaled. FIG. 9 is a diagram showing a record including the input management number, which is acquired by referring to the hierarchical object management information. FIG. 10 is a diagram showing a flow of referring to the acquired record and acquiring the record having the hierarchy level of 2. FIG. 11 is a diagram showing a flow of referring to the hierarchized object management information based on the acquired record having the hierarchy level of 2 and acquiring the record having the hierarchy level of 1. FIG. 12 is a diagram showing a flow of referring to the layered object management information on the basis of the acquired record having the hierarchy level of 1 and acquiring the record having the hierarchy level of 0. FIG. 13 is a diagram showing a flow of referring to the acquired records having the hierarchy levels of 2, 1, 0 and acquiring the record including the inputted hierarchy level and the node identification code. FIG. 14 is a diagram showing a flow of extracting the aggregation target value by referring to the aggregation target data based on the linking code included in the acquired record. FIG. 15 is a diagram showing the totalized result of the extracted totalization target values (when the double count is not removed). FIG. 16 is a diagram showing an example of aggregate key information data. FIG. 17 is a diagram showing an example of the aggregation result of the extracted aggregation target values (when the double count is removed). FIG. 18 is a diagram showing a conventional setting example of data when performing security management. FIG. 19 is a diagram showing an example of data in user information and user group information. FIG. 20 is a diagram showing an example of data in the user group affiliation information. FIG. 21 is a diagram showing which user group each user belongs to. FIG. 22 is a diagram showing an example of data in the authority setting information. FIG. 23 is a diagram showing the range of organizations that can be referred to by each user group. FIG. 24 is a diagram showing the range of organizations that can be referred to by each user group in the organization chart (1). FIG. 25 is a diagram showing the range of organizations that can be referred to by each user group in the organization chart (2). FIG. 26 is a diagram showing the range of organizations that can be referred to by each user group in the organization chart (3). FIG. 27 is a diagram showing an example of data in the hierarchical object management information. FIG. 28 is a diagram showing an example of data in the authority setting information. FIG. 29 is a diagram showing an example of data in the user group affiliation information. FIG. 30 is a diagram showing which user group each user belongs to. FIG. 31 is a diagram showing an example of a management number and a user ID that are input when data is totaled. FIG. 32 is a diagram showing a user group code acquired by referring to the user group affiliation information based on the input user ID. FIG. 33 is a diagram showing the hierarchy level and the 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 showing 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 showing a record further acquired by referring to the hierarchical object management information based on the acquired record. FIG. 36 is a diagram showing an example of data in the hierarchical object security development information. FIG. 37 is a diagram showing a record acquired by referring to the hierarchical object expansion information based on the hierarchical object security expansion information. FIG. 38 is a diagram showing a conventional setting example of data when performing internal transaction determination. FIG. 39 is an image diagram of a conventional internal transaction determination. FIG. 40 is a diagram showing an example of data in hierarchical object management information that manages a hierarchical structure made up of virtual organizations. FIG. 41 is a diagram showing an example of data in hierarchical object management information that manages a hierarchical structure composed of virtual segments. FIG. 42 is a diagram showing an example of a hierarchical structure composed of both virtual organizations and virtual segments. FIG. 43 is a diagram showing an outline of the supplier specific item setting information. FIG. 44 is a diagram showing an example of data in the supplier identification pattern setting information. FIG. 45 is a diagram showing transaction details defined by an example of data in the customer identification pattern setting information. FIG. 46 is a diagram showing an example of data in the aggregation target original data. FIG. 47 is a diagram showing a flow of updating the aggregation target original data based on the record in the first line of the supplier identification pattern setting information. FIG. 48 is a diagram showing a flow of updating the aggregation target original data based on the record in the second line of the supplier identification pattern setting information. FIG. 49 is a diagram showing a flow of updating the aggregation target original data based on the records in the third and subsequent rows of the supplier identification pattern setting information to create the aggregation target data. FIG. 50 is a diagram showing an example of a management number, a hierarchy level, and a node identification code that are input when making an internal transaction determination. FIG. 51 is a diagram showing an example of data in the layered object extraction information about the 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 of the company code and the like included in the hierarchical 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 having the same combination of management number, hierarchy level, and node identification code in the hierarchical object extraction information. FIG. 55 is a diagram showing a result of the inside/outside determination of the organization performed based on the matching result. FIG. 56 is a diagram showing an example of a counting result obtained by counting the numerical values included in the counting target data in consideration of the result of the inside/outside determination of the organization. FIG. 57 is a diagram showing an example of data in the layered object extraction information about the virtual segment. FIG. 58 is a diagram showing a matching result between the analysis code included in the hierarchical object extraction information and the analysis code of the own segment included in the aggregation target data. FIG. 59 is a diagram showing a matching result of the analysis code included in the hierarchical object extraction information and the partner analysis code of the partner segment included in the aggregation target data. FIG. 60 is a diagram showing records having the same combination of the management number, the hierarchy level, and the node identification code in the hierarchical object extraction information. FIG. 61 is a diagram showing a result of the segment inside/outside determination performed based on the matching result. FIG. 62 is a diagram showing an example of a counting result obtained by counting the numerical values included in the counting target data in consideration of the result of the segment inside/outside determination. FIG. 63 is a diagram showing the results of the organization inside/outside determination and the segment inside/outside determination. FIG. 64 is a diagram showing an example of the result of totaling the numerical values included in the totaling target data in consideration of the result of the internal/external determination of the organization and the result of the internal/external determination of the segment. 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 the conversion item setting information. FIG. 68 is a diagram showing an example of data in the conversion pattern setting information. FIG. 69 is a diagram showing an example of data in the conversion target data. FIG. 70 is a diagram showing a flow of converting the conversion source data in the conversion target data into the conversion destination data based on the first line record of the conversion pattern setting information. FIG. 71 is a diagram showing a flow of converting the conversion source data in the conversion target data into the conversion destination data based on the second line record of the conversion pattern setting information. FIG. 72 is a diagram showing a flow of converting the conversion source data in the conversion target data into the conversion destination data based on the record in the third line of the conversion pattern setting information. FIG. 73 is a diagram showing conversion target data for which conversion of all conversion source data into conversion destination data has been completed. FIG. 74 is a diagram showing an example of how to allocate common data (conversion destination data) to virtual segments. FIG. 75 is a diagram showing a hierarchical structure of a pre-reorganization organization and a hierarchical structure of a post-reorganization organization. FIG. 76 is a diagram showing an output example of multi-source data.

  Embodiments of a data totaling device, a data totaling method, and a data totaling program according to the present invention will be described below in detail with reference to the drawings. The present invention is not limited to this embodiment.

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

  Specifically, the three items of "Company code", "Business code" and "Department code" are set as the aggregation conditions from the journal entry which is the <data to be aggregated> shown in FIG. If you want to compile the journal details, it is necessary to list all the company codes, business office codes, and department codes that exist in the Hokkaido area you want to collect in <Information associated with the actual organization> shown in Fig. 2. . In this way, in the table for managing the virtual organization, if the method of managing three types of "company code", "business office code" and "department code" is used as the association with the real organization, all the association information is included in the association information. It was necessary to enumerate the assignments, and there were the following three issues. First, the number of items required was fixed and inflexible. Secondly, the more data the linking destination has, the more the setting becomes complicated. Thirdly, if the items to be used for tying increased or decreased from the items "company code", "office code" and "department code", it was necessary to change the program.

Therefore, in the present embodiment, a flexible data totalization setting function and totalization method using an object (target) having a hierarchical structure are provided. In the present embodiment, in the hierarchical object that groups data, the data to be aggregated and the allocation items to be allocated can be flexibly set by the following methods 1 to 3.
1. The contents of the allocation items and the number of allocation items were made variable.
2. Made it possible to select required/optional allocation items.
3. A reserved word that means omission of the allocation condition can be specified for any allocation item.

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

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

  The information processing apparatus 100 is a commercially available desktop personal computer. Note that 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 Assistants), smartphone, tablet personal computer, or the like. It may be an information processing device.

  As shown 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. The respective units included in the information processing apparatus 100 are communicatively connected via an arbitrary communication path.

  The communication interface unit 104 communicatively 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 to each other so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the storage unit 106 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-use television), a speaker, or a printer can be used. As the input device 112, a keyboard, a mouse, a microphone, and a monitor that realizes a pointing device function in cooperation with the mouse can be used. In the following, the output device 114 may be described as the monitor 114 as a display unit, and the input device 112 may be described as the keyboard 112 or the mouse 112.

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

  The storage unit 106 stores, 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. Total data 106e, total key information data 106f as total 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 expansion information 106j, supplier specific item setting information 106k, supplier specific pattern setting information 106l as transaction pattern setting data, aggregation target data 106m, aggregation target data 106n, and aggregation result data 106o. , Conversion item setting information 106p, conversion pattern setting information 106q as conversion pattern setting data, conversion target data 106r, and conversion completion data 106s.

  Further, in the present embodiment, the “object” is, for example, a real organization that is a real organization (for example, a real company, a business office, or a department), a virtual organization that is a virtual organization (for example, A real organization is a hierarchical or reorganized organization for simulation), a real segment that is a real segment (for example, a real business segment, an area or a brand, etc.), or a virtual segment that is a virtual segment (for example, a real segment). (Segmented or recombined segment for simulation) is meant. Specific examples of the real organization, virtual organization, real segment, and virtual segment are shown in the hierarchical structure of FIG. Further, in the present embodiment, the hierarchical structure means a structure formed by forming a 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 a 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 (hierarchical level), target identification data (node identification code), node name, upper level. It includes layer identification data (upper layer level), upper target identification data (upper node identification code), lower structure classification and lowest layer identification data (linking code).

  The management number is data for identifying the hierarchical structure. Specifically, the management number of the hierarchical structure shown in FIG. 5 is set to (1), the management number of the hierarchical structure shown in FIG. 6 is set to (2), and the management number of the hierarchical structure shown in FIG. 7 is set to (3). Thus, the 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 the data to be recorded in the hierarchical object management information 106a is in accordance with the following rules 1 and 2 for the hierarchical object identification information part.
1. A unique management number is assigned to each managed hierarchical object.
2. Set a management name that can be identified by the user for the unique management number.

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

  The node identification code is data for identifying the target. For example, in the case of the organizational chart (1) shown in FIG. 5, the company-wide node identification code is 10000, the company 1 node identification code is 01000, the company 2 node identification code is 02000, and the company 3 node identification code is A node identification code can be set for each target, 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 layer level is data for identifying a layer one layer above each layer. For example, the hierarchy level of companies 1 to 3 in the organizational chart (1) shown in FIG. The hierarchical level is 0. FIG. 3 shows an example of setting the upper hierarchy level.

  The upper node identification code is data for identifying an object in a layer one level higher than an object in each layer. For example, in the case of 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 next higher hierarchy is 10000 as described above, the upper nodes for 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 division is a division indicating whether or not there is a lower hierarchy. For example, in the case of the organizational chart (1) shown in FIG. 5, there is a lower hierarchy from the viewpoint of the entire company, and therefore the lower structure classification for the entire company is “0: lower level”. On the other hand, since there is no lower hierarchy from the viewpoint of the companies 1 to 3, the lower structure classification for the companies 1 to 3 is “1: no lower level”. FIG. 3 shows an example of setting the lower structure division.

The hierarchical level, the node identification code, the node name, the upper hierarchical level, the upper node identification code, and the lower structure classification are collectively referred to as a hierarchical 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 in accordance with the following rules 1 to 5 for the hierarchical structure information part. It should be noted that the upper hierarchy level and the lower structure classification are not essential items in the present invention, but if the data is held in the processing of specifying the upper and lower layers of the hierarchical node, the processing procedure of the program is simpler. It is an item that we are preparing to become.
1. Set a hierarchy level (0 to N) that identifies the hierarchy of the hierarchy object.
2. A unique node identification code is assigned to each same management number/hierarchical level.
3. A node name that can be identified by the user is set for a unique node identification code.
4. For each node in each layer, the layer level (upper layer level) and the node identification code (upper node identification code) of the parent node to which it belongs are set.
5. For each node in each layer, a substructure division is set that distinguishes whether it is the lowest node or if any child nodes exist.

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

  Since the lowest layer identification data is data for identifying the target of the lowest layer as described above, the lowest layer identification data is not assigned to the target higher than the lowest layer. For example, in the layered object management information 106a of FIG. 3, companies 1 to 3 (records in the 2nd to 4th rows from the top) are targets of the lowest layer, and therefore, as the lowest layer identification data, linking codes 1 to 3 are used. However, since the entire company (record in the first line from the top) is not the target of the lowest layer, the lowest layer identification data is not assigned, and the column of the pegging code is "NULL. It has become.

The lowest layer identification data (linking code) is referred to as a linking information section, as shown in FIG. Here, the recording method of the data to be recorded in the hierarchical object management information 106a is in accordance with the following rules 1 to 5 for the linking information part. Note that the character strings of <NULL> that means no setting and <ALL> that means all of them are not limited to this, and may be other character strings.
1. Holds the maximum number of items that will be the aggregation key of the data to be aggregated, which is assumed by the system. 2. In each node, when the substructure classification is “subordinate exists”, it is not necessary to hold the linking information, and thus the reserved word <NULL> which means no setting is held.
3. When the subordinate structure classification is “no subordinate”, each cording target code is held. At this time, the following rules 4 and 5 are applied.
4. Items that are indispensable as pegging items always hold pegging codes.
5. An item that is optional as a linking item holds a reserved word <ALL> that specifies a code when setting a breakdown and means all when a breakdown is not specified.

  Here, a data example of the hierarchical object management information 106a in which specific information is set is shown in FIG. In FIG. 4, a maximum of three items, “company CD (company code)” (required), “business office CD” (optional) and “department CD” (optional), are adopted as the linking information. In addition, "Company CD", which is an essential item, is all specified in the organizational charts (1) to (3) of the data example. In the organization charts (1) and (2), since only the organization in each company is assigned, the reserved word <ALL> which means all “business office CD” and “department CD” is designated. It is in a state of being Further, in the organization chart (3), since the allocation of the organization in the unit of company+the unit of establishment is included, the reserved word <ALL> that means all is specified in the “department CD”. The company 3 is in a state in which the reserved word <ALL>, which means all, is specified because the “business office CD” does not need to be allocated. 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, the organization CD is synonymous with the node identification code, and the organization 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. 5 to 7, respectively.

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

  Although the details of the hierarchical object expansion information 106b will be described later, from the record having the information on the object of the highest layer to the object of the upper layer one layer from the record having the information on the object of the highest layer in the hierarchical object management information 106a. It is information that has been expanded to. As shown in FIG. 12, the layered object expansion information 106b includes, for example, layer structure identification data (management number), layer identification data (layer level), target identification data (node identification code), upper layer identification data (upper layer). Level), upper target identification data (upper node identification code), lowest layer identification data (linking code), and the like.

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

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

  The tabulation result data 106e is data indicating a result of tabulating the tabulation 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), aggregation results, and the like.

  The aggregate key information data 106f is data showing a list of a plurality of specifications extracted by the extracting unit 102b, the details of which will be described later. As shown in FIG. 16, the plurality of specifications include, for example, hierarchical structure identification data (management number), hierarchy identification data (hierarchy level), target identification data (node identification code), detail identification data (detail ID), and aggregation target. Including values etc.

  The user information is information for managing an ID and a name that uniquely identify the user. As shown in the upper table of FIG. 19, the user information includes, for example, user identification data (user ID or user name) and the like.

  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 who belong 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, FIG. 21 shows which user group each user belongs to when the user group affiliation information 106g is set as shown in FIG. It is also possible for one user to belong to a plurality of user groups, that is, to serve concurrently, as in UserC and UserD shown in FIG.

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

  Here, FIG. 23 shows which hierarchy of organizations each user group can refer to when the authority setting information 106h is set as shown in FIG. As shown in FIG. 23, since the full authority group (UserA) can refer to the information of the whole company, it can also refer to the information of companies 1 to 3 which are lower layers of the whole company (see the upper-level browsing authority). Those who have automatically have all viewing rights underneath). On the other hand, the group 1 authority group (UserB and UserC) can refer only 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 the information in 3 can be referenced. A person who belongs to a plurality of authority groups has viewing authority for both companies.

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

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

  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. The hierarchical structure represented by the record indicated by MA5 in FIG. 27 is a hierarchical structure of a virtual organization in which all companies are lined up under the entire company, as shown in FIG. As shown in FIG. 25, the hierarchical structure represented by the record MA6 in FIG. 27 has a three-level hierarchical structure including a hierarchy for all companies, a hierarchy for core companies by business, and a hierarchy for each individual company. The hierarchical structure represented by the record MA7 in FIG. 27 is a hierarchical structure of the virtual organization of the sales department by area, as shown 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 each user group can refer to is shown in the next paragraph. Note that the record indicated by MA8 in FIG. 28 is a record that manages the browsing of the target in the virtual organization in which all companies are lined up under the whole company shown in FIG. 24, and the record indicated by MA9 in FIG. Is a record that manages the browsing of the target in the three layers of the hierarchy of No. 1, the core company by business, and the hierarchy of each individual company. The record indicated by MA10 in FIG. 29 is the record for browsing the target in the virtual organization of the sales department by area. It is a record to manage.

  That is, as shown in FIG. 24, UserA belonging to the user group “Full” can refer to information on all the companies 100 to 300, which are lower layers of the entire company. Further, 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. UserD belonging to the user group “Company3” can refer to the information of the company 300. Then, as shown in FIG. 25, UserA belonging to the user group “Full” can refer to information of all the companies 100 to 400, which are lower layers of the entire company, and UserB belonging to the user group “KougiGroup” belongs to the construction business group. Information of the lower layer companies 100 and 200 can be referred to, and UserD belonging to the user group “SeizouGroup” can refer to information of the company 300 and company 400 lower layers of the manufacturing business group. As indicated by MA4 in FIG. 25, the range of visible objects in these three groups differs depending on the range in which the 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 office, sales department) and (company 200, Osaka branch office, sales department), and UserE belonging to the user group “KantouGroup” is a lower layer of the Kanto group (company 100, Tokyo headquarters, Information of (Sales Department) and (Company 200, Tokyo Head Office, Sales Department) can be referred to, and UserD belonging to the user group “KansaiGroup” is a lower layer of the Kansai Group (Company 100, Osaka Branch, Sales Department) and (Company). 200, Osaka Branch, Sales Department). 24 to 26, a user who is not permitted any access cannot access all the 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 location according to the hierarchical level of the hierarchical object, and the minimum required setting is flexible. It is possible to respond.

  Although the details will be described later, the authority extraction information 106i is information extracted by referring 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, layer structure identification data (management number), layer identification data (layer level), target identification data (node identification code), and user group identification data (user group code). Including 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, the details of which will be described later. As shown in FIG. 36, the hierarchical object security development information 106j includes, for example, hierarchical structure identification data (management number), hierarchical identification data (hierarchical level), target identification data (node identification code), and the like.

  The business partner specific item setting information 106k defines a combination of a use item (business partner code, subject code, business office code, etc.) of the company's transaction content and a use item (business office code, department code, etc.) of other party information to be specified. This is information for doing. Specifically, as shown in FIG. 43, as items to be used for the transaction content of the company, for example, “use” or five items of a supplier code, a subject code, a business place code, a department code and an analysis code are used. It is possible to set "not use". Further, as shown in FIG. 43, as the use item of the other party information to be specified, for example, “use” or “not use” is set for three items of the other party office code, the other party department code and the other party analysis code. be able to.

  The supplier specific pattern setting information 106l is information for specifying a trading partner, in other words, information for defining the specified pattern information according to the supplier specific item setting information 106k. The supplier specific pattern setting information 106l illustrated in FIG. 44 is a data example when “use” is set for all the items in the supplier specific item setting information 106k described in the preceding paragraph. As shown in FIG. 44, the supplier identification pattern setting information 106l is the subject lowest layer identification data (company code, establishment code, department) that is the lowest layer identification data for identifying the subject who is the subject of the transaction. Code or analysis code), subject identification data (subject code) for identifying the accounting item of the transaction, supplier identification data (subscriber code) for identifying the subject of the transaction, and the transaction partner The partner lowest layer identification data (the partner company code, the partner office code, the partner department code or the partner analysis code) which is the lowest layer identification data for identifying a certain partner target. As shown in FIG. 44, supplier specific pattern setting information 106l may further include a determination order. The significance of the determination order will be described later.

  In the customer specific pattern setting information 106l, the character string of the reserved word <ALL>, which means all, is not limited to this, and may be another character string. If the code, subject code, business site code, department code or analysis code) is set in <ALL>, the same transaction can be executed for multiple partner attribute information (partner company code, partner business office code, partner department code or Since it may be associated with the other party analysis code), it should be uniquely determined according to the determination order.

  Here, what kind of transaction is defined by the supplier specific pattern setting information 106l shown in FIG. 44 will be described with reference to FIG. First, the transaction defined by the records (two records with the company code 100) from the top in the table of FIG. 44 is shown in FIG. 45(A). As shown in (A) of FIG. 45, the purchase transaction partner of the company 100 (company code)/Tokyo (establishment code)/Eigyo (department code)/product sales business (analysis code) is the company 300 (partner company). Code)/Osaka (counterpart office code)/Hanbai1 (counterpart code)/retail business (partner analysis code), and company 100/Tokyo/Eigyo/sales business partner is company 200/Tokyo/Seizou1 / It is a manufacturing business. Next, the transaction defined by the records in the fifth to sixth rows (two records with the company code of 300) in the table of FIG. 44 is shown in FIG. 45(B). As shown in (B) of FIG. 45, the sales transaction partners of company 300/Osaka/Hanbai1/retail business are company 100/Tokyo/Eigyo/product sales business and company 200/Osaka/Seizou2/manufacturing business. Finally, the transaction defined by the records in the third to fourth rows (two records with the company code of 200) in the table of FIG. 44 is shown in (C) of FIG. As shown in (C) of FIG. 45, all business establishments, divisions, and business fields of the company 200 are purchased/sales transaction partners of the company 100/Tokyo/Eigyo/product sales business and the company 300/Osaka/Hanbai1. / It is a retail business. Businesses, departments, and segments are uniquely determined for each business partner in transactions that occur in the manufacturing department.

  The aggregation target original data 106m is data that is a source when the aggregation target data 106n is created. As shown in FIG. 46, the aggregation target original data 106m is the subject lowest layer identification data (company code, establishment code, department code or analysis code), subject identification data (subject code), and supplier identification data (supplier). Code) and. 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 original data 106m further includes the date (occurrence date) and the numerical value (amount) of the details (details mean one horizontal line of information in the table of the aggregation target original 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, office code, department code or analysis code) and the partner lowest layer identification data (partner company code, partner office code, Partner department code or partner analysis code). As shown in FIG. 49, the aggregation target data 106n further includes the date of occurrence (occurrence date) of the details (the detail means the information in one row in the table of the aggregation target data 106n), the item identification data (the item code). ), supplier identification data (customer code), a numerical value (amount of money), and the like.

  The tabulation result data 106o is data indicating the result of tabulating the tabulation target data 106n. As shown in FIG. 56, the aggregation result data 106o includes, for example, hierarchical structure identification data (management number), hierarchical identification data (hierarchical level), target identification data (node identification code), subject identification data (subject code), group. It includes the external transaction amount which is the transaction amount between the two, the internal transaction amount which is the transaction amount within the group, and the total amount which is the total amount of the external transaction amount and the internal transaction amount.

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

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

  The conversion source data is composed of a plurality of data. A plurality of pieces of data are account identification data (subject code) for identifying accounting items, establishment identification data (establishment code) for identifying establishments in a certain company, and divisions for identifying divisions in a certain company. It is preferably at least two data selected from the group consisting of identification data (department code) and business content identification data (analysis code) for identifying the business content of a certain company. Further, the plurality of data is at least one of at least two data, company identification data (company code) for identifying a certain company, and supplier identification data (company code) for identifying a supplier of a certain company. And more preferably. The conversion pattern setting information 106q illustrated in FIG. 68 is an example that includes all six items of the subject code, the office code, the department code, the analysis code, the company code, and the supplier code as the conversion source data.

  The conversion destination data is, for example, data that is commonly held by certain objects. For example, the objects in the first, second, and fifth rows from the top of FIG. Therefore, it has the conversion destination data (common segment code) called “G_Hanbai”. As shown in FIG. 68, one common segment code (common segment code 1) may be used, or two or more common segment codes (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.

  Note that, 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 to <ALL>, the same transaction is common to multiple conversion destination common attribute parts (common Since there is a possibility that it will be associated with (segment code), it should be uniquely determined according to the determination order. Then, by setting the determination order of the line that sets all attributes other than company code in <ALL> to the lowest, the general purpose such as "other" is applied to the remaining conversion target data that is not converted in the higher determination order. It is possible to assign a specific code.

  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, supplier code, establishment code, department code or analysis code). The description of the conversion source data included in the conversion target data 106r can be based on the description of the conversion source data of the conversion pattern setting information 106q. As shown in FIG. 69, the conversion target data 106r further includes an occurrence date (occurrence date), a numerical value (amount of money), and the like of the details (details mean one horizontal line of information in the table of the conversion target data 106r). May be included.

  The conversion completion data 106s is data in which the conversion of the conversion source data included in the conversion target data 106r into the conversion destination data is completed. As shown in FIG. 73, the conversion completion data 106s includes, for example, conversion source data (subject code, company code, supplier code, business office code, department code or analysis code), conversion destination data (common segment code), details. The specification includes the date of occurrence (occurrence date) and the numerical value (amount of money) of the conversion completion data 106s (meaning information in one horizontal line in the table).

  The control unit 102 is a CPU or the like that totally 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 required data, and performs various information processing based on these stored programs. Run.

  The control unit 102 is functionally conceptually composed of, for example, (1) hierarchical structure identification data for identifying a hierarchical structure formed by a target of the lowermost layer and a target of the uppermost layer forming a hierarchy and the lowermost layer. An acquisition unit 102a as an acquisition unit that acquires the lowest layer identification data associated with the input hierarchical structure identification data by referring to the target management data including the lowest layer identification data for identifying the target of the layer. , (2) referring to the target management data, a record acquisition unit 102a1 as a record acquisition unit that acquires a record including the input hierarchical structure identification data, and (3) a record acquired by the record acquisition unit, A lowest layer record acquisition unit 102a2 as a lowest layer record acquisition means for acquiring the lowest layer record; and (4) upper layer identification data included in the lowest layer record acquired by the lowest layer record acquisition means, and A record including the same layer identification data and target identification data as the upper layer target identification data is obtained by referring to the target management data, and the obtained record is added to the lowest layer record obtained by the lowest layer record obtaining means. A record creating unit 102a3 as a record creating unit that creates a record to which the lowest layer identification data included is added, and (5) the lowest layer record acquired by the lowest layer record acquiring unit and the record creating unit. A lowest layer data acquisition unit 102a4 as a lowest layer data acquisition unit that acquires the lowest layer identification data included in the record by acquiring the record including the input layer identification data by referring to the record. (6) An extraction unit 102b as an extraction unit that extracts the numerical value associated with the lowest layer identification data acquired by the acquisition unit with reference to the aggregation target data including the lowest layer identification data and the numerical value, ( 7) To identify a hierarchical structure formed by aggregating unit 102c as an aggregating unit that aggregates the numerical values extracted by the extracting unit, and (8) a target of the lowest layer and a target of the upper layer form a hierarchy. Input hierarchical structure identification data with reference to target management data including hierarchical structure identification data, hierarchical identification data for identifying each layer in the hierarchical structure, and target identification data for identifying the target. It is input by referring to the first acquisition unit 102d as the first acquisition unit that acquires the associated layer identification data and the target identification data, and (9) the user management data including the user group identification data and the user identification data. Yu Group identification data acquisition unit 102d1 as a group identification data acquisition unit that acquires user group identification data associated with user identification data, and (10) hierarchical structure identification data, hierarchical identification data, target identification data, and user group identification data. Acquisition of layer identification data and the like for obtaining the layer identification data and the target identification data associated with the input hierarchical structure identification data and the user group identification data acquired by the group identification data acquisition means with reference to group management data including The layer identification data etc. acquisition unit 102d2 as means, and (11) referring to the target management data, the input hierarchical structure identification data and the layer identification data and target identification data acquired by the layer identification data etc. acquiring unit. And a record acquisition unit 102d3 as a record acquisition unit that acquires a record including, and (12) upper layer identification data and upper target identification data that are the same as the layer identification data and the target identification data included in the record obtained by the record acquisition unit. A record containing the same is acquired by referring to the target management data, and a record containing the same upper layer identification data and upper target identification data as the layer identification data and the target identification data included in the acquired record is acquired by the target management. A repeating unit 102d4 as a repeating unit that repeats the acquisition by referring to the data until the hierarchy identification data and the target identification data included in the lowest layer record are acquired by acquiring the lowest layer record. (13) The inputted hierarchical structure identification is referred to by referring to target expanded data including hierarchical structure identification data, hierarchical identification data, target identification data, and lowest layer identification data for identifying the object of the lowest layer. A second acquisition unit 102e as a second acquisition unit that acquires data and the lowest layer identification data associated with the layer identification data and the target identification data acquired by the first acquisition unit, and (14) refer to the target management data Then, the record including the input hierarchical structure identification data is obtained, the lowest layer record is obtained from the obtained record, and the obtained lowest layer record is set as the target expansion data. An expanded data creating unit 102f as expanded data creating means for creating target expanded data, and (15) upper layer identification data and upper layer included in the lowest layer record including the lowest layer identification data acquired by the second acquisition means. The same layer identification data as the target identification data and As a record creating unit that acquires a record including target identification data by referring to the target management data and creates a record in which the lowest layer identification data acquired by the second acquisition unit is added to the acquired record. The record creating unit 102g includes (16) the lowest layer record including the lowest layer identification data acquired by the second acquisition unit and the record created by the record creating unit, and includes the input layer identification data. A lowest layer data acquisition unit 102h as a lowest layer data acquisition unit that acquires the lowest layer identification data included in the record by acquiring the record, and (17) lowest layer identification data and a numerical value. With reference to the aggregation target data, an extraction unit 102i as an extraction unit that extracts a numerical value associated with the lowest layer identification data acquired by the lowest layer data acquisition unit, and (18) a numerical value extracted by the extraction unit. (19) Hierarchical structure identification data for identifying a hierarchical structure formed by the object of the lowest layer and the object of the upper layer forming a hierarchy, and Transaction is performed by referring to target extraction data including layer identification data for identifying each layer, target identification data for identifying the target, and lowest layer identification data for identifying the target of the lowest layer. The lowest layer identification data that is the lowest layer identification data that identifies the subject that is the subject of the transaction, and the lowest layer identification data that is the identification data that is the lowest layer that identifies the target of the transaction (20) The subject extraction unit 102k as a subject obtaining unit that obtains the hierarchical structure identification data associated with the subject lowest layer identification data included in the aggregation target data including A partner acquisition unit 102l as a partner acquisition unit that acquires the hierarchical structure identification data, the layer identification data, and the target identification data associated with the partner lowest layer identification data included in the aggregation target data with reference to the data, and (21 ) If the hierarchical structure identification data, the hierarchical identification data, and the target identification data acquired by the subject acquisition unit are the same as the hierarchical structure identification data, the hierarchical identification data, and the target identification data acquired by the partner acquisition unit, the subject target And a determination unit 102m as a determination unit that determines that the transaction between the other party and the other party is an internal transaction within the group, and (22) if the same, the subject maximum included in the aggregation target data. With lower layer identification data An aggregating unit 102n as an aggregating unit for aggregating the associated numerical values, (23) subject identification data for identifying the lowest layer identification data of the subject, item identification data for identifying the accounting item of the transaction, and a transaction target of the subject. By referring to the aggregation target source data including the supplier identification data, the subject maximum data included in the transaction pattern setting data including the subject lowest layer identification data, the subject identification data, the supplier identification data, and the partner lowest layer identification data. The same entity as the lower layer identification data, the item identification data, and the customer identification data, the lowest layer identification data, the item identification data, and the customer identification data are extracted, and the extracted subject lowest layer identification data, the item identification data, and the customer are extracted. A totaling target creating unit as a totaling target creating unit that creates the totaling target data by adding the partner lowest layer identification data included in the transaction pattern setting data, which is associated with the identification data, to the totaling target source data. 102o and (24) the target management data is referred to acquire a record including the input hierarchical structure identification data, the lowest layer record is acquired from the acquired record, and the acquired lowest layer is acquired. A record including the same layer identification data and target identification data as the upper layer identification data and the upper target identification data included in the record is acquired by referring to the target management data, and the acquired record is added to the acquired lowest layer. A record to which the lowest layer identification data included in the record is added is created, the record including the input layer identification data is acquired by referring to the acquired lowest layer record and the created record, and the acquired By using a record as the target extraction data, a target extraction creating unit 102p as a target extraction creating unit that creates the target extraction data, and (25) conversion target data including conversion source data composed of a plurality of data are referred to. An extraction unit 102q as an extraction unit that extracts the same conversion source data as the conversion source data included in the conversion pattern setting data that includes the conversion source data and the conversion destination data; and (26) the conversion extracted by the extraction unit. The conversion unit 102r as a conversion unit that converts the original data into the conversion destination data included in the conversion pattern setting data associated with the conversion source data. For details of the processing executed by each unit, refer to [3. Specific example of processing].

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

[3-1. Data aggregation processing]
First, the data totaling process will be described in detail mainly with reference to FIGS. The data totaling process is roughly divided into three processes, that is, an acquisition process, an extraction process, and a totaling process. Therefore, items will be described in this order in the following order.

(1) Acquisition Process The acquisition unit 102a refers to the hierarchical object management information 106a including the management number and the linking code, and acquires the linking code linked to the input management number. The specific processing is as shown in (1-1) to (1-4) below.

(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 condition for record acquisition. In this case, the record acquisition unit 102a1 acquires only the record including the organization chart (3) from the hierarchical object management information 106a including the records having various management numbers, as shown in FIG. Note that, in FIG. 9, a portion surrounded by a thick frame is data specified based on the inputted organization chart (3).

  Then, as shown in (1-2) to (1-4) below, regarding the records extracted from the hierarchical object management information 106a, the hierarchical objects are arranged in descending order of hierarchical level (hierarchical level). The expansion 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 retrieves 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 expansion information 106b.

  By now, as shown in FIG. 10, the creation of the layered object expansion information 106b including the record having the layer level 2 is completed.

(1-3) Record Creation Processing The record creation unit 102a3 is 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 obtained by referring to the hierarchical object management information 106a, and a record in which the linking code included in the lowest layer record obtained by the lowest layer record obtaining unit 102a2 is added to the obtained record is created.

  That is, for the layers above the terminal layer (the lowest layer), from the layered object management information 106a and the layered object development information 106b created in (1-2) to the layered object development information 106b of the upper layer. To create.

  Specifically, of 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 11000 will be described. The record including the same hierarchical level and node identification code as the upper hierarchical level 1 and the upper node identification code 11000 is the second record from the top in the hierarchical object management information 106a in FIG. 11 (enclosed by a thick frame). Therefore, the record creating unit 102a3 first acquires this record. Next, the record creation unit 102a3 adds to the acquired record the linking code (1, 001, ALL) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 and the acquired record. A record to which the linking code (1, ALL, A) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 is added is created. Then, the two created records are stored in the hierarchical object expansion information 106b.

  Of 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 also processed by performing the same process as in the preceding paragraph, so that FIG. A record obtained by acquiring the record (enclosed in a thick frame) in the fifth row from the top of the hierarchical object management information 106a, and adding the linking code (2,001, ALL) to the acquired record, and the acquired record. Create a record in which the pegging code (3, ALL, ALL) is added to. Then, the two created records are stored in the hierarchical object expansion information 106b.

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

  By now, as shown in FIG. 11, the creation of the layered object expansion information 106b including the record having the hierarchy level 2 and the record having the hierarchy level 1 is completed.

  Here, when the hierarchical object management information 106a includes only the hierarchy levels 0 and 1 (that is, when the hierarchy is two layers), the process performed by the record creating unit 102a3 is ended, but in this example. As described above, when the hierarchy level is 2 or more (that is, when the hierarchy is three or more layers), the record creating unit 102a3 continuously performs the following processing.

  That is, the record creating 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 upper node identification code included in the record created by the record creating unit 102a3. To obtain a record having the information about the target of the highest layer, create a record in which the linking code included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 is added to the acquired record. The process is repeated until the linking 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 higher hierarchy level 0 and the higher 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. It is a record (enclosed by a thick frame) in the first line from the top in the encrypted object management information 106a. Therefore, the record creating unit 102a3 first acquires this record. Next, the record creation unit 102a3 adds the linking code (1, 001, ALL) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 to the acquired record, and adds the acquired record to the acquired record. A record in which the linking code (1, ALL, A) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 is added, and the lowest layer record acquired by the lowest layer record acquisition unit 102a2 in the acquired record. To the record to which the pegging code (2, 001, ALL) included in is added and the pegging code (3, ALL, ALL) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 to the acquired record. Create a record. Then, the four records thus created are stored in the hierarchical object expansion information 106b.

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

  Up to this point, as shown in FIG. 11, the creation of the hierarchical object expansion information 106b including the record having the hierarchical level 2, the record having the hierarchical level 1, and the record having the hierarchical level 0 is completed, that is, the hierarchical object expansion. The information 106b is completed.

  Although not shown in this example, the record creating unit 102a3 has the information about the object of the highest layer when performing the processing described in this item (1-3) when there is a higher hierarchy. This may be repeated until the linking 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 of the layer level 0).

(1-4) Lowest layer data acquisition process 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 the record including the hierarchical level, the linking code included in the record is acquired.

  Specifically, as shown in FIG. 8, it is assumed that hierarchy level 1 is input as a condition for record acquisition. In this case, the lowest layer data acquisition unit 102a4 refers to the layered object expansion information 106b shown in FIG. 13 to acquire the record including the layer level 1, that is, the four records indicated by MA3 in FIG. , Four sets of associated codes (1,001,ALL), (1,ALL,A), (2,001,ALL) and (3,ALL,ALL) included in the record. 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, the node identification code may be input as the condition for record acquisition (whether or not the range of the node identification code is specified), but if not input, all the node identification codes are input. It is the target of acquisition by the lowest layer data acquisition unit 102a4.

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

(2) Extraction Process 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 linking code of the hierarchical object extraction information 106c. As a condition 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 pegging code 1, when the pegging code 1 is a required item, the pegging code 1 of the aggregation target data 106d=the pegging code 1 of the hierarchical object extraction information 106c is searched for, and the pegging code 1 is an optional item. In this case, the matching code 1 of the hierarchical object extraction information 106c is a reserved word <ALL>, or the matching code 1 of the aggregation target data 106d is the matching code 1 of the hierarchical object extraction information 106c.
2. Regarding the determination of the pegging code 2, if the pegging code 2 is an essential item, the pegging code 2 of the aggregation target data 106d=the pegging code 2 of the hierarchical object extraction information 106c is searched for, and the pegging code 2 is an optional item. In this case, the matching code 2 of the hierarchical object extraction information 106c is the reserved word <ALL>, or the matching code 2 of the aggregation target data 106d=the matching code 2 of the hierarchical object extraction information 106c is searched for.
3. Regarding the determination of the pegging code 3, when the pegging code 3 is an essential item, the pegging code 3 of the aggregation target data 106d=the pegging code 3 of the hierarchical object extraction information 106c is searched for, and the pegging code 3 is an optional item. In this case, the matching code 3 of the hierarchical object extraction information 106c is the reserved word <ALL>, or the matching code 3 of the aggregation target data 106d is the matching code 3 of the hierarchical object extraction information 106c.
4. Then, hereinafter, the evaluation is performed by the number of pegging codes used by the system (that is, when pegging codes 4 and later are present, the same processing as pegging codes 1 to 3 is executed).

  Specifically, as shown in the totalization target data 106d in FIG. 14, the details including the linking code (1,001, ALL) of the condition (1) are the details of the detailed ID=1 (totalization target value=1,000). ). Similarly, the details including the linking code (1, ALL, A) of the condition (2) are the details of the detail ID=1 (total target value=1,000) and the details of the detail ID=4 (total target value=4). , 000). <ALL> means that any information may be entered. Similarly, the specification including the linking code (2, 001, ALL) of the condition (3) is the specification with the specification ID=2 (total target value=2,000). Similarly, the details including the linking code (3, ALL, ALL) of the condition (4) are the details of the detail ID=3 (total target value=3,000) and the details of the detail ID=6 (total target value=6). , 000), the item with the item ID=9 (the target value for aggregation=9000), and the item with the item ID=12 (the target value for aggregation=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 totaling target to be searched matches a plurality of linking conditions, it is necessary to consider that the same line (same item) is counted a plurality (double count) (item ID=1). Details are applicable). The detail ID is key information that can uniquely identify a row (specification) of the aggregation target data 106d, and either a single item or a combination of complex items is possible, but in this example, an example of a single item is used. It has been 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 totaling target values extracted by the extracting unit 102b to obtain the total of 1,000+1,000+4,000+2,000+3,000+6,000+9000+2,000+38,000. May be performed, but it is preferable to perform aggregation in units of layers and aggregation without double counting as follows.

  Here, the contents of the aggregation key information data 106f necessary when performing aggregation in hierarchical units and aggregation without double counting 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, the management number, the hierarchy level, and the node included in the four records acquired by the lowest layer data acquisition unit 102a4. A plurality of specifications including a combination of identification codes and a specification ID are included.

(3-1) Aggregation in Hierarchical Units First, aggregation in hierarchical units will be described. As shown on the left side of FIG. 16, the aggregating unit 102c is a combination of the aggregation target value extracted by the extracting unit 102b, the management number, the hierarchy level, and the node identification code included in the four records acquired by the acquiring unit 102a4, With reference to the aggregate key information data 106f including a plurality of specifications including, the specifications having the same combination are specified, and the numerical values included in the specified details are totaled.

  Specifically, as shown on the left side of FIG. 16, the details of the first to third lines from the aggregate key information data 106f are all combinations of organization chart (3), hierarchy level 1, and node identification code 11000. Including. Therefore, the totaling unit 102c identifies the details of the first to third lines as the details having the same combination, and sets the numerical values included in the details of the specified first to third lines to 1,000+1,000+4. , 000=6,000. On the other hand, as shown on the left side of FIG. 16, the specifications in the fourth to eighth rows from the top of the aggregate key information data 106f all include the combination of organization chart (3), hierarchy level 1 and node identification code 12000. Therefore, the totaling unit 102c totals the numerical values included in the details of the fourth to eighth lines as 2,000+3,000+6,000+9000+2,000=32,000. The tabulation result is shown in tabulation result data 106e in FIG.

  As described above, in the present embodiment, the aggregation target values are aggregated in a hierarchy unit of hierarchy level 1. That is, the aggregation result for “company 1: Tokyo headquarters and company 1: Kanto sales department belonging to the Kanto area” shown in the hierarchical object management information 106a in FIG. 9 is 6,000, and “company 2: Kansai area 2: The total of 32,000 for the Osaka branch and company 3" was calculated (aggregation by region). However, when the user inputs the hierarchy level 0 or the hierarchy level 2, the following aggregation can be performed. That is, when the hierarchy level 0 is input, the aggregation result for "all companies" shown in the hierarchical object management information 106a of FIG. 9 becomes 38,000 by the same method as that described above (whole company unit). In total). Further, when the hierarchy level 2 is input, the aggregation result for “company 1: Tokyo head office” shown in the hierarchical object management information 106a of 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" Becomes 3,000+6,000+9,000+12,000=30,000 (aggregation by end unit). As described above, according to the information processing apparatus 100 according to the present embodiment, it is possible to perform aggregation in units of different layers (company-wide units, regional units, or terminal units) depending on the layers input by the user.

  Here, in the tabulation method described in this item, the details of the first to second rows (both of which are the item ID=1) from the top of the tally key information data 106f shown on the left side of FIG. Have been counted). It is not necessary to remove such double counts if the aggregation target does not correspond to multiple pegging settings in the pattern of pegging settings, or if the aggregation target has multiple pegging settings in the pattern of pegging settings. This may be the case when it is determined that double counting does not cause a problem or that double counting should be performed.

  However, there may be cases where the aggregation target corresponds to a plurality of pegging settings due to the pegging setting pattern, and it may be determined that double counting should not be performed. In this case, the unique key information (detail ID) of the details that match the pegging setting is specified, the duplicate rows are removed, and then the aggregation is performed, that is, double counting is performed as shown in (3-2) below. It is preferable to carry out the removed aggregation.

(3-2) Counting without Double Count Next, counting with double count removed will be described. If the item ID having the same item ID exists in the aggregation key data 106f that includes a plurality of items including the item to be totaled extracted by the extraction unit 102b and the item ID, the aggregating unit 102c only has one item of the items. The other items are deleted while the other items are deleted to update the aggregate key data 106f, and the numerical values included in the items included in the updated aggregate key data 106f are aggregated.

  Specifically, as shown on the left side of FIG. 16, since the detail IDs included in the details of the first and second rows from the top of the summary key information data 106f are both 1, the tallying unit 102c determines that the second row. The aggregate key data 106f is updated by deleting the details of (No. the details of the second line but the details of the first line may be deleted). 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 totalization key data 106f to obtain 1,000+4,000+2,000+3,000+6,000+9. , 000+12,000=37,000.

  Note that the aggregation unit 102c may perform aggregation in units of layers described in (3-1) in addition to removing the double count, and the aggregation result in this case is shown in the aggregation 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 of the objects can be efficiently aggregated.

  Further, according to the information processing apparatus 100 according to the present embodiment, the content of the linking code and the number of items can be freely set, so that flexible aggregation can be performed. In the present embodiment, the aggregation based on the three linking codes has been described, but other aggregations such as aggregation considering only the company code, aggregation considering the company code and department code, and segment code only are described. It is also possible to carry out the totalization in consideration.

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

  The processing performed in this item is the pre-processing of (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 hierarchy level, and the node identification code, and refers to the input management number and the hierarchy level and the node identification. Get the code. The specific processing is as shown in (1-1) to (1-4) below.

(1-1) Group Identification Data Acquisition Process The group identification data acquisition unit 102d1 acquires the user group code associated with the input user ID by referring to the user group affiliation information 106g including the user group code and the 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, UserB is input as the user ID. In this case, the group identification data acquisition unit 102d1 acquires Company1 and KojiGroup as user group codes associated with UserB, as indicated by MA11 and MA12 in FIG. 32, respectively.

(1-2) Acquisition Processing of Hierarchical Identification Data The hierarchical 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 inputs the management number. And a layer level and a node identification code associated with the user group code acquired by the group identification data acquisition unit 102d1. That is, the authority setting information 106h is queried 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. Also, 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 the node identification code associated with the organization chart (2) and KojiGroup, as indicated by MA13 in FIG.

  The hierarchy identification data acquisition 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 acquisition unit 102d1. The information 106i may be created as shown in FIG. If one user belongs to a plurality of user groups and has authority, the authority extraction information 106i may have multiple 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. 102d2. Acquire the record including the hierarchy level and node identification code acquired in. That is, the record acquisition unit 102d3 inquires the hierarchical object management information 106a based on the management number, hierarchy level, and node identification code of the authority extraction information 106i.

  Specifically, the input management number is the organizational chart (2) as described above. The layer level and node identification code acquired by the layer 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 the information surrounded by the thick frame in FIG. 34 as the record including the organization chart (2) and 1 and 21000.

(1-4) Repeating Process The repeating unit 102d4 manages a record including the same higher 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, in the hierarchical object management. The information 106a is obtained by referring to the information 106a, and a record including the same higher hierarchy level and higher node identification code as the hierarchy level and node identification code included in the obtained record is obtained by referring to the hierarchical object management information 106a. This is repeated until the lowest layer record is obtained to obtain the hierarchy level and node identification code included in the lowest layer record. That is, when the lower structure classification of the corresponding node is <lower structure exists>, the repeating unit 102d4 acquires a lower node list having its own node as the upper layer level and the upper node identification code, and restarts this process. To call. Then, when the subordinate structure classification of the corresponding node is <no subordinate structure>, the own node is held as the hierarchical object security development 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 repeating unit 102d4 obtains two lines of records including the information surrounded by the thick frame in FIG. 35, as the records including the same higher hierarchy level and higher node identification code as 1 and 21000. Further, the repeating unit 102d4 may repeat the same process to acquire the record of the lower layer, but in this example, the acquired record of two rows includes the lowest level 2 of the hierarchy. Since it is the lowest layer record, the processing ends here.

  The repeating unit 102d4 creates the hierarchical object security expansion 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 hierarchical object security development information 106j, lines detected when the authority is set to both 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 the “tier level 2 and node identification code 21100” and the “tier 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. A cording code associated with the hierarchy level and the node identification code acquired in 102d is acquired. That is, the second acquisition unit 102e narrows down the hierarchized object security development information 106j to information at the end of the hierarchized level of the hierarchized object development information 106b, and sets only referenceable data as developed data.

  Specifically, the input management number is the organizational chart (2) as described above. The hierarchical 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 layered object expansion information 106b of FIG. 37 as a linking code to be linked with the organizational charts (2), 2 and 21100. In addition, the second acquisition unit 102e acquires (200, ALL, ALL) in the hierarchical object expansion information 106b in FIG. 37 as a linking code to be linked with the organizational charts (2), 2 and 21200. In this way, the original hierarchical object development information 106b is narrowed down to only data that matches the hierarchical object security development information 106j.

  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. Is. The hierarchical object expansion information 106b including only the record of the hierarchical level 2 can be created by the expanded data creating unit 102f, and the specific creating method is as follows: [3-1] record acquisition unit 102a1 and lowest layer record. Since the processing is the same as that performed by the acquisition unit 102a2, the description thereof will be omitted.

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

  As described above, according to the information processing apparatus 100 according to the present embodiment, it is possible to limit the range of target information that the user can refer to.

  Further, according to the information processing apparatus 100 according to the present embodiment, for example, it is possible to flexibly set the position of the layer and the number of layers that the user can refer to.

  In the example of the organization chart (2) of FIG. 25, setting the position of the hierarchy means setting the range that the user can refer to in the layers of the entire company (that is, refer to all information of the companies 100 to 400). Yes, you can set it in the core company layer (you can refer to the information of the construction business group or manufacturing business group), or you can set it in the individual company layer (you can refer to the information of any one of the companies 100 to 400) ) Is the setting.

  Setting the number of layers means, for example, in the layer of the core company in the example of the organization chart (2) in FIG. 25, is it possible to refer to only the information of one of the construction business group and the manufacturing business group ( That is, it is a setting that either one of the hierarchies that can be referred to) or whether information of both the construction business group and the manufacturing business group can be referred to (that is, two hierarchies that can be referred to). By being able to refer to both groups, for example, it is possible to efficiently set the reference authority for a person (concurrent person) who is in the position of both the construction business and the manufacturing business.

  Continuing on, the record creation unit 102g and the lowest layer data acquisition unit 102h, based on only the upper two rows of records surrounded by the thick frame in the layered object expansion information 106b of FIG. It is also possible to create hierarchical object expansion information that has been expanded to → 1 → 0 and the end. The specific creation method is the same as the processing performed by the record creation unit 102a3 and the lowest layer data acquisition unit 102a4 in [3-1], and thus the description thereof is omitted. Note that, in the hierarchical object expansion information 106b in FIG. 37, the records in the lower two lines that are not surrounded by a thick frame are not expanded. That is, the expansion information is created only for the records in the upper two rows that UserB has the reference authority, whereas the expansion information is not created for the records in the lower two rows that UserB does not have the reference authority.

  Further, subsequently, the extraction unit 102i may extract the numerical value by referring to the aggregation target data based on the hierarchical object development information that has been developed to the end, and the aggregation unit 102j You may total the extracted numerical value. The specific processing method is the same as the processing performed by the extraction unit 102b and the aggregation unit 102c in [3-1], and thus the description thereof will be 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 virtual organization and virtual segment). If it is desired to perform, the processing of this item [3-2] can be performed for each individual 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 to 4 below.
1. By setting the authority for the management number/hierarchy level/node identification code of the hierarchical object, it is possible to flexibly set the viewable data range.
2. Since one user can belong to a plurality of user groups, it is easy to make settings for concurrent use.
3. By performing the processing procedure according to the following flow of a to c, it becomes possible to obtain all the higher-level nodes to be aggregated for the lower-level nodes having the reference authority.
a. Enumerate all terminal nodes belonging to the hierarchy level and node ID code for which authority has been set.
b. The upper layered object expansion data is expanded only from the listed hierarchy level and node identification code.
c. Aggregate the linking information that matches the hierarchical object expansion data.
4. Even if it has multiple analysis axes, it can be easily expanded.

[3-3. Internal transaction determination processing]
Next, the internal transaction determination process will be described in detail mainly with reference to FIGS. 46 to 66. In this item [3-3], the following flow is itemized and explained. First, the procedure for creating the totaling 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 with reference to FIGS. 50 to 56. Then, the internal transaction determination process for the virtual segment will be described mainly with reference to FIGS. 57 to 62. Finally, internal transaction determination processing using the two axes of virtual organization and virtual segment will be described with reference to FIGS. 63 to 64. The process performed in this item [3-3] is a process in which (2) of [3-1] is further subdivided.

(1) Creation of aggregation target data The aggregation target data 106n is created based on the aggregation target original data 106m in which the partner attribute information in the aggregation target data 106n is initialized without setting.

  The aggregation target creation unit 102o refers to the aggregation target source data 106m and refers to the subject lowest layer identification data, the subject code and the subject lowest layer identification data and the subject that are included in the supplier identification pattern setting information 106l. The code and the supplier code are extracted, and the opponent lowest layer identification data included in the supplier identification pattern setting information 106l, which is associated with the extracted subject lowest layer identification data, the subject code and the supplier code, is the aggregation target source. The addition target data 106n is created by adding to the data 106m.

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 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 place code, a department code or an analysis code.
1. As for the determination of the company attribute 1, if the company attribute 1 is a required item, the company attribute 1 of the aggregation target data 106m=the company attribute 1 of the supplier identification pattern setting information 106l is searched for, and the company attribute 1 is arbitrary. In the case of the 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=company attribute 1 of the supplier specific pattern setting information 106l Do a matching search.
2. Regarding the determination of the company attribute 2, if the company attribute 2 is a required item, a search for matching the company attribute 2 of the aggregation source data 106m=company attribute 2 of the supplier identification pattern setting information 106l is performed, and the company attribute 2 is optional. In the case of an 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 original data 106m=the company attribute 2 of the supplier specific pattern setting information 106l. Do a matching search.
3. Then, hereinafter, the evaluation is executed by 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 executed).

  Specifically, when the content of the supplier identification pattern setting information 106l is as shown in FIG. 44 and the content of the aggregation target original data 106m is as shown in FIG. 46, how is the aggregation target creation unit 102o how? It will be described whether to create the aggregation target data 106n.

  First, the aggregation target creation unit 102o starts from the record with the smallest determination order (the record from the top row) of the two records including the company code 100 in the supplier identification pattern setting information 106l shown in FIG. The following extraction processing and additional processing are performed in order.

(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 customer specific pattern setting information 106l, the subject lowest layer identification data is company code 100, office code Tokyo, 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 original data 106m in FIG. 47, the record including this combination (company code 100, office code Tokyo, department code Eigyo, analysis code Buppan, subject code 1000: sales and supplier code T1001) is , Two records (indicated by arrows) in the first and second rows from the top. Therefore, the aggregation target creation unit 102o is included in the two records of the aggregation target original data 106m (company code 100, business office code Tokyo, department code Eigyo, analysis code Buppan, subject code 1000: sales and supplier code). T1001) is extracted.

(Additional processing)
The additional processing will be described. In the customer specific pattern setting information 106l shown in FIG. 47, the extracted partner (company code 100, business office code Tokyo, department code Eigyo, analysis code Buppan, subject code 1000: sales and customer code T1001) is linked to 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, the aggregation target creation unit 102o adds the combination to the records (indicated by arrows) in the first and second rows from the top of the aggregation target original data 106m, as shown in FIG.

  Next, as shown in FIG. 48, the aggregation target creation unit 102o, in the supplier specific pattern setting information 106l, the record whose determination order is the second youngest among the two records including the company code 100 (2 from the top). The extraction process and the addition process are similarly performed for the record of the line). As a result, as shown in FIG. 48, the counting target creation unit 102o sets (counterpart company code 300, partner business place code Osaka, partner department code Hanbai1 and partner analysis code Kouri) to 4 Add to the record in the line (indicated by the arrow).

  Then, as shown in FIG. 49, the aggregation target creation unit 102o records the youngest determination order (the third line from the top) in the two records including the company code 200 in the supplier identification pattern setting information 106l. For the record), the extraction process and the addition process are similarly performed. As a result, as shown in FIG. 49, the aggregation target creation unit 102o sets (counterpart company code 100, partner business site code Tokyo, partner department code Eigyo, and partner analysis code Buppan) from the top of the aggregation target source data 106m. Add to the record in the line (indicated by the arrow).

  Further, the aggregation target creation unit 102o similarly performs the extraction process and the addition process on the records in the fourth to sixth rows from the top of the customer identification pattern setting information 106l, and finally, the aggregation target shown in FIG. Data 106n is created.

  In this way, the aggregation target creation unit 102o performs the extraction process and the addition process up to the last line of the supplier identification pattern setting information 106l, so that all the partner codes determined to be intra-group transactions are filled. On the other hand, the transactions specified by the banks that remain unset are transactions with external general companies that are not intra-group transactions.

(2) Internal Transaction Determination Processing for Virtual Organization Next, internal transaction determination processing for a virtual organization will be described. In this item, in the hierarchical structure shown in FIG. 42, the internal transaction determination processing in the middle layer (that is, it is determined that the company 100 Tokyo Sales and Company 200 Manufacturing 1 department belonging to the Kanto area are internal transactions, while How to realize the internal transaction of the company 300 Osaka sales 1 copy and the company 200 manufacture 2 copies belonging to the Kansai area) will be described.

  In this item, the totaling 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. The specific method of creating is the same as (1-1) to (1-4) of [3-1], and thus the description is omitted. FIG. 51 shows the hierarchical object extraction information 106c created by the target extraction creating 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 totaling process can be performed based on the result of the determination process. Therefore, hereinafter, the four processes will be described item by item in this order.

(2-1) Subject acquisition process The subject acquisition unit 102k refers to the layered object extraction information 106c including the management number, the hierarchy level, the node identification code, and the lowest layer identification data, and identifies the subject lowest layer identification data. The management number, hierarchy level, and 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 totaling 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 layered object extraction information 106c shown in FIG. 51, the combination (management number, hierarchy level and node identification code) associated with this combination is included in the record with A attached (organization chart (4), 1, 31000). Therefore, the subject acquisition unit 102k obtains (organization chart (4), 1, 31000) as information associated with the subject lowest layer identification data and the like included in the details of the first to fifth lines from the top of FIG. To do. In the same manner, the subject acquisition unit 102k associates information with the subject lowest layer identification data (company code 200, establishment code Tokyo, and department code Seizou1) included in the details of the sixth to seventh lines in FIG. 51 (organization chart (4), 1 and 31000) included in the record to which B is added 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 record (organization chart (4), 1, 32000) included in the record with D in FIG. 51 is acquired, and from the top of FIG. 52. 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, it is included in the record with C in FIG. 51 (organization chart (4), 1, 32000) is acquired. In addition, in the records with B and D in FIG. 51, the office code is <ALL>, which means that any information may be entered. Specifically, in this example, In the case, it means Tokyo or Osaka.

  Here, in the column of "own organization" of the organization matching result of FIG. 52, the correspondence relationship between each specification of FIG. 52 and each record of FIG. 51 is shown by A to D, but this notation is for convenience of description. Since it is attached, the aggregation target data 106n may not include the organization matching result.

  In this way, the subject acquisition unit 102k can perform matching with the own organization information of the aggregation target data 106n based on the hierarchical 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, and identifies the subject 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 specifications of the sixth and tenth lines from the top of the aggregation target data 106n illustrated in FIG. 53, the partner lowest layer identification data is (partner company code 100, partner business office code Tokyo and partner department code). Eigyo) is a combination. Here, referring to the layered object extraction information 106c shown in FIG. 51, the combination (management number, hierarchy level and node identification code) associated with this combination is included in the record with A attached (organization chart (4), 1, 31000). Therefore, the partner acquisition unit 102l uses (organization chart (4), 1, 31000) as the information associated with the partner lowest layer identification data included in the details of the first and sixth lines from the top of FIG. get. In the same manner, the partner acquisition unit 102l uses the partner lowest layer identification data (partner company code 200, partner business 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 linked, the information (organization chart (4), 1, 31000) included in the record with B in FIG. 51 is acquired, and the partner maximum included in the details of the fourth and eighth lines from the top of FIG. The information associated with the lower layer identification data (the partner company code 300, the partner office code Osaka and the partner department code Hanbai1) is included in the record with C in FIG. 51 (organization chart (4), 1, 32000). 51 as the information to be acquired and associated with the partner lowest layer identification data (partner company code 200, partner business office code Osaka and partner department code Seizou2) included in the description on the 12th line from the top of FIG. 53. Acquire (organization chart (4), 1, 32000) included in the attached record.

  Here, in the column of “partner organization” of the organization matching result of FIG. 53, the correspondence relationships between the details of FIG. 53 and the records of FIG. 51 are shown by A to D, but this notation is for convenience of explanation. Since it is attached, 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 hierarchical object extraction information 106c, and obtain a matching result regarding the partner organization.

(2-3) Judgment Processing The judgment unit 102m has the same management number, hierarchy level, and node identification code acquired by the subject acquisition unit 102k and the management number, hierarchy level, and node identification code acquired by the partner acquisition unit 102l. In this case, the transaction between the subject of the subject and the subject of the other party is determined to be an internal transaction within the group.

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

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

  In the same manner, the determination unit 102m determines the transactions on the second line, the sixth line, the eighth line and the twelfth line from the top of FIG. 55 to be internal transactions, while the third line to the fifth line, The transactions on the 7th, 9th to 11th lines and the 13th line are determined to be 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 if the “hierarchical level” and the “node identification code” are the same in the hierarchical object extraction information 106c, and the external transaction otherwise. judge. It should be noted that the transaction specified by the row in which the partner organization has not been set is determined to be an external transaction.

  As described above, according to the information processing apparatus 100 according to the present embodiment, it is possible to automatically determine whether the transaction between the targets 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 internal transaction is the transaction between the company 100 Tokyo Sales and the company 200 Manufacturing 1 that belong to the Kanto area. Similarly, the process of determining that the transaction between the company 300 Osaka Sales 1st Department and the Company 200 Manufacturing 2nd Department that belong to the Kansai area is internal transaction). It may be a “layer” or a “lower layer”.

  In the case of the internal transaction determination process in the “upper layer”, when the layered object extraction information 106c is created, by inputting the layer level “0”, the management number, the layer level and the node identification code are changed to (organization chart (4 ), 0, 30000), it is possible to create the hierarchical object extraction information 106c composed of four records. Therefore, the subject acquisition unit 102k refers to the layered object extraction information 106c to obtain a combination of the management number, the layer level, and the node identification code, and the partner acquisition unit 102l refers to the layered object extraction information 106c to obtain. The combination of management number, hierarchy level and node identification code is always the same. Therefore, all the items corresponding to the supplier specific pattern setting information 106l in the total data 106n (the details of the first to second lines from the top of the total data 106n, the details of the fourth line, the details of the sixth line). , The details of the 8th line, the details of the 10th line and the details of the 12th line) are internal transactions. On the other hand, the details that do not correspond to the supplier specific pattern setting information 106l (the details of the third line from the top of the total data 106n, the details of the fifth line, the details of the seventh line, the details of the ninth line, the details of the eleventh line). 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 layer”, when the layered object extraction information 106c is created, by inputting the layer level “2”, the management number, the layer level and the node identification code become In (organization chart (4), 2,31100), (organization chart (4), 2,31200), (organization chart (4), 2,32100) and (organization chart (4), 2,32200) Hierarchical object extraction information 106c including four records can be created. Therefore, the subject acquisition unit 102k refers to the layered object extraction information 106c to obtain a combination of the management number, the layer level, and the node identification code, and the partner acquisition unit 102l refers to the layered object extraction information 106c to obtain. Since the combination of the management number, the hierarchy level, and the node identification code is always different, the transactions in all the items of the aggregation target data 106n are external transactions.

  FIG. 65 shows an image diagram of the internal transaction determination processing in each of the “upper layer”, the “middle layer” and the “lower layer”. As shown in FIG. 65, the amount of internal transaction increases as the internal transaction determination processing is performed in a higher hierarchy. This is because the internal transaction determination process 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, if extracted, the amount of data determined as internal transactions will increase. As a result, when the nodes of the hierarchy level to be extracted are virtually regarded as one company and one segment, it is possible to judge the transaction between the inner nodes as an internal transaction and cancel them.

  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 by combining the content described in [3-2] and the content described in this item (2). It is possible to perform the internal transaction determination process). FIG. 66 shows an image diagram of this internal transaction determination processing. As shown in FIG. 66, by incorporating the content of [3-2], it becomes possible to aggregate the internal transactions and the external transactions by distinguishing them in the company for which the user has reference authority. Companies within the group that do not have reference authority to the user (manufacturing business group and companies 300 and 400 belonging thereto in FIG. 66) are regarded by the user as the same “external” transaction as other business partners outside the group. Be done.

  Further, according to the information processing apparatus 100 according to the present embodiment, for example, the content and number of items of the subject lowest layer identification data and the partner lowest layer identification data can be arbitrarily set, so that flexible internal transaction determination processing can be performed. It can be carried out. Specifically, conventionally, only internal transaction determination processing (for example, processing that determines that a transaction between the company 100 and the company 200 is an internal transaction) can be performed in a general unit such as a company unit or a segment unit. On the other hand, according to the information processing apparatus 100 according to the present embodiment, if three codes of the company code, the office code and the department code are set as the company information and the partner information, the internal transaction with a fine granularity can be performed. A determination process (for example, a process of determining that a transaction between “Company 100, Tokyo Head Office, Sales Department” and “Company 200, Osaka Head Office, Manufacturing 2 Department” is an internal transaction) can be performed.

  Here, in this item (2), the internal transaction determination process can be performed by the contents described in (2-1) to (2-3), but the aggregation unit 102n determines the result of the internal transaction determination process. The following (2-4) totaling process may be performed by 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 the same.

  Specifically, the same case means a combination of the management number, the hierarchy level and the node identification code acquired by the subject acquisition unit 102k and the combination of the management number, the hierarchy level and the node identification code acquired by the partner acquisition unit 102l. And are the same. In the case of the aggregation target data 106n in FIG. 55, when the details of the first, second, sixth, eighth, and twelfth lines from the top, which are internal and external determinations, are the same as above. Applicable The amounts associated with the entity lowest layer identification data (company code, establishment code and department code) included in these specifications are 10,000 yen, 15,000 yen and 50,000 yen, respectively, with reference to FIG. Yen, 70,000 yen and 110,000 yen. The aggregating unit 102n may aggregate all of these amounts and calculate 255,000 yen, but 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 total the amount of money for each.

  That is, in FIG. 55, the specifications 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 totaling unit 102n totals the amounts of money included in the details of the first and second lines as 10,000+15,000=25,000 yen. Similarly, in FIG. 55, the sixth line from the top has the combination of management number, hierarchy level, node identification code, and item code (organization chart (4), 1, 31000, purchase). The totaling unit 102n totals the amount of money included in the details of the sixth row as 50,000 yen. Similarly, in FIG. 55, the description on the eighth line from the top is the combination of the management number, hierarchy level, node identification code, and item code (organization chart (4), 1, 32000, purchase). The totaling unit 102n totals the amount of money included in the details of the eighth row to 70,000 yen. Similarly, in FIG. 55, the details on the 12th line from the top are the totalization because the management number, hierarchy level, node identification code and item code are a combination of (organization chart (4), 1, 32000, sales). The section 102n totalizes the amount of money included in the details of the 12th line to 110,000 yen. Thus, as shown in the aggregation result data 106o in FIG. 56, the aggregating unit 102n collects 25,000 yen, 50, 50% for each item having the same combination of management number, hierarchy level, node identification code, and subject code. Internal transaction amounts of 000 yen, 110,000 yen, and 70,000 yen can be calculated.

  In addition, the summation unit 102n may also sum the amount 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 items whose internal/external determination is external. As a result, as shown in the aggregation result data 106o of FIG. 56, the aggregating unit 102n makes 20,000 yen and 130,000 yen for each item having the same combination of the management number, the hierarchy level, the node identification code, and the subject code. External transaction amounts of Yen, 310,000 Yen and 80,000 Yen can be calculated.

  Then, the totaling unit 102n determines the management number, the hierarchy level, the node identification code, and the item code for both the internal and external details of the internal/external determination (that is, for all the details regardless of the internal/external determination result). The amounts may be aggregated for each item having the same combination of. As a result, the totaling unit 102n can calculate the total sum of 45,000 yen, 180,000 yen, 420,000 yen, and 150,000 yen, as shown in the totalization result data 106o in 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 only in the following items, and the process itself is the same as that in (2), so detailed description will be omitted. First, the lowest layer identification data included in the layered object extraction information 106c is not the "company code, establishment code and department code" but the "analysis code" as shown in FIG. This is because the hierarchical object extraction information 106c is created based on the hierarchical object management information 106a (including the "analysis code") shown in FIG. 41 and the input pattern (2) shown in FIG. In addition, in the aggregation target data 106o, the item used for matching regarding the own organization is not the "company code, office code and department code", but the "analysis code" as shown in FIG. Then, in the aggregation target data 106o, the item used for matching regarding the partner organization is not the "partner company code, the partner office code and the partner department code", but the "partner analysis code" as shown in FIG. As described above, by using the “analysis code” included in the layered object extraction information 106c, the “analysis code” and the “partner analysis code” included in the aggregation target data 106o, the same processing as (2) is performed. It is possible to perform the internal transaction determination process and the total based on the result. 57 to 61 show the contents of the internal transaction determination processing, and FIG. 62 shows the result of the aggregation.

  By the processing in this item (3), the sales department of the Tokyo head office of the company 100 that sells goods (real segment) belonging to the hierarchy of the sales business (virtual segment) in the hierarchical structure shown in FIG. It is possible to determine that the transaction between the sales department of the Osaka branch of the company 300 that performs retail (actual segment) belonging to the (segment) level 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 like

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

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

  In the table of FIG. 63, when the “internal transaction amount (within a segment)” is calculated, there is no detail whose internal/external determination is “internal” and segment internal/external determination is “internal”. do not do.

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

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

[3-4. Data conversion process]
Next, the data conversion process will be described in detail mainly with reference to FIGS. 69 to 74. 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 for which the conversion destination attribute information in the conversion completion data 106s is not set. It is created based on the data 106r (shown in FIG. 69) by the following procedure.

  The extraction unit 102q refers to the conversion target data 106r including the conversion source data to extract 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 the 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 the company order and the determination order is ascending order. In addition, as a condition for matching with the conversion target data 106r, the evaluation is performed according to the following procedures 1 to 3. In the following description, the conversion source attribute means a supplier code, a subject code, a business place 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 a required item, the conversion source attribute 1 of the conversion target data 106r=the conversion source attribute 1 of the conversion pattern setting information 106q is searched for, and the conversion source attribute 1 is searched. Is an arbitrary item, the conversion source attribute 1 of the conversion pattern setting information 106q is a reserved word <ALL>, or the conversion source attribute 1 of the conversion target data 106r is 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 a required item, 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 for, and the conversion source attribute 2 is searched. Is an arbitrary item, the conversion source attribute 2 of the conversion pattern setting information 106q is a reserved word <ALL>, or the conversion source attribute 2 of the conversion target data 106r is the conversion source attribute 2 of the conversion pattern setting information 106q. Search for a match.
3. Then, hereinafter, the evaluation is executed by the number of conversion source attributes used by the system (that is, if the conversion source attributes 3 and later exist, the same processing as the conversion source attributes 1 and 2 is executed).

  Specifically, when the contents of the conversion pattern setting information 106q are as shown in FIG. 68 and the contents of the conversion target data 106r are as shown in FIG. 69, how the extraction unit 102q and the conversion unit 102r convert It will be described whether the conversion source data in the data 106r is converted to generate the conversion completion data 106s.

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

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

(Conversion process)
Next, the 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, subject code 1000: sales, office 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, is the conversion source code (company code 100, transaction) acquired by the extraction unit 102q. Destination 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, the extraction unit 102q and the conversion unit 102r, as shown in FIG. 71, in the conversion pattern setting information 106q, in the conversion source data included in the three records of the company code 100, the second youngest determination order and the string. The extraction processing and the conversion processing are similarly performed on the conversion source data to be attached (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 (indicated by the fourth and fifth lines (indicated by arrows) from the top of the conversion target data 106r in FIG. 71. G_Hanbai).

  Furthermore, as shown in FIG. 72, the extraction unit 102q and the conversion unit 102r associate the conversion pattern setting information 106q with the third youngest judgment order in the conversion source data included in the three records of the company code 100. Similarly, extraction processing and conversion processing are performed on the conversion source data to be attached (that is, the conversion source data included in the record in the third 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 conversion destination data (G_Sonota), as shown in the second line (indicated by an arrow) from the top of FIG.

  Further, 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 4th to 6th rows from the top of the conversion pattern setting information 106q, and finally, 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 like 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, managing the association with the code of each company complicates the setting. Therefore, by the processing of this item [3-4], it is possible to easily set the analysis axis at various cuts by once converting to the common segment code and then assigning the common segment code to the virtual segment. .

  Assigning a common segment code to a virtual segment specifically means the following processing, for example. As shown in FIG. 74, a common segment code of “system business” is set for the SI business and PKG development of the company A and the development business department of the company B, while “common” is set for the support business department of the company B. Set a common segment code for "support business". Then, 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 this is the case, it is possible to analyze the business focusing on the point of view of the business content.

  As described above, according to the information processing apparatus 100 according to the present embodiment, it is possible to convert a combination of a plurality of data (conversion source data) into common data (conversion destination data). Thereby, for example, as described in the preceding paragraph, each target can be classified into the common segment code “system development business” and “support business”, and the business analysis can be performed focusing on the business content. In addition, for example, the transactions between the three objects of “SI business of Company A and PKG development and development business department of Company B” belonging to the common segment code “System development business” are determined to be internal transactions and eliminated. Therefore, the accounting treatment that the transactions between the three targets that belong to the common segment code “System Development Business” and the support division of Company B that belongs to the common segment code “Support Business” are judged as external transactions and are not offset You can also do

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

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

  According to the information processing apparatus 100 according to the present embodiment, it is possible to simulate reorganization of a group company. Specifically, when the information processing apparatus 100 according to the present embodiment handles a corporate group, when the corporate reorganization by absorption-type merger of companies within the group or acquisition of an external company by M&A (merger/acquisition) 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 not changed (organization before change (2) in FIG. 75). Can be compared with the post-reorganization organization (reorganized organization (2)′ in FIG. 75). In FIG. 75, the company 2 is a company belonging to the group core 1 before the organizational restructuring, but is a company belonging to the group core 2 after the organizational restructuring.

  Further, according to the information processing apparatus 100 according to the present embodiment, it is possible to perform the business analysis by totaling the amount of money on the three axes of organization×segment×course by combining the functions of the organization information and the segment information. Specifically, according to the information processing apparatus 100 according to the present embodiment, as shown in FIG. 76, information about a product/brand is arranged on the vertical axis and information about a store is arranged on the horizontal axis, and the data on the income and expenditure is the income and expenditure. Multiple data can be created by visualizing with. By creating such multi-dimensional data, it is possible to grasp the current state of the income and expenditure by brand by store. As a result, a sales strategy for each brand can be established for each store.

[4. Other Embodiments]
The present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims other than the above-described embodiments.

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

  Unless otherwise specified, processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions of each processing, screen examples, and database configurations shown in this specification and the drawings are excluded. Can be changed arbitrarily.

  Further, regarding the information processing apparatus 100, the illustrated constituent elements are functionally conceptual and do not necessarily have to be physically configured as illustrated.

  For example, the processing functions of the information processing apparatus 100, particularly the respective processing functions performed by the control unit 102, are implemented in whole or in part by a CPU and a program interpreted and executed by the CPU. Alternatively, the hardware may be realized by wired logic. The program is recorded on a non-transitory computer-readable recording medium that includes programmed instructions for causing the information processing apparatus to execute the processing described in the present embodiment, and the information processing apparatus may be used as necessary. Mechanically read to 100. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into the RAM, and constitutes a control unit in cooperation with the CPU.

  Further, this computer program may be stored in an application program server connected to the information processing apparatus 100 via an arbitrary network, and it is possible to download all or part of the computer program as necessary. is there.

  Further, the program for executing the processing described in this embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the “recording medium” includes a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (registered). (Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), etc. (registered trademark), MO (Magneto-Optical disk), etc. It shall include any "portable physical medium". Therefore, a recording medium storing a program for executing the processing or the processing method described in the present specification also constitutes the present invention.

  The "program" is a data processing method described in any 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 it achieves its function in cooperation with a plurality of modules or libraries that are distributed and configured, or with a separate program represented by an OS. Including things. Note that known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiments, and the installation procedure after reading.

  Various databases and the like stored in the storage unit 106 are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and storage means such as optical disks, and are used for various processes and website provision. Stores programs, tables, databases, files for web pages, 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 any peripheral device is connected. Further, the information processing apparatus 100 may be realized by mounting software (including a program, data, or the like) for realizing the processing described in the present embodiment on the apparatus.

  Further, the specific form of the dispersion/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 arranged in arbitrary units according to various additions or functional loads. It can be distributed and integrated. That is, the above-described embodiments may be implemented in any combination, or the embodiments may be selectively implemented.

  INDUSTRIAL APPLICABILITY The present invention is useful in all industries, but is extremely useful particularly in the fields of management accounting, consolidated accounting, group management accounting and the like.

100 Information processing device
102 control unit
102a acquisition unit
102a1 record acquisition unit
102a2 lowest layer record acquisition unit
102a3 record creation section
102a4 lowest layer data acquisition unit
102b extractor
102c counting section
102d First acquisition unit
102d1 group identification data acquisition unit
102d2 layer identification data acquisition unit
102d3 record acquisition unit
102d4 repeat unit
102e Second acquisition unit
102f Development data creation unit
102g record creation section
102h lowest layer data acquisition unit
102i extractor
102j Counting unit
102k Subject acquisition unit
102l Opponent acquisition section
102m judgment section
102n counting section
102o Aggregation target creation unit
102p target extraction creation unit
102q extractor
102r converter
104 Communication interface section
106 storage unit
106a Hierarchical object management information
106b Hierarchical object expansion information
106c Hierarchical object extraction information
106d Data to be aggregated
106e Total result data
106f Aggregation key information data
106g User group affiliation information
106h authority setting information
106i authority extraction information
106j Hierarchical object security development information
106k Supplier specific item setting information
106l Business partner specific pattern setting information
106m Source data for aggregation
106n Data to be aggregated
106o Total result data
106p conversion item setting information
106q conversion pattern setting information
106r Conversion target data
106s conversion completed data
108 Input/output interface section
112 Input device
114 output device 200 server 300 network

Claims (8)

A data acquisition device including a control unit,
The control unit is
Object management data including a record having information about a plurality of dependent objects,
The record before SL and a dependent destination object identification data for said target object identification data for identifying to identify a previous target belonging to the target,
Non the subordinate record is a record with information about the non-target dependent subject the subject belonging to the subject a the subject does not exist, further comprising a non-be dependent identification data for identifying the non-target dependent subject ,
Referring to the target management data,
Non -dependent record acquisition means for acquiring the non-dependent record ,
The records that contain the same Target identification data and which depends on the object identification data contained in the non-non-target dependent records acquired in the subordinate record acquiring means acquires with reference to the target management data, to the acquired record A record creating means for creating a record to which non-dependent identification data included in the non- dependent record acquired by the non -dependent record acquiring means is added,
Above with reference to records created by the non-non-acquired by the subordinate record acquiring means to be dependent records and the record creation unit, by acquiring the record including the target identification data input, the non-included in the record Non-dependent data acquisition means for acquiring dependent identification data ,
It is provided with,
And a data acquisition device. The control unit is
Further comprising an extracting means for extracting a numerical value associated with the non-dependent identification data acquired by the non-dependent data acquiring means, with reference to the aggregation target data including the non-dependent identification data and the numerical value.
The data acquisition device according to claim 1, wherein: The control unit is
Further comprising an aggregating unit that aggregates the numerical values extracted by the extracting unit,
The data acquisition device according to claim 2. The counting means is
The target identification data is the same by referring to the aggregate key data including a plurality of specifications including the numerical value extracted by the extraction unit and the target identification data included in the record acquired by the non-dependent data acquisition unit. Specify the details and aggregate the numerical values included in the specified details,
The data acquisition device according to claim 3, wherein The counting means is
When there is a description having the same specification identification data with reference to aggregate key data including a plurality of specifications including numerical values extracted by the extraction means and specification identification data, only one of the specifications is left. And updating the other key details by deleting the other details, and totaling the numerical values included in the details included in the updated key data,
The data acquisition device according to claim 3 or 4, characterized in that. The target management data is
The target of the lowest layer and the target of the upper layer includes a record having information about the target of each layer from the highest layer to the lowest layer in the hierarchical structure formed by forming a layer
The record includes the target identification data and upper target identification data for identifying a target in a layer one level higher than the target,
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,
The non-dependent record acquisition means refers to the target management data to acquire the lowest layer record,
The record creating unit acquires a record including the same target identification data as the upper target identification data included in the lowest layer record acquired by the non-dependent record acquisition unit by referring to the target management data, and acquires the record. A record to which the lowest layer identification data included in the lowest layer record acquired by the non-dependent record acquisition means is added,
The non-dependent data acquisition unit acquires the record including the input target identification data by referring to the lowest layer record acquired by the non-dependent record acquisition unit and the record created by the record creation unit. By acquiring the lowest layer identification data included in the record,
The data acquisition device according to claim 1, wherein the data acquisition device is a data acquisition device. A data acquisition method executed by an information processing device including a control unit,
Executed by the control unit,
Object management data including a record having information about a plurality of dependent objects,
The record includes target identification data for identifying the target and dependent destination target identification data for identifying a target to which the target belongs,
The non-dependent record, which is a record having information about the non-dependent subject that does not have the target that belongs to the target, further includes non-dependent identification data for identifying the non-dependent subject. ,
Referring to the target management data,
A non-dependent record acquisition step of acquiring the non-dependent record,
A record including the same target identification data as the dependent destination target identification data included in the non-dependent record acquired in the non-dependent record acquisition step is acquired by referring to the target management data, and the acquired record is A record creation step for creating a record to which the non-dependent record data included in the non-dependent record acquired in the non-dependent record acquisition step is added,
By referring to the non-dependent record acquired in the non-dependent record acquisition step and the record created in the record creation step to acquire the record including the input target identification data, the non-dependent record included in the record is acquired. A non-dependent data acquisition step of acquiring dependent identification data,
Including,
Data acquisition method characterized by. A data acquisition program to be executed by an information processing device including a control unit,
In order for the control unit to execute,
Object management data including a record having information about a plurality of dependent objects,
The record includes target identification data for identifying the target and dependent destination target identification data for identifying a target to which the target belongs,
The non-dependent record, which is a record having information about the non-dependent subject that does not have the target that belongs to the target, further includes non-dependent identification data for identifying the non-dependent subject. ,
Referring to the target management data,
A non-dependent record acquisition step of acquiring the non-dependent record,
A record including the same target identification data as the dependent destination target identification data included in the non-dependent record acquired in the non-dependent record acquisition step is acquired by referring to the target management data, and the acquired record has the A record creation step for creating a record to which the non-dependent record data included in the non-dependent record acquired in the non-dependent record acquisition step is added,
By referring to the non-dependent record acquired in the non-dependent record acquisition step and the record created in the record creation step to acquire the record including the input target identification data, the non-dependent record included in the record is acquired. A non-dependent data acquisition step of acquiring dependent identification data,
Including,
Data acquisition program characterized by.

Images