Methods, devices, electronic equipment, and media for querying material status

Abstract

This application relates to the field of data processing technology, and provides a method, apparatus, electronic device, and medium for querying material status. The method includes: carrying a target object identification code or material identification code of the material to be queried in a status query request; querying the determined material identification code in a first material table; using the material identification code as a query index, querying a second material table to determine the association between the material identification code and the material status; and obtaining the material status query result for the material to be queried. In this way, by using the material identification code as the hub for cross-table association, automatic table join queries between the first and second material tables are realized. This application can shorten the time consumed in a single query, improve the efficiency of material status query, and enhance the accuracy of data query.

Description

Technical Field

[0001] This application belongs to the field of data processing technology, and in particular relates to a method, apparatus, electronic device and medium for querying the status of materials. Background Technology

[0002] With the rapid development of information technology and the electronics manufacturing industry, the research and development and production processes of electronic products have become increasingly complex. In the supply chain management and production preparation stages of modern electronics manufacturing enterprises, the verification of electronic materials is a crucial and fundamental task. For example, in the manufacturing process of personal computers, servers, or smart terminals, it is necessary to confirm whether various electronic materials, such as solid-state drives, memory modules, and camera modules, are in a specific business condition that allows for mass production.

[0003] However, the key information of various electronic materials is not centrally stored in a single system, but is scattered in local ultra-large-scale spreadsheets. Faced with massive data matrices, when querying the status of materials, business personnel need to frequently drag scroll bars, switch table views and perform high-intensity visual searches, resulting in long query times and low overall business efficiency and accuracy. Summary of the Invention

[0004] In view of the shortcomings of the prior art, this application provides a method, apparatus, electronic device and medium for querying material status, which solves the problems of long query time and low overall business efficiency and accuracy when querying material status in related technologies.

[0005] Firstly, this application provides a method for querying the status of materials, including: Receive a status query request triggered by a user, wherein the status query request carries a query code for the material to be queried, and the query code is either a target object identification code or a material identification code; Based on the query code, the first association is queried in the first material table, where the first association represents the association between the material model, the target object identification code, and the material identification code; In response to the material identifier code to be queried determined based on the first association relationship, the second association relationship is queried in the second material table using the material identifier code as the query index; wherein the second association relationship represents the association relationship between the material identifier code and the material status. Based on the first and second association relationships, determine the material status query results for the material to be queried.

[0006] In one embodiment of this application, before receiving a status query request triggered by a user, the method further includes: When the executable program starts, it loads a pre-set first material table and a second material table, wherein the first material table and the second material table are pre-stored in the target storage path where the executable program is located; it then retrieves data from the loaded first material table and data from the loaded second material table.

[0007] In one embodiment of this application, querying a first association relationship in a first material table based on a query code includes: If the query code is a target object identification code, then the material identification code in the first material table that is associated with the target object identification code is determined as the material identification code to be queried, and the material model corresponding to the target object identification code is also extracted; if the query code is a material identification code, then the target object identification code and the material model that are associated with the material identification code in the first material table are extracted together.

[0008] In one embodiment of this application, before determining the material status query result of the material to be queried based on the first association relationship and the second association relationship, the method further includes: Obtain at least one preset configuration file, which is in Extensible Markup Language (EXPLAIN) format; determine whether the target object identification code exists in at least one configuration file; based on the determination result, generate confirmation information to characterize the existence status of the target object identification code in the configuration file; and incorporate the confirmation information into the material status query results.

[0009] In one embodiment of this application, the material status includes at least one of quality qualified confirmation status, abandoned status, or under investigation status; the first material table is a program matrix table corresponding to the target model, and the second material table is a hardware matrix table corresponding to the target model; the target object identification code is an identification code in the format XXXXXAV, where XXXXX is any combination of uppercase letters and numbers, and the material identification code is an identification code in the format xxxxxx-xxx, where xxxxxx-xxx is any combination of letters and numbers.

[0010] In one embodiment of this application, after determining the material status query result of the material to be queried, the method further includes: The query results are visualized on the user interface; the query results include the material model, target object identification code, the relationship between the material identification code and the material status, and the row and column positioning information of the material model, target object identification code, material identification code and material status in the first material table and the second material table.

