JPH0778212A - Form output device - Google Patents

Abstract

(57) [Summary] [Purpose] By simply specifying the record name etc. of the summary record corresponding to the aggregation level, aggregation is performed to the higher level according to the parent-child relationship of the specified aggregation level, The totaled result is output in a hierarchical structure according to the specified contents according to the order of the record names. [Structure] The expanded totalization processing unit 11 corresponds to the totalization target code read from a predetermined file based on the definition contents of table A (totalization record name corresponding to the totalization level, totalization target code corresponding to this record name). When data is aggregated to the corresponding summary record and this summary result is aggregated to a code higher than that and to the code, the arrangement of the record name at the higher level is determined and the upper summary or the lower summary is performed accordingly. . The print processing unit 13 is the tally file 1
The contents of 2 are printed as defined in Table A.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a form output device for accumulating record data from, for example, an accounting file, a personnel file, etc. in an office computer, a personal computer or the like, and outputting the totalized result as a form.

[0002]

2. Description of the Related Art Conventionally, in an office processing device such as an office computer or a general-purpose computer, an accounting file,
Various types of files such as personnel files, sales slip files, inventory files, etc. are stored and managed, but the record structure that constitutes each file is different for each file.
The same record form (records in which each item that constitutes a record matches) is collectively managed as a separate file. Here, when you specify an arbitrary item and read the record containing that item from the file and classify and aggregate it, even if you make a classification code system that makes it easy to classify and aggregate the data in the item first, As a result, the classification does not actually fit, and it is not possible to perform the classification and aggregation as it is. Therefore, conventionally, as a countermeasure, a code conversion table for classification and aggregation is provided, and a method of performing classification and aggregation by converting the code system suitable for classification and aggregation using this code conversion table is widely adopted at present.

[0003]

However, in the method using the code conversion table, a system engineer who is an expert has to create a code system (conversion table) for classification and aggregation. That is, creating a classification code system according to various business needs requires extremely specialized and sophisticated knowledge, so it is extremely difficult for a general user's business person to create it. The current situation was that we had to ask the system engineer to create it. An object of the present invention is to perform aggregating to a higher level according to the parent-child relationship of the specified aggregation level simply by arbitrarily specifying the record name of the aggregation record corresponding to the aggregation level, and the aggregation result. Is to be output in a hierarchical structure according to the specified contents according to the order of the record names.

[0004]

Means for Solving the Problems The means of the first invention is as follows. (1A), the specifying means arranges and specifies the record name of the totalized record at an arbitrary position corresponding to the totaling level, and specifies the totaling target corresponding to this record name. (2A), the first totaling means reads out data corresponding to the totaling target designated by the designating means from a predetermined file and totalizes the records having a record name corresponding to the totaling target. (3A), when the totaling direction determining means totals the totaling results of the records totaled by the first totaling means into higher level records, the order is based on the arrangement position of the upper level record name. Decide whether to aggregate in the direction or in the opposite direction. (4A), the second totaling means converts the totalized result of the records totaled by the first totaling means into a record having a record name at a higher level arranged in the totaling direction determined by the totaling direction determining means. Tally. (5A), the output means outputs the respective records totaled by the second totaling means according to the arrangement order of the record names designated by the designating means. The output means outputs each record totaled by the second totaling means according to the arrangement order of the record names designated by the designating means, and corresponds to the totaling direction determined by the totalizing direction determining means. You may make it output in a format. The means of the second invention is as follows. (1B), the designating unit arbitrarily designates the record name of the totalized record in correspondence with the totalization level, and designates the totalization target in correspondence with this record name. (2B), the first totaling means reads out the data corresponding to the totaling target designated by the designating means from a predetermined file and totalizes the records having the record names corresponding to the totaling target. (3B), the second tabulation means tabulates the tabulation results of the records tabulated by the first tabulation means into the records having the record names at a higher level than that. (4B), the output unit outputs each record totaled by the second totaling unit according to the arrangement order of the record names designated by the designating unit, and in a format according to the connection level of the totaling level of each record. Output.

[0005]

The operation of the means of the first invention is as follows. Now, in order to obtain the form desired by a person in charge of business who does not have specialized knowledge, the record name of the aggregated record is arranged and specified at an arbitrary position in accordance with the aggregation level, and in addition to this record name Specify the aggregation target. In this case, it is assumed that the record names of the aggregation records are arranged vertically in the table format. Then, the data corresponding to the specified aggregation target is read from the predetermined file and aggregated into the record having the record name corresponding to the aggregation target.
Next, the aggregation result of this aggregated record is aggregated to the record at a higher level than that. Whether to aggregate in the forward direction or the backward direction based on the placement position of the record name at this upper level. In this case, it is determined whether the upward totalization is performed in the upward direction or the downward totality is performed in the downward direction, and the totalized records are the records of the record names in the upper level arranged in that direction. Each record aggregated by this,
The form is output according to the arrangement order of the record names as specified. The operation of the means of the second invention is as follows.
Now, if you specify the record name and aggregation target in the same way as above, the data corresponding to this aggregation target will be read from the specified file and aggregated into the records with the record name corresponding to this aggregation target, and this aggregation result Will be aggregated to the record with the record name at a higher level than that.
Each record thus aggregated is output according to the arrangement order of the designated record names, and is also output in a format according to the connection level of the aggregation level of each record. Therefore, by simply specifying the record name etc. of the summary record corresponding to the aggregation level, aggregation is performed to the higher level according to the parent-child relationship of the specified aggregation level, and the aggregation result is It is possible to output in a hierarchical structure according to the specified contents according to the arrangement order.

[0006]

[First Embodiment] A first embodiment will be described below with reference to FIGS. FIG. 1 is a block diagram of the data processing apparatus according to this embodiment. This data processing device constitutes an office computer, and a person in charge of business who does not have specialized knowledge can simply specify the aggregation target etc. corresponding to the aggregation level using the aggregation definition table. The records corresponding to the definition contents of the tabulation definition table are read out from a predetermined file, the records are tabulated in a hierarchical structure according to the tabulation level, and the tabulation result is printed out as form data. The input unit 1 is a key input device for inputting various data and commands, and the data input from the input unit 1 is fetched by the parameter setting unit 2 and processed, and is displayed and output on the display unit 3. The input unit 1 gives a start command to the parameter setting unit 2 in response to a predetermined key operation.

