JP2003132297A - Document preparation system by document requirement electronic preparation method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a document by processing of a computer and eliminate the need for designing and developing work of an application per document. SOLUTION: In a client computer 2, an item information requesting function 21 receives a download of item information of the document from an item information responding function 41, and it stores the item information in an item record 22. A document requirement preparing function 24 prepares document requirement information from a document layout stored in a layout record 23 and relevant item information stored in the item record 22, and a document requirement sending function 26 sends the document requirement information to a server computer 4. In the server computer 4, a document requirement receiving function 43 receives the document requirement information and stores it in a document requirement record 45, a document forming function 45 prepares document information from document requirement data of the document requirement record 45 and relevant master data of a master data recorder 44, and a printer 5 prints the document 7 by the document information.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a form creation system using a form requirement electronic creation system for creating a form by computer processing.

[0002]

2. Description of the Related Art When a form is created by computer processing, conventionally, a dedicated application is generally developed for each form based on the form creation requirements presented by figures and documents. There is.

Further, as another conventional example, Japanese Patent Laid-Open No. 2000-1819.
In 73, a general-purpose form creation system is described, in which a layout part and a data part to be printed are separately managed, and these are matched to create a form.

[0004]

When a form is created by computer processing, design and development work of a dedicated form creating application based on form requirements occurs for each form. In addition, since the design and development work of applications often depend on human labor, there is a possibility that bugs may be created due to misreading of form requirements.

Further, in the form creation system described in JP-A-2000-181973, a form format file required by the form creation system is required in some form, and a print format corresponding to each form format file is required. Work to create a module occurs. These tasks are just alternatives to application development and not an approach to solving the above problems.

The same problem occurs not only when a new form is created but also when the form requirements are changed.

An object of the present invention is to solve such a problem, present the requirements for creating a form, which has been conventionally presented by a figure or a document, in an electronic form that can be handled by a computer, and directly use the electronic form requirement. The purpose of the present invention is to provide a form creation system based on the form requirement electronic creation method that eliminates the need for designing and developing an application for each form by printing the form.

[0008]

In order to achieve the above object, the present invention provides an electronic form in which a computer can handle form requirement information composed of a form layout and item information including various items to be printed. The client computer on the request side of the form requirement to be created and sent as a form requirement, and the form requirement specified by the form requirement information received from the client computer, received, stored, and stored according to the specified form creation instruction. The server computer on the side of creating the form that is specified based on the form requirement information of the form and the master data corresponding to the form requirement information, and the client computer includes the items required for the form requirement information to be created. Stored the item information request function to request and obtain information from the server computer and the form layout -Out record and the form layout required for the form requirement information to be created are acquired from the layout record, and the corresponding items of the item information acquired from the server computer are added at each predetermined position of the acquired form layout, and the form layout is added by the added items. The form requirement creation function that creates the form requirement information in electronic form that defines the addition position of the corresponding master data in step 2, and the form requirement transmission function that sends the form requirement information created by the form requirement creation function to the server computer. The server computer has an item information response function for responding to the request from the client computer with item information, a form requirement record storing form requirement information, and an electronic form requirement transmitted from the client computer. Of the form requirement information received and received And the form requirement record, the form requirement receiving function that stores the form requirement information received in the form requirement record, and the master that stores the master data corresponding to the form requirement information stored in the form requirement record The data record and the form requirement information of the form specified from the form requirement record according to the instruction to create the specified form, and the master data corresponding to this form from the master data record. And a form creating function for creating the form specified by the above.

Further, according to the present invention, the above-mentioned form creating function is
The form is created by directly using the form requirement condition received and stored from the client computer.

Further, according to the present invention, the above-mentioned form requirement transmission function is configured such that the user interface can transmit request information for changing or deleting the form requirement information stored in the form requirement record of the server computer at any time. Is.

Further, according to the present invention, the above-mentioned form requirement creating function creates electronic form form requirement information through a user interface.

[0012]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of a form creation system using a form requirement electronic creation method according to the present invention. Reference numeral 1 is an input / output device, 2 is a client computer for requesting form requirements, 3 is the Internet, 4 is a form. The server computer on the creation side, 5 is a printing device, 6
Is an input / output device, and 7 is a form.

