CN118863761A - Method and system for managing coding relationship - Google Patents

Abstract

The application provides a coding relationship management method and a coding relationship management system. First, a part replacement group is constructed, wherein the part replacement group comprises a cap code and a plurality of subcodes with the same control dimension, and the cap code is connected with the plurality of subcodes. And secondly, building a bill of material BOM relation, wherein the BOM relation comprises a father item code and one or more child item codes, the child item codes comprise a cap code and a child code, and the father item code is connected with the child item codes. And setting the attribute of the sub-item codes in the BOM relation again, 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 finally, setting the attribute of a 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. Through the coding relationship management method, BOM relationship can realize the functions of flexible material supply, reuse sharing and layered application.

Description

Method and system for managing coding relationship

Technical Field

The application belongs to the technical field of material management, and particularly relates to a method and a system for managing coding relations.

Background

In recent years, with the continuous development of the supply chain industry to globalization, the scale and complexity of material supply chains are remarkably improved, and the export control requirements on technology and material products are increasingly increased among various countries. Meanwhile, due to the rapid development of the supply chain industry, the material management scheme is gradually complicated, the product replacement period is gradually shortened, the variety of optional components of the product is gradually increased, and the trend is that the coding library of the bill of materials is gradually huge. With the continuous development of information and internet technology and the continuous increase of the supply demands of new products, the demand for creating a large amount of bill of materials has led to the continuous rise of the costs of bill of materials generation, maintenance and management.

Disclosure of Invention

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

In a first aspect, a coding relationship management method is provided. First, a part replacement set is constructed, wherein the part replacement set comprises a cap code and a plurality of subcodes with the same management dimension, and the cap code connects the plurality of subcodes. Secondly, building a bill of material BOM relation, wherein the BOM relation comprises a father item code and one or more child item codes, the child item codes comprise the cap code and the child code, and the father item code is connected with the child item codes. And 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 enabled or not in the BOM relation. And finally, 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. By the coding relationship management method, BOM relationship with the functional characteristics of supporting flexible material supply, reuse sharing and layered application can be realized.

Next, a specific method of constructing the component replacement set will be described. First, a plurality of codes are created, and the part replacement group is constructed according to the codes, wherein the code type of the codes comprises one cap code and a plurality of sub-codes. Second, the cap code cannot be used as a subcode in the other component replacement set, and the subcode cannot be used as a cap code in the other component replacement set. Finally, each subcode can be connected to only one cap code and not to the other subcodes or other cap codes within the replacement set of parts. By limiting the coding structure of the part replacement group, the part replacement group can be ensured to be a coding structure taking cap coding as the center, so as to realize a BOM coding relation of layered application.

In the component replacement group, the same control dimension between the plurality of subcodes includes the same functional specification, the same interface size, the same appearance material and the same process 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.

In the BOM relation, the child code includes the cap code and the child code. 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 that the child code is a child code, the child code is incorporated into the BOM relationship by connection with the parent code to implement a hierarchically applied BOM code relationship.

In a general embodiment, in the case that the child code is a child code, the child code directly links with the parent code to construct the BOM relationship, and does not link with the cap code and other child codes. When the child code is a cap code, the BOM child part replacement set does not contain the parent code, and cap codes in the BOM child part replacement set connect only the plurality of child codes having the same management dimension.

In a general embodiment, the part replacement group may be applied to a plurality of BOM relationships to construct the BOM sub-part replacement group, where the cap codes and the plurality of sub-codes applied to different BOM relationships in the part replacement group are identical, so that the functional characteristics of reuse and sharing of the code group may be realized.

When the part replacement group is applied to a plurality of BOM relations, the attribute of the cap code and the attribute of the subcode of the BOM sub part replacement group are independently set in each BOM relation according to service requirements, and the setting of the code attribute values between the BOM relations of the part replacement group is not affected. By setting the coding values of each code of the part replacement group in different BOM relations, the functional characteristics of reuse and sharing of the coding group are realized while the construction requirements of different BOM relations are met.

In a general embodiment, the attribute of the subcode connected to the cap code may be set to enable only if the attribute of the cap code of the BOM sub-item part replacement group is enable subcode. When the attribute of the cap code of the BOM sub-item part replacement group is an enabling sub-code, the attribute of at least one sub-code connected with the cap code is set to be enabling.

In a general embodiment, a modification operation may be performed on the component replacement set after the component replacement set is constructed, where the modification operation includes one or more operations of performing an add-drop-out check on the subcode or the subcode attribute without changing the cap code of the component replacement set. Through the change of the part replacement group, the functional characteristics of flexible material supply in the BOM relation can be realized.

In a general embodiment, when the change is required to be made to the component replacement group before the BOM relation changes, replacement verification is performed to make the change to the component replacement group on the BOM relation to which the component replacement group has been applied. And when the replacement verification in the BOM relation of the part replacement group is passed, executing the change operation on the BOM sub-part replacement group associated with the application, and updating and setting the sub-coding attribute of the changed BOM sub-part replacement group to determine whether the sub-coding is enabled in the BOM relation of the corresponding BOM sub-part replacement group. The replacement verification result is updated in time according to the specific BOM relation, so that the BOM can rapidly correspond to the material change and update speed, and the functional characteristics of flexible material supply are realized.

In the case where the child code of the BOM relationship contains a child code, performing a change operation on the child code connected to the parent code, wherein the change operation includes performing one or more of a pruned check on an attribute of the child code. And executing substitution verification of the change on the BOM relation of the child code connected with the parent code, wherein the child code connected with the parent code is applied to the BOM relation before the change on the BOM relation. And when the substitution verification in the BOM relation passes, executing the changing operation on the child code connected with the parent code in the BOM relation, and updating and setting the child code attribute in the BOM relation after the changing.

