CN118863761A - A method and system for managing coding relationships - Google Patents

Abstract

The present application provides a coding relationship management method and system. First, a parts substitution group is constructed, which includes a hat code and multiple sub-codes with the same control dimension, and the hat code connects multiple sub-codes. Secondly, a bill of materials BOM relationship is constructed, and the BOM relationship includes a parent item code and one or more sub-item codes. The sub-item code includes a hat code and a sub-code, and the parent code connects the sub-item code. The properties of the sub-item code in the BOM relationship are set again, and the properties of the sub-item code include determining whether to enable the parts substitution group corresponding to the sub-item code in the BOM relationship. Finally, the properties of multiple sub-codes in the BOM sub-item parts substitution group relationship are set, and the properties of multiple sub-codes include determining whether to enable the corresponding sub-codes in the BOM sub-item parts substitution group relationship. Through the coding relationship management method of the present application, the BOM relationship can realize the functions of flexible material supply, reuse sharing and layered application.

Description

A method and system for managing coding relationships

Technical Field

The present application belongs to the technical field of material management, and in particular, relates to a method and system for managing coding relationships.

Background Art

In recent years, with the continuous globalization of the supply chain industry, the scale and complexity of the material supply chain have increased significantly, and the export control requirements for technology and material products between countries have become increasingly stringent. At the same time, due to the rapid development of the supply chain industry, material management solutions have become increasingly complex, product replacement cycles have become shorter, and the number of optional components for products has increased. This trend has made the code library of the bill of materials increasingly large. With the continuous development of information and Internet technology and the increasing demand for the supply of new products, the need to create a large number of bills of materials has led to an increasing cost of generating, maintaining, and managing the bill of materials.

Summary of the invention

In order to solve the above problems, the present application provides a coding relationship management method and system, which can support the functional characteristics of flexible material supply, reuse sharing and layered application of the bill of materials.

In the first aspect, a coding relationship management method is proposed. First, a component substitution group is constructed, wherein the component substitution group includes a hat code and multiple sub-codes with the same control dimension, and the hat code connects the multiple sub-codes. Secondly, a bill of materials BOM relationship is constructed, wherein the BOM relationship includes a parent item code and one or more sub-item codes, the sub-item code includes the hat code and the sub-code, and the parent item code connects the sub-item code. Thirdly, the attributes of the sub-item code in the BOM relationship are set, wherein the attributes of the sub-item code include determining whether to enable the component substitution group corresponding to the sub-item code in the BOM relationship. Finally, the attributes of the multiple sub-codes in the BOM sub-item component substitution group relationship are set, wherein the attributes of the multiple sub-codes include determining whether to enable the corresponding sub-codes in the BOM sub-item component substitution group relationship. Through the coding relationship management method of the present application, a BOM relationship with functional characteristics of supporting flexible material supply, reuse sharing and layered application can be realized.

Next, the specific method of constructing a component replacement group is introduced. First, multiple codes are created, and the component replacement group is constructed according to the multiple codes, wherein the coding type of the code includes one hat code and multiple sub-codes. Secondly, the hat code cannot be used as a sub-code in other component replacement groups, and the sub-code cannot be used as a hat code in other component replacement groups. Finally, within the component replacement group, each sub-code can only be connected to one hat code, and cannot be connected to other sub-codes or other hat codes. By limiting the coding structure of the component replacement group, it can be ensured that the component replacement group is a coding structure centered on the hat code, so as to realize a BOM coding relationship of hierarchical application.

In the component replacement group, the same control dimensions among the multiple subcodes include the same functional specifications, same interface dimensions, same appearance materials, and same processes among the multiple components represented by the multiple subcodes. In the case where the multiple subcodes in the component replacement group have the same control dimensions, the multiple subcodes have a substitutable relationship.

In the BOM relationship, the sub-item code includes the hat code and the sub-code. When the sub-item code is a hat code, the hat code and the corresponding multiple sub-codes constitute the BOM sub-item component replacement group; when the sub-item code is a sub-code, the sub-code is included in the BOM relationship by connecting with the parent item code to realize a hierarchical BOM code relationship.

In a common embodiment, when the sub-item code is a sub-code, the sub-code is directly connected to the parent code to construct the BOM relationship, and is not connected to the hat code and other sub-codes. When the sub-item code is a hat code, the BOM sub-item component substitution group does not include the parent code, and the hat code in the BOM sub-item component substitution group only connects the multiple sub-codes with the same control dimension.

In a typical embodiment, the component replacement group can be applied to multiple BOM relationships to construct the BOM sub-item component replacement group. The hat code and the multiple sub-code compositions of the component replacement group applied in different BOM relationships are the same, which can realize the functional characteristics of code group reuse and sharing.

In the case where the component replacement group is applied to multiple BOM relationships, the attributes of the hat code and the attributes of the sub-code of the BOM sub-item component replacement group are independently set in each BOM relationship according to business needs, and the code attribute value settings between the various BOM relationships that apply the component replacement group do not affect each other. By setting the code values of each code of the component replacement group in different BOM relationships, the functional characteristics of code group reuse and sharing are realized while meeting the requirements for building different BOM relationships.

In a common embodiment, when the attribute of the hat code of the BOM sub-item component replacement group is to enable the sub-code, the attribute of the sub-code connected to the hat code can be set to enable. When the attribute of the hat code of the BOM sub-item component replacement group is to enable the sub-code, the attribute of at least one sub-code connected to the hat code is set to enable.

In a common embodiment, after the component replacement group is constructed, a change operation can be performed on the component replacement group, wherein the change operation includes performing one or more operations of adding, deleting, modifying, and checking the sub-code or the sub-code attribute without changing the hat code of the component replacement group. By changing the component replacement group, the functional characteristics of flexible material supply in the BOM relationship can be realized.

In a typical embodiment, before the BOM relationship changes, when the change needs to be made to the component substitution group, a substitution verification of the change to the component substitution group is performed on the BOM relationship to which the component substitution group has been applied. When the substitution verification in the component substitution group BOM relationship passes, the change operation is performed on the BOM sub-item component substitution group to which the component substitution group is applied, and the sub-coding attribute of the changed BOM sub-item component substitution group is updated to determine whether the sub-coding is enabled in the corresponding BOM sub-item component substitution group BOM relationship. By timely updating the substitution verification results for specific BOM relationships, the BOM can respond quickly to material changes and updates, thereby realizing the functional characteristics of flexible material supply.

When the sub-item code of the BOM relationship contains a sub-code, a change operation is performed on the sub-code connected to the parent code, wherein the change operation includes performing one or more operations of adding, deleting, modifying and checking the attributes of the sub-code. Before the BOM relationship changes, when the sub-code connected to the parent code needs to be changed, for the BOM relationship that has applied the sub-code connected to the parent code, a replacement verification of the change is performed on the sub-code connected to the parent code. When the replacement verification in the BOM relationship passes, the change operation is performed on the sub-code connected to the parent code in the BOM relationship, and the sub-code attributes in the BOM relationship after the change are updated and set.

In the second aspect, a coding relationship management device is proposed, including a substitution group construction module, a BOM relationship construction module, and a BOM sub-item substitution group construction module. First, the substitution group construction module is used to construct a component substitution group. Among them, the component substitution group includes a hat code and multiple sub-codes with the same management and control dimension, and the hat code connects the multiple sub-codes. Secondly, the BOM relationship construction module is used to construct a bill of materials BOM relationship and set the attributes of the extensible sub-item code. Among them, the BOM relationship includes a parent item code and one or more sub-item codes, and the sub-item code includes the hat code and the sub-code, and the parent item code connects the hat code. Thirdly, the BOM relationship construction module is also used to set the coding attributes of the hat code when the sub-item code of the BOM relationship is a hat code. Among them, the coding attributes of the hat code include determining whether the component substitution group corresponding to the hat code is enabled in the BOM relationship; finally, the BOM sub-item substitution group construction module is used to construct a BOM sub-item component substitution group. Among them, the coding attributes of the multiple sub-codes in the BOM sub-item component replacement group are set, and the coding attributes of the sub-codes include determining whether the corresponding sub-codes are enabled in the BOM relationship. Through the coding relationship management method of this application, a BOM relationship with functional characteristics of supporting flexible material supply, reuse sharing and layered application can be realized.

