A low-bit code query method, device, equipment and computer-readable storage medium

Abstract

The present invention discloses a method for querying low-level codes, which includes the following steps: parsing the received low-level code query request to obtain the business organization scope corresponding to the low-level code to be queried; obtaining the original low-level code table name carrying the global low-level code results of all business organizations in the business modeling document; determining the target low-level code table name according to the business organization scope and the original low-level code table name; searching for the target low-level code table according to the target low-level code table name; and using the target low-level code table to perform a query operation on the low-level code to be queried. By applying the low-level code query method provided by the present invention, the business decoupling of different organizations is realized, the system availability is improved, the system resource consumption is reduced, the performance is enhanced, and the distributed operation of the material requirements plan in a true sense is realized. The present invention also discloses a low-level code query device, equipment and storage medium, which have corresponding technical effects.

Description

Technical Field

[0001] The present invention relates to the technical field of material management, and particularly to a low-level code query method, device, equipment, computer-readable storage medium, and computer program product. Background Art

[0002] In the existing ERP (Enterprise Resources Planning) system, the low-level code, as the basic data of MRP (Material Requirement Planning), is the prerequisite for MRP calculation. Currently, in the ERP system, there is only one low-level code calculation result under the multi-organization business architecture of an enterprise. Each time the low-level code is calculated, the BOM (Bill of Material) and materials under all organizations need to be included for the low-level code calculation.

[0003] With the development of the enterprise, the number of its organizations is increasing, and the data volume of relevant materials and bills of materials is increasing incrementally. Loading the materials and materials of all organizations for calculation each time will consume a lot of IO (Input / Output) and memory, resulting in low performance.

[0004] In summary, how to effectively solve the problems that the existing low-level code query method cannot decouple engineering data between organizations, consumes IO and memory, and results in low performance is an urgent problem for those skilled in the art at present. Summary of the Invention

[0005] The purpose of the present invention is to provide a low-level code query method, which realizes the decoupling of the businesses of different organizations, improves the availability of the system, reduces IO, improves performance, and realizes the distributed calculation of the material requirement plan in a true sense; another purpose of the present invention is to provide a low-level code query device, equipment, and computer-readable storage medium.

[0006] To solve the above technical problems, the present invention provides the following technical solutions:

[0007] A low-level code query method includes:

[0008] Parsing the received low-level code query request to obtain the business organization scope corresponding to the low-level code to be queried;

[0009] Obtaining the original low-level code table name carrying the global low-level code results of all business organizations in the business modeling document;

[0010] Determining the target low-level code table name according to the business organization scope and the original low-level code table name;

[0011] Locate the target low-level code table according to the name of the target low-level code table;

[0012] Use the target low-level code table to perform a query operation on the low-level code to be queried.

[0013] In a specific embodiment of the present invention, before using the target low-level code table to perform a query operation on the low-level code to be queried, it further includes:

[0014] Screen the target bill of materials data from the business modeling documents according to the scope of the business organization;

[0015] Perform a low-level code operation on the target bill of materials data to obtain a target low-level code result;

[0016] Store the target low-level code result in the target low-level code table.

[0017] In a specific embodiment of the present invention, locating the target low-level code table according to the name of the target low-level code table includes:

[0018] Determine whether there is an existing low-level code table corresponding to the name of the target low-level code table in the database;

[0019] If so, determine the existing low-level code table as the target low-level code table;

[0020] If not, create the target low-level code table according to the name of the target low-level code table.

[0021] In a specific embodiment of the present invention, after determining that there is an existing low-level code table corresponding to the name of the target low-level code table in the database, it further includes:

[0022] Obtain the existing metadata version number corresponding to the existing low-level code in the existing low-level code table;

[0023] Parse the received low-level code query request to obtain the scope of the business organization corresponding to the low-level code to be queried, including:

[0024] Parse the received low-level code query request to obtain the scope of the business organization corresponding to the low-level code to be queried and the target metadata version number;

[0025] Determine whether the existing metadata version number is consistent with the target metadata version number;

[0026] If so, execute the step of determining the existing low-level code table as the target low-level code table;

[0027] If not, obtain the target fields corresponding to the target metadata version number, and create the target low-level code table according to the target fields and the name of the target low-level code table.

[0028] In a specific embodiment of the present invention, after creating the target low-level code table according to the target field and the target low-level code table name, the following steps are further included:

[0029] Perform a deletion operation on the existing low-level code table corresponding to the target low-level code table name in the database;