In a second aspect, an encoding relationship management apparatus is provided, including a substitution group construction module, a BOM relationship construction module, and a BOM sub-item substitution group construction module. First, the substitute group construction module is used for constructing a part substitute group. 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. And secondly, the BOM relation construction module is used for constructing a bill of materials BOM relation and setting the attribute of the extensible sub item code. Wherein the BOM relation comprises a parent code and one or more child codes, the child codes comprise the cap code and the child codes, and the parent code is connected with the cap code. And the BOM relation construction module is further used for setting the coding attribute of the cap code when the sub item code of the BOM relation is the cap code. Wherein the coding attribute of the cap code comprises determining whether the part replacement group corresponding to the cap code is enabled in the BOM relation; and finally, the BOM sub item substitution group construction module is used for constructing a BOM sub item part substitution group. Wherein, setting the coding attribute of the plurality of subcodes in the BOM sub item part substitution group, wherein the coding attribute of the subcodes comprises determining whether the corresponding subcodes are enabled in the BOM relation. Through the coding relationship management method, the BOM relationship with the functional characteristics of supporting flexible material supply, reuse sharing and layered application can be realized.

The replacement set construction module, when constructing a replacement set of parts, generally includes the following steps. First, a plurality of codes are created, and the part replacement group is constructed according to the codes, wherein the code type of the codes comprises one cap code and a plurality of sub-codes. Second, the cap code cannot be used as a subcode in the other component replacement set, and the subcode cannot be used as a cap code in the other component replacement set. Finally, in the part replacement set, each subcode can be connected with only one cap code and cannot be connected with other subcodes or other cap codes. By limiting the coding structure of the part replacement group, the part replacement group can be ensured to be a coding structure taking cap coding as the center, so as to realize a BOM coding relation of layered application.

In the component replacement group module, the plurality of subcodes have the same control dimension, and the component replacement group module comprises the same functional specification, the same interface size, the same appearance material and the same process among 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.

In the BOM relation construction module, the child code includes the cap code and the child code. 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.

In a general embodiment, the BOM relation building module is further configured to, when the child code is a child code, build the BOM relation directly with the parent code, without connecting with the cap code and other child codes. The BOM relation construction module is further used for enabling the BOM sub-item part replacement group to not contain the parent item code under the condition that the sub-item code is the cap code, and the cap codes in the BOM sub-item part replacement group are only connected with the plurality of sub-codes with the same management and control dimension.

The BOM sub-item part replacement group construction module is further configured to apply the part replacement group to a plurality of BOM relationships to construct the BOM sub-item part replacement group, where the cap codes and the plurality of subcodes applied to different BOM relationships form the same part replacement group. It can be appreciated that the coding relationship of a same component replacement set can implement the functional feature of reuse sharing of the coding set by being applied to multiple BOM relationships.

The BOM sub-item part replacement group module is further configured to independently set, in the case that the part replacement group is applied to a plurality of BOM relationships, the hat encoded attribute and the sub-encoded attribute of the BOM sub-item part replacement group in each BOM relationship according to service requirements. By setting the coding values of each code of the part replacement group in different BOM relations, the functional characteristics of reuse and sharing of the coding group are realized while the construction requirements of different BOM relations are met.

The BOM sub-item part replacement group module is further configured to set an attribute of the subcode connected to the cap code to be enabled only when the attribute of the cap code of the BOM sub-item part replacement group is enabled subcode. The BOM sub-item part replacement group module is further configured to set, when the attribute of the cap code of the BOM sub-item part replacement group is an enabled subcode, an attribute of at least one subcode connected to the cap code to be enabled.

The replacement set construction module is further configured to perform a change operation on the replacement set of parts after the replacement set of parts is constructed. Wherein the altering operation includes performing one or more of a pruning check on the subcode or the subcode attribute without altering the cap code of the part replacement set. Through the change of the part replacement group, the functional characteristics of flexible material supply in the BOM relation can be realized.

When the change is required to be made to the component replacement group before the change of the BOM relation occurs, the replacement verification of the change is performed to the BOM relation to which the component 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. By updating the substitution verification result in time aiming at the specific BOM relationship, the BOM relationship can be enabled to rapidly correspond to the material change and updating speed, so that the functional characteristics of flexible material supply are realized.

After building the bill of materials BOM relationship, the substitution group building module is used for executing changing operation on the child code connected with the parent code, wherein the changing operation comprises one or more operations of adding, deleting and checking the attribute of the child code. The functional characteristics of flexible material supply in the BOM relation are realized through changing the part replacement group.

And executing substitution verification of the change on the BOM relation of the child code connected with the parent code, wherein the child code connected with the parent code is applied to the BOM relation before the change on the BOM relation. 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. The coding attribute of the part replacement group after the change is refreshed, so that the part replacement group after the change can be normally matched with the applied BOM relationship, and the functional characteristics of flexible material supply can be realized.

In a third aspect, an electronic computing device is provided, including a memory and a processor, where the memory stores instructions and the processor, when executing the instructions in the memory, is capable of implementing the method according to any embodiment of the first aspect.

In a fourth aspect, a non-volatile storage medium is provided, comprising a plurality of instructions capable of implementing the method as claimed in any of the embodiments of the first aspect, when executed by an electronic device.

Drawings

In order to more clearly describe the embodiments of the present application or the technical solutions in the background art, the following description will describe the drawings that are required to be used in the embodiments of the present application or the background art.

FIG. 1 is a schematic diagram of a conventional Part/BOM coding relationship management method provided by the present application;

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

FIG. 3 is a schematic diagram of a Part/BOM coding relationship construction method provided by the application;

FIG. 4 is a schematic diagram of a Part replacement set with identical regulatory dimensions provided by the present application;

fig. 5 is a schematic diagram of Part code splitting requirements in an application scenario of differential supply of manufacturing devices provided by the present application;

FIG. 6 is a schematic diagram of a solution to device provisioning implementation in a differentiated scenario through Part/BOM coding relationship management methods provided by the present application;

FIG. 7 is a schematic diagram of a device supply new manufacturer model requirement provided by the present application;

FIG. 8 is a schematic diagram of a method for managing Part/BOM code relationships to solve the problem of quick new manufacturer types of device provisioning;

FIG. 9 is a schematic diagram of a Part/BOM coding relationship management apparatus provided by the present application;

fig. 10 is a schematic structural diagram of an electronic computing device provided by the present application.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be clearly and completely described by means of implementation examples with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

In the description of the present application, unless explicitly defined otherwise, terms such as arrangement and the like should be construed broadly, and those skilled in the art can reasonably determine the specific meaning of the terms in the present application in combination with the specific contents of the technical scheme.