The replacement group construction module, when constructing a component replacement group, generally includes the following steps. First, multiple codes are created, and the component replacement group is constructed according to the multiple codes, wherein the coding type of the coding includes one hat code and multiple sub-codes. Secondly, the hat code cannot be used as a sub-code in other component replacement groups, and the sub-code cannot be used as a hat code in other component replacement groups. Finally, within the component replacement group, each sub-code can only be connected to one hat code, and cannot be connected to other sub-codes or other hat codes. By limiting the coding structure of the component replacement group, it can be ensured that the component replacement group is a coding structure centered on the hat code, so as to realize a BOM coding relationship of hierarchical application.

In the component replacement group module, the multiple subcodes have the same control dimension, including the multiple components represented by the multiple subcodes have the same functional specifications, the same interface size, the same appearance material, and the same process. In the case where the multiple subcodes of the component replacement group have the same control dimension, the multiple subcodes have a replaceable relationship.

In the BOM relationship building module, the sub-item code includes the hat code and the sub-code. When the sub-item code is a hat code, the hat code and the corresponding multiple sub-codes form a BOM sub-item component replacement group to act on the BOM relationship; when the sub-item code is a sub-code, the sub-code is included in the BOM relationship by connecting with the parent item code.

In a common embodiment, the BOM relationship construction module is also used for when the sub-item code is a sub-code, the sub-code is directly connected with the parent code to construct the BOM relationship, and is not connected with the hat code and other sub-codes. The BOM relationship construction module is also used for when the sub-item code is a hat code, the BOM sub-item component replacement group does not include the parent item code, and the hat code in the BOM sub-item component replacement group only connects the multiple sub-codes with the same control dimension.

The BOM sub-item component replacement group construction module is also used to apply the component replacement group to multiple BOM relationships to construct the BOM sub-item component replacement group, and the hat code and the multiple sub-code compositions of the component replacement group applied to different BOM relationships are the same. It can be understood that the coding relationship of the same component replacement group can be applied to multiple BOM relationships to realize the functional characteristics of code group reuse and sharing.

The BOM sub-item component replacement group module is also used to independently set the attributes of the cap code and the sub-code of the BOM sub-item component replacement group in each BOM relationship according to business needs when the component replacement group is applied to multiple BOM relationships. By setting the code values of each code of the component replacement group in different BOM relationships, the functional characteristics of code group reuse and sharing are realized while meeting the requirements of building different BOM relationships.

The BOM sub-item component substitution group module is further used for setting the attribute of the sub-code connected to the hat code to be enabled only when the attribute of the hat code of the BOM sub-item component substitution group is to enable the sub-code. The BOM sub-item component substitution group module is further used for setting the attribute of at least one sub-code connected to the hat code to be enabled only when the attribute of the hat code of the BOM sub-item component substitution group is to enable the sub-code.

After the construction of the component replacement group is completed, the replacement group construction module is also used to perform a change operation on the component replacement group. The change operation includes performing one or more operations of adding, deleting, modifying, and checking the sub-code or the sub-code attribute without changing the hat code of the component replacement group. By changing the component replacement group, the functional characteristics of flexible material supply in the BOM relationship can be realized.

Before the BOM relationship changes, when it is necessary to make the change to the component substitution group, a substitution verification of the change to the component substitution group is performed on the BOM relationship to which the component substitution group has been applied. When the substitution verification in the component substitution group passes, the change operation is performed on the BOM sub-item component substitution group to which the component substitution group is applied, and the sub-coding attribute of the changed BOM sub-item component substitution group is updated and set to determine whether the sub-coding is enabled in the corresponding BOM sub-item component substitution group. By timely updating the substitution verification results for specific BOM relationships, the BOM relationship can quickly respond to material changes and updates, so as to realize the functional characteristics of flexible material supply.

After building the BOM relationship, the substitution group building module is used to perform a change operation on the sub-code connected to the parent code, wherein the change operation includes performing one or more operations of adding, deleting, modifying, and checking the attributes of the sub-code. By changing the component substitution group, the functional characteristics of flexible material supply in the BOM relationship are realized.

Before the BOM relationship changes, when the sub-code connected to the parent code needs to be changed, the BOM relationship that has applied the sub-code connected to the parent code performs a substitution verification on the sub-code connected to the parent code. When the substitution verification in the BOM relationship passes, the substitution group construction module performs the change operation on the sub-code connected to the parent code in the BOM relationship, and sets the changed sub-code attributes related to whether it is enabled in the BOM relationship. By refreshing and setting the coding attributes of the changed component substitution group, it is ensured that the changed component substitution group can be normally matched in the applied BOM relationship to realize the functional characteristics of flexible material supply.

In a third aspect, an electronic computing device is proposed, comprising a memory and a processor, wherein the memory stores instructions, and when the processor executes the instructions in the memory, the method described in any one of the embodiments of the first aspect can be implemented.

In a fourth aspect, a non-volatile storage medium is proposed, comprising a plurality of instructions, wherein when the instructions are executed by an electronic device, the method described in any one of the embodiments of the first aspect can be implemented.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the drawings required for use in the embodiments of the present application or the background technology will be described below.

FIG1 is a schematic diagram of an existing Part/BOM coding relationship management method provided by the present application;

FIG2 is a schematic diagram of a Part/BOM coding relationship management system provided by the present application;

FIG3 is a schematic diagram of a method for constructing a Part/BOM coding relationship provided by the present application;

FIG4 is a schematic diagram of a Part replacement group with the same control dimension provided by the present application;

FIG5 is a schematic diagram of the Part code splitting requirements in an application scenario of differentiated supply of manufacturing devices provided by the present application;

FIG6 is a schematic diagram of a method for managing the relationship between Part/BOM codes provided by the present application to solve the problem of implementing device supply in differentiated scenarios;

FIG7 is a schematic diagram of a device supply requirement for a new manufacturer model provided by the present application;

FIG8 is a schematic diagram of a method for managing the relationship between Part/BOM codes provided by the present application to solve the problem of quickly adding new manufacturers and models to device supply;

FIG9 is a schematic diagram of a Part/BOM coding relationship management device provided by the present application;

FIG10 is a schematic diagram of the structure of an electronic computing device provided by the present application.

DETAILED DESCRIPTION

In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described through the implementation method with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present application.

In the description of this application, unless otherwise clearly defined, words such as "setting" should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meaning of the above words in this application based on the specific content of the technical solution.

In the description of the present application, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific embodiments", "specific coding numbers", or "some examples" etc. means that the specific features or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

Next, the relevant concepts involved in this application are introduced respectively.

Parts (hereinafter referred to as "Part"): refers to raw materials, semi-finished products, finished products, customer-supplied materials, returned products, spare parts, expenses, services, software, outsourced parts, packaged virtual items, etc. related to the business activities of the enterprise. It is a unit for R&D, sales, supply, manufacturing, procurement, service and financial accounting.

Bill of material (BOM): reflects the elements of product material composition. Through the parent-child relationship, it can reflect the production process from raw materials to products. It is the master data guiding sales, production, planning, procurement, orders, cost accounting, etc.

