JP3109331B2 - Form output device - Google Patents

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 reading out record data from an accounting file, a personnel file, etc. and outputting the form in an office computer or a personal computer.

[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, and inventory files are stored and managed, but the record structure that constitutes each file is different for each file.
Each file is stored and managed as a separate file for each record of the same form (records in which each item of the record matches). By the way, when an arbitrary item is specified, a record including the item is read from the file, and the data is output in a form that is classified for each classification.
Even if it is made with a classification code system that makes it easy to classify and aggregate,
As time elapses, the classification does not actually match, and it becomes impossible to output each classification as it is. Therefore,
Conventionally, as a countermeasure, a method of providing a code conversion table for classification and using the code conversion table to convert to a code system most suitable for classification is currently widely used.

[0003]

However, in the method using the code conversion table, a system engineer who is an expert must create a code system (conversion table) for classification. In other words, creating a classification code system in response to various business needs requires extremely specialized and advanced knowledge, and it is extremely difficult for a general user's business staff to create it. At present, it was necessary to ask a system engineer to create it. An object of the present invention is to specify a code condition indicating an output level and a target item at the time of extracting an output record in association with a plurality of items in order to obtain a desired form. The purpose is to classify records into a hierarchical structure as specified and output them.

[0004]

According to the present invention, a record storage means for storing a plurality of records each including a plurality of items,
The first item of the record name of the first hierarchy and the extraction code condition in the first item, and the second item of the record name of the second hierarchy and the extraction code condition in the second item when the records are output in a plurality of hierarchies , And a second definition table for defining an output target item necessary for the form output among the items included in the record. Second definition storage means;
A first hierarchical record having an item code matching the first item extraction code condition, an item code matching the first item extraction code condition and an item code matching the second item extraction code condition are both included. Extracting means for extracting a second-level record having the information, and when creating a form based on each record extracted by the extracting means, a form corresponding to the item code of the first item in the extracted first-level record Is the record name in the form, the name corresponding to the item code of the second item in the extracted second-level record is the record name in the form, and each of the extracted first and second layers For each record, read out the contents of each output target item defined in the second definition table for each record and associate it with the record name. A form creation unit that creates a form that location, characterized by comprising output means for outputting the created document, the.

[0005]

[0006]

First Embodiment Hereinafter, a first embodiment will be described with reference to FIGS. FIG. 1 is a block diagram of the data processing apparatus according to the present embodiment. This data processing device constitutes an office computer, and a person in charge of business, etc. who does not have specialized knowledge simply specifies an aggregation target or the like at each aggregation level using an aggregation definition table. Records corresponding to the definition contents of the table are read from a predetermined file, the records are classified and totaled in a hierarchical structure according to the totaling level, and the totaling result is printed out as form data. The input unit 1 is a key input device for inputting various data, commands, and the like. Data input from the input unit 1 is taken into the parameter setting unit 2, processed, and displayed on the display unit 3. Note that 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 in order to instruct an arbitrary record aggregation desired by a business person or the like, the arrangement position of the record name of the aggregation record and the aggregation target item (In this embodiment, two types of tables A and B) are generated in accordance with the data input from the input unit 1 and are displayed and output from the display unit 3, and the parameters are displayed. Set in file 4. The tables A and B will be described in detail later, and will be described briefly here.

For example, in order to print out a “sales record table” as shown in FIG. 2 as a desired form, tables A and B are used as a total definition table according to the output image of the form.
Generate a table. Here, the form shown in FIG. 2 has the record name of the tally record arranged in a row item and the data item name of the tally record arranged in a column item. Table A defined to obtain this form is 3A and 3B are configured as shown in FIG. 3B. The table A defines, in addition to the file name of the tallying target, the arrangement position of the record name in the tallying record, the code condition indicating the target item when extracting the output record, and the like corresponding to the tallying level. That is,
In the illustrated example, “collected file” is specified as the file name of the aggregation target, and the actual record name, for example, “business office” is used as a general substitute name instead of XX business office, XX business office, etc. The position of the record name is specified by using parentheses. Note that this description method is arbitrary, and the position may be specified by a simple method such as placing a circle at the arrangement position of the record name. However, in this embodiment, a general substitute name is described. Parentheses are used to indicate that the name is a substitute name. In addition, for example, “10?” Is specified as a code condition indicating a target item when a total record is extracted.
The code condition "10?" Is composed of a three-digit numerical code from the item code, and indicates that all item codes including the upper two-digit value "10" are to be counted.
In other words, to specify multiple item codes at once with one definition, use? Although the code condition is defined by the description with the mark, when only one item code is specified, the item code may be defined as it is as the code condition. Table B defines an item name output as a data item of a tally record, a format for printing a form, a tally file, and a tally item extracted as a data item corresponding to the item name.

In the parameter file 4, the basic format (ruled line data, etc.) corresponding to the tables A and B is fixedly stored in advance by the manufacturer side, and various types of data input arbitrarily from the input unit 1 are also stored. A table parameter data and B table parameter data of the form, and various form names and A table parameter data arbitrarily input from the input unit 1;
A correspondence table for associating with table parameter data is stored.

The table structure analysis unit 5 operates according to a start command input from the input unit 1 when printing a form, and analyzes the A table parameter data and the B table parameter data corresponding to a form name arbitrarily specified as an output target. Then, the configuration file 7 is created according to the analysis result. Here, the table memory 6 stores an index table and the like in which item codes and names are associated with each other, and the index table and the like are arbitrarily set by the user from the input unit 2. The table structure analyzing unit 5 refers to the table memory 6 and creates the configuration file 7 while reading out the names corresponding to all the item codes matching the code conditions of the table A from the index table.

FIG. 4 shows a part of a table set in the table memory 6. The file recognition table is provided for each file, and is a table in which file item names are associated with table names of index tables. The illustrated file recognition table is a table corresponding to a collected file. The sales office table and the customer table are index tables corresponding to the illustrated file recognition table, and have a configuration in which item codes are associated with their names. The name corresponding to the item code is read from the index table, and the name is automatically generated.

Although the configuration file 7 will be described later in detail,
It is composed of various types of configuration records indicating the correspondence between the item code to be totalized and the corresponding totals record, the parent-child relationship (vertical relationship) in the hierarchical structure of the totals level, and the like. Further, the table structure analysis unit 5 reads the item name of each column defined at the header position of the table B, for example, the name such as “sales amount” and sets it in the print format memory 8, and also sets the position of the format of the table B. Is read out and set in the print format memory 8. After that, the table structure analysis unit 5 gives a start command to the expanded file creation unit 9.

The development file creation unit 9 refers to the contents of various tables in the parameter analysis table 6 and designates a file to be totaled from among various source files A... Based on the records extracted from the file, the expansion records are sequentially generated one record at a time, and written to the expansion file 11.
When the development file 11 is created in this way, the development file creation unit 9 gives a start instruction to the development totalization processing unit 12.

The development tabulation unit 12 sequentially creates a total record one record at a time based on the contents of the development file 11 with reference to the configuration file 7 and writes it into the total file 13. When the tally file 13 is created in this way, the development tally processing unit 12 gives a start command to the print processing unit 14. The print processing unit 14 forms a form by causing the printer 15 to print out the contents of the tabulation file 13 together with the form format one record at a time in accordance with the print format set in the print format memory 8.

Next, the operation of this embodiment will be described. First,
When an instruction to create a table A and a table B is issued from the input unit 1 to obtain a desired form, the parameter setting unit 2 operates in response to the instruction. First, at the time of 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. In this state, the input section 1 inputs the parameter data of Table A. FIG. 3A is a display example when parameter data is input to the A table. Here, in the row direction of the table A, in order to specify the arrangement position of the record name in the aggregation record corresponding to the aggregation levels A, B, and C, a general substitute name instead of the actual record name is written in parentheses. Has been entered. For example, “(Sales office)” is input in row No. “01” corresponding to aggregation level A, and “(Customer)” is input in row No. “02” corresponding to aggregation level B. Have been. Note that the hierarchical structure of the aggregation level has a relationship of A>B> C,
If the position of the record name is defined corresponding to the aggregation level, the records are aggregated in a hierarchical structure according to the aggregation level, and the record of the aggregation level B is compared with the record of the aggregation record A at a higher level. Aggregated into records.

In Table A, arbitrary file names and item names are input. For example, A shown in FIG.
In the table, the file name “collected file” is input, and this defines the target file name from which file the totals record should be extracted. Also, a first specification item and a second specification item are input as item names corresponding to the file names. For example, the item name “sales office code” is input as the first specified item, and the item name “customer code” is input as the second specified item, and this defines the target item name to be extracted as the aggregation record. Corresponding to these two item names, the code conditions of the items to be totaled are entered in Table A, respectively. That is, the row No. “0”
For "1", the code condition "10?"
Is input, and the code condition “3 ???” is input in the row No. “02” corresponding to the second designated item. The code condition “10?” Indicates that all item codes including the upper two-digit value “10” of each item code consisting of a three-digit numerical code are to be counted. The code condition “3 ???” indicates that all item codes including the upper one digit value “3” of each item code consisting of a four-digit numerical code are to be counted. As described above, the code conditions are defined in the table A in association with a plurality of item names. In this case, records respectively corresponding to a plurality of record conditions are counted. That is, all records having a value of "10" in the upper two digits of the office code and a value of "3" in the upper one digit of the customer code are to be totaled. In the illustrated example, the code condition of the first designated item is defined in line No. “01” in order to clarify the hierarchical relationship, but the line No. “0”
It is the same even if it is defined at the corresponding position of "2".

On the other hand, the table A has an output order area corresponding to each row No. The "output order" defines the order in which the record contents corresponding to the corresponding code condition are output. It is. Here, row No. “01”,
In the example shown in the figure, "code order" is input as the output order corresponding to "02", indicating that the corresponding records should be output in ascending order. That is, for example, in a case where a record having "102" and a record having "105" as the item codes that match the code condition of the sales office code respectively correspond, first, a record having the item code "102", And item code "1"
05 "should be output in the order of the records. Note that the “output order” may be in the order of names, reverse order, or the like in addition to the order of codes. In the table A, a management unit area is provided corresponding to each row, and an arbitrary row is designated and a circle is inputted at a position corresponding to the row. This management unit is referred to when the configuration file 7 is created. When the table A is created in this way, the parameter setting unit 2 sets the parameter data in the parameter file 4.

Next, the parameter setting section 2 reads out the basic format of Table B from the parameter file 4 and causes it to be displayed and output. In the heading of this line direction, "Format", "Target file", "Total item"
Are fixedly set in advance, and each column item of the heading portion in the column direction of the table B is associated with “A”, “B”, “C”,. I have.

In the state where the basic format of Table B is displayed and output, the business person in charge
Enter the parameter data for the table. FIG. 3B is a display example when parameter data is input to the table B. Here, an item name to be printed out as a data item of the total record is input in the heading portion in the column direction of the table B. For example, the item name “sales amount” is input in the item position “B”. In the line item of Table B, "Format"
The column width, character type, character size, and the like are input for each column item as the print format of the item data. In the next “target file”, “collected file” is input corresponding to the column item position “B”. Further, the next “total item” defines which item data is to be aggregated from the records extracted as the target of aggregation, and the column item position “B”
"Sales amount" is entered in correspondence with. When the table B is created in this way, the parameter setting unit 2 sets the parameter data in the parameter file 4.

Now, after creating the tables A and B, the input unit 1
If you specify any form name from and give the print command,
The table structure analysis unit 5 creates the configuration file 7 according to the table A parameters. Here, FIGS. 5 to 8 are flowcharts showing the operation when creating the configuration file 7, and FIGS.
FIG. 9 is a diagram showing an operation content when creating the configuration file 7, and FIG. 10 is a diagram showing a specific content of the configuration file 7 created based on the table A shown in FIG. It is. The configuration record is composed of "child code", "parent code", "end mark", and "name".
The “parent code” is a code that indicates the correspondence between the tallying target item and the corresponding tallying record, and the parent-child relationship (up / down relationship) in the hierarchical structure of the tallying level.
The "end mark" is a flag that is set to "1" when the parent code includes the highest aggregation level A, and is higher when the end mark is set to "1". Indicates that record aggregation to the level is not performed. The “name” is the record name of the tally record, and is a name automatically generated by referring to an index table or the like in the table memory 6.

First, the table structure analysis unit 5 reads the parameter data of the table A from the parameter file 4, and specifies a source file in the data file 10 indicated by the file name defined in the table A (step A1). ). Next, the first row of the table A is designated (step A
2) Clear all the contents of the later-described work memory (see FIG. 9B) in the table structure analysis unit 5 (step A3), and designate the work memory as the currently focused level (current level). Specify the row level (Step A
4). Then, a record having an item code that matches the code condition of the first designated item defined in Table A is searched from the designated file (step A5). Now, in Table A shown in FIG. 3A, “collected file” is defined as the file name, and “10?” Is defined as the code condition of the first designated item (item name “sales office code”). Top 2
A record having a business office code having a digit value of “10” is retrieved from the collection file. In this case, it is assumed that the collection file is configured as shown in FIG.
That is, the sales office code from the top of the collection file is “112”, “102”, “102”, “105”,
Assuming that records having "105", "125",... Are sequentially stored, first, a record corresponding to the code condition "10?" Place code "102"
The record with is searched.