In FIG. 1, an input / output device 1 is a peripheral device connected to a client computer 2 for requesting form requirements (hereinafter abbreviated as client computer), and has a keyboard, a mouse, a display and the like. Further, the input / output device 6 and the printing device 5 are peripheral devices connected to the server computer 4 on which the form is created,
The input / output device 6 has a keyboard, a mouse, a display and the like. In the following, the operations of the input / output operations 1 and 6 with the keyboard and the mouse will be referred to as the operations of the input / output devices 1 and 6.

The client computer 2 creates the form requirement information in an electronic form that can be handled by the computer under the operation of the input / output device 1, and the created form requirement information is transmitted via the Internet 3. It is sent to the server computer (hereinafter abbreviated as server computer) 4 on which the form is created. Server computer 4
Receives and saves the form requirement information transmitted from the client computer 2, creates the desired form information from the form requirement information and the master data for the same under the operation of the input / output device 6, and stores the desired form information. It is supplied to the printing device 5.
The printing device 5 performs a printing operation based on the supplied form information, and the form 7 is printed.

FIG. 2 is a block diagram showing a specific example of the functional configuration of each unit in FIG. 1, 21 is an item information request function, 22 is an item record, and 23 is a layout record.
24 is a form requirement creating function, 25 is a form requirement record, 2
6 is a form requirement transmission function, 41 is an item information response function, 42
Is an item record, 43 is a form requirement receiving function, 44 is a master data record, 45 is a form requirement record, and 46 is a form creating function, and the parts corresponding to those in FIG.

In FIG. 1, the client computer 2 stores, as a layout record 23, a form layout, which is one of the form creation requirements, for the various forms created on the client side. When creating a new form, the form layout is created and additionally stored in the layout record 23. Further, in the server computer 4, information (hereinafter referred to as item information) consisting of items for each form in which the form layout is stored in the layout record 23 of the client computer 2 is another one of the form creation requirements. It is stored as the item record 42. Therefore, when a new form layout is added to the layout record 23,
Item information for this form layout is item record 4
It is additionally stored as 2.

FIG. 3 shows a form layout of a settlement account as an example of the form. For example, as shown in FIG. 4, such form layout is HTML (HyperText M
It is stored in the layout code 23 as a source code defined in the arkup Language) format. Such a form layout can be created by a means such as a general commercially available HTML editor. Further, as the item information for this, for example, as shown in FIG. 5, items necessary for the settlement account are structurally developed and configured, and this is set as an item record 42 in the server computer 4. It is stored.

The client computer 2 inserts the corresponding item information in the item record 42 of the server computer 4 into the form layout of the layout record 23 to obtain the master data corresponding to this item (this master data is stored in the server computer 4). (Stored as a master data record 44 in the master data record 44) in the form layout, the form requirement information is defined, and the server computer 4 inserts the master data record in the fitting position of the item of the form requirement information. A form is created by adding master data (date, amount of money, etc.) corresponding to this item stored in 44.

The form requirement information created by the client computer 2 remains unchanged as long as it is not updated or deleted.
The form requirements information and master data record 4 stored in this form requirement record 45 are stored in
4 and the corresponding master data stored in 4. Therefore, the client computer 2 is used when creating a form in a new format or updating the form requirement information stored in the form requirement record 45 of the server computer 4.
In the master data record 44, the form requirement record 4
The master data relating to the form requirement information stored in 5 is sequentially added and updated.

Therefore, when creating a new form or updating the form requirement information stored in the form requirement record 45, first, the server computer 4 is requested to download the item information for the form. However, when a predetermined operation for this purpose is performed on the input / output device 1, an item record list screen 8 as shown in FIG. Is displayed. On the item record list screen 8, the type of the form in which the form layout is stored in the layout record 23 is displayed, and any one of them can be selected. Here, "statement data by accounting month",
"Charge statement data", "Settlement account data",
"ELC account data" is displayed and 4 types of forms, accounting monthly statement, fee statement, settlement account and ELC
It is assumed that a bill can be created.

A specific example of the item information download operation by the operation of the input / output device 1 based on the item record list screen 8 will be described below with reference to FIGS. 7 and 8.

