A method and system for realizing parent-child association entry of multi-version products

Abstract

The present application discloses a method and system for implementing the parent-child association entry of multi-version products, the method comprising: obtaining a first product; obtaining a version feature set of the first product; obtaining multiple versions of the first product through a decision tree; obtaining a first sub-product set through an OR logic operation; in a contract scenario, selecting the first product and selecting or not selecting all sub-products in the first sub-field frequency set to obtain a second sub-product set; in a work order scenario, performing an AND logic operation on the associated sub-product set of each version and the second sub-product set to obtain a matching sub-product set for each version. This solves the technical problem in the prior art that when a product has multiple versions and there are differences in the fixedly associated sub-products between different versions, if the product in the work order scenario is inconsistent with the product entered in the contract, the selectable sub-products will be incomplete or even completely missing.

Description

Technical Field

[0001] The present application relates to the field of artificial intelligence, and in particular to a method and system for implementing parent-child association entry for multi-version products.

[0002] In the actual process of selling products, manufacturers will encounter many special situations, and customers have different needs for different products. If a product has only one version, then the sub-products associated with the product are fixed, which can be supported by existing technology. However, when a product has multiple different versions, and there are differences in the sub-products associated with each version, in the contract scenario, customers only care about their own needs, that is, the product itself, and not the product version; in the work order scenario, the sub-products that can be selected for a certain version of the product are subject to the restrictions of the products and sub-products entered in the contract. As a result, if the product in the work order scenario is inconsistent with the product version entered in the contract, the selectable sub-products will be incomplete or even completely missing. How to control and select the associated sub-products of products in contract scenarios and work order scenarios, so that the parent-child relationship of multiple versions of products can be accurately and completely presented in the flow of contracts and work orders, is a practical problem that needs to be solved urgently.

[0003] In the process of implementing the technical solutions in the embodiments of the present application, the inventors of the present application discovered that the above technology has at least the following technical problems:

[0004] In the existing technology, when a product has multiple versions and the sub-products fixedly associated with different versions are different, the sub-products that can be selected for association with any version of the product are restricted by both the sub-products required by the customer and the sub-products fixedly associated with each version. As a result, if the product in the work order scenario is inconsistent with the product entered in the contract, there will be a technical problem that the selectable sub-products are incomplete or even completely missing. Summary of the Invention

[0005] In view of this, an embodiment of the present application provides a method and system for recording parent-child associations of multiple versions of products, the method comprising: obtaining a first product, wherein the first product has multiple versions; obtaining a version feature set of the first product; categorizing the versions of the first product using a decision tree for each version feature in the version feature set to obtain multiple versions of the first product; obtaining a set of associated sub-products for each version; performing an OR logic operation on the set of associated sub-products for each version to obtain a first set of sub-products; in a contract scenario, selecting the first product and selecting or deselecting all sub-products in the first sub-field frequency set to obtain a second set of sub-products; in a work order scenario, performing an AND logic operation on the set of associated sub-products for each version and the second sub-product set to obtain a set of compatible sub-products for each version. This solves the technical problem in the prior art that when a product has multiple versions and the sub-products fixedly associated between different versions are different, the sub-products that can be selected for association with any version of the product are limited by both the customer's required sub-products and the sub-products fixedly associated with each version, resulting in incomplete or even complete loss of selectable sub-products if the product in the work order scenario is inconsistent with the product entered in the contract. When a product has multiple versions and there are differences in the fixedly associated sub-products between different versions, the intersection of the product required by the customer and the sub-products associated with the current version is calculated in the work order scenario by taking the union of the sub-products associated with all versions in the contract scenario, and allowing selection, entry, and save operations. The technical effect of accurately displaying the flow of products and their sub-products from the contract scenario to the work order scenario is achieved.

[0006] In view of the above problems, an embodiment of the present application provides a method and system for implementing parent-child association entry for multi-version products.

[0007] In the first aspect, the present application provides a method for implementing parent-child association entry of multi-version products, and the method is implemented by a system for implementing parent-child association entry of multi-version products, wherein the method includes: obtaining a first product, wherein the first product has multiple versions; obtaining a version feature set of the first product; categorizing the version of the first product through a decision tree for each version feature in the version feature set to obtain multiple versions of the first product; obtaining a set of associated sub-products for each of the versions; performing an OR logic operation on the set of associated sub-products for each of the versions to obtain a first sub-product set; in a contract scenario, selecting the first product and selecting or deselecting all sub-products in the first sub-field frequency set respectively to obtain a second sub-product set; in a work order scenario, performing an AND logic operation on the set of associated sub-products for each of the versions and the second sub-product set to obtain a set of adapted sub-products for each of the versions.