[0030] Store the target low-level code table and the target metadata version number in the database.

[0031] A low-level code query device includes:

[0032] A request parsing module, configured to parse the received low-level code query request to obtain the business organization scope corresponding to the low-level code to be queried;

[0033] An original low-level code table name acquisition module, configured to acquire the original low-level code table name carrying the global low-level code results of all business organizations in the business modeling document;

[0034] A target low-level code table name determination module, configured to determine the target low-level code table name according to the business organization scope and the original low-level code table name;

[0035] A low-level code table search module, configured to search for the target low-level code table according to the target low-level code table name;

[0036] A low-level code query module, configured to perform a query operation on the low-level code to be queried by using the target low-level code table.

[0037] In a specific embodiment of the present invention, the following steps are further included:

[0038] A bill of materials data screening module, configured to screen target bill of materials data from the business modeling document according to the business organization scope before performing the query operation on the low-level code to be queried by using the target low-level code table;

[0039] A low-level code operation module, configured to perform a low-level code operation on the target bill of materials data to obtain a target low-level code result;

[0040] A low-level code result storage module, configured to store the target low-level code result in the target low-level code table.

[0041] A low-level code query device includes:

[0042] A memory, configured to store a computer program;

[0043] A processor, configured to implement the steps of the low-level code query method as described above when executing the computer program.

[0044] A computer-readable storage medium stores a computer program thereon, and when the computer program is executed by a processor, the steps of the low-order code query method described above are implemented.

[0045] A computer program product includes a computer program, and when the computer program is executed by a processor, the steps of any of the low-order code query methods described above are implemented.

[0046] The low-order code query method provided by the present invention parses the received low-order code query request to obtain the business organization scope corresponding to the low-order code to be queried; obtains the original low-order code table name carrying the global low-order code results of all business organizations in the business modeling document; determines the target low-order code table name according to the business organization scope and the original low-order code table name; searches for the target low-order code table according to the target low-order code table name; and uses the target low-order code table to perform a query operation on the low-order code to be queried.

[0047] As can be seen from the above technical solutions, by pre-defining the original low-order code table name carrying the global low-order code results of all business organizations in the business modeling document, the target low-order code table name of the target low-order code table where the low-order code to be queried is located is determined according to the original low-order code table name and the business organization scope included in the received low-order code query request, the target low-order code table is searched according to the target low-order code table name, and the target low-order code table is used to perform a query operation on the low-order code to be queried. The business decoupling of different organizations is realized, and if there are problems with the bill of materials of individual organizations, it will no longer affect the calculation of the material requirements plan of irrelevant organizations. Different business organization scopes have their own low-order code result tables, and they do not interfere with each other even under high concurrency, improving the system availability. The materials and bills of materials are obtained according to the business organization scope, reducing the consumption of system resources, improving the performance, and realizing the distributed operation of the material requirements plan in a true sense.

[0048] Correspondingly, the present invention also provides a low-order code query device, device, and computer-readable storage medium corresponding to the above low-order code query method, which have the above technical effects and will not be elaborated here. Description of the Drawings

[0049] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present invention, and those of ordinary skill in the art can obtain other drawings without creative efforts based on these drawings.

[0050] Figure 1 It is a flowchart of an implementation of the low-order code query method in an embodiment of the present invention;

[0051] Figure 2Another implementation flowchart of the low-level code query method in the embodiments of the present invention;

[0052] Figure 3 A timing diagram of a low-level code query method in the embodiments of the present invention;

[0053] Figure 4 A structural block diagram of a low-level code query device in the embodiments of the present invention;

[0054] Figure 5 A structural block diagram of a low-level code query device in the embodiments of the present invention;

[0055] Figure 6 A specific structural schematic diagram of a low-level code query device provided in this embodiment. Specific implementation manners

[0056] In order to enable those skilled in the art to better understand the solution of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific implementation manners. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0057] In the current ERP system, there is only one result of low-level code operation under the multi-organization business architecture of an enterprise. Each time low-level code operation is performed, the BOM (Bill of Material) and materials under all organizations need to be included for low-level code operation.

