Unified model and system implementation for SKU attribute definition and enumeration value setting in enterprise commodity or raw material information management system

Abstract

The present application relates to the technical field of data management and front-end interaction, and particularly relates to a unified model and system implementation for SKU attribute definition and enumeration value setting in an enterprise commodity or raw material information management system. The technical problem to be solved is that the existing SKU attribute enumeration value lacks unified ID management, resulting in a large number of repeated values in the database, slow performance in large-scale import, redundant and slow response of front-end filtering options, and user misoperation due to the same name but different ID attributes. The technical scheme mainly comprises: providing an independent attribute enumeration value preset page, and an operator can predefine standard enumeration values of attributes such as color, shape and fineness; a binding relationship between the enumeration value and the commodity category, type and material is established, and the user can reference the preset enumeration value by selecting the category range on the commodity setting page, so as to ensure data consistency; and the front-end interface adopts an optimization mode of omitting display and hovering prompt, thereby improving the user operation experience and interface neatness. The beneficial effect is that the unified management at the data level fundamentally eliminates data redundancy, significantly improves the import, filtering and response performance of the system under large data volume, and reduces the user operation error rate.

Description

Technical Field

[0001] This invention relates to the field of computer software technology, and in particular to data governance and front-end interaction technology in systems such as enterprise commodity or raw material information management systems and manufacturing production process information management systems. Specifically, it relates to a unified model and system implementation for defining SKU attributes and setting enumeration values ​​in an enterprise commodity or raw material information management system. Background Technology

[0002] In product information management systems, product attributes (such as color, shape, clarity, and size) are typically represented as enumerated values, allowing users to select them from dropdown lists, checkboxes, and other front-end components. However, existing technologies suffer from the following common problems:

[0003] 1. Data Redundancy and Inconsistency: Due to the lack of a unified enumeration value management center, when configuring attributes with the same name for different product materials (for example, configuring a color attribute named "dark blue" for "opal" and "jade" materials respectively), the system will generate multiple records with the same name but different IDs. This results in the database being filled with a large number of completely duplicate enumeration values, which not only wastes storage space, but more seriously, this phenomenon of "same name, different ID" completely undermines the uniqueness and consistency of the data, creating serious hidden dangers for subsequent data queries, filtering, and correlation analysis.

[0004] 2. System performance bottleneck: In large-scale data scenarios, such as customers with tens of thousands of materials, the query and filtering functions in the product database and operation table will become extremely slow due to the need to process a large number of duplicate and non-duplicate enumerated value options, which will seriously affect the user experience and system response efficiency.

[0005] 3. Chaotic Front-End Interaction: When filtering or selecting attributes, the front-end controls load all possible enumeration values, including a large number of duplicates. This not only makes the dropdown list unnecessarily long, but also easily leads to data confusion caused by users selecting options with the same name but different IDs, creating potential problems for subsequent data analysis and business processing.

[0006] 4. Difficult data maintenance: The creation, deletion, modification, and querying of enumerated values ​​are scattered throughout the system, resulting in high maintenance costs and difficulty in ensuring data consistency across different business modules. Some existing solutions attempt to alleviate the problem through front-end validation or local caching, but they fail to establish a unified management system at the data source that can be associated with business semantics, thus providing only temporary solutions. Summary of the Invention

[0007] (a) Technical problems to be solved

[0008] This invention aims to solve the technical problems caused by the lack of unified and standardized ID management for product attribute enumeration values, such as data redundancy, low system performance, poor front-end interactive experience, and difficulty in data maintenance.

[0009] (II) Technical Solution To achieve the above objectives, this invention proposes a unified model and system implementation for defining SKU attributes and setting enumeration values ​​in an enterprise commodity or raw material information management system. Its core lies in building a centralized enumeration value management architecture.

[0010] This method mainly includes the following steps:

[0011] S1: Provides a pre-defined enumeration value interface independent of the business setup process. System operators can pre-define a standard, non-repeating list of enumeration values ​​for various SKU attributes (such as color, shape, clarity, etc.) on this interface. This interface supports operations such as sorting, adding, deleting, copying, batch importing, and filling enumeration values.

[0012] S2: Establish the binding relationship between standard enumeration values ​​and product category information. Product category information includes at least product category, product type, and product material. Through this binding, an enumeration value (such as "round") is associated with a specific category range (such as "Category: Jewelry -> Type: Diamond -> Material: Platinum").