In the description of the present application, references to the terms "one embodiment," "some embodiments," "an exemplary embodiment," "an example," "a particular embodiment," "a particular coded number," or "some example," etc., mean that a particular feature or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

The related concepts related to the present application will be described separately.

Parts (hereinafter may be referred to as "Part"): the method refers to raw materials, semi-finished products, customer supplies, reworked products, spare parts, expenses, services, software, external cooperation parts, packaged virtual items and the like related to enterprise business activities. Is a unit oriented to research, sales, supply, manufacturing, purchasing, service, and financial accounting.

Bill of materials (billofmaterial, BOM): the elements reflecting the composition of the product materials can reflect the production process from raw materials to products through the parent-child item relationship, and are main data guiding sales, production, planning, purchasing, order, cost accounting and the like.

Manufacturer material number (manufacturerpartnumber, MPN): i.e., manufacturer model, refers to a unique identifier assigned by a manufacturer or vendor to the product it is making. It generally includes numbers, letters or symbols for distinguishing between products of the same type, same specification but different manufacturers or different batches, and facilitating tracking and identification in the links of purchasing, inventory management, production, etc. "factories" are "manufacturers" rather than "factories", and typically one "factory" may have multiple "factories" of the subordinate "

Part substitution group: that is, the component replacement set, comprising a cap code and a plurality of subcodes of the same functional specification, the same interface size, the same appearance material and the same process, allows the selection of the subcodes under the cap code for quotation, design selection, supply, manufacture, delivery, etc., based on business requirements.

Hat coding: the method is used for collecting a group of subcodes with the same functional specification, the same interface size, the same appearance material and the same process in the part replacement group.

Sub-coding: the coding method belongs to the coding of the same cap, but different part codes defined by different control dimensions. Controlling dimension: the method is characterized in that some key parameters of the bill of materials are managed and controlled to ensure the accuracy, feasibility and economy of production planning, including the number of parts, the specification of parts, the process route, cost accounting and inventory management. Through the effective management and control of the management and control dimensions, enterprises can realize the effective management and optimization of bill of materials, thereby improving the production efficiency and the product quality and reducing the cost and the inventory risk.

The "cap/subcode" attribute: to indicate whether the Part code is a member of the Part replacement group, and the position (cap code or subcode) in the Part replacement group.

BOM sub-item Part substitution group: the BOM sub item Part replacement group is a new relation generated after the two relations of the BOM and the Part replacement group are combined, and is used for solving the problem that the Part replacement group shares time difference different use scenes in all products. In addition to the objects that produce the relationship (BOM and Part replacement sets), the attributes that describe the relationship are also included, and the attributes of the BOM sub-Part replacement sets are configurable according to business scenario needs.

Whether the "BOM in enabled" attribute: for purposes of explaining whether each subcode in the Part replacement set is enabled in a particular BOM, it may be set to both an "enabled" and a "non-enabled" state.

Having described the related name concepts to which the present application relates, for the convenience of those skilled in the relevant art to understand the present application, a brief description will be made of the technical field and application background to which the present application is referred.

The Product Life cycle management system (hereinafter referred to as "PLM system") is an enterprise informatization tool for managing the whole process from Product development to design, manufacture, maintenance, retirement and the like, and comprises the support and management of the process of Product design, development, test, production, sales, marketing and the like, and can help enterprises to realize effective coordination and seamless connection of various links of Product development, process manufacture, after-sales service and the like. The PLM system mainly comprises subsystems such as product data management, process flow management, project collaborative management and the like, and reduces the time to market, the product quality and the development cost by managing the whole life cycle of the product and collaborative work.

After the product development and design stage of the enterprise is completed, the enterprise resource planning system can be used for realizing the release, production and use of the product. An enterprise resource planning system (ENTERPRISE RESOURCE PLANNING, hereinafter referred to as "ERP system") is a system that is mainly oriented to manufacturing industries, and develops an integrated enterprise resource planning management system for material resource management (logistics), human resource management (personnel flow), financial resource management (financial flow), and information resource management (information flow). The advent of EPR systems and the rapid development of computer information technology are indispensible, and the functions involved include not only conventional MRPII module (manufacturing, marketing, finance) applications, but also complementary applications such as supply chain management (SupplyChainManagement, SCM), sales and marketing, customer service, finance management, manufacturing management, inventory management, factory and equipment maintenance management, human resource management, report management, manufacturing execution system (ManufacturingExecutiveSystem, MES), workflow services and enterprise systems, factory cluster management, product quality management, laboratory management, material transportation management, process control interfaces, etc., as well as data acquisition interfaces, electronic communications, email, regulation and standards, project management, financial investment management, market information management, and process control.

The PLM system and the ERP system respectively serve different fields of an enterprise, however, in each stage of a product life cycle, the two systems can cooperate to support comprehensive enterprise management and production flow, and the production efficiency and management level of the enterprise are improved. The PLM system and the ERP system realize information sharing, data integration, flow coordination and collaborative analysis, so that data and documents related in the product design and development process can be integrated with the rest of business data, and better flow automation and data sharing are realized. The PLM system and the ERP system manage the product data in a unified way by a Part/BOM way. The Part/BOM management has important significance for realizing high-efficiency application of the PLM system and the ERP system and reducing the enterprise management cost.

The application is to introduce a Part/BOM coding relation management system, method and device. Enterprises generally adopt a mode of ' multiple manufacturers ' supply ' in order to ensure the safety and stability of a supply chain, avoid exclusive supply and the like. However, due to the influence of external environment, materials of different factories need to be differentially and finely managed based on factors such as production places, environmental protection regulations, processes and the like. Therefore, an effective Part/BOM technical scheme is needed, and the support business can support the continuous change of internal and external environment management and control in different business fields on the basis of continuously keeping the supply safety and stability and the advantages of multiple supplies.

Referring to fig. 1, fig. 1 is a schematic diagram of a conventional Part/BOM coding relationship management method according to the present application. The embodiment shown in fig. 1 is used to describe an existing Part/BOM coding relationship management method, including: part replacement management 110, BOM replacement management 120, part to MPN relationship management 130.