[0008] On the other hand, the present application also provides a system for implementing parent-child association entry of multi-version products, which is used to execute a method for implementing parent-child association entry of multi-version products as described in the first aspect, wherein the system includes: through a first acquisition unit: the first acquisition unit is used to obtain a first product, wherein the first product has multiple versions; a second acquisition unit: the second acquisition unit is used to obtain a version feature set of the first product; a third acquisition unit: the third acquisition unit is used to classify the version of the first product through a decision tree for each version feature in the version feature set, to obtain multiple versions of the first product; a fourth acquisition unit: the fourth acquisition unit is used to obtain an associated sub-product set of each version; a fifth acquisition unit: the fifth acquisition unit is used to perform an OR logic operation on the associated sub-product set of each version to obtain a first sub-product set; a sixth acquisition unit: the sixth acquisition unit is used to select the first product in a contract scenario and select or deselect all sub-products in the first sub-field frequency set respectively to obtain a second sub-product set; a seventh acquisition unit: the seventh acquisition unit is used to perform an AND logic operation on the associated sub-product set of each version and the second sub-product set in a work order scenario to obtain an adapted sub-product set for each version.

[0009] In the third aspect, an embodiment of the present application also provides a system for implementing the entry of parent-child associations of multiple versions of products, including a memory, a processor, and a computer program stored on the memory and runnable on the processor, wherein the processor implements the steps of the method described in the first aspect above when executing the program.

[0010] One or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages:

[0011] 1. Obtain a first product, wherein the first product has multiple versions; obtain a version feature set of the first product; categorize the versions of the first product using a decision tree for each version feature in the version feature set to obtain multiple versions of the first product; obtain a set of associated sub-products for each version; perform an OR logic operation on the associated sub-product sets of each version to obtain a first sub-product set; in a contract scenario, select the first product and select or deselect all sub-products in the first sub-product set to obtain a second sub-product set; in a work order scenario, perform an AND logic operation on the associated sub-product set of each version and the second sub-product set to obtain a set of compatible sub-products for each version. This achieves the technical effect of accurately displaying the product and its sub-products from the contract scenario to the work order scenario when there are multiple versions of a product and there are differences in the fixedly associated sub-products between different versions. By taking the union of all version-associated sub-products in the contract scenario and allowing selection, entry, and saving operations, the intersection of the customer's desired product and the sub-products associated with the current version is further calculated in the work order scenario, completing the technical effect of accurately displaying the product and its sub-products from the contract scenario to the work order scenario.

[0012] 2. Through logical AND operations in the work order scenario, the intersection of the customer's required product and the sub-products associated with the current version is obtained, that is, the set of adapted sub-products for each version of the first product. This further achieves the goal of accurately displaying the flow of products and their sub-products from the contract scenario to the work order scenario.

[0013] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely exemplary. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without any creative work.

[0015] Figure 1 This is a flowchart of a method for implementing parent-child association entry for multi-version products according to an embodiment of the present application;

[0016] Figure 2 A schematic diagram of a process for classifying the versions of the first product using a decision tree for each version feature in the version feature set to obtain multiple versions of the first product in a method for implementing parent-child association entry of multiple versions of a product according to an embodiment of the present application;

[0017] Figure 3 This is a flow chart of constructing a version feature category decision tree in a method for implementing parent-child association entry of multi-version products in an embodiment of the present application;

[0018] Figure 4 This is a flow chart of obtaining a set of associated sub-products of each version in a method for implementing parent-child association entry of multiple versions of products according to an embodiment of the present application;

[0019] Figure 5 This is a structural diagram of a system for implementing parent-child association entry for multi-version products according to an embodiment of the present application;

[0020] Figure 6 This is a schematic diagram of the structure of an exemplary electronic device according to an embodiment of the present application.

[0021] Description of reference numerals:

[0022] First obtaining unit 11 , second obtaining unit 12 , third obtaining unit 13 , fourth obtaining unit 14 , fifth obtaining unit 15 , sixth obtaining unit 16 , seventh obtaining unit 17 , bus 300 , receiver 301 , processor 302 , transmitter 303 , memory 304 , bus interface 305 . DETAILED DESCRIPTION

