JP6115353B2 - Data management program, data management method, and data management apparatus - Google Patents

Description

  The present invention relates to a data management program, a data management method, and a data management apparatus.

  When a large number of objects are managed in a plurality of databases, different identification information may be given to each database even if the objects are the same. For example, in a company that manufactures and sells products, a unique part number is assigned to a part for each department such as a design department or a procurement department, and is managed in a parts table database dedicated to each department. In this case, the objects to which the same identification information is assigned in different databases may mean different objects.

  Conventionally, a technique for unifying part numbers by checking whether the part numbers of parts included in the parts table data are already registered in the parts table DB is known (for example, see Patent Document 1). ).

JP 2005-189940 A

  There is a desire to manage different identification information assigned to the same object in a plurality of databases with unified identification information. This is because it is inefficient if the same object is managed with only different identification information when it is necessary to transmit information across departments. In this case, it is necessary to select an appropriate unified identification number, but it is not sufficient to check whether the unified identification information is already used in another object as in Patent Document 1.

  In one aspect, an object of the present invention is to provide a data management program, a data management method, and a data management apparatus that can easily display identification information that can be candidates for unified identification information.

  In one aspect, the data management program is a data management program for managing the same target managed in each of a plurality of databases using unified identification information, and the plurality of databases for the same target When a plurality of identification information assigned in step S1 is selected, identification information already used as unified identification information among the plurality of identification information and identification information already associated with the unified identification information are specified. A program for causing a computer to execute a process for distinguishing and displaying the identified identification information and other identification information.

  In one aspect, the data management method is a data management method for managing the same object managed in each of a plurality of databases using unified identification information, and the plurality of databases for the same object. When a plurality of pieces of identification information given in is selected, identification information already used as unified identification information among the plurality of pieces of identification information and identification information already associated with the unified identification information are specified. A data management method in which a computer executes a step and a step of distinguishing and displaying the identified identification information and other identification information.

  In one aspect, the data management device is a data management device for managing the same target managed in each of a plurality of databases using unified identification information, and the plurality of databases for the same target When a plurality of pieces of identification information given in is selected, identification information already used as unified identification information among the plurality of pieces of identification information and identification information already associated with the unified identification information are specified. A specific unit; and a display unit that distinguishes and displays the identified identification information and other identification information.

  Identification information that can be a candidate for unified identification information can be easily displayed.