In the client computer 2, as shown in FIG. 7, if the item record list screen 8 is displayed (step 211) and the input / output device 1 is operated, the form "accounting data for settlement" is selected. The item information requesting function 21 requests the server computer 4 via the Internet 3 to download the item information for the form "account for settlement" (step 212).

Then, in the server computer 4, the item information response function 41 in FIG. 8 receives this download request (step 411), and the item information for this form "account for settlement" is taken out from the item record 42 (step 412). ), And transfer to the client computer 2 via the Internet 3 (step 413).

Therefore, in the client computer 2, in FIG. 7, the item information request function 21 receives this item information as a response result (step 213), and when this reception is completed (step 214), the received item information is displayed as an item. Store as record 22 (step 214),
Wait for selection of the next form on the item record list screen 8.

In the meantime, the item record list screen 8 as shown in FIG. 6 is continuously displayed on the display screen of the input / output device 1, and the item record 22 of the above item information is displayed for one selected form. After the storage of
When another form is selected, step 212-
The above operation of 215 is performed. In this way, the required item information of one or more forms can be stored as the item record 22.

When the "end" key 8a on the item record list screen 8 is operated (step 216), the above operation is finished.

In FIG. 2, when the operation for creating the form requirement information is performed by the input / output device 1 after the download of the item information is completed as described above, the form requirement creating function 24 causes the item record 22 to read from the item record 22. Item information corresponding to the form requirement information to be created, and a form layout corresponding to this form requirement information from the layout record 23 are respectively fetched and supplied to the input / output device 1 to create the form requirement as shown in FIG. The screen 9 is displayed.

The form requirement creation screen 9 is provided with an item record designating section 9a for designating item information of a form and a layout record designating section 9b for designating a form layout. An information display unit 9c is provided, and a form layout display unit 9d is provided for the layout record designation unit 9b.
Here, the forms designated by the item record designating section 9a and the layout record designating section 9b are the same, and by operating either the "▼" button of the item record designating section 9a or the layout record designating section 9b. , You can change the specified form.

The form requirement creation screen 9 shown in FIG. 9 shows a state in which the form "account for settlement" is designated.
In the item record designation section 9a, "account data for settlement"
However, in the layout record designation portion 9b, "account layout for settlement" is displayed. Then, in this state, the item information display unit 9c reads and displays the structurally expanded item information corresponding to the form “account for settlement” as shown in FIG.
In the form layout display section 9d, the form "account for settlement" is displayed.
The form layout of the source code in HTML format as shown in FIG. 4 is read from the layout record 23 and displayed as an editor screen.

By using the form requirement creation screen 9 to insert a predetermined item displayed in the item information display section 9c into a predetermined position of the form layout displayed in the form layout display section 9d, an item to be printed It is possible to create the form requirement information in which the print positions of the master data, which will be described later, for the item and the item are defined. As the definition method, for example, the cursor is positioned at a position where the master data of the item in the form layout of the form layout display unit 9d is desired to be printed, and the item information display unit 9c desired to be printed at this position.
Click to select this applicable item in. After this item is selected, the selected item is expanded into a path at the corresponding position in the form layout display portion 9d and inserted as a comment line of HTML. The form requirement information is created by repeating this operation.

The form requirement creation screen 9 shown in FIG. 9 has the element "<u><b>" in the HTML document of the form layout shown in FIG.
"<B><u>", the item "reinsurance company name" in the item information shown in Fig. 5 is inserted, and by the above operation, this item becomes a comment line <!-Xsl: value. -of select = "
It is embedded in the above element as the reinsurance company name "/->".

Here, a specific example of the operation of the form requirement creating function 24 by the operation on the form requirement creating screen 9 is shown in FIG.
The description will be made with 0.

In the figure, when the form requirement creating function 24 is activated by a predetermined operation of the input / output device 1, the form requirement creating screen 9 shown in FIG. 9 is used as a user interface.
It is expanded on the display screen of the input / output device 1 (step 2401). When item information of a predetermined form, for example, item information of the form “account for settlement” is designated by the item record designation unit 9a on the form requirement creation screen 9 (step 2402), the designated item information is designated as an item. It is input from the record 22 (step 2403), this content is structurally developed (step 2404), and displayed on the item information display portion 9c of the form requirement creation screen 9 (step 2405).
Next, the layout record designating section 9b on the form requirement creation screen 9 is used to form a layout of a predetermined form, here,
When the form layout of the form "account for settlement" is designated (step 2406), the designated form layout is input from the layout record 23 (step 240).
7), the form layout display section 9 on the form requirement creation screen 9
It is displayed in d (step 2408).

