JPH0778213A - Form output device - Google Patents

Abstract

(57) [Abstract] [Purpose] To obtain the desired form, simply specify the position of the record name of the output record and the code condition of the output target item according to the form output image. Is read from a predetermined file and is output as an image according to the specified contents together with its name. [Structure] When the layout position of the record name of the totalized record is specified from the input unit 1 and the code condition indicating the target item when the totalized record is extracted is specified, the table structure analysis unit 5 sets the items that match this code condition. The record having the code is read from the predetermined file, and the name corresponding to this item code is read from the index table. The name read by this is output to the arrangement position of the record name, and the record read from the predetermined file is output in association with the corresponding name.

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

[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. By the way, in order to specify an arbitrary item and read a record including the item from a predetermined file and output the form, the name of the output record and the output target item are set to 1 in advance while considering the layout such as the record arrangement position. It was necessary to input them in correspondence with each other.

[0003]

However, if the name or the output target item is directly input for each output record when the number of records is large, the input work becomes extremely difficult and there is a risk of a description error or the like. There was also. An object of the present invention is to obtain all desired records by simply specifying the layout position of the record name of the output record and the code condition of the output target item according to the form output image, in order to obtain the desired form. It is to be able to read from a predetermined file and output the image with the name and the specified contents.

[0004]

Means for Solving the Problems The means of the first invention is as follows. (1A), the designating unit designates the arrangement position of the record name of the output record and also designates the code condition indicating the target item when the output record is extracted. Here, the code condition is, for example, an item code consisting of a three-digit numerical code,
By specifying the upper 2 digits as the code condition, the code condition for specifying all the item codes including the upper 2 digits code as the extraction target item, that is, the code condition for specifying the extraction target range. If a plurality of items are not extracted, the item code may be designated as the code condition. (2A), the table storage means stores an index table in which item codes and names are associated with each other. (3A), the reading means reads a record having an item code that matches the code condition designated by the designating means from a predetermined file, and reads the name corresponding to the item code from the index table. (4A), the output means outputs the name read by the reading means to the arrangement position of the record name designated by the designating means, and associates the record read from the predetermined file with the corresponding name. Output. When the name read by the reading unit is output to the arrangement position of the record name specified by the specifying unit, the corresponding item code may be output together with the name. The means of the second invention is as follows. (1B), the first designating means designates the record name of the output record and also designates the code content indicating the target item when the output record is extracted. Here, the code content of the target item is, for example, the item code as it is, that is,
When the item code is composed of a 3-digit numerical code, the 3-digit numerical code is the code content as it is. (2B), the second designating means designates the layout position of the record name of the output record and also designates the code condition indicating the target item when the output record is extracted. (3B), the table storage means stores an index table in which item codes and names are associated with each other. (4B), the first reading means reads a record matching the code content designated by the first designating means from a predetermined file. (5B), the second reading means reads a record having an item code that matches the code condition designated by the second designating means from a predetermined file, and also reads a name corresponding to the item code from the index table. . (6B), the first output means outputs the record read by the first reading means in association with the record name designated by the first designating means. (7B), the second output means outputs the name read by the second reading means to the arrangement position of the record name designated by the second designating means, and is also read from the predetermined file. The record is output in association with the corresponding name.

[0005]

The operation of the means of the first invention is as follows. Now, in order to obtain the desired form, if you specify the layout position of the record name added to the output record and also specify the code condition that is the target item when extracting the output record, items that match this code condition The record having the code is read from the predetermined file, and the name corresponding to this item code is read from the index table. The name read by this is output to the arrangement position of the record name designated in advance, and the record read from the predetermined file is output in association with the corresponding name. The operation of the means of the second invention is as follows. Now, in order to obtain the desired form, in addition to specifying the record name of the output record and the code content that is the target item when extracting the output record, the record added to the output record is the same as above. Specify the placement position of the name and the code condition. Then, a record that matches the specified code content is read from the predetermined file and is output in association with the specified record name. Further, a record having all the item codes that match the designated code condition is read from the predetermined file, the name corresponding to this item code is read from the index table, and this name is output to the record name arrangement position. At the same time, the record read from the predetermined file is output in association with the corresponding name. Therefore, in order to obtain the desired form, all the records that match the code condition are read from the specified file by simply specifying the layout position of the record name of the output record and the code condition of the output target item according to the form output image. , It is possible to output a form with its name and an image as specified.

[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. for each aggregation level using the aggregation definition table. The records corresponding to the definition contents of the table are read from a predetermined file, the records are classified and aggregated in a hierarchical structure according to the aggregation level, and the aggregation 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 section 2 operates in response to a start command from the input section 1, and in order to instruct any record aggregation desired by a person in charge of business or the like, an arrangement position of record names of aggregated records and items to be aggregated. A definition table (two types of tables A and B in this embodiment) that defines the code conditions and the like is generated in accordance with the data input from the input unit 1, and is displayed and output from the display unit 3. Set to file 4. Since the tables A and B will be described in detail later, they will be briefly described 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 summary definition table according to the output image of this form.
Generate a table. Here, in the form shown in FIG. 2, the record name of the totalized record is arranged in the line item, and the data item name of the totalized record is arranged in the column item, and the table A defined for obtaining this form is Tables (A) and B of FIG. 3 are configured as shown in (B) of FIG. In addition to the file name to be totalized, the table A defines the arrangement position of the record name in the totalized record, the code condition indicating the target item when extracting the output record, etc., corresponding to the totalization level. That is,
In the example shown in the figure, "collection file" is specified as the file name of the aggregation target, and "sales office" is used as a general substitute name for the actual record name, for example, XX sales office, XX sales office, etc. The position of the record name is specified by writing in parentheses. Note that this description method is arbitrary, and the position may be specified by a simple method such as adding a circle to the position where the record name is arranged, but in this embodiment, a general substitute name is described. The name is enclosed in parentheses to indicate that it is a substitute name. In addition, for example, “10?” Is designated as the code condition indicating the target item when extracting the totalized record.
This 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 totaled items.
In other words, to specify multiple item codes in a single definition ,? Although the code condition is defined by the marked description, when only one item code is designated, the item code may be defined as the code condition as it is. The table B defines the item name output as the data item of the totalized record and the format at the time of printing the form, the totaling target file, and the totaling target item extracted as the data item corresponding to this item name.

In the parameter file 4, the basic formats (ruled line data, etc.) corresponding to the tables A and B are fixedly stored in advance by the maker side, and various types are arbitrarily input from the input section 1. Table A 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 and B
A correspondence table that correlates with the table parameter data is stored.

The table structure analysis unit 5 operates according to the start command input from the input unit 1 when printing the form, and analyzes the A table parameter data and the B table parameter data corresponding to the form name arbitrarily designated 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 or the like in which item codes and names are associated with each other, and this index table or the like is arbitrarily set by the user from the input unit 2. The table structure analysis unit 5 refers to the table memory 6 and creates the configuration file 7 while reading the names corresponding to all the item codes matching the code condition of the table A from the index table.

FIG. 4 shows a part of the table set in the table memory 6. The file recognition table is provided for each file, and is a table in which the file item name is associated with the table name of the index table, and the illustrated file recognition table is a table corresponding to the collection file. Further, 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 this index table and the name is automatically generated.

The configuration file 7 will be described in detail later,
It is composed of various constituent records representing the correspondence between the item code to be totaled and the corresponding totalization record, the parent-child relationship (upper and lower relationships) in the hierarchical structure of the totalization level, and the like. Further, the table structure analysis unit 5 reads out the item name of each column defined in the header position of the B table, for example, the name of “sales amount” and sets it in the print format memory 8, and the position of the B table format. The print format of each column defined in 1 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 expansion file creation unit 9.

The expansion file creating unit 9 refers to various table contents in the parameter analysis table 6 to specify a file to be totalized from various source files A ... Based on the records extracted from the file, expanded records are sequentially generated one by one and written in the expanded file 11.
When the expansion file 11 is created in this way, the expansion file creation unit 9 gives a start command to the expansion aggregation processing unit 12.

The expansion totalization processing unit 12 refers to the configuration file 7 and sequentially creates one total record based on the contents of the expansion file 11 and writes the totalized records in the totalization file 13. When the totalization file 13 is created in this way, the expansion totalization processing unit 12 gives a start instruction to the print processing unit 14. The print processing unit 14 prints out the contents of the totalization file 13 from the printer 15 one record at a time in accordance with the print format set in the print format memory 8 together with the form format, thereby creating a form.

Next, the operation of this embodiment will be described. First,
When the input unit 1 gives an instruction to create the tables A and B in order to obtain a 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. In this state, the parameter data of Table A is input from the input unit 1. FIG. 3A is a display example when parameter data is input to the A table. Here, in the row direction of table A, in order to specify the layout position of the record name in the totalized record corresponding to the totaling levels A, B, and C, the general substitute name in place of the actual record name is written in parentheses. It has been entered. For example, in row No. “01”, “(sales office)” is entered corresponding to the aggregation level A, and in row No “02” is entered “(customer)” corresponding to the aggregation level B. Has been done. In addition, the hierarchical structure of the aggregation level has a relation of A>B> C,
If the layout position of the record name is defined in correspondence with this aggregation level, the records are aggregated in the hierarchical structure according to the aggregation level, and the records of the aggregation level B have the records of the aggregation record A at a higher level than that. It is aggregated into records.

Further, in the table A, arbitrary file names and item names are entered. For example, A shown in FIG.
In the table, the file name “collected file” is entered, and by this, the target file name from which the total record should be extracted is defined. Further, the first designated item and the second designated item are input as the item names corresponding to the file names. For example, the item name “sales office code” is input as the first designated item, and the item name “customer code” is input as the second designated item, which defines the target item name to be extracted as the aggregated record. Corresponding to these two item names, the code conditions of the items to be totaled are entered in the table A, respectively. That is, line No. "0
"1" corresponds to the first designated item and the code condition "10?"
Is entered, and the code condition “3 ??????” is entered in line No. “02” corresponding to the second designated item. The code condition "10?" Indicates that all item codes including the upper 2-digit value "10" of each item code consisting of a 3-digit numerical code are to be totaled items. Further, the code condition “3 ????” indicates that all the item codes including the value “3” of the upper one digit of each item code consisting of the four-digit numerical code are set as the aggregation target items. In this way, the code conditions are defined in the illustrated table A in association with a plurality of item names. In this case, records corresponding to a plurality of record conditions are to be aggregated. That is, all records having the value “10” in the upper two digits of the business office code and the value “3” in the upper one digit of the customer code are to be aggregated. 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.
Even if it is defined in the corresponding position of "2", it is equivalent.

On the other hand, the table A is provided with an output order area corresponding to each row No. This "output order" defines in what order the record contents corresponding to the corresponding code conditions are output. Is. Here, line No. “01”,
In the illustrated example, "code order" is input as the output order corresponding to "02", indicating that the output should be performed in the order of arrangement such that the corresponding records are in ascending order. That is, for example, when 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 to the record having the item code “102”, And the item code "1
It is defined that records should be output in the order of the records having "05". The "output order" may be a code order, a name order, a reverse order, or the like. Further, the table A has a management unit area corresponding to each row, and an arbitrary row is designated and a circle is input at a position corresponding to the designated row. It should be noted that 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 the table B from the parameter file 4 and outputs it for display. In this heading section in the row direction, "Format", "Target file", and "Summary item" are used as labels for the line item.
Is fixedly set in advance, and each column item in the heading section in the column direction of the table B is associated with “A”, “B”, “C” ... As a name indicating the item position. There is.

Now, in the state in which the basic format of the table B is displayed and output, the person in charge of business works from the input section 1 to the B
Enter the parameter data in the table. FIG. 3B is a display example when parameter data is input to the B table. Here, in the heading portion in the column direction of table B, the item name to be printed out as the data item of the total record is input. For example, the item name “sales amount” is entered in the item position “B”. Also, in the line item of table B, "format"
The column width, character type, character size, etc. are input for each column item as a print format of item data. Further, in the next "target file", "collection file" is input corresponding to the column item position "B". Further, the next “total item” defines which item data should be totaled from the records extracted as the total target, and the column item position “B”.
"Sales amount" is entered corresponding to. When the table B is created in this way, the parameter setting unit 2 sets the parameter data in the parameter file 4.

After creating tables A and B, input section 1
If you specify an arbitrary 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, FIG. 5 to FIG. 8 are flowcharts showing the operation when creating the configuration file 7,
FIG. 9 is a diagram showing operation contents when the configuration file 7 is created, and FIG. 10 is a diagram showing specific contents of the configuration file 7 created based on the table A shown in FIG. Is. The configuration record consists of "child code", "parent code", "end mark", and "name".
The “parent code” is a code that represents a correspondence relationship between the item to be totaled and the corresponding totalized record, and represents a parent-child relationship (upper / lower relationship) in a hierarchical structure at the totaling level.
The “end mark” is a flag that becomes “1” when the parent code includes the highest aggregation level A, and is higher than the end mark when “1” is set. It indicates that records are not aggregated to the level. The “name” is the record name of the totalized record, and is the name automatically generated by referring to the index table or the like in the table memory 6.

First, the table structure analysis unit 5 reads the parameter data of the A table from the parameter file 4 and specifies the source file in the data file 10 indicated by the file name defined in the A table (step A1). ). Next, specify the first row of table A (step A
2) Clear all the contents of the final item work memory (see FIG. 9B) in the table structure analysis unit 5 described later (step A3), and specify it as the currently focused level (current level). Specify the line level (Step A)
4). Then, the record having the item code that matches the code condition of the first designated item defined in the table A is searched from the designated file (step A5). Now, in the table A shown in FIG. 3A, "collection file" is defined as the file name and "10?" Is defined as the code condition of the first designated item (item name "office code"). Top 2
A record having a sales office code with a digit value of “10” is searched from the collection file. In this case, the recovery file is assumed to be configured as shown in FIG.
That is, in the collection file, the business office codes are “112”, “102”, “102”, “105”,
Assuming that the records having “105”, “125”, ... Are sequentially stored, first, as the record corresponding to the code condition “10?” Of the first designated item, the second record from the collection file, that is, the sales Office 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, since 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 line 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 this file recognition table, The index table corresponding to this table name is accessed and the name corresponding to the corresponding item code is read from this index table. In this case, the name "B sales office" corresponding to the item code "102" from the sales 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 in the last item work memory (step A8). As a result, as shown in FIG. 9B, the level line data “A
"01102" and the name "B sales office" are set. The final item work memory is configured to store level line data and names corresponding to the aggregation levels A, B, C, D ... As shown in FIG.