It is a figure showing roughly the composition of the data management system concerning one embodiment. FIG. 2A is a diagram illustrating the hardware configuration of the server, and FIG. 2B is a diagram illustrating the hardware configuration of the client. It is a functional block diagram of a server and a client. FIG. 4A is a diagram illustrating an example of a data structure of a parts table DB of a design department, and FIG. 4B is a diagram illustrating an example of a data structure of a parts table DB of a procurement department. FIG. 5A is a diagram illustrating an example of a mapping table, FIG. 5B is a diagram illustrating an example of a business-specific product number DB (part 1), and FIG. 5C is an integrated product number DB. FIG. 3 is a diagram (part 1) illustrating an example of the; It is a flowchart which shows a registration process. Fig.7 (a)-FIG.7 (c) are the figures for demonstrating a registration screen. It is a flowchart which shows an integrated product number provision process. FIG. 9A and FIG. 9B are views (No. 1) for explaining the integrated screen. It is FIG. (2) which shows an example of product number DB classified by business. FIG. 11A and FIG. 11B are diagrams (No. 2) for explaining the integrated screen. FIG. 12A is a diagram (part 2) illustrating an example of the integrated product number DB, and FIG. 12B is a diagram (part 3) illustrating an example of the product-specific product number DB. It is FIG. (3) for demonstrating an integrated screen. It is a flowchart which shows a search process. FIG. 15A and FIG. 15B are diagrams for explaining the search screen, and FIG. 15C is a diagram showing the search result screen.

  Hereinafter, an embodiment of a data management system will be described in detail with reference to FIGS.

  FIG. 1 schematically shows a configuration of a data management system 100 according to an embodiment. The data management system 100 of this embodiment includes a design department that examines parts used in a product to be developed and a combination thereof from a functional aspect, a procurement department that investigates parts procurement, a quality assurance department that investigates the quality of parts, and parts. This is a system for managing data of product components handled by related departments such as a production preparation department that performs production preparation for processing and assembly.

  As shown in FIG. 1, the data management system 100 includes a server 10 and a plurality of clients 70. The server 10 and the client 70 are connected to a network 80 such as the Internet or a LAN (Local Area Network).

  FIG. 2A shows the hardware configuration of the server 10. As shown in FIG. 2A, the server 10 includes a CPU (Central Processing Unit) 90, a ROM (Read Only Memory) 92, a RAM (Random Access Memory) 94, and a storage unit (here, an HDD (Hard Disk Drive)). 96, a network interface 97, a portable storage medium drive 99, and the like. Each component of the server 10 is connected to a bus 98. In the server 10, the CPU 90 executes a program (including a data management program) stored in the ROM 92 or the HDD 96 or a program (including a data management program) read from the portable storage medium 91 by the portable storage medium drive 99. By doing so, the functions as the parts table registration unit 12, the business-specific product number DB registration unit 14, the integrated product number registration unit 16, and the search unit 18 shown in FIG. 3 are realized. 3 also illustrates parts table DBs (databases) 30A, 30B, 30C,..., Mapping table 32, business-specific product number DB 34, and integrated product number DB 36 stored in the HDD 96 of the server 10.

  The parts table registration unit 12 registers part data in the parts table DBs 30 </ b> A, 30 </ b> B, 30 </ b> C,... According to an input from the client 70. Here, it is assumed that the parts table DBs 30A, 30B, 30C,... Are prepared for each department such as a design department and a procurement department and for each product. FIG. 4A shows an example of the data structure of the parts table DB 30A of the design department related to a certain product, and FIG. 4B shows an example of the data structure of the parts list DB 30B of the procurement department related to a certain product. It is shown.

  As shown in FIG. 4A, the parts table DB 30A of the design department has fields of “part number”, “name”, “quantity”, “weight”, and “classification”. In the “product number” field, the product number assigned to the part by the user of the design department is stored. In the “name” field, a name normally used by a user in the design department for a part is stored. In the “quantity” field, the quantity of each part used in a certain product is stored. The “weight” field stores the weight of each component. In the “division” field, the name (or abbreviation) of the division to which each part belongs is stored.

  On the other hand, as shown in FIG. 4B, the parts table DB 30B of the procurement department has fields of “product number”, “product name”, “QTY”, “manufacturer”, and “price”. In the “product number” field, the product number assigned to the part by the user of the procurement department is stored. In each department, the same part number is not necessarily assigned to the same part (target), but rather, an easy-to-use part number is often given to each department. Therefore, the same part number may be given to different parts in different parts table DBs. In the “product name” field, the product name (name) normally used by the user of the procurement department for the part is stored. The “product name” field in the parts table DB 30B corresponds to the “name” field in the parts table DB 30A. In the “QTY” field, the quantity of parts used in a certain product is stored. The “quantity” field in the parts table DB 30B corresponds to the “QTY” field in the parts table DB 30A. In the “manufacturer” field, the name of a manufacturer (manufacturer of the supplier) that manufactures each part is stored. In the “price” field, the procurement price of the part is stored.

  In this embodiment, as shown in FIG. 4A and FIG. 4B, in the parts table DB of each department, there are common (or corresponding) fields, while department-specific fields also exist. Existing.

  Returning to FIG. 3, the business-specific product number DB registration unit 14 registers the data registered in the parts table DBs 30A, 30B,... Of each department in the business-specific product number DB 34. Note that the business-specific product number DB registration unit 14 refers to the mapping table 32 in the registration process.

  FIG. 5A shows an example of the mapping table 32. As shown in FIG. 5A, the mapping table 32 associates the field names used in the business-specific product number DB 34 with the field names used in the parts table DBs 30A, 30B,. It is a table. For example, in the mapping table 32, the “name” field of the design department bill of materials DB 30A and the “product name” field of the procurement department bill of materials DB 30B correspond to the “name” field of the business-specific product number DB 34. Is defined. In the mapping table 32, each field of “quantity” in the bill of materials DB 30A of the design department and “QTY” of the parts bill DB 30B of the procurement department corresponds to the “quantity” field of the product number DB 34 by business. Is defined. In the present embodiment, it is assumed that the mapping table 32 is created in advance by the administrator.

  FIG. 5B shows an example of the business-specific product number DB 34. As shown in FIG. 5B, the business-specific product number DB 34 has fields of “product number”, “department”, “integration”, “name”, and “quantity”. In the “product number”, “name”, and “quantity” fields, data of corresponding fields of the parts table DBs 30A, 30B,. In the “department” field, information on which department table data is stored is stored. In the “integrated” field, a product number (integrated product number) for identifying the same component stored in each BOM DB is stored. The integrated product number is the product number (unified identification information) selected by the administrator from the product numbers (component identification information) assigned to the same component. The business-specific product number DB 34 is prepared for each product.

  The integrated product number registration unit 16 registers the integrated product number selected by the administrator in the integrated product number DB 36 and the business-specific product number DB 34. As shown in FIG. 5C, the integrated product number DB 36 has fields of “product number” and “attribute”. The integrated product number selected by the administrator is stored in the “product number” field. In the “attribute” field, various attributes (for example, product names) relating to the integrated product number are stored. The integrated product number registration unit 16 is also prepared for each product.

  When a department name of a certain department, a product number or item assigned to a part by a user belonging to the department, and another department name are input, the search unit 18 operates the product number assigned to the part in the other department. Search in the separate product number DB 34 and output to the client 70.

  FIG. 2B shows the hardware configuration of the client 70. The client 70 is a terminal used by users in each department such as a design department, a procurement department, and a quality assurance department. As shown in FIG. 2B, the client 70 includes a CPU 190, a ROM 192, a RAM 194, a storage unit (HDD) 196, a display unit 193, an input unit 195, a network interface 197, a portable storage medium drive 199, and the like. ing. Each component of the client 70 is connected to the bus 198. The display unit 193 includes a liquid crystal display unit and the like, and the input unit 195 includes a keyboard, a mouse, a touch panel, and the like. In the client 70, the CPU 190 executes a program stored in the ROM 192 or the HDD 196 or a program read from the portable storage medium 191 by the portable storage medium drive 199, whereby the display processing unit 60 shown in FIG. And the function as the input process part 62 is implement | achieved.

  The display processing unit 60 displays various screens on the display unit 193 in response to instructions from the parts table registration unit 12, the combined product number registration unit 16, and the search unit 18 of the server 10. The input processing unit 62 receives information input by the user using the client 70 via the input unit 195 and transmits the information to the parts table registration unit 12, the combined product number registration unit 16, and the search unit 18 of the server 10. To do.

  Next, processing in the present embodiment will be described in detail along the flowcharts of FIGS. 6, 8, and 14 with reference to other drawings as appropriate. In the following, processing for registering part data in the parts table DBs 30A, 30B,... And the business-specific product number DB 34 (registration processing), and processing for storing the integrated product number in the business-specific product number DB 34 and the integrated product number DB 36 (integrated product number assignment) Process), a process (search process) for searching for a part number assigned to the same part in another department from information on a part number or item of a certain department will be described.