Then, the current level and the current A
Level row data is generated from the row number of the table and the item code in the corresponding record (step A6). Now, because the focus is on the first row of table A, the current level is “A”, the row number is “01”, the item code in the corresponding record is “102”,
Therefore, the level row data "A01"
102 "is generated. Next, the name corresponding to the corresponding item code is read from the index table in the table memory 6 (step A7). That is, the file recognition table in the table memory 6 corresponding to the file name defined in the table A is accessed, and the table name corresponding to the item name of the first designated item is called by referring to the file recognition table, The index table corresponding to the table name is accessed, and the name corresponding to the corresponding item code is read from the index table. In this case, the name "B office" corresponding to the item code "102" from the office table
Is read. Next, the generated level row data and the name read from the index table are set at the current level position of the last item work memory (step A8). As a result, as shown in FIG. 9B, the level row data “A” corresponds to the current level A position of the last item work memory.
01102 "and the name" B office ". The final item work memory is configured to store level row data and names corresponding to the aggregation levels A, B, C, D... As shown in FIG. 9B.

Next, it is checked whether or not the management unit area of the current line is marked with a circle (step A9). Since the first row of the A table is not marked with a circle, it is checked whether data is set in the next row of the A table (step A10). Here, when the setting is detected, the current line is updated and the next line is designated (step A11). As a result, the second row of the table A is specified and the process proceeds to step A12, where an error check is performed to determine whether or not the level of the specified row is equal to or higher than the current level. The following contents are all cleared (step A13). Now
Since the designated row level B is less than the current level A, the process proceeds to step A14, and the current level is updated using the designated row level as the current level.