When the form layout and the item information correspond to each other on a one-to-one basis, the item information of the form "settlement account" and the corresponding form layout are specified.
Item record designation section 9a and layout record designation section 9
By operating either "▼" button of b
It is done at the same time. However, the same item information may correspond to a plurality of form layouts even for the same type of form. For example, even a bill for payment may have a different format depending on the customer. In such a case, the item record designation section 9a and the layout record designation section 9b can independently select the item information and the form layout. However, even in this case, for example, when item information (or the form layout in the layout record designation unit 9b) which is the item record designation unit 9a is designated, the layout record designation unit 9b.
(Alternatively, the item record designating section 9a) may designate only a form layout (or item information) of a type determined by the designated item information (or form layout). For example, when the item information of the form "account for settlement" is designated in the item record designation unit 9a, the operation of the "▼" button in the layout record designation unit 9b causes the form layout display unit 9d to display the form "for settlement". Only the form layout of "Invoice" is displayed.

After that, on the form requirement creation screen 9, the cursor is positioned at a position for determining the position to print the master data in the form layout of the form layout display section 9d, and the corresponding desired item in the item information display section 9c. When is clicked (step 2409), the clicked item is expanded as a comment line in HTML at the position of the cursor in the form layout display portion 9d (step 2411). At this time, if the cursor position breaks the HTML tag (step 2410), a warning message is displayed (step 2412) and the path expansion of the item is not executed.

When the "end" button 9e is operated (step 2413), the form requirement creating function 2
The operation of 4 ends.

In this way, the form requirement information is created by sequentially inserting the necessary items in the HTML document of the form layout, and an example thereof is shown in FIG. This is done by inserting the items “Accounting month”, “Reinsurance amount”, “Reinsurance fee”, “Reinsurance refund”, and “Fee rate” in the HTML document of the form layout shown in FIG. For example, the item "Accounting month" is an HTML element "<td ALIGN =" right "> month </ td> that follows the HTML element"<td> Accounting month </ td>"in FIG. 〉 ”, A comment line, <!-Xsl: value-of select =" Accounting month "/->. In addition, the item "reinsurance amount" is a comment line in the component "<td ALIGN =" right "> Yen </ td>" that follows the component "<td> reinsurance amount </ td>" in Fig. 4. ,
<!-Xsl: value-of select = "Set-in account information / reinsurance information / reinsurance amount"/-> Here, the item "reinsurance amount" is a subordinate item of the items "accounting information for settlement" and "reinsurance information" in a hierarchical structure as shown in FIG. ,
As described above, items including hierarchically higher items are added as "account information for settlement / reinsurance information / reinsurance amount". This means that the other items "reinsurance premium", "reinsurance refund",
The same applies to the “commission rate”, which is shown in FIG.
As shown in, it is embedded in the form layout.

In this way, the form requirement information (displayed as it is on the form layout display portion 9d in FIG. 9) is created, and when the input / output device 1 performs the following operation, the form requirement creating function 24 The completed form requirement information is stored as the form requirement record 25. Similarly, the form requirement information can be created for the item information of other forms stored in the item record 22, and the created form requirement information is stored as the form requirement record 25.

The form requirement information is uploaded to the server computer 4 by the form requirement transmitting function 26. When the input / output device 1 is operated for this purpose, the form requirement creating function 24 operates as a user interface. A form requirement ordering screen 10 as shown in FIG. 12 is displayed on the display screen of the input / output device 1. On the form requirement order screen 10, various form names including forms corresponding to the form requirement information stored in the form requirement record 25 are displayed, and any one or more of them can be selected. Here, the forms are “statement statement by accounting month”, “commission statement”, “account for settlement”, “E”.
It is assumed that this form requirement information is stored in the form requirement record 25.