[0023] The embodiment of the present application provides a method and system for entering parent-child associations for multi-version products, thereby resolving the existing technical problem that when a product has multiple versions and there are differences in the sub-products fixedly associated between different versions, the sub-products that can be selected for association with any version of the product are restricted by both the sub-products required by the customer and the sub-products fixedly associated with each version, resulting in incomplete or even complete missing sub-products if the product in the work order scenario is inconsistent with the product entered in the contract. The method achieves the goal of achieving the technical effect of accurately displaying the transferred product and its sub-products from the contract scenario to the work order scenario by taking the union of all version-associated sub-products in the contract scenario and allowing selection, entry, and save operations when there are multiple versions of a product and there are differences in the sub-products fixedly associated between different versions.

[0024] Below, the technical solutions in the embodiments of the present application will be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. It should be understood that the present application is not limited to the example embodiments described herein. Based on the embodiments of the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application. It should also be noted that, for the sake of ease of description, only the parts related to the present application, rather than all of them, are shown in the accompanying drawings.

[0025] Application Overview

[0026] In the actual process of selling products, manufacturers will encounter many special situations, and customers have different needs for different products. If a product has only one version, then the sub-products associated with the product are fixed, which can be supported by existing technology. However, when a product has multiple different versions, and there are differences in the sub-products associated with each version, in the contract scenario, customers only care about their own needs, that is, the product itself, and not the product version; in the work order scenario, the sub-products that can be selected for a certain version of the product are subject to the restrictions of the products and sub-products entered in the contract. As a result, if the product in the work order scenario is inconsistent with the product version entered in the contract, the selectable sub-products will be incomplete or even completely missing. How to control and select the associated sub-products of products in contract scenarios and work order scenarios, so that the parent-child relationship of multiple versions of products can be accurately and completely presented in the flow of contracts and work orders, is a practical problem that needs to be solved urgently.

[0027] In the existing technology, when a product has multiple versions and the sub-products fixedly associated with different versions are different, the sub-products that can be selected for association with any version of the product are restricted by both the sub-products required by the customer and the sub-products fixedly associated with each version. As a result, if the product in the work order scenario is inconsistent with the product entered in the contract, there will be a technical problem that the selectable sub-products are incomplete or even completely missing.

[0028] In response to the above technical problems, the overall idea of ​​the technical solution provided by this application is as follows:

[0029] The present application provides a method for implementing parent-child association entry of multi-version products, and the method is applied to a system for implementing parent-child association entry of multi-version products, wherein the method includes: obtaining a first product, wherein the first product has multiple versions; obtaining a version feature set of the first product; categorizing the version of the first product by using a decision tree for each version feature in the version feature set to obtain multiple versions of the first product; obtaining a set of associated sub-products for each of the versions; performing an OR logic operation on the set of associated sub-products for each of the versions to obtain a first sub-product set; in a contract scenario, selecting the first product and selecting or deselecting all sub-products in the first sub-product set respectively to obtain a second sub-product set; in a work order scenario, performing an AND logic operation on the set of associated sub-products for each of the versions and the second sub-product set to obtain a set of adapted sub-products for each of the versions.

[0030] After introducing the basic principles of the present application, various non-limiting implementation methods of the present application will be specifically introduced in conjunction with the drawings in the specification.

[0031] Example 1

[0032] Please see the attached Figure 1 The embodiment of the present application provides a method for implementing parent-child association entry for multi-version products, wherein the method is applied to a system for implementing parent-child association entry for multi-version products, and the method specifically includes the following steps:

[0033] Step S100: obtaining a first product, wherein the first product has multiple versions;

[0034] Specifically, the method for implementing the entry of parent-child associations of multi-version products is used in the system for implementing the entry of parent-child associations of multi-version products, which can accurately display the transfer of products and their sub-products from contract scenarios to work order scenarios through parent-child associations of multi-version products. The first product refers to any product sold. The first product has multiple different versions. For example, a certain product A has three different product versions: v1.0, v2.0, and v3.0. By obtaining the first product, the technical effect of clarifying the first product and its version status is achieved.

[0035] Step S200: obtaining a version feature set of the first product;

[0036] Step S300: using a decision tree to classify the versions of the first product using each version feature in the version feature set to obtain multiple versions of the first product;

[0037] Specifically, the system for realizing the entry of parent-child associations of multiple versions of products can intelligently record and store all version information corresponding to the first product, thereby obtaining a version feature set of the first product. Furthermore, based on a decision tree, each version feature of the first product in the version feature set is classified, thereby obtaining multiple versions of the first product. Among them, the decision tree is a prediction model, which represents a mapping relationship between object attributes and object values, and is a very commonly used classification method. Based on the decision tree, all versions of the first product can be efficiently managed, providing a management basis for subsequent version associations, etc.