Next, the process proceeds to step A15 in FIG. 6, and the code of the second designated item defined in the table A in the search record (the record retrieved in step A5 based on the code condition of the first designated item) Check whether the item code corresponding to the condition is included. Now, the code condition of the second designated item (item name “customer code”) is “3 ???”
The search record is the second record shown in FIG. 9D, that is, the record having the sales office code "102", and the customer code "3" in the second search record.
001 ”matches the code condition“ 3 ??? ”
This is detected in step A16 and step A17
To the last item in the work memory, the level position one level higher than the current level B (the position of the aggregation level A)
Row No. "01" from the level row data stored in
And the item code “102”. Then, the current level B and the row No. “0” read from the last item work memory
1 and the item code "102" and the item code "3001" corresponding to the code condition of the second designated item are sequentially combined to generate level row data "B011023001" (step A18). Next, based on the item code "3001" corresponding to the code condition of the second designated item, the corresponding name "XX store" is read from the index table (customer table) (step A19), and this name is stored in step A18. Is set to the level position corresponding to the current level in the last item work memory together with the level line data generated in step (A20). As a result, the level row data “B011023001” and the name “XX store” are set at the level B position of the last item work memory (see FIG. 9B). And the next step A
In step 21, this level line data is set as a child code of the constituent record (see FIG. 9A).