The parameter setting unit 2 operates in response to a start command from the input unit 1 and defines a record name of a totalized record, a totaling target, etc. in order to instruct arbitrary totalization of records desired by a person in charge of business. Definition table (A in this embodiment
A table) is generated according to the data input from the input unit 1, is displayed and output from the display unit 3, and is set in the parameter file 4. It should be noted that the table A will be described in detail later, so that it will be briefly described here. For example, in order to print out the “income statement” as shown in FIG. 2 (A) as a desired form, a table A as shown in FIG. 3 (A) is defined and shown in FIG. 2 (B). In order to print out such a form, a table A as shown in FIG. 3B is defined. Here, the table A is a definition table that defines the total contents according to the output image of the form, and the total level A,
The record name of the totalized record and the item contents (target item code) of the totaled target items extracted as totals are defined corresponding to B and C. Also, the hierarchical structure of the aggregation level is A
There is a relation of>B> C, and the parent-child relation (upper / lower relation) of the records is represented by this aggregation level. Note that when defining the record name corresponding to the aggregation level, the record name is arranged according to the parent-child relationship, but the arrangement position of the record name is arbitrary, and in this embodiment, the highest level A
The record name corresponding to # may be arranged in the first row of table A as shown in FIG. 3A, or may be arranged in the bottom row of table A as shown in FIG. 3B. Here, the aggregation result of the records corresponding to each record name of the A table is aggregated to the upper level record having a parent-child relationship with the record according to the definition content of the A table. At that time, if the highest-level record name is arranged in the first row of the table A as shown in FIG.
The records corresponding to the upper-level record names arranged in the upward direction are aggregated, but as shown in FIG. 3 (B),
If the record name of the highest level is arranged in the bottom row of the table A, the record corresponding to the record name of the upper level arranged in the downward direction is aggregated. Below, FIG. 3 (A)
As shown in Fig. 3, the total is calculated according to the definition contents as shown in Fig. 3.
When the total according to the definition contents as shown in (B) is referred to as “lower total”, FIG.
Shows an example of the form output when the data is tabulated below.

The parameter file 4 has its basic format (ruled line data, etc.) fixedly stored in advance by the maker side corresponding to the table A, and also the table A of various forms arbitrarily input from the input section 1. A correspondence table is stored in which the parameter data and various form names arbitrarily input from the input unit 1 are associated with the A-table parameter data. The parameter file 4 also stores a form arbitrarily designated from the input unit 1 at the time of printing the form in association with the A table parameter data.

The table structure analysis unit 5 operates in accordance with the start command input from the input unit 1 when printing the form, and according to the A table parameter data corresponding to the form name arbitrarily designated as the output target, according to the aggregation level. The hierarchical structure and the like are analyzed, and the configuration file 6 is created based on the analysis result. The configuration file 6, which will be described in detail later, is made up of various configuration records that represent the correspondence between the items to be aggregated in Table A and the aggregate records corresponding to them, and the vertical relationship in the hierarchical structure of the aggregation level. is there. Further, the table structure analysis unit 5 reads the print format from the parameter file 4 and sets it in the print format memory 7. After that, the table structure analysis unit 5 gives a start command to the expansion file creation unit 8.

In the print format memory 7, a format table for creating a form format is set corresponding to the form name as shown in FIG. 4 in addition to the print form set arbitrarily. By referring to the contents of the table, a form format (ruled line format) according to the aggregation level is generated for each of the upper and lower totals. Here, in the format table, the start point digit and the end point digit are set in order to specify the range in which the record name of the totalized record is arranged corresponding to the “name”. Further, the starting point digit is set in order to generate a ruled line for bundling that divides the aggregation levels A, B, and C corresponding to the aggregation levels A, B, and C. Further, in order to specify the range in which the value of the totalized record is arranged, the starting point digit and the ending point digit are set respectively. The format table is set by the table structure analysis unit 5 after being arbitrarily input from the input unit 1 and written in the parameter file 4. For example, the format table shown in FIG. 4 is for the “income statement”. Is set arbitrarily. In this way, if the starting point digit of the ruled line is shifted according to the totaling level, this "shift" can express the hierarchical structure of the totaling level. The vertical ruled lines have the same digit position for each level regardless of whether they are counted up or down, but the horizontal ruled lines are generated so that they are located above the vertical ruled lines in the upper tabulation and below in the lower tabulation. .

The expansion file creating section 8 uses the data file 9
The totalization target file is specified from among the various source files A ... N that compose the file, and the records extracted from the totalization target file are written into the expansion file 10 as expanded records one by one. When the expansion file 10 is created in this way, the expansion file creating unit 8 gives a start command to the expansion aggregation processing unit 11. Each record of the expansion file 10 is composed of a classification code and a data value, and this classification code corresponds to the aggregation target item code defined in the table A.

The development tabulation processing unit 11 refers to the configuration file 6 and sequentially creates a tabulation record for each record based on the contents of the development file 10 and writes it to the tabulation file 12. When the totalization file 12 is created by this, the expansion totalization processing unit 11 gives a start instruction to the print processing unit 13. The print processing unit 13 creates the form by printing out the contents of the totalization file 12 from the printer 14 together with the form format record by record according to the print format set in the print format memory 7.

Next, the operation of this embodiment will be described. First,
When the input unit 1 is instructed to create the table A in order to obtain the desired form, the parameter setting unit 2 operates in response to this. First, when creating the A table, the parameter setting unit 2 displays and outputs a table frame and the like according to the basic format of the A table read from the parameter file 4. Now, in the state where the basic format of table A is displayed and output, the person in charge of business inputs the parameter data of table A from the input unit 1. FIG. 3 is a display example when the parameter data is input in the table A. Here, in the basic format of table A, the heading portion in the column direction displays the heading character strings of “totaling level A”, “totaling level B”, and “totaling level C” corresponding to the three levels of totaling. The heading character strings of “management unit” and “target code” are displayed. Now, in the data input example shown in FIG. 3A, “Profit” is entered as the record name of the aggregate record in the row No. “01” corresponding to the aggregation level A and the row corresponding to the aggregation level B. The record name "sales" is entered in No. "02", the record name "expense-" is entered in line No. "05", and the record name "product sales" is entered in line No. "03" corresponding to the aggregation level C. , The record name “part sales” is entered corresponding to the line No. “04”, and the record name “general expense” is entered corresponding to the line No. “06”. As described above, the record names of the aggregated records are entered in the table A in correspondence with the aggregation levels A, B, and C.

When the record names of the totalized records are entered in the table A in correspondence with the totalized levels in this way, when a certain line is focused, the totaled result of the totalized records is at the higher level in the lines before that. Are summarized in the summary record in. That is, for example, the aggregation result of the aggregation record of row No. "06" is aggregated to the aggregation record of row No. "05" at a higher level, and the aggregation record of row No. "05" is higher than that. It is totaled in the total record of line No. “01” in the level. Here, the summation to the higher level is usually a positive summation, but if a minus sign is entered together with the record name such as the record name "expense-" in line No. "05", the summation to the higher level is performed. Is a negative tally.

Further, the table A has a management unit area corresponding to each row No. By designating an arbitrary row and inputting a circle at the position corresponding to it, the item code of that row is changed. Indicates that the area is being input. This is because when the definition contents of table A are analyzed line by line, the line marked with the circle becomes the analysis target and the other lines are excluded from the target to improve the processing speed. At the same time, it also means that the person in charge of business confirms that the data to be extracted and aggregated is in the source file (accounting file etc.). Further, in the input area corresponding to the heading portion of “target code” in Table A, the specific item content (item code) of the totaling target item is input. For example, line No "0
1 ”, that is, the item code“ 911 ”is entered in the input area corresponding to the record name“ profit ”of the aggregation level A, and the record name“ product sales ”of the aggregation level C is entered in the line No.“ 03 ”. The item code “111” is entered in the corresponding input area, which defines that records corresponding to the item code “911” or “111” should be extracted from the items to be totaled in the predetermined file. . In addition, the record name "Profit" of the aggregation level A
Item code "911" defined in the input area corresponding to
Indicates, for example, non-operating profits (profit profit of shares, patent fees, etc.) as items to be totaled. In the “target code” input area of table A, a plurality of item codes can be entered corresponding to each line. In the example of table A shown in FIG. 3A, two item codes can be entered. , A part of the basic format of table A can be modified and changed as appropriate, and three or more item codes can be input by expanding the entire table frame. Note that, although FIG. 3A shows the case where the record name of the aggregation level A is arranged in the first row of the A table, as shown in FIG. 3B, the record name of the aggregation level A is the bottom row of the A table. It may be arranged at. Here, in FIG.
The table A in (B) is different only in the arrangement position of the record name, and the definition contents are the same. When the table A is created in this way, the parameter setting unit 2 sets the A table parameter data in the parameter file 4.