Next, it is checked whether or not the management unit area of the current line is circled (step A9). Since the first row of the A table is not marked with a circle, the next row of the A table is focused on to check whether or not data is set in that row (step A10). 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 table A is designated, and the procedure advances to step A12, and an error check is performed to see if the level of the designated row is at or above the current level. The following contents are all cleared (step A13). Now
Since the designated row level B is lower than the current level A, the process proceeds to step A14, where the designated row level is set as the current level and the current level is updated.

Next, proceeding to step A15 in FIG. 6, the code of the second designated item defined in the table A in the retrieved 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 for the second designated item (item name "customer code") is "3 ????"
Then, 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.
Since "001" matches the code condition "3 ???",
When this is detected in step A16, step A17
To the last item, in the work memory, the level position one level higher than the current level B (position of the aggregation level A)
No. "01" from the level line data stored in
And the item code “102” are read. Then, the line number "0" read from the current level B and the last item work memory
1 ”and the item code“ 102 ”are sequentially combined with the item code“ 3001 ”corresponding to the code condition of the second designated item to generate the level line 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 read in step A18. It is set to the level position corresponding to the current level in the final item work memory together with the level row data generated in step A20. As a result, the level line data "B011023001" and the name "XX store" are set at the level B position of the final item work memory (see FIG. 9B). And the next step A
At 21, the level line data is set as a child code of the constituent record (see (A) of FIG. 9).

