JP2009080536A - Bom editing device, editing program, editing system and editing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a BOM editing device, program, system, and method, for easily reproducing editing of a desired BOM, in order to solve the problem that a correlation between processing contents of a highly abstractive BOM operation and the program is not clear, and that it is difficult to know the BOM editing operation to be executed from the program, while using the program prepared using a versatile program language, when editing the BOM for preparing a production BOM from a design BOM. <P>SOLUTION: The BOM is edited using a command and a script as a unit used for editing, in the BOM editing device, program and system. The BOM editing device or the like is further provided with a functional part for reproduceably recording editing history of the BOM, a functional part for recording the editing history with a name and a comment added thereto, when recorded, and a functional part for re-executing the recorded editing history. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a technology for editing a bill of materials (hereinafter referred to as BOM).

  Conventionally, when a production BOM is created from a design BOM or an evaluation BOM is created from a production BOM, for example, the technique described in Patent Document 1 has been used. In this prior art, when a design BOM is converted to a manufacturing BOM, or when a BOM is edited or modified, the BOM is managed using a program created in advance using a general-purpose programming language attached to the database software. The database needs to be edited / modified.

  Here, the BOM is a table showing how many parts are required for a certain product.

  In the process of creating the program, the BOM operation / conversion process / procedure is broken down into a database processing procedure composed of a plurality of steps by the program creator, and the procedure is described in a general-purpose programming language. When performing maintenance, a similar or similar process is performed.

  Further, the program may be modified to create another BOM editing program, or may be used without modification.