Part replacement management 110 is used to establish Part alternatives. Wherein Part replacement management 110 may establish a one-to-one alternative relationship between parts. For example, a Part encoded as 12XXXXX1 may be replaced with a Part encoded as 12XXXXX 2. When establishing the substitution relationship between Part and Part, substitution type, validation time, failure time may be specified. However, the relationships between the individual parts are not regrouped with explicit rules and are very scattered and cannot maximize the shared resources.

In the BOM replacement management 120, embodiments of the BOM replacement management at least include the following two types:

The first BOM sub-item substitution 121 adds all substitution Part encodings of a set of substitution relations to the BOM and maintains substitution policies, priorities, usage percentages, etc. in the substitution set. However, sub-item substitution relationships built in BOMs cannot be reused and shared by other BOMs. In the same BOM, each Part capable of replacing each other must be added to the BOM at the same time, and once the replacement relation in the Part replacement group changes, the BOM list also needs to be changed accordingly.

A second BOM sub-item substitution 122 maintains a Part code in the BOM as a BOM sub-item, establishes a set of substitute parts in substitution relation to the sub-item Part, which may maintain respective substitution numbers, priorities, etc. However, similar to the first approach, sub-item substitution relationships built in BOMs cannot be reused for sharing. Meanwhile, as the sub item serving as the BOM not only represents that the BOM design requirement is met, but also represents the specification of the specific materials delivered by some factories; when the manufacturer specification changes, the sub item code needs to be changed, and the BOM sub item substitution group relation is released accordingly.

Part and MPN relationship management 130 is used to establish a one-to-one or one-to-many relationship for Part and make model. Part to MPN relationship management 130 may relate manufacturer models that meet Part specification requirements to parts. Thus, when the Part specification requirement is satisfied with one manufacturer model, the Part and the manufacturer Model (MPN) establish a one-to-one relationship, and when the Part specification requirement is satisfied with a plurality of manufacturer models, the Part and the manufacturer Model (MPN) establish a one-to-many relationship. In the prior art, even though the specification requirements are the same, part of manufacturer models are not satisfied due to the differential control requirements, and the problem is solved by splitting codes. Therefore, the same specification requirements are caused, part codes are different, materials with manufacturer models are distributed to different Part codes to manage inventory objects, inventory cannot be fully shared on BOM of different products, and supply flexibility is reduced.

With the continuous development of information technology, the relationships among suppliers, manufacturers, retailers, factories, products, parts and differentiated application scenes are more and more complex, and the updating iteration speed is continuously increased. BOM is used as important data support for enterprise supply chain management, and the replacement of the management method by the existing BOM can cause the continuous increase of material redundancy and abandonment. Technical problems existing in the prior art are difficult to meet the requirements of the following application scenes:

1. The design specifications are the same, but because the differentiated management is split and combined into a plurality of codes, the substitution relation among the codes is not uniformly managed, the complicated device demand convergence can not be managed by purchasing, the complicated device substitution relation can be managed manually, and the manufacturing implementation device real object substitution is complicated. Therefore, the capability of decomposing actual manufacturer type material purchasing requirements and task order material receiving instructions after supporting centralized management based on Part substitution relation and BOM sub-item difference setting is needed.

2. When a new manufacturer model is introduced into the device code, the number of BOMs referring to the device code is large, and if the progress period difference of the product BOM for replacement verification is large, the product BOM which needs to be urgently verified cannot be supported to be switched first. There is therefore a need for a capability to support the validation of different manufacturer models based on different BOMs.

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

Referring to fig. 2, fig. 2 is a schematic diagram of a Part/BOM coding relationship management system according to the present application. As shown in FIG. 2, part/BOM coding 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 encoding 201, the management of Part contains Part encoding and an associated set of attribute information. The information contained in Part code 201 includes not only Part codes used to refer to parts, but also system association identifications involving Part/BOM management, including Product Lifecycle Management Systems (PLMs) and Enterprise Resource Planning Systems (ERPs). Part encoding 201 may associate Part replacement group 202, BOM relation 203, BOM sub-item Part replacement group 204.

Part substitution set 202 is used to describe a coding set consisting of a plurality of parts of the same regulatory dimension, including a cap code and a plurality of subcodes thereof having the same regulatory dimension. The same control dimension refers to the same functional specification, the same interface size, the same appearance material and the same process, and each subcode has an alternative relationship due to the same control dimension. Part replacement group 202 may be associated with Part encoding 201.

The BOM relation 203 is configured to set a parent code and a coding attribute and a coding relation of each child code connected to the parent code in the BOM relation. Wherein the subcode comprises a cap code and a subcode. And 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.

The BOM sub-item Part replacement group 204, when a sub-item code of a BOM relationship is a cap code, the Part replacement group corresponding to the cap code is referred to as a BOM sub-item Part replacement group. And setting the attribute of the plurality of sub-codes in the BOM sub-item Part substitution group relation, wherein the attribute of the plurality of sub-codes comprises determining whether to enable the corresponding sub-codes in the BOM sub-item Part substitution group relation. The BOM sub-item Part replacement group 204 may associate Part encodings 201 and BOM relationships 203.

Referring to fig. 3, fig. 3 is a schematic diagram of a Part/BOM coding relationship construction method according to the present application. The method provided by the application is used for constructing all or Part of the Part/BOM coding relation management system shown in figure 2. It will be appreciated that the Part/BOM code relationship management system constructed using the present embodiment is merely provided as a demonstration, and no limitation is made on specific attribute contents in the Part/BOM code relationship management system. The specific implementation steps are as follows:

S101: part substitution groups were constructed.

As shown in fig. 4, fig. 4 is a schematic diagram of a Part replacement set with the same control dimension provided in the present application. The Part substitution group comprises a cap code and a plurality of subcodes corresponding to the cap code and having the same functional specification, the same interface size, the same appearance material and the same process. As shown in FIG. 4, the regulatory dimensions of each subcode include one or more of sales and customers, manufacturing and inventory, purchasing, and the like.

For example, in the sales and customer regulatory dimension, the following application scenarios may be included:

1. The client interface does not need to distinguish differences, and internal reasons are divided to manage Part to set management and control dimensions;

2. Because of elements such as business, the client interface needs to separately manage Part, and the management and control dimension is avoided due to inconsistent single goods.