After the table A is created as described above, when an arbitrary form name is designated from the input section 1 and a print command is given, the table structure analysis section 5 causes the table structure parameter data in the parameter file 4 to be A table parameter data. Is analyzed and the processing for creating the configuration file 6 is performed. 5 to 7 are flowcharts showing the operation when creating the configuration file 6, and FIGS. 8 to 13 schematically show the operation contents of the table structure analysis unit 5 in this case and are shown in FIG. The figure which showed the production | generation process of the structure record produced | generated corresponding to the 1st line of the A table, and FIG. 14 is the figure which showed the content of the produced structure file 6 concretely. Each record structure of the configuration file 6 has a “child code”, a “parent code”, an “end mark”,
It consists of "signature" and "name", and "child code" and "parent code" represent the correspondence between the items to be totaled in table A and the corresponding totalized records, and the parent-child relationship in the hierarchical structure of the totaling level. This is a code representing (upper and lower relationships). The “end mark” is a flag that becomes “1” when the parent code includes the aggregation level A, and when the end mark is set to “1”, a record to a higher level than that. It indicates that no aggregation is performed. The "sign" is a sign that is set to "-" when a minus sign is added to the record name in the table A and a minus tabulation is defined. “Name” is the record name of the totalized record defined in table A. Now, FIG. 3 (A)
As an example, FIG. 5 illustrates a case where the configuration record is generated corresponding to the first to sixth rows based on the table A of the upper total shown in FIG.
~ The flowchart shown in Fig. 7 will be specifically described.

First, the table structure analysis unit 5 reads the parameters of the table A, searches for the description position of the record name corresponding to the aggregation level A (step A1), and the record name of the aggregation level A is in the first row of the table A. It is checked whether they are arranged (step A2). If it is located in the first line, the first line (first line) is specified (step A
3) If the record name of the summarization level A is located in the bottom row of table A, the lower summation flag is set to "1" (step A4) and the bottom row is designated (step A5). . Now, in the table A shown in FIG. 3A, the record name of the aggregation level A is arranged in the first row,
The first line is specified. Next, in step A6, it is checked whether the total level of the designated row is the highest level A. Now, since the totaling level in the first line is A, the contents of the last item work memory (see FIG. 8B) in the table structure analysis unit 5 are all cleared for initialization. In step A7), the aggregation level A is designated as the level of interest (current level) (step A).
8). In this state, level line data is generated from the current level and the line number of the line currently being focused on (current line) (step A9). Now, the first row of table A is aggregation level A
Since the line number is "01", the level line data "A01" is a combination of the current level and the line number.
To generate. Next, the level line data "A01" and the name of the current line (record name "profit" of the aggregated record) are set at the position corresponding to the current level A of the final item work memory (step A10). FIG. 8C shows the contents of the final item work memory in this case.
The final item work memory is configured to store level line data and names corresponding to the aggregation levels A, B, and C as shown in FIGS. 8B and 8C, and when the configuration record is created. Is the work memory of.

Next, it is checked whether or not the management unit area corresponding to the current line is circled (step A).
11). Now, as shown in Figure 3 (A),
A circle is added to the line, so step A2 in FIG.
7, the item code entered in the current line is designated from the beginning, and this designated code is set as a child code of the constituent record (step A28). In this case, since the item code is “911”, the child code is “911” as shown in FIG. Next, the level line data "A01" of the current level in the last item work memory is set as the parent code of the configuration record (step A2).
9). Next, it is checked whether the total level included in the parent code is A (step A30). In this case,
Since the parent code includes the aggregation level A, "1" is set to the end mark of the configuration record under this condition (step A31). Next, the name "profit" of the parent code is read from the final item work memory and set as the name of the constituent record (step A32). FIG. 8A shows the constituent record in the first row of the A table, and the child code is “911”,
The parent code is "A01", the end mark is "1", and the "name" is "profit", and this configuration record is written to the configuration file 6 (step A33). Here, the combination of the child code “911” and the parent code “A01” indicates the correspondence between the item code to be totalized and the totalized record corresponding thereto in the A table. Next, it is checked whether another item code is entered in the current line (step A34), and if there is, the process returns to step A27,
The next item code is specified, and the above operation is repeated item by item. Since only one item code is entered in the first line of table A, only one configuration record corresponding to the first line of table A is generated, but multiple item codes are entered in one line. If so, a configuration record corresponding to the number of items is generated and written in the configuration file 6.

When the absence of another item code is detected in step A34 after the first row of constituent records is generated in this way, the process proceeds to step A12 in FIG. When it is "1", paying attention to the previous line), it is checked whether or not a record name is set in that line. Since the record name "sales" is set in the next second line, the current line is updated and the next line (the previous line when the lower count flag is "1") is designated (step A1).
3). As a result, when the second row of the A table is designated, the process returns to step A6. In this case, the summarization level of the second row is B. Therefore, the procedure proceeds to step A10, and whether the level of the designated row is the current row level or higher. Check the error of whether or not,
If it is the current level or higher, all the contents below the level of the specified line are cleared in the last item memory (step A1).
5).

Since the total level B of the second line is lower than the current level A, the process proceeds to step A16, and the level of this designated line is set as the current level, and the current level is updated.
Next, level line data is generated from the current level and the line number of the current line (step A17), and this level line data is set in the position corresponding to the current level in the final item work memory together with the name of the current line ( Step A18). In this case, the level line data "B02" and the name "sales" are set at the position corresponding to the current level B in the final item work memory. As a result, the content of the final item work memory changes from the state shown in FIG. 9B to the state shown in FIG. 9C. Next, this level line data "B02" is set as a child code of the configuration record as shown in FIG. 9A (step A9). Then, step A in FIG.
Proceeding to 20, the level line data stored in the level position (current level + 1) in the last item work memory, that is, in the immediately preceding higher level position is read, and this is set as the parent code of the configuration record. . in this case,
The current level is B, and thus the level row data “A0 stored in the position of the level A of the last item work memory.
1 ”is the parent code (see FIG. 9A). here,
If the level included in the parent code is A (Fig. 1
7), "1" is set to the end mark of the configuration record (step A22). Next, it is checked whether or not the record name in the table A corresponding to the row number of the child code has a minus sign (step A23). -"Is set (step A24). Next, the parent code name "profit" is read from the final item work memory and set as the name of the configuration record (step A25).

When the child code “B02”, the parent code “A01”, the end flag “1”, and the name “profit” are prepared as data for one record in this way, this configuration record is written to the configuration file 6. Here, the child code "B
"02" and parent code "A01" combined row No. "02" in table A, record name "Sales" and record No. "01" at higher level, record name "Profit" The parent-child relationship (vertical relationship) with is shown. Next, returning to step A11 in FIG. 5, in this case,
Since the management unit area of the current line is not marked with a circle, that is, since the item code is not input to the current line, the configuration record generation process (steps A27 to A34) related to the item code is not performed. Then, the process moves to the designation of the next line (step A13).

