JP2019117651A - Internal transaction determination device, internal transaction determination method and internal transaction determination program - Google Patents

Abstract

To provide an internal transaction determination device, an internal transaction determination method and an internal transaction determination program which can automatically determine whether a transaction between objects is an internal transaction in a group or not.SOLUTION: In this embodiment, the internal transaction determination method comprises: a step (1) of referring to object extraction data including hierarchical structure identification data, hierarchy identification data, object identification data and lowest hierarchy identification data to acquire hierarchical structure identification data, hierarchy identification data and object identification data which are associated with agent lowest hierarchy identification data for identifying an agent object, which is included in aggregation target data including the agent lowest hierarchy identification data and partner lowest hierarchy identification data for identifying a partner object: a step (2) of referring to the object extraction data to acquire hierarchical structure identification data, hierarchy identification data and object identification data which are associated with the partner lowest hierarchy identification data included in the aggregation target data; and a step (3) of determining a transaction between the agent object and the partner object as an internal transaction if the data acquired in the step (1) and the data acquired in the step (2) are identical.SELECTED DRAWING: Figure 55

Description

  The present invention relates to an internal transaction determination device, an internal transaction determination method, and an internal transaction determination program.

  Patent Document 1 discloses an accounting system, an accounting method, and an accounting program, in particular, an accounting system having a management consolidation function, an accounting method, and an accounting program (see, for example, paragraph 0001).

JP, 2012-181731, A

  In the field such as management accounting, when the objects such as companies have a hierarchical structure conventionally, when the transactions between the objects are transactions in the same layer, the transactions between the objects are performed in a group. It was difficult to automatically determine that it was an internal transaction.

  For example, when a company consists of a company in the Kanto area and a company in the Kansai area, and a company in the Kanto area consists of companies 1 and 2 and a company in the Kansai area consists of only the company 3, the same Kanto area is used. It is determined that the transaction between company 1 and company 2 belonging to the hierarchy is an internal transaction within the group, while the transaction between company 1 and company 3 belonging to different hierarchies from each other is outside the group It was difficult to judge that it was an external transaction of

  This invention is made in view of the above, Comprising: The internal transaction determination apparatus which can be determined automatically whether the transaction between object is an internal transaction inside a group, an internal transaction determination method, and the inside Provide a transaction determination program.

  In order to solve the problems described above and achieve the object, an internal transaction determination device according to the present invention is an internal transaction determination device including a control unit, and the control unit is a target of the lowest layer and an upper layer. Hierarchical structure identification data for identifying a hierarchical structure formed by forming a hierarchy with objects; layer identification data for identifying each layer in the hierarchical structure; object identification data for identifying the objects; Subject lowest layer identification that is the lowest layer identification data for identifying the subject subject that is the subject of the transaction with reference to the target extraction data including the lowest layer identification data for identifying the subject of the lowest layer Hierarchical structure identification associated with the lowermost layer identification data included in the aggregation target data including the data and the lowermost layer identification data that is the lowest layer identification data for identifying the counterpart object that is the transaction partner Hierarchical structure identification data associated with data, hierarchical identification data and subject identification data, and hierarchical identification data associated with the lowest other-layer identification data included in the aggregation target data with reference to the subject extraction data And hierarchical structure identification data acquired by the subject acquisition means, hierarchical identification data and target identification data, hierarchical structure identification data acquired by the remote acquisition means, hierarchical identification data and object identification And determining means for determining a transaction between the subject object and the other object as an internal transaction within a group when the data is the same as the data.

  Further, in the internal transaction determination device according to the present invention, the aggregation target data further includes a numerical value, and the control unit is configured to associate the lowermost layer identification data contained in the aggregation target data when the same is the same. The information processing apparatus is further characterized by further comprising aggregation means for aggregating attached numerical values.

  Further, in the internal transaction determination apparatus according to the present invention, the control unit further includes tallying object creating means for creating the tallying object data, and the tallying object creating means is configured to identify the lowermost layer identification data and the transaction. The lowermost layer identification data and the item identification data with reference to the aggregation target source data including the item identification data for identifying the accruing items of the subject and the supplier identification data for identifying the supplier of the subject object. Subject lowest layer identification data, item identification data and vendor identification data included in transaction pattern setting data including customer identification data and counterpart lowest layer identification data Same subject lowest layer identification data, item identification data and transaction In the transaction pattern setting data, the first identification data is extracted, and the extracted lowermost layer identification data, the item identification data, and the customer identification data are linked. The Murrell opponent lowest layer identification data, by adding to the aggregate target source data, creating the aggregate subject data, and features.

  Further, in the internal transaction determination device according to the present invention, the control unit further includes target extraction creating means for creating the target extraction data, and in each hierarchy from the highest layer to the lowest layer in the hierarchical structure. In the object management data including a record having information about the object, the record is an upper layer for identifying a layer higher than the hierarchical structure identification data, the layer identification data, the object identification data, and the layers. A lowest layer record, which is a record including identification data and high-level object identification data for identifying a target in a hierarchy one level above the above-mentioned objects, the lowest-layer record being information having information on the lowest layer The method further includes identification data, and the target extraction and creation unit refers to the target management data to acquire a record including the input hierarchical structure identification data. The lowermost layer record is acquired from the acquired record, and a record including upper layer identification data and upper layer identification data included in the acquired lowermost layer record and target identification data the same as the upper layer identification data is the target A record is created by adding the lowest layer identification data included in the obtained lowest layer record to the obtained record acquired with reference to management data, and the obtained lowest layer record and the created record The target extraction data is created by acquiring a record including the input layer identification data with reference to and making the acquired record the target extraction data.

  Further, in the internal transaction determination device according to the present invention, the target extraction and creation means may include a record including the same hierarchy identification data and object identification data as the upper hierarchy identification data and the upper object identification data included in the created record. Information on the object of the highest layer, to create a record obtained by referring to the object management data and adding the lowest layer identification data included in the obtained lowest layer record to the acquired record Repeating until the lowest layer identification data included in the obtained lowest layer record is added to the record having.

  Further, the internal transaction determination method according to the present invention is an internal transaction determination method executed by an information processing apparatus including a control unit, which is a target of the lowest layer and a target of the upper layer, which are executed by the control unit. Hierarchical structure identification data for identifying a hierarchical structure formed by forming a hierarchy, hierarchical identification data for identifying each hierarchical layer in the hierarchical structure, target identification data for identifying the object, and the lowest Subject lowermost layer identification data, which is the lowest layer identification data for identifying a subject object that is the subject of a transaction, with reference to object extraction data including the lowest layer identification data for identifying a layer object Hierarchical structure identification data associated with the lowermost layer identification data included in the aggregation target data including the lowermost layer identification data that is the lowest layer identification data for identifying the counterpart object that is the transaction counterpart Hierarchical identification data associated with the lowermost layer identification data included in the aggregation target data with reference to the subject extraction step for acquiring data, layer identification data and object identification data, and the target extraction data And a partner acquisition step for acquiring target identification data, hierarchical structure identification data acquired in the subject acquisition step, hierarchical identification data and target identification data, hierarchical structure identification data acquired in the partner acquisition step, hierarchical identification data and object identification And determining, if the data is identical, a transaction between the subject object and the other object as an internal transaction within a group.

  Further, an internal transaction determination program according to the present invention is an internal transaction determination program to be executed by an information processing apparatus including a control unit, which is a target of the lowest layer and an upper layer to be executed by the control unit. Hierarchical structure identification data for identifying a hierarchical structure formed by forming a hierarchy with objects; layer identification data for identifying each layer in the hierarchical structure; object identification data for identifying the objects; Subject lowest layer identification that is the lowest layer identification data for identifying the subject subject that is the subject of the transaction with reference to the target extraction data including the lowest layer identification data for identifying the subject of the lowest layer Subject lowest layer identification data included in tallying object data including data and the lowest other layer identification data that is the lowest layer identification data for identifying the other party that is the transaction partner Hierarchical structure identification data, hierarchical identification data, and subject identification data acquiring target identification data, and the target extraction data with reference to the hierarchical structure associated with the lowest other-layer identification data included in the aggregation target data Identification data, hierarchy identification data and object identification data acquisition step, hierarchical structure identification data acquired in the subject acquisition step, hierarchy identification data and object identification data, hierarchical structure identification data acquired in the partner acquisition step, And determining the transaction between the subject object and the opposite object as an internal transaction within a group if the hierarchy identification data and the object identification data are the same. Do.

  According to the present invention, it is possible to automatically determine whether a transaction between objects is an internal transaction within a group.

FIG. 1 is a block diagram showing an example of the configuration of an information processing apparatus. FIG. 2 is a diagram showing an example of conventional setting of data at the time of data aggregation. FIG. 3 is a diagram showing an outline of hierarchical object management information. FIG. 4 is a diagram showing an example of data in hierarchical object management information. FIG. 5 is a diagram showing the organization chart (1). FIG. 6 is a diagram showing the organization chart (2). FIG. 7 is a diagram showing the organization chart (3). FIG. 8 is a diagram showing an example of a management number, a hierarchy level, and a node identification code input when performing data aggregation. FIG. 9 is a diagram showing a record including the input management number acquired by referring to the hierarchical object management information. FIG. 10 is a diagram showing a flow of acquiring a record having a hierarchy level of 2 with reference to the acquired record. FIG. 11 is a diagram showing a flow of acquiring a record having a hierarchy level of 1 with reference to hierarchical object management information based on the acquired record having a hierarchy level of 2. FIG. 12 is a diagram showing a flow of acquiring a record having a hierarchy level of 0 with reference to hierarchical object management information based on the acquired record having a hierarchy level of 1. FIG. 13 is a diagram showing a flow of acquiring a record including the input hierarchy level and the node identification code with reference to the acquired hierarchy level 2, 1, and 0 records. FIG. 14 is a diagram showing a flow of extracting the aggregation target value with reference to the aggregation target data based on the association code included in the acquired record. FIG. 15 is a diagram showing the tallying result of the extracted tallying target value (in the case where the double count is not removed). FIG. 16 is a diagram showing an example of the totalized key information data. FIG. 17 is a diagram showing an example of the aggregation result of the extracted aggregation target value (in the case of removing the double count). FIG. 18 is a diagram showing a conventional setting example of data when security management is performed. FIG. 19 shows an example of data in user information and user group information. FIG. 20 shows an example of data in user group affiliation information. FIG. 21 shows which user group each user belongs to. FIG. 22 shows an example of data in the authority setting information. FIG. 23 is a diagram showing the range of organizations that each user group can refer to. FIG. 24 is a diagram showing the range of organizations to which each user group can refer in the organization chart (1). FIG. 25 is a diagram showing the range of organizations to which each user group can refer in the organization chart (2). FIG. 26 is a diagram showing the range of organizations to which each user group can refer in the organization chart (3). FIG. 27 is a diagram showing an example of data in 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 user group affiliation information. FIG. 30 shows which user group each user belongs to. FIG. 31 is a diagram illustrating an example of a management number and a user ID which are input when performing data collection. FIG. 32 is a diagram showing a user group code acquired by referring to user group affiliation information based on the input user ID. FIG. 33 is a diagram showing a hierarchy level and a node identification code acquired with reference 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 with reference to 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 with reference to hierarchical object management information based on the acquired record. FIG. 36 is a diagram showing an example of data in hierarchical object security deployment information. FIG. 37 is a diagram showing a record acquired with reference to hierarchical object expansion information, based on hierarchical object security expansion information. FIG. 38 is a diagram showing a conventional setting example of data at the time of internal transaction determination. FIG. 39 is an image diagram of conventional internal transaction determination. FIG. 40 is a diagram showing an example of data in hierarchical object management information that manages the hierarchical structure of virtual organizations. FIG. 41 is a diagram of an example of data in hierarchical object management information that manages a hierarchical structure including virtual segments. FIG. 42 is a diagram showing an example of a hierarchical structure composed of both a virtual organization and a virtual segment. FIG. 43 is a diagram showing an outline of supplier specific item setting information. FIG. 44 is a diagram showing an example of data in supplier specific pattern setting information. FIG. 45 is a diagram showing the contents of a transaction defined by the data example in the supplier specific pattern setting information. FIG. 46 is a diagram illustrating an example of data in tallying source source data. FIG. 47 is a diagram showing a flow of updating the aggregation target source data based on the record in the first line of the supplier specific pattern setting information. FIG. 48 is a diagram showing a flow of updating the aggregation target source data based on the record in the second line of the supplier specific pattern setting information. FIG. 49 is a diagram showing a flow of creating tallying target data by updating tallying source original data based on the third and subsequent records of the supplier specific pattern setting information. FIG. 50 is a diagram showing an example of a management number, a hierarchy level and a node identification code which are input when the internal transaction determination is performed. FIG. 51 is a diagram of an example of data in hierarchical object extraction information on a virtual organization. FIG. 52 is a diagram showing the matching result between the company code etc. contained in the hierarchized object extraction information and the company code etc. of its own organization contained in the aggregation target data. FIG. 53 is a diagram showing the matching result between the company code etc. included in the hierarchical object extraction information and the other company code etc. of the other party organization included in the aggregation target data. FIG. 54 is a diagram showing a record in which the combination of the management number, the hierarchy level and the node identification code is the same in the hierarchical object extraction information. FIG. 55 is a diagram showing the result of the internal / external determination performed based on the matching result. FIG. 56 is a diagram showing an example of the aggregation result obtained by aggregating the numerical values included in the aggregation target data in consideration of the result of the internal / external determination. FIG. 57 is a diagram of an example of data in hierarchical object extraction information on a virtual segment. FIG. 58 is a diagram showing the matching result of the analysis code included in the layered object extraction information and the analysis code of the own segment included in the aggregation target data. FIG. 59 is a diagram showing the matching result of the analysis code included in the layered object extraction information and the other party analysis code of the other segment included in the aggregation target data. FIG. 60 is a diagram showing a record in which the combination of the management number, the hierarchy level and the node identification code is the same in the hierarchical object extraction information. FIG. 61 is a diagram showing the result of the inside / outside determination performed based on the matching result. FIG. 62 is a diagram showing an example of the aggregation result obtained by aggregating the numerical values included in the aggregation target data in consideration of the result of the determination of the inside and outside of the segment. FIG. 63 is a diagram showing the result of the internal / external determination and the result of the internal / external determination. FIG. 64 is a diagram showing an example of the aggregation result obtained by aggregating the numerical values included in the aggregation target data, in consideration of the result of the internal / external determination and the result of the internal / external determination. FIG. 65 is an image diagram of internal transaction determination according to the present embodiment. FIG. 66 is an image diagram of internal transaction determination according to the present embodiment in consideration of security management. FIG. 67 is a diagram showing an outline of conversion item setting information. FIG. 68 is a diagram showing an example of data in conversion pattern setting information. FIG. 69 is a diagram showing an example of data in conversion target data. FIG. 70 is a diagram showing a flow of converting conversion source data in conversion target data into conversion destination data based on the first line record of conversion pattern setting information. FIG. 71 is a diagram showing a flow of converting conversion source data in conversion target data into conversion destination data based on the record of the second line of the conversion pattern setting information. FIG. 72 is a diagram showing a flow of converting conversion source data in conversion target data into conversion destination data based on the third line record of 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 is completed. FIG. 74 is a diagram showing an example of a method of assigning common data (conversion destination data) to virtual segments. FIG. 75 is a diagram showing the hierarchical structure of the pre-reorganization organization and the hierarchical structure of the post-reorganization organization. FIG. 76 is a diagram showing an example of output of multiple data.

  Hereinafter, embodiments of an internal transaction determination device, an internal transaction determination method, and an internal transaction determination program according to the present invention will be described in detail based on the drawings. The present invention is not limited by the present embodiment.