The form requirement ordering screen 10 also displays a "new" button 10a, an "update" button 10b, a "delete" button 10c, and an "end" button 10d operated by a mouse. The "new" button 10a is an operation button for requesting an upload as a form for newly adding form requirement information, and the "update" button 10b is a form already stored in the server computer 4, as will be described later. The delete button 10c is an operation button for updating the requirement information, the delete button 10c is an operation button for deleting the form requirement information already stored in the server computer 4, and the "end" button 10d is the form requirement ordering screen. It is an operation button for ending the operation in 10.

Next, referring to FIG. 13, a specific example of the operation of the form requirement transmission function 26 by the operation of the input / output device 1 based on the form requirement ordering screen 10 shown in FIG. 12, and according to FIG. A specific example of the operation of the form requirement receiving function 43 of the server computer 4 with respect to the operation of the function 26 will be described.

In the client computer 2, FIG.
In FIG. 12, as the user interface developed by the form requirement creating function 24 on the display screen of the input / output device 1 by starting the form requirement transmitting function 26,
When the form requirement ordering screen 10 shown in is displayed and any button on the form requirement ordering screen 10 is operated and the operation button is the "end" button 10d (step 2610), the form requirement sending function 26 Operation ends. Also, the operated button is the "new" button 1.
0a, the “update” button 10b, or the “delete” button 10c (step 2602), but when none of the forms displayed on the form requirement ordering screen 10 is selected, the input / output device 1 is warned. It waits until a message is displayed and the message is selected again (step 2604).

When any one or more of the forms displayed on the form requirement ordering screen 10 is selected and any one of the "new" button 10a, "update" button 10b, and "delete" button 10c is operated (step 2602). , 2603), a request for new, update, or deletion of the form request information to the form requirement receiving function 43 of the server computer 4, and in the case of a new request and an update request, a new or update from the request form requirement record 25. The form requirement information is read and transmitted (step 2605).

For example, on the form requirement ordering screen 10,
The form "account for settlement" is selected, and "New" button 10
When a is operated, the form requirement transmission function 26 takes in the form requirement information of the selected form "account for settlement" from the form requirement record 25, and this and the request information for the new setting thereof are stored in the server computer 4. By sending, the upload of this form request information is requested. Further, for example, when the form “statement-specific statement” is selected and the “update” button 10b is operated, the form requirement transmission function 26 sets the form requirement information of the selected form “statement-specific statement” to the form requirement record. 25, and the request information for updating this is sent to the server computer 4 to request the upload of the form requirement information. Further, for example, when the form “commission statement” is selected and the “delete” button 10c is operated, the form requirement transmission function 2
Reference numeral 6 transmits to the server computer 4 request information for deleting the form requirement information of the form “commission statement”.

Therefore, in the server computer 4, in FIG. 14, the form requirement receiving function 43 receives the form requirement information uploaded from the form requirement transmitting function 26 of the client computer 2 and the above request information, and responds to this request information. And process the form requirement record 45.

That is, when the received request information is a "new" request (step 4301), first, it is judged whether or not the uploaded form requirement information is in the form requirement record 45 (step 4302). When there is the form requirement information, an error message saying that the new setting cannot be made is sent as response information to the form requirement sending function 26 of the client computer 2 (step 4312).
If there is no such error, it is confirmed whether the received form requirement information is correct (step 4303). If there is no error, the received form requirement information is converted into the form requirement record 45.
(Step 4304), and the response information indicating the new setting is transmitted to the form requirement transmission function 26. If there is an error, an error message indicating that new setting cannot be made is transmitted as response information to the form requirement transmission function 26 of the client computer 2 (step 4312).

If the received request information is an "update" request (step 4305), first, it is determined whether the uploaded form requirement information is in the form requirement record 45 (step 4306). When there is no form requirement information, an error message indicating that updating is not possible is sent as response information to the form requirement transmitting function 26 of the client computer 2 (step 4312). If there is, there is no error in the received form requirement information. Check if there is no mistake (step 4307),
The form requirement record 45 is updated with the received form requirement information (step 4308), and the response information indicating the update is transmitted to the form requirement transmitting function 26. If there is an error, an error message indicating that updating is not possible is sent to the form requirement sending function 26 of the client computer 2 as response information (step 4312).