[0011] Secondly, this application also provides a material status query device, comprising: The request receiving module is configured to receive status query requests triggered by users, wherein the status query request carries a query code for the material to be queried, and the query code is either a target object identification code or a material identification code. The first query module is configured to query the first association relationship in the first material table based on the query code, wherein the first association relationship represents the association relationship between the material model, the target object identification code and the material identification code; The second query module is configured to, in response to the material identifier code to be queried determined according to the first association relationship, use the material identifier code to be queried as the query index to query the second association relationship in the second material table; wherein the second association relationship represents the association relationship between the material identifier code and the material status. The status determination module is configured to determine the material status query result of the material to be queried based on the first association relationship and the second association relationship.

[0012] Thirdly, this application also provides an electronic device, including: one or more processors and a memory, wherein a computer program is stored in the memory, and when the one or more processors execute the computer program, the electronic device performs the steps of the above-described material status query method.

[0013] Fourthly, the present invention also provides a computer-readable storage medium comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, when the processor executes the computer program, the computer-readable storage medium implements the steps of the above-described material status query method.

[0014] The beneficial effects of this technical solution are as follows: the status query request carries either the target object identification code or the material identification code of the material to be queried; the determined material identification code to be queried is queried in the first material table; the material identification code to be queried is used as the query index to query the association between the material identification code and the material status in the second material table; and the material status query result of the material to be queried is obtained.

[0015] Specifically, in the status query request provided in this application, the query code can be flexibly configured as either a target object identification code or a material identification code. Compared with existing technologies that only support join table queries with a single fixed keyword type, this application establishes a bidirectional, peer-to-peer query triggering mechanism. Regardless of whether the user has a target object identification code or a material identification code, they can directly initiate a query without additional information conversion or preprocessing, significantly improving the adaptability of the query method to different business scenarios and the convenience of user operation.

[0016] Secondly, this application pre-builds and stores the complete association between material model, target object identification code, and material identifier code in the first material table, making the first material table a two-way mapping hub: it can find the corresponding material identifier code and material model through the target object identification code, and it can also trace back to the target object identification code and material model through the material identifier code. Based on this, using the query code as the entry point, the material identifier code is determined through the first material table, and then the material identifier code is used as a cross-table association index to query the material status in the second material table, thereby realizing automatic and accurate table join queries between the two tables. This design avoids errors such as misreading or misaligning rows caused by manual visual retrieval in massive spreadsheets in existing technologies. At the same time, compared with the solution of pre-merging all fields into a new persistent intermediate table, this application does not need to create and maintain an additional permanently stored intermediate data table, and directly queries based on the original table, reducing the storage occupation of redundant data from the source and lowering the cost of data storage and maintenance.

[0017] Finally, for ultra-large-scale material tables (such as program matrix tables and hardware matrix tables containing tens of thousands of rows and dozens of columns) in actual business operations in the electronics manufacturing field, this application achieves extremely high data access speed at runtime by fully loading the first and second material tables into memory when the executable program starts, and directly using the material identification code as the query index for fast matching in memory. This reduces the time taken for a single material status query from several minutes in traditional manual retrieval to seconds or even milliseconds, significantly improving the efficiency and accuracy of material status queries and providing reliable technical support for material compliance verification during the production preparation stage.

[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings: Figure 1 This is a schematic flowchart illustrating a method for querying material status, as shown in an exemplary embodiment of this application. Figure 2 This is a schematic diagram illustrating the structure of a material status query device according to an exemplary embodiment of this application; Figure 3 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Detailed Implementation

[0020] The embodiments of this application will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be understood that the preferred embodiments are only for illustrating this application and are not intended to limit the scope of protection of this application.

[0021] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of this application. Therefore, the drawings only show the components related to this application and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the shape, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0022] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the present application. However, it will be apparent to those skilled in the art that embodiments of the present application may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the present application.

[0023] Before describing the specific implementation methods of this application in detail, some technical terms and custom concepts involved in this application will be explained and described in order to enable those skilled in the art to accurately understand the technical solutions of this application.

[0024] First Material Table: A two-dimensional data matrix recording the hierarchical relationship and configuration information between a specific equipment model and its constituent target object identification codes and corresponding material identification codes. In this application, the first material table stores the association relationship between the material model, target object identification code, and material identification code.