[1. Overview]
In areas such as management accounting (especially consolidated accounting or group management accounting), it is necessary to determine the internal transactions of companies within the group and perform eliminations, but in the conventional method, only business partners in units of companies or segments Since it was not able to manage, there was a problem that the judgment and elimination of the internal transaction can not be correctly performed when performing the tabulation in units of establishments or divisions, which are units finer than the company. In addition, in the virtual organization structure in which the organization is hierarchical, when tallying from the end company through the group core company to the parent company, the range of offsetting internal transactions changes when going to the upper hierarchy, It was difficult to judge and eliminate internal transactions.

  Specifically, as shown in FIG. 38, when there are a journal entry of company (1) and a journal entry of company (2), customer code "T0001" included in the statement of company (1) is Even though it can be judged that the company within the group (2) is pointed out, the business office code, department code and segment code of the partner company are not managed, so it is accurately judged whether the transaction is an internal transaction or not It was difficult to do.

  That is, as shown in FIG. 39, when the counterparties of (company 100, Tokyo head office, sales department) are (company 200, Tokyo head office, sales department) and (company 200, Osaka branch office, sales department), From the perspective of the company 100, it is not possible to determine whether these two transactions are an internal transaction or an external transaction, since the business establishment and department of the company 200 on the side of the business partner are not known.

  Therefore, in the present embodiment, whether the transaction is a transaction (that is, an intra-group transaction) within an object (object) having a hierarchical structure, or an inter-object transaction (that is, an out-of-group transaction = group) Provides a method to determine whether the transaction is an inter-transaction) and to distinguish and aggregate the transactions. In the present embodiment, in the hierarchical object that groups data, it is determined which object is the transaction content of the transaction content, and if it is a transaction between lower objects belonging to the same object based on the object tree structure, within the group If it is a transaction, and a transaction with a subordinate object of another object, it is possible to determine it as an inter-group transaction and distinguish and aggregate.

  More specifically, it is possible to define a pattern that specifies the detailed information of the other party from the transaction information. That is, assuming a situation where it is possible to identify the pattern of the detailed information of the other party from multiple attributes such as the company's office, department or analysis code, it is possible to set the detailed information of the other company at any granularity. Further, in the hierarchical object structure, the internal transaction information can be determined each time according to the hierarchical level when aggregating from the lower hierarchy to the upper hierarchy.

  Thus, as an effect according to the present embodiment, for example, in the virtual organization or virtual segment structure used in the management accounting analysis, when tallying is performed in any hierarchy, the transactions under the own hierarchy are deducted as internal transactions. By aggregating transactions with other layers as inter-group transactions, it became possible to properly grasp the balance of group companies. The specific configuration and operation will be described below.