[0038] Step S400: obtaining a set of associated sub-products of each version;

[0039] Specifically, the set of associated sub-products of the version refers to the set of sub-products associated with each version of the multiple different versions of the first product. For example, product A has three product versions: v1.0, v2.0, and v3.0. Among them, version v1.0 is fixedly associated with three sub-products: α, β, and γ; version v2.0 is fixedly associated with three sub-products: β, γ, and δ; and version v3.0 is fixedly associated with three sub-products: β, γ, and ε. Then for product A, the set of sub-products associated with version v1.0 is {α, β, γ}, the set of sub-products associated with version v2.0 is {β, γ, δ}, and the set of sub-products associated with version v3.0 is {γ, δ, ε}. By converting the sub-products fixedly associated with each version of the first product into a set form, the technical effect of intuitively and clearly understanding the details of each version of the first product is achieved.

[0040] Step S500: performing an OR logic operation on the associated sub-product sets of each version to obtain a first sub-product set;

[0041] Specifically, by performing a union operation on the fixed associated sub-product sets of each of the versions, that is, the OR logical operation, a set of all associated sub-products of the first product can be obtained, that is, the first sub-product set. For example, product A has three product versions: v1.0, v2.0, and v3.0. The sub-product set associated with version v1.0 is {α, β, γ}, the sub-product set associated with version v2.0 is {β, γ, δ}, and the sub-product set associated with version v3.0 is {γ, δ, ε}. Then the sub-product set of product A is {α, β, γ, δ, ε}. Through the OR logical operation, the union of the sub-products associated with each version of the first product is obtained, achieving the technical effect of deduplication of multiple versions of the product.

[0042] Step S600: In a contract scenario, the first product is selected and all sub-products in the first sub-product set are selected or deselected to obtain a second sub-product set;

[0043] Specifically, in a contract scenario, the first product is selected and all sub-products in the first sub-product set are selected or unselected to obtain a second sub-product set. The contract scenario refers to the contract signed between a production and sales company and a purchasing customer. In the contract scenario, the product required by the purchasing customer, that is, the first product, is first selected. At this time, the system automatically displays all sub-products of the first product, that is, the first sub-product set of the first product automatically appears. Next, the corresponding sub-products are manually selected and entered according to the purchasing customer's needs. After selecting all the sub-products required by the purchasing customer, the product selection in the contract scenario is completed. By manually selecting, entering and saving all the sub-products of the first product, a technical effect of personalized customization based on the needs of the purchasing customer is achieved.

[0044] Step S700: In a work order scenario, perform an AND logic operation on the associated sub-product set of each version and the second sub-product set to obtain the adapted sub-product set of each version.

[0045] Specifically, in the work order scenario, a union operation is performed on the associated sub-product set of each version and the second sub-product set, that is, a logical operation is performed on the associated sub-product set of each version and the second sub-product set, and the adapted sub-product set of each version can be obtained respectively. Among them, the work order scenario refers to the work document used by the production and sales enterprise for its own management and record keeping. For example, assuming that the three sub-products α, γ, and ε associated with the purchasing customer's demand for product A are manually selected, entered, and saved in the contract scenario, the second sub-product set is obtained, and the second sub-product set is {α, γ, ε}; the associated sub-product sets of each version are: the associated sub-product set of version v1.0 is {α, β, γ}, the associated sub-product set of version v2.0 is {β, γ, δ}, and the associated sub-product set of version v3.0 is {γ, δ, ε}. Then the adapted sub-product sets of each version are: the adapted sub-product set of version v1.0 is {α, γ}, the adapted sub-product set of version v2.0 is {γ}, and the adapted sub-product set of version v3.0 is {γ, ε}.

[0046] Through logical operations in the work order scenario, we obtain the intersection of the product required by the customer and the sub-products associated with the current version, that is, the set of adapted sub-products for each version of the first product, further achieving the goal of accurately displaying the transferred products and their sub-products from the contract scenario to the work order scenario.

[0047] Further, as attached Figure 2 As shown, step S300 in this embodiment of the application further includes:

[0048] Step S310: constructing a version feature category decision tree;

[0049] Step S320: Input each version feature of the first product into the version feature category decision tree to obtain multiple versions of the first product.