Next, proceeding to step A31 in FIG. 7, the level row data stored at the (current level + 1) level position is read from the last item work memory, and this is set as the parent code of the configuration record. . Now, the current level is B, and therefore the level line data “A011” stored at the level A position of the last item work memory.
02 "is the parent code (see FIG. 9A). Here, if the level of the parent code is A (step A3)
3), "1" is set as the end mark of the configuration record (step A34). Next, the name of the parent code is read from the last item work memory and set as the name of the configuration record (step A35). In this manner, the child code “B011023001” as data for one record,
When the parent code "A01102", the end mark "1", and the name "B office" are prepared, this configuration record is written out as data of the first record of the configuration file 7 as shown in FIG. 10 (step A36). .

When the first configuration record is generated in this way, the process returns to step A9 in FIG. 5. In this case, the current row, that is, the management unit area corresponding to the row No. "02" is indicated by a circle. , The process proceeds to step A36 in FIG. 8, and from the level line data stored at the current level position in the last item work memory, the item code “102” corresponding to the code condition of the first designated item and the The item code “3001” corresponding to the code condition of the two specified items is read out, and this combination code is set as a child code of the next configuration record (see FIG. 9C). Next, the level row data “B01102300” stored at the current level position in the last item work memory
"1" is read and set as the parent code of the configuration record (step A37), and the name of this parent code is read from the last item work memory and set as the name of the configuration record (step A38). FIG. 9C shows the configuration record generated by this,
This configuration record has a child code of “1023001”, a parent code of “B011023001”, and a name of “XX store”, and is written out as data of the second record of the configuration file 7 (step A39).

When the second record is formed as described above, the process proceeds to step A22 in FIG. 6, and in the last item work memory, the level row data stored in the level position one level higher than the current level is stored. The item code "102" is read from the file, and a search is made to determine whether another record having the same code as the item code exists in the source file (step A23). Now, as shown in FIG. 9D, the sales office code of the third record of the collection file is also "102", so the presence of the same code is detected in step A24, and the process returns to step A15. In this case, the customer code of this search record is "3003", and therefore matches the code condition "3 ???" of the second designated item, so that a configuration record is generated based on this search record as described above. I do. That is, the row No. “0” read from the next higher level position in the last item work memory
1 ", item code" 102 ", current level B, second
The level line data "B011023003" is generated from the item code "3003" of the designated item (steps A17 and A18), and the name "xx sales" corresponding to the item code "3003" is read from the customer table (step A17). A19), the level line data and the name are set at the current level position of the last item work memory (step A20). As a result, the contents of the level B position of the last item work memory shown in FIG.
The level row data is “B011023003” and the name is “xx sales”. Then, this level line data is set as a child code of the constituent record (step A).
21). Next, the level row data “A01102” read from the level A position of the last item work memory is set as the parent code of the configuration record (step A31), and “1” is set as the end mark of the configuration record (step A31). A33) and the name of the parent code "B office"
Is set as the name of the configuration record (step A3).
4). The configuration record generated in this way is written to the third record of the configuration file 7 (see FIG. 10).