Although the third line is designated by this, since the totaling level of the third line is C, which is less than the current level B, the process proceeds to step A16, the current level is changed to C, and then the configuration record is generated. Processing (steps A17 to A2
Go to 6). That is, now, in the state where the contents of the final item work memory are as shown in FIG. 10B, the level line data “C03” generated from the current level C and the line number of the current line.
And the name "Product Sales" of the current row are set at the current level C position of the final item work memory (see (C) of FIG. 10). Next, this level line data “C03” is set as a child code of the configuration record, and the (current level + 1) level line data “C” in the last item work memory is set.
02 "is set as the parent code of the constituent record (see FIG. 10A). In this case, the level included in the parent code is B, and thus the end mark is not set. Next, the name “sales” in the final item work memory stored in the position that is the parent code is read and set as the name of the configuration record. As a result, as shown in FIG. 10A, as a configuration record corresponding to the third row of table A, a configuration record having a child code “C03”, a parent code “B02”, and a name “sales” is first generated. And is written in the configuration file 6.

On the other hand, in the third row of table A, the item code "11
"1" has been entered and the line is marked with a circle,
This is detected in step A11, and the configuration record generation processing relating to this item code is performed thereafter (steps A27 to A34). That is, this item code "11
1 "is set as the child code of the configuration record, and the level line data" C03 "of the current level C in the last item work memory is set as the parent code of the configuration record. In this case as well, since the level of the parent code is not A, the end mark is not set. Next, the name “product sales” of the parent code is set as the name of the constituent record. As a result, as shown in FIG. 10, a configuration record having a child code “111”, a parent code “C03”, and a name “product sales” is generated and written in the configuration file 6. Since the next item code is not entered in the third row of Table A, the process returns to step A12 at this point.

Next, the fourth row of table A is designated (step A13). In this case, the totaling level and the current level are both C, so that it is detected in step A14 and the process proceeds to step A15, and the contents below the level of the designated line in the last item work memory, in this case level C
Is cleared (see FIG. 11B). In this state, "C04" is generated as the level row data, and as shown in FIG. 11C, at the position of level C in the last item work memory, the level row data and the name "part "Sales" is set. Then, the level line data “C04” is set as a child code of the configuration record, and the level line data “B03” of (current level + 1) in the last item work memory is set as a parent code of the configuration record. The parent code name “sales” is set as the name of the component record. As a result, a configuration record as shown in FIG. 11A is generated and written in the configuration file 6.
On the other hand, since the management unit is also circled in the 4th line of Table A, the configuration record is generated below, and the item code "121" in the 4th line is the child code, and the last item is currently in the work memory. The level line data “C04” of the level becomes the parent code, and the name “part sales” of the parent code becomes the name of the constituent record (see (D) of FIG. 11).

Next, the fifth row of the table A is designated. In this case, the total level of the fifth row is B and the current level is C. Therefore, as shown in FIG. In the memory, all the contents of level B and below of the designated line are cleared (step A15). In this state, “B05” is generated as the level line data, and the level line data shown in FIG.
As shown in, at the position of level B of the last item work memory, the name of the current line "expense-" is displayed together with this level line data.
Of these, the "expense" excluding the minus sign is set. The level row data "B05" is the child code, the level row data "A01" of the (current level + 1) in the last item work memory is the parent code, and the name "profit" of this parent code is the name of the constituent record. Record (Fig. 1
2 (see (A)) is generated and written in the configuration file 6. Since the management unit on the 5th line of Table A is not marked with a circle, the configuration record relating to this item code is not generated.

Subsequently, the 6th row of the A table is designated. In this case, the totaling level of the 6th row is C and the current level is B. Therefore, processing for clearing the contents of the last item work memory (step A15) ) Is not performed, and the contents of the final item work memory are in the state shown in FIG. In this state, "C06" is generated as the level line data, and as shown in FIG. 13C, at the position of the level C of the last item work memory, the level line data and the name "general expense" of the current line are stored. Set. The level line data “C06” is the child code, the level line data “B05” of the (current level + 1) in the last item work memory is the parent code, and the name “expense” of this parent code is the name of the constituent record. A record (see FIG. 13A) is generated and written in the configuration file 6. Where 6 in Table A
Since the circle is added to the line, a configuration record related to the item code is generated. In this case, (D) of FIG.
As shown in, the item code "411" on the 6th line is a child code,
The level line data "C06" of the current level in the last item work memory is the parent code, and the name "general expense" of the parent code is the name of the constituent record.

Next, when the 7th row of the A table is designated, the absence of data is detected in step A14, so that the configuration file creating process ends at this point. Thus, FIG.
The configuration file 6 created by analyzing the table A in FIG. 14A is as shown in FIG. That is, the configuration file 6 consists of nine configuration records, the first record is the first row of the A table, the second record is the second row of the A table,
The 3rd and 4th records are the 3rd row of the A table, the 5th and 6th records are the 4th row of the A table, the 7th record is the 5th row of the A table,
The 8th and 9th records are generated corresponding to the 6th row of the A table.

On the other hand, FIG. 14 (B) shows the configuration file 6 created by analyzing the lower tabulation A table shown in FIG. 3 (A). Here, when the configuration file 6 is created based on the table A of the upper tabulation, it is created by sequentially analyzing the table A from the first row as described above. When the configuration file 6 is created, it is created by sequentially analyzing the table A from the bottom row. Similarly to the configuration file for upper aggregation, the lower aggregation configuration file thus created represents the correspondence between the items to be aggregated and the corresponding aggregation records according to the definition contents of table A, and the vertical relation in the hierarchical structure of the aggregation level. However, in the case of the lower tabulation, the upper and lower relations are in the downward direction. In this way the configuration file 6
When the table structure analysis unit 5 creates
Give a start command to.

Then, the expansion file creation unit 8 specifies a file to be totalized from the various source files A ... N forming the data file 9 and expands the records extracted from the files to be totalized one by one. As a result, the process of writing the file in the expanded file 10 is performed. Here, each record constituting the expansion file 10 is composed of a classification code and a data value. When the expansion file 10 is created, the expansion file creating unit 8 gives a start command to the expansion aggregation processing unit 11.

The expansion totalization processing unit 11 sequentially creates an aggregate record for each record based on the contents of the expansion file 10 while referring to the configuration file 6, and writes it in the totalization file 12. In this case, the expansion totalization processing unit 11 generates the totalization file 12 based on the contents of the expansion file 10 and the contents of the configuration file 6 according to the component expansion method. FIG. 15 is a flowchart showing the operation of the expansion totalization processing unit 11. 16 to 25, the expansion totalization processing unit 11 is shown.
FIG. 7 is a diagram for specifically explaining the operation content of FIG. Now, with reference to FIG.
It is assumed that the aggregate record is generated based on the contents of the expansion file 10 shown in 6A.