[0050] Specifically, decision trees are a form of supervised learning. Given a set of samples, each with a set of attributes and a category, these categories are determined in advance. Through learning, a classifier is generated that can correctly classify newly encountered objects. The decision tree is a predictive model that represents a mapping between object attributes and object values ​​and is a very common classification method. By constructing a version feature classification decision tree, effective management of all versions corresponding to the first product can be achieved.

[0051] Further, as attached Figure 3 As shown, step S310 in this embodiment of the application further includes:

[0052] Step S311: Obtaining a first version feature, a second version feature, and a third version feature from the version feature set;

[0053] Step S312: performing information theory coding operations on the first version feature, the second version feature, and the third version feature respectively to obtain first version feature information entropy, second version feature information entropy, and third version feature information entropy;

[0054] Step S313: Obtain the version feature of the first root node according to the first version feature information entropy, the second version feature information entropy, and the third version feature information;

[0055] Step S314: constructing a version feature category decision tree based on a recursive algorithm of the first root node version feature and the version feature set.

[0056] Specifically, based on the first version feature, the second version feature, and the third version feature, the first hierarchical feature, the second hierarchical feature, and the third hierarchical feature are obtained respectively, and all product versions in the version feature set are classified. In order to specifically construct the version feature classification decision tree, the information entropy calculation can be performed on the first hierarchical feature, the second hierarchical feature, and the third hierarchical feature respectively, that is, the information entropy calculation formula in information theory coding is used:

[0057]

[0058] Among them, t represents a random variable, corresponding to which is the set of all possible outputs, defined as a symbol set. The output of the random variable is represented by t, and p(i|t) represents the output probability function. The greater the uncertainty of the variable, the greater the entropy.

[0059] A specific calculation of the information entropy value is performed to obtain the corresponding first feature information entropy, the second feature information entropy and the third feature information entropy. Further, based on the data size comparison model, the first feature information entropy, the second feature information entropy and the third feature information entropy are compared in size to obtain the feature with the smallest entropy value, that is, the first root node feature information. By prioritizing the feature with the smallest entropy value and then classifying each version feature in order of entropy value from small to large, a recursive algorithm is used to classify the version features in turn, and finally a version feature category decision tree for the first product is constructed.

[0060] Further, as attached Figure 4 As shown, step S400 in this embodiment of the application further includes:

[0061] Step S410: Obtain associated sub-products of the first product in each of the versions;

[0062] Step S420: converting the associated sub-products of each version into an associated sub-product set of each version.

[0063] Specifically, first, the situation of each version of the first product is obtained to obtain the situation of the sub-products fixedly associated with the first product in each version, and then the associated sub-products of each version are converted into a set of associated sub-products for each version. For example, version v1.0 of product A is fixedly associated with three sub-products α, β and γ; version v2.0 of product A is fixedly associated with three sub-products β, γ and δ; and version v3.0 of product A is fixedly associated with three sub-products β, γ and ε. Then for product A, the set of associated sub-products of version v1.0 is {α, β, γ}, the set of associated sub-products of version v2.0 is {β, γ, δ}, and the set of associated sub-products of version v3.0 is {γ, δ, ε}. By converting the fixed associated sub-products of each version of the first product into a set form, the technical effect of intuitively and clearly understanding the details of the fixed associated sub-products of each version of the first product is achieved. Furthermore, the set of associated sub-products of each version includes the same associated sub-products.

[0064] Specifically, the associated sub-product set for each version includes the same sub-products that are fixedly associated with each version. For example, version v1.0 of product A is fixedly associated with sub-products α, β, and γ, while version v2.0 of product A is fixedly associated with sub-products β, γ, and δ. Both versions v1.0 and v2.0 contain sub-products β and γ.

[0065] Furthermore, the associated sub-product set of each version includes different associated sub-products.

[0066] Specifically, each version's associated sub-product set includes different sub-products that are not fixedly associated with other versions. For example, version v1.0 of product A is fixedly associated with sub-products α, β, and γ, while version v2.0 of product A is fixedly associated with sub-products β, γ, and δ. Version v1.0 includes sub-product α, which is not included in version v2.0, and version v2.0 includes sub-product δ, which is not included in version v1.0.

[0067] Furthermore, step S600 in the embodiment of the present application further includes:

[0068] Step S610: Enter and save the second sub-product set.