(registration process)
This process is a process of registering the part data input by the user of each department on the client 70 in the parts table DBs 30A, 30B,. This process is executed according to the flowchart of FIG.

  In the process of FIG. 6, first, in step S10, the parts table registration unit 12 stands by until a registration screen display request is made. In this case, when a user in a certain department inputs a registration screen display request on the client 70, the determination in step S10 is affirmed, and the parts table registration unit 12 proceeds to step S12. It is assumed that the user designates which product part is to be registered when inputting the registration screen display request.

  In step S12, the parts table registration unit 12 displays a registration screen. Specifically, the parts table registration unit 12 transmits registration screen data to the display processing unit 60 of the client 70, and the display processing unit 60 displays a registration screen (see FIG. 7A) on the display unit 193. indicate.

  In step S14, the parts table registration unit 12 stands by until a registration request is made. That is, the process waits until the user presses the registration button on the registration screen (FIG. 7A). Here, in the registration screen, when a department (a department to which the user belongs) is input (or selected) by the user, input items other than “department” and “product number” are displayed. That is, as shown in FIG. 7B, when “design department” is input (or selected) as “department”, the field names “name”, “quantity”, “weight” of the parts table DB 30A of the design department are entered. "," Category "is automatically displayed. Further, as shown in FIG. 7C, when “Procurement Department” is input as “Department”, the field names “Product Name”, “QTY”, “Manufacturer”, “Price” of the parts list DB 30B of the procurement department are entered. "Is automatically displayed.

  When the input to each item by the user is completed and the registration button is pressed, the determination in step S14 is affirmed, and the parts table registration unit 12 proceeds to step S16. At this stage, the input processing unit 62 of the client 70 transmits the data input on the registration screen to the parts table registration unit 12. In step S16, the parts table registration unit 12 registers the data input on the registration screen in the parts table DB of the corresponding department and the corresponding product.

  Next, in step S18, the business-specific product number DB registration unit 14 registers the data input on the registration screen in the business-specific product number DB 34 of the corresponding product. In this case, the business-specific product number DB registration unit 14 refers to the mapping table 32 shown in FIG. 5A and registers data input by the user in the corresponding field of the business-specific product number DB 34. The “integration” field of the business-specific product number DB 34 is empty.

  Thus, the registration process of FIG. 6 ends.

