JP2012118677A - Slip preparation device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To define a format of a slip corresponding to attributes of a user of the slip, and to enable the user of the slip to recognize that it is the slip that he/she can output.SOLUTION: A slip preparation device of this invention receives input defining the format of a slip in association with a user who is to output the slip and stores information specifying the slip and the user capable of outputting the slip in association. Then, to a terminal of a certain user, a list of the slips that the user can output is displayed.

Description

  The present invention relates to a form creation apparatus.

When outputting data contained in a business database as a form, settings such as selecting the data item to be output to the form or changing the output location of the data item may be made according to the purpose and user of the form. Generally done.
For example, in the invention of Patent Document 1, manufacturing-related data items (stirring time, ph value) in each manufacturing process are stored in association with the product lot, and the range of processes to be output and the data items in each process A form can be output after specifying the output location (line).

JP 2006-293571 A (Claims 1, 2 and 4)

  The invention of Patent Document 1 takes into account the creation of a form format after designating a user who can view the form for each attribute of the form user, for example, each department, position, or business in charge. Absent. Further, it is impossible for the user of the form to know what forms are available for output to him / her.

  Therefore, an object of the present invention is to define the format of the form in accordance with the attribute of the form user, and to know the form that the form user can output.

The present invention is a form creation device that outputs a part of data to a form, and the form creation device relates to data items to be output on a form in association with information for specifying the form, and information on the arrangement of the data items And the correspondence information storing the information for identifying the person who can output the form can be accessed, and the data item of the data to be output to the form, the information on the arrangement of the data item, and the form can be output. The information for identifying the person is received, and the data items of the data to be output to the form, the information on the arrangement of the data items, and the information for identifying the person who can output the form are the information for identifying the form. It is necessary to output the form together with the information specifying the candidate from the terminal device of the candidate who can output the form by instructing to store it as a record of correspondence information. Based on the information for identifying the candidate of the received record, the record having the information for identifying the accepted candidate as the information for identifying the person who can output the form, and the information for identifying the form of the identified record, It has the processing part which outputs the display which prompts output of a form to a candidate's terminal device.
Other means will be described in the embodiment for carrying out the invention.

  According to the present invention, the format of the form is defined according to the attribute of the form user, and the form user can know the form that he / she can output.

It is a block diagram of the form creation system which concerns on this embodiment. It is a figure which shows an example of the manufacturing data which concern on this embodiment. It is a figure which shows an example of the charge business data which concern on this embodiment. It is a figure showing an example of form definition data concerning this embodiment. It is a figure which shows an example of the definition form output data which concerns on this embodiment. (A) And (b) is a figure which shows an example of the form which concerns on this embodiment. (A) And (b) is a figure which shows an example of the form which concerns on this embodiment. (A) And (b) is a figure which shows an example of the form which concerns on this embodiment. It is a figure which shows an example of the form which concerns on this embodiment. (A) And (b) is a figure which shows an example of the form definition and output condition setting screen concerning this embodiment. (A) is a figure which shows an example of the form output screen which concerns on this embodiment. (B) is a figure which shows an example of the form format confirmation screen which concerns on this embodiment. It is a flowchart of a form definition / output condition setting process procedure according to the present embodiment. It is a flowchart of a form output processing procedure according to the present embodiment.

  Hereinafter, a mode for carrying out the present invention (referred to as “the present embodiment”) will be described in detail with reference to the drawings. In this embodiment, an example in which a company that manufactures food defines a format of a form for managing the manufacturing process will be described. However, it goes without saying that the present invention is widely applicable to other industries.