[0069] Specifically, in a contract scenario, the first step is to select the product requested by the purchasing customer, namely the first product. The system then automatically displays all of the first product's sub-products, i.e., the first sub-product set of the first product. Next, the system manually selects and enters the corresponding sub-products based on the purchasing customer's needs. Once all the sub-products required by the purchasing customer are selected, the system saves the selection, completing the product selection for the contract scenario. By manually selecting, entering, and saving all of the sub-products required by the first product, the system achieves the technical effect of personalized customization tailored to the purchasing customer's needs.

[0070] In summary, the method for implementing parent-child association entry for multi-version products provided by the embodiments of the present application has the following technical effects:

[0071] 1. Obtain a first product, wherein the first product has multiple versions; obtain a version feature set of the first product; categorize the versions of the first product using a decision tree for each version feature in the version feature set to obtain multiple versions of the first product; obtain a set of associated sub-products for each version; perform an OR logic operation on the associated sub-product sets of each version to obtain a first sub-product set; in a contract scenario, select the first product and select or deselect all sub-products in the first sub-product set to obtain a second sub-product set; in a work order scenario, perform an AND logic operation on the associated sub-product set of each version and the second sub-product set to obtain a set of compatible sub-products for each version. This achieves the technical effect of accurately displaying the product and its sub-products from the contract scenario to the work order scenario when there are multiple versions of a product and there are differences in the fixedly associated sub-products between different versions. By taking the union of all version-associated sub-products in the contract scenario and allowing selection, entry, and saving operations, the intersection of the customer's desired product and the sub-products associated with the current version is further calculated in the work order scenario, completing the technical effect of accurately displaying the product and its sub-products from the contract scenario to the work order scenario.

[0072] 2. Through logical AND operations in the work order scenario, the intersection of the customer's required product and the sub-products associated with the current version is obtained, that is, the set of adapted sub-products for each version of the first product. This further achieves the goal of accurately displaying the flow of products and their sub-products from the contract scenario to the work order scenario.

[0073] Example 2

[0074] Based on the same inventive concept as the method for implementing parent-child association entry of multi-version products in the aforementioned embodiment, the present invention also provides a system for implementing parent-child association entry of multi-version products. Figure 5 , the system comprising:

[0075] First obtaining unit 11: The first obtaining unit 11 is used to obtain a first product, wherein the first product has multiple versions;

[0076] Second obtaining unit 12: The second obtaining unit 12 is used to obtain a version feature set of the first product;

[0077] The third obtaining unit 13 is configured to classify the versions of the first product using a decision tree for each version feature in the version feature set, thereby obtaining multiple versions of the first product.

[0078] Fourth obtaining unit 14: the fourth obtaining unit 14 is used to obtain a set of associated sub-products of each version;

[0079] The fifth obtaining unit 15 is configured to perform an OR logic operation on the associated sub-product sets of each version to obtain a first sub-product set;

[0080] The sixth obtaining unit 16 is configured to select the first product and select or deselect all sub-products in the first sub-field frequency set in a contract scenario to obtain a second sub-product set;

[0081] The seventh obtaining unit 17 is used to perform an AND logic operation on the associated sub-product set of each version and the second sub-product set in a work order scenario to obtain the adapted sub-product set of each version.

[0082] Furthermore, the system further comprises:

[0083] First construction unit: The first construction unit is used to construct a version feature category decision tree;

[0084] An eighth obtaining unit: The eighth obtaining unit is used to input each version feature of the first product into the version feature category decision tree to obtain multiple versions of the first product.

[0085] Furthermore, the system further comprises:

[0086] Ninth obtaining unit: the ninth obtaining unit is used to obtain the first version feature, the second version feature, and the third version feature from the version feature set;

[0087] A tenth obtaining unit: the tenth obtaining unit is configured to perform information-theoretic coding operations on the first version feature, the second version feature, and the third version feature, respectively, to obtain first version feature information entropy, second version feature information entropy, and third version feature information entropy;

[0088] An eleventh obtaining unit: the eleventh obtaining unit is configured to obtain a first root node version feature according to the first version feature information entropy, the second version feature information entropy, and the third version feature information;

[0089] Second construction unit: The second construction unit is used to construct a version feature category decision tree based on a recursive algorithm of the first root node version feature and the version feature set.

[0090] Furthermore, the system further comprises:

[0091] a twelfth obtaining unit, configured to obtain associated sub-products of the first product in each of the versions;

[0092] A first conversion unit is configured to convert the associated sub-products of each version into an associated sub-product set of each version.

[0093] Furthermore, the system further comprises:

[0094] A first setting unit is configured to include the same associated sub-product in the associated sub-product set of each version.