[0025] The second material table is a two-dimensional data matrix that records the material identification codes and their corresponding underlying hardware attributes, such as material status, across the entire scope. In this application, the second material table stores the association between material identification codes and material status.

[0026] Target object identification code: Encoded information used to uniquely identify a specific assembly variant or set of components.

[0027] Material identification code: A unique identification code assigned by the enterprise to each specific electronic component according to specific rules.

[0028] Material Status: A specific business node identifier for electronic materials in lifecycle management and compliance verification, used to indicate whether the material is currently permitted to be used for mass production, whether it has been discarded, or whether it is under investigation.

[0029] With the increasing sophistication of the electronics manufacturing industry, bill of materials (BOM) verification and compliance checks of electronic materials have become core aspects of the production preparation phase. In practice, business personnel need to confirm whether materials for specific models are ready for mass production. However, this crucial information is scattered across massive local spreadsheets. In traditional operations, personnel must simultaneously open both the Program Matrix and Hardware Matrix spreadsheets, performing intensive visual searches and cross-spreadsheet comparisons across tens of thousands of rows and columns. This purely manual approach has serious technical drawbacks: firstly, frequent scrolling and view switching lead to extremely long query times and overall low efficiency; secondly, the human eye is prone to fatigue with massive amounts of data, resulting in misreading or misplacing rows, compromising data accuracy. Furthermore, manual queries lack system-level logging, making it impossible to trace back compliance issues afterward.

[0030] To overcome the shortcomings of the existing technology, this application provides a method, apparatus, electronic device, and medium for querying material status. This method replaces manual visual retrieval by using a low-level memory-level data loading and material identification code mapping mechanism, achieving rapid and accurate cross-table data association and improving overall business efficiency and accuracy.

[0031] Please see Figure 1 , Figure 1 This is a flowchart illustrating a method for querying material status, as shown in an exemplary embodiment of this application. Figure 1 As shown, in an exemplary embodiment, the method for querying the material status includes steps S110 to S140, and each step is described in detail below.

[0032] S110, receives a status query request triggered by the user; Specifically, if a user needs to query the status of a certain material, they can enter the corresponding status query request in the front-end query interface. The status query request carries the query code of the material to be queried, which is either the target object identification code or the material identification code. In actual business operations, the known conditions possessed by business personnel are often dynamically changing. Sometimes business personnel only know the target object identifier code, and sometimes they only know the material identifier code. If the system only supports single-dimensional query triggers, it will not be able to meet the query needs under different business scenarios. Therefore, this application supports both the target object identifier code query method and the material identifier code query method.

[0033] For example, the front-end query interface provides a first query entry based on the target object identifier code and a second query entry based on the material identifier code. When a user knows the target object identifier code, they can directly enter the corresponding information to initiate a query at the first query entry; if they only know the material identifier code, they can enter information through the second query entry to trigger a query.

[0034] In addition, the system also receives strings input by users through a front-end interactive interface. Then, it automatically determines whether the input string is a target object identifier code or a material identifier code using regular expressions or string length features, and then executes the corresponding query logic based on the determination result.

[0035] In some embodiments, before receiving a user-triggered status query request, the method further includes: When the executable program starts, it loads the preset first material table and second material table, retrieves the data from the loaded first material table, and retrieves the data from the loaded second material table.

[0036] The first and second material tables are pre-stored in the target storage path where the executable program is located; Specifically, after the executable program starts, it can automatically read the first and second material table files that have been pre-organized and saved from the preset target storage path, load the full data of the two tables into the local memory, and then extract the association information between the equipment model, target object identification code and material identification code from the first spreadsheet; at the same time, it extracts the association information between the material identification code and the material status from the second material table.

[0037] This allows subsequent queries to directly read data from memory for matching, eliminating the need to repeatedly call the file read interface. This significantly improves query response speed, avoids latency caused by frequent disk reads and writes, and meets the need for rapid material status queries in business scenarios.