Next, in step A31 of FIG. 7, the level line data stored at the level position (current level + 1) is read out from the last item work memory and set as the parent code of the configuration record. . Now, the current level is B, so the level line data “A011” stored at the position of level A in 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 to the end mark of the configuration record (step A34). Next, the name of the parent code is read from the final item work memory and set as the name of the configuration record (step A35). In this way, the child code “B011023001” as data for one record,
When the parent code "A01102", the end mark "1", and the name "B office" are complete, this configuration record is written out as the data of the first record of the configuration file 7 as shown in FIG. 10 (step A36). .

When the first constituent record is generated in this way, the process returns to step A9 in FIG. 5, but in this case, the management unit area corresponding to the current line, that is, the line No. "02" is circled. 8, the process proceeds to step A36 of FIG. 8 and the item code "102" corresponding to the code condition of the first designated item is determined from the level line data stored at the current level position in the last item work memory. The item code "3001" corresponding to the code condition of the two designated items is read out, and this combination code is set as a child code of the next configuration record (see (C) of FIG. 9). Next, the level line data "B01102300" stored at the current level position in the last item work memory.
1 "is read out and set as the parent code of the configuration record (step A37), and the name of this parent code is read out 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 as data of the second record of the configuration file 7 (step A39).

When the constituent record of the second record is generated in this way, the process proceeds to step A22 in FIG. 6, and the level line data stored in the last item work memory is stored in the level position one level higher than the current level. The item code "102" is read from the inside, and it is searched whether another record having the same code as this item code exists in the source file (step A23). Now, as shown in FIG. 9 (D), the office code of the third record of the collection file is also "102", so that 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. Therefore, the configuration record is generated based on this search record as described above. I do. That is, the line number "0" read from the level position one level higher in the last item work memory.
1 ”, item code“ 102 ”, current level B, second
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 S17). A19), this level line data and 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. 9B are rewritten,
The level line data is “B011023003”, and the name is “XX sale”. Then, this level line data is set as a child code of the configuration record (step A
21). Next, the level line data “A01102” read from the position of level A of the last item work memory is set as the parent code of the configuration record (step A31), and “1” is set to the end mark of the configuration record (step S31). A33) and the name of the parent code "B sales office"
Is set as the name of the constituent record (step A3).
4). The configuration record thus generated is written in the third record of the configuration file 7 (see FIG. 10).