(Integrated part number assignment process)
Next, the integrated product number assigning process will be described. This process is a process for assigning an integrated part number to the same part among the parts registered in the business-specific part number DB 34. This process is executed according to the flowchart of FIG.

  In the process of FIG. 8, first, in step S30, the integrated product number registration unit 16 waits until an integrated screen display request is transmitted from the input processing unit 62 of the client 70 used by the administrator who manages the system. In this case, when the administrator inputs an integrated screen display request via the input unit 195 of the client 70, the determination in step S30 is affirmed, and the integrated product number registration unit 16 proceeds to step S32. Note that the administrator designates which product is to be processed when inputting the integrated screen display request.

  In step S32, the integrated product number registration unit 16 displays an integrated screen. Specifically, the integrated product number registration unit 16 transmits the data of the integrated screen to the display processing unit 60 of the client 70, and the display processing unit 60 displays the integrated screen (see FIG. 9A) on the display unit 193. indicate. In the integrated screen of FIG. 9A, a combination of a plurality of departments and product numbers can be selected. Note that, when selecting a combination of a plurality of departments and product numbers, the administrator presses a downward triangle button provided in a department or product number input field on the integrated screen. In this case, the integrated product number registration unit 16 does not have a department name (data in the field of “department”) registered in the business-specific product number DB 34 or a product number corresponding to the department selected by the administrator (integrated product number is not assigned). (Part number) option is displayed.

  Next, in step S34, the integrated product number registration unit 16 waits until a plurality of product numbers are selected on the integrated screen and the downward triangle button of the integrated product number input field is pressed. That is, as shown in FIG. 9B, when the department selects a plurality of departments and product numbers and presses the downward triangle button of the integrated product number input field, the integrated product number registration unit 16 proceeds to step S36. . Here, it is assumed that data as shown in FIG. 10 is stored in the business-specific product number DB 34 when the process proceeds to step S36. That is, E1 and S3 are used as integrated product numbers, and product numbers E1, S1, and G2 are associated with integrated product number E1, and product numbers E2, S3, and G5 are associated with integrated product number S3. .

  In step S36, the integrated product number registration unit 16 identifies the product number that is already used as the integrated product number and the product number that is already associated with the integrated product number among the selected product numbers. In the case of FIG. 9B, since the product numbers S3, S8, and G6 are selected, the product number S3 that is already used as the integrated product number is specified.

  Next, in step S38, the integrated product number registration unit 16 displays options for the specified product number and other product numbers in a different manner (differentiated). Specifically, as shown in FIG. 11A, the product number S3 and the product numbers S8 and G6 are displayed in different modes. In FIG. 11A, the product number S3 is displayed smaller, the product numbers S8 and G6 are displayed larger, and the word “recommended” is also added. However, the present invention is not limited to this. For example, the product number S3 and the product numbers S8 and G6 may be displayed in different colors, the product number S3 may be displayed lightly, and the product numbers S8 and G6 may be displayed darkly. Alternatively, the product number S3 may be displayed in a non-selectable state, and the product numbers S8 and G6 may be displayed in a selectable state. This makes it easier for the administrator to specify the part number that should be selected as the integrated part number (the part number that has not yet been used as the integrated part number), so the administrator must select the integrated part number appropriately. Is possible.

  Next, in step S40, the integrated product number registration unit 16 waits until any product number is selected and a registration request is made. That is, when the administrator selects the integrated product number on the integrated screen and presses the registration button, the process proceeds to step S42. Here, as shown in FIG. 11B, it is assumed that the administrator selects “G6” as the integrated product number.

  In step S42, the integrated product number registration unit 16 stores the selected product number as an integrated product number in the integrated product number DB 36. Specifically, the integrated product number registration unit 16 adds the newly selected integrated product number “G6” to the integrated product number DB 36 as shown in FIG.

  Next, in step S44, the integrated product number registration unit 16 stores the selected product number as an integrated product number in the integration field of the business-specific product number DB 34. Specifically, as shown in FIG. 12B, the integrated product number registration unit 16 newly selects the integrated product number “in the“ integrated ”field corresponding to the product numbers S3, S8, and G6 of the business-specific product number DB 34. G6 "is stored.

  Thus, the integrated product number assigning process in FIG. 8 ends.

  As shown in FIG. 13, it is assumed that the product number G5 of the design department, the product number S7 of the procurement department, and the product number S3 of the quality assurance department are selected on the integrated screen. In this case, in step S36 of FIG. 8, the product number S3 already used as the integrated product number is specified from FIG. 12, and the product number G5 already associated with the integrated product number is specified. In step S38, the integrated product number registration unit 16 displays the product numbers G5 and S3 and the product number S7 separately (in a different manner) as shown in FIG. This makes it easier for the administrator to specify the part number to be selected as the integrated part number (part number that has not yet been used as an integrated part number, or part number that has not yet been associated with the integrated part number). It becomes possible to select appropriately. Note that the product number (characteristic product number) appropriate for representing the combination of the product numbers selected by the administrator is not recommended because the product number (G5) already associated with the integrated product number is not recommended as the integrated product number. Can be adopted as.