First, the expansion totalization processing unit 11 reads data for one record from the beginning of the expansion file 10 (step B1). Then, in the next step B2, it is checked whether the data has ended, that is, whether or not all the records have been read from the beginning of the expanded file 10. At first, since one record of data is read from the beginning of the expansion file 10, the process proceeds to the next step B3, the contents of the configuration file 6 are searched, and the child code matching the classification code of the expansion record is set to the configuration file. Search from 6. Here, FIG. 16 shows the operation contents when the data of the first record is read from the expansion file 10. Now, in the expansion file 10 having the content shown in FIG. 16A, the classification code of the first expansion record is “11”.
1 ", the data value is" 1,000 ", and the configuration record having the child code matching this classification code is shown in FIG.
Since it exists in the fourth record in the configuration file 6 shown in (A), a match is detected in step B3 and step B4
Then, the record of the totalization file 12 is generated. That is, in the specific example of FIG. 16, (C) shows the expansion record of the first record, and (D) shows the configuration record in which the match is detected. First, the expansion aggregation processing unit 11 corresponds to the child code in this configuration record. Read the parent code "C03"
This parent code is decomposed into the row No. of the table A and the totaling level, the row No. “03” is arranged in the first item of the first record of the totaling file 12, and the totaling level “C” is arranged following it. Then, the name in this constituent record is arranged in the next item of the total record. Then, the data value “1,000” of the expansion record is arranged in the next item of the totalization record. FIG. 16E shows the aggregated record thus generated. In other words, this aggregate record is an aggregate record of the record name "Product Sales" and aggregation level C defined in row No. "03" of table A, and the aggregate record defined in table A corresponding to this record name. The data "1,000" corresponding to the target code "111" is aggregated.

Next, the process proceeds to step B5, it is checked whether a record having the same key as the generated aggregate record is already stored in the aggregate file 12, and if there is no aggregate record having the same key, the aggregate record generated. Is simply written to the totalization file 12 (step B6), but if a record having the same key is already stored in the totalization file 12, the process proceeds to step B7.
Check if the minus sign is set by referring to "Sign" in the configuration record. As a result, if there is no minus sign, the existing aggregation record having the same key and the aggregation record generated this time are positively aggregated and put together into one record and written in the aggregation file 12 (step B8). If so, the existing tabulation record having the same key and the tabulation record generated this time are negatively tabulated and written into the tabulation file 12 in a single record (step B9), now FIG. 16 (B).
As shown in, since no totalization record is stored in the totalization file 12, it is detected in step B5 that no existing totalization record having the same key exists, and additional totalization to the totalization file 12 is performed. Is done.

Next, it is checked whether the end mark "1" is set in the configuration record (step B10).
Here, as described above, the end mark in the configuration record is "1" when the aggregation level included in the parent code is A, and when the end mark is "1", the step B is directly used.
Returning to step 3, if the end mark is not "1", a new expanded record is newly generated and written in the expanded file 10 (step B11). In other words, if a record name at a higher level than the aggregate record generated this time is defined in table A, a new result will be added in order to aggregate the aggregated result of the aggregate record generated this time to the aggregate record having the record name at an upper level. A new expansion record is generated and written to the expansion file 10.

Since the end mark "1" is not set in the constituent record, a record as shown in FIG. 16 (F) is newly generated and written in the expanded file 10. That is, the parent code “C03” in the configuration record is placed as it is in the first item as a classification, and subsequently, a new development record in which the data value “1,000” in the development record is placed is generated to generate the development file 10 Write to. After that, the process returns to step B3, and thereafter, all the contents of the configuration file 6 are searched, and the classification code "11" in the expansion record is searched.
The above operation is repeated until a configuration record having a child code matching "1" is not detected. As a result, when it is determined in step B3 that there is no corresponding record and the disagreement ends, the process returns to step B1 to read the next record from the expanded file 10.

FIG. 17 shows the operation contents when the next record is read from the expansion file 10. here,
(A) shows the contents of the expansion file 10 at this time, and the records arranged below the bold line in the figure show the expansion records newly generated in the case of FIG. Also,
(B) shows the contents of the totalization file 12 at this time, and shows the state in which the totalization record generated in the case of FIG. 16 is written at the beginning. Furthermore, (C)
Indicates a record read this time from the expanded file 10, and (D) indicates a constituent record having a child code that matches the classification key of this expanded record. Here, the expansion totalization processing unit 11 generates the totalization record as shown in (E) from the expansion record and the constituent record. This total record is a total record of record name "part sales" defined in row No. "04" of table A and total level C, and total target code defined in table A corresponding to this record name. Data corresponding to "121""2,000
This is a total of "0". Even in this case, since the record having the same key does not exist in the totalization file 12, additional totalization to the totalization file 12 is performed (step B6). Further, as in the above case, since the end mark is not set in this configuration record, a new expansion record (see FIG. 17F) is generated and the expansion file 10 is generated.
(Step B11). Then, step B3
When the non-matching end is detected at, the next record is read from the expanded file 10 (step B1).

Similarly, FIG. 18 shows the operation contents when the next record is read from the expanded file 10. In this case, an aggregate record as shown in (E) is generated from the record (C) read from the expansion file 10 and the corresponding constituent record (D). This summary record is a summary record of record name "general" and summary level C defined in row No. "06" of table A, and the summary target code "table" defined in table A corresponding to this record name. The data "800" corresponding to "411" is added up and added to the counting file 12. Also,
Also in this case, a new expansion record as shown in (F) is generated in order to total the totalized result of the totalized record generated this time into the totalized record of the record name at a higher level than that.

Further, FIG. 19 shows the operation contents when the next record is read from the expansion file 10. Also in this case, the aggregate record as shown in (E) is generated from the record (C) read from the expansion file 10 and the corresponding constituent record (D). This aggregate record is an aggregate record of record level "profit" and aggregation level A defined in row No. "01" of table A.
The data "500" corresponding to the aggregation target code "911" defined in the table A corresponding to this record name is aggregated, and is additionally aggregated in the aggregation file 12. In this way, if the aggregation target code “911” is defined corresponding to the record name “profit” of the aggregation level A in the table A,
A total record based on the total target code is also generated. Here, assuming that the target item code “911” is an item of non-operating profit, the generated record becomes a record of this non-operating profit. In this case, the aggregation level is A,
Therefore, since the end mark "1" is set in the configuration record, no new expansion record is generated.

In this way, when the contents of the expansion file 10 shown in FIG. 16A are sequentially read out record by record to generate a total record, the total file 12 is displayed as shown in FIG. A total record is written.
Each record in the tabulation file 12 is a tabulation target item code “111”, “121”,
It is an aggregate record in which data corresponding to “411” and “911” are aggregated. As a result, all the aggregate records corresponding to each item to be aggregated are prepared.

Next, the process for totaling the totalized results of each totalized record to the totalized record at the higher level will be described. First, a process of generating a totalization record of the totalization level B after the totalization record of the totalization level B is generated. Here, FIGS. 20 to 22 show the case of generating the totalization record of the totalization level B, and FIGS. 23 to 25 show the case of generating the totalization record of the totalization level A.

FIG. 20 shows the operation contents when the newly generated expansion record is read in the case of FIG. In this case, as shown in (C), the classification code of the expansion record is "C03", and the parent code of the component record having a child code matching this is "B02" as shown in (D).
Is. Therefore, a totalization record as shown in (E) is generated from the expansion record and the configuration record. This tabulation record is a tabulation record of row number "02" and record name "sales" in higher level B than the tabulation record of row number "03" in table A, and the data value of the expansion record shown in (C). That is, this is the total of the total result "1,000" of the row No. "02". In this case, since there is no total record having the same key in the total file 12, this total record is the total file 12
Is added to. Also in this case, a development record as shown in (F) is newly generated and written in the development file 10 in order to add up to the totalization record of the record name in the higher level.