Subsequently, the process returns to step A9. In this case as well, since the presence of a circle is detected in the management unit, FIG.
As a result of the execution of steps A36 to A39, the fourth configuration record shown in FIG. 10 is generated. In this case, the child code is “1023003” and the parent code is “B0”.
11023003 ", and the name is" xx sale ".

Then, returning to step A22 in FIG.
In this case, as shown in FIG.
Since there is no other record whose sales office code is “102”, the process proceeds to step A25, and another item code corresponding to the code condition “10?” Of the first designated item is searched from the collection file. In this case, as shown in FIG.
As a record corresponding to this code condition, there is a record having the office code "105" in the fourth record of the collection file, so the presence of the corresponding code is detected in step A26, and the process proceeds to step A27. Name and line from the level line data stored in the level position one level higher than the current level
No. is read out, and level line data is generated from the level name and the line No. and the item code corresponding to the code condition of the first designated item (step A28). In this case, “A01105” is generated as the level row data. Next, based on the item code "105" corresponding to the first designated item, the corresponding name "E business office" is read out from the index table (step A29), and this is displayed together with the level row data and one level higher than the last item work memory. It is set at the level position (step A30). As a result, the contents of the level A position of the last item work memory shown in FIG. 9B are rewritten, and the level row data is “A01105” and the name is “E business office”.

Next, returning to step A15, in this case, the customer code of the fourth record of the collection file is "3
102 ", and therefore the code condition" 3?
? ? , A configuration record is generated based on this record (steps A17 to A21, A31 to A31).
A35). As shown in FIG. 10, the fifth record generated by this process has a child code “B0110”.
53102 ", the parent code is" A01105 ", the end mark is" 1 ", and the name is" E office ". Hereinafter, step A
In step 10, the process of generating the configuration record is repeated one record at a time until no setting is detected in the next row of the table A. As a result, a configuration file 7 as shown in FIG. 10 is created.

When the configuration file 7 is created in this way, the table structure analysis unit 5 reads out the table B parameters from the parameter file 4, reads out the format data from the parameter data, and sets them in the print format memory 8. In this case, the table structure analysis unit 5 reads out the item names of each column defined in the header position of the table B and sets them in the print format memory 8. After that, the table structure analysis unit 5 activates the expanded file creation unit 9.

Then, the expanded file creating section 9 performs an expanded file creating process according to the flowchart of FIG. The development file 11 is an intermediate file that is generated before the tally file 13 that is the output data of the form is created. Here, FIG. 12 shows an expanded record generated according to the contents of the source file when the source file is a collected file. First, the development file creator 9 specifies a source file corresponding to the file name defined in the table A in the parameter file 4 (step B1), and specifies a first record of the specified file (step B2). Then, an item code corresponding to the first specified item defined in Table A is read from the specified record (step B3), and it is checked whether the item code satisfies the code condition (step B4). Now, the head record of the collection file is specified and the item code “112” corresponding to the first specified item “sales office code” is read. However, since this item code does not correspond to the code condition “10?” B
The process proceeds to step 7 to check whether or not the next record exists in the specified file. If so, the next record is specified in step B8, and the process returns to step B3.

As a result, the second record of the collection file is specified, and the office code “102” is read. Since this office code satisfies the code condition of the first designated item, the process proceeds to step B5, where the item code corresponding to the second designated item of Table A is read from the designated record, and it is checked whether the code condition is met. (Step B6). Now, the second designated item is “customer code”, and the item code “3001” corresponds to the code condition “3 ???”.
The corresponding code "1" corresponding to the specified item and the second specified item
02 "and" 3001 "are combined and set as the classification key of the expanded record. Next, from the specified record
The item data corresponding to the tabulated item in the table is read (step B10), and is set at the corresponding position of the expanded record (step B11). Here, since “sales amount” is defined in the column item position B as a total item of the table B, the sales amount “200,
000 "is read out and set to the corresponding position B of the expanded record. The developed record thus generated is written to the first record of the developed file 11 (step B12).