[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 apparatus 100. As shown in FIG.

  The information processing apparatus 100 is a commercially available desktop personal computer. The information processing apparatus 100 is not limited to a stationary information processing apparatus such as a desktop personal computer, and may be a portable personal computer such as a commercially available notebook personal computer, a PDA (Personal Digital Assistants), a smartphone, and a tablet personal computer. It may be an information processing apparatus.

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

  The communication interface unit 104 communicably 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 another device via a communication line. Here, the network 300 has a function of communicably connecting the information processing apparatus 100 and the server 200, and is, for example, the Internet, a local area network (LAN), or the like. Note that 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. For the output device 114, in addition to a monitor (including a home television), a speaker or a printer can be used. The input device 112 can be a keyboard, a mouse, a microphone, and a monitor that cooperates with the mouse to realize a pointing device function. Hereinafter, the output device 114 may be described as a monitor 114 as a display unit, and the input device 112 may be described as a keyboard 112 or a mouse 112.

  The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for giving instructions to a central processing unit (CPU) in cooperation with an operating system (OS) to perform various processes. As the storage unit 106, for example, a memory device such as a random access memory (RAM) or a read only memory (ROM), 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 includes, for example, hierarchical object management information 106a as target management data, hierarchical object expansion information 106b as target expansion data, hierarchical object extraction information 106c as target extraction data, and aggregation target data 106d. , Aggregation result data 106e, aggregation key information data 106f as aggregation key data, user group affiliation information 106g as user management data, authority setting information 106h as group management data, authority extraction information 106i, hierarchy Integrated object security deployment information 106j, supplier specific item setting information 106k, supplier specific pattern setting information 1061 as transaction pattern setting data, aggregation target original data 106m, aggregation target data 106n, aggregation result data 106 When comprises a converting item setting information 106p, a conversion pattern setting information 106q as converted pattern setting data, and the converted data 106r, a conversion completion data 106s, the.

  Further, in the present embodiment, the “object (object)” is, for example, a real organization (for example, a real company, a business place or a department, etc.) that is an existing organization, or a virtual organization (for example, a virtual organization). Real tissue layered or organized for simulation), real segment which is a real segment (for example, real business segment, area or brand etc) or virtual segment which is a virtual segment (for example real "Segment hierarchized for simulation" or "recombined segment" etc. Specific examples of a real organization, a virtual organization, a real segment and a virtual segment are shown in the hierarchical structure of FIG. And in this embodiment, hierarchical structure means the thing of the structure formed by the object of the lowest layer and the object of the upper layer forming a hierarchy.

  The hierarchical object management information 106a is information for managing the hierarchical structure. As shown in FIG. 3, the hierarchical object management information 106a includes, for example, hierarchical structure identification data (management number), management name, hierarchy identification data (hierarchical level), target identification data (node identification code), node name, and higher ranks. Layer identification data (upper layer level), upper object identification data (upper node identification code), lower structure classification and lower layer identification data (association code), etc. are included.

  The management number is data for identifying a hierarchical structure. Specifically, the management number of the hierarchical structure shown in FIG. 5 is (1), the management number of the hierarchical structure shown in FIG. 6 is (2), and the management number of the hierarchical structure shown in FIG. 7 is (3) Thus, management numbers 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 unit as shown in FIG. Here, the data recording method for recording data in the hierarchical object management information 106 a is to follow the following rules 1 and 2 for the hierarchical object identification information part.
1. Assign a unique management number to each hierarchical object to be managed.
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 hierarchy of the top layer becomes hierarchy level 0, and the hierarchy level also increases by one each time the hierarchy moves down one level thereafter. For example, in the case of the organization chart (1) shown in FIG. 5, all companies are hierarchy level 0 (that is, the top layer), and companies 1 to 3 are hierarchy level 1 (that is, the lowest layer). An example of setting of the hierarchy level is shown in FIG.

  The node identification code is data for identifying an object. For example, in the case of organization 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 object, such as 03000. The node name is a name corresponding to the node identification code. A setting example of the node identification code and the node name is shown in FIG.

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

  The upper node identification code is data for identifying an object of a layer one layer higher than the object of each layer. For example, in the case of companies 1 to 3 in the organization chart (1) shown in FIG. 5, the node identification code of the whole company which is the target of the hierarchy one rank higher is 10000 as described above. The identification code is 10000. An example of setting of the upper node identification code is shown in FIG.

  The lower structure classification is a classification indicating the presence or absence of the lower hierarchy. For example, in the case of the organization chart (1) shown in FIG. 5, since the lower hierarchy exists in the whole company, the lower structure division about the whole company becomes "0: lower place". On the other hand, since there is no lower hierarchy as seen from companies 1 to 3, the lower structure division for companies 1 to 3 is "1: no lower order". An example of setting of the lower structure classification is shown in FIG.

The hierarchy level, the node identification code, the node name, the upper hierarchy level, the upper node identification code, and the lower structure division are collectively referred to as a hierarchical structure information unit as shown in FIG. Here, the data recording method of recording data in the hierarchical object management information 106 a conforms to the following rules 1 to 5 for the hierarchical structure information unit. Although the upper hierarchy level and the lower structure classification are not essential items in the present invention, the process procedure of the program is simplified if data is held in the process of specifying the upper and lower hierarchy nodes. It is an item that you are preparing to become.
1. Set the hierarchy level (0 to N) to identify the hierarchy of hierarchical objects.
2. A unique node identification code is assigned to each identical management number / hierarchical level.
3. A node name that can be identified by the user is set for the unique node identification code.
4. For nodes in each hierarchy, the hierarchy level (upper hierarchy level) and the node identification code (upper node identification code) of the parent node to which the node belongs are set.
5. For nodes in each hierarchy, substructure division is set to distinguish whether the node is the lowest node or whether there are further child nodes.

  The lowest layer identification data is data for identifying an object of the lowest layer, and may be referred to as a tied code. Specific examples of the lowest layer identification data include, for example, company identification data (company code) for identifying a certain company, business place identification data (business code) for identifying a place of business in a certain company, and a certain company Department identification data (department code) for identifying the department in the above, or business content identification data (analysis code) for identifying the business content in a certain company. FIGS. 4 and 40 show setting examples of the hierarchical object management information 106a in the case of using a company code, a business office code and a department code as the lowest layer identification data. Further, FIG. 41 shows a setting example of the hierarchical object management information 106 a in the case of using an analysis code as the lowest layer identification data.

  Since the lowest layer identification data is data for identifying the object of the lowest layer as described above, the lowest layer identification data is not allocated to the objects higher than the lowest layer. For example, in the hierarchical object management information 106 a of FIG. 3, since companies 1 to 3 (records in the second to fourth rows from the top) are targets of the lowest layer, the association codes 1 to 3 are the lowest layer identification data. Are assigned, but since the whole company (the first record from the top) is not the target of the lowest layer, the lowest layer identification data is not assigned, and the column of the tying code is “NULL It is ".

The lowest layer identification data (tie-up code) is referred to as a tie-up information unit as shown in FIG. Here, the data recording method of recording data in the hierarchical object management information 106 a conforms to the following rules 1 to 5 for the association information part. In addition, the character string of <NULL> meaning no setting and <ALL> meaning all is not limited to this, and may be another character string.
1. It holds the maximum number of items in the system assumption that will be the aggregation key of the data to be aggregated. 2. In each node, when the lower structure classification is “with lower order”, since it is not necessary to hold the correlated information, the reserved word <NULL> meaning no setting is held.
3. When the lower structure classification is "no lower rank", each code to be linked is held. At this time, the following rules 4 and 5 apply.
4. An item that is essential as a tied item always holds a tied code.
5. For the item that is optional as a tied item, a code is specified when setting a breakdown, and when not specifying a breakdown, a reserved word <ALL> meaning all is held.

  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 of “company CD (company code)” (essential), “business office CD” (optional) and “division CD” (optional) are adopted as the association information. In addition, the required item "company CD" is all designated in the organization charts (1) to (3) of the data example. And, in organization charts (1) and (2), since it is a case where only organization in company unit is assigned, reserved word <ALL> which means all for "business place CD" and "department CD" is specified It is in a state of Furthermore, in organizational chart (3), since the assignment of the organization by company unit + establishment unit is included, "department CD" is in a state where the reserved word <ALL> meaning all is specified, and further The company 3 is also in a state where a reserved word <ALL> which means all is designated since allocation of the “business office CD” is unnecessary. In FIG. 4, the organization chart number has the same meaning as the management number, the organization chart name has the same meaning as the management name, the organization level has the same meaning as the hierarchy level, and the organization CD has the same meaning as the node identification code. The name is the same as the node name, the upper organizational level is the same as the upper hierarchical level, and the upper organization CD is the same as the upper node identification code.

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

  Here, the hierarchical object management information 106 a may include a record having information on objects of each hierarchy from the highest layer to the lowest layer in the hierarchical structure. A record is one row of information in the table of the hierarchical object management information 106a shown in FIG. As shown in FIG. 3, for example, the record includes 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 Hierarchy level), upper object identification data (upper node identification code), lower structure classification, and the like. In addition, the lowest layer record (three records having a hierarchy level of 1 in FIG. 3), which is a record having information on the lowest layer, further includes, for example, lowest layer identification data (a tying code).

  The layered object expansion information 106b will be described later in detail, but is a record having information on a target of the highest layer in the layered object management information 106a, and a record having information on a target of one layer higher than the lowest layer. It is the information which developed up to. The hierarchical object expansion information 106b includes, for example, hierarchical structure identification data (management number), hierarchical identification data (hierarchical level), target identification data (node identification code), upper hierarchical layer identification data (upper hierarchical layer), as shown in FIG. Level), upper object identification data (upper node identification code), lower layer identification data (pinning code), and the like.

  The hierarchized object extraction information 106c is information obtained by extracting only the record including the hierarchal level input by the user from the records included in the hierarchized object expansion information 106b, although the details will be described later. The hierarchical object extraction information 106c includes, for example, hierarchical structure identification data (management number), hierarchical identification data (hierarchical level), target identification data (node identification code), upper hierarchical layer identification data (upper hierarchical layer), as shown in FIG. Level), upper object identification data (upper node identification code), lower layer identification data (pinning code), and the like.

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

  The aggregation result data 106 e is data indicating the result of aggregation of the aggregation target data 106 d. The aggregation result data 106e includes, for example, hierarchical structure identification data (management number), hierarchy identification data (hierarchical level), object identification data (node identification code), and aggregation results, as shown in FIGS.

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

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

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

  The user group affiliation information 106g is information for managing a user who belongs to the user group. The user group affiliation information 106g includes, for example, user group identification data (user group code) and user identification data (user ID) as shown in FIG. Here, when the user group affiliation information 106g is set as shown in FIG. 20, FIG. 21 shows which user group each user belongs to. Note that one user may belong to a plurality of user groups, as in User C and User D shown in FIG.

  The authority setting information 106 h is information for holding the reference authority to the user group with respect to the hierarchical object. The authority setting information 106 h includes, for example, hierarchical structure identification data (management number), hierarchy identification data (hierarchical level), object identification data (node identification code), and user group identification data (user group code), as shown in FIG. Etc. In the authority setting information 106h, it is also possible to associate a plurality of user group codes with one node identification code.

  Here, when the authority setting information 106h is set as shown in FIG. 22, it is shown in FIG. 23 which hierarchical structure each user group can refer to. As shown in FIG. 23, since the full authority group (User A) can refer to company-wide information, it can also refer to information on companies 1 to 3 which are lower layers of the company (upper browsing authority Because the person who owns automatically has all the browsing rights under)). On the other hand, group 1 authority group (User B and User C) can only refer to information on company 1, group 2 authority group (User C and User D) can only refer to information on company 2, and group 3 authority group (User D) is company Only 3 information can be referenced. Persons who belong to a plurality of authority groups have the authority to view both companies.

  In the present embodiment, a flag for switching whether to manage the authority setting of the hierarchical object may be held in order to set whether to perform the authority (security) setting in the first place. The flags include, for example, a "use" flag which means to set the authority and a "not use" flag which means not to set the authority.

  Here, in the present embodiment, what kind of data setting can be specifically performed and what kind of data reference authority management can be performed will be described using FIG. 24 to FIG.

  First, the hierarchical structure of the organization can be set by the hierarchical object management information 106a. A case where 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 arranged below the entire company, as shown in FIG. As shown in FIG. 25, the hierarchical structure represented by the record indicated by MA 6 in FIG. 27 is a three-layered hierarchical structure including the company-wide hierarchy, the hierarchy of core companies classified by business, and the hierarchy of individual companies. The hierarchical structure represented by the record indicated by MA 7 in FIG. 27 is a hierarchical structure of the virtual organization of the sales department classified by area as shown in FIG.

  The reference authority for objects 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 (the group to which each user belongs 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 as shown in the next paragraph. The record indicated by MA8 in FIG. 28 is a record for managing the viewing of objects in a virtual organization in which all companies are arranged under the company shown in FIG. 24, and the record indicated by MA9 in FIG. 28 is the company shown in FIG. Records for managing the browsing of objects in three hierarchies consisting of the hierarchy of core companies according to business and the hierarchy of individual companies, and the record shown by MA 10 in FIG. 29 shows the browsing of objects in the virtual organization of the sales department by area It is a record to manage.

  That is, as shown in FIG. 24, User A belonging to the user group “Full” can refer to the information of all the companies 100 to 300 which are lower layers of the company. Although not shown in FIG. 24, User B and User C belonging to user group “Company 1” can refer to the information of company 100, and User C and User D belonging to user group “Company 2” can refer to information on company 200. User D belonging to the user group “Company 3” can refer to the information on the company 300. Then, as shown in FIG. 25, User A belonging to the user group "Full" can refer to all information of companies 100 to 400 which are lower layers of the company, and User B belonging to the user group "Kougi Group" Information of lower-level companies 100 and 200 can be referenced, and User D belonging to the user group “Seizou Group” can reference information of lower-level companies 300 and 400 of the manufacturing business group. As shown by MA 4 in FIG. 25, these three groups differ in the range of objects to be viewed depending on the range in which the reference is permitted. Further, as shown in FIG. 26, User A belonging to the user group “Full” is a lower layer of the company (company 100, Tokyo head office, sales department), (company 200, Tokyo head office, sales department), (company 100) UserE belonging to the user group "KantouGroup" can refer to the respective information of (Osaka branch office, sales department) and (company 200, Osaka branch office, sales department) and is a lower layer of the Kanto group (company 100, Tokyo head office, User D belonging to the user group "Kansai Group", who can refer to information of sales department) and (company 200, Tokyo head office, sales department), is a lower layer of Kansai group (company 100, Osaka branch office, sales department) 200, Osaka branch office, sales department) information can be referred. Note that, in FIG. 24 to FIG. 26, the user who has not been permitted any permission can not 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 browsing authority can be set at any place according to the hierarchical level of the hierarchical object, and the setting is flexible with the minimum necessary setting. It is possible to respond.

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

  The layered object security deployment information 106 j is information acquired with reference to the layered object management information 106 a based on the authority extraction information 106 i although the details will be described later. The hierarchical object security deployment information 106 j includes, for example, hierarchical structure identification data (management number), hierarchical identification data (hierarchical level), target identification data (node identification code), etc., as shown in FIG.

  Supplier specific item setting information 106k defines a combination of usage items (company code, item code or establishment code, etc.) of transaction contents of the company and usage items (business code, division code, etc.) of the other party information to be specified. It is information to do. Specifically, as shown in FIG. 43, “use” or “use” of five items of, for example, a supplier code, an item code, an establishment code, a department code, and an analysis code, as use items of the transaction contents of the company "Not use" can be set. Further, as shown in FIG. 43, “use” or “do not use” is set as the use item of the other party information to be specified, for example, for the three items of the other party office code, the other department code and the other party analysis code. be able to.

  The supplier specific pattern setting information 1061 is information for specifying the other party of the transaction, in other words, information for defining pattern information to be specified according to the supplier specific item setting information 106k. The supplier specific pattern setting information 106l shown in FIG. 44 is an example of data when “use” is set for all items in the supplier specific item setting information 106k described in the previous paragraph. As shown in FIG. 44, the supplier specific pattern setting information 106l is the lowermost layer identification data (company code, business office code, department) which is the lowermost layer identification data for identifying the subject object that 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 (a supplier code) for identifying the business partner of the subject, and the other party of the transaction It includes lower-layer identification data (lower-party company code, opposite-company code, opposite-section code, or opposite-analysis code), which is the lowest layer identification data for identifying a certain opposite object. As shown in FIG. 44, the supplier specific pattern setting information 1061 may further include a determination order. The significance of the determination order will be described later.

  Note that in the supplier specific pattern setting information 106l, the character string of the reserved word <ALL> that means all is not limited to this, and may be another character string, and the in-house attribute code (customer If the code, subject code, establishment code, department code or analysis code) is set in <ALL>, multiple counterpart attribute information (the counterpart company code, the other establishment code, the other department code or Since it may be linked with the other party analysis code, it should be uniquely determined by the determination order.

  Here, what kind of transaction is defined by the supplier specific pattern setting information 1061 shown in FIG. 44 will be described using FIG. First, a transaction defined by the first and second records from the top in the table of FIG. 44 (two records in which the company code is 100) is shown in FIG. As shown in (A) of FIG. 45, the purchase transaction partner of company 100 (company code) / Tokyo (business office code) / Eigyo (division code) / product sales business (analysis code) is company 300 (a partner company Code) / Osaka (partner office code) / Hanbai 1 (partner department code) / retail business (counterpart analysis code), and the company 100 / Tokyo / Eigyo / sales business of the product sales business is the company 200 / Tokyo / Seizou 1 / Manufacturing business. Next, a transaction defined by the fifth to sixth lines from the top in the table of FIG. 44 (two records with a company code of 300) is shown in (B) of FIG. As shown in (B) of FIG. 45, sales 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 third and fourth top records (two records with a 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 locations, divisions, and business areas of company 200 are engaged in purchase transactions and sales transactions with company 100 / Tokyo / Eigyo / product sales business and company 300 / Osaka / Hanbai1. / Retail business. The transactions that occur in the manufacturing division are uniquely determined for each business partner, business establishment, division, and segment.

  The aggregation target source data 106m is data that is the source when creating the aggregation target data 106n. As shown in FIG. 46, the aggregation target original data 106m includes the lowermost-layer identification data (company code, office code, division code or analysis code), the item identification data (item code), and the supplier identification data (business partner Code) and On the other hand, the aggregation target original data 106m does not include the other party lowest layer identification data (the other party company code, the other business office code, the other department code or the other party analysis code), and these items are shown in FIG. , "Unset" has become. As shown in FIG. 46, the aggregation target source data 106m further includes the date of occurrence (date of occurrence) and the numerical value (amount of money) of the item (the item means information of one horizontal row in the table of the aggregation target source data 106m). Etc. may be included.

  The aggregation target data 106 n is data to be aggregated. As shown in FIG. 49, the aggregation target data 106n includes the lowermost-layer identification data (company code, office code, division code or analysis code) and the lower-layer identification data (opposite company code, opposite office code, Include the other department code or the other party analysis code). As shown in FIG. 49, the aggregation target data 106n further includes the date of occurrence (date of occurrence) of the statement (the statement means information in one horizontal row in the table of the aggregation target data 106n), the item identification data (subject code , Customer identification data (supplier code), numerical value (amount), etc. may be included.

  The aggregation result data 106 o is data indicating the result of aggregation of the aggregation target data 106 n. 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 external transaction amount, which is the amount of inter-company transaction, internal transaction amount, which is the intra-group transaction amount, and overall total amount, which is the total of external transaction amount and internal transaction amount.

  The conversion item setting information 106p is used to define a combination of the use item (business partner code, item code or establishment code etc.) of the transaction content of each company and the use item (common segment code etc.) of the information to be converted. It is information. Specifically, as shown in FIG. 67, “use” is used as the use item of the transaction contents of each company, for example, five items of a supplier code, an item code, an office code and a department code, and an analysis code. Or you can set "do not use". Further, as shown in FIG. 67, “use” or “not use” can be set as the use item of the conversion destination information, for example, for the item “common segment code”.

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

  The conversion source data consists of a plurality of data. A plurality of data are item identification data (item code) for identifying accruing items, business place identification data (business code) for identifying a place of business in a company, and a department for identifying a department in a company Preferably, the data is at least two data selected from the group consisting of identification data (department code) and business content identification data (analysis code) for identifying business content in a certain company. Also, the plurality of data are 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 business partner of a certain company. And are more preferable. The conversion pattern setting information 106q shown in FIG. 68 is an example including all six items of an item code, a business office code, a department code, an analysis code, a company code and a supplier code as conversion source data.

  The conversion destination data is, for example, data which a certain target holds in common, and for example, the targets on the first line, the second line and the fifth line from the top of FIG. Therefore, it has conversion destination data (common segment code) "G_Hanbai". As shown in FIG. 68, only one common segment code (common segment code 1) may be used, or two or more common segment codes (common segment codes 2, 3...) May be used.

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

  As shown in FIG. 68, the character string of the reserved word <ALL> meaning all is not limited to this, and may be another character string. In addition, when the conversion source individual company attribute section (customer code, item code, business office code, department code or analysis code) is set in <ALL>, the same transaction has multiple conversion common attribute sections (common As it may be linked with the segment code, it should be uniquely determined by the determination order. Then, by setting the determination order of the lines for which all attributes other than the company code are set to <ALL> as the lowest, general purpose data such as "Other" is used for the remaining conversion target data not converted in the upper determination order. Codes can be assigned.

  The conversion target data 106 r 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, business office code, department code or analysis code). The description of the conversion source data of the conversion pattern setting information 106q can be incorporated into the description of the conversion source data included in the conversion target data 106r. As shown in FIG. 69, the conversion target data 106r further includes the date of occurrence (date of occurrence) and the numerical value (amount of money) of the specification (specification means information in one row in the table of the conversion target data 106r). May be included.

  The conversion completion data 106 s is data in which conversion of the conversion source data included in the conversion target data 106 r into conversion destination data is all 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 term "information" means one row of information in the conversion completion data 106s table) date of occurrence (date of occurrence), numerical value (amount of money) and the like.

  The control unit 102 is a CPU or the like that controls the information processing apparatus 100 in an integrated manner. The control unit 102 has an internal memory for storing control programs such as the OS, programs defining various processing procedures, required data, etc., and performs various information processing based on the stored programs. Run.

  In terms of functional concept, the control unit 102 may, for example, (1) hierarchical structure identification data for identifying a hierarchical structure formed by forming a hierarchy of an object of the lowermost layer and an object of the upper layer; Acquisition unit 102a as an acquisition unit that acquires lowest layer identification data associated with the input hierarchical structure identification data with reference to target management data including the lowest layer identification data for identifying the layer object; (2) A record acquisition unit 102a1 as a record acquisition unit that acquires a record including the input hierarchical structure identification data with reference to the target management data; (3) From the record acquired by the record acquisition unit The lowest layer record acquisition unit 102a2 as the lowest layer record acquisition means for acquiring the lowest layer record, (4) acquired by the lowest layer record acquisition means The record including the upper layer identification data and the upper layer identification data and the same layer identification data as the upper layer identification data included in the lower layer record is acquired with reference to the object management data, and the acquired record includes the lowest layer A record creation unit 102a3 as a record creation unit for creating a record to which the lowest layer identification data included in the lowest layer record acquired by the record acquisition unit is added; (5) the most acquired by the lowest layer record acquisition unit The lowest layer data acquisition for acquiring the lowest layer identification data included in the record by acquiring the record including the input hierarchy identification data with reference to the lower layer record and the record created by the record creation means The lowest layer data acquisition unit 102a4 as a means, (6) lowest layer identification data and number And the extraction unit 102b as an extraction unit that extracts a numerical value associated with the lowest layer identification data acquired by the acquisition unit with reference to the aggregation target data including; and (7) totals the numerical values extracted by the extraction unit Hierarchical structure identification data for identifying a hierarchical structure formed by the aggregation unit 102c as aggregation means, (8) objects of the lowermost layer and objects of the upper layer forming a hierarchy, and each of the hierarchical structures Reference is made to object management data including layer identification data for identifying a layer and object identification data for identifying the object, and layer identification data and object identification data associated with the input hierarchical structure identification data are acquired. The first acquisition unit 102d as a first acquisition unit, and (9) the user management data including the user group identification data and the user identification data, and the input user Group identification data acquiring unit 102d1 for acquiring user group identification data linked with the user identification data, (10) hierarchical structure identification data, hierarchy identification data, target identification data, and user group identification data Acquisition of hierarchical identification data and target identification data that are 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 hierarchy identification data etc. acquiring unit 102d2 as a means, (11) the hierarchical structure identification data input with reference to the target management data, the hierarchy identification data acquired by the hierarchy identification data etc. acquiring means, and the object identification data As a record acquisition means for acquiring records containing (12) records including upper layer identification data and upper object identification data which are the same as the layer identification data and object identification data included in the record acquired by the record acquisition unit 102d3; Acquiring the record including the hierarchy identification data and the upper hierarchy identification data and the upper object identification data which are the same as the hierarchy identification data and the object identification data contained in the acquired record with reference to the object management data, Repeating unit 102d4 as repeating means that repeats until hierarchical identification data and target identification data included in the lowest layer record are acquired by acquiring the lowest layer record, (13) Hierarchical structure identification data and hierarchy Identification data, object identification data, and the lowest layer for identifying the object of the lowest layer The lower layer identification data associated with the input hierarchical structure identification data and the layer identification data acquired by the first acquiring means and the object identification data with reference to the target expansion data including the separate data (14) The record including the input hierarchical structure identification data is acquired with reference to the second acquisition unit 102e as an acquisition unit and (14) the target management data, and the lowest layer record is acquired from the acquired record. And the expanded data creation unit 102 f as expanded data generation means for generating the target expanded data by setting the acquired lowest layer record as the target expanded data, and (15) acquired by the second acquisition means The same hierarchy identification data as the upper hierarchy identification data and the upper object identification data included in the lowest hierarchy record including the lowest hierarchy identification data, and Record creation means for creating a record in which a record including target identification data is acquired with reference to the target management data, and the lowest layer identification data acquired by the second acquisition unit is added to the acquired record (16) The lowest layer record including the lowest layer identification data acquired by the second acquisition unit and the hierarchy identification data input with reference to the record generated by the record generation unit The lowest layer data acquisition unit 102h as the lowest layer data acquisition means for acquiring the lowest layer identification data included in the record by acquiring the record, and (17) including the lowest layer identification data and a numerical value Extraction means for extracting numerical values associated with the lowest layer identification data acquired by the lowest layer data acquisition means with reference to the aggregation target data (18) the target of the lowest layer and the target of the upper layer form a hierarchy. Hierarchical structure identification data for identifying a hierarchical structure to be formed, layer identification data for identifying each layer in the hierarchical structure, object identification data for identifying the object, and object of the lowermost layer The lowermost layer identification data, which is the lowest layer identification data for identifying the main subject that is the subject of the transaction, with reference to the target extraction data including the lowermost layer identification data for Hierarchical structure identification data that is associated with the lowermost layer identification data included in the aggregation target data including the lowest other layer identification data that is the lowest layer identification data for identifying an object, layer identification Entity acquisition unit 102k as entity acquisition means for acquiring data and object identification data, and (20) a hierarchical structure associated with the other party lowest layer identification data included in the aggregation object data with reference to the object extraction data (21) Hierarchical structure identification data acquired by the subject acquiring means, hierarchical identification data and object identifying data, and the other party acquiring means for identifying data, hierarchy identification data and object identification data A determination unit that determines that a transaction between the subject object and the opposite object is an internal transaction within a group when the hierarchical structure identification data, the hierarchy identification data, and the object identification data acquired by the means are the same (22) the same as in the determination unit 102m as the second embodiment, and the lowermost-layer identification data included in the aggregation target data (23) subject identification data for identifying the subject lowest layer identification data and the accounting item of the transaction, and for identifying the business partners of the subject object With reference to tallying object original data including customer identification data, the main object included in transaction pattern setting data including main object lowest layer identification data, item identification data, customer identification data and lowest other layer identification data The lower-layer identification data, the item identification data, and the supplier identification data same as the lower-layer identification data, the item identification data, and the supplier identification data are extracted, and the extracted lowest-layer identification data, the item identification data, and the supplier By adding the other party lowest layer identification data included in the transaction pattern setting data, which is associated with identification data, to the aggregation target source data, The record including the input hierarchical structure identification data is acquired with reference to the target management data and (24) the target management data, and the acquired record is acquired. And the lowermost layer record is obtained, and the target management data is referred to the record including the upper layer identification data and the upper layer identification data and the target identification data which are included in the obtained lower layer record and the upper layer identification data. To the acquired record, the lowest layer identification data included in the acquired lowest layer record is added, and a record is created, and the acquired lowest layer record and the created record are referred to. Acquire a record including the input hierarchical identification data, and set the acquired record as the target extraction data The conversion source data and the conversion destination are referred to with reference to the conversion target data including the conversion source data consisting of a plurality of data (25) a target extraction generation unit 102p as target extraction generation means for generating the target extraction data, An extraction unit 102 q as an extraction unit that extracts the same conversion source data as conversion source data included in the conversion pattern setting data including data, and (26) the conversion source data extracted by the extraction unit is the conversion source data And a conversion unit 102r as a conversion unit that converts the conversion destination data included in the conversion pattern setting data. In addition, about the detail of the process which each part performs, below [3. Specific Example of Processing].

[3. Specific example of processing]
Hereinafter, specific examples of the process according to the present embodiment will be described. The process according to the present embodiment can be roughly divided into five processes of data collection process, data reference authority management process, internal transaction determination process, data conversion process, and processes other than these. I will explain the item.

[3-1. Data aggregation process]
First, the data aggregation process will be described in detail mainly using FIGS. The data aggregation process is roughly divided into three processes of an acquisition process, an extraction process, and an aggregation process, so 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 associating code, and acquires the associating code associated with the input management number. The specific processing is as shown in the following (1-1) to (1-4).

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

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

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

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

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

  Up to here, as shown in FIG. 10, the creation of the hierarchical object expanded information 106b including the record having the hierarchical 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 the upper node identification code included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2. Are acquired with reference to the hierarchical object management information 106a, and a record is created in which the association code included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 is added to the acquired record.

  That is, for the layer from the end layer (lowermost layer) to the upper layer, the upper hierarchical object expansion information 106b is obtained from the hierarchical object management information 106a and the hierarchical object expansion information 106b created in (1-2). Create

  Specifically, among the four lowest layer records acquired by the lowest layer record acquisition unit 102a2, two records including the upper hierarchy level 1 and the upper node identification code 11000 will be described. The record including the same hierarchy level and node identification code as the upper hierarchy level 1 and the upper node identification code 11000 is the second line from the top in the hierarchical object management information 106a of FIG. 11 (indicated by a bold frame). Therefore, the record creation unit 102a3 first acquires this record. Next, the record creation unit 102a3 adds the association code (1, 001, ALL) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 to the acquired record, and the acquired record A record is created in which the tying code (1, ALL, A) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 is added. 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, the same process as in the previous paragraph is performed also on two records including the upper hierarchy level 1 and the upper node identification code 12000. Record (indicated by a bold frame) from the top of the fifth line in the hierarchical object management information 106a of the second record (indicated by a bold frame), a record obtained by adding the association code (2, 001, ALL) to the acquired record, and the acquired record Create a record with the pegging code (3, ALL, ALL) added to. Then, the two created records are stored in the hierarchical object expansion information 106b.

  Thus, four records created in the previous paragraphs and the previous paragraph and stored in the hierarchical object expanded information 106b are indicated by MA1 in FIG. As shown by MA1 in FIG. 11, in the expansion information of hierarchy level 1, all the association information of hierarchy level 2 included in the lower (end) is expanded.

  Up to here, as shown in FIG. 11, the creation of the hierarchical object expanded 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 creation unit 102a3 is completed by this, but As described above, when the hierarchy level 2 or more is included (that is, when the hierarchy is three or more layers), the record creation unit 102a3 continuously performs the following processing.

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

  Specifically, the record including the same hierarchy level and node identification code as the upper hierarchy level 0 and the upper node identification code 10000 in the four records (shown by MA1 in FIG. 11) created by the record creation unit 102a3 is the hierarchy of FIG. It is a record (indicated by a bold frame) of the first line from the top in the integrated object management information 106a. Therefore, the record creation unit 102a3 first acquires this record. Next, the record creation unit 102a3 adds the association code (1, 001, ALL) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 to the acquired record to the acquired record The record to which the association code (1, ALL, A) included in the lowest layer record acquired by the lowest layer record acquisition unit 102a2 is added, and the lowest layer record acquired by the lowest layer record acquisition unit 102a2 to the acquired record Add the tying code (2, 001, ALL) included in the record and the tying 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 created four records are stored in the hierarchical object expansion information 106b.

  Thus, four records created in the previous paragraph and stored in the hierarchical object expanded information 106b are indicated by MA2 in FIG. As shown in FIG. 12, in the expansion information of hierarchy level 1, all the association information of hierarchy level 2 contained in the lower (end) is expanded, and in the expansion information of hierarchy level 0, lower (end) All the association information of the hierarchy levels 1 to 2 included in the state is expanded.

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

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

(1-4) Lowermost Layer Data Acquisition Processing The lowermost layer data acquisition unit 102a4 is input with reference to the lowermost layer record acquired by the lowermost layer record acquisition unit 102a2 and the record created by the record creation unit 102a3. By acquiring the record including the hierarchical level, the tying 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 hierarchical object expanded information 106b shown in FIG. 13 to acquire a record including the hierarchy level 1, ie, four records indicated by MA3 in FIG. The four sets of tying codes (1, 001, ALL), (1, ALL, A), (2, 001, ALL) and (3, ALL, ALL) included in the record are acquired. The lowest layer data acquisition unit 102a4 may store the acquired four records in the hierarchical object extraction information 106c, as shown in FIG. Note that, as shown in FIG. 8, as a condition for acquiring a record, a node identification code may be input (arbitrary range presence / absence of node identification code is optional), but if not input, all node identification codes are It becomes an object of acquisition of the lowest layer data acquisition unit 102a4.

  As described above, the acquiring unit 102a determines four sets of tying codes (1, 001, ALL) shown in the hierarchical object extraction information 106c of FIG. 13 as tying codes that are tied to the input organization chart (3). (1, ALL, A), (2, 001, ALL) and (3, ALL, ALL) can be obtained.

(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 an aggregation target value associated with the association code acquired by the acquisition unit 102a.

That is, the extraction unit 102b performs matching search of the aggregation target data 106d based on the association code of the hierarchical object extraction information 106c. As a condition at the time of matching with the aggregation target data 106d, evaluation is performed according to the following procedure 1 to 4.
1. Regarding the determination of the tied code 1, when the tied code 1 is an essential item, the matching code 1 of the aggregation target data 106d = matching code 1 of the hierarchical object extraction information 106c is searched for, and the tied code 1 is an optional item In this case, the matching code 1 = reserved word <ALL> in the hierarchical object extraction information 106c is obtained, or the matching code 1 in the aggregation target data 106d = the tied code 1 in the hierarchical object extraction information 106c is searched.
2. Regarding the determination of the tied code 2, when the tied code 2 is an essential item, the matching code 2 of the aggregation target data 106d = matching code 2 of the hierarchical object extraction information 106c is searched for, and the tied code 2 is an optional item In this case, the matching code 2 = reserved word <ALL> in the hierarchical object extraction information 106c or the matching code 2 in the aggregation object data 106d = the tied code 2 in the hierarchical object extraction information 106c is searched.
3. Regarding the determination of the tied code 3, when the tied code 3 is an essential item, the matching code 3 of the aggregation target data 106d = matching code 3 of the hierarchical object extraction information 106c is searched, and the tied code 3 is an optional item In this case, the matching code 3 = reserved word <ALL> in the hierarchical object extraction information 106c is obtained, or the matching code 3 in the aggregation object data 106d = tie code 3 in the hierarchical object extraction information 106c is searched.
4. And evaluation is performed only by the number of the tying cords which a system uses hereafter (namely, when tying cord 4 or subsequent ones exist, the same processing as the tying cords 1-3 is performed).

  Specifically, as shown in the aggregation target data 106 d of FIG. 14, the item including the tying code (1, 001, ALL) of the condition (1) is the specification of the item ID = 1 (total object value = 1,000 ). Similarly, the item including the tying code (1, ALL, A) of the condition (2) is the item with the item ID = 1 (total object value = 1,000) and the item with the item ID = 4 (total object value = 4 , 000). Note that <ALL> means that any information may be included. Similarly, the item including the pegging code (2, 001, ALL) of the condition (3) is the item of the item ID = 2 (total object value = 2,000). Similarly, the item including the pegging code (3, ALL, ALL) of the condition (4) is the item with the item ID = 3 (total object value = 3,000) and the item with the item ID = 6 (total object value = 6) , 000), the item with item ID = 9 (total object value = 9,000) and the item with item ID = 12 (total object value = 12,000). In this manner, the extraction unit 102b calculates 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, in the case where the aggregation target to be searched matches a plurality of tying conditions, it is necessary to take into account that the same row (the same specification) is counted in a plurality (double count) (a specification ID of 1 The item is applicable). Although the item ID makes the row (item) of the aggregation target data 106d uniquely identifiable key information and can be either a single item or a combination of multiple items, in this example, an example of a single item is used. Described.

(3) Counting Process The counting unit 102c counts the counting target values extracted by the extracting unit 102b.

  Specifically, the aggregation unit 102c simply adds up the eight aggregation target values extracted by the extraction unit 102b to an aggregation of 1,000 + 1,000 + 4,000 + 2,000 + 3,000 + 6,000 + 9,000 + 12,000 = 38,000. However, it is preferable to perform the tabulation by removing the tabulation and double counting in hierarchical units as follows.

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

(3-1) Tabulation in Layers First, tabulation in layers will be described. The aggregation unit 102c, as illustrated on the left side of FIG. 16, includes the aggregation target value extracted by the extraction unit 102b, the combination of the management number included in the four records acquired by the acquisition unit 102a4, the hierarchy level, and the node identification code; The item which has the same combination is specified with reference to the aggregate key information data 106f including a plurality of items including the item, and the numerical values included in the item specified are summarized.

  Specifically, as shown on the left side of FIG. 16, the first to third lines of the summary key information data 106f all have a combination of organization chart (3), hierarchy level 1 and node identification code 11000. Including. Therefore, the aggregating unit 102c identifies the first to third lines of the specification as the same combination, and adds the numerical values included in the specified first to third lines of the specification to 1,000 + 1,000 + 4. It counts as 000, 6,000. On the other hand, as shown on the left side of FIG. 16, the specifications of the fourth to eighth rows from the top of the total key information data 106 f all include combinations of organization chart (3), hierarchy level 1 and node identification code 12000. Therefore, the counting unit 102c counts the numerical values included in the specifications of the fourth to eighth lines as 2,000 + 3,000 + 6,000 + 9,000 + 12,000 = 32,000. The tabulated result is shown in tabulated result data 106e of FIG.

  As described above, in the present embodiment, the aggregation target values are aggregated on a hierarchy level level 1 basis. That is, the tabulated result of “company 1: belonging to Kanto area: Tokyo head office and company 1: Kanto sales department” shown in the hierarchical object management information 106 a in FIG. 9 is 6,000, and “company 2: belonging to Kansai area: We have calculated that the totals for Osaka branch office and company 3 are 32,000 (area-based aggregation). However, when hierarchy level 0 or hierarchy level 2 is input by the user, the following aggregation can be performed. That is, when hierarchy level 0 is input, the aggregation result for “company” shown in the hierarchical object management information 106 a of FIG. Tabulation). Also, when hierarchy level 2 is input, the tabulated result for “company 1: Tokyo head office” shown in the hierarchical object management information 106a of FIG. 9 is 1,000 by the same method as described above. , The result of aggregation for "Company 1: Kanto Sales Department" is 1,000 + 4,000 = 5,000, the result of aggregation for "Company 2: Osaka branch office" is 2,000, and the result of aggregation for "Company 3" Becomes 3,000 + 6,000 + 9,000 + 12,000 = 30,000 (counting in terminal units). As described above, according to the information processing apparatus 100 according to the present embodiment, it is possible to perform aggregation in different hierarchy units (whole company unit, area unit, or terminal unit) according to the hierarchy input by the user.

  Here, in the tabulation method described in this item, the specifications (line ID = 1) of the first and second lines from the top of the tabulated key information data 106f shown on the left side of FIG. It will be counted. There is no need to remove such double counts if there is no occurrence of the aggregation target corresponding to multiple association settings on the association setting pattern or if there are multiple association targets on the association setting pattern If it is judged that it does not matter if it is double counted or it should be double-canted.

  However, due to the association setting pattern, it may occur that the aggregation target corresponds to a plurality of association settings, and it may be determined that double counting should not be performed. In this case, unique key information (detail ID) of the item that matches the pegging setting is specified, duplicate lines are removed, and counting is performed, that is, double counting is performed as shown in (3-2) below. It is preferable to perform the tabulated counting.

(3-2) Tabulation with Removal of Double Count Next, tabulation with removal of double count will be described. When there is a specification with the same item ID in the aggregation key data 106 f including a plurality of items including the aggregation target value extracted by the extraction unit 102 b and the item ID, the aggregation unit 102 c determines only one of the items The summary key data 106 f is updated by deleting the other items except for, and the numerical values included in the items included in the updated summary key data 106 f are added up.

  Specifically, as shown on the left side of FIG. 16, since the specification IDs included in the first and second lines of the summary key information data 106 f are both 1, the tabulation unit 102 c determines the second line. The summary key data 106f is updated by deleting the specification of (the specification of the first line may be deleted instead of the description of the second line). The updated total key data 106f is shown on the right side of FIG. Then, the aggregation unit 102c aggregates the numerical values included in the items (seven items shown on the right side of FIG. 16) included in the updated totalized key data 106f to obtain 1,000 + 4,000 + 2,000 + 3,000 + 6,000 + 9. It counts as 000, 000, 12,000 = 3, 7000.

  Note that the counting unit 102c may perform counting in units of hierarchy described in (3-1) in addition to the removal of double counting, and the counting result in this case is shown in the counting result data 106e of FIG. .

  As described above, according to the information processing apparatus 100 according to the present embodiment, even when the targets have a hierarchical structure, it is possible to efficiently total the numerical values of the targets.

  Further, according to the information processing apparatus 100 according to the present embodiment, the content and the number of items of the tying code can be freely set, so flexible aggregation can be performed. In the present embodiment, the aggregation based on the three tying codes has been described, but other aggregations, for example, an aggregation considering only the company code, an aggregation considering the company code and the department code, and the segment code It is also possible to take into account, etc.

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

  In addition, the process performed by this item turns into a pre-processing of (1-2) of [3-1].

  Further, as described above, when the authority setting of the hierarchical object is "do not use", the processing in this item is not performed. That is, the narrowing down of the security 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 identifies the hierarchy level and node identification associated with the input management number. Get code The specific processing is as shown in the following (1-1) to (1-4).

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

  Specifically, as shown in FIG. 31, it is assumed that User B is input as the user ID. In this case, the group identification data acquisition unit 102d1 acquires Company1 and Kouji Group as user group codes associated with User B, as shown by MA11 and MA12 in FIG. 32, respectively.

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

  Specifically, as shown in FIG. 31, it is assumed that organization chart (2) is input as the management number. The user group code acquired by the group identification data acquisition unit 102d1 is Company1 and Kouji Group, as described above. In this case, the hierarchy identification data etc. acquiring unit 102d2 acquires 1 and 21000 as shown by MA 13 in FIG.

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

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

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

(1-4) Repeating Process The repeating unit 102d4 manages a hierarchical object including the upper hierarchy level and the upper node identification code same as the hierarchy level and the node identification code included in the record acquired by the record acquisition unit 102d3 by hierarchical object management. A record obtained by referring to the information 106a and further including a record including the same upper hierarchy level and higher node identification code as the hierarchy level and node identification code included in the acquired record is obtained by referring to the hierarchized object management information 106a. The process is repeated until the hierarchy level and the node identification code included in the lowest layer record are obtained by obtaining the lowest layer record. That is, when the lower structure classification of the corresponding node is <presence of lower structure>, the repeating unit 102d4 acquires a lower-level node list having its own node as the upper hierarchy level and upper node identification code, and restarts this processing. Call. Then, if the lower structure classification of the corresponding node is <no lower structure>, the node of its own is held as hierarchical object security deployment information 106 j.

  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 102 d 4 acquires a two-line record including the information enclosed by a bold frame in FIG. 35 as a record including the same upper hierarchy level and upper node identification code as 1 and 21000. Furthermore, the repeating unit 102d4 may repeat the same process to acquire a further lower layer record, but in the present example, the acquired two-line record includes the lowest hierarchy level 2 Since this is the lowest layer record, the process ends here.

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

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

(2) Second Acquisition Processing The second acquisition unit 102e refers to the hierarchized object expansion information 106b including the management number, hierarchy level, node identification code, and linking code, and the input management number and the first acquisition unit A tying code associated with the hierarchy level and node identification code acquired in 102d is acquired. That is, the second acquisition unit 102e narrows down the information at the end of the hierarchical level of the hierarchical object expansion information 106b according to the hierarchical object security expansion information 106j, and uses only the referenceable data as expansion data.

  Specifically, the input management number is the organization chart (2) as described above. Also, the hierarchy level and the node identification code acquired by the first acquisition unit 102d are “2 and 21100” and “2 and 21200”, as described above. In this case, the second acquiring unit 102e acquires (100, ALL, ALL) in the hierarchical object expanded information 106b of FIG. Further, the second acquisition unit 102e acquires (200, ALL, ALL) in the hierarchical object expanded information 106b of FIG. In this manner, only the data that matches the hierarchical object security expansion information 106 j is narrowed from the original hierarchical object expansion information 106 b.

  The hierarchical object expansion information 106b referred to by the second acquisition unit 102e is not hierarchical object expansion information 106b including records of hierarchy levels 2 to 0, but hierarchical object expansion information 106b including only records of hierarchy level 2 It is. The layered object expansion information 106b including only the record of the hierarchy level 2 can be created by the deployment data creation unit 102f, and the specific creation method is the record acquisition unit 102a1 and the lowest layer record of [3-1]. The processing is the same as the processing performed by the acquisition unit 102a2, and thus the description thereof is omitted.

  As described above, User B refers only to the tying codes (100, ALL, ALL) of company 100 belonging to the construction work group and the tying codes (200, ALL, ALL) of company 200 in the hierarchical structure shown in FIG. 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 can be referred to by the user.

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

  In the setting of the position of the hierarchy, for example, in the example of the organization chart (2) in FIG. 25, is the range that the user can refer to be set as the company-wide layer (that is, reference to all information of companies 100 to 400) Can, be set in the core company layer (can refer to construction business group or manufacturing business group information), or can be set in individual company layer (can refer to any one information of company 100 to 400) Setting).

  For example, in the case of the core company layer of the example of the organization chart (2) in FIG. 25, setting of the number of layers makes it possible to refer to only one of the construction business group and the manufacturing business group That is, it is the setting of whether it is possible to refer to the information of both the construction business group and the manufacturing business group (that is, two hierarchies can be referred to). By being able to refer to both groups, for example, it is possible to perform efficient reference authority setting for a person who is also in a position to double as a construction business and a manufacturing business.

  Continuing on, the record creation unit 102g and the lowest layer data acquisition unit 102h are based on the records of the upper two lines surrounded by thick frames in the hierarchical object expanded information 106b of FIG. → You may create hierarchical object expansion information that has been expanded to 1 → 0 and so on. 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 of [3-1], and thus the description thereof is omitted. The lower two rows of records not surrounded by a thick frame in hierarchical object expansion information 106b of FIG. 37 are not expanded. That is, the expansion information is created only for the upper two rows of records for which User B has the reference authority, while the expansion information is not created for the lower two rows of records for which User B does not have the reference authority.

  Further, the extraction unit 102i may further extract numerical values with reference to the aggregation target data based on the hierarchical object expansion information expanded to the end, and the aggregation unit 102j further performs the extraction. The extracted numerical values may be aggregated. The specific processing method is the same as the processing performed by the extraction unit 102 b and the aggregation unit 102 c of [3-1], and thus the description thereof is omitted.

  In the item [3-2], although the case of one analysis axis (virtual organization) has been described, multi-axis analysis by a plurality of combinations of hierarchical objects (for example, combination of virtual organization and virtual segment) In the case where it is desired to perform the processing of the item [3-2] for each hierarchical object (virtual organization, virtual segment), the reference data range can be narrowed.