Then, the process returns to step A9, but in this case as well, a circle mark is detected in the management unit.
As a result of execution of steps A36 to A39, the fourth constituent record shown in FIG. 10 is generated. In this case, the child code is “1023003” and the parent code is “B0
"11230003" and the name is "XX sale".

Then, returning to step A22 in FIG. 6,
In this case, as shown in (D) of FIG.
Since there is no other record having the office code of "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 the record corresponding to this code condition, there is a record whose sales office code is "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, where the final item work memory. Level name and line from the level line data stored in the level position one level higher than the current level in
No is read, and level line data is generated from the level name and line number, 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 sales office" is read from the index table (step A29), and this is read along with the level row data, and is 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 final item work memory shown in FIG. 9B are rewritten, and the level line data becomes "A01105" and the name becomes "E sales office".

Next, returning to step A15, in this case, the customer code of the fourth record of the collection file is "3.
102 ”, and thus the code condition“ 3?
? ? ", The configuration record is generated based on this record (steps A17-A21, A31-).
A35). As shown in FIG. 10, the child record “B0110” is generated in the fifth component record thus generated.
53102 ”, the parent code is“ A01105 ”, the end mark is“ 1 ”, and the name is“ E sales office ”. Step A below
In step 10, the process of generating the configuration record is repeated record by record until no setting is detected in the next row of table A. As a result, the 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 the B table parameter from the parameter file 4, reads the format data from this parameter data, and sets it in the print format memory 8. In this case, the table structure analysis unit 5 reads the item name of each column defined in the header position of the table B and sets it in the print format memory 8. Then, the table structure analysis unit 5 activates the expansion file creation unit 9.