JP 2005-346530 A

  However, since the program used in the above-described conventional technology uses a general-purpose program language, it is difficult to understand the correspondence between the processing instruction described in the source code and the BOM operation instruction having a higher abstraction level. Therefore, for example, when the program is reused, it is difficult to grasp in a short period what BOM editing operation the program realizes.

  An object of this invention is to provide the technique which can re-implement BOM edit and conversion from an implementation log | history.

  The parts table editing device, parts table editing program, and parts table editing system according to the present application are provided with a function unit that can receive and execute a script that describes commands for editing operations on the BOM in order to solve the above-described problems. The BOM can be edited by specifying the conditions for specifying the part and the conditions for specifying the editing content via this command, so the contents of the BOM operation can be grasped from the script. It becomes easy.

  Furthermore, the edit history performed on the parts table is recorded so as to be reproducible, and when the edit history is recorded, a function unit for recording the name and a free memo is attached, and the recorded edit history is reproduced, that is, re-executed. And a functional part.

  That is, specifically, it is a parts table editing device that edits a parts table, and includes a control unit that executes a plurality of editing instructions, a storage unit, and an input unit, and the control unit includes the plurality of editing commands. One input from among the editing commands, a component condition that is a condition for designating a part to be edited from the parts table, and an execution condition that is a condition for designating the editing content of the editing command are input. An edit receiving unit that receives the component, and a component that satisfies the component condition received by the component condition receiving unit is acquired from the parts table, and the acquired condition is received according to the execution condition received by the edit receiving unit. An editing unit that performs editing processing, a history storage unit that stores a history of editing performed on the parts table in the storage unit, and an input of a name and a comment to be added to the stored editing history Accepted through the department The history storage unit to be added to the editing history and stored in the storage unit, the parts table designation receiving unit that receives the specification of the parts table to be processed via the input unit, and the storage by the history storage unit The editing history stored in the unit is read and displayed together with the comment, and the editing history selected from the editing history is received via the input unit, and the editing history received by the editing history receiving unit. The editing command, the part condition, and the execution condition included in the part are identified, a part satisfying the part condition is acquired from the parts table, and the execution part is designated as the execution condition. And a history reproducing unit that performs an editing process according to the editing command with the above conditions added.

  According to the present invention, it is possible to provide a technique capable of re-implementing BOM editing / conversion from the execution history.

  First, an embodiment of the present invention will be described with reference to FIGS.

  FIG. 1 is a configuration diagram of a parts table editing system 1 showing an embodiment of the present invention. The parts table editing system 1 includes an input / output unit 11, a BOM management unit 12, and a data storage unit 13.

  The input / output unit 11 includes an input unit 111 and an output unit 112.

  The input unit 111 is a functional unit that receives an editing operation on the BOM from the user and delivers the received information to the BOM management unit 12. For example, the input unit 111 is a device such as a keyboard or a mouse for a user to give an operation instruction to the BOM.

  The output unit 112 is a functional unit having a display output function for presenting BOM data to the user. For example, the output unit 112 is a device that conveys information to the user, such as a display device or an audio device.

  The BOM management unit 12 includes an editing condition reception unit 121, an editing process execution unit 122, an editing / operation history management unit 123, an editing / operation history execution unit 124, and a control unit 125. Is done.

  The editing condition receiving unit 121 is a functional unit that receives various condition designations according to the contents of BOM editing.

  As shown in FIG. 2, the editing condition reception unit 121 includes a component attribute batch setting condition reception unit 211, a component deletion condition reception unit 212, a component addition condition reception unit 213, a component replacement condition reception unit 214, and a component attribute. A copy condition receiving unit 215 and a script receiving unit 216 are included.

  The part attribute batch setting reception unit 211 receives input from the user that parts attribute batch setting is to be performed, part condition specification input for specifying a condition to be satisfied by the BOM data editing target, and a part to be edited. An input of an execution condition, which is a condition for executing the editing process performed in step S3, is received via the input unit 111. Then, each received input value is configured in accordance with the data format received by the editing process execution unit 122 and transferred to the editing process execution unit 122. Further, when the processing of the editing process execution unit 122 ends, the part attribute batch setting reception unit 211 receives the processing result and outputs it to the user via the output unit 112.

  Similarly, the component deletion condition reception unit 212 receives an input to perform a deletion process from the user and a component condition specification input for specifying a condition to be satisfied by the deletion target of the BOM data via the input unit 111. Based on the received and accepted input values, parameters are configured in accordance with the data format accepted by the editing process execution unit 122 and passed to the editing process execution unit 122. Further, when the process of the editing process execution unit 122 ends, the part deletion condition reception unit 212 receives the processing result and outputs it to the user via the output unit 112.

  The component addition condition reception unit 213 inputs an input to perform a component addition process from a user, a component condition designation input for designating a condition to be satisfied by a target to which BOM data is added, and a component to be added. A specification input of an execution condition, which is a condition to be identified, is received via the input unit 111. Based on the received input value, parameters are configured according to the data format accepted by the editing process execution unit 122, and editing processing is performed. The data is transferred to the execution unit 122. Further, when the processing of the editing process execution unit 122 ends, the component addition condition reception unit 213 receives the processing result and outputs it to the user via the output unit 112.

  The part replacement condition receiving unit 214 inputs an instruction to perform a part replacement process from the user, a part condition specification input for specifying a condition to be satisfied by a replacement target of the BOM data, and a part to be replaced. A specification input of an execution condition, which is a condition for specifying a replacement source to be performed, is received via the input unit 111, and parameters are configured according to the data format received by the editing process execution unit 122 based on the received input value. Then, the data is transferred to the editing process execution unit 122. In addition, when the processing of the editing process execution unit 122 ends, the component replacement condition reception unit 214 receives the processing result and outputs it to the user via the output unit 112.

  The component attribute copy condition accepting unit 215 receives an input indicating that the copy process is to be performed from the user, a specification input of a component condition that specifies a condition to be satisfied by a copy destination target of the BOM data, and a target that is a source of the copy. A specification input of an execution condition, which is a condition to be identified, is received via the input unit 111. Based on the received input value, parameters are configured according to the data format accepted by the editing process execution unit 122, and editing processing is performed. The data is transferred to the execution unit 122. Further, when the processing of the editing process execution unit 122 ends, the part attribute copy condition reception unit 215 receives the processing result and outputs it to the user via the output unit 112.

  Further, the script receiving unit 216 inputs an input to the user to execute the script, a user name necessary for authentication, a password, a BOM name to be executed, and a script file name to be executed, and inputs the input unit 111. Based on the received input value, the parameters are configured in accordance with the data format accepted by the editing process execution unit 122 and transferred to the editing process execution unit 122. In addition, when the process of the editing process execution unit 122 ends, the script reception unit 216 receives the processing result and outputs it to the user via the output unit 112.

  The edit processing execution unit 122 extracts the execution target BOM data from the BOM data in the BOM data storage unit 131 by using the specification condition of the part condition in the edit condition reception unit 121 related to the BOM editing, and the extracted BOM data is the target. As a result, an editing process that matches the specified execution condition is executed. At this time, if the editing condition receiving unit 121 has received the confirmation of execution immediately before executing the editing process for each part, an execution confirmation message is displayed through the output unit 112, and the input unit 111 It is executed on condition that a confirmation instruction from the user is accepted.

  As shown in FIG. 3, the edit processing execution unit 122 includes a component attribute batch setting unit 221, a component deletion unit 222, a component addition unit 223, a component replacement unit 224, a component attribute copy unit 225, and a script execution unit. 226.

  The part attribute batch setting unit 221 starts processing by a “part attribute batch setting” command, specifies the type of editing passed from the part attribute batch setting condition reception unit 211, specifies the part condition, and sets the execution condition. Based on the parameters including the designation, a process for changing and setting the component attributes at once is performed.

  In this processing, it is specified from the designated part condition whether the part master table 1311 or the part table 1312 is to be selected, and a record that matches the part condition is searched from any part table data, and the part Extract records that meet the conditions. Then, the condition specified as the execution condition is set for the record.

  Specifically, for example, when the part type specified in the part condition is “screw”, it is determined whether or not the attribute of the part type is included in the attribute of the part master table 1311. It is determined whether or not the attribute includes a component type attribute. For example, if the part table 1312 includes an attribute of a part type as a result of the determination, the parts table 1312 is searched to extract a record whose part type is “screw”. Set the value of “[↓] [Q]” in the “Assembly operation” attribute.

  Similarly, the component deletion unit 222 is configured to start processing by a “delete component” command and include the specification of the type of editing and the specification of the component condition transferred from the component deletion condition reception unit 212. Delete parts based on parameters.

  In this processing, it is specified from the designated part condition whether the part master table 1311 or the part table 1312 is to be selected, and a record that matches the part condition is searched from any part table data, and the part Extract records that meet the conditions. Then, the record is deleted.

  Specifically, for example, when the part code specified in the part condition is “675-UT1002”, it is determined whether or not the attribute of the part master table 1311 includes an attribute called a part code. It is determined whether or not the attribute 1312 includes an attribute called a part code. And, for example, if the part master table 1311 includes an attribute called a part code as a result of the determination, the part master table 1311 described later is searched to extract a record whose part code is “675-UT1002”. Process such as deleting the record.

  Similarly, the component addition unit 223 starts processing by an “add component” command, specifies the type of editing passed from the component addition condition reception unit 213, specifies the component condition, specifies the execution condition, Add a part based on the parameters that include

  In this process, it is specified which of the parts master table 1311 or the parts table 1312 should be selected from the specified part conditions, and a record that matches the part conditions is created in any part table data. Then, information on parts satisfying the conditions specified in the execution condition is copied and set for the record.

  Specifically, for example, when the part code specified in the part condition is “675-UT1111”, it is determined whether or not the attribute of the part master table 1311 includes an attribute called a part code. It is determined whether or not the attribute 1312 includes an attribute called a part code. And, for example, if the part master table 1311 contains an attribute called a part code as a result of the determination, a part master table 1311 described later is searched to create a record whose part code is “675-UT1111”. On the other hand, processing such as searching for a part whose part code is “675-FV600”, which is the condition specified as the execution condition, and copying the value set in the record is performed.

  The component replacement unit 224 starts processing by a “component replacement” command, and includes the specification of the type of editing passed from the component replacement condition reception unit 214, the specification of the component condition, and the specification of the execution condition. Replace parts based on configured parameters.

  In this processing, it is specified from the designated part condition whether the part master table 1311 or the part table 1312 is to be selected, and a record that matches the part condition is searched from any part table data, and the part Extract records that meet the conditions. Then, the information of the part satisfying the condition specified in the execution condition is copied and set for the record.

  Specifically, for example, when the part code specified in the part condition is “675-UT1111”, it is determined whether or not the attribute of the part master table 1311 includes an attribute called a part code. It is determined whether or not an attribute called a part code is included in the PS attribute 1312. Then, for example, if the part master table 1311 includes an attribute called a part code as a result of the determination, the part master table 1311 described later is searched to extract a record whose part code is “675-UT1111”. Processing such as searching for a part whose part code is “675-FV600”, which is the condition specified as the execution condition, is copied to the extracted record.

  Similarly, the component attribute copy unit 225 starts processing by a “copy component attribute” command, specifies the type of editing passed from the component attribute copy condition reception unit 215, specifies the component condition, and the execution condition. A specific attribute of the part is copied based on the parameter including the designation.

  In this processing, it is specified from the designated part condition whether the part master table 1311 or the part table 1312 is to be selected, and a record that matches the part condition is searched from any part table data, and the part Extract records that meet the conditions. Then, specific attribute information of a component that satisfies the conditions specified in the execution condition is copied and set for the record.

  Specifically, for example, when the part type specified in the part condition is “screw”, it is determined whether or not the attribute of the part type is included in the attribute of the part master table 1311. It is determined whether or not the attribute includes a component type attribute. For example, if the result of determination includes an attribute of component type in the component table 1312, a component table 1312 to be described later is searched to extract a record whose component type is “screw”. Then, the setting value of the attribute “Assembly operation” of the part whose parent part code is “675-FV600” and whose child part code is “675-IA300”, which is the condition specified in the execution condition, is stored in the extracted record. Performs processing such as copying.

  In addition, the script execution unit 226 starts processing by the “execute script” command, inputs that the script execution passed from the script reception unit 216 is executed, the name of the script to be executed, the target BOM name, and the user ID And execute the script based on the parameters including password and password.

  In this process, the script execution unit 226 performs an authentication process using a user ID and a password. The authentication process is a process for determining whether or not a combination of a user ID and a password matches a predetermined and stored one, and determining that the combination is appropriate by matching. This authentication process is performed by a functional unit included in the server 53 such as an authentication processing unit (not shown) or an authentication processing unit of another server (not shown). When the script execution unit 226 determines that the result of the authentication process is appropriate, the script execution unit 226 identifies the script to be executed from the script name. Then, the specified script is read from the script file 1324 of the editing / operation history data storage unit 132. Then, for each line described in the script file 1324, the line is extracted as a command, and parameters are configured based on the extracted command. Then, a BOM name is designated for each row, and processing is performed from the component attribute batch setting unit 221, the component deletion unit 222, the component addition unit 223, the component replacement unit 224, and the component attribute copy unit 225 to the matching functional unit. Delegate. When all the lines of the script have been processed by repeating this, the fact that the processing has been completed is transmitted to the script receiving unit 216.

  The commands received by the script execution unit 226 correspond to the respective processing units of the editing processing execution unit 122 described above, and are five types of component attribute batch setting, component deletion, component addition, component replacement, and component attribute copy. It is. The command syntax is shown below.

  First, “SetAttr (blank) component condition, execution condition;” is the grammar of the component attribute batch setting. Here, “SetAttr” is a description indicating a command, and by this, a process of batch setting of component attributes can be specified. The following “(blank)” is a blank. The following “component condition” is a description for specifying the component condition as described above. However, when a plurality of conditions are set according to the condition relationship, the component condition can be specified by using the description of the condition relationship (condition (1), condition (2)) in the part corresponding to the component condition. . That is, “SetAttr (blank) condition relationship (condition (1), condition (2)), execution condition;” can also be established. The subsequent “execution condition” is a description for specifying the execution condition as described above. The following “;” is an end-of-line symbol indicating the end of the command.

  Next, “DelParts (blank) part condition;” is the grammar of part deletion. Here, “DelParts” is a description indicating a command, and by this, a process of part deletion can be specified. The following “(blank)” is a blank. The subsequent “component condition” is a description for specifying the component condition as described above. However, when a plurality of conditions are set according to the condition relationship, the component condition can be specified by using the description of the condition relationship (condition (1), condition (2)) in the part corresponding to the component condition. . That is, “SetAttr (blank) condition relationship (condition (1), condition (2)), execution condition;” can also be established. The following “;” is an end-of-line symbol indicating the end of the command.

  Next, as for part addition, “AddParts (blank) part condition, execution condition;” is the grammar. Here, “AddParts” is a description indicating a command, and by this, a process of adding a part can be specified. The following “(blank)” is a blank. The following “component condition” is a description for specifying the component condition as described above. However, when a plurality of conditions are set according to the condition relationship, the component condition can be specified by using the description of the condition relationship (condition (1), condition (2)) in the part corresponding to the component condition. . That is, “SetAttr (blank) condition relationship (condition (1), condition (2)), execution condition;” can also be established. The subsequent “execution condition” is a description for specifying the execution condition as described above. The following “;” is an end-of-line symbol indicating the end of the command.

  Next, as for component replacement, “RplParts (blank) component condition, execution condition;” is the grammar. Here, “RplParts” is a description indicating a command, and by this, a process of component attribute batch setting can be specified. The following “(blank)” is a blank. The following “component condition” is a description for specifying the component condition as described above. However, when a plurality of conditions are set according to the condition relationship, the component condition can be specified by using the description of the condition relationship (condition (1), condition (2)) in the part corresponding to the component condition. . That is, “SetAttr (blank) condition relationship (condition (1), condition (2)), execution condition;” can also be established. The subsequent “execution condition” is a description for specifying the execution condition as described above. The following “;” is an end-of-line symbol indicating the end of the command.

  Next, for the component attribute copy, “CpyAttr (blank) component condition, execution condition;” is the grammar. Here, “CpyAttr” is a description indicating a command, and by this, it is possible to specify a process of component attribute batch setting. The following “(blank)” is a blank. The following “component condition” is a description for specifying the component condition as described above. However, when a plurality of conditions are set according to the condition relationship, the component condition can be specified by using the description of the condition relationship (condition (1), condition (2)) in the part corresponding to the component condition. . That is, “SetAttr (blank) condition relationship (condition (1), condition (2)), execution condition;” can also be established. The subsequent “execution condition” is a description for specifying the execution condition as described above. The following “;” is an end-of-line symbol indicating the end of the command.

  The above is the syntax of the command that the script execution unit 226 accepts.

  The editing / operation history management unit 123 is a functional unit that records an editing history and an operation history, and receives an instruction when the recorded history is read and executed.

  As shown in FIG. 4, the editing / operation history management unit 123 includes an editing / operation history recording unit 231 and an editing / operation history execution receiving unit 232.

  When the editing / operation history recording unit 231 receives a history recording start instruction via the input unit 111, the editing / operation history recording unit 231 thereafter specifies the type of editing received by the editing condition reception unit 121 until a history recording end instruction is received. The specification of the component condition and the designation of the execution condition when designated are monitored. The editing / operation history recording unit 231 stores the editing operation in the command history table 1322 or the editing history table 1323 of the editing / operation history data storage unit 132 described later. At this time, the identifier of the command history table 1322 or the editing history table 1323 recorded in the history list 1321 (not shown) is used as the type of editing, that is, whether the command is executed or the operation of the BOM data. Is recorded together with information for identifying.

  When the editing / operation history recording unit 231 receives an instruction to end the history recording via the input unit 111 during the monitoring of the above-described history recording, the editing history storing unit 231 provides the user with a storage name of the editing history and an attachment via the output unit 112. And to enter a comment. Then, the editing / operation history recording unit 231 accepts an input of the command history or the saved name of the editing history and the attached comment from the user via the input unit 111. If a unique identifier is assigned and the command is executed, the command history table 1322 of the editing / operation history data storage unit 132 is displayed. If the BOM data operation is performed, the command parameter or BOM is stored in the editing history table 1323. The edited contents of data are stored.

  The editing / operation history executing unit 124 designates the same condition based on the command history table 1322 or the editing history table 1323 recorded by the editing / operation history management unit 123, and performs the same or different BOM data. It is an execution part which performs the same editing.

  As shown in FIG. 5, the edit / history execution unit 124 includes a history execution control unit 241, a component attribute batch setting unit 242, a component deletion unit 243, a component addition unit 244, a component replacement unit 245, and a component attribute. And a copy unit 246.

  The history execution control unit 241 performs processing for reading and reproducing the command history table 1322 and processing for reading and reproducing the editing history table 1323.

  In the process of reading and reproducing the command history table 1322, the history execution control unit 241 first receives a command history reproduction instruction and an identifier of the command history to be reproduced from the user via the input unit 111, and edits / operates. A command history record identified by the received identifier is identified and read from the command history table 1322 recorded by the history recording unit 231.

  For each command 432, parameters are reconfigured using the specified condition (1) 433, condition relationship 434, condition (2) 435, and execution condition 436, and the component attribute batch setting unit 242, component The processing is transferred from the deletion unit 243, the component addition unit 244, the component replacement unit 245, and the component attribute copy unit 246 to the matching functional unit. When the execution of the command history is finished, the history execution control unit 241 displays the completion of execution to the user via the output unit 112.

  In the process of reading and playing the editing history table 1323, the history execution control unit 241 first receives an editing history playback instruction and an editing history identifier to be played back from the user via the input unit 111, and edits / operates. The editing history record identified by the received identifier is read from the editing history table 1323 recorded by the history recording unit 231.

  The history execution control unit 241 reads a parent part 422, a child part 423, an editing operation 424, an editing target 425, a value 426 before change, and a value 427 after change from the read editing history record. Each parameter is extracted and edited so that these parameters conform to a predetermined data format. Then, the history execution control unit 241 delegates the processing from the component attribute batch setting unit 242, the component deletion unit 243, the component addition unit 244, the component replacement unit 245, and the component attribute copy unit 246 to the corresponding functional unit. Specifically, in order to perform an operation indicated by the editing operation stored in the editing operation 424 of the editing history table 1323 to be described later, the processing is delegated to each functional unit.

  When the history execution control unit 241 completes the reprocessing of the edit history record, the history execution control unit 241 displays the completion of the processing to the user via the output unit 112.

  The component attribute batch setting unit 242, the component deletion unit 243, the component addition unit 244, the component replacement unit 245, and the component attribute copy unit 246 are respectively set by the component attribute batch setting included in the editing process execution unit 122. The unit 221, the component deletion unit 222, the component addition unit 223, the component replacement unit 224, and the component attribute copy unit 225 bear the same functions and perform the same processing. Therefore, the component attribute batch setting unit 242, the component deletion unit 243, the component addition unit 244, the component replacement unit 245, and the component attribute copy unit 246 are respectively included in the editing process execution unit 122. The collective setting unit 221, the component deletion unit 222, the component addition unit 223, the component replacement unit 224, and the component attribute copy unit 225 may serve as the roles.

  The control unit 125 is a processing unit that controls the operations of the editing condition receiving unit 121, the editing process execution unit 122, the editing / operation history management unit 123, and the editing / operation history execution unit 124.

  The data storage unit 13 includes a parts table data storage unit 131 and an editing / operation history data storage unit 132.

  The parts table data storage unit 131 includes a storage area for storing the parts master table 1311 and a storage area for storing the parts table 1312. The parts master table 1311 and the parts table 1312 are stored by adding a BOM name that is an identifier for uniquely identifying each of them.

  The editing / operation history data storage unit 132 includes a storage area for storing the history list 1321, a storage area for storing the command history table 1322, a storage area for storing the editing history table 1323, and a storage area for storing the script file 1324. And.

  FIG. 6 shows the data structure of the parts master table 1311 and the parts table 1312 stored in the parts table data storage unit 131. The PN (Parts Number) that is the parts master table 1311 and the PS (Parts Structure) that indicates the hierarchical structure of the parts that are the parts table 1312 are collectively referred to as BOM data.

  The component master table 1311 includes a component code column 311 for storing a component code for identifying a component, a component name column 312 for storing the name of the component, and a component attribute a column 313 for storing different attribute information for each component. And a component attribute b column 314. In general, the component attributes in the component master table vary depending on the component, and therefore the attribute names in the component attribute a column 313 and the component attribute b column 314 are different depending on the component.

  The parts table 1312 also includes a parent part code column 321 that stores a parent part code that is a part code of a part, and a child part code that is a part code of a child part that is necessary to configure the part. A component code column 322, a number column 323 for storing the number indicating the number of child components, and a PS attribute c column 324 for storing different PS attribute information for each parent component are configured. In general, the PS attribute of the parts table varies depending on the part, and therefore the name of the attribute in the PS attribute c column differs depending on the variation of the PS attribute.

  The history list 1321 stored in the editing / operation history data storage unit 132 includes an ID column 411, a type column 412, and a link ID column 413. The ID column 411 is a column for storing an ID having a unique value that can identify a record on the history list 1321. The type column 412 is a history of command execution whether the history type is a BOM operation history. This is a column for storing a value for determining whether or not. For example, the value is “operation” if it is a BOM operation history, and “command” if it is a command execution history. The link ID column 413 is a column for storing a unique value for identifying details of a recorded operation or command. Specifically, this is a column for storing values for identifying data in the command history table 1322 or the edit history table 1323.

  Next, FIG. 7 shows the data structure of the command history table 1322 stored in the editing / operation history data storage unit 132. As shown in FIG. 7, the command history table 1322 includes a command ID column 431, a command column 432, a condition (1) column 433, a condition relation column 434, a condition (2) column 435, and an execution condition column 436. And a remarks column 437. The command ID column 431 stores a command ID that is an identifier for identifying each record in the command history table 1322. The command column 432 stores executed commands. The condition (1) column 433 stores the component condition 1 which is the first condition among the component conditions specified when selecting the target of the executed command. The condition (2) column 435 stores the component condition 2 which is the second condition among the component conditions specified when selecting the target of the executed command. The condition relationship column 434 stores the logical relationship between the component condition 1 and the component condition 2 specified when selecting the target of the executed command. The execution condition column 436 stores an execution condition specified when processing the executed command.

  As described above, by storing the command history information in the command history table 1322, the same operation can be easily performed again on other BOM data based on the command history.

  Next, FIG. 8 shows the data structure of the edit history table 1323 stored in the edit / operation history data storage unit 132. As shown in FIG. 8, the edit history table 1323 includes an operation ID column 421, a parent component column 422, a child component column 423, an edit operation column 424, an edit target column 425, and a value column 426 before change. The changed value column 427 and the remarks column 428 are configured. The operation ID column 421 stores an operation ID that is an identifier for identifying each record of the edit history table 1323. The parent part column 422 stores a parent part code 321 relating to a parent part constituted by the edited target part. The child component column 423 stores a component code 311 related to the edited target component. The edit operation column 424 stores an edit operation name at the time of editing. The edit target column 425 stores the part name of the part master table 1311 or the parts table 1312 to be edited. The value column 426 before change stores the value of the attribute before editing with respect to the edited object. The changed value column 427 stores attribute values after editing. The remarks column 428 stores remark information.

  Next, FIG. 9 shows the data structure of the script file 1324 stored in the editing / operation history data storage unit 132. As shown in FIG. 9, the script file 1324 describes one or more lines that combine the command description, the component condition description, and the execution condition description, and data that describes an EOF (End of File) symbol at the end. Composed of structure. The command description is a description of the command to be executed. The component condition description is a description of the component condition specified when selecting the target of the command to be executed. The execution condition description is a description of an execution condition specified when processing the command to be executed.

  Next, hardware constituting the parts table editing system 1 showing an embodiment of the method of the present invention will be described with reference to FIG.

  In the present embodiment illustrated in FIG. 10, the client 51 can be connected to the server 53 via the network 52. The server 53 is a device configured to include an input device 531, a system device 532, and an output device 533. The system device 532 has a configuration in which a central processing unit 5321, a main storage device 5322, an auxiliary storage device 5323, and a communication device 5324 are connected by a bus 5325. On the other hand, the client 51 is a computer including an input device 511, a system device 512, and an output device 513. The system device 512 has a configuration in which a central processing unit 5121, a main storage device 5122, an auxiliary storage device 5123, and a communication device 5124 are connected by a bus 5125.

  The editing condition reception unit 121, the editing process execution unit 122, the editing / operation history management unit 123, the editing / operation history execution unit 124, and the control unit 125 are implemented on the server 53. However, the present invention is not limited to this, and of course, the client 51 and the server 53 may be separately function-implemented. That is, the input / output unit 11 may be mounted on the client 51, and the BOM management unit 12 and the data storage unit 13 may be mounted on the server 53. In addition, although the BOM management unit 12 and the data storage unit 13 are mounted on the same server 53 in the present embodiment, they may be mounted on different servers. Further, the editing condition instruction unit 121, the editing process execution unit 122, the editing / operation history management unit 123, the editing / operation history execution unit 124, and the control unit 125 of the BOM management unit 12 are the same in this embodiment. However, they may be mounted on different servers.

  Further, the parts table storage unit 131 and the editing operation history data storage unit 132 of the data storage unit 13 are mounted on the same server. However, the present invention is not limited to this.

  In the present embodiment, each function of the BOM management unit 12 is realized by a program that causes the central processing unit 5321 of the server to perform processing. This program is stored in the server main storage device 5322 or the auxiliary storage device 5323, loaded on the main storage device 5322 of the server 53 for execution, and executed by the central processing unit 5321.

  Alternatively, the server 53 may send the program of the BOM management unit 12 to the client 51 and the client 51 may execute the program. That is, the server 53 transmits the program stored in the server main storage device 5322 or the auxiliary storage device 5323 to the client 51 via the communication device 5324 and the network 52, and the main storage device 5122 or the auxiliary storage device of the client 51 is transmitted. A part or all of the functional blocks may be implemented so that the program is stored in 5123 and then executed by the central processing unit 5121 of the client.

  Next, the flow of editing processing in the parts table editing system 1 according to the present embodiment will be described with reference to FIG.

  As shown in FIG. 11, first, the control unit 125 receives a command related to BOM editing, and transfers control to each function unit of the editing condition receiving unit 121 according to the received command. For example, when the received command is a component attribute batch setting command, control is transferred to the component attribute batch setting condition receiving unit 211. Then, each function unit of the editing condition receiving unit 121 that has received the control prompts the user to input each condition specification, and displays a screen for receiving the input. For example, the part attribute batch setting condition accepting unit 211 displays a part condition and execution condition input screen 60 as shown in FIG. 12 to the user via the output part 112 (step 71). Of course, if the received command corresponds to another functional unit of the editing condition receiving unit 121, a screen corresponding to the functional unit is displayed. Examples thereof will be described later.

  Here, the screen 60 of FIG. 12 will be described. A screen 60 illustrated in FIG. 12 is an input screen for performing component attribute batch setting. The screen 60 includes an input area 61 for storage conditions, an input area 62 for parts conditions, an input area 63 for execution conditions, an execution button 64 that is a button for inputting a command to execute a command under the input conditions, and this screen. Cancel button 65 for inputting an instruction to cancel, save button 66 for inputting a command for saving conditions set on screen 60, and setting of attribute values for each part And a check box 67 for designating a confirmation mode to be processed while confirming.

  First, the storage condition input area 61 will be described. In the storage condition input area 61, a combo box for selectively inputting a storage condition name is displayed. When the selection of the storage name is received from the user via the combo box, the control unit 125 extracts the storage condition that matches the specified storage name from the data storage unit 13 and stores the part condition and the execution condition stored in advance. Is read. The read conditions are displayed in the parts condition input area 62 and the execution condition input area 63. Accordingly, the user can reuse by selecting a previously saved condition, and the reuse becomes easy. The pre-saved conditions are part conditions and execution conditions that are pre-named and saved in the data storage unit 13 by accepting an instruction to the save button 66.

  Next, the component condition input area 62 will be described. The part condition input area 62 includes input areas for two conditions of a first condition and a second condition. There may be three or more input areas. Further, the logical relationship between the first condition and the second condition is selected and input to the relationship input 616 by the user. The relation input 616 is displayed by a combo box or the like that can be selectively input, and the logic of any one of “first condition only”, “and (And)”, and “or (Or)” is displayed. A relationship can be specified. “Only the first condition” means that only parts satisfying the first condition are to be processed, and the second condition is not applied to selection of the process target. This means that a part that also satisfies the second condition is to be processed. “Or” means that a part that satisfies only the first condition, a part that satisfies only the second condition, or a part that satisfies both the first condition and the second condition is a processing target.

  The first condition input area of the part condition input area 62 is an area for inputting a condition for specifying a component to be processed. The part condition input area 62 includes a search target designation area 611, a condition selection designation area 612, an attribute name designation area 613, a value designation area 614 to be retrieved, and a value condition designation area 615 to be retrieved. The search target designation area 611 is an area that accepts an input for designating whether to search for and extract a target part with a part code, or to search for and extract a target part with a part attribute. The condition selection area 612 is an area that receives an input for specifying a condition for narrowing down a target to be searched and extracted. The condition selection area 612 is displayed so as not to accept an input when “part code” is designated in the search target designation area 611. The attribute name designation area 613 is an area for designating an attribute name for narrowing down a target to be searched and extracted. The attribute name designation area 613 is displayed so as not to accept an input when “part code” is designated in the search target designation area 611. The value specifying area 614 to be searched is an area for specifying an attribute value to be searched with a character string. The search value condition specifying area 615 is an area for accepting input of a detailed search condition of a search value specified in the search value specifying area 614. The value condition specification area 615 to search includes (search value) “includes”, “does not include”, “matches with”, “does not match”, “greater than”, and “more than”. And “less than”, “below”, “starts with”, “does not start with”, “ends with”, and “does not end with”.

  “Including” refers to a condition for searching that all parts having an attribute having a value to be searched for as a part of the value are applicable. “Does not include” means a condition for searching for all parts having an attribute that does not have a value to be searched as part of the value.

  “Matches” means a condition for searching for a component having a value to be searched for in its attribute value. In contrast, “does not match” refers to a condition for searching for a component that does not have a value to be searched for in its attribute value.

  “Including” refers to a condition for searching that all parts having an attribute having a value to be searched for as a part of the value are applicable. “Does not include” means a condition for searching that all parts that are only attribute values that do not have the value to be searched for are applicable.

  “Greater than” refers to a condition for searching for a component having a value larger than the value to be searched for in its attribute value. “Following” refers to a condition for searching for a component having a value equal to or less than the value to be searched for in its attribute value.

  “Begins with” refers to a condition for searching for a component that includes a value to be searched for in the attribute value and the attribute value matches the value to be searched forward. “Does not begin with” refers to a condition for searching for a component that includes a value to be searched for in the attribute value and the attribute value does not coincide with the value to be searched forward.

  “Ends with” means a condition for searching for a component that includes the value to be searched for in the attribute value and the attribute value is backwardly matched with the value to be searched. “Does not end with” refers to a condition for searching for a component that includes the value to be searched for in the attribute value and whose attribute value does not coincide with the value to be searched for.

  Similar to the first condition input area, the second condition input area is a search target designation area 617, a condition selection designation area 618, an attribute name designation area 619, a value designation area 620 to be retrieved, and a value condition designation to be retrieved. A region 621. The search condition designation area 611, the condition selection designation area 612, the attribute name designation area 613, the value designation area 614 to be retrieved, and the value condition designation area 615 to be retrieved are the same as the first condition input area, respectively. is there.

  Next, the execution condition input area 63 will be described. The content specified in the execution condition input area 63 is to specify detailed conditions of processing to be performed on the part selected in the part condition input area 62. For example, when “batch setting of attributes” is performed, an attribute to be set and a setting value are designated.

  The execution condition input area 63 includes a condition selection / designation area 622, an attribute name designation area 623, and a set value designation area 624. The condition selection / designation area 622 is an area that accepts designation of conditions for narrowing down target component attributes based on conditions designated by the user. The attribute name designation area 623 is an area for accepting designation of the name of a component attribute for which a value is set. The setting value designation area 624 is an area for accepting designation of a value to be set.

  The execution button 64 is a button for receiving an instruction to start processing using the conditions specified by the check box 67 for receiving the specification of the component condition 62, the execution condition 63, and the confirmation mode. The part attribute batch setting condition accepting unit 211 that accepts the instruction accepts and edits the conditions specified by the part condition input area 62, the execution condition input area 63, and the check box 67 for accepting the specification of the confirmation mode. Control is transferred to the component attribute batch setting unit 221 of the process execution unit 122.

  The cancel button 65 is a button that accepts an input of an instruction to end the processing of the component attribute batch setting condition accepting unit 211. The component attribute batch setting condition reception unit 211 that has received the instruction interrupts the process and returns control to the control unit 125.

  The save button 66 is a button for receiving an instruction to store the conditions specified by the check box 67 for receiving the specification of the component condition 62, the execution condition 63, and the confirmation mode in an area (not shown) of the data storage unit 13. . The component attribute batch setting condition reception unit 211 that has received the instruction causes the data storage unit 13 to store the condition specified by the check box 67 for receiving the specification of the component condition 62, the execution condition 63, and the confirmation mode.

  The check box 67 is an area for accepting designation of applying a confirmation mode in which processing is performed while confirming the attribute value setting for each part with the user, and accepts designation of application depending on whether the check is ON or OFF.

  Return to the description of the process. When the screen 60 is displayed in step 71, the editing condition receiving unit 121 displays a storage condition input area 61, a part condition input area 62, an execution condition input area 63, an execution button 64, and a cancel button. 65, a save button 66, and a check box 67 are accepted. Among them, when an operation on the execution button 64 is accepted, the designated content of the storage condition input area 61 and the designated content of the part condition input area 62 are accepted (step 72), and the execution condition input area 63 and the check box 67 are displayed. The designated content is accepted (step 73). Then, for example, the component attribute batch setting unit 221 is requested to perform the processing for each component using the received condition as a parameter (step 74).

  When the part attribute batch setting unit 221 acquires the specification contents of the part condition input area 62 from the parameters, the part attribute batch setting unit 221 searches the part master table 1311 and the parts table 1312 and matches the part master table 1311 and the parts that match the part condition specification contents. The record of Table 1312 is loaded into the main storage device 5322.

  The part attribute batch setting unit 221 performs the following steps 75 to 79 for each of the loaded parts master table 1311 and parts table 1312 records.

  The part attribute batch setting unit 221 determines whether or not the check box 67 is set to ON (step 75).

  When the determination result in step 75 is NO, that is, when the check box 67 is set to OFF, the part attribute list setting unit 221 executes the execution condition for the loaded parts master table 1311 and parts table 1312 records. The processing is performed based on the designated content, and the execution content is recorded in the edit history table 1323 (step 76).

  Specifically, for example, the component attribute list setting unit 221 selects a table having the attribute specified in the condition selection specification area 622 for the component master table 1311 and the component table 1312, and selects the attribute of the selected table. The setting value specified in the setting value specifying area 624 is set for the attribute that matches the attribute name specified in the name specifying area 623.

  After executing step 76, the component attribute list setting unit 221 determines whether or not the processing has been performed for all the loaded component master tables 1311 and 1312, and YES, that is, all the loaded component master tables. If the processing is performed on the component table 1311 and the parts table 1312, the processing is terminated and the control is returned to each functional unit of the editing condition receiving unit 121, and each functional unit of the editing condition receiving unit 121 interrupts the processing. Then, control is returned to the control unit 125 (step 77).

  The part attribute list setting unit 221 executes the process from step 75 again if the determination in step 77 is NO, that is, if all the loaded parts master table 1311 and parts table 1312 have not been executed. To do.

  If the determination result in step 75 is YES, that is, the check box 67 is set to ON, the component attribute list setting unit 221 selects the component code of the record to be executed from the loaded component master table 1311 and component table 1312. A message including 312 or a combination of the parent part code 321 and the child part code 322 to be executed is displayed on the screen to make the user confirm the execution target (step 78).

  Here, a message screen to be displayed in step 78 is shown in FIG.

  FIG. 13 is a diagram showing a target component confirmation screen 1300 when execution confirmation is performed.

  The target component confirmation screen 1300 includes a message display column 1301, an execution target confirmation reception column 1302, an all check designation column 1303, an OK button 1304, a cancel button 1305, a check input column 1306, a component display column 1307, It is comprised.

  The component attribute list setting unit 221 displays a message including the processing content in the message display field 1301. For example, a message such as “value [↓] [Q] is set in the assembling operation item of the following configuration information” is used as the message.

  In addition, the part attribute list setting unit 221 displays parts satisfying the part condition in the execution target confirmation receiving field 1302. Although not shown, when there are parts that cannot be displayed at this time, a scroll button or the like may be displayed.

  In the all check designation field 1303, when ON is designated, all parts displayed in the execution target confirmation field 1302 are set to ON. If OFF is specified, all component checks are set to OFF.

  An OK button 1304 is a button for starting a process of transmitting a part whose check is designated as ON among the parts displayed in the execution target confirmation receiving field 1302.

  A cancel button 1305 is a button for ending the display of the target component confirmation screen 1300 and returning the display to the screen 60.

  The check input field 1306 is an input field that is displayed according to one component displayed in the component display field 1307, and is set as an execution target when set to ON, and from the execution target when set as OFF. Although excluded, this is a column for accepting ON and OFF.

  The component display column 1307 is a column for displaying components that satisfy the component condition.

  When the specified content is transmitted by an operation on the OK button 1304 on the target component confirmation screen 1300 displayed in step 78, the component attribute list setting unit 221 receives a user response via the input unit 111, and the content is It is determined whether or not the execution is permitted (step 79). For example, for each component shown in the component display field 1307, if the corresponding check input field 1306 is ON, it is determined that the execution is permitted.

  If the result of determination in step 79 is YES, that is, if the received response permits execution, the component attribute list setting unit 221 executes step 76.

  If the result of determination in step 79 is NO, that is, if the accepted response does not permit execution, the component attribute list setting unit 221 executes step 77.

  The above is the process flow of the component attribute batch setting process.

  Hereinafter, processing when the command received in step 71 is a component deletion command will be described with reference to FIGS. 14 and 15. If the received command is a component deletion command, the control unit 125 passes control to the component deletion condition reception unit 212. Then, the component deletion condition reception unit 212 prompts the user to input a condition specification and displays a screen for receiving the input. For example, the component deletion condition reception unit 212 displays a component condition input screen 1400 as shown in FIG. 15 to the user via the output unit 112 (step 151).

  Here, the screen 1400 of FIG. 15 will be described. A screen 1400 shown in FIG. 15 is an input screen for performing component deletion. The screen 1400 cancels and cancels the input of this screen, the storage condition input area 1401, the part condition input area 1402, the execution button 1403 that is a button for inputting a command to execute a command under the input conditions. A cancel button 1404 that is a button for inputting a command, a save button 1405 that is a button for inputting a command for saving conditions set on the screen 1400, and processing while confirming that attribute value setting is executed for each component And a check box 1406 for designating a confirmation mode.

  First, the storage condition input area 1401 will be described. A storage condition input area 1401 displays a combo box that selectively receives an input of a storage condition name. When the selection of the storage name is received from the user via the combo box, the control unit 125 extracts the storage condition that matches the specified storage name from the data storage unit 13 and reads the pre-stored part condition. Then, each read condition is displayed in the part condition input area 1402. Accordingly, the user can reuse by selecting a previously saved condition, and the reuse becomes easy. The pre-saved conditions are part conditions and execution conditions that are pre-named and saved in the data storage unit 13 by accepting an instruction to the save button 1405.

  Next, the component condition input area 1402 will be described. The component condition input area 1402 includes two condition input areas, a first condition and a second condition. There may be three or more input areas. The logical relationship between the first condition and the second condition is selected and input by the user to the relationship input 1416. The relation input 1416 is displayed by a combo box or the like that can be selectively input. The relation input 1416 is a logic of any one of “first condition only”, “and (And)”, and “or (Or)”. A relationship can be specified. “Only the first condition” means that only parts satisfying the first condition are to be processed, and the second condition is not applied to selection of the process target. This means that a part that also satisfies the second condition is to be processed. “Or” means that a part that satisfies only the first condition, a part that satisfies only the second condition, or a part that satisfies both the first condition and the second condition is a processing target.

  The first condition input area of the part condition input area 1402 is an area for inputting a condition for specifying a component to be processed. The part condition input area 1402 includes a search target designation area 1411, a condition selection designation area 1412, an attribute name designation area 1413, a value designation area 1414 to be retrieved, and a value condition designation area 1415 to be retrieved. The search target designation area 1411 is an area that accepts an input that designates either searching for and extracting a target part with a part code or searching for and extracting a target part with a part attribute. The condition selection area 1412 is an area that receives an input for specifying a condition for narrowing down a target to be searched and extracted. The condition selection area 1412 is displayed so as not to accept an input when “part code” is designated in the search target designation area 1411. The attribute name designation area 1413 is an area for designating an attribute name for narrowing down a target to be searched and extracted. This attribute name designation area 1413 is displayed so as not to accept an input when “part code” is designated in the search target designation area 1411. The value specification area 1414 to be searched is an area for specifying a search attribute value by a character string. Further, the search value condition specification area 1415 is an area for accepting input of a detailed search condition of the search value specified in the search value specification area 1414. The value condition specifying area 1415 to search includes (search value) “includes”, “does not include”, “matches with”, “does not match”, “greater than”, and “more than”. And “less than”, “below”, “starts with”, “does not start with”, “ends with”, and “does not end with”.

  Note that these conditions are the same as those in the value condition designation area 615 to be searched for on the screen 60 displayed in the component attribute batch setting process described above, and thus the description thereof is omitted here.

  Similar to the first condition input area, the second condition input area includes a search target designation area 1417, a condition selection designation area 1418, an attribute name designation area 1419, a value designation area 1420 to be retrieved, and a value condition designation to be retrieved. A region 1421. The same as the search target specifying area 1411, the condition selection specifying area 1412, the attribute name specifying area 1413, the value specifying area 1414 to be searched, and the value condition specifying area 1415 to be searched, respectively, in the first condition input area. is there.

  The execution button 1403 is a button for accepting an instruction to start processing using the conditions designated by the check box 1406 for accepting designation of the component condition 1402 and the confirmation mode. The component deletion unit 212 that has received the instruction receives the conditions specified by the input area 1402 of the component conditions and the check box 1606 for receiving the specification of the confirmation mode, and controls the component deletion condition unit 222 of the editing process execution unit 122 to control the conditions. Hand over.

  A cancel button 1404 is a button for accepting an input of an instruction to end the process of the component deletion condition accepting unit 212. The component deletion condition receiving unit 212 that has received the instruction interrupts the process and returns control to the control unit 125.

  The save button 1405 is a button for accepting an instruction to store the condition designated by the check box 1406 for accepting the specification of the component condition 1402 and the confirmation mode in an area (not shown) of the data storage unit 13. The component deletion condition reception unit 212 that has received the instruction causes the data storage unit 13 to store the condition specified by the check box 1406 for receiving the specification of the component condition 1402 and the confirmation mode.

  A check box 1406 is an area for accepting designation of applying a confirmation mode in which processing is performed while confirming the attribute value setting for each component with the user, and accepts designation of application depending on whether the check is ON or OFF.

  Return to the description of the process. When the screen 1400 is displayed in step 151, the part deletion condition reception unit 212 displays a storage condition input area 1401, a part condition input area 1402, an execution button 1403, a cancel button 1404, and a save button 1405. , An operation for the check box 1406 is accepted. Among them, when an operation on the execution button 1403 is accepted, the designated content of the storage condition input area 1401 and the designated content of the part condition input area 1402 are accepted (step 152), and the designated content of the check box 1406 is accepted (step 153). The Then, for example, the component deletion unit 222 is requested to perform the process so that the process is performed for each component using the received condition as a parameter (step 154).

  When the part deletion unit 222 acquires the specification content of the part condition input area 1402 from the parameters, the part deletion unit 222 searches the part master table 1311 and the part table 1312 and matches the part condition specification content with the part master table 1311 and the part table 1312. Are loaded into the main memory 5322.

  The parts deletion unit 222 performs the following processes of steps 155 to 159 for each of the loaded parts master table 1311 and parts table 1312 records.

  The component attribute batch setting unit 221 determines whether or not the check box 1406 is set to ON (step 155).

  If the determination result in step 155 is NO, that is, if the check box 1406 is set to OFF, the component deletion unit 222 specifies the execution condition specification contents for the loaded component master table 1311 and component table 1312 records. Is deleted, and the execution contents are recorded in the edit history table 1323 (step 156).

  Specifically, for example, the component deletion unit 222 deletes the record from the loaded component master table 1311 and the component table 1312.

  After executing step 156, the component deletion unit 222 determines whether or not the processing has been performed for all the loaded component master tables 1311 and the component table 1312. YES, that is, all the loaded component master tables 1311 and If it has been performed on the parts table 1312, the process is terminated and control is returned to the part deletion condition reception unit 212 of the editing condition reception unit 121. The part deletion condition reception unit 212 interrupts the process, Control is returned to the control unit 125 (step 157).

  If the determination in step 157 is NO, that is, if the execution has not been completed for all the loaded component master table 1311 and component table 1312, the component deletion unit 222 executes the processing from step 155 again.

  When the determination result in step 155 is YES, that is, when the check box 1406 is set to ON, the component deletion unit 222 includes the component code 312 of the execution target record in the loaded component master table 1311 and the component table 1312. Alternatively, a message including a set of the parent part code 321 and the child part code 322 to be executed is displayed on the screen to make the user confirm the target to be executed (step 158).

  Here, the message screen displayed in step 158 is the same as the target component confirmation screen 1300 shown in FIG.

  When the specified content is transmitted by an operation on the OK button 1304 of the target component confirmation screen 1300 displayed in step 158, the component deletion unit 222 receives a response from the user via the input unit 111, and the content is executed. It is determined whether or not it is permitted (step 159). For example, for each component shown in the component display field 1307, if the corresponding check input field 1306 is ON, it is determined that the execution is permitted.

  If the result of determination in step 159 is YES, that is, if the accepted response permits execution, the component deletion unit 222 executes step 156.

  If the result of determination in step 159 is NO, that is, if the accepted response does not permit execution, the component deletion unit 222 executes step 157.

  The processing flow in the case of component deletion processing has been described above.

  Hereinafter, processing when the command received in step 71 is a component addition command will be described with reference to FIGS. 16 and 17. If the received command is a component addition command, the control unit 125 passes control to the component addition condition reception unit 213. Then, the component addition condition reception unit 213 prompts the user to input a condition specification and displays a screen for receiving the input. For example, the component addition condition receiving unit 213 displays a component condition and execution condition input screen 1600 as shown in FIG. 17 to the user via the output unit 112 (step 171).

  Here, the screen 1600 in FIG. 17 will be described. A screen 1600 shown in FIG. 17 is an input screen for adding a component. The screen 1600 includes a storage condition input area 1601, a part condition input area 1602, an execution condition input area 1603, an execution button 1604 that is a button for inputting a command to execute a command under the input conditions, and this screen. Cancel button 1605 that is a button for inputting an instruction to cancel, a save button 1606 that is a button for inputting a command for saving the conditions set on the screen 1600, and setting attribute values for each part And a check box 1607 for designating a confirmation mode to be processed while confirming.

  First, the storage condition input area 1601 will be described. A storage condition input area 1601 displays a combo box that selectively receives an input of a storage condition name. When the selection of the storage name is received from the user via the combo box, the control unit 125 extracts the storage condition that matches the specified storage name from the data storage unit 13 and stores the part condition and the execution condition stored in advance. Is read. The read conditions are displayed in the parts condition input area 1602 and the execution condition input area 1603. Accordingly, the user can reuse by selecting a previously saved condition, and the reuse becomes easy. The pre-saved conditions are part conditions and execution conditions that are pre-named and saved in the data storage unit 13 by accepting an instruction to the save button 1606.

  Next, the component condition input area 1602 will be described. The part condition input area 1602 includes two condition input areas, a first condition and a second condition. There may be three or more input areas. Further, the logical relationship between the first condition and the second condition is selected and input to the relationship input 1616 by the user. The relation input 1616 is displayed by a combo box or the like that can be selectively input, and the logic of any one of “first condition only”, “and (And)”, and “or (Or)” is displayed. A relationship can be specified. “Only the first condition” means that only parts satisfying the first condition are to be processed, and the second condition is not applied to selection of the process target. This means that a part that also satisfies the second condition is to be processed. “Or” means that a part that satisfies only the first condition, a part that satisfies only the second condition, or a part that satisfies both the first condition and the second condition is a processing target.

  The first condition input area of the part condition input area 1602 is an area for inputting a condition for specifying a component to be processed. The part condition input area 1602 includes a search target designation area 1611, a condition selection designation area 1612, an attribute name designation area 1613, a value designation area 1614 to be retrieved, and a value condition designation area 1615 to be retrieved. The search target designation area 1611 is an area that accepts an input for designating whether to search for and extract a target part with a part code, or to search for and extract a target part with a part attribute. The condition selection area 1612 is an area for receiving an input for specifying a condition for narrowing down a target to be searched and extracted. The condition selection area 1612 is displayed so as not to accept an input when “part code” is designated in the search target designation area 1611. The attribute name designation area 1613 is an area for designating an attribute name for narrowing down a target to be searched and extracted. This attribute name designation area 1613 is displayed so as not to accept input when “part code” is designated in the search target designation area 1611. The search value designation area 1614 is an area for designating a search attribute value by a character string. Further, the search value condition specifying area 1615 is an area for accepting input of a detailed search condition of the search value specified in the search value specifying area 1614. The value condition specifying area 1615 to search includes (search value) “includes”, “does not include”, “matches with”, “does not match”, “greater than”, and “greater than”. And “less than”, “below”, “starts with”, “does not start with”, “ends with”, and “does not end with”.

  Note that these conditions are the same as those in the value condition designation area 615 to be searched for on the screen 60 displayed in the component attribute batch setting process described above, and thus the description thereof is omitted here.

  Similar to the first condition input area, the second condition input area includes a search target designation area 1617, a condition selection designation area 1618, an attribute name designation area 1619, a value designation area 1620 to be retrieved, and a value condition designation to be retrieved. Region 1621. The search condition designation area 1611, the condition selection designation area 1612, the attribute name designation area 1613, the value designation area 1614 to be retrieved, and the value condition designation area 1615 to be retrieved are the same as the first condition input area, respectively. is there.

  Next, the execution condition input area 1603 will be described. The contents specified in the execution condition input area 1603 specify detailed conditions for processing to be performed on the part selected in the part condition input area 1602. For example, when “add attribute” is performed, a condition for specifying a component as a base for adding is specified.

  The execution condition input area 1603 includes a copy source BOM 1622 and a component designation 1623. The copy source BOM 1622 is an area that accepts specification of conditions for narrowing down the target copy source BOM based on conditions specified by the user. The component designation 1623 is an area for accepting designation of a component code of a component to be copied.

  The execution button 1604 is a button for accepting an instruction to start processing using the conditions specified in the check box 1607 for accepting designation of the component condition 1602, the execution condition 1603, and the confirmation mode. The component addition condition reception unit 213 that has received the instruction receives the conditions specified in the component condition input area 1602, the execution condition input area 1603, and the check box 1607 for receiving the confirmation mode specification, and executes the editing process. Control is transferred to the component adding unit 223 of the unit 122.

  A cancel button 1605 is a button that accepts an input of an instruction to end the processing of the component addition condition accepting unit 213. The component addition condition receiving unit 213 that has received the instruction interrupts the process and returns control to the control unit 125.

  A save button 1606 is a button for accepting an instruction to store the conditions specified in the check box 1607 for accepting designation of the component condition 1602, the execution condition 1603, and the confirmation mode in an area (not shown) of the data storage unit 13. . The component addition condition receiving unit 213 that has received the instruction causes the data storage unit 13 to store the conditions specified by the check box 1607 for receiving the specification of the component condition 1602, the execution condition 1603, and the confirmation mode.

  A check box 1607 is an area for accepting designation of applying a confirmation mode in which processing is performed while confirming the attribute value setting for each component with the user, and accepts designation of application depending on whether the check is ON or OFF.

  Return to the description of the process. When the screen 1600 is displayed in step 171, the component addition condition receiving unit 213 of the editing condition receiving unit 121 includes a storage condition input region 1601, a component condition input region 1602, an execution condition input region 1603, Operations for the execute button 1604, cancel button 1605, save button 1606, and check box 1607 are accepted. Among them, when an operation for the execution button 1604 is accepted, the designated content of the storage condition input area 1601 and the designated content of the part condition input area 1602 are accepted (step 172), and the execution condition input area 1603 and the check box 1607 The specified content is accepted (step 173). Then, for example, the component adding unit 223 is requested to perform the processing so that the processing is performed for each component using the received condition as a parameter (step 174).

  When the component addition unit 223 acquires the specification content of the component condition input area 1602 from the parameters, the component addition unit 223 searches the component master table 1311 and the component table 1312 and matches the specification content of the component condition with the component master table 1311 and the component table 1312. Are loaded into the main memory 5322. If there is no matching record, create and load an empty record.

  The parts adding unit 223 performs the following processes of steps 175 to 179 for each of the records of the loaded parts master table 1311 and parts table 1312.

  The component adding unit 223 determines whether or not the check box 1607 is set to ON (step 175).

  When the determination result of step 175 is NO, that is, when the check box 1607 is set to OFF, the component adding unit 223 specifies the execution condition for the loaded component master table 1311 and component table 1312 records. Is executed, and the execution content is recorded in the edit history table 1323 (step 176).

  Specifically, for example, the component adding unit 223 copies all the values included in the record having the component code specified by the component specification 1623 included in the BOM specified by the copy source BOM 1622 and loads the loaded component master table. The copied value is written in the records 1311 and the parts table 1312.

  After executing step 176, the component adding unit 223 determines whether or not the processing has been performed for all the loaded component master tables 1311 and the component table 1312. YES, that is, all the loaded component master tables 1311 and If it has been performed on the parts table 1312, the process is terminated and control is returned to the part addition condition reception part 213 of the editing condition reception part 121, and the part addition condition reception part 213 interrupts the process, Control is returned to the control unit 125 (step 177).

  If the determination in step 177 is NO, that is, if the execution has not been completed for all the loaded component master table 1311 and component table 1312, the component adding unit 223 executes the processing from step 175 again.

  When the determination result in step 175 is YES, that is, when the check box 1607 is set to ON, the component adding unit 223 includes the component code 312 of the record to be executed among the loaded component master table 1311 and the component table 1312. Alternatively, a message including a set of the parent part code 321 and the child part code 322 to be executed is displayed on the screen to make the user confirm the target to be executed (step 178).

  Here, the message screen displayed in step 178 is the same as the target component confirmation screen 1300 shown in FIG.

  When the specified content is transmitted by an operation on the OK button 1304 on the target component confirmation screen 1300 displayed in step 178, the component adding unit 223 receives a response from the user via the input unit 111, and the content is executed. It is determined whether or not it is permitted (step 179). For example, for each component shown in the component display field 1307, if the corresponding check input field 1306 is ON, it is determined that the execution is permitted.

  If the result of determination in step 179 is YES, that is, if the accepted response permits execution, the component adding unit 223 executes step 176.

  If the result of determination in step 179 is NO, that is, if the accepted response does not permit execution, the component adding unit 223 executes step 177.

  The processing flow in the case of the component addition processing has been described above.

  Hereinafter, processing when the command received in step 71 is a component replacement command will be described with reference to FIGS. If the received command is a component replacement command, the control unit 125 passes control to the component replacement condition receiving unit 214. Then, the component replacement condition receiving unit 214 prompts the user to input a condition specification and displays a screen for receiving the input. For example, the component replacement condition reception unit 214 displays a component condition and execution condition input screen 1800 as shown in FIG. 19 to the user via the output unit 112 (step 191).

  Here, the screen 1800 in FIG. 19 will be described. A screen 1800 shown in FIG. 19 is an input screen for adding a component. The screen 1800 includes a storage condition input area 1801, a part condition input area 1802, an execution condition input area 1803, an execution button 1804 that is a button for inputting a command to execute a command under the input conditions, and this screen. Cancel button 1805 which is a button for inputting an instruction to cancel, a save button 1806 which is a button for inputting a command for saving the conditions set on the screen 1800, and setting attribute values for each part And a check box 1807 for designating a confirmation mode to be processed while confirming.

  First, the storage condition input area 1801 will be described. In a storage condition input area 1801, a combo box for selectively receiving a storage condition name is displayed. When the selection of the storage name is received from the user via the combo box, the control unit 125 extracts the storage condition that matches the specified storage name from the data storage unit 13 and stores the part condition and the execution condition stored in advance. Is read. The read conditions are displayed in the parts condition input area 1802 and the execution condition input area 1803. Accordingly, the user can reuse by selecting a previously saved condition, and the reuse becomes easy. The pre-saved conditions are part conditions and execution conditions that are pre-named and saved in the data storage unit 13 by accepting an instruction to the save button 1806.

  Next, the component condition input area 1802 will be described. The part condition input area 1802 includes two condition input areas, a first condition and a second condition. There may be three or more input areas. The logical relationship between the first condition and the second condition is selected and input by the user to the relationship input 1816. The relation input 1816 is displayed by a combo box or the like that can be selectively input. The relation input 1816 is a logic of any one of “first condition only”, “and (And)”, and “or (Or)”. A relationship can be specified. “Only the first condition” means that only parts satisfying the first condition are to be processed, and the second condition is not applied to selection of the process target. This means that a part that also satisfies the second condition is to be processed. “Or” means that a part that satisfies only the first condition, a part that satisfies only the second condition, or a part that satisfies both the first condition and the second condition is a processing target.

  The first condition input area of the part condition input area 1802 is an area for inputting a condition for specifying a component to be processed. The part condition input area 1802 includes a search target designation area 1811, a condition selection designation area 1812, an attribute name designation area 1813, a value designation area 1814 to be retrieved, and a value condition designation area 1815 to be retrieved. The search target designation area 1811 is an area that accepts an input for designating whether to search for and extract a target part with a part code, or to search for and extract a target part with a part attribute. The condition selection area 1812 is an area for receiving an input for specifying a condition for narrowing down a target to be searched and extracted. The condition selection area 1812 is displayed so as not to accept an input when “part code” is designated in the search target designation area 1811. The attribute name designation area 1813 is an area for designating an attribute name for narrowing down a target to be searched and extracted. The attribute name designation area 1813 is displayed so as not to accept an input when “part code” is designated in the search target designation area 1811. A value specification area 1814 to be searched is an area for specifying a search attribute value by a character string. Further, the search value condition specifying area 1815 is an area for receiving an input of a detailed search condition of the search value specified in the search value specifying area 1814. The value condition specifying area 1815 to be searched includes (search value) “includes”, “does not include”, “matches with”, “does not match”, “greater than”, and “more than”. And “less than”, “below”, “starts with”, “does not start with”, “ends with”, and “does not end with”.

  Note that these conditions are the same as those in the value condition designation area 615 to be searched for on the screen 60 displayed in the component attribute batch setting process described above, and thus the description thereof is omitted here.

  Similar to the first condition input area, the second condition input area includes a search target designation area 1817, a condition selection designation area 1818, an attribute name designation area 1819, a value designation area 1820 to be retrieved, and a value condition designation to be retrieved. A region 1821. The search condition designation area 1811, the condition selection designation area 1812, the attribute name designation area 1813, the value designation area 1814 to be retrieved, and the value condition designation area 1815 to be retrieved are the same as the first condition input area, respectively. is there.

  Next, the execution condition input area 1803 will be described. The content specified in the execution condition input area 1803 specifies detailed conditions for processing to be performed on the part selected in the part condition input area 1802. For example, when “attribute replacement” is performed, a condition for specifying a replacement source attribute is designated.

  The execution condition input area 1803 includes a copy source BOM 1822 and a component designation 1823. The copy source BOM 1822 is an area that accepts specification of conditions for narrowing down the target copy source BOM based on conditions specified by the user. The component designation 1823 is an area for accepting designation of a component code of a component to be copied.

  The execution button 1804 is a button for accepting an instruction to start processing using the conditions specified in the check box 1807 for accepting designation of the component condition 1802, the execution condition 1803, and the confirmation mode. The component replacement condition reception unit 214 that has received the instruction receives the conditions specified by the component condition input area 1802, the execution condition input area 1803, and the check box 1807 for receiving the confirmation mode specification, and executes the editing process. Control is transferred to the component replacement unit 224 of the unit 122.

  A cancel button 1805 is a button for accepting an input of an instruction to end the process of the component replacement condition accepting unit 214. The component replacement condition receiving unit 214 that has received the instruction interrupts the process and returns control to the control unit 125.

  A save button 1806 is a button for accepting an instruction to store the conditions specified in the check box 1807 for accepting designation of the component condition 1802, the execution condition 1803, and the confirmation mode in an area (not shown) of the data storage unit 13. . Receiving the instruction, the component replacement condition receiving unit 214 stores in the data storage unit 13 the conditions specified by the check box 1807 for receiving the specification of the component condition 1802, the execution condition 1803, and the confirmation mode.

  A check box 1807 is an area for accepting designation of applying a confirmation mode in which processing is performed while confirming the attribute value setting for each component with the user, and accepts designation of application depending on whether the check is ON or OFF.

  Return to the description of the process. When the screen 1800 is displayed in step 191, the component replacement condition receiving unit 214 of the editing condition receiving unit 121 includes a storage condition input region 1801, a component condition input region 1802, an execution condition input region 1803, Operations for the execute button 1804, cancel button 1805, save button 1806, and check box 1807 are accepted. Among them, when an operation for the execution button 1804 is accepted, the designation content of the storage condition input area 1801 and the designation content of the part condition input area 1802 are accepted (step 192), and the execution condition input area 1803 and the check box 1807 The designated content is accepted (step 193). Then, for example, the component replacement unit 224 is requested to perform the processing so that the processing is performed for each component using the received condition as a parameter (step 194).

  When the component replacement unit 224 acquires the specified content of the component condition input area 1802 from the parameters, the component replacement unit 224 searches the component master table 1311 and the component table 1312 and matches the specified content of the component condition with the component master table 1311 and the component table 1312. Are loaded into the main memory 5322. If there is no matching record, this flow is terminated and control is returned to the control unit 125 in order to process it as an error.

  The component replacement unit 224 performs the following processing of steps 195 to 199 for each of the records of the loaded component master table 1311 and the component table 1312.

  The component replacement unit 224 determines whether or not the check box 1807 is set to ON (step 195).

  When the determination result in step 195 is NO, that is, when the check box 1807 is set to OFF, the component replacement unit 224 specifies the execution condition specification contents for the loaded component master table 1311 and component table 1312 records. Is executed, and the execution content is recorded in the edit history table 1323 (step 196).

  Specifically, for example, the component replacement unit 224 copies all the values included in the record having the component code specified by the component specification 1823 included in the BOM specified by the copy source BOM 1822 and loads the loaded component master table. The copied value is written in the records 1311 and the parts table 1312.

  After executing step 196, the component replacement unit 224 determines whether or not the processing has been performed for all the loaded component master tables 1311 and the component table 1312. YES, that is, all the loaded component master tables 1311 If it has been performed on the parts table 1312, the process is terminated and control is returned to the part replacement condition reception unit 214 of the editing condition reception unit 121, and the part replacement condition reception unit 214 interrupts the process, Control is returned to the control unit 125 (step 197).

  If the determination in step 197 is NO, that is, if the execution has not been completed for all the loaded component master table 1311 and the component table 1312, the component replacement unit 224 executes the processing from step 195 again.

  If the determination result in step 195 is YES, that is, if the check box 1807 is set to ON, the component replacement unit 224 includes the component code 312 of the record to be executed among the loaded component master table 1311 and the component table 1312. Alternatively, a message including a set of the parent part code 321 and the child part code 322 to be executed is displayed on the screen to make the user confirm the target to be executed (step 198).

  Here, the message screen displayed in step 198 is the same as the target component confirmation screen 1300 shown in FIG.

  When the specified content is transmitted by an operation on the OK button 1304 of the target component confirmation screen 1300 displayed in step 198, the component replacement unit 224 receives a user response via the input unit 111, and the content is executed. It is determined whether or not it is permitted (step 199). For example, for each component shown in the component display field 1307, if the corresponding check input field 1306 is ON, it is determined that the execution is permitted.

  If the result of determination in step 199 is YES, that is, if the received response permits execution, the component replacement unit 224 executes step 196.

  If the result of determination in step 199 is NO, that is, if the accepted response does not permit execution, the component replacement unit 224 executes step 197.

  The processing flow in the case of the component replacement processing has been described above.

  Hereinafter, processing when the command received in step 71 is a component attribute copy command will be described with reference to FIGS. 20 and 21. FIG. If the received command is a component attribute copy command, the control unit 125 passes control to the component attribute copy condition reception unit 215. Then, the component attribute copy condition receiving unit 215 prompts the user to input a condition specification and displays a screen for receiving the input. For example, the component attribute copy condition reception unit 215 displays a component condition and execution condition input screen 2000 as shown in FIG. 21 to the user via the output unit 112 (step 261).

  Here, the screen 2000 of FIG. 21 will be described. A screen 2000 shown in FIG. 21 is an input screen for performing component attribute copying. The screen 2000 includes a storage condition input area 2001, a part condition input area 2002, an execution condition input area 2003, an execution button 2004 that is a button for inputting a command to execute a command under the input conditions, and this screen Cancel button 2005 that is a button for inputting an instruction to cancel, save button 2006 that is a button for inputting a command for saving conditions set on screen 2000, and setting of attribute values for each part And a check box 2007 for designating a confirmation mode to be processed while confirming.

  First, the storage condition input area 2001 will be described. In a storage condition input area 2001, a combo box that selectively receives a storage condition name is displayed. When the selection of the storage name is received from the user via the combo box, the control unit 125 extracts the storage condition that matches the specified storage name from the data storage unit 13 and stores the part condition and the execution condition stored in advance. Is read. The read conditions are displayed in the parts condition input area 2002 and the execution condition input area 2003. Accordingly, the user can reuse by selecting a previously saved condition, and the reuse becomes easy. The pre-saved conditions are part conditions and execution conditions that are pre-named and saved in the data storage unit 13 by accepting an instruction to the save button 2006.

  Next, the component condition input area 2002 will be described. The component condition input area 2002 includes two condition input areas, a first condition and a second condition. There may be three or more input areas. Further, the logical relationship between the first condition and the second condition is selected and input by the user to the relationship input 2016. The relation input 2016 is displayed by a combo box or the like that can be selectively input, and the logic of any one of “first condition only”, “and (And)”, and “or (Or)” is displayed. A relationship can be specified. “Only the first condition” means that only parts satisfying the first condition are to be processed, and the second condition is not applied to selection of the process target. This means that a part that also satisfies the second condition is to be processed. “Or” means that a part that satisfies only the first condition, a part that satisfies only the second condition, or a part that satisfies both the first condition and the second condition is a processing target.

  The first condition input area of the part condition input area 2002 is an area for inputting a condition for specifying a component to be processed. The part condition input area 2002 includes a search target specification area 2011, a condition selection specification area 2012, an attribute name specification area 2013, a search value specification area 2014, and a search value condition specification area 2015. The search target designation area 2011 is an area for receiving an input for designating whether to search for and extract a target part with a part code, or to search for and extract a target part with a part attribute. The condition selection area 2012 is an area that receives an input for specifying a condition for narrowing down a target to be searched and extracted. The condition selection area 2012 is displayed so as not to accept an input when “part code” is designated in the search object designation area 2011. The attribute name designation area 2013 is an area for designating the name of an attribute for narrowing down the object to be searched and extracted. The attribute name designation area 2013 is displayed so as not to accept an input when “part code” is designated in the search target designation area 2011. The search value specification area 2014 is an area for specifying a search attribute value by a character string. Further, the value condition specifying area 2015 to be searched is an area for receiving the input of the detailed search condition of the value to be searched specified in the value specifying area 2014 to be searched. The value condition specifying area 2015 to search includes (search value) “includes”, “does not include”, “matches with”, “does not match”, “greater than”, and “more than”. And “less than”, “below”, “starts with”, “does not start with”, “ends with”, and “does not end with”.

  Note that these conditions are the same as those in the value condition designation area 615 to be searched for on the screen 60 displayed in the component attribute batch setting process described above, and thus the description thereof is omitted here.

  Similar to the first condition input area, the second condition input area includes a search target designation area 2017, a condition selection designation area 2018, an attribute name designation area 2019, a value designation area 2020 to be retrieved, and a value condition designation to be retrieved. An area 2021. The same as the search target designation area 2011, the condition selection designation area 2012, the attribute name designation area 2013, the value designation area 2014 to be retrieved, and the value condition designation area 2015 to be retrieved, respectively, in the first condition input area. is there.

  Next, the execution condition input area 2003 will be described. The content specified in the execution condition input area 2003 is to specify detailed conditions for processing to be performed on the part selected in the part condition input area 2002. For example, when “attribute copying” is performed, a condition for specifying an attribute to be set is designated.

  The execution condition input area 2003 includes a copy source BOM 2022, a condition selection 2023, an attribute name 2024, a parent part designation 2025, and a child part designation 2026. The copy source BOM 2022 is an area that accepts specification of conditions for narrowing down the target copy source BOM based on the conditions specified by the user. The condition selection 2023 is an area for receiving designation of a component management unit to which a component as a copy source belongs. An attribute name 2024 is an area for accepting designation of an attribute as a copy source. The parent part designation 2025 and the child part designation 2026 are areas for receiving designation of a parent part code and a child part code for specifying a part having an attribute as a copy source.

  The execution button 2004 is a button for receiving an instruction to start processing using the conditions specified in the check box 2007 for receiving specification of the component condition 2002, the execution condition 2003, and the confirmation mode. The component attribute copy condition reception unit 215 that has received the instruction receives the conditions specified by the component condition input area 2002, the execution condition input area 2003, and the check box 2007 for receiving the confirmation mode specification, and the editing process. Control is transferred to the component attribute copy unit 225 of the execution unit 122.

  A cancel button 2005 is a button for accepting an input of an instruction to end the process of the component attribute copy condition accepting unit 215. The component attribute copy condition reception unit 215 that has received the instruction interrupts the process and returns control to the control unit 125.

  The save button 2006 is a button for accepting an instruction to store the conditions specified in the check box 2007 for accepting designation of the component condition 2002, the execution condition 2003, and the confirmation mode in an area (not shown) of the data storage unit 13. . The component attribute copy condition receiving unit 215 that has received the instruction causes the data storage unit 13 to store the conditions specified by the check box 2007 for receiving the specification of the component condition 2002, the execution condition 2003, and the confirmation mode.

  A check box 2007 is an area for accepting designation of applying a confirmation mode in which processing is performed while confirming the attribute value setting with the user for each component, and accepts designation of application depending on whether the check is ON or OFF.

  Return to the description of the process. When the screen 2000 is displayed in step 261, the component attribute copy condition receiving unit 215 of the editing condition receiving unit 121 includes a storage condition input area 2001, a part condition input area 2002, and an execution condition input area 2003. , An operation for the execution button 2004, the cancel button 2005, the save button 2006, and the check box 2007 is accepted. Among them, when an operation on the execution button 2004 is accepted, the designated content of the storage condition input area 2001 and the designated content of the part condition input area 2002 are accepted (step 262), and the execution condition input area 2003 and the check box 2007 are displayed. The specified content is accepted (step 263). Then, for example, the component attribute copying unit 225 is requested to perform the processing so that the processing is performed for each component using the received condition as a parameter (step 264).

  When the component attribute copy unit 225 acquires the specified content of the component condition input area 2002 from the parameters, the component attribute copy unit 225 searches the component master table 1311 and the component table 1312 and matches the specified content of the component condition with the component master table 1311 and the component table. The record 1312 is loaded into the main memory 5322. If there is no matching record, this flow is terminated and control is returned to the control unit 125 in order to process it as an error.

  The component attribute copy unit 225 performs the following processes of steps 265 to 269 for each of the loaded component master table 1311 and component table 1312 records.

  The component attribute copy unit 225 determines whether or not the check box 2007 is set to ON (step 265).

  If the determination result in step 265 is NO, that is, if the check box 2607 is set to OFF, the component attribute copy unit 225 specifies execution conditions for the loaded records of the component master table 1311 and the component table 1312. The processing is performed based on the contents, and the execution contents are recorded in the editing history table 1323 (step 266).

  Specifically, for example, the component attribute copy unit 225 includes the parent component code specified in the parent component code 2025 and the child component code 2026 for the component configuration specified in the condition selection 2023 included in the BOM specified in the copy source BOM 2022. The attribute value of the attribute name 2024 included in the record having the child part code is copied, and the copied attribute value is written into the loaded parts master table 1311 and parts table 1312 records.

  After executing step 266, the component attribute copy unit 225 determines whether or not the processing has been performed for all the loaded component master tables 1311 and the component table 1312, and YES, that is, all the loaded component master tables 1311. And the parts table 1312, the process is terminated and control is returned to the part attribute copy condition accepting unit 215 of the editing condition accepting unit 121, and the part attribute copy condition accepting unit 215 performs the process. The process is interrupted, and control is returned to the control unit 125 (step 267).

  If the determination in step 267 is NO, that is, if the execution has not been completed for all the loaded component master table 1311 and the component table 1312, the component attribute copy unit 225 performs the processing from step 265 again. .

  When the determination result in step 265 is YES, that is, when the check box 2007 is set to ON, the component attribute copy unit 225 selects the component code 312 of the record to be executed from the loaded component master table 1311 and component table 1312. Alternatively, a message including a set of the parent part code 321 and the child part code 322 to be executed is displayed on the screen to make the user confirm the execution target (step 268).

  Here, the message screen displayed in step 268 is the same screen as the target component confirmation screen 1300 shown in FIG.

  When the specified content is transmitted by an operation on the OK button 1304 of the target component confirmation screen 1300 displayed in step 268, the component attribute copy unit 225 receives the user's response via the input unit 111, and the content is executed. It is determined whether or not it is permitted (step 269). For example, for each component shown in the component display field 1307, if the corresponding check input field 1306 is ON, it is determined that the execution is permitted.

  If the result of determination in step 269 is YES, that is, if the received response permits execution, the component attribute copy unit 225 executes step 266.

  If the result of determination in step 269 is NO, that is, if the accepted response does not permit execution, the component attribute copy unit 225 executes step 267.

  The processing flow in the case of component attribute copy processing has been described above.

  Next, the flow of editing processing using a script in the parts table editing system 1 according to the present embodiment will be described with reference to FIG.