FIG. 21 shows the operation contents when the newly generated expansion record is read in the case of FIG. Also in this case, as shown in (C), the parent code of the component record having the child code that matches the classification code “C04” of the expansion record is “B02”. Therefore, a totalization record as shown in (E) is generated from the expansion record and the configuration record. This summary record is higher level B than the summary record of row No. "04" in table A.
In the row No. "02" and the record name "Sales", and the data value of the expansion record shown in (C) (Line No.
This is a result of totaling the totaling result of "04""2,000"). Here, since the totalized record with the same key generated in the case of FIG. 20 already exists in the totalization file 12, the totalization record generated this time and the totalization record with the same key in the totalization file 12 are 1 The records are collectively written in the record file 12. That is, the data values of the total record generated this time and the total record already generated are totaled. In this case, however, the minus sign is not set in the “sign” in the constituent record as shown in (D). , Plus totals are added and "1,000
+2,000 = 3,000 "as a data value for a new totalization record (key and name are the same) Totaling file 1
It is written in the fifth record of 2, that is, the position where the totalized record having the same key was stored, and the content is replaced with a new totalized record. As a result, the total record newly written in the total file 12 has the row numbers “03” and “04” of the table A at the lower level than that.
21 (the contents of the first record and the second record in FIG. 21B) are added up and aggregated. Even in this case, a development record as shown in (F) is newly generated. This expansion record is the same as the classification code “B02” of the expansion record generated in the case of FIG. 20, but the data value is different.

FIG. 22 shows the operation contents when the newly created expansion record is read in the case of FIG.
A development record shown in (C) and a configuration record shown in (D) generate a totalization record as shown in (E). This totalization record is at a higher level than the totalization record of row No. “06” of table A. The data value of the expansion record shown in (C), which is the aggregate record of the line No. “05” and the record name “expense” in B, that is, the aggregate result of the line No. “06” “80”
This is a total of "0". Here, tally file 12
Since there is no summary record with the same key in,
Additional tabulation to the tabulation file 12 is performed. Also,
A development record as shown in (F) is also newly generated.

In this way, from the expansion file 10 to FIG.
6 to FIG. 18, the newly generated expansion records are sequentially read and the aggregation record of the aggregation level B is generated accordingly, and the newly generated expansion records in FIGS. 20 to 22 are further extracted from the expansion file 10. Sequential reading is performed to generate a total record (FIGS. 23 to 25). in this case,
Since this is a process of generating the aggregated record of the highest level A, aggregation to the upper level is unnecessary, and no new expanded record is generated.

FIG. 23 shows a case in which the expanded record newly generated in FIG. 20 is read. At this time, the totalized record generated is the row No. “01” of table A, the totalization level A, and the record name “profit”. In the summary record, the data value is "1,0
However, in this case, since the totalized record having the same key as this totalized record exists in the fourth record in the totalization file 12 and the minus sign is not set in the constituent record, it is generated this time. Data values of the aggregated record and the aggregated record of the fourth record in the aggregated file 12 are added up and aggregated, and the value “500 + 1,00
“0 = 1,500” is rewritten with the contents of the fourth record in the totalization file 12.

Further, FIG. 24 shows the case where the expanded record newly generated in FIG. 21 is read, and the totalized record generated at this time is the totaling record of the totaling level A as in the case of FIG. 23. In this case, the data value is "2.00
It becomes "0". Even in this case, the summation is added to the summation record of the fourth record in the summation file 12 having the same key to be summed up into one summation record.

Finally, FIG. 25 shows a case where the expanded record newly generated in FIG. 22 is read, and the totalized record generated at this time is the totaling record of the totaling level A as in the case of FIG. 23. The data value becomes “800”.
In this case, since the minus sign is set in the constituent record, the aggregate record generated this time and the aggregate record having the same key in the fourth record in the aggregate file 12 are subtracted and aggregated, and the value " 3,500-80
0 = 2,700 "is replaced with the contents of the fourth record in the totalization file 12.

The value "2,700" of the totalization record of the totalization level A thus obtained is the value "500" of the totalization record of the item code "911" corresponding to the value "product" which is at a lower level than that. "Sales" record value "1,
000 ”and“ part sales ”record value“ 2,000 ”
"0" is added and totaled, and the record value "800" of "general expense" is subtracted and totalized from the totalized result. Therefore, the record value of the aggregation level A also records the non-operating profit.

When all the records in the expanded file 10 are read in this way, the end of the data is detected in step B2 of FIG. 15 and the process proceeds to step B12, in which each record constituting the totalization file 12 has its key content (line). Sort in ascending order according to No.). FIG. 26 shows the contents of the aggregation file 12 in this case, (A) before sorting, (B)
Indicates the contents of the totalization file 12 after sorting. The records in the tabulation file 12 sorted in this way are rearranged in the printing order when the form is output.

On the other hand, FIG. 26C shows the contents of the totalization file after sorting the totalization file created in the case of the bottom totalization. In this case as well, each record in the totalization file 12 is a form. Sorted in print order when output. Then, the expansion totalization processing unit 11 activates the print processing unit 13.

Then, the print processing unit 13 operates according to the flowchart of FIG. Here, the print processing unit 13
Takes in the contents of the print format memory 7, reads the contents of the totalization file 12 one record at a time according to the print format, determines the totalization level contained in this totalization record, and determines the corresponding totalization level. A ruled line format is generated with reference to the format table in the print format memory 7, and the name and data value in the totalized record are printed out one by one together with this ruled line format to create a form.
In this case, the printing form of the form differs depending on whether the upper tabulation or the lower tabulation is performed.

That is, the print processing unit 13 uses the tally file 12
Read the aggregated record from the beginning of (step C1),
It is checked whether the total level in this top record is A (step C2). Now, if it is level A, it means that the upward totalization has been performed, and accordingly, the printing process is performed (steps C3 to C6). First, referring to the format table in the print format memory 7, a ruled line format corresponding to the level A for upper totalization is generated, and according to the print format, the ruled line format and the name and data value of the totalized record are allocated in the format. It is printed out (step C3). Then, the next record is read from the totalization file 12 (step C4), the level included in the totalization record is discriminated, and the ruled line format for upper totalization corresponding to the level is generated. While assigning the name and data value of the totalized record in the format, it is printed out according to the print format (step C5). Next, the process proceeds to step C6, and it is checked whether or not the next record exists in the totalization file 12, and if there is, the process returns to step C4 and the above-described operation is repeated until all the records in the totalization file 12 are printed. As a result, a top-up tabulation form as shown in FIG. 2 (A) is created, but this form is as defined in the table A shown in FIG. 3 (A), and the tabulated tabulation result is the table A. It is printed out in a hierarchical structure from the upper level corresponding to the order of the record names defined in.