[0058] The inventor found that in actual applications, many organizations of an enterprise do not have production functions, or there is no business interaction between organizations, and their material requirement plans are also calculated separately by organization. Under the existing solution, all organizations are calculated together, and the engineering data decoupling between organizations cannot be achieved. If there is a nested BOM in a certain organization, it will cause all organizations that have checked the automatic calculation of low-level code operation to fail in the MRP calculation and prompt the existence of nesting. It is necessary to notify the business personnel of the problematic organization to correct the BOM under their organization, which brings inconvenience in the process. In addition, the result of low-level code operation only exists in one physical table, and it is easy to cause table deadlocks when multiple organizations perform concurrent low-level code operations, reducing the usability of the function.

[0059] See Figure 1 , Figure 1 An implementation flowchart of a low-level code query method in the embodiments of the present invention. The method may include the following steps:

[0060] S101: Analyze the received low-level code query request to obtain the business organization scope corresponding to the low-level code to be queried.

[0061] When a low-level code query is required, a low-level code query request is sent to the low-level code management center. The low-level code query request contains the business organization scope corresponding to the low-level code to be queried. The low-level code management center receives the low-level code query request and parses the received low-level code query request to obtain the business organization scope corresponding to the low-level code to be queried. For example, the low-level code query request may be a request to query the low-level code corresponding to the tire production quantity, and the business organization scope may be the organization scope composed of Factory A and Factory B.

[0062] S102: Obtain the original low-level code table name that bears the global low-level code results of all business organizations in the business modeling document.

[0063] Create a document of low-level code operation results through the BOS IDE (integration platform). This is the business modeling document. Pre-define the original low-level code table name that bears the global low-level code results of all business organizations in the business modeling document, that is, the static low-level code table name, and define the table field names, field types, etc. After parsing to obtain the business organization scope corresponding to the low-level code to be queried, obtain the original low-level code table name that bears the global low-level code results of all business organizations in the business modeling document.

[0064] S103: Determine the target low-level code table name according to the business organization scope and the original low-level code table name.

[0065] After parsing to obtain the business organization scope and obtaining the original low-level code table name, determine the target low-level code table name according to the business organization scope and the original low-level code table name. If the incoming business organization scope is 0 or not passed in, then determine the target low-level code table name as the original low-level code table name; otherwise, determine the target low-level code table name as the dynamic low-level code table name (the dynamic low-level code table name is the original low-level code table name + the business organization scope).

[0066] In addition, the target low-level code table name can also be obtained by passing in the internal code of the plan scheme. If the passed-in internal code of the plan scheme is 0 or not passed in, then return the original low-level code table name, that is, the static low-level code table name; otherwise, return the dynamic low-level code table name (the dynamic low-level code table name is the static low-level code table name + the internal code of the plan scheme).

[0067] S104: Search for the target low-level code table according to the target low-level code table name.

[0068] Pre-store each low-level code table in the database, and pre-store the corresponding relationship between each low-level code table name and each low-level code table. After determining the target low-level code table name according to the business organization scope and the original low-level code table name, search for the target low-level code table according to the target low-level code table name.

[0069] S105: Use the target low-level code table to perform a query operation on the low-level code to be queried.

[0070] After finding the target low-level code table according to the target low-level code table name, use the target low-level code table to perform a query operation on the low-level code to be queried. By determining the target low-level code table name based on the business organization scope and the original low-level code table name, and creating the target low-level code table corresponding to the target low-level code table name, the creation of the low-level code table according to the business organization scope is realized. Therefore, when performing a low-level code query, it is only necessary to query the low-level code to be queried from the target low-level code table, rather than querying the low-level code from the original low-level code table that contains the global low-level code results of all business organizations in the overall business modeling document. This greatly improves the low-level code query efficiency. It realizes the decoupling of the businesses of different organizations, and problems with the bill of materials of individual organizations no longer affect the calculation of the material requirements plan of irrelevant organizations. Different business organization scopes have their own low-level code result tables, and they do not interfere with each other even in high-concurrency situations, improving the system availability. Obtain materials and bills of materials according to the organization, reduce IO, improve performance, and realize the distributed operation of the material requirements plan in a true sense.

[0071] As can be seen from the above technical solution, by pre-defining the original low-level code table name that contains the global low-level code results of all business organizations in the business modeling document, determining the target low-level code table name of the target low-level code table where the low-level code to be queried is located according to the original low-level code table name and the business organization scope included in the received low-level code query request, finding the target low-level code table according to the target low-level code table name, and using the target low-level code table to perform a query operation on the low-level code to be queried. It realizes the decoupling of the businesses of different organizations, and problems with the bill of materials of individual organizations no longer affect the calculation of the material requirements plan of irrelevant organizations. Different business organization scopes have their own low-level code result tables, and they do not interfere with each other even in high-concurrency situations, improving the system availability. Obtain materials and bills of materials according to the business organization scope, reduce system resource consumption, improve performance, and realize the distributed operation of the material requirements plan in a true sense.