Furthermore, when the received request information is a "deletion" request (step 4309), it is judged whether or not the form requirement information 45 requested to be deleted exists in the form requirement record 45 (step 4310). If there is no form requirement information, an error message indicating that the form requirement information cannot be deleted is sent as response information to the form requirement transmission function 26 of the client computer 2 (step 4312). If there is this, the form requirement record 45 requires deletion. The requirement information is deleted (step 4311), and the response information indicating the deletion is transmitted to the form requirement transmission function 26.

Therefore, the form requirement transmission function 26 of the client computer 2 receives the response information from the form requirement reception function 43 in FIG. 13 (step 260).
6) When the reception is completed (step 2607), it is determined whether this response information is the previous error message (step 2608). If the response information is an error message, the error message is displayed on the input / output device 1 (step 2609), and if it is not an error message, the next operation on the form requirement ordering screen 10 shown in FIG. 12 is waited for.

In this way, when the form requirement transmission function 26 makes an upload request for each form requirement information for new setting or update stored in the form requirement record 25 or a request for deleting the form requirement information, the form requirement information is deleted. Requirements reception function 4
3 receives these form requirement information and request information, and processes the form requirement record 45 according to the request information.
As a result, the form requirement record 45 is in a state in which the newly added form requirement information and the updated form requirement information are stored.

When the transmission by the form requirement transmission function 26 is completed, the client computer 2 receives the item information stored in the item record 22 and the form requirement record 25.
The form requirement information stored in is deleted as unnecessary.

Further, on the form requirement ordering screen 10, "new" button 10a, "update" button 10b, "delete" button 1
Even if any of 0c is operated, the form requirement ordering screen 10 continues to be displayed as it is, unless the "end" button 10d is operated. As a result, for example, it is possible to request upload of the newly set form requirement information to the server computer 4 and then successively request to upload the next updated form requirement information to the server computer 4. And this form requirement order screen 1
When the "end" button 10d is operated at 0 (step 2610 in FIG. 13), the above operation of the form requirement transmission function 26 ends.

In FIG. 2, the form requirement information created in the client computer 2 is stored in the form requirement record 45 in this way. By performing an operation of designating the form by the user interface of the input / output device 6. The form creation function 46 reads the form requirement information of the form specified from the form requirement record 45 and the corresponding master data from the master data record 44, adds the master data to this form requirement information, and adds the master data to the form. Create information. This form information is supplied to the printing device 5 and printed, whereby the specified form 7 is obtained.

FIG. 15 is a diagram showing a specific example of master data stored in the master data record 44.

In the figure, the master data has a hierarchical structure. In the illustrated example, the data "ID",
"Accounting month", "Reinsurance company name", "Reinsurance company code",
"Payment account number" becomes the main data with a specific numerical value, and the main data "Payment account number" is the sub data with a specific numerical value such as "Insurance item" and "Security number / branch number". Attached as data, the data “insurance amount”, “insurance fee”,
“Currency refund”, data “reinsurance rate”, “reinsurance amount”,
"Reinsurance fee", "Reinsurance refund", "Reinsurance fee rate"
Is attached as a sub-data with a concrete numerical value.

When a form is designated, a form creation screen 11 as shown in FIG. 16 is displayed on the display screen by performing a predetermined operation on the input / output device 6. In the form creation screen 11, for inputting predetermined condition data for conditioning the master data to be used and the form selecting section 11a that displays the type of form corresponding to the form requirement information stored in the form requirement record 45. And a data input section 11b of. By performing a predetermined operation on the input / output device 6 based on this form creation screen 11,
Form information in which master data is added to the form requirement information is created.

A specific example of the operation of the form creating function 46 by operating the input / output device 6 based on the form creating screen 11 shown in FIG. 16 will be described below with reference to FIG.

In the figure, the form creating function 46 is activated by the operation of the input / output device 6, and the form creating screen 11 is displayed on the display screen of the input / output device 6 as a user interface developed by the form creating function 46. This is displayed (step 4601), and this form creation screen 11 is displayed.
Then, when the “end” button 11d is operated without selecting a form (step 4609), the form requirement transmission function 26
Operation is completed, and either button 11c, 11d
Is also not operated (steps 4609, 460
2) The form creating function 46 is in a standby state as it is.