(Search process)
Next, the search process will be described. This process is a process of searching for a part number assigned to the same part in another department from information on a part number or item of a certain department. This process is executed according to the flowchart of FIG.

  As a premise of this processing, for example, it is assumed that the procurement department has received a notification from a supplier that a part of a certain product number (here, S8) is being produced. Assume that the procurement department wants to contact the design department with information that the part will be discontinued.

  In the process of FIG. 14, first, in step S <b> 50, the search unit 18 stands by until there is a search screen display request. In this case, when a user in the procurement department inputs a search screen display request via the input unit 195 of the client 70, the determination in step S50 is affirmed, and the search unit 18 proceeds to step S52. It is assumed that the user specifies which product is to be searched when inputting the search screen display request.

  In step S52, the search unit 18 displays a search screen. Specifically, the search unit 18 transmits search screen data to the display processing unit 60 of the client 70, and the display processing unit 60 displays the search screen (see FIG. 15A) on the display unit 193. . In the search screen of FIG. 15A, the “affiliation department” of the user to be searched, “article number” or “item” used in the department, and “other department” (the department for which the corresponding article number is to be searched) This is a screen where the user can search by inputting.

  Next, in step S54, the search unit 18 waits until the user inputs the department name and product number or item and other department fields on the search screen and presses the search button. When the user inputs as shown in FIG. 15B and presses the search button, the search unit 18 proceeds to step S56.

  In step S56, the search unit 18 acquires the input department name and the integrated product number corresponding to the product number or item in the business-specific product number DB 34 corresponding to the designated product. 12B, “G6” is acquired as the integrated product number corresponding to the department name “Procurement Department” and the product number “G8”.

  Next, in step S58, the search unit 18 acquires a product number of another department corresponding to the acquired integrated product number in the business-specific product number DB 34 corresponding to the designated product. That is, the product number “S3” is acquired from FIG. 12B as the product number of the other department “design department” corresponding to the integrated product number “G6” acquired in step S56.

  In step S60, the search unit 18 displays the acquired product number (and product). Specifically, the search unit 18 transmits the data of the search result screen to the display processing unit 60 of the client 70, and the display processing unit 60 displays the search result screen (see FIG. 15C) on the display unit 193. indicate. In the search result screen of FIG. 15C, the search result that the product number “S3” (and the item “Button-1”) is assigned in the design department to the part of the product number “S8” in the procurement department. Is displayed. Therefore, the user of the procurement department can notify the design department that the part of the product number “S3” is finished production.

  Thus, the search process ends.

  As can be seen from the above description, in the present embodiment, when the integrated part number registration unit 16 selects a plurality of part numbers given in a plurality of parts table DBs for the same part, among the plurality of part numbers The function of the specific part that identifies the part number that is already used as the integrated part number and the part number that is already associated with the integrated part number, and the display part that distinguishes and displays the identified part number and other part numbers It has been realized.

  As described above in detail, according to the present embodiment, when the same parts managed in each of the plurality of parts table DBs 30A, 30B,... When a plurality of product numbers assigned in a plurality of parts table DBs are selected (S34: Yes), a product number already used as an integrated product number among a plurality of product numbers, a product number already associated with the integrated product number, Is identified (S36), and the identified product number and other product numbers are displayed separately (S38). Here, if a product number that is already used as an integrated product number is used as an integrated product number of another component, a problem in component management occurs. Further, the product number already associated with the integrated product number is not a product number (characteristic product number) appropriate for representing a part. For this reason, as shown in this embodiment, by displaying the product numbers that can be used as integrated product numbers and other product numbers in an easy-to-identify manner, the administrator can easily identify product numbers that can be candidates for integrated product numbers. can do.

  In this embodiment, since the same part is managed using the integrated part number, for example, by contacting the part to each department using the integrated part number in the integrated part number DB 36, the communication to each department is performed. It is possible to improve efficiency. Each department may search the product number used in its department in the business-specific product number DB 34 by using the integrated product number.

  In the present embodiment, the business-specific product number DB 34 has only fields corresponding to a part of the fields of the parts table DBs 30A, 30B,..., So that the data amount of the business-specific product number DB 34 is increased. It can be suppressed.

  In this embodiment, since the display mode of the product number that can be used as the integrated product number and the other product numbers are different in FIGS. 11A and 13, the administrator intuitively selects the integrated product number candidate. The product number to be specified can be specified.

  In the above embodiment, as shown in FIG. 11A, the case has been described in which the display mode of the options is changed when the downward triangle button of the integrated product number is pressed on the integrated screen, but the present invention is not limited to this. It is not a thing. For example, the display of each product number may be made different when a department and a product number are selected on the integrated screen of FIG. Even in this case, the administrator can easily specify the product numbers that can be candidates for the integrated product number.

  In the above embodiment, the case where the mapping table 32 is created in advance by the administrator has been described. However, the present invention is not limited to this. For example, the mapping table 32 may be automatically created by automatically acquiring the fields of the parts table DB corresponding to the fields of the business-specific product number DB 34.

  In the above-described embodiment, the case where the data management system 100 is used for data management related to components has been described. However, the present invention is not limited to this. The data management system 100 may be used for data management related to other objects.

  The above processing functions can be realized by a computer. In that case, a program describing the processing contents of the functions that the processing apparatus should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing contents can be recorded on a computer-readable recording medium (except for a carrier wave).

  When the program is distributed, for example, it is sold in the form of a portable recording medium such as a DVD (Digital Versatile Disc) or a CD-ROM (Compact Disc Read Only Memory) on which the program is recorded. It is also possible to store the program in a storage device of a server computer and transfer the program from the server computer to another computer via a network.

  The computer that executes the program stores, for example, the program recorded on the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. Further, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

  The above-described embodiment is an example of a preferred embodiment of the present invention. However, the present invention is not limited to this, and various modifications can be made without departing from the scope of the present invention.