[0013] S3: Provides a "Product Settings Interface". When a user selects category information (category, type, material) for a specific product on this interface, the system will dynamically and accurately load the corresponding attribute enumeration value options based on the established binding relationship, thereby avoiding the user seeing or selecting irrelevant or duplicate options.

[0014] S4: When displaying on the front end, perform "visual optimization" on excessively long enumeration value text. That is, by default, it is displayed in an abbreviated form (such as "..."). When the user hovers the mouse over the text, the full content is displayed through the tooltip component, thereby saving interface space and keeping it clean.

[0015] S5: Store the user's final confirmed product information and its associated standard enumeration value ID into the database to ensure data consistency and standardization at the storage level.

[0016] (III) Beneficial Effects Compared with the prior art, the present invention has the following significant advantages:

[0017] 1. Data Root Cause Governance: Through centralized preset and binding mechanisms, the duplication and chaos of enumeration values ​​are eliminated from the source, achieving data standardization and uniqueness, laying the foundation for high-quality data analysis.

[0018] 2. Significantly improved performance: It greatly reduces redundant data in the database and significantly reduces the number of options for front-end filtering and loading, thereby significantly improving the speed of large-scale data import, querying and front-end interface response.

[0019] 3. User experience optimization: The front-end options are clear, accurate, and non-repetitive. Combined with intelligent omission and hover prompt design, it effectively reduces user confusion and error rate, and improves operation efficiency.

[0020] 4. Convenient and efficient maintenance: The maintenance of all enumeration values ​​is carried out in one place, and the changes can be applied globally, which greatly reduces the maintenance cost and complexity of the system. Attached Figure Description

[0021] Figure 1 shows the relationship between system module functions and data interaction.

[0022] Figure 2 is a schematic diagram of the enumeration value preset interface provided in an embodiment of the present invention.

[0023] Figure 3 is a schematic diagram of the binding relationship between enumeration values ​​and product categories provided in an embodiment of the present invention.

[0024] Figure 4 is a flowchart illustrating the process of dynamically loading enumeration value options in the product settings interface according to the present invention.

[0025] Figure 5 is a schematic diagram of the interaction between long text omission and hover prompt in the product settings interface provided in an embodiment of the present invention. Detailed Implementation

[0026] A preferred embodiment of the present invention will now be described in detail with reference to the accompanying drawings. This embodiment is implemented based on the technical solution of the present invention, but the scope of protection of the present invention is not limited to the following embodiment.

[0027] When the system of the present invention is implemented, its core architecture and module interaction relationship are shown in Table 1. It mainly includes four modules that work together: enumeration value preset module, binding relationship management module, product setting module and data storage module.

[0028] 1. Implementation of the enumeration value preset module

[0029] Referring to Figure 2, the enumeration value preset module (corresponding to Table 1) provides an independent web management interface. System operators can predefine system-wide unique standard enumeration values ​​for different SKU attributes (such as "color," "shape," and "clarity"). This interface provides operation buttons for sorting, adding, saving, deleting, importing, copying, and batch filling, and supports filtering by product category, type, and material. Its core function is to ensure the uniqueness and standardization of enumeration values ​​from the source, laying the data foundation for subsequent accurate binding.

[0030] 2. Implementation of the Binding Relationship Management Module

[0031] The binding relationship management module (corresponding to Table 1) is the logical core of the system, maintaining a set of binding rules between enumeration values ​​and product categories in the background. As illustrated in Figure 3, this module manages a relational data table, whose key fields include: "Attribute Type", "Enumeration Value ID", "Associated Product Category", "Associated Product Type", and "Associated Product Material". When an operator binds the enumeration value "dark blue" to "Category: Jewelry -> Type: Colored Gemstone -> Material: Opal" in the interface shown in Figure 2, this module creates a corresponding binding record in the database.

[0032] This mechanism fundamentally solves the data redundancy problem of "same name, different IDs". For example, when an operator needs to configure the same color "dark blue" for both "opal" and "jade" materials, they don't create separate "dark blue" entries for each. Instead, they select the same "dark blue" entry (with a fixed ID) from a unified pre-defined enumeration value library and bind it to both the "opal" and "jade" materials. This means that no matter how many materials "dark blue" appears on, it always points to the same unique ID in the database. This design ensures global uniqueness and consistency of data, completely eliminating data silos and query errors caused by ID confusion.