For example, in the manufacturing and inventory management dimension, the following application scenarios may be included:

1. The self-made Part and the purchase Part coexist due to the source difference to set a management and control dimension;

2. and setting a control dimension due to coexistence of homemade Part and homemade Part caused by device difference.

For example, in the management and control dimension of purchasing, materials of different factories are required to be managed due to the difference of application scenes such as trace components, production places, environmental protection regulations, processes and the like.

The Part replacement set allows selection of one or more subcodes under the cap code for quotation, design choice, supply, manufacture, delivery, etc., based on business requirements. The cap code is used by the business definition rules to aggregate (sub-codes of) a set of identical management dimensions.

The gist when constructing the Part substitution group includes:

1. the set code type identifies whether a code is a cap code or a subcode, or does not involve a code.

2. The type of code of a code cannot be either a cap code or a subcode.

3. The cap code and the subcode construct a Part substitution group relation, and the BOM relation is not allowed to be mounted under the cap code.

4. The coding rule of the subcode is limited according to the service requirement, and after the subcode is required to be disconnected from the cap code, the subcode can not be applied any more, and only one cap code is required to be allowed for the same subcode.

5. The cap code cannot be used as a subcode in other Part replacement sets, and the subcode cannot be used as a cap code in the other Part replacement sets;

6. Each subcode in the Part substitution group can only be connected with one cap code, and each subcode in the group has no direct connection relation.

The same control dimension of the sub-codes in the Part substitution group comprises the same functional specification, the same interface size, the same appearance material, the same process and the like. The control dimension of the sub-codes in the Part substitution group is edited through the coding attribute of the sub-codes according to the application scene and the service requirement difference of the Part substitution group, and the operation of adding, deleting and checking the control dimension is carried out; in the case where the sub-encodings of the Part replacement set have the same regulatory dimension, there is a relationship of mutual replacement between the sub-encodings in the Part replacement set.

S102: and constructing a BOM relation.

In the BOM relationship, a parent code and one or more child codes connected to the parent code are included. Wherein the type of sub-item code includes a cap code representing a Part substitution group, a sub-code not containing a Part substitution group relationship.

In the case where the child code is a cap code, the "whether child code is enabled" attribute of each cap code is set. The "whether subcode is enabled" attribute includes "enable/disable" and "do not involve" two states. Wherein "enable/disable" indicates whether a subcode of this cap code is enabled in the BOM and "not related" indicates that this code does not include subcodes. The parent code may be concatenated with one or more cap codes, and correspondingly, the number of Part substitution sets in a BOM relationship may be one or more. In other possible embodiments, where a child code in a BOM relationship is a child code, the "whether child code is enabled" attribute of the child code is not involved.

S103: and constructing a BOM sub item Part substitution group. The BOM sub-item Part replacement group is a relationship resulting from the application of the Part replacement group to the BOM relationship. In the BOM relation, only the parent item code and the child item code are included, and the step introduces the construction of the BOM child item Part substitution group by taking the child item code as the cap code as an example. As can be seen from the encoding structure corresponding to step S103 in fig. 3, only two layers of structures, namely "PartB" encoded as a parent item and "PartA", "Part1" encoded as a child item, and the rest of the encoding are included in the BOM relation. It will be understood that "PartA" as a child code is also a set of Part replacement set cap codes, with multiple child codes of "PartA-1", "PartA-2", etc., so in the corresponding example of FIG. 3, the connecting lines between the codes of the Part replacement set are set as dashed lines, and the connecting lines between the codes of the BOM relationship are set as solid lines. In the following embodiments, the connection manner of the dashed lines represents the connection of the Part substitution group coding relationships, and the description is not repeated.

In the case where the sub-item codes in the BOM relation are cap codes, the Part substitution group corresponding to the cap codes is called a BOM sub-item Part substitution group in the BOM relation. The properties of the BOM sub-item Part substitution group can be expanded and configured according to the service scene requirement. When the attribute of "whether to enable subcode" of the cap codes of the Part substitution group is enabled, the attribute of "whether to enable in BOM" of the subcode in the BOM relation can be set, and the attribute of "whether to enable in BOM" comprises enabling and not enabling two states. When the "if in BOM" attribute is enabled, the corresponding subcode may be employed in the BOM relationship; when the "if in BOM" attribute is enabled, the corresponding subcode is disabled from being employed in the BOM relationship.

When the "whether to enable subcode" attribute of the cap code of the Part substitution group is enabled, the "whether to enable in BOM" attribute of at least one subcode in the Part substitution group needs to be set to be enabled, otherwise, the BOM relation cannot be set to be in a usable state.

In the relation of the Part substitution groups of the BOM sub-items, the sub-codes can set whether the attribute is enabled in the BOM, and the cap codes and the sub-codes of the same Part substitution group in different BOM relations are identical in structure. Because of the difference of management and control dimensions of different BOM relations, when Part substitution groups are adopted by the different BOM relations, whether the Part substitution groups are started or not in the corresponding BOM sub-item Part substitution group relations is determined by independently setting cap coding attributes and sub-coding attributes of the Part substitution groups adopted by the different BOM sub-item Part substitution group relations so as to meet business requirements.

Even though the coding structures of Part substitution groups having the same cap code are identical in different BOM relations, the coding properties of the cap code and the sub-code need to be set independently, and the coding property settings between the BOM relations of the Part substitution groups are not affected each other.

In the BOM sub-item Part substitution group, the coding attribute of each sub-code has the expandable capability, and a user of the Part/BOM coding relation management system can perform one or more operations of adding, deleting and checking on the coding attribute in the corresponding BOM sub-item Part substitution group according to the requirements of different business scenes.

The Part/BOM coding relation construction method shown in the application can construct a Part/BOM coding relation management system shown in figure 2. The Part/BOM coding relation construction method described in the steps S101-S103 can meet the requirements that all sub-coding combinations started in the BOM are identified through parent item coding and cap coding under the service scenes of supply, manufacture, purchase and the like, and the sub-coding relation is converted into a task instruction according to the required quantity, the existing stock quantity, the cap and the sub-coding relation, so that the Part real objects are identified and processed according to the sub-coding on the task instruction are manufactured.