[0072] It should be noted that based on the above embodiments, the embodiments of the present invention also provide corresponding improvement solutions. In the subsequent embodiments, the same steps or corresponding steps involved in the above embodiments can be referred to each other, and the corresponding beneficial effects can also be referred to each other. They will not be repeated one by one in the following improvement embodiments.

[0073] See Figure 2 , Figure 2 which is another implementation flowchart of the low-level code query method in the embodiments of the present invention. The method may include the following steps:

[0074] S201: Parse the received low-level code query request to obtain the business organization scope and the target metadata version number corresponding to the low-level code to be queried.

[0075] The low-level code query request also includes the target metadata version number corresponding to the low-level code to be queried. The low-level code management center parses the received low-level code query request to obtain the business organization scope and the target metadata version number corresponding to the low-level code to be queried.

[0076] S202: Obtain the original low-level code table name that bears the global low-level code results of all business organizations in the business modeling document.

[0077] S203: Determine the target low-level code table name based on the business organization scope and the original low-level code table name.

[0078] S204: Determine whether there is an existing low-level code table corresponding to the target low-level code table name in the database. If so, execute step S205; if not, execute step S211.

[0079] After determining the target low-level code table name based on the business organization scope and the original low-level code table name, determine whether there is an existing low-level code table corresponding to the target low-level code table name in the database. If so, it means that the low-level code table established according to this business organization scope has been pre-stored in the database, and execute step S205; if not, it means that the low-level code table established according to this business organization scope has not been stored in the database, and execute step S211.

[0080] S205: Obtain the existing metadata version number corresponding to the existing low-level code in the existing low-level code table.

[0081] When it is determined that there is an existing low-level code table corresponding to the target low-level code table name in the database, it means that the low-level code table established according to this business organization scope has been pre-stored in the database, and obtain the existing metadata version number corresponding to the existing low-level code in the existing low-level code table.

[0082] S206: Determine whether the existing metadata version number is the same as the target metadata version number. If so, execute step S207; if not, execute step S208.

[0083] After obtaining the existing metadata version number corresponding to the existing low-level code in the existing low-level code table, determine whether the existing metadata version number is the same as the target metadata version number. If so, it means that the current metadata version number meets the requirements, and execute step S207; if not, it means that the current metadata version number does not meet the requirements, and execute step S208.

[0084] S207: Determine the existing low-level code table as the target low-level code table.

[0085] When it is determined that the existing metadata version number is the same as the target metadata version number, it means that the current metadata version number meets the requirements, and determine the existing low-level code table as the target low-level code table.

[0086] S208: Obtain the target fields corresponding to the target metadata version number, and create a target low-level code table based on the target fields and the target low-level code table name.

[0087] When it is determined that the stored metadata version number is inconsistent with the target metadata version number, it indicates that the current metadata version number does not meet the requirements. For example, if the metadata corresponding to the stored metadata version number has one less field than the metadata corresponding to the target metadata version number, obtain the target fields corresponding to the target metadata version number, and create a target low-level code table based on the target fields and the target low-level code table name.

[0088] S209: Perform a deletion operation on the stored low-level code table corresponding to the target low-level code table name in the database.

[0089] When it is determined that the stored metadata version number is inconsistent with the target metadata version number, it indicates that an update operation needs to be performed on the stored low-level code table corresponding to the target low-level code table name in the database. After creating the target low-level code table based on the target fields and the target low-level code table name, perform a deletion operation on the stored low-level code table corresponding to the target low-level code table name in the database.

[0090] S210: Store the target low-level code table and the target metadata version number in the database.

[0091] After performing a deletion operation on the stored low-level code table corresponding to the target low-level code table name in the database, store the target low-level code table and the target metadata version number in the database, thereby realizing the update of the low-level code table in the database. This enables the seamless upgrade and expansion of the low-level codes in the database. Through the business modeling documents of the integration platform, fields can be added expandably, and the service will dynamically create low-level code tables according to the field definitions of the latest metadata based on the metadata version number.

[0092] S211: Create a target low-level code table according to the target low-level code table name.

[0093] S212: Screen the target bill of materials data from the business modeling documents according to the business organization scope.