Manufacturer part number (MPN): also known as manufacturer model, refers to a unique identifier assigned by a manufacturer or supplier to a product it manufactures. It usually includes numbers, letters or symbols, and is used to distinguish products of the same type and specification but from different manufacturers or batches, and facilitates tracking and identification in procurement, inventory management, production and other links. "Manufacturer" means "manufacturer" rather than "factory". Usually a "manufacturer" can have multiple "factories" under it.

Part substitution group: that is, a component substitution group, including a cap code and multiple sub-codes with the same functional specifications, the same interface size, the same appearance material and the same process. It allows multiple sub-codes under the cap code to be selected based on business needs for quotation, design selection, supply, manufacturing and delivery, etc.

Hat code: It is used to group a group of sub-codes with the same functional specifications, interface dimensions, appearance materials and processes within a parts replacement group.

Subcode: Different part codes that belong to the same hat code but are defined due to differences in control dimensions. Control dimensions: refers to the management and control of some key parameters of the bill of materials to ensure the accuracy, feasibility and economy of the production plan, including the number of parts, part specifications, process routes, cost accounting, and inventory management. Through effective management and control of these control dimensions, enterprises can achieve effective management and optimization of the bill of materials, thereby improving production efficiency and product quality, and reducing costs and inventory risks.

"Hat/Subcode" attribute: used to indicate whether the Part code is a member of the Part substitution group and its position in the Part substitution group (hat code or subcode).

BOM sub-item Part substitution group: BOM sub-item component substitution group, a new relationship generated by combining the two relationships of BOM and Part substitution group, is used to solve the differentiated usage scenarios of Part substitution group when shared by various products. In addition to the objects that generate the relationship (BOM and Part substitution group), it also contains attributes that describe the relationship. The attributes of BOM sub-item Part substitution group can be configured according to the needs of the business scenario.

"Enabled in BOM" attribute: used to indicate whether each sub-code in the Part alternative group is enabled in the specific BOM. It can be set to "enabled" or "disabled".

After introducing the relevant name concepts involved in this application, in order to facilitate the understanding of the present invention by people in the relevant field, the technical field and application background cited in this application will be briefly described below.

Product Life-Cycle Management (hereinafter referred to as "PLM system") is an enterprise information tool that manages the entire process of product development from design to manufacturing, maintenance and retirement, including support and management of product design, development, testing, production, sales, marketing and other processes, which can help enterprises achieve effective coordination and seamless connection of various links such as product research and development, process manufacturing, and after-sales service. The PLM system mainly includes subsystems such as product data management, process flow management and project collaborative management. By managing the entire life cycle of the product and working together, it shortens the time to market, improves product quality and reduces development costs.

After the product development and design phase of an enterprise is completed, the enterprise resource planning system can be used to realize the release and production of products. The enterprise resource planning system (Enterprise Resource Planning, hereinafter referred to as the "ERP system") is an integrated enterprise resource planning management system mainly for the manufacturing industry, which is developed for material resource management (logistics), human resource management (personnel flow), financial resource management (financial flow), and information resource management (information flow). The emergence of the EPR system is inseparable from the rapid development of computer information technology. The functions involved include not only the traditional MRPII module (manufacturing, supply and marketing, and finance) applications, but also supply chain management (Supply Chain Management, SCM), sales and marketing, customer service, financial management, manufacturing management, inventory management, factory and equipment maintenance management, human resource management, report management, manufacturing execution system (Manufacturing Executive System, MES), workflow services and enterprise systems, factory cluster management, product quality management, laboratory management, material transportation management, process control interface and other new applications, as well as data collection interface, electronic communication, e-mail, regulations and standards, project management, financial investment management, market information management and process control and other supplementary applications.

The PLM system and ERP system serve different areas of the enterprise respectively. However, in each stage of the product life cycle, the two systems can work together to support comprehensive enterprise management and production processes, and improve the production efficiency and management level of the enterprise. The PLM system and ERP system realize information sharing, data integration, process coordination, and collaborative analysis, so that the data and documents involved in the product design and development process can be integrated with the rest of the business data, thereby achieving better process automation and data sharing. The PLM system and ERP system manage product data in a unified manner through Part/BOM. Part/BOM management is of great significance to the efficient application of the PLM system and ERP system and the reduction of enterprise management costs.

Next, this application will introduce a Part/BOM coding relationship management system, method and device provided by this application. In order to ensure the security and stability of the supply chain and avoid exclusive supply, companies usually adopt the "multiple manufacturers supply" model for materials. However, due to the influence of the external environment, materials from different manufacturers need to be managed in a differentiated and refined manner based on factors such as origin, environmental regulations, and processes. Therefore, an effective Part/BOM technical solution is needed to support the business to continue to maintain a secure and stable supply and the advantages of multiple suppliers, while supporting different business areas to cope with the constant changes in internal and external environmental control.

Please refer to Figure 1, which is a schematic diagram of an existing Part/BOM coding relationship management method provided by the present application. The embodiment shown in Figure 1 is used to describe the existing Part/BOM coding relationship management method, including: Part replacement management 110, BOM replacement management 120, and Part and MPN relationship management 130.

Part substitution management 110 is used to establish a Part substitution plan. Part substitution management 110 can establish a one-to-one substitutable relationship between Parts. For example, a Part coded as 12XXXXX2 can be used to replace a Part coded as 12XXXXX1. When establishing a substitution relationship between Parts, the substitution type, effective time, and expiration time can be specified. However, the relationship between the various Parts is not grouped according to clear rules, and the relationship between the various Parts is very scattered, and it is impossible to maximize shared resources.

In the BOM replacement management 120, the implementation methods of BOM replacement management include at least the following two:

The first BOM sub-item substitution method 121 adds all the alternative Part codes with substitution relationships to the BOM, and maintains the substitution strategy, priority, usage percentage, etc. in the substitution group. However, the sub-item substitution relationship constructed in the BOM cannot be reused and shared by other BOMs. In the same BOM, each Part that can be substituted for each other must be added to the BOM at the same time. Once the substitution relationship in the Part substitution group changes, the BOM list also needs to be changed accordingly.

The second BOM sub-item substitution method 122 maintains a Part code in the BOM as a BOM sub-item, and establishes a group of alternative Parts that have a substitution relationship with the sub-item Part. These alternative Parts can maintain their own substitution quantity, priority, etc. However, similar to the first method, the sub-item substitution relationship constructed in the BOM cannot be reused and shared. At the same time, since the sub-item of the BOM not only represents the satisfaction of the BOM design requirements, but also represents the specific material specifications delivered by certain manufacturers; when the manufacturer's specifications change, the sub-item code needs to be changed, and the BOM sub-item substitution group relationship will be released.

The Part and MPN relationship management 130 is used to establish a one-to-one or one-to-many relationship between Part and manufacturer model. The Part and MPN relationship management 130 can establish a relationship between all manufacturer models that meet the Part specification requirements and Part. Therefore, when there is only one manufacturer model that meets the Part specification requirements, a one-to-one relationship is established between Part and the manufacturer model (MPN). When there are multiple manufacturer models that meet the Part specification requirements, a one-to-many relationship is established between Part and the manufacturer model (MPN). In the existing technical solution, even if the specification requirements are the same, some manufacturer models are not met due to differentiated management and control requirements, and this needs to be solved by splitting the coding. This results in the same specification requirements but different Part codes, and the materials of the manufacturer models are assigned to different Part codes to manage the physical inventory, making it impossible to fully share the inventory on different product BOMs, reducing supply flexibility.

With the continuous development of information technology, the relationship between suppliers, manufacturers, retailers, factories, products, parts, and differentiated application scenarios is becoming more and more complex, and the speed of updates and iterations is increasing. BOM is an important data support for enterprise supply chain management. Replacing the management method with the existing BOM may cause increasing material redundancy and waste. The technical problems existing in the existing technical solutions often make it difficult to meet the needs of the following application scenarios:

1. The design specifications are the same, but due to differentiated management, they are split and combined into multiple codes. The substitution relationship between codes is not uniformly managed. Procurement cannot manage complex device demand aggregation, supply manually manages complex device substitution relationships, and manufacturing implements complex device physical substitution. Therefore, a method is needed to support centralized management based on Part substitution relationships, and after setting BOM sub-item differences, the ability to decompose actual manufacturer model material procurement requirements and task order material collection instructions is required.

2. When a new manufacturer model is introduced into the device code, there are many BOMs that reference the device code. If the progress cycle of the product BOM replacement verification is very different, it is impossible to support the urgent demand for the verified product BOM to switch first. Therefore, a capability is needed to support the differentiated configuration of manufacturer model verification results based on different BOMs.

In order to improve the reusability and shareability of materials, the present application proposes a Part/BOM coding relationship management system, method and device, which can enable the bill of materials to have the functional characteristics of supporting flexible material supply, reuse and sharing, and layered application.

Please refer to Figure 2, which is a schematic diagram of a Part/BOM code relationship management system proposed in this application. As shown in Figure 2, the Part/BOM code relationship management system 200 includes a Part code 201, a Part replacement group 202, a BOM relationship 203, and a BOM sub-item Part replacement group 204.

Part code 201, Part management includes Part code and a set of related attribute information. The information contained in Part code 201 includes not only the Part code used to refer to the component, but also the system association identifiers used to associate with the Product Lifecycle Management System (PLM) and Enterprise Resource Planning System (ERP) involving Part/BOM management. Part code 201 can be associated with Part substitution group 202, BOM relationship 203, and BOM sub-item Part substitution group 204.

Part substitution group 202 is used to describe a coding group composed of multiple Parts of the same control dimension, including a hat code and multiple sub-codes with the same control dimension. The same control dimension refers to the same functional specifications, the same interface size, the same appearance material and the same process. The sub-codes are mutually replaceable due to the same control dimension. Part substitution group 202 can be associated with Part code 201.

BOM relationship 203 is used to set the coding attributes and coding relationships of the parent item code and each sub-item code connected to the parent item code in the BOM relationship. The sub-item code includes a hat code and a sub-code. The attributes of the sub-item code in the BOM relationship are set, and the attributes of the sub-item code include determining whether to enable the component replacement group corresponding to the sub-item code in the BOM relationship.

BOM sub-item Part substitution group 204, when the sub-item code of the BOM relationship is a hat code, the Part substitution group corresponding to the hat code is called a BOM sub-item Part substitution group. The properties of the multiple sub-codes in the BOM sub-item Part substitution group relationship are set, and the properties of the multiple sub-codes include determining whether to enable the corresponding sub-codes in the BOM sub-item Part substitution group relationship. The BOM sub-item Part substitution group 204 can be associated with the Part code 201 and the BOM relationship 203.

Please refer to Figure 3, which is a schematic diagram of a method for constructing a Part/BOM coding relationship provided by the present application. The method provided by the present application is used to construct all or part of the Part/BOM coding relationship management system as shown in Figure 2. It can be understood that the Part/BOM coding relationship management system constructed using this embodiment is only used as a demonstration and does not limit the specific attribute content in the Part/BOM coding relationship management system. The specific implementation steps are as follows:

S101: Construct a Part replacement group.

As shown in Figure 4, Figure 4 is a schematic diagram of a Part replacement group with the same control dimension provided by this application. The Part replacement group includes a hat code and a plurality of sub-codes corresponding to the hat code with the same functional specifications, the same interface size, the same appearance material and the same process. As shown in Figure 4, the control dimensions of each sub-code include one or more of the business areas of sales and customers, manufacturing and inventory, and procurement.

For example, in the sales and customer management dimension, the following application scenarios can be included:

1. The customer interface does not need to distinguish differences, and the internal reasons are to manage the parts separately and set the control dimension;

2. Due to business and other elements, the customer interface needs to manage parts separately to avoid inconsistencies between orders and goods and set up control dimensions.

For example, in the dimension of manufacturing and inventory control, the following application scenarios can be included:

1. Due to differences in sources, self-made parts and purchased parts coexist, so control dimensions are set;

2. Due to differences in devices, self-made parts coexist with self-made parts, so control dimensions are set.

For example, in the control dimension of procurement, the control dimension is set up because of the differences in application scenarios such as trace ingredients, origin, environmental regulations, and processes, and it is necessary to manage materials from different manufacturers.

The Part substitution group allows one or more sub-codes under the hat code to be selected based on business needs for quotation, design selection, supply, manufacturing and delivery, etc. Among them, the hat code is used by the business definition rules to group a group of sub-codes of the same control dimension. The sub-codes belong to the same hat code, but different part codes are defined due to differences in business.

The key points when constructing the Part substitution group include:

1. Set the encoding type to identify whether a code is a hat code, a sub-code, or no code involved.

2. The encoding type of a code cannot be both a hat code and a sub-code.

3. Hat coding and sub-coding construct the Part substitution group relationship, and BOM relationship is not allowed to be mounted under hat coding.

4. According to business needs, the coding rules of sub-codes are restricted. After the relationship between the sub-code and the hat code is disconnected, the sub-code cannot be used again. It is also required that the same sub-code is only allowed to have one hat code.

5. The hat code cannot be used as a subcode in other Part substitution groups, and the subcode cannot be used as a hat code in other Part substitution groups;

6. Each sub-code in the Part substitution group can only be connected to one hat code, and there is no direct connection between the sub-codes in the group.

The same control dimensions of the sub-codes in the Part replacement group include the same functional specifications, the same interface size, the same appearance material, and the same process, etc. The control dimensions of the sub-codes in the Part replacement group are added, deleted, modified, and queried by editing the coding attributes of the sub-codes according to the application scenarios and business needs of the Part replacement group; when the sub-codes in the Part replacement group have the same control dimensions, the sub-codes in the Part replacement group have a mutual replacement relationship.

S102: Construct BOM relationship.

In the BOM relationship, it includes a parent item code and one or more child item codes connected to the parent item code. The types of child item codes include hat codes representing part substitution groups and child codes that do not contain part substitution group relationships.

When the sub-item code is a hat code, set the "whether to enable sub-coding" attribute of each hat code. The "whether to enable sub-coding" attribute includes two states: "enable/disable" and "not involved". Among them, "enable/disable" indicates whether the sub-coding of this hat code is enabled in the BOM, and "not involved" means that this code does not contain sub-coding. The parent code can be connected to one or more hat codes, and correspondingly, the number of Part replacement groups in a BOM relationship can be one or more. In other possible embodiments, when the sub-item code in the BOM relationship is a sub-coding, the "whether to enable sub-coding" attribute of the sub-item code is not involved.

S103: Construct a BOM sub-item Part substitution group. The BOM sub-item Part substitution group is the relationship generated by the application of the Part substitution group to the BOM relationship. In the BOM relationship, only the parent item code and the child item code are included. This step will take the child item code as a hat code as an example to introduce the construction of the BOM sub-item Part substitution group. It can be seen from the coding structure corresponding to step S103 in Figure 3 that in the BOM relationship, only two layers of structure are included, namely "PartB" as the parent item code and "PartA", "Part1" and other codes as child item codes. It is not difficult to understand that "PartA" as a child item code is also a hat code of a group of Part substitution groups, with multiple sub-codes such as "PartA-1", "PartA-2", etc. Therefore, in the example corresponding to Figure 3, the connecting line between the codes of the Part substitution group is set to a dotted line, and the connecting line between the codes of the BOM relationship is set to a solid line. In the following embodiments, the connection method of the dotted lines represents the connection of the coding relationship of the Part substitution group, and will not be repeated.