On the other hand, if the top totalization record is not level A in step C2, printing processing is performed according to the lower totalization (steps C7 to C9). First, the level of the top record is discriminated, and the ruled line pattern for bottom totalization corresponding to the level is determined.
A mat is generated and, along with this ruled line format, the name and data value of the totalized record are assigned to the format and printed out according to the print format (step C7). Next, it is checked whether or not there is another totaling record (step C8), and if there is another totaling record, the next totaling record is read out (step C9), and then the process returns to step C7 to perform the above-mentioned operation in the totaling file 12 Repeat printing until all the records inside are printed. As a result, a form of bottom tabulation as shown in FIG. 2B is created. This form is as defined in the table A shown in FIG. 3 (B), and the tabulated results of the tabulation are printed out in a hierarchical structure from the lower level corresponding to the order of the record names defined in the table A. It has been done.

As described above, in the present embodiment, the record name of the totalized record is defined corresponding to the totalization level in the totalization definition table A in order to obtain the form desired by the person in charge of business. Moreover, if the aggregation target code is defined corresponding to this record name, the table A is referred to, the data corresponding to the aggregation target code is read from the predetermined file, and the read data is stored in the table A. In addition to being summarized to the summary record of the corresponding record name, if the record name at a higher level than this summary record is defined in table A, the summary result of this summary record is the summary record of the record name at a higher level. Is counted in. On the other hand, if a minus sign is added to the record name in order to define a negative summary for the summary record at the higher level, the summary result of the summary record with that record name will be negative for the summary record at the higher level. It is totaled. In particular, in this embodiment, when defining the record name of the aggregated record in the table A according to the parent-child relationship according to the aggregation level, the record name corresponding to the highest level is arranged in the first row of the table A,
You can place it at the bottom line or define it freely,
Even if table A is defined in this way, when totaling the totaled results of the totalized records into upper level records, it is determined whether the upper level record names are arranged in the upward direction or the downward direction. Since the upper tabulation or the lower tabulation is performed, the table A can be defined in the form of the upper tabulation or the lower tabulation. In addition, in order to define the negative aggregation to the aggregation record at the higher level, "-" is added to the record name.
If the code is added, the totalized result of the totalized records in the record name is negatively totalized in the totalized record at the higher level. In addition, if non-operating income, that is, items such as profit on stocks and patent fees are defined as item codes to be aggregated corresponding to the record name "profit" in row No. "01" in table A, Non-operating profit is also recorded in the record of “profit”.

Further, since the expansion totalization processing unit 11 creates the totalization file 12 and then sorts each record according to its row number, the arrangement order of each record in the totalization file 12 is defined in the table A. The print processing unit 13 reads the contents of the totalization file 12 one record at a time from the beginning, checks the totalization level included in the totalization record, and decides in advance in accordance with it. The name and data value of the totalized record are printed out together with the ruled line format that is used. The print result of the created form corresponds to the definition contents of table A, and the form of the hierarchical structure according to the totalization level is obtained. It becomes possible. In particular, even if the table A is defined in the form of top totaling or bottom totaling, the forms are printed in the order of the top totaling and the bottom totaling according to the definition contents, so that the form can be obtained as an image.

[0055]

[Second Embodiment] A second embodiment will be described below with reference to FIGS. FIG. 28 shows Table A of this example, and FIG.
Similar to the A table shown in (A), the case where the A table is defined in the form of the above tabulation, the row No. “0” of the A table shown in FIG.
2 ”, the record name“ sales ”of the aggregation level B is removed, and the definition contents below that are moved up line by line. If such table A is defined, row number “01” of table A
Is the record name "Profit" of the aggregation level A, line No. "02"
The record name “Product Sales” of the aggregation level C is arranged in the table, and the aggregation levels are not hierarchically continuous. However, in the present embodiment, when the form is printed, the connection level of the aggregation levels is determined and the connection level is determined. I am trying to print in a format that suits me. It should be noted that this embodiment may define the table A in any of the upper tabulation and lower tabulation formats as in the first embodiment, but is applied to a form output device that is limited to only the upper tabulation and the lower tabulation in advance. You can also do it. Hereinafter, the operation of this embodiment will be described by taking the case where the table A is defined in the form of the above tabulation as an example.

FIG. 29 is a flow chart showing the operation when printing a form. Now, it is assumed that a format memory as shown in FIG. 30 is set in the print format memory 7 in this embodiment. The contents of this format memory are the same as those in the first embodiment, and the ruled line format is generated for each level according to the contents of this format memory. Here, FIG. 30 shows a ruled line format for upper counting. In this embodiment, when a ruled line format corresponding to level C is generated, two types of ruled line formats are selected depending on whether or not there is a level B above it. I am trying to generate. That is, when there is a level B at the upper level, a ruled line format (level C-
1), or if there is no B in the upper level, a ruled line format (level C-2) peculiar to this embodiment is generated. The ruled line format of Level C-2 is Level C-
The vertical ruled line corresponding to the starting point digit of level B is deleted from the ruled line format of 1. The other ruled line formats of levels A and B are the same as those in the first embodiment. Further, FIG. 31 shows the contents of the totalization file 12, and this totalization file is the totalized file after the above totalization.

First, the print processing unit 13 uses the totalization file 1
Read the aggregation record from the beginning of 2 (step D1)
The total level is judged (step D2). Now, the leading totalized record proceeds to level A, and therefore to step D3, a level A ruled line format is generated, and the name and data value of the totalized record are allocated in the format and printed out according to the print format. Then, check whether there is another total record record (step D
4) If there is, return to step D1, read the totalization record, and judge the level (step D
2). Here, since the second record is the totalization level C, the process proceeds to step D6 to check whether there is a totalization record of level B which is the higher level of the totalization file 12 in the upward direction. Since there is no totalization record, the process proceeds to step D8 and level C-2.
The ruled line format of is generated and the printout is performed according to the print format while assigning the record name and data value of the total record in the format.

Next, the third record is read from the totalization file 12 or, even in this case, the totalization record of the level B, which is the upper level, does not exist in the upward direction of the totalization file 12, and therefore the level C-2 A ruled line format is generated and the contents of the totalized record are printed out together with this format. Next, tally file 12
Or the fourth record is read, or this aggregated record is level B, and therefore the process proceeds to step D5, and level B
The ruled line format of is generated, and the content of the totalized record is printed out together with this format. continue,
The fifth record is read from the totalization file 12. This aggregated record proceeds to level C, and therefore step D6, or in this case, the aggregated record of its higher level, level B, exists in the aggregate file 12 in the upward direction, so the process proceeds to step D7 and the level C-1 A ruled line format is generated, and the contents of the totalized record are printed out together with this format.