[0038] S120, based on the query code, query the first relationship in the first material table; The first association relationship represents the association between the material model, the target object identification code, and the material identification code; Specifically, the first material table pre-stores at least one record, each record including at least: a material model field, a target object identification code field, and a material identifier code field. The material model is used to characterize the equipment model to which the material belongs (e.g., a certain model of laptop or a certain model of server); the target object identification code is used to identify a type of material model or material group; the material identifier code is used to uniquely identify a specific material. In the first material table, one target object identification code corresponds to one material model and one or more material identifier codes; one material identifier code uniquely corresponds to one target object identification code and one material model.

[0039] In some embodiments, querying a first association in a first material table based on a query code includes: If the query code is a target object identification code, then the material identification code in the first material table that is associated with the target object identification code is determined as the material identification code to be queried, and the material model corresponding to the target object identification code is also extracted; if the query code is a material identification code, then the target object identification code and the material model that are associated with the material identification code in the first material table are extracted together.

[0040] This step executes the corresponding query logic based on the specific type of the received query code: If the query code is a target object identification code, then search the first material table for all material identification codes and corresponding material models that are associated with that target object identification code; if the query code is a material identification code, then search the first material table for the target object identification code and material model that are associated with that material identification code. If the query code cannot be matched with any record in the first material table, a no-match message is generated and the query process is terminated.

[0041] In this way, through bidirectional query logic, this application can adapt to the different query conditions that business personnel have in different scenarios, without requiring users to perform additional format conversion or preprocessing, further improving the convenience of querying and the universality of the method.

[0042] S130, in response to the material identification code to be queried determined according to the first association, the second association is queried in the second material table using the material identification code to be queried as the query index.

[0043] The second association relationship represents the association between the material identification code and the material status.

[0044] Specifically, the second material table pre-stores at least one record, each record including at least a material identifier field and a material status field. The material identifier uses the same encoding rule as the material identifier in the first material table, thus serving as a link between the two tables. In the second material table, each material identifier uniquely corresponds to one material status.

[0045] This step responds to the material identifier code to be queried determined based on the first association relationship, and uses the material identifier code to be queried as a query index to perform a matching query in the second material table to extract the material status information corresponding to the material identifier code.

[0046] If the material identifier code to be queried cannot be matched with any record in the second material table, a status missing prompt message can be generated and included in the subsequent material status query results to remind the user that the material identifier code has not been configured with a material status.

[0047] S140, determine the material status query result of the material to be queried based on the first association relationship and the second association relationship.

[0048] Specifically, the system integrates and correlates the first and second relationships to generate a complete material status query result. The query result includes at least: material model, target object identification code, material identifier code, and material status.

[0049] In some embodiments, before determining the material status query result of the material to be queried based on the first association relationship and the second association relationship, the method further includes: Obtain at least one preset configuration file, which is in Extensible Markup Language (EXPLAIN) format; determine whether the target object identification code exists in at least one configuration file; based on the determination result, generate confirmation information to characterize the existence status of the target object identification code in the configuration file; and incorporate the confirmation information into the material status query results.

[0050] For example, in the product development and production process, there exists a set (e.g., 7) of configuration files in Extensible Markup Language (XML) format. These files are the actual instruction files that drive the hardware. Only when the target object identifier of the material is correctly written into these configuration files can the operating system or driver truly recognize and invoke the material.

[0051] Specifically, the system reads the contents of each configuration file, compares the target object identification code determined in step S120 with the material identification field in the configuration file one by one, and determines whether the target object identification code appears in each configuration file.

[0052] If the target object identifier exists in all configuration files, the received information is confirmed as fully added; if it exists in some configuration files, the received information is confirmed as partially added; if it does not exist in any configuration file, the received information is confirmed as not added or missing.

[0053] In this way, the final material status query results not only include the material status at the table level (such as the quality conformity confirmation status), but also the effective status at the configuration level (such as the existence status in the configuration file). This ensures that materials marked as complete in the table have actually taken effect in the actual control code, thereby improving the accuracy and reliability of configuration from R&D to production transition.

[0054] In some embodiments, the material status includes at least one of quality qualified confirmation status, abandoned status, or under investigation status; the first material table is a program matrix table corresponding to the target model, and the second material table is a hardware matrix table corresponding to the target model; the target object identification code is an identification code in the format XXXXXAV, where XXXXX is any combination of uppercase letters and numbers, and the material identification code is an identification code in the format xxxxxx-xxx, where xxxxxx-xxx is any combination of letters and numbers.