When the sub-item code in the BOM relationship is a hat code, the Part substitution group corresponding to the hat code is called the BOM sub-item Part substitution group in the BOM relationship. The properties of the BOM sub-item Part substitution group can be extended and configured according to the needs of the business scenario. When the "Whether to enable sub-coding" attribute of the hat code of the Part substitution group is enabled, the "Whether to enable in BOM" attribute of the sub-code in the BOM relationship can be set. The "Whether to enable in BOM" attribute includes two states: enabled and disabled. When the "Whether to enable in BOM" attribute is enabled, the corresponding sub-code can be used in the BOM relationship; when the "Whether to enable in BOM" attribute is disabled, the corresponding sub-code is prohibited from being used in the BOM relationship.

When the "Whether to enable sub-coding" attribute of the hat code of the Part substitution group is enabled, the "Whether to enable in BOM" attribute of at least one sub-coding in the Part substitution group needs to be set to enabled, otherwise the BOM relationship cannot be set to an available state.

In the BOM sub-item Part substitution group relationship, the sub-code can set the "whether to enable in BOM" attribute. The hat code and sub-code composition of the same Part substitution group in different BOM relationships are the same. Due to the differences in management and control dimensions of different BOM relationships, when the Part substitution group is adopted by different BOM relationships, the hat code attribute and sub-code attribute of the Part substitution group adopted by different BOM sub-item Part substitution group relationships are independently set to determine whether to enable or not enable in the corresponding BOM sub-item Part substitution group relationship to meet business needs.

Even in different BOM relationships, the coding structure of the Part replacement group with the same hat code is consistent, but the coding attributes of the hat code and the sub-code need to be set independently, and the coding attribute settings between the BOM relationships applying the Part replacement group do not affect each other.

In the BOM sub-item Part substitution group, the coding attributes of each sub-code are scalable. Users of the Part/BOM coding relationship management system can perform one or more operations of adding, deleting, modifying and checking the coding attributes in the corresponding BOM sub-item Part substitution group according to the needs of different business scenarios.

The Part/BOM coding relationship construction method shown in this application can construct a Part/BOM coding relationship management system as shown in Figure 2. The Part/BOM coding relationship construction method described in steps S101 to S103 can meet the business scenarios of supply, manufacturing, procurement, etc., identify all sub-coding combinations enabled in the BOM through "parent item code + hat code", and convert them into task instructions according to the demand, existing inventory, hat and sub-coding relationship, and manufacture identifies and processes physical parts according to the sub-coding on the task instruction.

The following will combine two specific application scenarios to illustrate the application of the Part/BOM coding relationship construction method described in Figure 3 in specific business scenarios. The following two embodiments will be used to demonstrate the functional characteristics of the Part/BOM coding relationship management method shown in this application to realize the bill of materials to support flexible material supply, reuse sharing, and layered application.

First, the first embodiment is introduced, and the specific application of the Part/BOM coding relationship management method shown in this application is introduced by taking the differentiated supply of manufacturing components in a supply chain management system as an example.

Please refer to Figure 5, which is a schematic diagram of the Part code splitting requirements in an application scenario of differentiated supply of manufacturing devices provided by this application. In the device supply shown in Figure 5, the device Part 500 with Part code 12XXXXXX includes four different models, namely Model A, Model B, Model C and Model D. By managing the origin difference 501, it is split into product BOM Part with Part code 12XXXXX1, and the available models only include Model B, Model C and Model D; by managing the environmental protection regulations difference 502, it is split into device Part with Part code 12XXXXX2, and the available models only include Model D; by managing the process difference 503, it is split into device Part with Part code 12XXXXX3, and the available models only include Model A. With the continuous development of the supply chain management system, the constraints of the supply scenario are becoming more and more complex, and the number of split Parts coded as 12XXXXXX will continue to increase. In the application scenario of differentiated supply of manufacturing devices, devices that meet the same R&D and design requirements have differences in management and control dimensions due to differences in management origin, environmental regulations, processes and other factors, and need to be split into multiple codes. As a result, buyers/suppliers in the supply chain are unable to aggregate and manage complex manufacturing device demands, and cannot promptly correct and adjust complex manufacturing device substitution relationships to implement physical substitution solutions for complex manufacturing devices.

Please refer to Figure 6, which is a schematic diagram of a method provided by the present application for solving the problem of device supply in a differentiated scenario through a Part/BOM coding relationship management method. The specific steps for implementing the solution are as follows:

S201: Create hat codes according to business needs.

When building a Part replacement group, create a hat code to express the business needs and control dimensions met by the Part replacement group represented by the hat code, and then connect multiple sub-codes with the same control dimensions to the hat code to build a Part replacement group. The business needs for building a Part replacement group can be caused by changes in management origin, environmental regulations, and process changes, or changes in other control dimensions in some BOM relationships. As shown in Figure 6, the hat code is set to 12XXXXXX, which is used to refer to a batch of devices with the same control dimensions.

This step is included in step S101 of the Part/BOM relationship management method. For the relevant concepts of creating hat codes, please refer to the relevant description of S101.

S202: Assign subcodes to the Parts, and construct a Part substitution group by connecting the subcodes and the hat codes.

After the hat code is generated, according to the business needs of the determined Part replacement group, one or more Parts that meet the hat code are collected, and a code is assigned to each Part as a sub-code of the hat code. The hat code is used as the convergence point of the Part replacement group to connect the one or more sub-codes to form a Part replacement group. The sub-codes that construct the Part replacement group are required to have the same management and control dimensions, that is, the same functional specifications, interface dimensions, appearance materials, and processes.

The control dimensions of each sub-code in the Part substitution group are the same, so they can be substituted for each other. As shown in Figure 6, the Part substitution group includes a hat code and four sub-codes, each of which refers to a type of Part, namely Model A, Model B, Model C, and Model D.

This step is included in step S101 of the Part/BOM relationship management method. For the relevant concepts of building a Part replacement group, please refer to the relevant description of S101.

S203: Use the hat code as the sub-item code of the BOM to build a BOM relationship.

After constructing the Part substitution group, a BOM relationship is formed by creating a BOM parent item code and using the hat code in the Part substitution group as the sub-item code in the BOM relationship. In other possible embodiments, the number of sub-item codes connected to the parent item code in the BOM relationship can also be one or more. Due to the differentiated supply requirements of devices, the hat code in the generated Part substitution group relationship can be applied to multiple BOMs. As shown in Figure 6, in the BOM relationship, the sub-item code includes not only the hat code coded as "12XXXXXX", but also other sub-item codes such as "label" and "software" that do not include the substitution group structure.

When the hat code in the Part alternative group is connected with the parent code and a BOM relationship is established, you can set whether the Part alternative group enables sub-coding in the BOM by setting the "Whether to Enable Sub-coding" property of the hat code.

This step corresponds to step S102 of the Part/BOM relationship management method. For the relevant concepts of building a BOM relationship, please refer to the relevant description of S102.

S204: Setting the sub-code attribute of the BOM sub-item Part alternative group to determine the sub-code enabled by the alternative group in the corresponding BOM.

By locking the Part substitution group with the hat code as the identifier, the subcodes of the BOM sub-item Part substitution group in all applied BOM relationships of the hat code in the Part substitution group are identified, and according to the "whether enabled in BOM" attribute identifier of each subcode, it is identified whether the Part substitution group enables the subcode in the BOM sub-item Part substitution group. When the attribute identifier is "enabled", the Part substitution group enables the corresponding subcode in the BOM sub-item Part substitution group, and when the attribute identifier is "disabled", the Part substitution group does not enable the corresponding subcode in the BOM sub-item Part substitution group.