[0094] After parsing the business organization scope corresponding to the low-level code to be queried, screen the target bill of materials data from the business modeling documents according to the business organization scope. For example, when the low-level code query request is a request to query the low-level code corresponding to the tire production quantity, and the business organization scope is the organization scope composed of Factory A and Factory B, then only screen the tire production quantities in Factory A and Factory B.

[0095] S213: Perform low-level code operations on the target bill of materials data to obtain the target low-level code result.

[0096] After filtering out the target bill of materials data from the business modeling document according to the business organization scope, perform a low-level code operation on the target bill of materials data to obtain the target low-level code result.

[0097] S214: Store the target low-level code result in the target low-level code table.

[0098] After performing a low-level code operation on the target bill of materials data to obtain the target low-level code result, store the target low-level code result in the target low-level code table, thereby realizing the organization-based storage of low-level codes.

[0099] S215: Use the target low-level code table to perform a query operation on the low-level code to be queried.

[0100] See Figure 3 , Figure 3 , which is the timing diagram of a low-level code query method in an embodiment of the present invention. The low-level code management center includes a low-level code operation service and a table management service. When the client needs to perform a low-level code query, it passes the business organization scope to the low-level code operation service, and the low-level code operation service passes the business organization scope and the original low-level code table name to the table management service. The table management service pre-generates a target low-level code table corresponding to the business organization scope and the original low-level code table name, creates the target low-level code table according to the metadata information, and directly returns it if the table exists and the version numbers are the same, otherwise creates the target low-level code table. The table management service returns the target low-level code table name to the low-level code operation service. The low-level code operation service pre-calculates the low-level code based on the target bill of materials data of the business organization scope, and after receiving the target low-level code table name, stores the target low-level code result in the target low-level code table. The low-level code operation service returns the low-level code information to the client.

[0101] Corresponding to the above method embodiment, the present invention also provides a low-level code query device, and the low-level code query device described below can be mutually corresponding and referred to with the low-level code query method described above.

[0102] See Figure 4 , Figure 4 , which is the structural block diagram of a low-level code query device in an embodiment of the present invention. The device may include:

[0103] A request parsing module 41, configured to parse the received low-level code query request to obtain the business organization scope corresponding to the low-level code to be queried;

[0104] An original low-level code table name obtaining module 42, configured to obtain the original low-level code table name carrying the global low-level code result of all business organizations in the business modeling document;

[0105] A target low-level code table name determining module 43, configured to determine the target low-level code table name according to the business organization scope and the original low-level code table name;

[0106] The low-order code table lookup module 44 is used to look up the target low-order code table according to the target low-order code table name;

[0107] The low-order code query module 45 is used to query the to-be-query low-order code by using the target low-order code table.

[0108] As can be seen from the above technical solutions, by pre-defining the original low-order code table name carrying the global low-order code results of all business organizations in the business modeling document, determining the target low-order code table name of the target low-order code table where the to-be-query low-order code is located according to the original low-order code table name and the business organization scope included in the received low-order code query request, looking up the target low-order code table according to the target low-order code table name, and querying the to-be-query low-order code by using the target low-order code table. The business decoupling of different organizations is realized, and if there are problems with the bill of materials of individual organizations, it will no longer affect the material requirements planning operation of irrelevant organizations. Different business organization scopes have their own low-order code result tables, and they do not interfere with each other even in high-concurrency situations, improving the system availability. Obtaining materials and bills of materials according to the business organization scope reduces system resource consumption, improves performance, and realizes the distributed operation of the material requirements plan in a true sense.

[0109] In a specific embodiment of the present invention, the device may further include:

[0110] The bill of materials data screening module is used to screen the target bill of materials data from the business modeling document according to the business organization scope before querying the to-be-query low-order code by using the target low-order code table;

[0111] The low-order code operation module is used to perform low-order code operation on the target bill of materials data to obtain the target low-order code result;

[0112] The low-order code result storage module is used to store the target low-order code result into the target low-order code table.

[0113] In a specific embodiment of the present invention, the low-order code table lookup module 44 includes:

[0114] The judgment sub-module is used to judge whether there is an existing low-order code table corresponding to the target low-order code table name in the database;

[0115] The low-order code table determination sub-module is used to determine the existing low-order code table as the target low-order code table when there is an existing low-order code table corresponding to the target low-order code table name in the database;