As mentioned above, it is as showing to the following 1-4 when the point of this item [3-2] is put together.
1. By setting the authority to the management number / hierarchical level / node identification code of the hierarchical object, it is possible to flexibly set the viewable data range.
2.1 The ability to belong to more than one user group makes it easy to set up a dual role.
3. By performing the procedure of the process according to the flow of a to c below, it is possible to obtain all the upper nodes to be aggregated for the lower nodes having reference authority.
a. Enumerate all end nodes belonging to the hierarchy level, node identification code that has been set authority.
b. Expand upper hierarchical object expansion data only from the enumerated hierarchy levels and node identification codes.
c. Tied-up information that matches hierarchical object expanded data is aggregated.
4. Even with multiple analysis axes, it can be easily extended.

[3-3. Internal transaction judgment processing]
Next, the internal transaction determination process will be described in detail mainly using FIG. 46 to FIG. In the item [3-3], the following flow will be described with items. First, the procedure for creating the aggregation target data 106n will be described mainly with reference to FIGS. Next, internal transaction determination processing for a virtual organization will be described mainly with reference to FIGS. Then, the internal transaction determination processing for the virtual segment will be described mainly using FIGS. Finally, internal transaction determination processing using two axes of a virtual organization and a virtual segment will be described using FIGS. In addition, the process performed by this item [3-3] is the process which subdivided (2) of [3-1] further.

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

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