In order to meet the business needs of BOM, when the Part substitution group is adopted by different BOM relationships, the hat coding attributes and sub-coding attributes of the Part substitution group adopted by different BOM relationships are independently set to determine whether the above coding attributes are enabled in the corresponding BOM relationship. In different BOM relationships, the coding structure of the Part substitution group with the same hat coding is consistent, but the coding attributes of the hat coding and sub-coding need to be set independently, and the coding attribute settings between the BOM relationships that apply the Part substitution group do not affect each other.

This step corresponds to step S103 of the Part/BOM relationship management method. For the concepts related to setting the hat coding attribute and sub-coding attribute in the BOM relationship, please refer to the relevant description of S103.

Next, we will take the application scenario of introducing a new manufacturer model MPN under the device code as an example to introduce the specific application of the Part/BOM coding relationship construction method shown in this application. The second embodiment shows the Part/BOM coding relationship construction method shown in this application in the case of a change in the Part replacement group, which has the functional characteristics of supporting the rapid introduction of device replacement.

Please refer to Figure 7, which is a schematic diagram of the demand for new manufacturer models for device supply provided by this application. As shown in Figure 7, before introducing a new manufacturer "Model E", the device code "12XXXXXX" must undergo device replacement testing and verification. After the newly added manufacturer "Model E" passes the replacement test verification of each product BOM, the code "12XXXXXX" can add the manufacturer "Model E", and the product BOM that does not pass the test needs to be processed by splitting the new code.

Since there are usually dozens or hundreds of product BOMs to be verified, it takes a long time to complete the testing or technical evaluation of all BOMs before the final replacement conclusion can be drawn. At this time, some product lines have a short test cycle, and the demand for quick reference of the device is either not met or can only be solved by splitting the code, which increases the complexity of code replacement management.

Please refer to Figure 8, which is a schematic diagram of a method provided by the present application for solving the problem of quickly adding new manufacturer models to the device supply through the Part/BOM coding relationship management method. As shown in Figure 8, the Part/BOM coding relationship management method shown in the present application can make the replacement verification process of different devices relatively independent, so that product lines with small batch test cycles can be put into production quickly without having to wait for all verification results to appear before uniformly modifying the BOM. The specific solution implementation steps are as follows:

S301: Create a sub-code according to the new manufacturer model and hat code.

In the embodiment shown in the present application, the Part substitution group already exists and has even been applied to one or more BOM relationships and put into production. Due to changes in business needs, the Part substitution group is changed. The embodiment shown in the present application involves changes in the Part substitution group, which requires the creation of a generated sub-code and the addition of it to the existing Part substitution group.

In the application scenario of the new manufacturer model shown in this application, a sub-code corresponding to the hat code is generated according to the new manufacturer model selection and the Part control dimension represented by the hat code. As shown in Figure 8, there is an existing hat code "12XXXXXX", and a sub-code "12XXXXXX5" is generated according to the same control dimension and connected to the new manufacturer model "Model E".

In the embodiment of the present application, the newly added manufacturer model is unique and named "Model E", and each sub-code in the Part replacement group is mounted with a corresponding manufacturer model (MPN), so only one new sub-code is created. It can be understood that the present application is only used as an example. Since each sub-code is connected to a manufacturer model, in other possible embodiments, the number of newly added manufacturer models can be more, the new sub-code can be mounted with one or more manufacturer models, and the newly added manufacturer model can also be mounted under the existing sub-code in the Part replacement group, without limitation.

S302: adding the newly added sub-code to the corresponding Part replacement group using the hat code as an identifier.

As shown in FIG8 , the sub-code “12XXXXXX1” is connected to the hat code “12XXXXXX”, and the “Model E” representing the newly added manufacturer model is added to the replacement group corresponding to the hat code to construct the Part replacement group of the newly added manufacturer model.

The update operation of the Part replacement group does not need to be verified before the product replacement conclusions are included in the BOM, which can effectively add the start time of the manufacturer or sub-code in the BOM.

S303: Searching for a BOM list with enabled sub-codes by using the hat code as an identifier.

As shown in FIG8 , in an embodiment of the present application, the Part substitution group has been enabled in two BOMs, and the corresponding Part substitution groups in the two BOMs are updated with the hat code as an identifier to update the BOM coding structure. In other possible embodiments, the number of BOMs to which the Part substitution group has been applied can be less or more. As shown in FIG8 , in the BOM relationship, the sub-item coding includes not only the hat code coded as “12XXXXXX”, for example, but also other sub-item codes such as “label” and “software” that do not include the substitution group structure.

For each BOM that has completed the Part Alternative Group update, the "Enabled in BOM" attribute of the sub-code corresponding to the newly added manufacturer model will be set to "Not Enabled" by default before the corresponding alternative verification is completed.

S304: Determine the attribute value of the sub-code in the BOM sub-item Part replacement group according to the alternative verification result of the manufacturer model.

After each BOM completes the substitutability verification of the new manufacturer model, by setting the "Whether to Enable in BOM" attribute of the sub-code in the BOM sub-item Part substitution group, you can determine whether the new manufacturer model is enabled in the corresponding BOM sub-item Part substitution group. Through the BOM sub-item Part substitution group, there is no need to wait for all BOMs using the hat code to complete the substitutability verification before uniformly updating the BOM list, while minimizing the management complexity of the Part substitution relationship caused by the Part code split.

It can be understood that this embodiment only introduces the situation where the addition of manufacturer models leads to the addition of new sub-codes. In other possible embodiments, due to changes in business needs and management dimensions, there will be deletions, modifications, invalidations, etc. of sub-codes in the Part replacement group. Therefore, corresponding operations are required for each sub-code and coding attribute in the BOM sub-item Part replacement group. Among them, the above operations include performing one or more operations of adding, deleting, and modifying the sub-code or sub-code attribute without changing the hat code of the Part replacement group. When the Part replacement group does not change, when the BOM sub-item Part replacement group changes, only the sub-codes in the BOM sub-item Part replacement group are corrected, and one or more operations such as deletion, modification, and invalidation are performed on the corresponding sub-codes.

Refer to Fig. 9, which is a schematic diagram of a Part/BOM coding relationship management device provided by the present application. A Part/BOM coding relationship management device of this embodiment includes: a replacement group construction module 901, a BOM relationship construction module 902, and a BOM sub-item replacement group construction module 903.

The alternative group construction module 901 is used to generate a corresponding hat code through the control dimension of a certain Part, and to connect each of the sub-codes in this group with the corresponding hat code to construct a Part alternative group that can be applied to different BOM relationships. In other possible cases, it is also used to implement the addition, deletion, modification and query operations on the sub-codes or hat codes in the Part without changing the control dimension of the existing Part alternative group. Through the above operations, the alternative group construction module 901 can realize the construction of a Part alternative group for application to different BOMs as shown in step S101.

The replacement group construction module 901 is also used to screen out multiple sub-codes with the same functional specifications, the same interface size, the same appearance material and the same process according to the principle of the same control dimension, so that the hat code has a matching relationship with the multiple sub-codes. Since the multiple sub-codes have the same control dimension, the sub-codes are replaceable. In other possible cases, it is used to implement the addition, deletion, modification and query operations of the sub-codes or hat codes in the Part replacement group by modifying the control dimension of the generated Part replacement group, and to maintain the control dimension of the Part replacement group according to factors such as manufacturing process, process route, device specifications, cost accounting, inventory management, etc., so as to dynamically adjust the principles of adding or deleting sub-codes within the group.