[0095] Furthermore, the system further comprises:

[0096] The second setting unit is configured to include different associated sub-products in the associated sub-product set of each version.

[0097] Furthermore, the system further comprises:

[0098] A first saving unit is used to input and save the second sub-product set.

[0099] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. Figure 1 The method and specific examples for realizing the entry of parent-child associations of multi-version products in Example 1 are also applicable to the system for realizing the entry of parent-child associations of multi-version products in this embodiment. Through the above detailed description of the method for realizing the entry of parent-child associations of multi-version products, those skilled in the art can clearly understand the system for realizing the entry of parent-child associations of multi-version products in this embodiment. Therefore, for the sake of brevity of the specification, it will not be described in detail here. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple. For relevant parts, please refer to the description of the method part.

[0100] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present application. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments shown herein, but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

[0101] Exemplary electronic devices

[0102] Reference below Figure 6 To describe the electronic device of the embodiment of the present application.

[0103] Figure 6 The figure shows a schematic structural diagram of an electronic device according to an embodiment of the present application.

[0104] Based on the inventive concept of a method for realizing the entry of parent-child associations of multi-version products in the aforementioned embodiment, the present invention also provides a system for realizing the entry of parent-child associations of multi-version products, on which a computer program is stored, which, when executed by a processor, realizes the steps of any method of the aforementioned method for realizing the entry of parent-child associations of multi-version products.

[0105] Among them, Figure 6 In the embodiment of the present invention, a bus architecture (represented by bus 300) is shown. Bus 300 may include any number of interconnected buses and bridges. Bus 300 links various circuits together, including one or more processors represented by processor 302 and memory represented by memory 304. Bus 300 may also link various other circuits together, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not described further herein. Bus interface 305 provides an interface between bus 300 and receiver 301 and transmitter 303. Receiver 301 and transmitter 303 may be the same component, namely a transceiver, which provides a means for communicating with various other devices over a transmission medium.

[0106] The processor 302 is responsible for managing the bus 300 and general processing, while the memory 304 may be used to store data used by the processor 302 when performing operations.

[0107] The present application provides a method for implementing parent-child association entry of multi-version products, and the method is applied to a system for implementing parent-child association entry of multi-version products, wherein the method includes: obtaining a first product, wherein the first product has multiple versions; obtaining a version feature set of the first product; categorizing the version of the first product by using a decision tree for each version feature in the version feature set to obtain multiple versions of the first product; obtaining a set of associated sub-products for each of the versions; performing an OR logic operation on the set of associated sub-products for each of the versions to obtain a first sub-product set; in a contract scenario, selecting the first product and selecting or deselecting all sub-products in the first sub-product set respectively to obtain a second sub-product set; in a work order scenario, performing an AND logic operation on the set of associated sub-products for each of the versions and the second sub-product set to obtain a set of adapted sub-products for each of the versions. This solves the existing technical problem that when a product has multiple versions and there are differences in the sub-products fixedly associated between different versions, the sub-products that can be selected for association with any version of the product are restricted by both the sub-products required by the customer and the sub-products fixedly associated with each version, resulting in incomplete or even complete missing sub-products if the product in the work order scenario is inconsistent with the product entered in the contract. This achieves the technical effect of accurately displaying the transferred product and its sub-products from the contract scenario to the work order scenario by taking the union of all sub-products associated with the versions in the contract scenario and allowing selection, entry, and save operations when there are multiple versions of a product and there are differences in the sub-products fixedly associated between different versions. Furthermore, in the work order scenario, the intersection of the product required by the customer and the sub-products associated with the current version is calculated, completing the technical effect of accurately displaying the transferred product and its sub-products from the contract scenario to the work order scenario.

[0108] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, devices, or computer program products. Therefore, the present application may adopt a complete software embodiment, a complete hardware embodiment, or a combination of software and hardware embodiments. In addition, the present application is in the form of a computer program product that can be implemented on one or more computer-usable storage media containing computer-usable program code. The computer-usable storage medium includes, but is not limited to, various media that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk storage, a compact disc read-only memory (CD-ROM), and an optical storage device.

[0109] The present invention is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products of the embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as the combination of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A system that specifies the functions of a box or boxes.

[0110] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction system that is implemented in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0111] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps of the functions specified in the block or blocks are described. Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they are aware of the basic inventive concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0112] Obviously, those skilled in the art may make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if such changes and modifications fall within the scope of the claims and their equivalents, the present invention is intended to include such changes and modifications.