[0116] The low-order code table creation sub-module is used to create the target low-order code table according to the target low-order code table name when there is no existing low-order code table corresponding to the target low-order code table name in the database.

[0117] In a specific embodiment of the present invention, the device may further include:

[0118] An existing metadata version number acquisition module, configured to acquire the existing metadata version number corresponding to the existing low-order code in the existing low-order code table after determining that there is an existing low-order code table corresponding to the target low-order code table name in the database;

[0119] The request parsing module 41 is specifically a module that parses the received low-order code query request to obtain the service organization scope corresponding to the to-be-query low-order code and the target metadata version number;

[0120] A judgment module, configured to judge whether the existing metadata version number is consistent with the target metadata version number;

[0121] The low-order code table determination sub-module is specifically a module that determines the existing low-order code table as the target low-order code table when it is determined that the existing metadata version number is consistent with the target metadata version number;

[0122] A low-order code table creation module, configured to, when it is determined that the existing metadata version number is inconsistent with the target metadata version number, acquire the target fields corresponding to the target metadata version number, and create a target low-order code table according to the target fields and the target low-order code table name.

[0123] In a specific embodiment of the present invention, the device may further include:

[0124] A low-order code table deletion module, configured to perform a deletion operation on the existing low-order code table corresponding to the target low-order code table name in the database after creating the target low-order code table according to the target fields and the target low-order code table name;

[0125] A low-order code table and metadata version number storage module, configured to store the target low-order code table and the target metadata version number in the database.

[0126] Corresponding to the above method embodiment, refer to Figure 5 , Figure 5 which is a schematic diagram of the low-order code query device provided by the present invention. The device may include:

[0127] A memory 332, configured to store a computer program;

[0128] A processor 322, configured to implement the steps of the low-order code query method in the above method embodiment when executing the computer program.

[0129] Specifically, please refer to Figure 6 , Figure 6FIG. 0 is a schematic structural diagram of a low-level code query device provided in this embodiment. The low-level code query device may vary greatly due to different configurations or performances, and may include a processor (central processing units, CPU) 322 (for example, one or more processors) and a memory 332. The memory 332 stores one or more computer application programs 342 or data 344. Among them, the memory 332 may be short-term storage or persistent storage. The program stored in the memory 332 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the data processing device. Further, the processor 322 may be set to communicate with the memory 332 and execute a series of instruction operations in the memory 332 on the low-level code query device 301.

[0130] The low-level code query device 301 may further include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input / output interfaces 358, and / or one or more operating systems 341.

[0131] The steps in the low-level code query method described above may be implemented by the structure of the low-level code query device.

[0132] Corresponding to the above method embodiment, the present invention further provides a computer-readable storage medium. A computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, the following steps may be implemented:

[0133] Parse the received low-level code query request to obtain the service organization scope corresponding to the low-level code to be queried; obtain the original low-level code table name carrying the global low-level code results of all service organizations in the service modeling document; determine the target low-level code table name according to the service organization scope and the original low-level code table name; find the target low-level code table according to the target low-level code table name; use the target low-level code table to perform a query operation on the low-level code to be queried.

[0134] The computer-readable storage medium may include: various media such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks, or optical discs that can store program codes.

[0135] For the introduction of the computer-readable storage medium provided by the present invention, please refer to the above method embodiment, and the present invention will not be elaborated herein.

[0136] The present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it can implement the steps of any of the above-mentioned low-bit code query methods.

[0137] It should be noted that the information (including but not limited to user information, device information, etc.) and data (including but not limited to read data, target data, etc.) involved in the embodiments of the present application are all information and data authorized by the user or fully authorized by all parties, and the processing process of the information and data also complies with the provisions of relevant laws and regulations.

[0138] In this specification, the various embodiments are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. For the same or similar parts among the various embodiments, reference can be made to each other. For the devices, equipment, and computer-readable storage media disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple. For the relevant parts, reference can be made to the description of the method part. In this article, specific examples are used to elaborate on the principles and implementation manners of the present invention. The description of the above embodiments is only used to help understand the technical solution and its core idea of the present invention. It should be noted that for those of ordinary skill in the art in the technical field of the present invention, without departing from the principle of the present invention, several improvements and modifications can still be made to the present invention, and these improvements and modifications also fall within the protection scope of the claims of the present invention.

Claims