The application of the Part/BOM coding relationship construction method shown in fig. 3 in a specific service scenario will be described below in conjunction with two specific application scenarios, and the functional characteristics of the Part/BOM coding relationship management method shown in the present application, such as flexible supply, reuse sharing and layering application of bill of materials, are implemented through the following two embodiments.

First, a first embodiment will be described, taking the differentiated supply of manufacturing devices in a supply chain management system as an example, to describe a specific application of the Part/BOM coding relationship management method shown in the present application.

Referring to fig. 5, fig. 5 is a schematic diagram illustrating Part code splitting requirements in an application scenario of differentiated supply of manufacturing devices according to the present application. In the device supply shown in FIG. 5, device Part500, part encoded as 12XXXXXX, contains four different models, model A, model B, model C, and model D, respectively. By managing the split of the place of origin difference 501 into products BOMPart with Part code 12XXXXX1, the available models include only model B, model C, and model D; by managing the splitting of environmental regulatory differences 502 into device parts with Part codes of 12XXXXX2, available models include only model D; by managing process variation 503 split into device Part with Part encoded as 12XXXXX3, available models include only model a. With the continuous development of supply chain management systems, the constraint conditions of supply scenes are increasingly complex, and the number of split parts coded as 12XXXX is continuously increased. Under the application scene of differential supply of manufacturing devices, the devices meeting the same research and development design requirements are differentiated in management and control dimensions due to the differences of factors such as management production places, environmental protection regulations, processes and the like, and the devices need to be split into a plurality of codes, so that a purchasing party/supplying party of a supply chain cannot collect and manage complex manufacturing device requirements, and cannot timely correct and adjust complex manufacturing device substitution relations so as to realize a physical substitution scheme of complex manufacturing devices.

Referring to fig. 6, fig. 6 is a schematic diagram of a Part/BOM coding relationship management method for solving a problem of implementation of device provisioning in a differentiated scenario according to the present application. The specific solution implementation steps are as follows:

s201: and creating cap codes according to the service requirements.

In constructing a Part replacement group, a Part code is created to express the business requirements and regulatory dimensions satisfied by the Part replacement group represented by the Part code, and then a plurality of subcodes having the same regulatory dimensions are concatenated with the Part code to construct the Part replacement group. The business requirements for building Part replacement groups can be caused by changes in management production places, environmental regulations and process, and can also be caused by changes in other management dimensions in some BOM relations. As shown in FIG. 6, the cap code is set to 12XXXXXX, which is used to refer to a collection of devices having the same regulatory dimensions.

The present step includes step S101 of the Part/BOM relation management method, and the related concept of creating cap codes is described in step S101.

S202: the Part is assigned a subcode, and the Part substitution group is constructed by connecting the subcode with the cap code.

After the cap code is generated, one or more parts conforming to the cap code are collected according to the service requirement of the Part substitution group, and each Part is assigned with a code as a subcode of the cap code. And connecting the cap codes as converging points of the Part substitution group with the one or more subcodes to form the Part substitution group. The sub-codes for constructing the Part substitution group are required to have the same control dimension, namely the same functional specification, interface size, appearance material and process.

The control dimensions between the sub-encodings in the Part substitution set are the same and thus have a relationship that can be substituted for each other. As shown in fig. 6, the Part replacement set includes a cap code and four subcodes, each subcode respectively referring to a Part of a model number, respectively model number a, model number B, model number C, and model number D.

The step includes a step S101 of the Part/BOM relationship management method, and related concepts of constructing Part substitution groups are described in the related description of S101.

S203: the cap code is encoded as a child of the BOM to construct a BOM relationship.

After the Part substitution group is constructed, the BOM relation is constructed by creating a BOM parent item code and using cap codes in the Part substitution group as child item codes in the BOM relation. In other possible embodiments, the number of child encodings connected to a parent encoding in a BOM relationship may also be one or more. The cap codes in the generated Part replacement set relationship may be applied to multiple BOMs due to the differentiated supply requirements of the devices. As shown in FIG. 6, in the BOM relationship, sub-item encodings include not only cap encodings such as encoded as "12XXXXXX", but also other sub-item encodings such as "tag", "software", etc. that do not include alternative group structures.

After the cap code in the Part replacement group is connected with the parent code and the BOM relation is built, whether the Part replacement group enables the child code in the BOM can be set by setting the attribute of whether the child code is enabled of the cap code.

The step corresponds to step S102 of the Part/BOM relationship management method, and related concepts of the BOM relationship are constructed as described in step S102.

S204: setting the subcode attribute of the BOM sub-item Part substitution group, and determining the subcode enabled by the substitution group in the corresponding BOM.

And locking the Part substitution group by taking the cap code as an identifier, identifying the subcodes of the Part substitution group of the cap code in the Part substitution group in all applied BOM relations, and identifying whether the Part substitution group is enabled in the BOM sub item Part substitution group according to the attribute identifier of whether the 'BOM of each subcode is enabled'. When the attribute is identified as "enabled", the Part replacement group enables the corresponding subcode in the BOM sub-item Part replacement group, and when the attribute is identified as "not enabled", the Part replacement group does not enable the corresponding subcode in the BOM sub-item Part replacement group.

In order to meet the business requirement of BOM, when Part substitution groups are adopted by different BOM relations, cap coding attributes and subcode attributes of the Part substitution groups adopted by the different BOM relations are independently set to determine whether the coding attributes are started in the corresponding BOM relations. In different BOM relations, the coding structures of Part substitution groups with the same cap codes are consistent, but independent setting is needed on the coding attributes of the cap codes and the sub-codes, and the coding attribute setting between the BOM relations of the Part substitution groups is not affected.

The step corresponds to step S103 of the Part/BOM relation management method, and the related concepts of the cap coding attribute and the subcode attribute in the BOM relation are set as described in S103.

Next, taking an application scenario of introducing a new manufacturer type MPN under device coding as an example, a specific application of the Part/BOM coding relation construction method shown in the present application is described. In the second embodiment, the Part substitution group shows the Part/BOM coding relation construction method shown in the application under the condition of changing, and the method has the functional characteristic of supporting rapid introduction of device substitution.