Next, returning to step B7, the third record of the designated file is designated. This record is also A
Since each of the code conditions of the first and second designated items defined in the table is satisfied, an expanded record is generated based on the record. The expanded record in this case is shown in FIG.
The contents of the second record shown in FIG. Further, a development record is generated based on the fourth record of the collection file, and the contents of the third record shown in FIG. 12 are obtained.
Hereinafter, the above-described operation is repeated for all records of the specified file, and processing for generating an expanded record one record at a time is performed. Thus, when the expanded file 11 is created,
The development file creation unit 9 activates the development totalization processing unit 12.

FIG. 13 is a flowchart showing the operation of the development and aggregation processing unit 12, and FIG.
FIG. 4 is a diagram for specifically explaining the operation content of FIG. The development file creation unit 9 generates the total file 13 based on the contents of the development file 11 and the contents of the configuration file 7 in accordance with the component development method. First, the development tabulation unit 12 reads data of one record from the top of the development file 11 (step C1). Then, in the next step C2, it is checked whether or not the data has ended, that is, whether or not all the records have been read from the beginning of the development file 11. Since the first case is a case where data for one record is read from the beginning of the development file 11, the process proceeds to the next step C3,
The contents of the configuration file 7 are searched, and a child code that matches the classification key is searched from the configuration file 7. Now, as shown in FIG. 12, the classification key in the first record of the development file 11 is “1023001”, and the configuration file 7 has a configuration record having a child code that matches this as shown in FIG. Since it exists in the record, the fact is detected in step C3 and the process proceeds to step C4, where a record (total record) of the total file 13 is generated.
That is, in the specific example of FIG. 14, first, the development and aggregation processing unit 12 reads the parent code corresponding to the child code “1023001” from the configuration file 7 and reads the parent code “B
“011023001” is decomposed into a totaling level and other numerical values, and this numerical value “011023001” is arranged as the first item of the first record of the totalizing file 13, and “B” of the totaling level is arranged subsequently thereto. Then, the name “XX store” corresponding to the child code is read from the configuration file 7 and is arranged in the next item of the tally record. Following this, the data item "200,00"
"0" is sequentially arranged after the next item of the tally record.

When the first record data of the totalization file 13 is generated, the generated record is written to the totalization file 13.
If a record having the same classification key already exists in the file, the record is collected into one record and written in the aggregation file 13, and if no record with the same classification key exists, the newly generated record is newly added. Total file 1
3 (step C5).

Next, it is checked whether or not the end mark is set at the corresponding record position in the configuration file 7 (step C6). Here, the end mark in the configuration file 7 is "1" when the aggregation level of the parent code is "A".
Returning to step 3, if the end mark is not "1", a new expansion record is generated and written to the expansion file 11 (step C7). In this case, since the end mark is not set in the corresponding record position of the configuration file 7, FIG.
A new expansion record as shown in FIG. 4 is generated and returned to the expansion file 11. In other words, if a record at a higher level than the total record generated this time is defined in Table A,
In order to add up the totaling result of the totaling record generated this time to a record at a higher level, a new expanded record is generated and written to the printer 15. Here, the corresponding parent code “B01102300” in the configuration file 7
"1" is placed in the first item, followed by the expanded file 1
A record formed by sequentially arranging the item data read from No. 1 at corresponding positions is written to the development file 11.

Thereafter, the flow returns to step C3, and thereafter, the entire contents of the configuration file 7 are searched, and the above operation is repeated until the corresponding record is not detected. As a result, when the absence of the record is detected in step C3 and the mismatch ends, the process returns to step C1 and reads the next record from the development file 11. Such an operation is performed for all records in the development file 11. Then, the end of data is detected in step C1, and the process proceeds to step C8.
The records constituting the tally file 13 are sorted according to the key content of the first item. In this case, the development tabulation unit 12 sorts the contents of the tabulation file 13 in accordance with the output order defined in the table A in the parameter file 4. FIG. 15 shows the contents of the tally file 13 in this case, in which (A) shows before sorting and (B) shows after sorting. Here, "output order" defined in Table A
Since “sales office” and “customer” are in code order, the corresponding records in the totalization file 13 are sorted in ascending order (code order) according to the key contents, as shown in FIG. It becomes a line. After that, the development tabulation unit 12 activates the print processing unit 14. Then, the print processing unit 14 fetches the contents of the print format memory 8 and prints out the contents of the aggregation file 13 together with the form format from the printer 15 in accordance with the print format, thereby creating a form. In this case, the print processing unit 14 reads the total records one record at a time from the top of the total file 13, determines the total level included in the total records, and, together with the corresponding ruled line format for grouping, displays the total records in the total records. Is printed out one record at a time, and each item name stored in the print format memory 8 is sequentially taken out and printed out at a corresponding position in the ruled line format. FIG. 2 shows a form printing example in this case. In the row direction, the name of the totaling record is printed along with the format of the hierarchical structure corresponding to the totaling level, and the item name of the totaling record is printed in the column direction. Further, the contents of the aggregation file 13 are printed out for each record.