As illustrated in FIG. 22, first, the control unit 125 receives a notification that script execution is performed, and transfers control to the script reception unit 216 of the editing condition reception unit 121 in accordance with the received notification. Then, the script receiving unit 216 of the editing condition receiving unit 121 to which the control has been transferred prompts the user to input a condition designation via the output unit 112 and is an input screen 80 in FIG. Is displayed to the user. (Step 91)
Here, the screen 80 of FIG. 23 will be described. A screen 80 shown in FIG. 23 is an input screen for executing a script. The screen 80 is a button for receiving a user name input area 81, a password input area 82, a target BOM name input area 83, a script file name input area 84, and an instruction to execute the input script. The button 85 and a cancel button 86, which is a button for accepting an instruction to cancel and cancel the input on this screen, are configured.

  First, the user name input area 81 will be described. The user name input area 81 is a text box for inputting a user name for executing the script.

  Next, the password input area 82 will be described. The password input area 82 is a text box for inputting a password for certifying the authenticity of the user input in the user name input area 81.

  The target BOM name input area 83 is a text box for inputting the name of a BOM that is a target for executing the script.

  The script file name input area 84 is a text box for inputting a script name for identifying a script to be executed.

  The execute button 85 is an instruction to start processing using the conditions specified by the user name input area 81, the password input area 82, the target BOM name input area 83, and the script file name input area 84. It is a button that accepts. Receiving the instruction, the script receiving unit 216 receives the conditions specified by the user name input area 81, the password input area 82, the target BOM name input area 83, and the script file name input area 84. Then, control is passed to the script execution unit 226 of the editing process execution unit 122.

  The cancel button 86 is a button for accepting an instruction to end the processing of the script accepting unit 216. The script reception unit 216 that has received the instruction interrupts the process and returns control to the control unit 125.

  Return to the description of the process. When the screen 80 displayed in step 91 is displayed, the script receiving unit 216 inputs the user name input area 81, the password input area 82, the target BOM name input area 83, and the script file name input. Operations for the area 84, the execution button 85, and the cancel button 86 are accepted, and the respective operations are performed. When an operation for the execution button 85 is received, the specified contents of the user name input area 81, the password input area 82, the target BOM name input area 83, and the script file name input area 84 are displayed. Accept, pass as a parameter to the script execution unit 226, and pass control.

  The script execution unit 226 extracts the user name and password from the passed parameters and performs authentication (step 92). Note that this authentication may be a request for authentication to an authentication server existing in another device as long as the authentication is a specification that permits using a user name and a password.

  Next, the script execution unit 226 uses the target BOM name and the script file name among the passed parameters, and edits the BOM that matches the target BOM name from the BOM data storage unit 131 and edits, respectively. The script file 1324 that matches the script file name is allocated from the operation history data storage unit 132 and loaded into the main storage device 5322. (Step 93).