On the other hand, the desired form is selected in the form selection section 11a of the form creation screen 11, and the data input section 11 is selected.
After inputting the specified condition data in b, click the "Print" button 1
When 1c is operated (step 4602), it is determined whether or not the master data matching the condition indicated by the condition data of the selected form exists in the master data record 44 (step 4608). A message to that effect is sent to the device 6 and the system stands by, but if there is master data that matches this condition, the form requirement information of the selected form is acquired from the form condition record 45 (step 460).
4).

The form selected by the form selection unit 11a of the form creation screen 11 will be described below as the "account for settlement". In the data input unit 11b, "accounting month" is October and "reinsurance company code" is When the “Print” button 11c is operated by inputting the condition data for XX insurance company, whether the master data for which the accounting month for the settlement account of XX insurance company is October is in the master data record 44. It is judged (step 4603), and if there is, the form requirement function 4
6 obtains the form requirement information of “settlement account” from the form requirement record 45 (step 4604).

Then, the form is edited in accordance with the HTML format defined in the form requirement information of the acquired "settlement account" (step 4605), and the edited form requirement information is read from the master data record 44. By adding (pasting) the master data (step 4606), the data input unit 11 of this form creation screen 11
Accounting month specified by the condition data input in b
Form information of "month", "invoice for settlement" of reinsurance company (XX insurance company) code is created, output to the printing device 7 and printed (step 4607).

Here, in the form requirement information acquired from the form requirement record 45, as described in FIG. 11, the insertion position of the comment line by the start tag “<!-” And the end tag “->” is set. It is defined as the position where the master data is added. For example, if the "accounting month" is October, the master data of this item "accounting month" is "10", and the comment line <!-Xsl: In value-of select = "Accounting month"/->,
"Accounting month" is replaced with "10". Note that this "10" is printed by replacing this "accounting month" with "10."
The HTML in which the above comment line is embedded in FIG.
Element <td ALIGN = "right"><!-Xsl: value-of select
"Month" is printed after the above comment line in "Accounting month"/-> month </ td>. The above is the item "reinsurance amount", "reinsurance fee", "reinsurance refund",
The same applies to the “reinsurance fee rate”.

FIG. 18 shows the form 7 thus created.
Showing a settlement account as a specific example of
Each item “sama” printed on this settlement account 7,
"Settlement account", "Accounting month", "Reinsurance amount", "Reinsurance fee", "Reinsurance refund", "Fee rate" and unit "Month", "Yen", "%" are figures It is already added to the form layout shown in FIG. 4 and is added when the form layout is created. In addition, "1" of these items
Numerical values such as “0” and “500,000” are added to the form requirement information of “account for settlement” acquired from the form requirement record 45 by the form requirement function 46 by the above operation using the form creation screen 11 shown in FIG. It is the master data.

The form creation screen 11 remains displayed even after the "print" button 11c is operated, which allows the next form to be created continuously.
When the "end" button 11d is operated, the above-described operation of creating the form information by the form requirement function 46 ends (FIG. 17).
4609).

Although the embodiment of the present invention has been described above, the present invention is not limited to this embodiment. For example, in the above embodiment, the HTML format has been described as an example of an electronic form that can be handled by a computer, but the invention is not limited to this, and any format may be used as long as the computer can handle it. Also, the form has been described as an example, and is not limited to the above example.

[0066]

As described above, according to the present invention,
Since the form creation requirements can be presented in an electronic form that can be handled by a computer and the forms can be printed directly using the electronic form requirements, it is necessary to design and develop an application for each form. It is possible to provide a form creation system and a printing method.

[Brief description of drawings]

FIG. 1 is a block diagram showing an embodiment of a form creation system by a form requirement electronic creation system according to the present invention.

FIG. 2 is a block diagram showing a specific example of a functional configuration of each unit in FIG.

FIG. 3 is a diagram showing a form layout of a settlement account as an example of a form in the specific example shown in FIG.

FIG. 4 is a diagram showing an HTML-format source code of the form layout shown in FIG.

FIG. 5 is a diagram showing a specific example of item information for the form layout shown in FIG.

FIG. 6 is a diagram showing a specific example of an item record list screen expanded by the item request function in FIG.

FIG. 7 is a diagram showing the item record list screen shown in FIG.
5 is a flowchart showing a specific example of an operation for downloading item information of the item request function in FIG.