(Form creation system)
The form creation system 1 in FIG. 1 includes a data storage server 2, a Web server 3, a management authority user terminal device 4, and a general user terminal device 5. These are connected to each other via a wired and / or wireless network 6. The data storage server 2 is mainly installed in a management department of a company. In FIG. 1, a single unit is configured, but a configuration divided into a plurality of cases may be used. The same applies to the Web server 3. Furthermore, the data storage server 2 and the Web server 3 may be integrated into one configuration. Although the management authority user terminal device 4 is not particularly limited in location, it is assumed that one or a plurality of management authority user terminal devices 4 are mainly installed in locations where the user who defines the format of the form can use. Although the general user terminal device 5 is not particularly limited in the place where it is installed, it is assumed that one or a plurality of general user terminal devices 5 are installed in a place where a user who mainly outputs a form can use. The “form creation device” corresponds to the Web server 3.

(Data storage server)
The data storage server 2 is a general computer and includes a central control device 11, a main storage device 12, an auxiliary storage device 13, a communication device 14, an input device 15, and an output device 16. These are connected to each other by a bus. The auxiliary storage device 13 stores production data 31, work data 32, form definition data 33, and definition form output data 34 (all of which will be described later). The business data management unit 21 and the form output data management unit 22 are programs. Thereafter, when the subject is described as “XX section”, the central controller 11 reads out each program from the auxiliary storage device 13 and loads it into the main storage device 12, and then the function of each program (detailed later). (The same applies to the Web server 3 to be described later). The “corresponding information” corresponds to the form definition data 33 and the definition form output data 34.

(Web server)
The Web server 3 is also a general computer and includes a central control device 41, a main storage device 42, an auxiliary storage device 43, a communication device 44, an input device 45, and an output device 46. These are connected to each other by a bus. The form definition unit 51 and the form output processing unit 52 are programs.

  The management authority user terminal device 4 is also a general computer, and includes a central control device, a main storage device, an auxiliary storage device, a communication device, an input device, and an output device. These are connected to each other by a bus (not shown). The same applies to the general user terminal device 5.

(Production data)
The manufacturing data 31 will be described with reference to FIG.
In the manufacturing data 31, in association with the lot ID stored in the lot ID column 101, the product name column 102 has a product name, the quantity column 103 has a quantity, the process name column 104 has a process name, and an additive. The name column 105 stores the additive name, the stirring time column 106 stores the stirring time, the addition quantity column 107 stores the addition quantity, and the date / time column 108 stores the date / time.

The lot ID in the lot ID column 101 is an identifier that uniquely identifies a lot which is the minimum quantitative unit for manufacturing a product.
The product name in the product name column 102 is the name of the product.
The quantity in the quantity column 103 is the quantity of products included in the lot.

The process name in the process name column 104 is the name of the product manufacturing process.
Additive name column 105 The additive name is the name of the additive that is a substance added to the product.
The stirring time in the stirring time column 106 is a time during which the mixture of the product and the additive is stirred.
The addition quantity in the addition quantity column 107 is the quantity of the additive.
The date and time in the date and time column 108 is the date on which the process is executed.

By the way, paying attention to the record in the first line of the manufacturing data 31, on the date and time “20100110”, the product name “L0001” and the product name “vegetable juice” “2kl” and the additive name “ It can be seen that the mixture of “carrot extract” with the additive “500 ml” is stirred for “10 minutes” and the name of the process is “formulation 1”.
Further, focusing on the records in the first to third lines, the product “vegetable juice” having the lot ID “L0001” from the date “20100110” to “20100112” It becomes an object of “preservation treatment”, and it can be seen that “carrot extract”, “honey”, “preservative A” and the like are added in each step.
There are as many records of the manufacturing data 31 as the number of combinations of lot IDs and process names.

(Business data in charge)
The assigned business data 32 will be described with reference to FIG.
In the assigned job data 32, in association with the employee ID stored in the employee ID column 111, the name column 112 has a name, the affiliation column 113 has a affiliation, the position column 114 has a position, and the assigned job column 115 has a name. The work in charge is stored.