The script execution unit 226 reads the command for each line of the script file 1324 loaded in step 93 and assembles the component condition description and the execution condition description as parameters. Then, the script execution unit 226 transfers control together with parameters to each function unit of the editing process execution unit 122 according to the command. (Step 94)
Each functional unit of the editing process execution unit 122 searches the parts master table 1311 and the parts table 1312 using the part conditions from the parameters passed in step 94, and the part master table 1311 that matches the specified content of the part conditions. The parts table 1312 is selected from the BOM loaded in step 93 and loaded into the main memory 5322 (step 95).

  Each functional unit of the editing process execution unit 122 acquires an execution condition from the parameters passed in Step 94 (Step 96).

  Each functional unit of the editing process execution unit 122 executes a command on all of the parts master table 1311 and the parts table 1312 loaded in Step 95 based on the specified contents of the execution condition acquired in Step 96. The command that is the execution content and its parameters are divided and stored in the command column 432, the condition (1) column 433, the condition relation column 434, the condition (2) column 435, and the execution condition column 436 of the command history table 1322. When the command for all the loaded parts master table 1311 and parts table 1312 has been executed, control is returned to the script receiving unit 216 of the editing condition receiving unit 121, and the script receiving unit 216 is shown in the lower diagram of FIG. As described above, the execution result screen 87 is displayed via the output unit 112.

  The execution result screen 87 includes an area indicating the execution result, a re-execution button 88 that is a button for accepting re-execution, and a close button 89 that is a button for accepting an instruction to close the screen.

  The re-execution button 88 is a button that, when receiving an instruction to execute, gives an instruction to execute the steps 91 to 97 shown in FIG.

  Close 89 is a button that, upon receiving an instruction to execute, terminates the process and returns control to the control unit 125.

  When the execution instruction for the close button 89 is received, the script reception unit 216 ends its own processing and returns control to the control unit 125 (step 97).

  Next, a flow of processing related to editing / operation history recording in the parts table editing system 1 according to the present embodiment will be described with reference to FIG.

  As shown in Step 101 of FIG. 24, when the control unit 125 receives an editing / operation history recording instruction, it determines whether or not it is a recording start instruction (Step 101).

  If the result of determination in step 101 is NO, that is, if it is not a recording start instruction, the processing is terminated as it is.

  If the result of determination in step 101 is YES, that is, a recording start instruction, the control unit 125 has received a recording start instruction to the editing / operation history recording unit 231 of the editing / operation history management unit 123. And pass control.

  The editing / operation history recording unit 231 first creates a new file in the editing / operation history data storage unit 132 (step 102).

  Then, the editing / operation history recording unit 231 monitors execution by hooking the execution of each function unit of the editing processing execution unit 122, and the parent part, child part, editing operation, editing target, and change that are parameters of the executed operation. The previous value and the changed value are acquired and recorded in the new file created in step 102 (step 103).

  The editing / operation history recording unit 231 continues to execute the process of step 103 until a recording end instruction is received via the input unit 111. The editing / operation history recording unit 231 determines whether a recording end instruction has been received from the input unit 111 (step 104).

  When the recording end instruction is accepted (YES in step 104), the editing / operation history recording unit 231 extracts the editing record corresponding to the editing history from the recording start point to the recording end point from the file recorded in step 103 ( Step 105).

  Then, the editing / operation history recording unit 231 displays an input screen for inputting a name for identifying the recording of the editing history and a management comment via the output unit 112, and accepts the input (step 106). ).

  The editing / operation history recording unit 231 records the parent part, child part, editing operation, editing target, value before change, and value after change recorded in step 103 in the command history table 1322. The data is stored in a parent part field 422, a child part field 423, an editing operation field 424, an editing target field 425, a value field 426 before change, and a value field 427 after change. Then, the name and comment received in step 106 are stored in the remarks column 428, an operation ID that is a unique value is assigned, and stored in the operation ID 421 column and the link ID column 413 of the history list 1321. A serial number on the history list 1321 is allocated and stored in the ID column 411 of the list 1321, and “operation” is stored in the type 412 column. Then, the process ends (step 107).

  Also, if there is a command executed between the start of recording and the end of recording in step 107, the editing / operation history recording unit 231 disassembles the command and stores it in the command history table 1322, where a unique value is stored. Is stored in the command ID 431 field and the link ID field 413 of the history list 1321, and the serial number on the history list 1321 is allocated and stored in the ID field 411 of the history list 1321, The fact that it is “command” is stored in the type 412 column.

  Next, a processing flow relating to execution of editing / operation history will be described with reference to FIG.

  Upon receiving an instruction to execute editing / operation history, the control unit 125 passes control to the editing / operation history execution receiving unit 232 of the editing / operation history management unit 123. The edit / operation history execution accepting unit 232 displays an input screen for inputting the name of the target BOM to the user and determines the target BOM for executing the edit / operation history, and accepts the input (step) 1101).

  The editing / operation history execution receiving unit 232 loads the BOM corresponding to the target BOM name received in step 1101 into the main storage device 5322, refers to the history list 1321, and determines a predetermined number of recent operations (for example, 50). Get the records up to. If the value stored in the acquired record type column 412 is “command”, the editing / operation history execution receiving unit 232 identifies the history that matches the value in the link ID 413 column for the command history table 1322. The command ID column 431 is searched to identify a history record. If “operation”, the editing history table 1323 is targeted, and the operation ID column 421 is used to identify a history that matches the value in the link ID 413 column. In order to specify the history record and select and input the specified history record, a selection screen showing the stored name and comment stored in the remark is displayed (step 1102).

  The selection screen displayed in step 1102 will be described with reference to FIG.

  A screen 1200 is a screen that accepts an input from a user to select a recorded editing / operation history. The screen 1200 includes a storage name selection input area 1201, a comment field 1202, a copy execution area 1203 that is a check box, an execution button 1204, and a cancel button 1205.

  The saved name input area 1201 is an area for displaying the name saved in step 107 of the flow for recording the editing / operation history.

  The comment column 1202 is an area for displaying the comment saved in step 107 of the flow for recording the editing / operation history.

  In the copy and execution area 1203, when executing the editing / operation history, either the target BOM is copied and the process is executed on the copied BOM, or the process is directly executed on the target BOM. It is a check box that accepts such designation.

  The execute button 1204 accepts the designation of the designated save name of the selected save name input area 1201 and the ON / OFF of the copy area 1203 to be copied, and passes it to the editing / operation history execution accepting unit 232 as a parameter for execution. It is a button to make.

  A cancel button 1205 is a button for accepting an instruction to end the process of the editing / operation history execution accepting unit 232. Receiving the instruction, the editing / operation history execution receiving unit 232 interrupts the process and returns control to the control unit 125.

  Return to the description of the process. When the screen 1200 shown in FIG. 26 displayed in step 1102 is displayed, the editing / operation history execution receiving unit 232 performs a storage name input area 1201, a comment field 1202, a copy execution area 1203, and an execution. Operations for the button 1204 and the cancel button 1205 are accepted, and the respective operations are performed. Among them, when an operation for the execution button 1204 is accepted, the specified contents of the storage name input area 1201 and the copy and execution area 1203 are accepted, and the history execution control unit 241 of the editing / operation history execution unit 124 receives parameters. And pass control as.

  The history execution control unit 241 accepts the ON / OFF designation of the execution area 1203 by copying the received parameters (step 1103).

  Next, the history execution control unit 241 acquires the storage name name as the editing history name from the received parameters (step 1104).

  The history execution control unit 241 determines that the target BOM received in step 1101 is set as another BOM if the specified content indicating whether or not to copy and execute received in step 1103 is ON (that is, copy and execute). make a copy. Then, the history execution control unit 241 specifies a record that matches the command ID 431 in the command history table 1322 of the editing / operation history data storage unit 132 from the editing history name received in step 1104, and stores the record in the main storage device 5322. Load it. If the specified content received in step 1103 is OFF (that is, execute without copying), the history execution control unit 241 loads the target BOM received in step 1101 to the main storage device 5322 and receives it in step 1104. A record that matches the command ID 431 in the command history table 1322 of the editing / operation history data storage unit 132 is specified from the editing history name, and the record is loaded into the main storage device 5322.

  In addition, the history execution control unit 241 specifies a record that matches the operation ID 422 of the editing history table 1323 of the editing / operation history data storage unit 132 from the editing history name received in step 1104, and stores the record in the main memory. Load into device 5322.

  The history execution control unit 241 reads a command from the loaded command history table 1322 and assembles the component condition description and the execution condition description as parameters.

  Specifically, the history execution control unit 241 includes the command stored in the command column 432 of the command history table 1322, the condition (1) column 433, the condition relation column 434, and the condition (2) column 435 of the command history table 1322. The execution condition 436 is read out and the information is combined according to a predetermined rule, thereby creating a character string of the command and its parameter.

  Here, the predetermined rule is that a blank is combined after the read command. If the value in the condition relation column 434 of the component condition is “only the first condition”, only the condition (1) is combined. If the value in the condition relation field 434 of the part condition is “And”, the condition (1) is combined after combining “AND (”, and then the comma symbol is combined, and the condition following the comma symbol Combine (2) and then combine ")". If the value in the condition relation field 434 of the component condition is “or (Or)”, after combining “OR (”, the condition (1) is combined, and then a comma symbol is combined, followed by a comma symbol and a condition. Combine (2) and then combine ")". Subsequently, the comma symbols are combined, and then the values in the execution condition column 436 are combined. Then, the end-of-line symbol “;” is combined to complete the command sentence.

  For example, in the history example shown in FIG. 7, in the history identified by “ID1”, the value in the command column 432 is “SetAttr”, and the value in the condition (1) column 433 of the component condition is “EQU (part attribute. Part configuration.part type, “screw”) ”, the value of the condition relation column 434 of the part condition is“ condition 1 only ”, the value of the condition (2) column 435 is“ (not specified) ”, The value of the execution condition column 436 is “(part configuration. Assembly operation,“ [↓] [Q] ”)”.

  Based on this, the history execution control unit 241 reproduces the command to be executed. First, a blank is combined after “SetAttr”, and then only the condition (1) is combined because the value of the condition relation column 434 of the part condition is “condition 1 only”. Next, a comma symbol is added, and then the values in the execution condition column 436 are combined. Then, the end-of-line symbol “;” is combined to complete the command sentence. As a result, a command statement “SetAttr (blank) EQU (part attribute.part configuration.part type,“ screw ”), (part configuration.assembly operation,“ [↓] [Q] ”);” is obtained.

  Then, the history execution control unit 241 transfers control together with parameters to each function unit of the editing / operation history execution unit 124 in accordance with the command. That is, if the command is SetAttr, control is transferred to the component attribute batch installation unit 221. If the command is DelParts, control is transferred to the component deletion unit 222. If the command is AddParts, control is performed to the component addition unit 223. If the command is RplParts, control is transferred to the component replacement unit 224. If the command is CpyAttr, control is transferred to the component attribute copy unit 225.

  Then, each functional unit of the editing / operation history execution unit 124 receives the part condition from the transferred parameter, searches the part master table 1311 and the part table 1312, and matches the specified part condition table. The record 1311 and the record of the parts table 1312 are selected and loaded into the main storage device 5322.

  Of the functional units of the editing / operation history executing unit 124, the functional unit corresponding to the command to be executed processes all of the loaded records in the component master table 1311 and the records in the component table 1312.

  When each function unit of the editing / operation history executing unit 124 finishes executing the command, it subsequently performs processing based on the editing history. Specifically, if the value of the editing operation 424 in the editing history table 1323 specified above is a batch setting of component attributes, the editing / operation history execution unit 124 passes control to the component attribute batch setting unit 242. Then, the part attribute batch setting unit 242 targets the parts in the parts table 1312 identified from the values in the parent part field 422 and the values in the child parts field 423 stored in the loaded record of the editing history table 1323. As long as the value in the BOM edit target field 425 matches the value 426 before the change, the value is changed to the value 427 after the change and stored. If the editing history is deletion of a component, the editing / operation history execution unit 124 passes control to the component deletion unit 243 of the editing / operation history execution unit 124. The component deletion unit 243 of the editing / operation history execution unit 124 then identifies a component in the component table that can be identified from the value in the parent component column 422 and the value in the child component column 423 stored in the record of the loaded editing history table 1323. Delete the target. If the editing history is the addition of a component, the editing / operation history execution unit 124 passes control to the component addition unit 243 of the editing / operation history execution unit 124. Then, the component adding unit 243 of the editing / operation history executing unit 124 adds a new record including the value of the parent component column 422 and the value of the child component column 423 to the component table 1312.

  Then, the editing / operation history execution unit 124 ends the processing, returns control to the editing / operation history execution reception unit 232 of the editing / operation history management unit 123, and ends (step 1105).

  The embodiment of the present invention has been described above.

  The parts table editing system 1 is not only a transaction target as a system, but can also be a transaction target for each device or for each program component that realizes the operation of the device.

  The above is the embodiment of the present invention.

It is a system configuration figure in an embodiment of the present invention. It is a functional block diagram of the edit condition reception part in embodiment of this invention. It is a functional block diagram of the edit process execution part in embodiment of this invention. It is a function block diagram of the edit and operation history management part in embodiment of this invention. It is a function block diagram of the edit and operation history execution part in embodiment of this invention. It is a figure which shows the data structure of the components table | surface in embodiment of this invention. It is a figure which shows the data structure of the condition log | history in embodiment of this invention. It is a figure which shows the data structure of the edit history in embodiment of this invention. It is a figure which shows the data structure of the script in embodiment of this invention. It is a figure which shows the hardware constitutions in embodiment of this invention. It is a flowchart which shows the flow of the edit process in embodiment of this invention. It is a figure which shows the input screen of the component attribute batch setting in embodiment of this invention. It is a figure which shows the confirmation screen of the process execution in embodiment of this invention. It is a flowchart which shows the flow of the components deletion process in embodiment of this invention. It is a figure which shows the input screen of components deletion in embodiment of this invention. It is a flowchart which shows the flow of the component addition process in embodiment of this invention. It is a figure which shows the input screen of components addition in embodiment of this invention. It is a flowchart which shows the flow of the component replacement process in embodiment of this invention. It is a figure which shows the input screen of component replacement in embodiment of this invention. It is a flowchart which shows the flow of the component attribute copy process in embodiment of this invention. It is a figure which shows the input screen of the component attribute copy in embodiment of this invention. It is a flowchart which shows the flow of the script execution process in embodiment of this invention. It is a figure which shows the input screen of script execution in embodiment of this invention. It is a flowchart which shows the flow of a recording process of the edit and operation history in embodiment of this invention. It is a flowchart which shows the flow of the edit and operation log | history execution process in embodiment of this invention. It is a figure which shows the input screen of execution of edit and operation history in embodiment of this invention.

Explanation of symbols

1: parts table editing system, 11: input / output unit, 12: BOM management unit, 13: data storage unit, 51: client, 52: network, 53: server

Claims (7)

A BOM editing device for editing a BOM,
A control unit that executes a plurality of editing instructions, a storage unit, and an input unit;
The controller is
One editing command among the plurality of editing commands, a component condition that is a condition for specifying a component to be edited from the parts table, and an execution condition that is a condition for specifying the editing content of the editing command. , An edit reception unit that receives via the input unit;
An editing unit that acquires a component that satisfies a component condition received by the component condition receiving unit from the parts table, and performs an editing process on the acquired component according to the execution condition received by the editing receiving unit;
A history storage unit that stores in the storage unit a history of editing performed on the parts table;
A history storage unit that accepts an input of a name and a comment to be added to the stored editing history, adds the editing history to the editing history, and stores it in the storage unit;
A bill of materials designation accepting unit that accepts designation of a bill of materials to be processed via the input unit;
An edit history stored in the storage unit by the history storage unit is read and displayed together with the comment, and an edit history selected from the edit history is received via the input unit;
The edit command included in the edit history received by the edit history receiving unit, the part condition, and the execution condition are specified, and a part satisfying the part condition is acquired from the parts table, and the acquired A history reproducing unit that performs an editing process in accordance with the editing command with a condition specified as the execution condition for the component;
A parts table editing apparatus comprising: The parts table editing device according to claim 1,
The control unit further includes:
Via the input unit, a start instruction receiving unit that receives an instruction to start storing the editing history to the history storage unit;
An end instruction receiving unit that receives an instruction to end storage of the editing history via the input unit;
The history storage unit starts the process of storing the editing history when receiving an instruction from the start instruction receiving unit, and ends the process of storing the editing history when receiving an instruction from the end instruction receiving unit To
A parts table editing device. The parts table editing device according to claim 1,
In addition, with an output unit,
The history execution accepting unit further accepts an instruction whether to confirm execution of the editing process via the input unit,
In response to the confirmation instruction received by the history execution reception unit, the history execution unit displays and displays on the output unit selectable for each component that satisfies the part condition before performing the editing. Among the parts, information on a part selected and input via the input unit is received, and editing is performed on the part that is selected and input.
A parts table editing device. The parts table editing device according to claim 1,
The edit accepting unit further accepts designation of a script stored in the storage unit via the input unit, and is an object to be edited from the editing command described in the designated script and the parts table. Accepts a component condition that is a condition for specifying a component and an execution condition that is a condition for specifying the processing content of the editing instruction;
The editing unit acquires a part satisfying the received part condition from the parts table, and attaches a condition specified to the execution condition received by the editing receiving unit to the acquired part to the editing command. According to the editing process.
A parts table editing device. A BOM editing program for editing a BOM,
For a computer including a control unit that executes a plurality of editing instructions, a storage unit, and an input unit,
One editing command among the plurality of editing commands, a component condition that is a condition for specifying a component to be edited from the parts table, and an execution condition that is a condition for specifying the editing content of the editing command. , An edit reception step for receiving via the input unit;
An editing step for acquiring a part satisfying the part condition received in the part condition receiving step from the parts table, and performing an editing process on the acquired part according to the execution condition received by the editing receiving unit;
A history storage step of storing a history of editing performed on the parts table in the storage unit;
A history saving step of accepting an input of a name and a comment to be added to the recorded editing history via the input unit, adding it to the editing history, and storing it in the storage unit,
A bill of materials designation accepting step of accepting designation of a bill of materials to be processed via the input unit;
An edit history stored in the storage unit by the history saving step is read and displayed together with the comment, and an edit history selected and input from among the edit history is received via the input unit;
The editing command included in the editing history received by the editing history receiving step, the part condition, and the execution condition are specified, and a part satisfying the part condition is acquired from the parts table, and the acquired A history reproduction step for performing an editing process in accordance with the editing command with a condition designated as the execution condition for the part;
A bill of material editing program characterized in that A BOM editing system for editing a BOM,
The parts table editing system
A parts table editing device and an operation terminal;
The operation terminal is
Operation accepting means for accepting an operation to the parts table editing device;
Transmitting means for transmitting the operation received by the operation receiving means to the parts table editing device;
With
The parts table editing device
A control unit that executes a plurality of editing instructions; and a storage unit,
The controller is
One editing command among the plurality of editing commands, a component condition that is a condition for specifying a component to be edited from the parts table, and an execution condition that is a condition for specifying the editing content of the editing command. An edit accepting unit that accepts via the transmission means of the operation terminal;
An editing unit that acquires a component that satisfies a component condition received by the component condition receiving unit from the parts table, and performs an editing process on the acquired component according to the execution condition received by the editing receiving unit;
A history storage unit that stores in the storage unit a history of editing performed on the parts table;
A history storage unit that accepts an input of a name and a comment to be added to the recorded editing history via the transmission unit of the operation terminal, adds the editing history to the editing history, and stores the history in the storage unit;
An edit history stored in the storage unit by the history storage unit is read and displayed together with the comment, and an edit history selected from the edit history is received via the input unit;
The edit command included in the edit history received by the edit history receiving unit, the part condition, and the execution condition are specified, and a part satisfying the part condition is acquired from the parts table, and the acquired A history reproducing unit that performs an editing process in accordance with the editing command with a condition specified as the execution condition for the component;
A parts table editing system comprising: A method for editing a bill of materials by a bill of material editing device,
The parts table editing device
A control unit that executes a plurality of editing instructions, a storage unit, and an input unit;
The controller is
One editing command among the plurality of editing commands, a component condition that is a condition for specifying a component to be edited from the parts table, and an execution condition that is a condition for specifying the editing content of the editing command. , An edit reception unit that receives via the input unit;
An editing unit that acquires a component that satisfies a component condition received by the component condition receiving unit from the parts table, and performs an editing process on the acquired component according to the execution condition received by the editing receiving unit;
A history storage unit that stores in the storage unit a history of editing performed on the parts table;
A history storage unit that accepts an input of a name and a comment to be added to the recorded editing history, adds the editing history to the editing history, and stores the history in the storage unit;
A bill of materials designation accepting unit that accepts designation of a bill of materials to be processed via the input unit;
An edit history stored in the storage unit by the history storage unit is read and displayed together with the comment, and an edit history selected from the edit history is received via the input unit;
The edit command included in the edit history received by the edit history receiving unit, the part condition, and the execution condition are specified, and a part satisfying the part condition is acquired from the parts table, and the acquired A history reproducing unit that performs an editing process in accordance with the editing command with a condition specified as the execution condition for the component;
A method of editing a bill of materials, comprising:

Images