A product information management method and related device
By merging product information hierarchies and nodes from different departments into a tree structure, the problem of data mismatch in the retail and FMCG industry was solved, achieving efficient data unification and communication, and improving enterprise operational efficiency.
Patent Information
- Application Number
- CN202211044753.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-08-30
- Publication Date
- 2025-12-23
- Estimated Expiration
- 2042-08-30
AI Technical Summary
In the retail and fast-moving consumer goods industry, the existing methods for maintaining product information hierarchy lack structure and transparency, leading to data mismatch when different departments switch planning perspectives, increasing communication and troubleshooting costs, and affecting data timeliness and business operations.
By receiving product information hierarchies and nodes from different departments and merging them into a tree structure for display, and by matching enterprise organizational structure and e-commerce platform data, the system can automatically adjust and generate collaborative information error prompts, thereby improving data consistency and communication efficiency.
It simplified the process of switching perspectives between departments, improved the quality and efficiency of data statistics, reduced communication costs, and ensured the timeliness of data and the smooth operation of the enterprise.
Smart Images

Figure CN115455242B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of computer, in particular to a product information management method and related equipment. BACKGROUND
[0002] In the demand planning scenario of the retail fast-consumption industry, the planning coordination personnel need to frequently switch the planning perspective to analyze and verify whether the plan meets the business objectives of the enterprise, market trends and supply constraints. The faster and more accurate the analysis and verification work is completed, the more market competitive advantage the enterprise can obtain. At present, the hierarchical information maintenance is usually realized by relying on manual or unstructured and non-transparent maintenance system, which causes low statistical quality and statistical efficiency when planning coordination is carried out under different planning perspectives. For example, when planning coordination or transmission is needed, the results obtained by a certain department according to the hierarchical data maintained by itself for statistics and analysis will deviate from the maintenance standards of other departments due to the lack of structured maintenance rules. In the case of statistics and analysis required by other departments, hierarchical data needs to be maintained again, which results in high cost and long time for communication and troubleshooting. SUMMARY
[0003] The present application provides a product information management method to solve the problem that the data information obtained when the planning perspective is switched and the demand planning statistics are carried out in each department of the enterprise is not adapted to the department demand information due to the low structure and transparency of the current product information hierarchical maintenance method, and further communication and troubleshooting based on the inadapted data are needed, which increases the workload and working hours of the staff, affects the timeliness of the data, and further affects the operation of the enterprise.
[0004] In a first aspect, the present application provides a product information management method, comprising:
[0005] receiving a first product information hierarchy and a first hierarchical node associated with a target product sent by a first client;
[0006] receiving a second product information hierarchy and a second hierarchical node associated with the target product sent by a second client, the second client and the first client belonging to different departments in an organizational department architecture;
[0007] merging the first product information hierarchy and the second product information hierarchy, and merging the first hierarchical node and the second hierarchical node, so that the first product information hierarchy, the first hierarchical node, the second product information hierarchy and the second hierarchical node are displayed in a tree structure.
[0008] Optionally, the product information management method further comprises:
[0009] In a case where the second hierarchical node is the same as the first hierarchical node and a first product information hierarchy to which the first hierarchical node belongs and a second product information hierarchy to which the second hierarchical node belongs are different, traversing the organization department architecture;
[0010] In a case where a department hierarchy to which the second client belongs is higher than a department hierarchy to which the first client belongs, replacing the first hierarchical node with the second hierarchical node, otherwise, ignoring the second hierarchical node.
[0011] Optionally, the product information management method further comprises:
[0012] In a case where the second hierarchical node is the same as the first hierarchical node and a first product information hierarchy to which the first hierarchical node belongs and a second product information hierarchy to which the second hierarchical node belongs are different, obtaining an e-commerce product hierarchy to which the second hierarchical node belongs in an e-commerce platform;
[0013] Selecting a product information hierarchy matching the e-commerce product hierarchy from the first product information hierarchy and the second product information hierarchy as a product information hierarchy to which the second hierarchical node and the first hierarchical node belong.
[0014] Optionally, the product information management method further comprises:
[0015] In a case where the second hierarchical node is the same as the first hierarchical node and a first product information hierarchy to which the first hierarchical node belongs and a second product information hierarchy to which the second hierarchical node belongs are different, triggering a conversation window in the first client and the second client at the same time, the conversation window including a user to which the first client belongs and a user to which the second client belongs;
[0016] Generating a collaborative information error prompt in the conversation window.
[0017] Optionally, the generating a collaborative information error prompt in the conversation window comprises:
[0018] Displaying a historical tree structure before merging in the conversation window, and displaying a first tree structure generated after the first product information hierarchy and the first hierarchical node are added to the historical tree structure and a second tree structure generated after the second product information hierarchy and the second hierarchical node are added to the historical tree structure, respectively.
[0019] Optionally, the product information management method further comprises:
[0020] Calculating a demand plan result of a preset type through the first tree structure and the second tree structure, respectively;
[0021] Display the demand plan results corresponding to the first tree structure and the second tree structure respectively in the dialog window.
[0022] Optionally, the product information management method further comprises:
[0023] Display the actual demand of the historical same period of the preset type.
[0024] In a second aspect, the present application provides a product information management device, comprising:
[0025] A first receiving module is configured to receive a first product information hierarchy and a first hierarchy node associated with a target product sent by a first client;
[0026] A second receiving module is configured to receive a second product information hierarchy and a second hierarchy node associated with the target product sent by a second client, the second client and the first client belonging to different departments in an organizational department framework;
[0027] A processing module is configured to merge the first product information hierarchy and the second product information hierarchy, and merge the first hierarchy node and the second hierarchy node, so that the first product information hierarchy, the first hierarchy node, the second product information hierarchy and the second hierarchy node are displayed in a tree structure.
[0028] In a third aspect, the present application provides an electronic device, comprising a memory and a processor, the processor being configured to execute a computer program stored in the memory to realize the steps of the product information management method according to any one of the first aspect.
[0029] In a fourth aspect, the present application provides a computer readable storage medium, having a computer program stored thereon, the computer program being executed by a processor to realize the steps of the product information management method according to any one of the first aspect.
[0030] From the above technical solutions, the embodiment of the present application provides a product information management method, comprising: receiving first product information hierarchy and first hierarchy node associated with a target product sent by a first client; receiving second product information hierarchy and second hierarchy node associated with the target product sent by a second client, the second client and the first client belong to different departments in an organizational department architecture; merging the first product information hierarchy and the second product information hierarchy, and merging the first hierarchy node and the second hierarchy node, so that the first product information hierarchy, the first hierarchy node, the second product information hierarchy and the second hierarchy node are displayed in a tree structure. Since the current hierarchy information maintenance is usually realized by relying on manual or unstructured and non-transparent maintenance system, it will cause low statistical quality and statistical efficiency when planning collaboration is carried out under different plan perspectives, and further cause high cost and long time of communication and troubleshooting. The embodiment of the present application integrates the information hierarchy and hierarchy node of the same product sent by different departments and displays in a tree structure, which can improve the efficiency of different departments in the perspective switching process and simplify the switching operation steps. BRIEF DESCRIPTION OF DRAWINGS
[0031] In order to more clearly illustrate the technical solutions of the present application, the drawings needed in the embodiments will be briefly introduced below. Obviously, for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.
[0032] Figure 1 A schematic flow chart of a product information management method provided by the embodiment of the present application is shown in the figure.
[0033] Figure 2 A schematic structural diagram of a product information management device provided by the embodiment of the present application is shown in the figure.
[0034] Figure 3 A schematic structural diagram of an electronic device provided by the embodiment of the present application is shown in the figure.
[0035] Figure 4 A schematic structural diagram of a computer readable storage medium provided by the embodiment of the present application is shown in the figure. DETAILED DESCRIPTION
[0036] The embodiments will be described in detail below with reference to drawings, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following embodiments are not meant to represent all implementations consistent with the present disclosure. Rather, they are merely examples of implementations consistent with some aspects of the present disclosure as detailed in the claims. In several embodiments provided by the present disclosure, it should be understood that the disclosed apparatus and methods can also be implemented in other manners. The embodiments described in the present disclosure are merely exemplary.
[0037] As Figure 1 described above, the embodiments of the present disclosure provide a product information management method, Figure 1 A schematic flowchart of a product information management method provided by the embodiments of the present disclosure is shown in FIG. 1. The method includes the following steps.
[0038] In step S110, a first product information hierarchy and a first hierarchy node associated with a target product are received from a first client.
[0039] For example, in a clothing enterprise, the product information hierarchy can include brand, category, style, and size. The hierarchy node is the category to which the product belongs in the product information hierarchy, which can be set uniformly when the enterprise builds the product information hierarchy.
[0040] In step S120, a second product information hierarchy and a second hierarchy node associated with the target product are received from a second client, the second client and the first client belonging to different departments in the organizational department structure.
[0041] In step S130, the first product information hierarchy and the second product information hierarchy are merged, and the first hierarchy node and the second hierarchy node are merged, so that the first product information hierarchy, the first hierarchy node, the second product information hierarchy, and the second hierarchy node are displayed in a tree structure.
[0042] For example, in the tree structure, any member has at least one of a parent member and a child member, which is used to depict and describe the relationship between products under different demand plan perspectives, such as inclusion and inheritance. The first product information hierarchy and the second product information hierarchy of the target product can be merged based on the demand plan of the enterprise, and the first hierarchy node and the second hierarchy node can be merged. After the information hierarchy and the hierarchy node are merged, the tree structure can automatically locate the merged information hierarchy and hierarchy node, and automatically determine the information hierarchy and hierarchy node located in the upper and lower layers.
[0043] By integrating the product information levels and level nodes sent by different departments, the uniformity of the data structures of the departments can be ensured, the data can be automatically aggregated and automatically split based on the needs of different departments in a tree structure, and thus the switching operation steps can be simplified and the work efficiency of the different departments in the perspective switching process can be improved.
[0044] According to some embodiments, the method further includes:
[0045] In a case where the second level node is the same as the first level node and the first product information level to which the first level node belongs is different from the second product information level to which the second level node belongs, traversing the organizational department architecture;
[0046] In a case where the department level to which the second client belongs is higher than the department level to which the first client belongs, replacing the first level node with the second level node, otherwise, ignoring the second level node.
[0047] For example, in the organizational architecture of an enterprise, the department level to which the marketing department belongs is higher than the department level to which the sales department belongs, in a case where the level nodes are all juice, the product information level associated with the juice sent by the marketing department is the beverage level, the product level associated with the juice sent by the sales department is the juice level, and the juice level and the beverage level are at the same product information level. Therefore, in the tree structure, the juice needs to be determined as the juice node under the beverage level.
[0048] Because there may be information asymmetry when the enterprise changes the demand plan, resulting in differences in the product information levels and level nodes of the same target product between the departments belonging to different department levels, determining the product information levels and level nodes according to the organizational department architecture of the enterprise can avoid the non-uniformity of the data structures of the departments of the enterprise due to information asymmetry, can improve the uniformity of the data structures of the departments, and thus can improve the work efficiency of the departments in the perspective switching process.
[0049] According to some embodiments, the method further includes:
[0050] In a case where the second level node is the same as the first level node and the first product information level to which the first level node belongs is different from the second product information level to which the second level node belongs, obtaining the e-commerce product level to which the second level node belongs in the e-commerce platform;
[0051] The product information level matching the e-commerce product level is selected from the first product information level and the second product information level as the product information level to which the second level node and the first level node belong.
[0052] For example, the e-commerce product level to which the target product belongs in the e-commerce platform is the classification information of the target product in the e-commerce platform, which can be directly obtained according to the classification to which the product sold by the enterprise belongs in the associated e-commerce platform.
[0053] Since the retail enterprise has the demand for selling products in the e-commerce platform, directly determining the product information level to which the target product belongs based on the e-commerce product level can improve the quality and extraction efficiency of the product demand statistical data of the e-commerce platform, and can simplify the switching operation steps.
[0054] According to some embodiments, the method further comprises:
[0055] In the case where the second level node is the same as the first level node and the first product information level to which the first level node belongs is different from the second product information level to which the second level node belongs, a dialogue window is triggered in the first client and the second client at the same time, and the dialogue window includes the user to which the first client belongs and the user to which the second client belongs.
[0056] A collaboration information error prompt is generated in the dialogue window.
[0057] For example, the collaboration information error prompt can include the first level node, the first product information level, the second product information level, all level nodes of the first product level and the second product level, and the number of level nodes in the first product level and the second product level that are close to the first level node.
[0058] In the case where the level node to which the target product belongs cannot be determined, at least two clients with different opinions can be added to the same dialogue window to improve the communication efficiency and reduce the communication cost, thereby facilitating the uniformity of the data structure and the overall operation of the enterprise.
[0059] According to some embodiments, the collaboration information error prompt is generated in the dialogue window, comprising:
[0060] The historical tree structure before merging is displayed in the dialogue window, and the first tree structure generated after the first product information level and the first level node are added to the historical tree structure and the second tree structure generated after the second product information level and the second level node are added to the historical tree structure are displayed respectively.
[0061] By displaying the tree structure of the product information hierarchy and the hierarchy nodes sent by different clients in the above dialogue window, the department to which the client in the dialogue window belongs can more intuitively obtain the updated tree diagram, and communication can be carried out based on the above updated tree diagram, which can improve the communication efficiency and reduce the communication cost.
[0062] According to some embodiments, the above method further comprises:
[0063] The demand plan results of the preset type are determined based on the demand plan data of the product information hierarchy to which the preset type belongs, and can be directly obtained through the first tree structure and the second tree structure.
[0064] The demand plan results of the preset type are determined based on the demand plan data of the product information hierarchy to which the preset type belongs, and can be directly obtained through the first tree structure and the second tree structure.
[0065] For example, the preset type is determined based on the demand plan of the department hierarchy to which the client belongs, and the product information hierarchy to which the preset type belongs can be at least one of the first product information hierarchy, the second product information hierarchy, and an upper hierarchy of the first product information hierarchy and / or the second product information hierarchy. The demand plan result of the preset type is determined based on the demand plan data of the product information hierarchy to which the preset type belongs, and can be directly obtained through the first tree structure and the second tree structure.
[0066] By directly displaying the corresponding demand plan result in the above dialogue window, the department to which the client in the dialogue window belongs can more intuitively obtain the demand plan result, and communication can be carried out based on the above demand plan result combined with actual production and sales data, which can improve the communication efficiency and communication quality, and reduce the communication cost.
[0067] According to some embodiments, the above method further comprises:
[0068] The historical actual demand of the preset type is displayed.
[0069] By displaying the historical actual demand of the preset type in the above dialogue window, the department to which the client in the dialogue window belongs can communicate based on historical data, and make a comprehensive judgment based on the current demand plan, which can improve the convenience and efficiency of communication, reduce the communication cost, and improve the uniformity of the data structure.
[0070] Please refer to Figure 2 , Figure 2 A schematic structural diagram of a product information management device provided by an embodiment of the present application. The embodiment of the present application provides a product information management device 200, which comprises:
[0071] The first receiving module 201 is configured to receive the first product information hierarchy and the first hierarchy node associated with the target product sent by the first client.
[0072] The second receiving module 202 is configured to receive a second product information hierarchy and a second hierarchy node associated with the target product and sent by a second client, the second client and the first client belonging to different departments in an organizational department framework.
[0073] The processing module 203 is configured to merge the first product information hierarchy and the second product information hierarchy, and merge the first hierarchy node and the second hierarchy node, so that the first product information hierarchy, the first hierarchy node, the second product information hierarchy and the second hierarchy node are displayed in a tree structure.
[0074] The product information management device 200 can realize Figure 1 The processes realized in the method embodiment are not repeated here to avoid repetition.
[0075] As Figure 3 shown, Figure 3 a schematic structural diagram of an electronic device provided in the embodiments of the present application.
[0076] The embodiments of the present application provide an electronic device 300, which comprises a memory 310, a processor 320, and a computer program 311 stored in the memory 310 and capable of running on the processor 320, and the processor 320 realizes the following steps when executing the computer program 311.
[0077] The first product information hierarchy and the first hierarchy node associated with the target product and sent by a first client are received.
[0078] The second product information hierarchy and the second hierarchy node associated with the target product and sent by a second client are received, the second client and the first client belonging to different departments in an organizational department framework.
[0079] The first product information hierarchy and the second product information hierarchy are merged, and the first hierarchy node and the second hierarchy node are merged, so that the first product information hierarchy, the first hierarchy node, the second product information hierarchy and the second hierarchy node are displayed in a tree structure.
[0080] Since the electronic device introduced in the embodiments is a device used to implement the device in the embodiments of the present application, the specific implementation of the electronic device and its various forms can be understood by those skilled in the art based on the method introduced in the embodiments of the present application. Therefore, how the electronic device realizes the method in the embodiments of the present application is not described in detail here, as long as the device used by those skilled in the art to implement the method in the embodiments of the present application belongs to the scope of the present application.
[0081] AsFigure 4 As shown, Figure 4 An illustrative structural diagram of a computer readable storage medium provided by an embodiment of the present application.
[0082] The embodiment provides a computer readable storage medium 400, and the computer readable storage medium 400 stores a computer program 411. The computer program 411 is executed by a processor to implement the following steps.
[0083] Receiving first product information hierarchy and first hierarchy node associated with a target product sent by a first client;
[0084] Receiving second product information hierarchy and second hierarchy node associated with the target product sent by a second client, the second client and the first client belonging to different departments in an organizational department framework;
[0085] Merging the first product information hierarchy and the second product information hierarchy, and merging the first hierarchy node and the second hierarchy node, so that the first product information hierarchy, the first hierarchy node, the second product information hierarchy and the second hierarchy node are displayed in a tree structure.
[0086] It should be noted that in the above embodiments, the description of each embodiment has its own emphasis, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.
[0087] Those skilled in the art should understand that embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can adopt a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can adopt a computer program product in the form of one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
[0088] The present application is described with reference to flowcharts and / or block diagrams according to the method, device (system), and computer program product of the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows 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 general-purpose computer, a special-purpose computer, an embedded computer, or other programmable data processing devices to produce a machine, so that the instructions executed by the computer or other programmable data processing devices produce a device for implementing the functions specified in the flowcharts and / or block diagrams. Figure 1 The device for implementing the functions specified in one flow or multiple flows and / or blocks. Figure 1 The device for implementing the functions specified in one flow or multiple flows and / or blocks.
[0089] These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions which implement the flow Figure 1 one or more flow or block Figure 1 one or more flow or block
[0090] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions executed on the computer or other programmable apparatus provide steps for implementing the flow Figure 1 one or more flow or block Figure 1 one or more flow or block
[0091] The embodiments of the present application also provide a computer program product, which includes computer software instructions, when the computer software instructions are run on a processing device, cause the processing device to execute the flow Figure 1 in the product information management method in the corresponding embodiments.
[0092] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function described in the embodiments of the present application is produced. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium that can be stored by the computer or data storage device such as server, data center, etc. integrated with one or more available media sets. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), optical media (for example, DVD), or semiconductor media (for example, solid state disk (SSD)) and the like.
[0093] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be described here.
[0094] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other manners. For example, the described device embodiments are merely schematic. The division of the units is merely logical function division. There can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be indirect couplings or communication connections through some interfaces, devices or units, and can be in electrical, mechanical or other forms.
[0095] The units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments.
[0096] In addition, each functional unit in the embodiments of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
[0097] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on such an understanding, the technical solutions of the present application essentially or substantially, or all or part of the technical solutions, can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. The foregoing storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and various other media that can store program codes.
[0098] In summary, the above examples are only used to illustrate the technical solutions of the present application, rather than limit them; although the present application has been described in detail with reference to the foregoing examples, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing examples, or make equivalent replacements for part of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims
1. A product information management method characterized by comprising: The method comprises the following steps: receiving first product information hierarchy and first hierarchy node associated with a target product sent by a first client; receiving second product information hierarchy and second hierarchy node associated with the target product sent by a second client, the second client belonging to a different department in the organizational department framework from the first client; merging the first product information hierarchy and the second product information hierarchy, and merging the first hierarchy node and the second hierarchy node, so that the first product information hierarchy, the first hierarchy node, the second product information hierarchy and the second hierarchy node are displayed in a tree structure; in the case that the second hierarchy node is the same as the first hierarchy node and the first product information hierarchy to which the first hierarchy node belongs is different from the second product information hierarchy to which the second hierarchy node belongs, obtaining an e-commerce product hierarchy to which the second hierarchy node belongs in an e-commerce platform; selecting a product information hierarchy matching the e-commerce product hierarchy in the first product information hierarchy and the second product information hierarchy as the product information hierarchy to which the second hierarchy node and the first hierarchy node belong; the e-commerce product hierarchy to which the second hierarchy node belongs in the e-commerce platform is the classification information of the target product in the e-commerce platform, which can be directly obtained through the classification of the product sold by the enterprise in the associated e-commerce platform.
2. The method of claim 1, wherein, Further comprising: in the case that the second hierarchy node is the same as the first hierarchy node and the first product information hierarchy to which the first hierarchy node belongs is different from the second product information hierarchy to which the second hierarchy node belongs, traversing the organizational department framework; in the case that the department hierarchy to which the second client belongs is higher than the department hierarchy to which the first client belongs, replacing the first hierarchy node with the second hierarchy node, otherwise, ignoring the second hierarchy node.
3. The method of claim 1, wherein, Further comprising: in the case that the second hierarchy node is the same as the first hierarchy node and the first product information hierarchy to which the first hierarchy node belongs is different from the second product information hierarchy to which the second hierarchy node belongs, triggering a dialogue window in the first client and the second client at the same time, the dialogue window including the user to which the first client belongs and the user to which the second client belongs; generating a collaborative information error prompt in the dialogue window.
4. The method of claim 3, wherein, The collaborative information error prompt generated in the dialogue window comprises: displaying the historical tree structure before merging in the dialogue window, and displaying the first tree structure generated after the first product information hierarchy and the first hierarchy node are added to the historical tree structure and the second tree structure generated after the second product information hierarchy and the second hierarchy node are added to the historical tree structure.
5. The method of claim 4, wherein, Further comprising: calculating demand planning results of a preset type through the first tree structure and the second tree structure respectively; displaying the demand planning results corresponding to the first tree structure and the second tree structure respectively in the dialogue window.
6. The method of claim 5, wherein, Further comprising: displaying the actual demand of the preset type in the same period.
7. A product information management device characterized by comprising: The first receiving module is configured to receive a first product information hierarchy and a first hierarchy node associated with a target product sent by a first client; The second receiving module is configured to receive a second product information hierarchy and a second hierarchy node associated with the target product sent by a second client, the second client and the first client belonging to different departments in an organizational department architecture; The processing module is configured to merge the first product information hierarchy and the second product information hierarchy, and merge the first hierarchy node and the second hierarchy node, so that the first product information hierarchy, the first hierarchy node, the second product information hierarchy and the second hierarchy node are displayed in a tree structure; In a case where the second hierarchy node is the same as the first hierarchy node and the first product information hierarchy to which the first hierarchy node belongs and the second product information hierarchy to which the second hierarchy node belongs are different, an e-commerce product hierarchy to which the second hierarchy node belongs in an e-commerce platform is obtained; In a case where the first product information hierarchy and the second product information hierarchy are selected to match a product information hierarchy in the e-commerce product hierarchy, the product information hierarchy to which the second hierarchy node and the first hierarchy node belong is selected; the e-commerce product hierarchy in the e-commerce platform is classification information of the target product in the e-commerce platform, and can be directly obtained through a classification to which a product sold by an enterprise in the associated e-commerce platform belongs.
8. An electronic device comprising a memory, a processor, characterized in that, The processor is configured to implement the steps of the product information management method according to any one of claims 1 to 6 when executing the computer program stored in the memory.
9. A computer readable storage medium having stored thereon a computer program, characterized in that: The computer program is configured to implement the steps of the product information management method according to any one of claims 1 to 6 when executed by the processor.
Citation Information
Patent Citations
Synchronizing multiple hierarchal data structures
US8301994B1