As described above, in this embodiment, even if a large number of item codes are collectively designated by defining the target items for extracting the total record by the code condition, all the items corresponding to the code condition are specified. The name of the record is read from the index table, automatically generated, and output to the position where the record name is defined in advance. Therefore, it is not necessary to describe the name of the totaled record one by one.
The description can be greatly simplified, the whole can be easily viewed, and description errors can be reduced. Also, when specifying a large number of item codes as aggregation targets,
It is not necessary to directly describe the contents of the item codes one by one in accordance with the arrangement order of the output order. Even if the codes are collectively specified by describing the code conditions, all records corresponding to the code conditions are defined in advance. Since the output is performed in the arrangement order according to the output order, the description of the aggregation definition table can be further simplified. Also, when multiple code conditions are defined in a hierarchical structure according to the aggregation level,
All records corresponding to a plurality of code conditions are classified and tabulated according to the tabulation level, and the tabulation results are output in a hierarchical structure. ) Does not need to be created, and anyone can easily obtain a desired form simply by writing a simple summary definition table.

[0040]

Second Embodiment Hereinafter, a second embodiment will be described with reference to FIGS. FIG. 16 shows the table A of the present embodiment. The definition contents corresponding to the row Nos. “01” and “02” of the table A are the same as those of the first embodiment, but the row No. Is directly described in association with the aggregation level, and the code content of the target item when extracting the aggregation record is defined as it is in association with the first specified item and the second specified item. That is, in the present embodiment, items that do not correspond to the code conditions corresponding to the first and second designated items of the first embodiment can also be counted. An item that satisfies the code condition “10?” Of the first specified item but does not correspond to the code condition “3 ???” of the second specified item, ie,
The code content of the first designated item is “105”, and the code content of the second designated item is “2001”. The record name “ZZ sales” is directly described in the row No. “03” in correspondence with the aggregation level B, but this name is not a general substitute name as in the first embodiment. Since it is a record name, there is no need to write it in parentheses. As described above, even when the description for collectively specifying a plurality of calculation target items and the description for individually specifying the calculation targets are mixed, in the present embodiment, the record calculation is performed according to the definition contents and the definition is performed. The form is output with the image as the contents.

FIG. 17 shows the contents of the configuration file 7 created based on the table A shown in FIG. Here, the seventh record and the eighth record of the configuration file 7 are newly generated configuration records in the present embodiment, and the others are the same as those in the first embodiment. The newly generated configuration record is characterized by the code form of its child code and parent code, and uses a special symbol called a delta symbol.
In other words, the child code of the seventh record and the parent code of the eighth record are originally “B011052001”, but “B011052001”.
105Δ03 ”, and the child code of the eighth record is originally“ 1052001 ”.
5Δ03 ”. Here, “03” following the delta symbol indicates a row number. The reason why the code content of the second designated item is represented by the delta symbol instead of "2001" is to arrange the exceptional "ZZ sales" record at the bottom line when outputting the form. That is,
As described above, the tabulation file 13 created according to the contents of the configuration file 7 is defined in the table A with the parent code (excluding the tabulation level) of the configuration record as a key and referring to the key contents. Since the sort is performed in the output order and the print order when the form is output, if the code content of the second specified item is included as it is in the key of the exceptional record, this record is not arranged at the bottom line.
To prevent this, in this embodiment, a delta symbol is used instead of the code content of the second designated item. Here, when the contents of the tally file 13 are sorted in code order (ascending order), the contents are sorted in the order of 0-9, AZ, az, and Δ.

FIG. 18 shows the contents of the tallying file 13 before and after sorting. Even if an exceptional record is included in the middle of the tallying file 13, the record is sorted in the order of the code so that the record becomes the last record. Sorted by position. Total file 13 after this sort
Is printed out, a form as shown in FIG. 19 is obtained, and the tabulation result of “ZZ sales” is arranged at the bottom line of the form, and the form is output with an image as defined. In addition,
The reason why the line number is added after the delta symbol in the configuration record is that, when a plurality of exceptional records are defined, the form is output in the order of the definition.

The present embodiment having the above-described structure has the same effect as the first embodiment. In addition, exceptional items which are not included in the description for collectively specifying a plurality of items to be totaled are also individually tabulated. Then, the form can be output.

[0044]

Third Embodiment Hereinafter, a third embodiment will be described with reference to FIGS. FIG. 20 shows Table A of this embodiment. The difference from the first embodiment is that parentheses are added by adding "," to the general substitute name described corresponding to the aggregation level. is there. If "," is added to the substitute name in this way, the corresponding item code is printed out along with the record name when the form is output (see FIG. 21). in this case,
When reading the contents of the tallying file 13 one record at a time from the beginning, the item code included in the key may be read out together with the name and printed out. The present embodiment thus configured has the same effects as the first embodiment, and if the item code is not memorized correctly, it can be recognized again.