That is, the aggregation target creation unit 102 o extracts the aggregation target data based on the supplier specific item setting information 106 k and the supplier specific pattern setting information 106 l, and updates the identified destination information. At this time, the processing order is preferably performed in ascending order of determination for each company. Further, as a condition for matching with the aggregation target original data 106m, evaluation is performed in the following procedure 1 to 3. In the following description, the company attribute indicates a supplier code, an item code, an establishment code, a department code, or an analysis code.
1. About the judgment of the company attribute 1, if the company attribute 1 is a required item, the matching of the company attribute 1 = total company attribute 1 = supplier specific pattern setting information 106l of the aggregation target original data 106m is searched, and the company attribute 1 is optional In the case of the item, company attribute 1 = reserved word <ALL> of supplier specific pattern setting information 106l, or company attribute 1 of tally target original data 106m = company attribute 1 of supplier specific pattern setting information 106l Do a matching search.
2. About the judgment of the company attribute 2, if the company attribute 2 is a required item, the matching of the company attribute 2 = total company attribute 2 = supplier specific pattern setting information 106l of the aggregation target original data 106m is searched, and the company attribute 2 is optional In the case of the item, the company attribute 2 = reserved word <ALL> of the supplier specific pattern setting information 106 l or the company attribute 2 of the aggregation target original data 106 m = company attribute 2 of the supplier specific pattern setting information 106 l Do a matching search.
3. Then, the evaluation is performed only for the number of company attributes used by the system (that is, when the company attributes 3 and later exist, the same process as the company attributes 1 and 2 is performed).

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

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