Then, the expansion file creating unit 9 executes the expansion file creating process according to the flowchart of FIG. The expansion file 11 is a file that is intermediately generated until the total file 13 that is the output data of the form is created. Here, FIG. 12 shows the expansion record generated according to the contents of the file when the source file is the recovery file. First, the expansion file creation unit 9 specifies the source file corresponding to the file name defined in the table A in the parameter file 4 (step B1) and the top record of this specified file (step B2). Then, the item code corresponding to the first designated item defined in the table A is read from this designated record (step B3), and it is checked whether this item code satisfies the code condition (step B4). Now, the first record of the collection file is designated and the item code "112" corresponding to the first designated item "sales office code" is read out, but since this item code does not correspond to the code condition "10?", The step B
7, the process proceeds to step 7 to check if the next record exists in the specified file. If there is, the next record is specified in step B8, and then the process returns to step B3.

As a result, the second record of the collection file is designated and the business office code "102" is read. Since this office code corresponds to the code condition of the first designated item, the process proceeds to step B5, the item code corresponding to the second designated item of the 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 ????"
Corresponding code "1" corresponding to the designated item and the second designated item
02 "and" 3001 "are combined and set as the classification key of the expansion record. Next, from the specified record, B
Item data corresponding to the tabulated items in the table are read (step B10) and set to the corresponding positions of the expansion record (step B11). Here, since the “sales amount” is defined in the column item position B as the total item of the table B, the sales amount “200,” is calculated from the second record of the collection file.
“000” is read out and set in the corresponding position B of the expansion record. The expansion record thus generated is written to the first record of the expansion file 11 (step B12).