In each of the above embodiments, the code condition of the item to be summed is "10?" Or "3 ???". A plurality of items are designated collectively by attaching a mark. For example, 123 <? <1
34 may be specified. Also,
In the above embodiment, the code condition is defined for the first and second specified items. However, a third specified item may be provided, and the code condition may be defined for the third specified item. Further, in the above embodiment, the A table and the B table are defined separately, but the A table and the B table may be defined collectively. Further, in the third embodiment, it is defined that the item code and the name are associated with each other to be printed out by adding “,” to the general substitute name, but it is not necessary to add a special symbol. By simply specifying the arrangement position of the record name, the name and the item code may be correlated and printed out.

[0046]

According to the present invention, the first item of the record name of the first hierarchy, the extraction code condition in the first item, and the second item of the record name of the second hierarchy when the record is output in the form of a plurality of hierarchies. A first definition table that defines correspondence between two items and an extraction code condition in the second item, and a second definition table that defines an output target item necessary for form output among the items included in the record in advance By defining it,
Within multiple records, extract records by hierarchy based on the definition contents in each definition table, determine record names by hierarchy, and immediately create a form that narrows down the output target items among the items in the record can do.

[Brief description of the drawings]

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

FIG. 2 is a diagram illustrating an example of a print output of a form.

FIG. 3 shows a summary definition table, where (A) is Table A and (B) is B
The figure which showed the content of the table.

4A and 4B show a part of a table memory 6, wherein FIG. 4A shows a file recognition table, FIG. 4B shows a business office table, and FIG. 4C shows a customer table.

FIG. 5 is a flowchart showing a part of a configuration file creation process in detail.

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

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

FIG. 8 is a flowchart showing a part of a configuration file creation process following FIG. 5;

9A and 9C are diagrams specifically showing a state of creating a configuration record, wherein FIG. 9A and FIG. 9C are configuration records, FIG. 9B is the contents of the last item work memory, and FIG. FIG.

FIG. 10 is a diagram showing specific contents of a configuration file.

FIG. 11 is a diagram showing a development file creation process.

FIG. 12 is a diagram showing a development record creation state.

FIG. 13 is a flowchart illustrating a development tabulation process.

14A and 14B are diagrams specifically showing the operation contents of the development and aggregation processing, in which FIG. 14A shows a state in which a summary record is generated from a development file and a configuration file, and FIG. The figure which showed the expansion record.

FIG. 15 is a diagram showing the contents of a tally file before and after the tally file is sorted.

FIG. 16 is a diagram showing a description example of a table A according to the second embodiment.

FIG. 17 is a diagram showing the contents of a configuration file according to the second embodiment.

FIG. 18 shows a state before sorting of a total file according to the second embodiment;
The figure which showed the content after sorting.

FIG. 19 is a diagram illustrating a form printing example according to the second embodiment.

FIG. 20 is a diagram showing a description example of a table A according to the third embodiment.

FIG. 21 is a diagram showing a form output example according to the third embodiment.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Input part 2 Parameter setting part 3 Display part 4 Parameter file 5 Table structure analysis part 6 Table memory 7 Configuration file 8 Printing format memory 9 Development file creation part 10 Data file 11 Development file 12 Development total processing part 13 Total file 14 Printing processing Part 15 Printer

──────────────────────────────────────────────────続 き Continued on the front page (58) Fields surveyed (Int. Cl. ⁷ , DB name) G06F 19/00 G06F 17/21-17/27

Claims (1)

(57) [Claims] 1. A plurality of records including a plurality of items are stored.
Record storage means and records in multiple layers
The first item of the first layer record name and the first
Extraction code condition for one item, record name of second layer
Of the second item and the extraction code condition in the second item
First definition storage for storing a first definition table for defining association
Means and the form in each item included in the record
Stores the second definition table that defines the output items required for output
A second definition storage means for performing the above, and an extraction code section of the first item.
First-level record with item code that matches the condition, above
Item code that matches the extraction code condition of the first item
Item code that meets the extraction code condition of the second item
Extracting means for extracting a second hierarchical record having the same,
Form creation based on each record extracted by the above extraction means
When performing the above, in the extracted first-level record
Enter the name corresponding to the item code of the first item in the form
And the extracted second-level record
Name corresponding to the item code of the second item in
The name of the record in the form and the extracted
1. For each record in the second layer, its individual record
Of each output target item defined in the second definition table
Read the contents and place them in association with the above record name
A form output device, comprising: a form creation unit for creating a form; and an output unit for outputting the created form.