[0055] The Q-Complete status indicates that the material has completed all quality verification procedures and is qualified, and is allowed to be used for mass production; the Dropped status indicates that the material has been discarded and is no longer used; and the Investigating status indicates that the material is undergoing further verification or investigation and is not recommended for mass production at this time.

[0056] In practical applications, Program Matrix tables are used to store the correspondence between identification codes in XXXXXAV format and identifier codes in xxxxxx-xxx format, typically containing more than 13,000 rows and 48 columns of data; Hardware Matrix tables are used to store the correspondence between identifier codes in xxxxxx-xxx format and material status, typically containing more than 3,300 rows and 75 columns of data. The method in this application is specifically designed to address the query needs of these ultra-large-scale spreadsheets.

[0057] The XXXXXAV format identification code (abbreviated as AV code) is used to uniquely identify a type of material model or material group, where XXXXX is any combination of uppercase letters and numbers, for example, AD3H8, H5J6T; the xxxxxx-xxx format identification code (abbreviated as 6-3 code) is used to uniquely identify a specific material instance, where xxxxxx-xxx is any combination of letters and numbers, for example, A12cb4-36b, aAB526-ASD. One xxxxxx-xxx format identification code corresponds to one or more xxxxxx-xxx format identification codes, and the xxxxxx-xxx format identification code is stored simultaneously in the first material table and the second material table, used as a field for association query between the two tables.

[0058] According to the technical solution provided in the embodiments of this application, the status query request carries either a target object identification code or a material identification code of the material to be queried; the determined material identification code to be queried is queried in the first material table; using the material identification code to be queried as a query index, the association relationship between the material identification code and the material status is queried in the second material table; thus, the material status query result of the material to be queried is obtained. In this way, by using the material identification code as the hub for cross-table association, automatic table join query of the first and second material tables can be realized, which can significantly shorten the time of a single query; at the same time, it avoids errors such as misreading or misaligning rows that may occur based on visual retrieval, and there is no need to build an intermediate table to store all related data, reducing the storage occupation of redundant data, lowering the cost of data storage and maintenance, and improving the efficiency and accuracy of material status query.

[0059] In some embodiments, after determining the material status query result of the material to be queried, the method further includes: The query results are visualized on the user interface; the query results include the material model, target object identification code, the relationship between the material identification code and the material status, and the row and column positioning information of the material model, target object identification code, material identification code and material status in the first material table and the second material table.

[0060] Specifically, the system's front-end query interface includes an input interface and a display interface. The input interface receives status query requests triggered by users; the display interface outputs the material status query results in a visual format.

[0061] The query results include the following: the relationship between material model, target object identification code, material identifier code, and material status. Users can see the complete data chain from the query code, through the material identifier code, to the material status on the interface.

[0062] Row and column location information: This information indicates the row and column location of the material model, target object identification code, material identifier code, and material status in the first and second material tables. This information indicates the specific row and column number of the data entry in the original spreadsheet file, allowing users to easily refer back to the original table for verification or auditing when needed.

[0063] With the above visualization, users no longer need to manually browse through massive amounts of raw table data to intuitively obtain the complete status information of the material to be queried, significantly improving the user experience.

[0064] In some embodiments, after visualizing the query results on the user interface, the method further includes: in response to an export command triggered by the user, exporting the material status query results to a data storage file in a target format. The target format may include a spreadsheet format (such as xlsx format).

[0065] In this way, users can save query results in batches, which is convenient for future tracing, sharing, or data integration with other business systems.

[0066] In some embodiments, after determining the material status query result of the material to be queried, the method further includes: Obtain the historical state change set of the material, and determine the abandonment transfer confidence level of the material based on the historical state change set. The abandonment transfer confidence level represents the probability that the material will transfer from the state in the survey to the abandoned state. Risk prediction information is generated when the confidence level of abandonment transfer is greater than or equal to the preset risk threshold.