The employee ID in the employee ID column 111 is an identifier that uniquely identifies an employee of a company or the like that operates the form creation system 1. The employee may define the format of the form and may output the form in the defined format.
The name in the name column 112 is the name of the employee.
The affiliation in the affiliation column 113 is the name of the organization to which the employee belongs.
The position in the position column 114 is the position in the employee's organization.
The work in charge column 115 is the job content of the staff.
By the way, paying attention to the record 201 of the assigned business data 32, the employee whose employee ID is “P001” and whose name is “Ichiro Suzuki” belongs to the “Material Procurement Department” and the position is “General Manager”. , It turns out that the work in charge is "material procurement control".
There are as many records of the assigned business data 32 as the number of employee IDs.

(Form definition data)
The form definition data 33 will be described with reference to FIG.
In the form definition data 33, the form name is stored in the form name field 122, the output item 1 is output in the output item 1 field 123, and the output item 2 is stored in the output item 2 field 124 in association with the form ID stored in the form ID field 121. The output item 2 is stored in the output item 3 column 125, the output item 4 is stored in the output item 4 column 126, and the target date and time is stored in the target date and time column 127.
The form ID in the form ID column 121 is an identifier that uniquely identifies a form that outputs a part of the manufacturing data 31.
The form name in the form name column 122 is the name of the form.

  The output item 1 in the output item 1 column 123 is a heading of the column of the product data 31 that is output as the first column (column) of the form. The output item 1 column 123 may store a specific value in the column along with the heading of the column of the product data 31. For example, “product name“ vegetable juice ”” is stored in the output item 1 field 123 of the record 216. In this case, it means that the product name of the record having the product name “vegetable juice” among the records of the product data 31 is output in the first column of the form (after all, only the record of “vegetable juice” is arranged). (Details below).

Similarly, the output item 2 in the output item 2 column 124 is the heading of the column of the product data 31 that is output as the second column (column) on the form. The description for the output item 1 column 123 applies to the 3 column 125 and the output item 4 column 126 as well.
As described above, the values stored in the output item 1 column 123 to the output item 4 column 126 are arranged in the arrangement of the output items when a plurality of output items are output to the form 61. It shows that.
It is not necessary for the output item 1 column 123 to the output item 4 column 126 to store the heading of the product data 31 column (for example, records 211 and 212). Note that an output item 5 column, an output item 6 column, and so on may be provided immediately to the right of the output item 4 column 126.
The target date and time in the target date and time column 127 indicates the date and time of the record of the product data 31 to be output on the form in the range of the start date and the end date.

(Form definition data and corresponding form)
4 and FIGS. 6 to 9, the record of the form definition data 33 and the format of the form 61 corresponding to the record will be specifically described.
The format of the form defined by the record 211 in FIG. 4 is the format of the form “S001” 61 in FIG.
“S001” stored in the form ID column 121 of the record 211 in FIG. 4, “additive management” stored in the form name column 122 and “20100101-20100228” stored in the target date / time column 127 are: In FIG. 6A, the data are output to a form ID column 251, a form name column 252, and a target date / time column 253, respectively.
The “lot ID” stored in the output item 1 column 123 of the record 211 in FIG. 4 is the heading of the column 254a in FIG. The “product name” stored in the output item 2 column 124 is the heading of the column 254b in FIG.

  The format of the form defined by the record 212 in FIG. 4 is the format of the form “S002” 61 in FIG. When the record 211 and the record 212 in FIG. 4 are compared, the values in the target date and time column 127 are different. For example, among the records of manufacturing data 31 (FIG. 2), those included in the range of the target date and time “20100101-20100228” of the record 211 but not included in the range of the target date and time “20100301-20100331” of the record 212 (For example, the record having the product name “vegetable juice”) is output in the columns 254a and 254b in FIG. 6A, but not output in the columns 255a and 255b in FIG. 6B.