Next, returning to step B7, the third record of the designated file is designated. This record is also A
Since the code conditions of the first and second designated items defined in the table are respectively satisfied, the expansion record is generated based on the record. The expansion record in this case is shown in Figure 1.
This is the content of the second record shown in 2. Further, a developed record is also generated in the fourth record of the collected file based on the fourth record, and has the contents of the third record shown in FIG.
Hereinafter, the above-described operation is repeated for all the records of the specified file, and a process of generating expanded records one by one is performed. When the expansion file 11 is created by this,
The expansion file creation unit 9 activates the expansion aggregation processing unit 12.

FIG. 13 is a flow chart showing the operation of the expansion totalization processing unit 12, and FIG. 14 is the expansion totalization processing unit 12.
FIG. 7 is a diagram for specifically explaining the operation content of FIG. The expansion file creation unit 9 generates the totalization file 13 according to the parts expansion method based on the contents of the expansion file 11 and the contents of the configuration file 7. First, the expansion totalization processing unit 12 reads data for one record from the beginning of the expansion file 11 (step C1). Then, in the next step C2, it is checked whether the data has ended, that is, whether all the records have been read from the beginning of the expanded file 11. First, since the data for one record is read from the beginning of the expanded 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 expansion file 11 is "1023001", and the configuration file 7 has a configuration record having a child code matching this as shown in FIG. Since it exists in the record, it is detected in step C3 and the process proceeds to step C4 to generate a record (total record) of the total file 13.
That is, in the specific example of FIG. 14, the expansion tabulation processing unit 12 first reads the parent code corresponding to the child code “1023001” from the configuration file 7, and the parent code “B
“011023001” is decomposed into a totaling level and other numerical values, and this numerical value “011023001” is placed in the first item of the first record of the totaling file 13, and the totaling level “B” is placed following it. Then, the name "XX store" corresponding to this child code is read from the configuration file 7 and placed in the next item of the total record. Following this, the data item “200,00” of the expansion file 11
"0" is sequentially arranged after the next item of the aggregation record.

When the data of the first record of the totalization file 13 is generated in this way, this generated record is written to the totalization file 13. At this time, the totalization file 13
If a record having the same classification key already exists in the record, it is put together into one record and written into the totalization file 13. If no record having the same classification key exists, the record generated this time is newly added. Summary 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", and when the end mark is "1", the step C is used as it is.
Returning to step 3, if the end mark is not "1", a new expanded record is generated and written in the expanded file 11 (step C7). In this case, since the end mark is not set in the corresponding record position of the configuration file 7,
A new expansion record as shown in 4 is generated and returned to the expansion file 11. That is, if a record at a higher level than the aggregate record generated this time is defined in table A,
A new expansion record is generated and written to the printer 15 in order to total the totalized result of the totalized records generated this time to the record at the higher level. Here, the corresponding parent code “B01102300” in the configuration file 7
"1" is placed in the first item, followed by expansion file 1
A record formed by sequentially arranging item data read from 1 at corresponding positions is written to the expansion file 11.