[0067] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0068] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0069] Figure 2 This is a schematic diagram illustrating the structure of a material status query device, as shown in an exemplary embodiment of this application. Figure 2 As shown, the exemplary material status query device includes: The request receiving module 210 is configured to receive a status query request triggered by a user, wherein the status query request carries a query code for the material to be queried, and the query code is either a target object identification code or a material identification code. The first query module 220 is configured to query the first association relationship in the first material table based on the query code, wherein the first association relationship represents the association relationship between the material model, the target object identification code and the material identification code; The second query module 230 is configured to, in response to the material identifier code to be queried determined according to the first association relationship, use the material identifier code to be queried as the query index to query the second association relationship in the second material table; wherein the second association relationship represents the association relationship between the material identifier code and the material status. The status determination module 240 is configured to determine the material status query result of the material to be queried based on the first association relationship and the second association relationship.

[0070] In some embodiments, the request receiving module 210 is further configured to load a preset first material table and a second material table when the executable program starts, wherein the first material table and the second material table are pre-stored in the target storage path where the executable program is located; retrieve data from the loaded first material table; and retrieve data from the loaded second material table.

[0071] In some embodiments, the first query module 220 is further configured to, if the query code is a target object identification code, determine the material identification code in the first material table that is associated with the target object identification code as the material identification code to be queried, and extract the material model corresponding to the target object identification code together; if the query code is a material identification code, extract the target object identification code and the material model in the first material table that are associated with the material identification code together.

[0072] In some embodiments, the first query module 220 is further configured to obtain at least one preset configuration file, the configuration file being in Extensible Markup Language format; determine whether the target object identification code exists in at least one configuration file; generate confirmation information to characterize the existence status of the target object identification code in the configuration file based on the determination result; and incorporate the confirmation information into the material status query result.

[0073] In some embodiments, the first query module 220 is further configured such that the material status includes at least one of quality qualified confirmation status, abandoned status, or under investigation status; the first material table is a program matrix table corresponding to the target model, and the second material table is a hardware matrix table corresponding to the target model; the target object identification code is an identification code in the format XXXXXAV, where XXXXX is any combination of uppercase letters and numbers, and the material identification code is an identification code in the format xxxxxx-xxx, where xxxxxx-xxx is any combination of letters and numbers.

[0074] In some embodiments, the status determination module 240 is further configured to visualize the query results on the user interface; wherein the query results include the material model, the target object identification code, the association between the material identification code and the material status, and the row and column positioning information of the material model, the target object identification code, the material identification code and the material status in the first material table and the second material table.

[0075] According to the apparatus provided in the embodiments of this application, the status query request carries either the target object identification code (AV code) or the material identification code (6-3 code) of the material to be queried; the determined material identification code (6-3 code) to be queried is queried in the first material table; using the material identification code (6-3 code) to be queried as the query index, the association relationship between the material identification code (6-3 code) and the material status is queried in the second material table; thus, the material status query result of the material to be queried is obtained. In this way, by using the material identification code (6-3 code) as the hub for cross-table association, automatic table join query of the first material table and the second material table can be realized, which can significantly shorten the time of a single query; at the same time, it avoids errors such as misreading or misaligning rows that may occur based on visual retrieval, and there is no need to build an intermediate table to store all related data, reducing the storage occupation of redundant data, reducing the cost of data storage and maintenance, and improving the efficiency and accuracy of material status query.

[0076] Embodiments of this application also provide an electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, cause the electronic device to implement the methods provided in the above embodiments.

[0077] Figure 3 A schematic diagram of a computer system suitable for implementing the embodiments of this application is shown. It should be noted that... Figure 3 The computer system 300 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0078] like Figure 3As shown, the computer system 300 includes a Central Processing Unit (CPU) 301, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 302 or programs loaded from storage portion 308 into Random Access Memory (RAM) 303, such as executing the methods described in the above embodiments. The RAM 303 also stores various programs and data required for system operation. The CPU 301, ROM 302, and RAM 303 are interconnected via a bus 304. An Input / Output (I / O) interface 305 is also connected to the bus 304.

[0079] The following components are connected to I / O interface 305: an input section 306 including a keyboard, mouse, etc.; an output section 307 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 308 including a hard disk, etc.; and a communication section 309 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 309 performs communication processing via a network such as the Internet. A drive 310 is also connected to I / O interface 305 as needed. Removable media 311, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 310 as needed so that computer programs read from them can be installed into storage section 308 as needed.