The format of the form defined by the record 213 in FIG. 4 is the format of the form “S003” 61 in FIG.
“S003” stored in the form ID column 121 of the record 213 in FIG. 4, “additive detail management” stored in the form name column 122 and “20100101-20100228” stored in the target date / time column 127 are In FIG. 7A, the data are output to a form ID column 251, a form name column 252, and a target date / time column 253, respectively.
The “lot ID” stored in the output item 1 column 123 of the record 213 in FIG. 4 is the heading of the column 256a in FIG. The “product name” stored in the output item 2 column 124 is the heading of the column 256b in FIG. The “additive name” stored in the output item 3 column 125 is the heading of the column 256c in FIG. The “added quantity” stored in the output item 4 column 126 is the heading of the column 256d in FIG.

  The format of the form defined by the record 214 in FIG. 4 is the format of the form “S004” 61 in FIG. When the record 213 and the record 214 in FIG. 4 are compared, the values in the target date and time column 127 are different. For example, among the records of the manufacturing data 31 (FIG. 2), those included in the range of the target date “20100101-20100228” of the record 213 but not included in the range of the target date “20100301-20100331” of the record 214 (For example, a record having the product name “vegetable juice”) is output in the columns 256a to 256d in FIG. 7A, but is not output in the columns 257a to 257d in FIG. 7B.

Similarly, the formats of the forms defined by the records 215, 216, and 217 in FIG. 4 are the form “S005” 61 in FIG. 8A, the form “S006” 61 in FIG. 8B, and the form in FIG. The format is “S007” 61. The description of these forms 61 is generally as described above.
8A, FIG. 8B, and FIG. 9, only the record about “vegetable juice” is output in the columns 259a to 259d in FIG. 8B. In the columns 260a to 260d of FIG. 9, only the record for “lemon juice” is output. On the other hand, records for both “vegetable juice” and “lemon juice” are output in columns 258a to 258d in FIG. This difference is that, in the form definition data 33 (FIG. 4), the “product name” is stored in the output item 2 column 124 of the record 215 without any limitation, whereas the output item 1 column of the record 216 is stored. This is because “product name“ vegetable juice ”” is stored in 123, and “product name“ lemon juice ”” is stored in the output item 1 field 123 of the record 217. That is, the records of FIG. 2 to be output in FIG. 8B and FIG. 9 are limited to those having the product names “vegetable juice” and “lemon juice”, respectively.

The definition form output data 34 will be described with reference to FIG.
In the definition form output data 34, in association with the form ID stored in the form ID field 131, the form name field 132 has a form name, the creator field 133 has an employee ID, and the output target person field 134 has an employee. The output possible date and time column 135 stores the output possible date and time.
The form ID in the form ID column 131 is the same as the form ID in FIG.
The form name in the form name column 132 is the same as the form name in FIG.
The employee ID in the creator column 133 is an employee ID that identifies an employee who defines the format of the form.

The employee ID in the output target person column 134 is an employee ID that identifies an employee who is permitted to output the form. That is, the employee ID is a candidate for a person who can output the form. In this embodiment, an employee who defines the format of a form designates an employee who is permitted to output the form (details will be described later). In many cases, the permitted employee is an employee of a lower rank, but may be designated for memorandum and reference.
In the output target person column 134, an affiliation such as “material procurement department” may be stored instead of the employee ID. In this case, all employees belonging to the “material procurement department” are permitted to output.
Further, the output target person column 134 may store a conditional statement including affiliation and position that conditions an employee who is permitted to output, such as “" Principal "or more of“ Material Procurement Department ””. . In short, a search condition that can identify one or a plurality of employee IDs in the assigned business data 32 (FIG. 3) only needs to be stored in the output target person column 134.
The output date / time in the output date / time column 135 is the date when the output is permitted. The output possible date and time may be any of designation of only the start date (example in FIG. 5), designation of only the end date, and a combination of the start date and end date.
There are as many records of the definition form output data 34 as the number of form IDs.