In addition, the following additional remarks are disclosed regarding description of the above embodiment.
(Supplementary Note 1) A data management program for managing the same object managed in each of a plurality of databases using unified identification information,
When a plurality of identification information assigned to the same target in the plurality of databases is selected, the identification information already used as the unified identification information among the plurality of identification information is associated with the unified identification information. Identifying identification information,
The data management program which makes a computer perform the process which distinguishes and displays the said identified identification information and other identification information.
(Supplementary note 2) The data management program according to supplementary note 1, wherein in the process of displaying, the identification information identified in the identifying process and other identification information are displayed in different modes.
(Supplementary Note 3) In the display process, the identification information specified in the specifying process is displayed in a form that cannot be selected as new unified identification information, and the other identification information can be selected as new unified identification information. The data management program according to appendix 2, characterized by:
(Supplementary Note 4) A data management method for managing the same object managed in each of a plurality of databases using unified identification information,
When a plurality of identification information assigned to the same target in the plurality of databases is selected, the identification information already used as the unified identification information among the plurality of identification information is associated with the unified identification information. Identifying identification information that is provided, and
A data management method, wherein the computer executes the step of distinguishing and displaying the identified identification information and other identification information.
(Supplementary note 5) The data management method according to supplementary note 4, wherein in the displaying step, the identification information identified in the identifying step and other identification information are displayed in different modes.
(Appendix 6) In the displaying step, the identification information identified in the identifying step is displayed in a mode that cannot be selected as new unified identification information, and the other identification information can be selected as new unified identification information The data management method according to appendix 5, wherein the data management method is displayed.
(Appendix 7) A data management apparatus for managing the same object managed in each of a plurality of databases using unified identification information,
When a plurality of identification information assigned to the same target in the plurality of databases is selected, the identification information already used as the unified identification information among the plurality of identification information is associated with the unified identification information. A identifying unit that identifies the identification information
A data management device comprising: a display unit that distinguishes and displays the identified identification information and other identification information.
(Additional remark 8) The said display part displays the identification information which the said specific part specified, and other identification information in a different aspect, The data management apparatus of Additional remark 7 characterized by the above-mentioned.
(Additional remark 9) The said display part displays the said identification information which the said specific part specified in the aspect which cannot be selected as new unified identification information, and displays the said other identification information in the aspect which can be selected as new unified identification information The data management device according to appendix 8, characterized by:

10 server (data management device)
16 Integrated part number registration part (specific part, display part)
30A, 30B, 30C Parts list DB (database)
90 CPU (computer)

Claims (5)

A data management program for managing the same object managed in each of a plurality of databases using unified identification information,
When a plurality of identification information assigned to the same target in the plurality of databases is selected, the identification information already used as the unified identification information among the plurality of identification information is associated with the unified identification information. Identifying identification information,
The data management program which makes a computer perform the process which distinguishes and displays the said identified identification information and other identification information.   The data management program according to claim 1, wherein the display process displays the identification information specified in the specifying process and other identification information in different modes.   In the process of displaying, the identification information specified in the specifying process is displayed in a mode that cannot be selected as new unified identification information, and the other identification information is displayed in a mode that can be selected as new unified identification information. The data management program according to claim 2. A data management method for managing the same object managed in each of a plurality of databases using unified identification information,
When a plurality of identification information assigned to the same target in the plurality of databases is selected, the identification information already used as the unified identification information among the plurality of identification information is associated with the unified identification information. Identifying identification information that is provided, and
A data management method, wherein the computer executes the step of distinguishing and displaying the identified identification information and other identification information. A data management device for managing the same object managed in each of a plurality of databases using unified identification information,
When a plurality of identification information assigned to the same target in the plurality of databases is selected, the identification information already used as the unified identification information among the plurality of identification information is associated with the unified identification information. A identifying unit that identifies the identification information
A data management device comprising: a display unit that distinguishes and displays the identified identification information and other identification information.

Images