FIG. 8 is a diagram showing the operation of the item request function shown in FIG.
5 is a flowchart showing a specific example of the operation of the item information response function in FIG.

9 is a diagram showing a specific example of a form requirement creation screen developed by the form requirement creation function in FIG.

10 is a flowchart showing a specific example of the operation of the form requirement creation function in FIG. 2 using the form requirement creation screen shown in FIG.

FIG. 11 is a diagram showing a specific example of form requirement information created by the form requirement creating function in FIG. 2;

FIG. 12 is a diagram showing a specific example of a form requirement ordering screen developed by the form requirement creating function in FIG.

13 is a diagram using the form requirement ordering screen shown in FIG.
5 is a flowchart showing a specific example of the operation of the form requirement transmission function in FIG.

14 is a flowchart showing a specific example of the operation of the form requirement receiving function in FIG. 2 with respect to the operation of the form requirement transmitting function shown in FIG.

FIG. 15 is a diagram showing a specific example of master data stored in a master data record in FIG.

FIG. 16 is a diagram showing a specific example of a form creation screen developed by the form creation function in FIG.

17 is a flowchart showing a specific example of the operation of the form creation function in FIG. 2 using the form creation screen shown in FIG.

FIG. 18 is a diagram showing a specific example of the form obtained in the specific example shown in FIG.

[Explanation of symbols]

1 I / O device 2 Client computer requesting form requirements 3 Internet 4 Form creation side server computer 5 Printing device 6 I / O device 7 reports 8 item record list screen 8a "End" button 9a Item record specification part 9b Layout record specification section 9c Item information display section 9d Form layout display section 9e "End" button 10 Form requirement order screen 10a "New" button 10b "Update" button 10c "Delete" button 10d "End" button 11 Form creation screen 11a Form selection section 11b Data input section 11c "Print" button 11d "End" button 21 Item information request function 22 item records 23 Layout record 24 Form requirement creation function 25 Form requirement record 26 Form requirement transmission function 41 Item information response function 42 item records 43 Form requirements reception function 44 Master data 45 Form requirement record 46 Form creation function

Claims (3)

[Claims] 1. A client computer that requests and sends a form requirement, which creates and transmits form requirement information composed of a form layout and item information including various items to be printed in an electronic form that can be handled by a computer. The form requirement information transmitted from the client computer is received, stored, and stored, and the form requirement information of the specified form among the stored form requirements is stored according to the instruction to create the specified form. A form creating server computer that creates a specified form based on the master data corresponding to this is provided, and the form requirement requesting client computer is the item information required for the form requirement information to be created. The item information request function to request and acquire the form creation server computer, and the layout of the form. The stored layout record and the form layout required for the form requirement information to be created are acquired from the layout record, and the item information of the item information acquired from the server computer that created the form is acquired at each predetermined position of the acquired form layout. A form requirement creating function for creating form requirement information in an electronic form in which a corresponding item is added, and an addition position of the corresponding master data in the form layout is defined by the added item, and the form requirement creating function It has a form requirement transmission function of transmitting the form requirement information created in step 1 to the form creating side server computer, and the form producing side server computer requests the item information from the form requirement requesting client computer. To the item information response function that responds to the item information, and the form requirement record that stores the form requirement information. And the form requirement information in electronic form transmitted from the request-side client computer of the form requirement, check the contents of the received form requirement information and the form requirement record, and then select the form requirement record. By the form requirement receiving function for storing the received form requirement information, the master data record in which the master data corresponding to the form requirement information stored in the form requirement record is stored, and the instruction to create the specified form, The form requirement information of the form specified from the form requirement record is acquired from the master data records, and the master data corresponding to the form is acquired from the master data record, and the form specified from the acquired form requirement information and the master data is acquired. A form creation system using a form requirement electronic creation method, which has a form creation function of creating a form. 2. The form requirement transmission function according to claim 1, wherein a request for changing or deleting the form requirement information stored in the form requirement record of the server computer on which the form is created is transmitted by the user interface. A form creation system based on the electronic form creation method, which is characterized by being able to send. 3. The form requirement creating function according to claim 1, wherein the form requirement creating function interactively uses the user interface in which layout information in HTML format and structurally expanded item information are displayed at the same time. A form creation system using a form requirements electronic creation method characterized by creating requirement information.