(Extraction process)
The extraction process will be described. As shown in FIG. 47, in the record (indicated by an arrow) on the first line from the top of the supplier specific pattern setting information 106l, the subject lowermost layer identification data includes the company code 100, the office code Tokyo, the department code Eigyo and The analysis code is Buppan, the subject code is 1000: sales, and the supplier code is T1001. Here, referring to the aggregation target 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 , And two records from the top line and the second line (indicated by arrows). Therefore, the aggregation target creation unit 102o is included in the two records of the aggregation target original data 106m (company code 100, office code Tokyo, department code Eigyo, analysis code Buppan, item code 1000: sales and supplier code Extract T1001).

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

  Next, as shown in FIG. 48, in the supplier specific pattern setting information 106l, the aggregation target creation unit 102o selects the second record having the second lowest determination order among the two records including the company code 100 (the Similarly, the extraction process and the addition process are performed on the line As a result, as shown in FIG. 48, the aggregation target creation unit 102 o generates (the partner company code 300, the partner office code Osaka, the partner department code Hanbai 1 and the partner analysis code Kouri) from the top of the aggregation target source data 106 m. Add to the line record (indicated by an arrow).

  Then, as shown in FIG. 49, the aggregation target creation unit 102o selects the record with the youngest determination order among the two records including the company code 200 in the supplier specific pattern setting information 106l (third line from the top Similarly, the extraction process and the addition process are performed on the As a result, as shown in FIG. 49, the aggregation target creating unit 102 o generates (the partner company code 100, the partner office code Tokyo, the partner department code Eigyo and the partner analysis code Buppan) from the top of the aggregation target source data 106 m. Add to the line record (indicated by an arrow).

  Further, the aggregation target creation unit 102o similarly performs the extraction processing and the addition processing on the records in the fourth to sixth rows from the top of the supplier specific pattern setting information 106l, and finally, the aggregation target shown in FIG. Create data 106n.

  As described above, the aggregation target creation unit 102o performs the extraction process and the addition process until the final line of the supplier specific pattern setting information 106l, whereby all the partner codes determined to be intra-group transactions are filled. On the other hand, the transaction specified by a row left unset becomes a transaction with an external general company or the like that is not an intra-group transaction.

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

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

  Moreover, 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 that there is. The specific creation method is the same as (1-1) to (1-4) in [3-1], and thus the description is omitted. The hierarchized object extraction information 106c created by the target extraction creation unit 102p is shown in FIG.

  Here, the internal transaction determination processing can be roughly divided into three processings of subject acquisition processing, partner acquisition processing, and determination processing. In addition, tabulation processing can be performed based on the result of the determination processing. Therefore, in the following, the four processes will be described in this order.

(2-1) Subject Acquisition Process The subject acquisition unit 102 k refers to the hierarchical object extraction information 106 c including the management number, the hierarchy level, the node identification code, and the 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 other party lowest layer identification data are acquired.

  Specifically, in the first to fifth lines of the summary target data 106n shown in FIG. 52, the subject lowermost layer identification data is a combination of (company code 100, office code Tokyo and department code Eigyo). is there. Here, referring to the layered object extraction information 106c shown in FIG. 51, this combination and the association (management number, hierarchy level and node identification code) are included in the record with A (organization chart (4), 1, 31000). Therefore, the subject acquiring unit 102k acquires (organization chart (1, 4), 31000) as information associated with the subject lowermost layer identification data etc. included in the specification of the first to fifth lines from the top of FIG. Do. In the same manner, the subject acquiring unit 102k associates information with the subject lowermost layer identification data (company code 200, office code Tokyo, and department code Seizou 1) included in the specification of lines 6 to 7 from the top of FIG. As shown in FIG. 51, “B” in FIG. 51 is included in the record (Organizational Chart (4), 1, 31000), and the lowermost-layer identification data (FIG. As information linked with the company code 200, the office code Osaka and the department code Seizou 2), obtain (organization chart (4,) 1, 32000) included in the record with D in FIG. 51, and from the top of FIG. As information linked with the subject lowest layer identification data (company code 300, office code Osaka and department code Hanbai 1) included in the specification of lines 10 to 13, Included in the record marked with 1 C (organizational chart (4), 1,32000) acquires. In the records with B and D in FIG. 51, the establishment code is <ALL>, which means that any information may be included, and more specifically, in the present example, If you mean Tokyo or Osaka.

  Here, in the “self-organized” column of the tissue matching result in FIG. 52, the correspondence between each item in FIG. 52 and each record in FIG. 51 is indicated by A to D, but this notation Since it is added, the aggregation target data 106 n may not include the tissue matching result.

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

(2-2) Partner Acquisition Processing The partner acquisition unit 1021 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, The management number, hierarchy level and node identification code associated with the other party lowest layer identification data included in the aggregation target data 106n including the other party lowest layer identification data are acquired.

  Specifically, in the sixth and tenth lines from the top of tallying target data 106n shown in FIG. 53, the other party lowest layer identification data is (the other company code 100, the other business office code Tokyo, and the other department code It is a combination called Eigyo). Here, referring to the layered object extraction information 106c shown in FIG. 51, this combination and the association (management number, hierarchy level and node identification code) are included in the record with A (organization chart (4), 1, 31000). For this reason, the other party acquiring unit 102l uses (organization chart (1, 4), 31000) as information to be associated with the other party lowermost layer identification data included in the first and sixth lines from the top of FIG. get. In the same manner, the other party acquiring unit 102l determines the other party lowest layer identification data (the other company code 200, the other business office code Tokyo, and the other department code Seizou 1) included in the specification of the first and second lines from the top of FIG. As association information, acquire (organization chart (4,) 1, 31000) included in the record with B in FIG. 51 and obtain the other party included in the specification of the fourth and eighth lines from the top of FIG. The information included in the record with C in FIG. 51 (organizational chart (4), 1, 32000) as information to be associated with lower layer identification data (the partner company code 300, partner office code Osaka and partner department code Hanbai 1) The other party lowest layer identification data (the other company code 200, the other business office code Osaka, and the other department code) which are acquired and included in the specification of the twelfth line from the top of FIG. As a link attached information Eizou2), included in the record marked with D in FIG. 51 (organizational chart (4), 1,32000) acquires.

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

  In this manner, the partner acquisition unit 1021 can perform matching with the partner organization information of the aggregation target data 106n based on the hierarchical object extraction information 106c, and can obtain a matching result regarding the partner organization.

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

  Specifically, for example, regarding the first line of the summary target data 106n in FIG. 55, the management number, the hierarchy level, and the node identification code acquired by the subject acquiring unit 102k are as follows (organization chart (4), 1, 31000), while the management number, hierarchy level and node identification code acquired by the other party acquisition unit 102l are also the combination (organization chart (4), 1, 31000), and the combination of both is It is exactly the same. In this case, the determination unit 102m determines that the transaction in the first line is an internal transaction within the group.

  The contents will be described as follows using the tissue matching result in FIG. That is, the tissue matching result of the specification in the first line from the top of FIG. 55 is A for the own tissue and B for the partner tissue. Here, referring to the hierarchical object extraction information 106c of FIG. 54, the record with A and the record with B are in an internal business relationship as shown by MA 14 (ie, management number, hierarchy The combination of level and node identification code is the same relationship). As described above, since the transaction specified in the first specification from the top of FIG. 55 can be determined to be an internal transaction, the word "internal" is attached to the column "determination of inside and outside of organization" of the organization matching result. ing.

  In the same manner, the determination unit 102m determines that the second, sixth, eighth, and twelfth transactions from the top of FIG. 55 are internal transactions, while the third to fifth rows, The transactions on the seventh, ninth to eleventh and thirteenth rows are determined to be external transactions.

  In this manner, the determination unit 102m determines that the combination of the own organization and the counterpart organization is the same as the internal transaction when the “hierarchical level” and the “node identification code” are the same in the hierarchical object extraction information 106c and the external transaction otherwise. judge. In addition, it determines with the transaction specified with the line in which the other party organization is unset as 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 a transaction between targets is an internal transaction within a group. In this example, internal transaction determination processing in the “middle class” in the virtual organization (ie, in FIG. 42, internal transactions between the company 100 Tokyo sales belonging to the Kanto area and one company 200 production) In the same way, a process of determining a transaction between a company 300 Osaka Sales 1 part belonging to the Kansai area and a company 200 production 2 division as an internal transaction has been described. It may be a hierarchy or may be a lower hierarchy.

  In the case of internal transaction determination processing in the “upper layer”, the management number, the hierarchy level and the node identification code can be Hierarchical object extraction information 106c consisting of four records of 0), 30000) can be created. Therefore, the combination of the management number, the hierarchy level, and the node identification code acquired by the subject acquiring unit 102k with reference to the hierarchical object extraction information 106c, and the partner acquiring unit 102l with reference to the hierarchical object extraction information 106c. The combination of management number, hierarchy level and node identification code is always the same. For this reason, all the items corresponding to the supplier-specific pattern setting information 106l among the aggregation target data 106n (specifications in the first to second lines from the top of the aggregation target data 106n, the fourth line, the sixth line , Line 8, line 10 and line 12) are internal transactions. On the other hand, the items that do not correspond to the supplier specific pattern setting information 1061 (the third line from the top of the aggregation target data 106n, the fifth line, the seventh line, the ninth line, the eleventh line) The itemized statement and the itemized statement on line 13 are external transactions.

  On the other hand, in the case of the internal transaction determination process in the "lower hierarchy", the management number, the hierarchy level and the node identification code can be obtained by inputting the hierarchy level "2" when creating the hierarchical object extraction information 106c. (Organization chart (4), 2, 3 1100), (Organization chart (4), 2, 31200), (Organization chart (4), 2, 32100) and (Organization chart (4), 2, 32200) respectively. Hierarchical object extraction information 106 c consisting of certain four records can be created. Therefore, the combination of the management number, the hierarchy level, and the node identification code acquired by the subject acquiring unit 102k with reference to the hierarchical object extraction information 106c, and the partner acquiring unit 102l with reference to the hierarchical object extraction information 106c. Since the combination of the management number, the hierarchy level and the node identification code is always different, the transaction in all the items of the aggregation target data 106n is an external transaction.

  An image diagram of internal transaction determination processing in each of the “upper hierarchy”, the “middle hierarchy” and the “lower hierarchy” is shown in FIG. As shown in FIG. 65, the amount of internal transactions increases as the internal transaction determination process 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 upper level organization are at the same level, so the hierarchy level to be extracted is made higher (closer to 0) This is because when extracted, data to be determined as an internal transaction will increase. By this, when the nodes at the hierarchical level to be extracted are virtually regarded as one company / one segment, it is possible to determine the transaction between the inner nodes as the internal transaction and cancel the cancellation.

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

  Then, according to the information processing apparatus 100 according to the present embodiment, for example, the contents and the number of items of the subject lowest layer identification data and the other party lowest layer identification data can be arbitrarily set, so flexible internal transaction determination processing can be performed. It can be carried out. Specifically, conventionally, only internal transaction determination processing (for example, processing for determining that the 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 company code, office code and department code are set as company information and partner information, internal transactions with fine granularity are performed. A determination process (for example, a process of determining that the transaction of “company 100, Tokyo head office, sales department” and “company 200, Osaka head office, 2 production units” is an internal transaction) can be performed.

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

(2-4) Counting Process The counting unit 102 n counts the numerical value associated with the lowermost layer identification data of the subject included in the counting target data 106 n when they are the same.

  Specifically, the same case is a combination of the management number, the hierarchy level and the node identification code acquired by the subject acquiring unit 102k, and the management number, the hierarchy level and the node identification code acquired by the other party acquiring unit 102l. And are the same. In the case of the aggregation target data 106n of FIG. 55, when the details of the first line, the second line, the sixth line, the eighth line, and the twelfth line from the top, which are internal / external determination inside, are the same. Applicable Referring to FIG. 55, the amount associated with the entity lowest layer identification data (company code, office code and department code) included in these specifications is ¥ 10,000, ¥ 15,000, and ¥ 50,000, respectively. It is yen, 70,000 yen and 110,000 yen. The totaling unit 102n may total all these amounts and calculate it as ¥ 255,000, but as described below, a combination in which the combination of management number, hierarchy level, node identification code and item code is the same It is preferable to add up the amount of money each time.

  That is, in FIG. 55, the specifications in the first and second rows from the top are a combination of the management number, hierarchy level, node identification code, and item code (organization chart (1, 4), 1, 31000, sales), The aggregation unit 102 n aggregates the amounts included in the first and second lines of the statement as 10,000 + 15,000 = 25,000 yen. Similarly, in FIG. 55, the sixth line from the top is a combination of the management number, hierarchy level, node identification code and item code (organization chart (1, 4), 1, 31000, purchase), The aggregation unit 102 n aggregates the amount of money included in the details of the sixth line to 50,000 yen. Similarly, in FIG. 55, the eighth line from the top is a combination of the management number, hierarchy level, node identification code, and item code (organization chart (1, 4), 1, 32000, purchase), The aggregation unit 102 n aggregates the amount of money included in the specification of the eighth line into 70,000 yen. Similarly, in FIG. 55, the specification in the 12th line from the top is a combination because the management number, hierarchy level, node identification code and item code are (organization chart (1, 4), 1, 32000, sales). The part 102n totals the amount of money included in the specification of the 12th line as 110,000 yen. Thus, as shown in the tabulation result data 106 o of FIG. 56, the tabulating unit 102 n determines that the combination of the management number, the hierarchy level, the node identification code, and the subject code is 25,000 yen, 50, It is possible to calculate the internal transaction amount of ¥ 000, ¥ 110,000 and ¥ 70,000.

  Further, the aggregation unit 102 n may also aggregate the amount of money for each specification in which the combination of the management number, the hierarchy level, the node identification code, and the item code is the same for internal and external determinations. Thus, as shown in the aggregation result data 106 o of FIG. 56, the aggregation unit 102 n is 20,000 yen or 130,000 for each item in which the combination of management number, hierarchy level, node identification code and item code is the same. It is possible to calculate the external transaction amount of yen, 310,000 yen and 80,000 yen.

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

(3) Internal transaction determination process for virtual segment This item is different from the process described below only in the following items, and the process itself is the same as (2), so detailed description will be omitted. First, the lowermost layer identification data included in the hierarchical object extraction information 106c is not the "company code, the office code and the 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. Further, in the aggregation target data 106o, items used for matching regarding the own organization are “analysis code” as shown in FIG. 58 instead of “company code, office code and department code”. Then, in the aggregation target data 106o, items used for matching regarding the partner organization are not the partner company code, partner office code and partner department code but the partner analysis code as shown in FIG. As described above, by using the “analysis code” included in the hierarchical object extraction information 106 c and the “analysis code” and the “other party analysis code” included in the aggregation target data 106 o, the same processing as (2) is performed. Internal transaction determination processing and aggregation based on the result can be performed. The content of the internal transaction determination process is shown in FIG. 57 to FIG. 61, and the result of tabulation is shown in FIG.

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

(4) Internal transaction determination processing using two axes of virtual organization and virtual segment Combining the organization matching result of (2) and the segment matching result of (3), internal transaction determination processing using two axes Can be done as.

  FIG. 63 shows the tissue matching result of (2) and the segment matching result of (3) together. By referring to FIG. 63, three types of aggregation results, “total sum”, “internal transaction amount (within segment)” and “internal transaction amount (outside segment)” can be obtained in consideration of internal / external determination and internal / external determination be able to. The "total sum" is a simple sum not determined by internal or external determination or segment determination. The “internal transaction amount (within segment)” is the total amount of internal / external determination “internal” and internal / external determination “internal”. “Internal transaction amount (outside segment)” is the total amount of internal and external determinations “internal” and internal and external determinations “external”.

  In the table of FIG. 63, in the case of calculating “overall total amount”, the amount of money will be totaled for all items. Here, the processing of “total sum” is performed for each specification 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 item code are the same. May be That is, the following tabulation may be performed for all the details (details in lines 1 to 13) in the table of FIG. In FIG. 64, the total sum 45,000 yen is the total value of the amounts included in the first to third lines from the top of FIG. 63, and the total sum 70,000 yen is from the top of FIG. The total value of 110,000 yen is the total value of the amounts included in the sixth to seventh lines from the top of Fig. 63 420,000 yen is the total value of the amounts included in the specification of lines 10 to 13 from the top of FIG. 63, and the total sum of 150,000 yen is the specification of lines 8 to 9 from the top of FIG. It is an aggregate value of the included amount.

  In the table of FIG. 63, when calculating “internal transaction amount (within a segment)”, there is no item whose internal / external determination is “internal” and internal / external determination is “internal”, so there is an amount of money to be totaled do not do.

  In the table of FIG. 63, when the “internal transaction amount (outside segment)” is calculated, the first and second lines from the top, line 6 where the internal / external determination is “internal” and the internal / external determination is “external” The amounts will be summarized for the details of the eighth and twelfth lines. Here, in the processing of "internal transaction (outside segment)", the combination of the virtual organization management number, hierarchy level and node identification code, virtual segment management number, hierarchy level and node identification code and item code are the same. You may go for every specification. That is, the following tabulation may be performed for the first to second, sixth, eighth, and twelfth lines from the top of the table in FIG. In FIG. 64, the internal transaction amount (outside segment) of 25,000 yen is the total value of the amounts included in the first and second lines from the top of FIG. 63, and the internal transaction amount (outside segment) of 50,000 yen. Is the total value of the amounts included in the 6th line from the top of Figure 63, and the internal transaction amount (outside the segment) of 110,000 yen is the amount of the amount included in the 12th line from the top of Figure 63 It is a totalized value, and the internal transaction amount (outside the segment) of 70,000 yen is a totalized value of the amounts included in the details of the eighth line from the top of FIG.

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

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

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

That is, the extraction unit 102 q extracts conversion target data based on the conversion item setting information 106 p and the conversion pattern setting information 106 q, and the conversion unit 102 r updates the specified conversion destination attribute information. At this time, it is preferable that the processing order is performed in ascending order of determination order of company. Further, as a condition for matching with the conversion target data 106r, evaluation is performed according to the following procedure 1 to 3. In the following description, the conversion source attribute indicates a supplier code, an item code, an establishment code, a department code, and an analysis code.
1. Regarding the determination of conversion source attribute 1, when conversion source attribute 1 is an essential item, a match of conversion source attribute 1 of conversion target data 106r = conversion source attribute 1 of conversion pattern setting information 106q is searched, and conversion source attribute 1 If the item is an optional item, the conversion source attribute 1 of the conversion pattern setting information 106 q becomes a reserved word <ALL>, or the conversion source attribute 1 of conversion target data 106 r = conversion source attribute 1 of conversion pattern setting information 106 q Search for a match.
2. Regarding the determination of conversion source attribute 2, when conversion source attribute 2 is an essential item, a match of conversion source attribute 2 of conversion target data 106r = conversion source attribute 2 of conversion pattern setting information 106q is searched, and conversion source attribute 2 If the item is an optional item, the conversion source attribute 2 of the conversion pattern setting information 106 q = reserved word <ALL> or the conversion source attribute 2 of conversion target data 106 r = conversion source attribute 2 of conversion pattern setting information 106 q Search for a match.
3. Thereafter, evaluation is performed only for the number of conversion source attributes used by the system (that is, when conversion source attributes 3 and thereafter exist, processing similar to conversion source attributes 1 and 2 is performed).

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

  Among the conversion source data included in the three records of the company code 100 in the conversion pattern setting information 106 q shown in FIG. Preferably, extraction is performed. That is, the extraction unit 102 q first converts the conversion source data (company code 100, supplier code ALL, subject code 1000: sales, office code Tokyo, department code) included in the first record from the top including determination order 1 The following extraction process and conversion process are performed on Eigyo and analysis code Buppan).