[0080] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 309, and / or installed from removable medium 311. When the computer program is executed by central processing unit (CPU) 301, it performs various functions defined in the system of this application.

[0081] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium, a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0082] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation that may be implemented in systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0083] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0084] Another aspect of this application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a computer's processor, causes the computer to perform the method as described above. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not assembled into the electronic device.

[0085] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods described in the various embodiments above.

[0086] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in this application should still be covered by the steps of this application.

Claims

1. A method for querying the status of materials, characterized in that, include: Receive a status query request triggered by a user, wherein the status query request carries a query code for the material to be queried, and the query code is either a target object identification code or a material identification code; According to the query code, the first association is queried in the first material table, wherein the first association represents the association between the material model, the target object identification code and the material identification code; In response to the material identification code to be queried determined according to the first association relationship, the second association relationship is queried in the second material table using the material identification code to be queried as the query index; wherein the second association relationship represents the association relationship between the material identification code and the material status. Based on the first association relationship and the second association relationship, the material status query result of the material to be queried is determined.

2. The method according to claim 1, characterized in that, Before receiving the status query request triggered by the user, the method further includes: When the executable program starts, the first material table and the second material table are loaded, wherein the first material table and the second material table are pre-stored in the target storage path where the executable program is located; Retrieve data from the first material table after loading, and retrieve data from the second material table after loading.

3. The method according to claim 1, characterized in that, The step of querying the first association relationship in the first material table according to the query code includes: If the query code is a target object identification code, then the material identification code in the first material table that is associated with the target object identification code is determined as the material identification code to be queried, and the material model corresponding to the target object identification code is extracted together; If the query code is a material identification code, then the target object identification code and material model that are associated with the material identification code in the first material table will be extracted together.

4. The method according to claim 1, characterized in that, Before determining the material status query result of the material to be queried based on the first association relationship and the second association relationship, the method further includes: Obtain at least one preset configuration file, wherein the configuration file is in Extensible Markup Language format; Determine whether the target object identification code exists in at least one configuration file; Based on the judgment result, confirmation information is generated to characterize the existence status of the target object identification code in the configuration file; The confirmed receipt information is included in the material status query results.

5. The method according to any one of claims 1-4, characterized in that, The material status includes at least one of the following: quality qualified confirmation status, abandoned status, or under investigation status. The first material table is a program matrix table corresponding to the target model, and the second material table is a hardware matrix table corresponding to the target model; The target object identification code is an identification code in the format of XXXXXAV, where XXXXX is any combination of uppercase letters and numbers. The material identification code is an identification code in the format of xxxxxx-xxx, where xxxxxx-xxx is any combination of letters and numbers.

6. The method according to claim 1, characterized in that, After determining the material status query result of the material to be queried, the method further includes: The query results are then visualized on the user interface. The query results include the material model, the target object identifier, the association between the material identifier and the material status, and the row and column positioning information of the material model, the target object identifier, the material identifier and the material status in the first material table and the second material table.

7. A material status query device, characterized in that, include: The request receiving module is configured to receive a status query request triggered by a user, wherein the status query request carries a query code for the material to be queried, and the query code is one of a target object identification code or a material identification code. The first query module is configured to query a first association relationship in a first material table based on the query code, wherein the first association relationship represents the association relationship between the material model, the target object identification code, and the material identification code; The second query module is configured to, in response to the material identifier code to be queried determined according to the first association relationship, use the material identifier code to be queried as the query index to query the second association relationship in the second material table; wherein the second association relationship represents the association relationship between the material identifier code and the material status. The status determination module is configured to determine the material status query result of the material to be queried based on the first association relationship and the second association relationship.

8. The apparatus according to claim 7, characterized in that, The request receiving module further includes: The loading module is configured to load the first material table and the second material table when the executable program starts, wherein the first material table and the second material table are pre-stored in the target storage path where the executable program is located; The data capture module is configured to capture data from the first material table after loading, and to capture data from the second material table after loading.

9. An electronic device, characterized in that, include: One or more processors and a memory, the memory storing a computer program that, when executed by the one or more processors, causes the electronic device to perform the steps of the material status query method as described in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by one or more processors, causes the device to perform the method as described in any one of claims 1 to 6.

Images