1. A method for querying low-order codes, characterized in that, including: Parsing the received low-level code query request to obtain the business organization scope corresponding to the low-level code to be queried; Obtaining the original low-level code table name carrying the global low-level code results of all business organizations in the business modeling document; Determining the target low-level code table name according to the business organization scope and the original low-level code table name; Searching for the target low-level code table according to the target low-level code table name; Performing a query operation on the low-level code to be queried by using the target low-level code table; Searching for the target low-level code table according to the target low-level code table name, including: Judging whether there is an existing low-level code table corresponding to the target low-level code table name in the database; If so, determining the existing low-level code table as the target low-level code table; After determining that there is an existing low-level code table corresponding to the target low-level code table name in the database, it further includes: Obtaining the existing metadata version number corresponding to the existing low-level code in the existing low-level code table; Parsing the received low-level code query request to obtain the business organization scope corresponding to the low-level code to be queried, including: Parsing the received low-level code query request to obtain the business organization scope and the target metadata version number corresponding to the low-level code to be queried; Judging whether the existing metadata version number is consistent with the target metadata version number; If so, performing the step of determining the existing low-level code table as the target low-level code table; If not, obtaining the target field corresponding to the target metadata version number, and creating the target low-level code table according to the target field and the target low-level code table name.

2. The low-bit code query method according to claim 1, wherein Before performing the query operation on the low-level code to be queried by using the target low-level code table, it further includes: Screening target bill of materials data from the business modeling document according to the business organization scope; Performing low-level code calculation on the target bill of materials data to obtain a target low-level code result; Storing the target low-level code result in the target low-level code table.

3. The low-order code query method according to claim 1, wherein When it is determined that there is no existing low-level code table corresponding to the target low-level code table name in the database, it further includes: Creating the target low-level code table according to the target low-level code table name.

4. The low-bit code query method according to claim 3, characterized in that After creating the target low-level code table according to the target field and the target low-level code table name, it further includes: Performing a deletion operation on the existing low-level code table corresponding to the target low-level code table name in the database; Storing the target low-level code table and the target metadata version number in the database.

5. A low-order code query device, characterized in that, including: A request parsing module for parsing the received low-level code query request to obtain the business organization scope corresponding to the low-level code to be queried; An original low-level code table name obtaining module for obtaining the original low-level code table name carrying the global low-level code results of all business organizations in the business modeling document; A target low-level code table name determining module for determining the target low-level code table name according to the business organization scope and the original low-level code table name; A low-level code table searching module for searching for the target low-level code table according to the target low-level code table name; A low-level code query module for performing a query operation on the low-level code to be queried by using the target low-level code table; The low-level code table searching module includes: A judgment sub-module, configured to judge whether there is a stored low-level code table corresponding to the target low-level code table name in the database; A low-level code table determination sub-module, configured to determine the stored low-level code table as the target low-level code table when there is a stored low-level code table corresponding to the target low-level code table name in the database; It further includes: A stored metadata version number acquisition module, configured to acquire the stored metadata version number corresponding to the stored low-level code in the stored low-level code table after determining that there is a stored low-level code table corresponding to the target low-level code table name in the database; The request parsing module is specifically a module that parses the received low-level code query request to obtain the business organization scope corresponding to the low-level code to be queried and the target metadata version number; A judgment module, configured to judge whether the stored metadata version number is consistent with the target metadata version number; The low-level code table determination sub-module is specifically a module that determines the stored low-level code table as the target low-level code table when it is determined that the stored metadata version number is consistent with the target metadata version number; A low-level code table creation module, configured to obtain the target fields corresponding to the target metadata version number and create a target low-level code table according to the target fields and the target low-level code table name when it is determined that the stored metadata version number is inconsistent with the target metadata version number.

6. The low-order code query device according to claim 5, wherein It further includes: A bill of materials data screening module, configured to screen target bill of materials data from the business modeling documents according to the business organization scope before querying the low-level code to be queried by using the target low-level code table; A low-level code calculation module, configured to perform low-level code calculation on the target bill of materials data to obtain a target low-level code result; A low-level code result storage module, configured to store the target low-level code result in the target low-level code table.

7. A low-order code query device, characterized in that, It includes: A memory, configured to store a computer program; A processor, configured to implement the steps of the low-level code query method according to any one of claims 1 to 4 when executing the computer program.

8. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, it implements the steps of the low-level code query method according to any one of claims 1 to 4.

9. A computer program product, characterized in that, The computer program product includes a computer program, and when the computer program is executed by a processor, it implements the steps of the low-level code query method according to any one of claims 1 to 4.

Images