(Extraction process)
As shown in FIG. 70, in the first record (indicated by an arrow) from the top of the conversion pattern setting information 106q, the conversion source data is as described in the previous paragraph (company code 100, customer code ALL, subject Code 1000: Sales, establishment 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 two records (indicated by arrows) in the first and third lines from the top. Therefore, the extraction unit 102q includes (company code 100, customer 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, processing performed by the conversion unit 102r will be described. In conversion pattern setting information 106q shown in FIG. 70, conversion destination data associated with the extracted (company code 100, customer code T1001, subject code 1000: sales, office code Tokyo, department code Eigyo, and analysis code Buppan) , (G_Hanbai). Therefore, as indicated by the first and third lines (indicated by arrows) from the top of the conversion target data 106r in FIG. 70, the conversion unit 102r converts the conversion source code (company code 100, transaction) acquired by the extraction unit 102q. The destination code T1001, the subject code 1000: sales, the office code Tokyo, the department code Eigyo and the analysis code Buppan are converted into conversion destination data (G_Hanbai).

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

  Furthermore, as illustrated in FIG. 72, the extraction unit 102 q and the conversion unit 102 r determine, in the conversion pattern setting information 106 q, the third lowest determination order and the string among the conversion source data included in the three records of the company code 100. The extraction process and the conversion process are similarly performed on the attached conversion source data (that is, the conversion source data included in the third record from the top of the conversion pattern setting information 106 q). As a result, the conversion unit 102 r converts the conversion source data extracted by the extraction unit 102 q into conversion destination data (G_Sonota), as indicated by the second line from the top in FIG. 72 (indicated by an arrow).

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

  In the case where business establishments and departments of each company can be linked as they are in a hierarchical structure as in a virtual organization, there is little need to process the item [3-4]. On the other hand, when it is desired to perform aggregation on a common analysis axis in the whole group as in a virtual segment, managing association with codes of individual companies makes setting complicated. Therefore, by converting the common segment code into a common segment code by the processing of this item [3-4], it is possible to easily set analysis axes in various sections by assigning the common segment code to the virtual segment .

  Specifically, assigning a common segment code to a virtual segment means, for example, the following processing. As shown in Fig. 74, common segment code of "system business" is set for SI business and PKG development of company A and development department of company B, while "support business department of company B" Set the common segment code of “Support business”. Then, as shown in FIG. 74, the common segment code “system business” is allocated to the “system development business” which is a virtual segment, while the common segment code “support business” is allocated to the “support business” which is a virtual segment. Then, it is possible to conduct business analysis focusing on 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). Thus, for example, as described in the previous paragraph, each target can be classified into the common segment codes “system development business” and “support business”, and business analysis can be performed by focusing on the business content. Also, for example, a transaction among three targets of “SI business and PKG development of company A and development business of company B” belonging to the common segment code “system development business” is determined to be an internal transaction and is eliminated and eliminated, In the accounting process, transactions between three targets belonging to the common segment code “system development business” and the support division of company B belonging to the common segment code “support business” are judged as external transactions and no elimination is performed. You can also do

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

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

  According to the information processing apparatus 100 according to the present embodiment, reorganization of a group company can be simulated. Specifically, when the information processing apparatus 100 according to the present embodiment deals with a corporate group, when an external company is acquired as a subsidiary by reorganization or merger and acquisition (M & A) by mergers and acquisitions of companies in the group It is necessary to consider the company's fluctuations, etc. Under the present circumstances, according to the information processing apparatus 100 which concerns on this embodiment, as shown in FIG. 75, a structure | tissue chart is copied and a structure | tissue change is performed before structure | tissue reorganization (organization before reorganization (2) of FIG. 75). And the post-reorganization (after-reorganization (2) 'in FIG. 75) can be compared. In FIG. 75, company 2 is a company belonging to group core 1 before the reorganization, but is a company belonging to group core 2 after reorganization.

  Further, according to the information processing apparatus 100 according to the present embodiment, the business analysis can be performed by totaling the amount of money by the three axes of organization × segment × subject by combination of functions of organization information and segment information. Specifically, according to the information processing apparatus 100 according to the present embodiment, as shown in FIG. 76, information on a product / brand is placed on the vertical axis, and information on a store is placed on the horizontal axis, and data on the balance is the height of the balance. By visualizing with, it is possible to create multiple data. By creating such multi-objective data, it becomes possible to grasp the current status of balance by brand by store. This makes it possible to establish a sales strategy for each brand for each store.