[0033] 3. Implementation of the Product Setting Module The product settings module (corresponding to Table 1) is designed for end users, and its dynamic loading process for options is shown in Figure 4: Step 1: Trigger Executing entity: User Action: In the product settings interface, specific [Product Category], [Product Type], and [Product Material] were selected. Step Two: Request Execution Entity: Product Settings Module (Frontend) Action: Upon detecting a change in product category selection, automatically send an asynchronous request (AJAX / API request) to the backend server. This request carries the product category information selected by the user. Step 3: Processing Execution Entity: Binding Relationship Management Module (Backend) Action: Receive frontend requests, parse out product category information, and generate corresponding database query commands. Step 4: Query Execution Entity: Data Storage Module (Database) Action: Execute the query command, search the "Enumeration Value - Category Binding Relationship Table" for all standard enumeration value IDs and names that match the requested category information, and return the result list to the backend module. Step 5: Return Execution Entity: Binding Relationship Management Module (Backend) Action: Return the list of enumerated values ​​retrieved from the database to the front end via an HTTP response. Step Six: Rendering Execution Entity: Product Settings Module (Frontend) Action: After successfully receiving the list of enumerated values ​​returned by the backend, dynamically update the dropdown selection boxes for the corresponding attributes (such as "color" and "shape") on the webpage using JavaScript, filling the list with selectable options.

[0034] 4. Implementation of front-end interaction optimization Referring to Figure 5, in the interface of the product settings module, front-end optimizations were implemented to improve the display effect of long text and the cleanliness of the interface:

[0035] Omitted display: For field values ​​(such as material or attribute names) whose character length exceeds a preset threshold, the system will truncate them by default and display them with an ellipsis ("...").

[0036] Hover tooltip: By binding a "mouseover" event to this HTML element, when the user hovers the mouse pointer over the field, a floating window is dynamically triggered using the browser API or the tooltip component of the front-end UI framework. This floating window displays the entire content of the field. This design ensures complete readability of the information without occupying additional UI space.

[0037] Through the coordinated implementation of the above modules, this invention constructs a complete solution from data definition and binding association to front-end intelligent interaction, which efficiently solves the problems of data redundancy, low system performance, chaotic front-end interaction and difficult data maintenance mentioned in the background technology.

Claims

1. A unified management method for defining SKU attributes and setting enumeration values ​​in an enterprise product or raw material information management system, characterized in that, Includes the following steps: Provides a separate enumeration value preset interface for receiving and storing standard enumeration value definitions for different SKU attributes; Establish a binding relationship between the standard enumeration values ​​and product category information, wherein the product category information includes at least product category, product type and product material; provide a product settings interface, which, in response to the user's selection operation of product category information, dynamically loads and presents the corresponding attribute options from the bound standard enumeration values ​​for the user to select; and associates and stores the product category information finally selected by the user and the corresponding standard enumeration values ​​in the product settings data table.

2. The method according to claim 1, characterized in that, In the product settings interface, when the character length of the standard enumeration value exceeds a preset threshold, it is displayed in an abbreviated form in the display area, and when the user's hover operation is detected, the enumeration value content is fully displayed in the form of a prompt box.

3. The method according to claim 1, characterized in that, The specific steps for establishing the binding relationship are as follows: the standard enumeration value is associated with a specific product category, product type and product material, so that in the product settings interface, the corresponding standard enumeration value is presented as an optional option only when the product category information selected by the user matches the binding relationship.

4. The method according to claim 1, characterized in that, The method further includes a batch operation step, which includes at least: batch importing preset enumeration values, batch copying enumeration value definitions, and batch filling a preset enumeration value into multiple specified product category binding relationships.

5. The method according to claim 1, characterized in that, The enumeration value preset interface provides functions for sorting, adding, editing, deleting, and filtering by product category information for defined standard enumeration values.

6. A unified management system for defining SKU attributes and setting enumeration values ​​in an enterprise's product or raw material information management system, characterized in that... include: The enumeration value preset module provides an independent operation interface to receive and store standard enumeration value definitions for different SKU attributes; The binding relationship management module is used to establish and maintain the association between the standard enumeration values ​​and the product category information; the product setting module is used to provide a product setting interface, and based on the product category information selected by the user, obtain the corresponding standard enumeration values ​​from the binding relationship management module and generate front-end options. The data storage module is used to store the standard enumeration values, binding relationships, and the product settings data finally submitted by the user.

7. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method as described in any one of claims 1 to 5.

Images