The BOM relationship construction module 902 is used to generate a parent item code covering the manufacturing process, process route, component structure and other elements of the BOM, and to associate one or more sub-item codes of product elements such as the manufacturing process, process route, and device specifications represented by the BOM according to the parent item code. Through the above operations, the BOM relationship construction module 902 can realize the construction of a BOM relationship including a parent item code and one or more sub-item codes as shown in S102.

The BOM relationship construction module 902 is also used to set and change the sub-item code associated with the parent item code of the BOM. Among them, the sub-item code can be a hat code or a sub-code. When the sub-item code is a hat code, it means that the sub-item code is a group of multiple sub-codes with a substitutable relationship corresponding to the hat code. At this time, the Part substitution group represented by the hat code and the corresponding multiple sub-codes is called the BOM sub-item Part substitution group. In this BOM, the attribute of "whether to enable sub-coding" is set to "enabled" to open the sub-coding level of the Part substitution group represented by the hat code, otherwise it is set to "not enabled". When the sub-item code is a sub-code, the attribute of "whether to enable sub-coding" of the sub-code of the sub-item code defaults to "not involved".

The BOM sub-item substitution group construction module 903 is used to construct and maintain the coding structure and coding attributes in the BOM sub-item Part substitution group when the hat code of the Part substitution group is used as the sub-item code in the BOM relationship. Among them, the "whether to enable in BOM" attribute is set for each sub-code. When the sub-code attribute is selected as "enabled", the corresponding sub-code in the Part substitution group can be used in the BOM. Conversely, when the sub-code attribute is selected as "disabled", the corresponding sub-code in the Part substitution group cannot be used in the BOM, which facilitates the flexible replacement of sub-codes and the flexible use of Part substitution groups.

The BOM sub-item substitution group construction module 903 is also used to provide configurable, extensible, and deletable coding attributes for each sub-code of the Part substitution group in the BOM, supporting the user of the device of this application to set, modify, expand, and delete corresponding business attributes according to different business scenarios. Through the above operations, the BOM sub-item substitution group construction module 903 can realize the construction of the BOM sub-item Part substitution group relationship as shown in S103.

For the sake of simplicity, a detailed description of a Part/BOM coding relationship management device of this embodiment can be specifically referred to Figures 3 to 8 and the related descriptions of steps S101 to S103, steps S201 to S204, and steps S301 to S304. Each module in the Part/BOM coding relationship management device shown in this embodiment can be located in different electronic computing devices and connected through a cloud network.

Refer to Figure 10, which is a schematic diagram of the structure of an electronic computing device provided by the present application. The data processing device of this embodiment includes: one or more first processors 1010, a data collector 1020, a communication interface 1030, an external memory 1040 and a bus 1050. Among them, the first processor 1010, the data collector 1020, the communication interface 1030, and the external memory 1040 can be connected through the bus 1050.

The data collector 1020 is used to collect relevant data generated during the construction of various Part/BOM coding management relationships in the method described in S101 to S103, and is used for data acquisition between various modules in the Part/BOM information architecture.

The first processor 1010 includes one or more general-purpose processors, wherein the general-purpose processor can be any type of device capable of processing electronic instructions, including a central processing unit (CPU), a microprocessor, a microcontroller, a main processor, a controller, and an ASIC (Application Specific Integrated Circuit), etc. The first processor 1010 executes various types of digital storage instructions, such as software or firmware programs stored in the external memory 1040, which enables the data processing device to provide a wide variety of services. For example, the first processor 1010 can execute programs or process data to perform at least a portion of the methods discussed herein.

The communication interface 1030 may be a wired interface (eg, an Ethernet interface) for communicating with other data processing devices or users, and for implementing a Part/BOM coding relationship management method. For related concepts, please refer to the detailed introduction described above and will not be repeated here.

The external memory 1040 may include a volatile memory, such as a random access memory (RAM); the memory may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD). The memory may also include a combination of the above-mentioned types of memory. The external memory 1040 may store program code and program data.

The first processor 1010 can be used to execute the steps described in steps S101 to S103, steps S201 to S204, and steps S301 to S304 by calling the program code in the external memory 1040 to implement the Part/BOM coding relationship management method. For the sake of simplicity, the detailed introduction of this embodiment can be specifically referred to Figures 3 to 8 and related descriptions.

Although the present invention describes functions performed by certain virtual components and physical entities, in a cloud service system application scenario, some or all of the above-mentioned encoding relationship management process may be distributed among multiple virtual components and entities, and one or more instances of the process may be executed on a distributed system, a virtual machine, and one or more cloud service systems.

The present application provides a non-transitory computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, all steps of the above-mentioned target reporting method are implemented. For example, when the processor executes the computer program, the processes of steps S101 to S103, steps S201 to S204, and steps S301 to S304 and related operations are implemented.

The computer software product is stored in a storage medium, including several instructions for making a computer device perform all or part of the steps of the method described in each embodiment of the present application. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, cloud service center or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server, cloud service center or data center.

The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media, or a cloud storage resource provided by a cloud server. The available medium may be a magnetic medium (e.g., a floppy disk, a storage disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state storage disk, Solid State Disk, SSD), etc.

In addition, when the logic instructions in the external memory 1040 shown in FIG10 can be implemented in the form of a software functional unit and sold or used as an independent product, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product.

The present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, all the steps of the above-mentioned target reporting method are implemented. For example, when the processor executes the computer program, the processes of steps S101 to S103, steps S201 to S204, and steps S301 to S304 and related operations are implemented.

The embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application is described in detail with reference to the above embodiments, a person skilled in the art should understand that the technical solutions described in the above embodiments can still be modified, or some of the technical features can be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims (30)

1. A coding relationship management method, comprising:

constructing a part replacement group, wherein the part replacement group comprises a cap code and a plurality of sub-codes with the same management and control dimension, and the cap code is connected with the plurality of sub-codes;

Building a bill of material (BOM) relation, wherein the BOM relation comprises a parent item code and one or more child item codes, the child item codes comprise the cap code and the child code, and the parent item code is connected with the child item codes;

setting the attribute of the sub item codes in the BOM relation, wherein the attribute of the sub item codes comprises determining whether the part substitution group corresponding to the sub item codes is started in the BOM relation;

And setting the attribute of the plurality of subcodes in the BOM sub-item part substitution group relation, wherein the attribute of the plurality of subcodes comprises determining whether to enable the corresponding subcodes in the BOM sub-item part substitution group relation.

2. The method of claim 1, wherein the constructing a replacement set of parts comprises:

creating a plurality of codes, and constructing the part replacement group according to the codes, wherein the code type of the codes comprises one cap code and a plurality of sub-codes;

The cap code cannot be used as a subcode in the other part replacement set, and the subcode cannot be used as a cap code in the other part replacement set;

within the component replacement set, each subcode can be connected to only one cap code and not to other subcodes or other cap codes.

3. The method of claim 1, wherein the same control dimension among the plurality of subcodes in the part replacement set includes identical functional specifications, identical interface dimensions, identical appearance materials and identical processes among the plurality of parts represented by the plurality of subcodes;

with the same regulatory dimension between the plurality of subcodes of the part replacement set, there is an alternative relationship between the plurality of subcodes.

4. The method of claim 1, wherein the subcode comprises the cap code and the subcode, comprising:

when the sub item code is a cap code, the cap code and the plurality of sub codes correspondingly connected form a BOM sub item part substitution group;

in the case where the child code is a child code, the child code is included in the BOM relationship through a connection with the parent code.

5. The method of claim 4, wherein in the event that the child code is a child code, the child code is directly concatenated with the parent code to construct the BOM relationship without concatenating with the cap code and other child codes.

6. The method of claim 4, wherein the BOM child part replacement set does not contain the parent code in the case where the child code is a cap code, the cap codes in the BOM child part replacement set only concatenate the plurality of child codes having the same governance dimension.