[4. Other embodiments]
The present invention may be practiced in various different embodiments within the scope of the technical idea described in the claims in addition to the embodiments described above.

  For example, among the processes described in the embodiment, all or part of the process described as being automatically performed may be manually performed, or all the processes described as being manually performed. Alternatively, some of them can be performed automatically by known methods.

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

  Further, with regard to the information processing apparatus 100, each component shown in the drawings is functionally conceptual, and does not need to be physically configured as illustrated.

  For example, with regard to the processing functions included in the information processing apparatus 100, in particular each processing function performed by the control unit 102, all or any part thereof is realized by a CPU and a program interpreted and executed by the CPU. May also be implemented as wired logic hardware. The program is stored in a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the processing described in the present embodiment, and the information processing apparatus as necessary. 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 HDD (Hard Disk Drive). The computer program is executed by being loaded into the RAM, and cooperates with the CPU to configure the control unit.

  Also, the 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 a part of the computer program as needed. is there.

  Furthermore, the program for executing the processing described in the present embodiment may be stored in a non-temporary computer readable recording medium, or may be configured as a program product. Here, the "recording medium" means a memory card, a universal serial bus (USB) memory, a secure digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an erasable programmable read only memory (EPROM), and an EEPROM (registration). Trademarks (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Versatile Disk), and Blu-ray (registered trademark) Disc etc. Any "portable physical media It is intended to include. Therefore, a recording medium storing a program for executing the processing or the processing method as 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 format such as source code or binary code. Note that the “program” is not necessarily limited to one that is configured in a single way, and achieves its function in cooperation with a separate program represented by a plurality of modules or libraries or a separate program represented by the OS. Including things. In addition, as a specific configuration and reading procedure for reading the recording medium in each device shown in the embodiment, an installation procedure after reading, and the like, a known configuration and procedure can be used.

  The 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, storage means such as optical disks, etc. Stores programs, tables, databases, files for web pages, etc.

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

  Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them may be functionally or physically in any unit in accordance with various additions or according to functional load. It can be distributed and integrated. That is, the embodiments described above may be implemented in any combination, and the embodiments may be implemented selectively.

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

100 information processor
102 control unit
102a Acquisition unit
102a1 Record acquisition part
102a2 lowest layer record acquisition part
102a3 Record making department
102a4 lowest layer data acquisition part
102b Extraction unit
102c Totaling Department
102d 1st acquisition department
102d1 Group identification data acquisition unit
102d2 Hierarchy identification data etc. acquisition unit
102d3 record acquisition part
102d4 Repeating unit
102e Second acquisition unit
102f Expansion data creation part
102g Record making department
102h lowest layer data acquisition unit
102i extraction unit
102j Summary part
102k Subject Acquisition Department
102l Opponent Acquisition Department
102m judgment unit
102n tabulation unit
102o tally target creation department
102p Target extraction creation unit
102 q extraction unit
102r converter
104 Communication interface
106 storage unit
106a Hierarchical object management information
106b Hierarchical Object Expansion Information
106c Hierarchical Object Extraction Information
106d Data to be calculated
106e Summary result data
106f Summary key information data
106g User Group Affiliation Information
106h Authority setting information
106i Authority extraction information
106j Hierarchical Object Security Deployment Information
106k Customer specific item setting information
106l Customer specific pattern setting information
106m Summary target source data
106n Summary target data
106o Summary result data
106p Conversion item setting information
106q Conversion pattern setting information
106r Conversion target data
106s conversion complete data
108 Input / output interface section
112 input device
114 output device 200 server 300 network

Claims (1)

An internal transaction determination apparatus comprising a control unit, wherein
The control unit
Hierarchical structure identification data for identifying a hierarchical structure formed by forming a hierarchy of objects in the lowermost layer and objects in the upper layer; hierarchical identification data for identifying each hierarchy in the hierarchical structure; and the object A lowest layer for identifying an object subject that is a subject of a transaction, with reference to object extraction data including object identification data for identification and lowest layer identification data for identifying an object of the lowest layer Subject lowest layer identification included in tallying object data including subject lowermost layer identification data that is identification data and lowest layer identification data that is the lowest layer identification data for identifying a partner object that is a transaction partner Subject acquisition means for acquiring hierarchical structure identification data, hierarchy identification data, and object identification data associated with data;
Hierarchical structure identification data associated with the lowest other-layer identification data included in the aggregation target data, hierarchical identification data, hierarchical identification data, and target identification data with reference to the target extraction data;
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 other party acquisition unit, A determination unit that determines a transaction with the counterpart object as an internal transaction within the group;
Equipped with
The lowest layer identification data includes at least one of business establishment identification data for identifying an establishment in a certain company and division identification data for identifying a division in a certain company.
An internal transaction determination device characterized by

Images