As a result, when the previous record in the totalization file 12 has been printed, a form as shown in FIG. 32 is obtained. According to the definition contents of the table A shown in FIG. 28, this book has a result that the tabulated totaling result is printed out in a hierarchical structure and the connection level of the totaling level fluctuates from level A to level C. It will be printed out in a format according to the connection. The present embodiment configured in this way has the same effect as the first embodiment, and in particular, in the present embodiment, form printing is performed in a format according to the level of connection defined in Table A. Since it is performed, when defining the A table, it is not necessary to define the aggregation levels so as to be continuous, and the A table can be defined in a format in which the intermediate level is omitted, and the A table is defined for the user. The degree of freedom is increased, and the desired form can be obtained according to the image defined in Table A. In addition,
In the above example, the case of the upper total is shown, but also in the case of the lower total, even if the table A is defined in a format in which the intermediate level is omitted, a form of a format corresponding to that can be obtained. Although the three levels A, B, and C are shown as the totaling level in each of the above embodiments, the form may be output in a hierarchical structure having four or more totaling levels. In the first embodiment, the top total and bottom total are calculated depending on whether the highest-level record name is placed in the first row or the bottom row of table A. The left total may be calculated. Further, the ruled line format is not limited in shape as long as it can identify the aggregation level, and is arbitrary. Further, in the above embodiment, any record name is directly input to the table A from the input unit 1 for each aggregation level. However, when the record name to be used is predetermined, these record names to be used are It may be stored in a table, and when the record name is input, the table contents may be displayed in a list on the window screen, and the record name may be input by selecting an arbitrary record name from the list. Further, the record name is not limited to the name and may be a code. Further, in the above-mentioned embodiment, the item code to be totaled is input to the table A, but a name may be input in addition to the code, and the totaling target is specified by designating the intersection position on the matrix of the table A. May be instructed.

[0060]

According to the present invention, by simply specifying a record name or the like of a totalization record corresponding to a totaling level, totaling to higher levels can be performed according to the parent-child relationship of the specified totaling level. Since the totaled result can be output in a hierarchical structure according to the specified contents according to the order of the record names, it is not necessary to request an expert such as a system engineer to create a code system as in the past, and a general user It is possible to easily obtain a form as inspected according to the form image desired by a business person, which is extremely practical.

[Brief description of drawings]

FIG. 1 is a block configuration diagram of a data processing device according to an embodiment.

FIG. 2 shows a form printing example, (A) is a form printing example,
FIG. 6B is a diagram showing an example of printing a form for bottom tabulation.

FIG. 3 is a diagram showing a specific example of the contents defined in table A, which is a tabulation definition table, in which (A) is an upper tabulation table A and (B) is a lower tabulation table A.

FIG. 4 is a diagram showing a format table set in a print format memory 7 and ruled line formats for upper totalization and lower totalization generated for each totaling level according to the contents of the table.

FIG. 5 is a flowchart showing a part of a process in which the table structure analysis unit 5 creates a configuration file 6.

FIG. 6 is a flowchart showing a part of a configuration file creation process following FIG.

FIG. 7 is a flowchart showing a part of a configuration file creation process following FIG.

FIG. 8 is a diagram showing a generation process of a configuration record generated corresponding to the first row of table A.

FIG. 9 is a diagram showing a process of generating a configuration record generated corresponding to the second row of table A.

FIG. 10 is a diagram showing a process of generating a configuration record generated corresponding to the third row of table A.

FIG. 11 is a diagram showing a process of generating a configuration record generated corresponding to the fourth row of table A.

FIG. 12 is a diagram showing a process of generating a configuration record generated corresponding to the fifth row of table A.

FIG. 13 is a diagram showing a process of generating a configuration record generated corresponding to the sixth row of table A.

14A and 14B show a specific example of the configuration file 6, where FIG. 14A shows the configuration file 6 for upper totaling created according to the table A shown in FIG. 3A, and FIG. 14B shows it in FIG. 3B. FIG. 6 is a diagram showing a configuration file 6 for lower totalization created according to a table A.

FIG. 15 is a flowchart showing an operation in the case where the development totalization processing unit 11 creates the totalization file 12 from the contents of the configuration file 6 and the expansion file 10.

FIG. 16 is a diagram showing the operation contents when the expansion aggregation processing unit 11 reads the first record from the expansion file 10.

FIG. 17 is a diagram showing the operation contents when the expansion aggregation processing unit 11 reads the second record from the expansion file 10.

FIG. 18 is a diagram showing the operation contents when the expansion aggregation processing unit 11 reads the third record from the expansion file 10.

FIG. 19 is a diagram showing the operation contents when the expansion aggregation processing unit 11 reads out the fourth record from the expansion file 10.

FIG. 20 is a diagram showing the operation contents when the expansion aggregation processing unit 11 reads the fifth record from the expansion file 10.

FIG. 21 is a diagram showing the operation contents when the expansion aggregation processing unit 11 reads the sixth record from the expansion file 10.

FIG. 22 is a diagram showing the operation contents when the expansion aggregation processing unit 11 reads the seventh record from the expansion file 10.

FIG. 23 is a diagram showing the operation contents when the expansion aggregation processing unit 11 reads the eighth record from the expansion file 10.

FIG. 24 is a diagram showing the operation contents when the expansion aggregation processing unit 11 reads the ninth record from the expansion file 10.

FIG. 25 is a diagram showing the operation contents when the expansion aggregation processing unit 11 reads the last record from the expansion file 10.

26A shows the contents of the totalized file before sorting, FIG. 26B shows the contents of the totalized file after sorting, and FIG. 26C shows the sorted totalized file. The figure which shows the contents of the summary file after.

FIG. 27 is a flowchart showing print processing.

FIG. 28 is a diagram showing definition contents of table A in the second embodiment.

FIG. 29 is a flowchart showing the operation of the print processing unit 13 in the second embodiment.

FIG. 30 is a diagram showing a format table set in the print format memory according to the second embodiment and a ruled line format for upper totalization generated for each totaling level according to the contents of the table.

FIG. 31 is a diagram showing the contents of the summary file 12 after sorting in the second embodiment.

FIG. 32 is a diagram showing an example of printing forms according to the second embodiment.

[Explanation of symbols]

 1 Input Part 2 Parameter Setting Part 3 Display Part 4 Parameter File 5 Table Structure Analysis Part 6 Configuration File 7 Printing Format File 8 Expanded File Creation Part 9 Data File 10 Expanded File 11 Expanded Aggregation Processing Part 12 Aggregation File 13 Print Processing Part 14 Printer

Claims (3)

[Claims] 1. A designation means for arranging and designating a record name of a summary record at an arbitrary position corresponding to a compilation level, and designating a collection target corresponding to this record name, and designation by this designating means. The first aggregation means for reading out the data corresponding to the aggregation target from a predetermined file and totaling the records having the record name corresponding to the aggregation target, and the aggregation result of the records aggregated by the first aggregation means When totaling to a record of a higher level than the above, based on the arrangement position of the record name of this higher level, a totaling direction determining means for determining whether to total in the forward direction or the reverse direction, and the first totaling The record of the record name at the higher level arranged in the totaling direction determined by the totaling direction determining unit based on the totaling result of the records totaled by the totaling unit A form comprising: a second totaling means for totaling, and an output means for outputting each record totalized by the second totaling means in accordance with the arrangement order of the record names designated by the designating means. Output device. 2. The output means outputs the records totaled by the second totaling means according to the arrangement order of the record names designated by the designating means, and the totaling direction determined by the totaling direction determining means. The form output device according to claim 1, wherein the form output device outputs the form. 3. A specifying means for arbitrarily specifying a record name of a totalized record corresponding to a totaling level and specifying a totaling target corresponding to this record name, and corresponding to a totaling target specified by this specifying means. Data from a specified file and aggregate it into records with the record name corresponding to this aggregation target, and the aggregation results of the records aggregated by this first aggregation means to a higher level than that. A second totaling means for totaling records of a certain record name, and each record totaled by this second totaling means is output according to the order of arrangement of the record names specified by the specifying means, and the totaling level of each record is output. A form output device, comprising: an output unit that outputs in a format according to the connection state of.