7. The method of any one of claims 1 to 6 wherein said component replacement set is applicable to a plurality of said BOM relationships to construct said BOM sub-item component replacement set, said component replacement set being identical in both said cap code and said plurality of sub-codes applied to different of said BOM relationships.

8. The method according to claim 7, wherein in the case where the component replacement group is applied to a plurality of the BOM relations, the attribute of the cap code and the attribute of the subcode of the BOM sub-component replacement group are set independently according to business requirements among the BOM relations, and the setting of the code attribute values between the BOM relations to which the component replacement group is applied does not affect each other.

9. The method of claim 8, wherein the attribute of the subcode connected to the cap code is enabled only if the attribute of the cap code of the BOM sub-item part replacement set is enabled subcode.

10. The method according to claim 8 or 9, wherein when the attribute of the cap code of the BOM sub item part replacement group is an enable subcode, the attribute of at least one subcode connected to the cap code is set to enable.

11. The method according to any one of claims 1 to 10, wherein after constructing the component replacement set, the method further comprises:

and performing a altering operation on the component replacement set, wherein the altering operation includes performing one or more of an add-drop-check on the subcode or the subcode attribute without altering the cap-code of the component replacement set.

12. The method of claim 11, wherein, before the BOM relationship changes,

When the change is required to be performed on the part replacement group, performing replacement verification of the change on the part replacement group on the BOM relation related to the part replacement group;

And when the replacement verification in the part replacement group passes, executing the change operation on the BOM sub-item part replacement group related to the part replacement group, and updating and setting the subcode attribute of the changed BOM sub-item part replacement group to determine whether the subcode is enabled in the corresponding BOM sub-item part replacement group.

13. The method of claim 4, wherein after constructing the bill of materials BOM relationship, the method further comprises:

And performing a change operation on a child code connected with the parent code, wherein the change operation comprises one or more operations of performing a pruning check on the attribute of the child code.

14. The method of claim 13, wherein, before the BOM relationship is changed,

When the child code connected with the parent code needs to make the change, executing substitution verification of the change on the BOM relation of the child code connected with the parent code by the child code connected with the parent code;

and when the replacement verification in the BOM relation passes, executing the changing operation on the child code connected with the parent code in the BOM relation.

15. The coding relation management device is characterized by comprising a substitution group construction module, a BOM relation construction module and a BOM sub-item substitution group construction module;

the replacement group construction module is used for constructing a part replacement group, wherein the part replacement group comprises a cap code and a plurality of sub-codes with the same management and control dimension, and the cap code is connected with the plurality of sub-codes;

The BOM relation construction module is used for constructing a bill of materials BOM relation and setting the attribute of an extensible child item code, wherein the BOM relation comprises a parent item code and one or more child item codes, the child item codes comprise the cap code and the child code, and the parent item code is connected with the cap code;

The BOM relation construction module is further configured to set an encoding attribute of the cap code if the child code of the BOM relation is a cap code, where the encoding attribute of the cap code includes determining whether to enable the part replacement group corresponding to the cap code in the BOM relation;

The BOM sub item substitution group construction module is used for constructing a BOM sub item part substitution group, wherein the coding attributes of the plurality of sub codes in the BOM sub item part substitution group are set, and the coding attributes of the sub codes comprise determining whether the corresponding sub codes are started in the BOM relation.

16. The apparatus of claim 15, wherein the replacement set construction module is configured to construct a replacement set of parts, comprising:

creating a plurality of codes, and constructing the part replacement group according to the codes, wherein the code type of the codes comprises one cap code and a plurality of sub-codes;

The cap code cannot be used as a subcode in the other part replacement set, and the subcode cannot be used as a cap code in the other part replacement set;

within the component replacement set, each subcode can be connected to only one cap code and not to other subcodes or other cap codes.

17. The apparatus of claim 15, wherein the plurality of subcodes have the same control dimensions in the component replacement group module, including identical functional specifications, identical interface dimensions, identical appearance materials, and identical processes between the plurality of components represented by the plurality of subcodes;

with the same regulatory dimension between the plurality of subcodes of the part replacement set, there is an alternative relationship between the plurality of subcodes.

18. The apparatus of claim 16, wherein in the BOM relation construction module, the child code comprises the cap code and the child code, comprising:

When the sub item code is a cap code, the cap code and the plurality of sub codes correspondingly connected form a BOM sub item part substitution group to act on the BOM relation;

in the case where the child code is a child code, the child code is included in the BOM relationship through a connection with the parent code.

19. The apparatus of claim 18, wherein the BOM relationship construction module is further configured to, in the event that the child code is a child code, construct the BOM relationship directly with the parent code without interfacing with the cap code and other child codes.

20. The apparatus of claim 18, wherein the BOM relation building module is further configured to, when the child code is a cap code, the BOM child part replacement set does not contain the parent code, the cap codes in the BOM child part replacement set only concatenate the plurality of child codes having the same regulatory dimension.

21. The apparatus of any one of claims 15 to 20, wherein the BOM sub-item part replacement set construction module is further configured to apply the part replacement set to a plurality of the BOM relationships to construct the BOM sub-item part replacement set, the part replacement set being identical in both the cap code and the plurality of sub-codes applied to different BOM relationships.

22. The apparatus of claim 21, wherein the BOM sub-component replacement set module is further configured to independently set the hat-coded attribute and the sub-coded attribute of the BOM sub-component replacement set in each of the BOM relationships according to business requirements if the component replacement set is applied to a plurality of the BOM relationships.

23. The apparatus of claim 22, wherein the BOM sub-item part replacement set module is further configured to set an attribute of the subcode connected to the cap code to enabled only if the attribute of the cap code of the BOM sub-item part replacement set is enabled subcode.

24. The apparatus of claim 22 or 23, wherein the BOM sub-item part replacement set module is further configured to set an attribute of at least one subcode connected to the cap code to enabled if the attribute of the cap code of the BOM sub-item part replacement set is enabled subcode.

25. The apparatus of any one of claims 15 to 24, wherein, after the component replacement set is constructed,

The substitute group construction module is further configured to perform a change operation on the part substitute group, where the change operation includes performing one or more operations of adding, deleting, and modifying the subcode or the subcode attribute without changing the cap code of the part substitute group.

26. The apparatus of claim 25 wherein, before the BOM relationship changes,

When the change is required to be performed on the part replacement group, performing replacement verification of the change on the part replacement group on the BOM relation to which the part replacement group has been applied;

and when the replacement verification in the part replacement group passes, executing the change operation on the BOM sub-item part replacement group to which the part replacement group is applied, and updating and setting the subcode attribute of the changed BOM sub-item part replacement group to determine whether the subcode is enabled in the corresponding BOM sub-item part replacement group.

27. The apparatus of claim 26, wherein the substitute group construction module is to perform a change operation on a child code connected to the parent code after constructing a bill of materials BOM relationship, wherein the change operation comprises performing one or more of an add-drop check on an attribute of the child code.

28. The method of claim 27, wherein, before the BOM relationship is changed,

When the child code connected with the parent code needs to make the change, executing substitution verification of the change on the BOM relation of the child code connected with the parent code by the child code connected with the parent code;

And when the replacement verification in the BOM relation is passed, the replacement group construction module executes the changed operation on the child code connected with the parent code in the BOM relation, and sets the changed child code attribute which is enabled in the BOM relation or not.

29. An electronic computing device comprising a memory and a processor, wherein the memory stores instructions that, when executed by the processor, enable the method of any one of claims 1 to 14 to be carried out.

30. A non-volatile storage medium comprising a plurality of instructions capable of implementing the method of any one of claims 1 to 14 when executed by an electronic device.