Referring to fig. 7, fig. 7 is a schematic diagram of a device supply new manufacturer type requirement provided by the present application. As shown in fig. 7, device code "12 xxxxx" is subjected to device replacement test verification before a new manufacturer "model E" is introduced. When the newly added manufacturer 'model E' passes the replacement test verification of each product BOM, the code '12 XXXXXX' can be added to the manufacturer 'model E', and the product BOM which does not pass the code is processed by splitting the new code.

Since the number of BOMs of a product to be validated is typically tens or hundreds, it takes a long time to wait for all of the BOMs to be tested or technically evaluated before a final replacement conclusion can be reached. Some product line test cycles are short, and the need to quickly reference the device is either not satisfied or can only be solved by splitting the code, increasing the complexity of code replacement management.

Referring to fig. 8, a schematic diagram of a Part/BOM code relationship management method for resolving a quick new manufacturer model of device supply is provided in the present application. As shown in FIG. 8, the Part/BOM coding relation management method can enable the replacement verification processes of different devices to be relatively independent, so that a product line with a short test period of a small batch can be put into production rapidly, and the BOM does not need to be uniformly modified after all verification results appear. The specific solution implementation steps are as follows:

s301: creating subcodes according to the new manufacturer model and the new cap code.

In the illustrated embodiment of the application, part replacement sets already exist and even have been applied to one or more BOM relationships and put into production for use, with changes to Part replacement sets due to changes in business requirements. The illustrated embodiment of the application involves a modification of the Part replacement set requiring creation of a generator sub-code and addition of an already existing Part replacement set.

In the application scene of the new manufacturer type, a subcode corresponding to the cap code is generated according to the selection of the new manufacturer type and the Part management dimension represented by the cap code. As shown in FIG. 8, the existing cap code "12XXXXXX", a subcode "12XXXXXX5" is generated from the same regulatory dimensions and concatenated with the new manufacturer's model "model E".

In the embodiment of the application, the newly added manufacturer model is unique and named as model E, and each subcode in the Part substitution group is mounted with a corresponding manufacturer Model (MPN), so that only one subcode is newly created. It will be appreciated that the present application is merely an example, and that since each subcode is connected to one manufacturer model, in other possible embodiments, the number of newly added manufacturer models may be more, the new subcode may be loaded with one or more manufacturer models, and the newly added manufacturer model may be loaded with subcodes existing in the Part replacement set, without limitation.

S302: and adding the new child code into the corresponding Part substitution group by taking the cap code as a mark.

As shown in FIG. 8, the subcode "12XXXXXX1" is joined with the cap code "12XXXXXX", and a Part substitution group representing the newly added manufacturer model "model E" is added to the substitution group corresponding to the cap code to construct a Part substitution group of the newly added manufacturer model.

The Part substitution group is updated, and the Part substitution group is not required to be incorporated into the BOM after all product substitution conclusions pass verification, so that the starting time of a manufacturer or subcode in the BOM can be effectively increased.

S303: the cap code is used as an identification to search the BOM list of the enabled subcodes.

As shown in FIG. 8, in an embodiment of the present application, the Part replacement group has been enabled in 2 BOMs, and the Part replacement group corresponding to the 2 BOMs is updated with the cap code as the identification to update the BOM coding structure. In other possible embodiments, the number of BOMs to which the Part replacement set has been applied may also be fewer or greater. As shown in FIG. 8, in the BOM relationship, sub-item encodings include not only cap encodings such as encoded as "12XXXXXX", but also other sub-item encodings such as "tag", "software", etc. that do not include alternative group structures.

For each BOM for which Part replacement group update has been completed, the "if enabled in BOM" attribute of the subcode corresponding to the new make model defaults to "not enabled" before the corresponding alternate verification is completed.

S304: and determining the attribute value of the sub-code in the Part substitution group of the BOM sub-item according to the substitution verification result of the manufacturer model.

After each BOM completes the replacement verification of the new manufacturer model, whether the new manufacturer model is started in the corresponding BOM sub-item Part replacement group can be determined by setting the attribute of whether the new manufacturer model is started in the 'BOM in the sub-coding of the BOM sub-item Part replacement group'. Through the Part replacement group of the BOM sub-item, the unified updating of the BOM list after the completion of the replaceable verification by using all BOMs of the cap code is not needed, and meanwhile, the management complexity of the Part replacement relation caused by the splitting of the Part code is reduced as much as possible.

It can be understood that, in this embodiment, only the case where adding a manufacturer model results in adding a new subcode is introduced, and in other possible embodiments, due to the change of service requirements and management dimensions, deletion, modification, invalidation, etc. of subcodes in the Part replacement group may also occur, so that it is necessary to correspondingly operate each subcode and coding attribute in the BOM sub-Part replacement group. Wherein the operations include performing one or more of adding, deleting, and modifying the subcode or subcode attributes without changing the cap encoding of the Part replacement set. When the Part replacement group is unchanged, only each item of the Part replacement group of the BOM sub-item is modified when the Part replacement group of the BOM sub-item is changed, and one or more operations such as deleting, modifying, invalidating and the like are performed on the corresponding sub-code.

Referring to fig. 9, fig. 9 is a schematic diagram of a Part/BOM coding relationship management apparatus according to the present application. The Part/BOM coding relation management device of the embodiment comprises: the substitute group construction module 901, the BOM relationship construction module 902, and the BOM sub-items substitute the group construction module 903.

The substitution group construction module 901 is configured to generate a corresponding cap code through a management dimension of a Part, and to connect each of the set of sub-codes with the corresponding cap code, so as to construct a Part substitution group applicable to different BOM relations. In other possible cases, the method is also used for realizing the adding, deleting and checking operation of Part neutron coding or cap coding without changing the existing Part replacement group management dimension. Through the above-described operations, the substitute group construction module 901 may implement construction of a Part substitute group for application by a different BOM as shown in step S101.

The replacement group construction module 901 is further configured to screen a plurality of cap codes and a plurality of subcodes according to the same management and control dimension principle, where the cap codes and the subcodes have the same functional specification, the same interface size, the same appearance material and the same process. Since there are identical regulatory dimensions between the multiple subcodes, there are alternative relationships between the individual subcodes. In other possible cases, the method is used for implementing the adding, deleting and checking operation of the sub-codes or the cap codes in the Part substitution group by modifying the management dimension of the generated Part substitution group, and is used for maintaining the management dimension of the Part substitution group according to the factors of manufacturing flow, process route, device specification, cost accounting, inventory management and the like so as to dynamically adjust the principle of adding or deleting the sub-codes in the group.