Thereafter, the process 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 no corresponding record is detected in step C3 and the mismatch ends, the process returns to step C1 to read the next record from the expanded file 11. Such an operation is performed for all the records of the expanded file 11. Then, the end of data is detected in step C1 and the process proceeds to step C8,
The records forming the totalization file 13 are sorted according to the key content of the first item. In this case, the expansion totalization processing unit 12 sorts the contents of the totalization file 13 according to the output order defined in the table A in the parameter file 4. FIG. 15 shows the contents of the tabulation file 13 in this case, (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 aggregation file 13 are sorted in ascending order (code order) according to their key contents, as shown in FIG. It becomes a line. After that, the development totalization processing unit 12 activates the print processing unit 14. Then, the print processing unit 14 takes in the content of the print format memory 8 and prints out the content of the totalization file 13 together with the form format from the printer 15 according to the print format to create the form. In this case, the print processing unit 14 reads the totalized records one by one from the beginning of the totalization file 13, determines the totalization level included in the totalized record, and determines the totalized level in the totalized record together with the corresponding ruled line format for bundling. The name and data are 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 the corresponding position of the ruled line format. FIG. 2 is an example of printing a form in this case. In the row direction, the format of the hierarchical structure according to the aggregation level is printed, the names of the aggregation records are printed, and the item names of the aggregation records are printed in the column direction. Further, the contents of the totalization file 13 are printed out for each record.

As described above, in the present embodiment, even if a large number of item codes are collectively designated by defining the target item for extracting the totalized record by the code condition, all items corresponding to the code condition are 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 totalized record one by one.
The description can be greatly simplified, the whole is easy to see, and the description error 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 code one by one according to the arrangement order of the output order, and even if they are collectively specified by the description of the code condition, all the records corresponding to this code condition are defined in advance. Since the output is performed in the order according to the output order, the description of the aggregate definition table can be further simplified. Also, when multiple code conditions are defined in a hierarchical structure according to the aggregation level,
All records that correspond to multiple code conditions are classified and aggregated according to the aggregation level, and this aggregation result is output in a hierarchical structure. Therefore, an expert such as a system engineer in advance can classify and aggregate code systems (code conversion table). ) Is not required to be created, and anyone can easily obtain a desired form simply by describing a simple tabulation definition table.

[0040]

[Second Embodiment] A second embodiment will be described below with reference to FIGS. FIG. 16 shows the A table of the present embodiment, and the definition contents corresponding to the row numbers “01” and “02” of the A table are the same as those of the first embodiment, but the row No “03” has the aggregation record. Is directly described in association with the aggregation level and the code content of the target item when the aggregation record is extracted is defined as it is in correspondence with the first designated item and the second designated item. That is, in the present embodiment, items which do not correspond to the code conditions corresponding to the first and second designated items of the first embodiment can be targeted for aggregation. Items that correspond to the code condition “10?” Of the first designated item but not the code condition “3 ???” of the second designated item, that is,
The definition content is shown in which the code content of the first designated item is “105” and the code content of the second designated item is “2001”. Although the record name "ZZ sale" is directly described in the row No. "03" in association with the aggregation level B, this name is not a general substitute name as in the first embodiment. Since it is the record name of, it is not necessary to write it in parentheses. As described above, even if the description for collectively specifying a plurality of items to be totalized and the description for individually specifying the totaling target are mixed, in the present embodiment, the record totalization is performed according to the definition contents and the definition is performed. The form is output with the image as it is.

FIG. 17 shows the contents of the configuration file 7 created based on the table A shown in FIG. Here, the 7th record and the 8th record of the configuration file 7 are the configuration records newly generated in this embodiment, and the others are the same as those in the first embodiment. This newly generated configuration record is characterized by the code form of its child code and parent code, and a special symbol called a delta symbol is used.
That is, the child code of the 7th record and the parent code of the 8th record are originally "B011052001".
It is expressed by "105Δ03", and the child code of the 8th record is originally "1052001".
5Δ03 ”. Here, "03" following the delta symbol indicates a row number. In this way, the reason why the code content “2001” of the second designated item is replaced by the delta symbol is that this exceptional “ZZ sale” record is arranged at the bottom line when the form is output. That is,
As described above, the totalization file 13 created in accordance with the contents of the configuration file 7 uses the parent code (excluding the totalization level) of the configuration record as a key, and is defined in the table A by referring to this key content. Since the records are sorted in the output order and sorted in the print order when the form is output, if the code content of the second designated item is included as it is in the key of the exceptional record, this record will not be placed at the bottom line.
In order to prevent this, in this embodiment, a delta symbol is used in place of the code content of the second designated item. Here, when the contents of the totalization file 13 are sorted in code order (ascending order), they are sorted in the order of 0-9, AZ, az, and Δ.

FIG. 18 shows the contents of the totalization file 13 before and after sorting. Even if an exceptional record is included in the middle of the totalization file 13, by sorting it in code order, that record is the last record. Sorted by position. Total file 13 after this sort
When the contents of is printed out, a form as shown in FIG. 19 is obtained, and the totalized result of "ZZ sales" is placed in the bottom line of the form, and the form is output as an image according to the definition contents. In addition,
The line No. is added after the delta symbol in the constituent records in order to output the forms in the order of arrangement as defined when a plurality of exceptional records are defined.