(Relationship between responsible business data and definition form output data)
With reference to FIGS. 3 and 5, the relationship between the assigned business data 32 and the definition form output data 34 will be described.
For example, the employee “P001” is in charge of “material procurement management” (record 201 in FIG. 3), and the employee “P003” is in charge of “material procurement” (record 203 in FIG. 3). The employee “P001” can cause the employee “P003” to output the form “S001 (additive management)” in which the format is defined (record 221 in FIG. 5).
In addition, the employee “P002” is in charge of “assistant manager's business assistant” (record 202 in FIG. 3), and the form “S002 (additives) whose format is defined by the employee“ P001 ”in the absence of the employee“ P001 ”. Management) ”can be output to the employee“ P003 ”(record 222 in FIG. 5).
Further, the employee “P004” and the employee “P005” have a “commercial contact” as the business in charge (records 204 and 205 in FIG. 3). The employee “P003” can cause the employees “P004” and “P005” to output the forms “S003 (additive details management)” and “S004 (additive details management)” in which the format is defined by the employee “P003” ( Records 223, 224 in FIG.

(Processing procedure)
Hereinafter, the processing procedure of this embodiment will be described. The processing procedure includes (1) form definition / output condition setting process procedure and (2) form output process procedure. In order to execute the processing procedure (2), it is premised that the processing procedure (1) is executed at least once and the form definition data 33 and the definition form output data 34 are created.

(Form definition / output condition setting process)
The form definition / output condition setting processing procedure will be described with reference to FIG. 12, with reference to FIGS. 1, 10, and 11 as appropriate.
In step S <b> 301, the management authority user terminal device 4 requests the form definition / output condition setting screen 62. Specifically, the management authority user terminal device 4 inputs an instruction for a user (mainly an employee of a higher rank) to start an application for form definition / output condition setting (not shown) via the input device. Accept to do. Then, the application transmits a request for the form definition / output condition setting screen 62 (FIG. 10A) to the Web server 3.
Hereinafter, the operation subject of the management authority user terminal device 4 is the application.

In step S302, the form definition unit 51 (FIG. 1) of the Web server 3 transmits a form definition / output condition setting screen. Specifically, the form definition unit 51 first receives a request for the form definition / output condition setting screen 62.
Second, a form definition / output condition setting screen 62 is created and transmitted to the management authority user terminal device 4.

In step S303, the management authority user terminal device 4 accepts the form definition and the output conditions. Specifically, the management authority user terminal device 4 first receives the form definition / output condition setting screen 62.
Second, the user accepts data input to the columns 261 to 265, 266a to 266d of the form definition / output condition setting screen 62 via the input device. The data that has received the input may be hereinafter referred to as “input definition data”.
Your employee ID column 261 in FIG. 10A corresponds to the creator column 133 in FIG. Similarly, the form name field 262 corresponds to the form name field 122 in FIG. 4 and the form name field 132 in FIG. 5, and the target date / time field 263 corresponds to the target date / time field 127 in FIG. Corresponds to the output target person column 134 in FIG. 5, the output possible date / time column 265 corresponds to the output possible date / time column 135 in FIG. 5, and the output item 1 column 266a to the output item 4 column 266d correspond to the output in FIG. This corresponds to the item 1 column 123 to the output item 4 column 126.
When all the “input definition data” are input, the form definition / output condition setting screen 62 is in the state shown in FIG.
Third, when the user presses the “form registration” button 269, the input definition data is transmitted to the Web server 3.

When the user accepts that the “output target data list” button 267 in FIG. 10A is pressed, the management authority user terminal device 4 acquires the manufacturing data 31 from the data storage server 2, and the management authority user terminal It is displayed on the output device of the device 4. This facilitates selection of output items and the like.
When the user accepts that the “format check” button 268 of FIG. 10A is pressed, the management authority user terminal device 4 displays the form format confirmation screen 64 (FIG. 11B) of the management authority user terminal device 4. Display on the output device. In the form format confirmation screen 64, the form format defined by the input definition data is displayed. (Since the form ID is not assigned at this stage, it is blank.) This allows the user to input data while viewing the specific completion state of the form.

  In step S304, the form definition unit 51 (FIG. 1) of the Web server 3 transfers the form definition and output conditions. Specifically, the form definition unit 51 receives the input definition data transmitted in “third” in step S303, and transfers the input definition data to the data storage server 2 as it is.

In step S305, the form output data management unit 22 (FIG. 1) of the data storage server 2 updates the form definition data 33. Specifically, the form output data management unit 22 first receives the input definition data transferred in step S304.
Second, a new form ID is assigned.
Third, a new record of the form definition data 33 (FIG. 4) is created.
Fourth, the form ID column 121, the form name column 122, the output item 1 column 123, the output item 4 column 126, and the target date / time column 127 of the newly created record are included in the form ID and the input definition data, respectively. The form name, output items 1 to 4 included in the input definition data, and the target date and time included in the input definition data are stored.

In step S306, the form output data management unit 22 (FIG. 1) of the data storage server 2 updates the definition form output data 34 (FIG. 5). Specifically, the form output data management unit 22 first creates a new record of the definition form output data 34 (FIG. 5).
Secondly, the form ID field 131, form name field 132, creator field 133, output target person field 134, and output date / time field 135 of the newly created record are included in the form ID and the input definition data, respectively. The form name, “your employee ID” included in the input definition data, the employee ID of the output target person included in the input definition data, and the output date and time included in the input definition data are stored.
Thereafter, the form definition / output condition setting process is terminated.

(Form output processing procedure)
The form output processing procedure will be described with reference to FIG.
In step S <b> 401, the general user terminal device 5 requests the form output screen 63. Specifically, the general user terminal device 5 receives an instruction for a user (mainly an employee at a lower position) to start an application for document output (not shown) and his / her employee ID via the input device. To accept input. Then, the application transmits the received employee ID and the request for the form output screen 63 (FIG. 11A) to the Web server 3.
Hereinafter, the operation subject of the general user terminal device 5 is the application.

In step S402, the form output processing unit 52 (FIG. 1) of the Web server 3 inquires about a form that can be output. Specifically, the form output processing unit 52 first receives the employee ID and the request for the form output screen 63 (FIG. 11A) transmitted in step S401.
Second, the received employee ID is transmitted to the data storage server 2.

In step S403, the form output data management unit 22 (FIG. 1) of the data storage server 2 searches for a form 61 that can be output. Specifically, the form output data management unit 22 first receives the employee ID transmitted in “second” in step S402.
Secondly, among the records of the definition form output data 34, a record in which the received employee ID is included in the employee ID of the output target person column 134 and the current date and time is included in the outputable date and time is searched, and the corresponding record is searched. A set of the form ID, form name, and employee ID in the creator column 133 is acquired. When a plurality of records are applicable, a plurality of such sets are acquired. If the corresponding record does not exist, the message “There is no form that can be output” is generated.
Third, referring to the assigned business data 32 (FIG. 3), the name corresponding to the acquired employee ID as the creator is acquired, and the employee ID included in the group is replaced with the name.
Fourth, a set of form ID, form name and name (or generated message) is transmitted to the Web server 3.

In step S404, the form output processing unit 52 (FIG. 1) of the Web server 3 transmits a form output screen 63. Specifically, the form output processing unit 52 first receives the form ID, form name, and name combination (or generated message) transmitted in “fourth” in step S403.
Second, a form output screen 63 (FIG. 11A) is created, and the screen and a set of form ID, form name and name (or generated message) are transmitted to the general user terminal device 5.

In step S405, the general user terminal device 5 accepts selection of a form to be output. Specifically, the general user terminal device 5 receives the form output screen 63 and the set of form ID, form name, and name (or generated message) transmitted in “second” in step S404.
Secondly, the received form output screen 63 and the form ID, form name, and name combination (or generated message) are displayed on the output device.
At this time, the combination of the form ID, form name, and name is displayed as a record having a form ID field 281a, a form name field 281b, and a creator field 281c, as shown in FIG. When a message is received, a record is not displayed in these fields, and “There is no form that can be output” is displayed instead of “Currently, the following forms can be output” in FIG.
Third, it is accepted that the user presses the “form output” button 283 after checking one of the check boxes in the selection field 281d.
Fourth, the form ID of the checked record is transmitted to the Web server 3.

  When the user checks that the selection field 281d in FIG. 11A is checked and then presses the “format confirmation” button 282, the general user terminal device 5 displays the form format confirmation screen 64 (FIG. 11B). Is displayed on the output device of the general user terminal device 5. In the form format confirmation screen 64, the format of the form selected by the user is displayed. As a result, the user can select a form while viewing the format of the form to be output.

In step S406, the form output processing unit 52 (FIG. 1) of the Web server 3 requests necessary data. Specifically, the form output processing unit 52 first receives the form ID transmitted in “fourth” in step S405.
Second, a “data request” is transmitted to the data storage server 2 together with the form ID.

In step S407, the business data management unit 21 (FIG. 1) of the data storage server 2 searches for necessary data. Specifically, the business data management unit 21 first receives the form ID and “data request” transmitted in “second” in step S406.
Second, the form definition data 33 (FIG. 4) is searched using the received form ID as a search key, and the form name, output item 1, output item 2, output item 3, output item 4, and target date and time of the corresponding record are searched. To get.
Thirdly, a record included in the target date and time when the date and time in the date and time column 108 is acquired is acquired from the records of the manufacturing data 31 (FIG. 2).
Fourth, among the acquired records, the other columns are deleted except for the columns having headings corresponding to the acquired output item 1, output item 2, output item 3, and output item 4.
Fifth, the remaining column headings are rearranged from the left in the order of the headings corresponding to the acquired output item 1, output item 2, output item 3, and output item 4. The record of the manufacturing data 31 at the stage when the processing is completed may be hereinafter referred to as “display scheduled record”.
Sixth, the form ID, form name, target date and time, and display schedule record are transmitted to the Web server 3.

  For example, when “S003” is received as the form ID in “first” in step S407, the display-scheduled record has the date and time included in “20100101-20100228” among the records of the manufacturing data 31 (FIG. 2). It is a record. Furthermore, in the record to be displayed, the column headings are narrowed down to “lot ID”, “product name”, “additive name” and “addition quantity”, and the column headings are arranged in this order from the left. It is a record. That is, the display schedule record is nothing but the one shown in the columns 256a to 256d of the form “S003” 61 (FIG. 7A).

In step S408, the form output processing unit 52 (FIG. 1) of the Web server 3 creates a form 61. Specifically, the form output processing unit 52 first receives the form ID, form name, target date and time, and display schedule record transmitted in “Sixth” in step S407.
Second, a form 61 is created based on the received form ID, form name, target date and time, and display schedule record. The created form 61 is, for example, FIG.
Third, the form 61 is transmitted to the general user terminal device 5.

In step S409, the general user terminal device 5 outputs the form 61. Specifically, the general user terminal device 5 receives the form 61 transmitted in “third” in step S <b> 408 and displays it via an output device or prints it on a paper medium and outputs it.
Thereafter, the form output processing procedure ends.

(Modification 1)
The configuration of the manufacturing data 31 (FIG. 2) can have various examples other than the above. For example, in association with information for specifying a product, a component of the product, a manufacturing cost per unit quantity, a selling price per unit quantity, related patent information, and the like may be stored. Furthermore, a plurality of manufacturing data 31 exists for each manufacturing base and each product category, and any manufacturing data 31 may be designated when defining the form format.
Further, the data is not limited to manufacturing-related data. For example, it may be management data that is not directly related to a business in which personnel information such as employee performance, transfer history, etc. is stored in association with information specifying the employee. In short, the manufacturing data 31 may be anything as long as the data items to be output to the form 61 can be selected and the order or position thereof can be changed.

(Modification 2)
The configuration of the form definition data 33 (FIG. 4) may have various examples other than the above. For example, in association with a form ID, a plurality of sets of output items and areas on the form in which the values of the output items are output (rectangles specified by the coordinates of the upper left point and the lower right point, etc.) May be stored. Further, a plurality of sets of output items and output forms of values of the output items (sizes of characters, colors, etc.) may be stored in association with the form ID. Then, on the form definition / output condition setting screen 62 (for example, FIG. 10A), for the output item 1 column 266a to the output item 4 column 266d, the user can output the value of the output item on the form. Information indicating the output form of the area or the value of the output item may be input together.

(Modification 3)
In step S303, when the management authority user terminal device 4 accepts the form definition and the output conditions, the business data management unit 21 (FIG. 1) of the data storage server 2 manages the business data 32 (FIG. 3) in charge. You may display on the output device of the user terminal device 4. FIG. Then, when the user selects a specific employee ID, affiliation, or the like of the assigned business data 32 with an input device such as a mouse, the management authority user terminal device 4 displays the selected value as an output target person in FIG. You may make it transcribe | transfer to the column 264.

(Modification 4)
In step S406, the form output processing unit 52 (FIG. 1) of the Web server 3 receives the form ID (column 281a in FIG. 11A) of the record checked by the user in “first” in step S403. It may be stored in association with the ID. For each employee ID and each form ID, the cumulative number of times that the form 61 to be output has been selected in the past is stored. In the next process, the general user terminal device 5 refers to the cumulative number when displaying the combination of the form ID, the form name, and the name in the “second” in step S405, and the form ID having a large cumulative number is displayed. You may make it display in order from the group containing.

(Modification 5)
In step S406, the form output processing unit 52 (FIG. 1) of the Web server 3 transmits the set of the form ID, the employee ID, and the cumulative number to the data storage server 2 at a predetermined time. Then, the form output data management unit 22 of the data storage server 2 stores, for example, “P004 (n),” in the output target person column 134 of the record of the definition form output data 34 (FIG. 5) having the transmitted form ID. P005 (m) "(n and m are cumulative numbers) are stored. With such a configuration, the actual output count of the form 61 can be grasped for each form ID and each employee ID.

  The present invention is not limited to the above-described embodiment, and can be modified without departing from the gist of the present invention.

DESCRIPTION OF SYMBOLS 1 Form creation system 2 Data storage server 3 Web server 4 Management authority user terminal device 5 General user terminal device 11, 41 Central controller (control part)
12, 42 Main storage device (storage unit)
13, 43 Auxiliary storage device (storage unit)
14, 44 Communication device 15, 45 Input device 16, 46 Output device 21 Business data management part 22 Form output data management part 31 Manufacturing data 32 Business data in charge 33 Form definition data 34 Definition form output data 51 Form definition part 52 Form Output processing section 61 Form 62 Form definition / output condition setting screen 63 Form output screen 64 Form format confirmation screen

Claims (3)

A form creation device that outputs a part of data to a form,
The form creation device
Corresponding information for storing data items of the data to be output to the form, information on the arrangement of the data items, and information for specifying a person who can output the form in association with the information for specifying the form Accessible,
Accepting input of data items of the data to be output to the form, information on the arrangement of the data items, and information specifying a person who can output the form,
The received data item of the data to be output to the form, information on the arrangement of the data item, and information for specifying a person who can output the form are associated with the information for specifying the form and the correspondence Instruct to store as a record of information,
Accepting a request to output the form together with information for identifying the candidate from a terminal device of a candidate who can output the form,
Among the records of correspondence information, identify the record that has the information that identifies the accepted candidate as information that identifies the person who can output the form,
A processing unit that outputs a display for prompting output of the form to the candidate terminal device based on information for specifying the form of the specified record;
A form creation device characterized by Information about the placement is
The order in which the data items are arranged;
The form creation device according to claim 1. The processor is
In response to the display prompting the output of the form, the number of times the user has selected information for specifying the form is stored,
When displaying the display prompting the output of the form to the candidate terminal device, displaying in the order of the selected number of times,
The form creation device according to claim 1.

Images