The BOM relation building module 902 is configured to generate a parent code covering elements such as a manufacturing flow, a process route, a component structure, and the like of the BOM, and associate one or more child codes of product elements such as a manufacturing flow, a process route, a device specification, and the like represented by the BOM according to the parent code. Through the above operations, the BOM relation construction module 902 may implement construction of a BOM relation including one parent item code and one or more child item codes as shown in S102.

The BOM relation construction module 902 is further configured to set and change a child code associated with a parent code of the BOM. Wherein, the sub-item code can be a cap code or a sub-code. In the case that the sub-item code is a cap code, a plurality of sub-codes having a replaceable relation, which indicate that the sub-item code is a group corresponding to the cap code, are referred to as a Part replacement group of the BOM sub-item, where the cap code and the Part replacement group represented by the corresponding plurality of sub-codes are referred to as a Part replacement group of the BOM sub-item. In the BOM, the attribute of whether the sub-code is enabled is set to be enabled, the sub-code level of the Part substitution group represented by the cap code is opened, and otherwise, the sub-code level is set to be not enabled. When the child code is a child code, then the attribute of "whether or not child code is enabled" as a child code of the child code defaults to "not involved".

The BOM sub-item substitution group construction module 903 is configured to construct and maintain a coding structure and a coding attribute in the BOM sub-item Part substitution group when the cap code of the Part substitution group is used as the sub-item code in the BOM relationship. Wherein a "if in BOM" attribute is enabled is set for each subcode. When the sub-coding attribute is selected as 'enabled', the corresponding sub-codes in the Part substitution group can be used in the BOM, otherwise, when the sub-coding attribute is selected as 'not enabled', the corresponding sub-codes in the Part substitution group cannot be used in the BOM, and flexible substitution of the sub-codes and flexible use of the Part substitution group is facilitated.

The BOM sub-item substitution group construction module 903 is further configured to provide a capability of configurable, extensible and deletable coding attributes for each sub-code of the Part substitution group in the BOM, so as to support the device user of the present application to set, modify, extend and delete corresponding service attributes according to different service scenarios. Through the above operations, the BOM sub item Part substitution group construction module 903 may implement construction of the BOM sub item Part substitution group relationship as shown in S103.

For ease of description, a detailed description of a Part/BOM coding relationship management apparatus of the present embodiment may be specifically referred to fig. 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 apparatus shown in this embodiment may be located in different electronic computing devices and connected through a cloud network.

Referring to fig. 10, fig. 10 is a schematic structural diagram of an electronic computing device according to the present application. The data processing apparatus of the present embodiment includes: one or more first processors 1010, a data collector 1020, a communication interface 1030, external memory 1040, and a bus 1050. The first processor 1010, the data collector 1020, the communication interface 1030, and the external memory 1040 may be connected by a bus 1050.

The data collector 1020 is used for collecting related data generated in the process of constructing various Part/BOM coding management relations according to the methods described in S101-S103, and for obtaining data between various modules in the Part/BOM information architecture.

The first processor 1010 includes one or more general-purpose processors, which may be any type of device capable of processing electronic instructions, including a central processor (CentralProcessingUnit, CPU), a microprocessor, a microcontroller, a main processor, a controller, and an ASIC (ApplicationSpecificIntegratedCircuit ), among others. The first processor 1010 executes various types of digitally stored instructions, such as software or firmware programs stored in the external memory 1040, which enable the data processing apparatus 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 (e.g., an ethernet interface) for communicating with other data processing devices or users for implementing the Part/BOM code relationship management method, and the related concepts may be described in detail herein without further description.

The external memory 1040 may include volatile memory (VolatileMemory), such as random access memory (RandomAccessMemory, RAM); the memory may also include Non-volatile memory (Non-VolatileMemory), such as Read-only memory (ROM), flash memory (Flashmemory), hard disk (HARDDISKDRIVE, HDD), or Solid state disk (Solid-state-STATEDRIVE, SSD) memory, as well as combinations of the above. The external memory 1040 may store program codes and program data.

The first processor 1010 may be configured to implement the Part/BOM coding relationship management method by invoking program codes in the external memory 1040 to execute the steps described in steps S101 to S103, steps S201 to S204, and steps S301 to S304. For ease of presentation, the detailed description of this embodiment may be found in detail in fig. 3-8 and the associated description.

While the present invention describes functionality performed by certain virtual components and physical entities, in a cloud service system application scenario, some or all of the above-described coding relationship management processes may be distributed among multiple virtual components and entities, and one or more instances of the processes may be performed on a distributed system, virtual machine, and one or more cloud service systems.

The present application provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements all the steps of the above-described target method, for example, the processor implements the processes and related operations as steps S101 to S103, steps S201 to S204, and steps S301 to S304.

The computer software product is stored on a storage medium and includes instructions for causing a computer device to perform all or part of the steps of the methods described in the various embodiments of the application. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. 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 one website, computer, server, cloud service center, or data center to another website, computer, server, cloud service center, or data center by wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means.

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, a data center, etc. containing one or more integration of the available media, and may also be a cloud storage resource provided by a cloud server. The usable medium may be a magnetic medium (e.g., floppy disk, memory disk, tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state memory disk SolidStateDisk, SSD), etc.

Further, the logic instructions in the external memory 1040 shown in fig. 10 may be implemented in the form of software functional units and may be stored in a computer-readable storage medium for sale or use as a stand-alone product. Based on such an understanding, the technical solution of the application, in essence, or the part contributing 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 comprising a computer program which, when executed by a processor, implements all the steps of the above-described target method, for example, the processor implements the following procedures and related operations as steps S101 to S103, steps S201 to S204, and steps S301 to S304.

The embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules can be selected according to actual needs to achieve the purpose of the embodiment of the application.

The above embodiments are only for illustrating the technical solution of the present application, and are not limiting. Although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some of the technical features thereof can be replaced by equivalents. Such modifications and substitutions do not depart 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.