The present embodiment thus constructed has the same effect as that of the first embodiment, and records exceptional items individually even if they are not included in the description for collectively designating a plurality of items to be aggregated. Then, the form can be output.

[0044]

[Third Embodiment] A third embodiment will be described below with reference to FIGS. FIG. 20 shows Table A of the present embodiment, which differs from the first embodiment described above in that the general substitute name described in correspondence with the aggregation level is parenthesized by adding “,”. is there. When "," 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 totalization file 13 one record at a time from the beginning, the item code included in the key may be read together with the name and printed out. The present embodiment configured as described above has the same effect as that of the first embodiment, and when the item code is not remembered correctly, it can be recognized again.

In each of the above-mentioned embodiments, a part of the item code such as "10?" Or "3 ???" Although a mark is added to specify a plurality of items at once, for example, 123 <? <1
It may be specified by a code condition such as 34. Also,
In the above embodiment, the code condition is defined in the first designated item and the second designated item, but a third designated item may be provided and the code condition may be defined in the third designated 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 together. Further, in the third embodiment, the item code and the name are associated and printed by adding "," to the general substitute name, but it is not necessary to add a special symbol. The name and the item code may be associated with each other and printed out by simply specifying the arrangement position of the record name.

[0046]

According to the present invention, in order to obtain a desired form, it is possible to match the code condition by simply specifying the arrangement position of the record name of the output record and the code condition of the output target item according to the form output image. It is possible to read all the records to be read from a specified file and output the image with the name as the specified contents, so it is necessary to directly describe the record name for each output record or the item code for each output target item. Nonetheless, anyone can easily obtain a desired form with a simple designation, 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 is a diagram showing a printout example of a form.

FIG. 3 shows an aggregation definition table, (A) is A table, and (B) is B.
The figure which showed the content of the table.

FIG. 4 is a diagram showing a part of a table memory 6, (A) showing a file recognition table, (B) showing a sales office table, and (C) showing 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.

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

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

9A and 9B are diagrams specifically showing a creation state of a configuration record, where FIGS. 9A and 9C show configuration records, FIG. 9B shows the contents of the last item work memory, and FIG. 9D shows a part of a collection file. The figure shown.

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

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

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

FIG. 13 is a flowchart showing a development totaling process.

14A and 14B are diagrams specifically showing the operation contents of the expansion and aggregation process, in which FIG. 14A is a view showing a generation record from the expansion file and the configuration file, and FIG. 14B is newly generated. The figure which showed the expansion record.

FIG. 15 is a diagram showing the contents of a totalization file before and after sorting the totalization file.

FIG. 16 is a diagram showing a description example of 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 is a diagram showing a summary file before sorting according to the second embodiment;
The figure showing the contents after sorting.

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

FIG. 20 is a diagram showing a description example of 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]

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

Claims (3)

[Claims] 1. An index table formed by associating an item code and a name with a designating unit that designates a layout position of a record name of an output record and a code condition that indicates a target item when the output record is extracted. Table reading means for storing, and a reading means for reading a record having an item code matching the code condition designated by the designating means from a predetermined file and reading a name corresponding to the item code from the index table, The name read by the reading means is output to the arrangement position of the record name designated by the designating means, and
An output device for outputting a record read from a predetermined file in association with a name corresponding to the record, and a output device. 2. When outputting the name read by the reading means to the arrangement position of the record name designated by the designating means, the output means outputs the corresponding item code together with the name. The form output device according to claim 1, characterized in that. 3. A first designation means for designating a record name of an output record, a code content indicating a target item when the output record is extracted, and a layout position of the record name of the output record. Second designation means for designating a code condition indicating a target item when extracting an output record, table storage means for storing an index table in which item codes and names are associated with each other, and the first designation means. And a record having an item code matching the code condition designated by the second designating means, from the predetermined file. Second reading means for reading the name corresponding to the item code from the index table, and the first reading means for reading the name. First output means for outputting the record in association with the record name designated by the first designating means, and the name read by the second reading means designated by the second designating means. A form output device comprising: a second output unit that outputs a record name to a layout position and outputs a record read from a predetermined file in association with a corresponding name.