Claims

1. A method for implementing parent-child association entry for multi-version products, the method being applied to a system for implementing parent-child association entry for multi-version products, wherein: The method comprises: Obtaining a first product, wherein the first product has multiple versions; Obtaining a version feature set of the first product; Classify the versions of the first product by using each version feature in the version feature set through a decision tree to obtain multiple versions of the first product; Obtaining a set of associated sub-products for each of the versions; Performing an OR logical operation on the associated sub-product sets of each version to obtain a first sub-product set, where the first sub-product set is a set of all sub-products associated with the first product; In a contract scenario, the first product is selected and all sub-products in the first sub-product set are selected or deselected based on the requirements of the contract scenario to obtain a second sub-product set. The contract scenario refers to a contract signed between a manufacturing and sales enterprise and a purchasing customer. In the contract scenario, the first product required by the purchasing customer is selected so that the system displays a first sub-product set of the first product. Based on the purchasing customer's requirements, corresponding sub-products are selected for entry and saving. In the work order scenario, a logical operation is performed on the associated sub-product set of each version and the second sub-product set to obtain the product required by the customer and the adapted sub-product set of each version of the associated sub-product of the current version, so as to realize the transfer of products and their sub-product display from the contract scenario to the work order scenario. The work order scenario refers to the work document used by the production and sales company for its own management and record-keeping.

2. The method according to claim 1, wherein The classifying the versions of the first product by using each version feature in the version feature set through a decision tree to obtain multiple versions of the first product includes: Construct a version feature category decision tree; Each version feature of the first product is input into the version feature category decision tree to obtain multiple versions of the first product.

3. The method according to claim 2, wherein: The building version feature category decision tree includes: Obtaining a first version feature, a second version feature, and a third version feature from the version feature set; Performing information theory coding operations on the first version feature, the second version feature, and the third version feature respectively to obtain first version feature information entropy, second version feature information entropy, and third version feature information entropy; Obtaining a first root node version feature according to the first version feature information entropy, the second version feature information entropy, and the third version feature information; A version feature category decision tree is constructed based on a recursive algorithm of the first root node version feature and the version feature set.

4. The method according to claim 1, wherein The obtaining of a set of associated sub-products of each version includes: Obtain associated sub-products of the first product in each of the versions; Convert the associated sub-products of each version into an associated sub-product set of each version.

5. The method according to claim 1, wherein The associated sub-product set of each version includes the same associated sub-products.

6. The method of claim 1, wherein: The associated sub-product set of each version includes different associated sub-products.

7. The method of claim 1, wherein: In the contract scenario, after selecting the first product and selecting all sub-products in the first sub-product set to obtain the second sub-product set, the method includes: The second sub-product set is entered and saved.

8. A system for recording parent-child relationships between multiple versions of products, wherein: The system comprises: First obtaining unit: The first obtaining unit is used to obtain a first product, wherein the first product has multiple versions; Second obtaining unit: The second obtaining unit is used to obtain a version feature set of the first product; A third obtaining unit: the third obtaining unit is configured to classify the versions of the first product using a decision tree for each version feature in the version feature set, thereby obtaining multiple versions of the first product; Fourth obtaining unit: the fourth obtaining unit is used to obtain a set of associated sub-products of each version; A fifth obtaining unit: the fifth obtaining unit is configured to perform an OR logic operation on the associated sub-product sets of each version to obtain a first sub-product set, where the first sub-product set is a set of all sub-products associated with the first product; Sixth obtaining unit: The sixth obtaining unit is configured to select the first product in a contract scenario and select or deselect all sub-products in the first sub-product set according to the requirements of the contract scenario to obtain a second sub-product set. The contract scenario refers to a contract signed between a manufacturing and sales enterprise and a purchasing customer. In the contract scenario, the first product required by the purchasing customer is selected so that the system displays the first sub-product set of the first product. Corresponding sub-products are selected according to the purchasing customer's requirements for entry and storage. The seventh acquisition unit: The seventh acquisition unit is used to perform a logical operation on the associated sub-product set of each version and the second sub-product set in the work order scenario, and respectively obtain the product required by the customer and the adaptive sub-product set of each version of the associated sub-product of the current version, so as to realize the transfer of products and their sub-product display from the contract scenario to the work order scenario. The work order scenario refers to the work document used by the production and sales company for its own management and record-keeping.

9. A system for recording parent-child associations of multiple versions of products, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the steps of the method according to any one of claims 1 to 7 are implemented.

Images