Project-customized adaptive data query and display method, system, equipment and medium

Abstract

The invention provides a project-customized adaptive data query and display method, system, device and medium, and belongs to the technical field of data query, the method comprises the following steps: determining the business meaning of each business entity in a key field in a form scene, and solidifying the business meaning in ERP (Enterprise Resource Planning) system configuration; carrying out association relation configuration on the key fields according to the requirements of the business entities; the association relationship comprises an association table, an association field and an association condition; configuring a target field which needs to be brought out by each service entity in the form scene; and in response to a service demand, determining an association relationship of the key fields according to a service entity type, constructing a dynamic SQL query statement by using the determined association relationship, obtaining target data, and filling the target data into a target field of the form scene. According to the method, the personalized requirements of different projects or departments are met, the data query and display content is flexibly configured, dynamic configuration adjustment is supported, the method adapts to the change of service requirements, and the secondary development workload is reduced.

Description

Technical Field

[0001] This application belongs to the technical field of data query, and relates to a method, system, device and medium for project-customized adaptive data query and display. Background Art

[0002] With the rapid development of enterprise informatization, the ERP system has become an important part of enterprise management and operation. The ERP system covers multiple key links such as procurement, sales, production and finance. By integrating the resources of the enterprise, it has realized the information management of the enterprise and the optimization of business processes to a certain extent. However, with the expansion of enterprise scale and the increase of business complexity, there are problems in data query and display in traditional ERP systems.

[0003] First of all, traditional ERP systems usually adopt fixed data query and display methods, which cannot meet the personalized needs of different projects or departments. For example, a financial reimbursement form may need to display the information of the department head, while a purchase order may need to display the contact information of the supplier. It is difficult for traditional ERP systems to flexibly adapt to these differentiated business needs. Secondly, when business requirements change, traditional ERP systems often require a large amount of secondary development, modifying code or database structures, which is not only time-consuming and laborious, but may also introduce new errors, affecting the stability and reliability of the ERP system. Thirdly, in actual business, the acquisition of data often needs to be achieved through multi-level association relationships. When traditional ERP systems process multi-level association queries, they usually require complex SQL statements and a large amount of code logic, with high development and maintenance costs.

[0004] In summary, the existing ERP systems cannot meet the diverse data query and display requirements. Summary of the Invention

[0005] In a first aspect, an embodiment of this application provides a method for project-customized adaptive data query and display, including the following steps: S1. Determine the business meaning of the key fields of each business entity in the form scenario and solidify it in the ERP system configuration; S2. Configure the association relationships for the key fields according to the requirements of each business entity; the association relationships include association tables, association fields and association conditions; S3. Configure the target fields that need to be brought out by each business entity in the form scenario; S4. Respond to business requirements, determine the association relationships of the key fields according to the business entity types, use the determined association relationships to construct dynamic SQL query statements, obtain the target data, and fill it into the target fields of the form scenario. By meeting the personalized needs of different projects or departments, flexibly configuring the content of data query and display, supporting dynamic adjustment of configurations, adapting to changes in business requirements, and reducing the workload of secondary development.

[0006] Further, the following steps are also included: S5. Respond to the requirement change of the business entity and change the configuration of the association relationship of the key fields; S6. Change the target fields that need to be brought out by the business entity in the form scenario. The response ability to business requirement changes is increased, allowing the association relationship of the key fields and the target fields to be changed, enabling the ERP system to adapt to the dynamic changes of enterprise business.

[0007] Further, the specific steps in step S1 are as follows: S11. Standardize the naming rules and value ranges of the key fields through the data dictionary; S12. Bind the business descriptions of the key fields in the ERP system configuration to ensure the consistency of the meanings of the key fields. By standardizing the naming and value ranges of the key fields through the data dictionary and binding the business descriptions, the consistency of the meanings of the key fields is ensured, reducing data errors caused by differences in understanding. \

[0008] Further, the specific steps of step S2 are as follows: S21. Determine the candidate tables for configuring the association relationship according to the data table structures involved in each business entity; S22. Select the association tables from the candidate tables according to the requirements of each business entity, and configure the association fields and association conditions; S23. Configure the filtering parameters for the association conditions. Through candidate table determination, association table selection, association field and condition configuration, and filtering parameter setting, accurate association relationship configuration is achieved.

[0009] Further, the following steps are also included: S101. Predetermine a field extension rule library in the ERP system to define the field type standard, type association mapping table, and default association condition template. By predetermining the field extension rule library, a basis is provided for the derivation of multi-layer association relationships, improving the ability of the ERP system to process complex association relationships.

[0010] Further, the specific implementation of step S4 is as follows: S41. Respond to the form creation requirement of the business entity, and obtain the association relationship of the key fields according to the business entity type and form ID; S42. Generate the SELECT clause of the specified target fields, generate the FROM clause of the specified association table, and generate the WHERE clause that combines the association conditions and filtering conditions according to the obtained association relationship to complete the construction of the dynamic SQL query statement; S43. After performing character escape processing on the values of the key fields, pass them into the dynamic SQL query statement as variables through the precompiled parameters; S44. Execute the dynamic SQL query statement to obtain the target data and map it to the target fields in the form scenario. By generating the SELECT, FROM, and WHERE clauses, as well as the escape processing and parameter passing of the key field values, the security and accuracy of the query statement are ensured, and the construction of the dynamic SQL query statement is achieved.

[0011] Further, before step S42, the following steps are also included: SS1. Determine whether the association relationship of the key fields is multi-layer; If not, directly enter step S42; If so, enter step SS2; SS2. Deduce the lower-level associations through the field extension rule library, specifically as follows: Match the lower-level associated tables according to the field types, apply the default association condition template, and automatically identify the foreign key association fields; SS3. Recursively construct the dynamic SQL query statements at all levels; SS4. Merge the dynamic SQL query statements at all levels and enter step S42. By processing the multi-layer association relationships, a method for recursive deduction and merging of query statements is provided, enabling the ERP system to automatically process complex association relationships and improving the query efficiency.

[0012] Further, in step S2, if the association relationship of the business entity is multi-layer, mark the extensible fields in the associated table; The specific steps of step SS1 are as follows: SS11. Determine the dynamic SQL query statement at the first level according to the steps of step S42; SS12. Execute the dynamic SQL query statement at the first level to obtain the first-level associated table, associated fields, and association conditions; SS13. Search for the marked extensible fields in the first-level associated table, and determine the next-level association relationship according to the marked extensible fields, specifically as follows: Determine the lower-level associated table from the candidate tables according to the marked extensible fields; Identify the lower-level associated fields according to the database foreign key constraints; Use the default association condition target as the lower-level association condition; SS14. Determine whether the maximum recursion depth is reached; If so, enter step SS2; If not, enter step SS15; SS15. Determine whether there is no matching field type standard; If so, enter step SS2; If not, enter step SS16; SS16. Use the type association mapping table to determine the subordinate association table from the candidate table, identify the subordinate association field according to the database foreign key constraint, use the default association condition target as the subordinate association condition, and return to step SS14.

[0013] In a second aspect, embodiments of the present application further provide a project-customized adaptive data query and display system, comprising: The key field determination and meaning solidification module is used to determine the business meaning of key fields in form scenarios for each business entity and solidify it in the ERP system configuration; An association relationship configuration module is used to configure association relationships for key fields according to the needs of each business entity; the association relationships include association tables, association fields, and association conditions; The export field configuration module is used to configure the target fields that need to be exported in the form scenario for each business entity; The query and display module responds to business needs by determining the relationships between key fields based on business entity types. Using these relationships, it constructs dynamic SQL queries to retrieve target data and populates it into target fields within form scenarios. Through the interaction of the key field determination and meaning solidification module, the relationship configuration module, the pull-out field configuration module, and the query and display module, the personalized needs of different projects or departments can be met, allowing for flexible configuration of data query and display content, effectively addressing the limitations of traditional ERP systems in data query and display.

[0014] Furthermore, the key field determination and meaning solidification module includes: Key field meaning definition unit, used to standardize the naming rules and value ranges of key fields through the data dictionary; The key field business description configuration unit is used to bind the business description of the key field in the ERP system configuration to ensure the consistency of the meaning of the key field.

[0015] Furthermore, the association relationship configuration module includes: A candidate table configuration unit, configured to determine a candidate table for configuring an association relationship based on the data table structure involved in each business entity; The association field and association condition configuration unit is used to select an association table from the candidate table according to the needs of each business entity and configure the association fields and association conditions; The filter parameter configuration unit is used to configure the filter parameters for the association condition.

[0016] Furthermore, the query and display module includes: The form creation demand response unit is used to respond to the form creation demand of the business entity and obtain the association relationship of key fields based on the business entity type and form ID; The construction of SQL query statements is like this, which is used to generate the SELECT clause of the specified target field according to the obtained association relationship, generate the FROM clause of the specified associated table, and generate the WHERE clause that combines the association conditions and filtering conditions to complete the construction of the dynamic SQL query statement; The SQL injection prevention unit is used to perform feature character escape processing on the values of key fields and then pass them into the dynamic SQL query statement as variables through pre-compiled parameters; The form generation unit is used to execute the dynamic SQL query statement to obtain the target data and map it to the target fields in the form scenario.

[0017] In a third aspect, an embodiment of the present application further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, it implements the steps of the project-customized adaptive data query and display method as described in the first aspect.

[0018] In a fourth aspect, an embodiment of the present application further provides a storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the steps of the project-customized adaptive data query and display method as described in the first aspect.

[0019] From the above technical solutions, it can be seen that the present application has the following advantages: In the project-customized adaptive data query and display method, system, device, and medium provided by the present application, by standardizing the naming and meaning of key fields and predefining the field extension rule library, the consistency and maintainability of data are improved; it supports the automatic derivation of multi-layer association relationships and the construction of dynamic SQL query statements, reducing the development and maintenance costs and improving the scalability of the ERP system; it can quickly respond to changes in business requirements, timely adjust the association relationships and target fields of key fields, ensure the synchronization between the ERP system and the business, and achieve project-customized data query and display. It can flexibly configure key fields, association relationships, and target fields according to the needs of different business entities to meet the diverse business needs of enterprises. Description of the Drawings

[0020] In order to more clearly illustrate the technical solutions of the present application, the drawings required to be used in the description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0021] Figure 1 It is a schematic flowchart of the project-customized adaptive data query and display method of the present invention.

[0022] Figure 2 Schematic diagram of the customized adaptive data query and display system for the project of the present invention. Detailed implementation manners

[0023] In the following, the specific steps of the customized adaptive data query and display method for the project will be described in detail, and various embodiments of the present disclosure will be described more comprehensively. The present disclosure may have various embodiments, and adjustments and changes may be made therein. However, it should be understood that there is no intention to limit the various embodiments of the present disclosure to the specific embodiments disclosed herein, but the present disclosure should be understood to cover all adjustments, equivalents, and / or alternative solutions falling within the spirit and scope of the various embodiments of the present disclosure.

[0024] Exemplarily, with the continuous advancement of enterprise informatization construction, the ERP system has become the core tool for enterprise management and operation, and is widely used in key business areas such as procurement, sales, production, and finance. By integrating various resources within the enterprise, the ERP system has optimized information management and business processes to a certain extent and improved the operation efficiency of the enterprise.

[0025] However, with the continuous expansion of the enterprise scale and the significant increase in business complexity, the traditional ERP system has gradually revealed many deficiencies in the data query and display functions.

[0026] On the one hand, the traditional ERP system generally adopts a fixed data query and display mode, which lacks flexibility and is difficult to adapt to the diverse business requirements put forward by different projects or departments. For example, in the financial reimbursement process, it may be necessary to display the relevant information of the department head on the reimbursement form; while in the procurement process, the purchase order needs to show the specific information of the supplier contact person. Facing these differentiated business requirements, the traditional ERP system is often difficult to adjust flexibly and cannot effectively meet the actual requirements of the enterprise.

[0027] On the other hand, when the business requirements of the enterprise change, the traditional ERP system usually requires a large amount of secondary development work. This not only includes modifying the existing code, but may also involve adjusting the database structure. This process is not only time-consuming and laborious, but also prone to introducing new errors, thereby affecting the stability and reliability of the entire ERP system and bringing potential risks to the normal operation of the enterprise.

[0028] In addition, in actual business operations, in order to obtain the required data, it is often necessary to perform queries through multi-level association relationships. When the traditional ERP system processes such multi-level association queries, it usually needs to write complex SQL statements and requires a large amount of code logic to support. This not only increases the development difficulty, but also makes the subsequent maintenance work more cumbersome, significantly increasing the development and maintenance costs.

[0029] In summary, the existing ERP systems have obvious limitations in data query and display, and it is difficult to meet the data query and display requirements of enterprises in diverse business scenarios.

[0030] In view of the above problems, this embodiment provides a project-customized adaptive data query and display method, which can flexibly configure the content of data query and display according to different business requirements to meet diverse needs; supports dynamic configuration and modification, and when the business requirements change, there is no need to modify the code, just adjust the configuration; reduces the workload of secondary development and improves the development and maintenance efficiency of the ERP system; through reasonable query logic and optimization measures, reduces performance problems and improves the user experience.

[0031] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0032] Please refer to Figure 1 The flowchart of the project-customized adaptive data query and display method in a specific embodiment is shown. The method includes the following steps: S1. Determine the business meanings of the key fields of each business entity in the form scenario and solidify them in the ERP system configuration; It should be noted that by solidifying the business meanings of the key fields, a basis is provided for subsequent configuration and query, ensuring the consistency of the business meanings of the key fields in the system and avoiding errors caused by unclear field meanings; S2. Configure the association relationships of the key fields according to the requirements of each business entity; the association relationships include association tables, association fields, and association conditions; It should be noted that the association relationships are flexibly configured according to business requirements to meet the needs of different business scenarios; a basis is provided for subsequent dynamic adjustment of the association relationships to adapt to changes in business requirements; S3. Configure the target fields that need to be brought out by each business entity in the form scenario; It should be noted that the target fields to be displayed are configured according to business requirements to meet personalized needs; a basis is provided for subsequent adding or modifying the target fields at any time to improve the scalability of the ERP system; S4. Respond to the business requirements, determine the association relationships of the key fields according to the business entity types, use the determined association relationships to construct dynamic SQL query statements, obtain the target data, and fill it into the target fields of the form scenario; It should be noted that through feature character escape processing and passing in pre-compiled parameters, the security of the system is improved to prevent SQL injection attacks. Through reasonable query logic and optimization measures, performance issues are reduced and the user experience is enhanced. By automatically constructing dynamic SQL query statements, manual intervention is reduced and query efficiency is improved.

[0033] In this embodiment, by meeting the personalized needs of different projects or departments, the content of data query and display is flexibly configured, supporting dynamic configuration adjustment to adapt to changes in business requirements and reducing the workload of secondary development.

[0034] Furthermore, as a refinement and extension of the specific implementation manner of the above embodiment, in order to fully illustrate the specific implementation process in this embodiment, another method for adaptive data query and display with project customization is provided. This method includes the following steps: S1. Determine the business meaning of the key fields of each business entity in the form scenario and solidify it in the ERP system configuration. The specific steps in step S1 are as follows: S11. Standardize the naming rules and value ranges of the key fields through a data dictionary; Exemplarily, the "supplier_code" field in the procurement module is clearly defined as "unique supplier identifier" in the data dictionary, and the value range is limited to an 8-digit alphanumeric combination starting with "S" (such as "S1001A23"); Specifically, it is implemented through the "field registration center" of the ERP system. The administrator fills in the following information for the field on the interface: business label, such as "department code", data format, such as regular expression constraints, and association description, such as "associated with the department basic information table"; S12. Bind the business descriptions of the key fields in the ERP system configuration to ensure the consistency of the meanings of the key fields; Exemplarily, in the REP system, the field department_id always represents "employee's affiliated department number" in the system. Its value range, associated table, such as department_table, and associated fields, such as manager_id, are predefined through the data dictionary to avoid ambiguity in the meaning of the field due to changes in business requirements; Another example is that when both the finance module and the procurement module use the "project_id" field, the system forcibly requires: sharing the same value range, such as 1000 - 9999, and associating with the same project master table, such as project_master; conflict detection: the ERP system automatically detects different definitions of fields with the same name during configuration, and if detected, triggers an approval process; The consistency of the meanings of the key fields is ensured through the above examples; It should be noted that by standardizing the naming and value range of keyword fields through a data dictionary and binding business descriptions, the consistency of the meanings of keyword fields is ensured, and data errors caused by differences in understanding are reduced; S2. Configure the association relationships for the keyword fields according to the requirements of each business entity; the association relationships include association tables, association fields, and association conditions; the specific steps of step S2 are as follows: S21. Determine the candidate tables for configuring the association relationships based on the data table structures involved in each business entity; S22. Select the association tables from the candidate tables according to the requirements of each business entity, and configure the association fields and association conditions; S23. Configure filtering parameters for the association conditions, and the filtering parameters include fixed-value filtering conditions and dynamic variable filtering conditions, such as form input values, system context values, and environment variables; Exemplarily, when only querying valid departments, the following fixed-value filtering condition "status = 'ACTIVE' AND is_deleted = 0" is used; Form input values, such as the form currently filled in by the user, system context, such as the user logging in to the department, and environment variables, such as the server system time; Specifically, the configuration of the association relationships is carried out through a visual configuration interface, and the configuration interface provides recommendations for the association tables of keyword fields and also provides the selection of logical operators; It should be noted that through candidate table determination, association table selection, association field and condition configuration, and filtering parameter setting, accurate association relationship configuration is achieved; S3. Configure the target fields that need to be brought out in the form scenario for each business entity; S4. According to the business entity type in response to business requirements, determine the association relationships of the keyword fields, use the determined association relationships to construct a dynamic SQL query statement, obtain the target data, and fill it into the target fields in the form scenario; the specific steps of step S4 are as follows: S41. In response to the form creation requirement of the business entity, obtain the association relationships of the keyword fields according to the business entity type and form ID; S42. Generate the SELECT clause for the specified target fields, generate the FROM clause for the specified association tables, and generate the WHERE clause that combines the association conditions and filtering conditions to complete the construction of the dynamic SQL query statement; S43. After performing character escape processing on the values of the keyword fields, pass them into the dynamic SQL query statement as variables through precompiled parameters; Exemplarily, the original input of the keyword field is user_input = "1'; DROP TABLE users--". After escaping special characters, it becomes 1\'\; DROP TABLE users\-\-. Then, parameters are bound to "WHERE id = ?" to implement SQL injection prevention measures; S44. Execute a dynamic SQL query statement to obtain target data and map it to the target fields in the form scenario; It should be noted that through the generation of the SELECT, FROM, and WHERE clauses, as well as the escape processing of keyword field values and parameter passing, the security and accuracy of the query statement are ensured, and the construction of a dynamic SQL query statement is achieved; S5. Respond to the requirement changes of the business entity and change the configuration of the association relationship of the keyword field; S6. Change the target fields that need to be brought out by the business entity in the form scenario; It should be noted that the requirement changes of the business entity include modifying the target fields that need to be brought out by the original keyword fields or adding new target fields that need to be brought out; When modifying the target fields that need to be brought out by the original keyword fields, it is done by modifying the configuration of the original association fields; When adding new target fields that need to be brought out, add a record to the association relationship of the keyword field; It should be noted that the ability to respond to business requirement changes is increased, allowing changes to the association relationship and target fields of the keyword field, enabling the ERP system to adapt to the dynamic changes of enterprise business.

[0035] In an embodiment of the present invention, based on step S42, a possible embodiment will be given below to non-restrictively elaborate on its specific implementation scheme.

[0036] It further includes the following steps: S101. Pre-define a field extension rule library in the ERP system and define field type standards, type association mapping tables, and association condition templates; Exemplarily, the field type standard, for example, "dept_id" is identified as the department type; the type association mapping table, for example, "department type → associated department table"; It should be noted that by pre-defining the field extension rule library, a basis is provided for the derivation of multi-layer association relationships, improving the ability of the ERP system to handle complex association relationships; Before step S42, it further includes the following steps: SS1. Determine whether the association relationship of the keyword field is multi-layer; If not, directly proceed to step S42; If so, proceed to step SS2; SS2. Deduce the subordinate associations through the field extension rule library, specifically as follows: Match the subordinate association table according to the field type, apply the default association condition template, and automatically identify the foreign key association fields; SS3. Recursively construct dynamic SQL query statements at all levels; SS4. Merge the dynamic SQL query statements at all levels and proceed to step S42; It should be noted that when merging the execution results of the dynamic SQL query statements at all levels, the superior query results are retained as the benchmark, the subordinate results are matched through foreign key associations, and the conflicting fields are processed according to the priority. Usually, the priority of the fields in the superior query results is higher than that of the subordinate query results; Specifically, set whether it is a multi-level association by marking the extensible fields in the association table; The association relationships at the first level are configured manually, and the association relationships at the second level and more levels are automatically deduced by the ERP system. For example: According to the manager_id matching rule library, it is found that the employee table is associated; Automatically add the default condition AND employee.status = 'employed' Generate the following dynamic SQL query statement: SELECT employee_name, position FROM employee WHERE emp_id =? For the specific processing of conflicting fields, for example, for fields with the same name, the superior results take precedence, and for foreign key association fields, the association prefix is automatically added; It should be noted that through the processing of multi-level association relationships, a method for recursive deduction and merging of query statements is provided, enabling the ERP system to automatically handle complex association relationships and improving the query efficiency.

[0037] In an embodiment of the present invention, based on step SS1, the following will give a possible embodiment to non-restrictively elaborate on its specific implementation scheme.

[0038] In step S2, if the association relationship of the business entity is multi-level, mark the extensible fields in the association table; The specific steps of step SS1 are as follows: SS11. Determine the dynamic SQL query statement at the first level according to the steps of step S42; SS12. Execute the dynamic SQL query statement at the first level to obtain the first-level association table, association fields, and association conditions; SS13. Search for the marked extensible fields in the first-level association table and determine the next-level association relationship based on the marked extensible fields, as follows: Determine the subordinate association table from the candidate table according to the marked extensible field; Identify subordinate related fields based on database foreign key constraints; Use the default link condition target as the subordinate link condition; SS14. Determine whether the maximum recursion depth has been reached; If yes, go to step SS2; If not, go to step SS15; SS15. Determine if there is no matching field type standard; If yes, go to step SS2; If not, proceed to step SS16; SS16. Use the type association mapping table to determine the subordinate association table from the candidate table, identify the subordinate association field according to the database foreign key constraint, use the default association condition target as the subordinate association condition, and return to step SS14; It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0039] like Figure 2 As shown, the following is an embodiment of the project-customized adaptive data query and display system provided by the embodiment of the present disclosure. This system and the project-customized adaptive data query and display methods of the above-mentioned embodiments belong to the same inventive concept. For details not fully described in the embodiment of the project-customized adaptive data query and display system, please refer to the embodiment of the above-mentioned project-customized adaptive data query and display method.

[0040] The system includes: The key field determination and meaning solidification module is used to determine the business meaning of key fields in form scenarios for each business entity and solidify it in the ERP system configuration; An association relationship configuration module is used to configure association relationships for key fields according to the needs of each business entity; the association relationships include association tables, association fields, and association conditions; The export field configuration module is used to configure the target fields that need to be exported in the form scenario for each business entity; The query and display module is used to respond to business needs, determine the relationship between key fields according to the business entity type, use the determined relationship to build dynamic SQL query statements, obtain target data, and fill it into the target field in the form scenario.

[0041] This embodiment meets the personalized needs of different projects or departments through the interaction of the key field determination and meaning solidification module, the association relationship configuration module, the brought-out field configuration module, and the query and display module, flexibly configures the content of data query and display, and can effectively solve the limitations of traditional ERP systems in data query and display.

[0042] Furthermore, as a refinement and extension of the specific implementation of the above embodiment, in order to fully illustrate the specific implementation process of this embodiment, another project-customized adaptive data query and display system is provided, which includes: The key field determination and meaning solidification module is used to determine the business meaning of key fields in form scenarios for each business entity and solidify it in the ERP system configuration; The key field determination and meaning solidification modules include: Key field meaning definition unit, used to standardize the naming rules and value ranges of key fields through the data dictionary; The key field business description configuration unit is used to bind the business description of key fields in the ERP system configuration to ensure the consistency of the meaning of key fields; It should be noted that by standardizing the naming and value range of key fields through the data dictionary and binding them to business descriptions, the consistency of the meaning of key fields is ensured, reducing data errors caused by differences in understanding; An association relationship configuration module is used to configure association relationships for key fields according to the needs of each business entity; the association relationships include association tables, association fields, and association conditions; The association configuration module includes: A candidate table configuration unit, configured to determine a candidate table for configuring an association relationship based on the data table structure involved in each business entity; The association field and association condition configuration unit is used to select an association table from the candidate table according to the needs of each business entity and configure the association fields and association conditions; A filter parameter configuration unit, used to configure filter parameters for associated conditions; It should be noted that accurate association relationship configuration is achieved through candidate table determination, association table selection, association field and condition configuration, and filter parameter setting; The export field configuration module is used to configure the target fields that need to be exported in the form scenario for each business entity; The query and display module is used to determine the relationship between key fields according to business entity types in response to business needs, use the determined relationship to build dynamic SQL query statements, obtain target data, and fill it into the target fields in the form scenario; The query and display modules include: A form creation requirements response unit is used to respond to the form creation requirements of a business entity and obtain the association relationship of key fields according to the business entity type and form ID. The SQL query statement construction unit is used to generate the SELECT clause of the specified target field, generate the FROM clause of the specified associated table, and generate the WHERE clause that combines the association condition and the filtering condition according to the obtained association relationship, and complete the construction of the dynamic SQL query statement. The SQL injection prevention unit is used to perform feature character escape processing on the values of the key fields and then pass them into the dynamic SQL query statement as variables through pre-compiled parameters. The form generation unit is used to execute the dynamic SQL query statement to obtain the target data and map it to the target fields in the form scenario. It should be noted that through the generation of the SELECT, FROM, and WHERE clauses, as well as the escape processing and parameter passing of the key field values, the security and accuracy of the query statement are ensured, and the construction of the dynamic SQL query statement is realized.

[0043] The project customization adaptive data query and display method provided by the embodiments of the present application can be applied to an electronic device. Those skilled in the art can understand that the structure of the electronic device involved in the embodiments of the present invention does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine some components, or have different component arrangements. In the embodiments of the present invention, the electronic device includes, but is not limited to, a laptop computer, a desktop computer, a workbench, a personal digital assistant, a server, a blade server, a mainframe computer, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown in the figure, their connections and relationships, and their functions are only examples and are not intended to limit the implementation of the embodiments of the present application described and / or claimed herein.

[0044] The electronic device may include a processor, an external memory interface, an internal memory, a universal serial bus (USB) interface, a charging management module, a power management module, a battery, a wireless communication module, an audio module, a speaker, a microphone, a sensor module, a key, a camera, a display screen, and a SIM card interface, etc.

[0045] It can be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the electronic device. In other embodiments of the present application, the electronic device may include more or fewer components than those illustrated, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0046] The processor may include one or more processing units. For example, the processor may include a central processing unit (CPU), an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0047] Among them, the processor may be the nerve center and command center of the electronic device. The controller may generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.

[0048] A memory may also be provided in the processor for storing instructions and data. In some embodiments, the memory in the processor is a cache memory. This memory can store the instructions or data that the processor has just used or recycled. If the processor needs to use the instruction or data again, it can be directly called from this memory. This avoids repeated accesses, reduces the waiting time of the processor, and thus improves the system efficiency.

[0049] The above-mentioned electronic device implements the technical solution of the customized adaptive data query and display method of the present application project, which determines the business meaning of the key fields of each business entity in the form scenario and solidifies it in the ERP system configuration; configures the association relationship of the key fields according to the requirements of each business entity; the association relationship includes an association table, association fields, and association conditions; configures the target fields that need to be brought out by each business entity in the form scenario; responds to the business requirements to determine the association relationship of the key fields according to the business entity type, constructs a dynamic SQL query statement using the determined association relationship, obtains the target data, and fills it into the target fields of the form scenario, achieving the beneficial effect of flexibly configuring the content of data query and display by meeting the personalized needs of different projects or departments, supporting dynamic configuration adjustment, adapting to the changes in business requirements, and reducing the workload of secondary development.

[0050] In the storage medium provided by the present application, there is a program product that can implement the customized adaptive data query and display method of the project.

[0051] The customized adaptive data query and display method of the project includes: determining the business meaning of the key fields of each business entity in the form scenario and solidifying it in the ERP system configuration; configuring the association relationship of the key fields according to the requirements of each business entity; the association relationship includes an association table, association fields, and association conditions; configuring the target fields that need to be brought out by each business entity in the form scenario; responding to the business requirements to determine the association relationship of the key fields according to the business entity type, constructing a dynamic SQL query statement using the determined association relationship, obtaining the target data, and filling it into the target fields of the form scenario.

[0052] In some possible implementation manners, the customized adaptive data query and display method of the present disclosure may be implemented in the form of a program product, which includes program code. When the program product runs on a terminal device, the program code is used to cause the terminal device to execute the steps according to various exemplary embodiments of the present disclosure described in the "Exemplary Method" section above of this specification.

[0053] The storage medium of the present disclosure may adopt any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0054] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An adaptive data query and display method for project customization, characterized in that It includes the following steps: S1. Determine the business meanings of the key fields of each business entity in the form scenario and solidify them in the ERP system configuration; S2. Configure the association relationships for the key fields according to the requirements of each business entity; the association relationships include association tables, association fields, and association conditions; S3. Configure the target fields that need to be brought out by each business entity in the form scenario; S4. Respond to the business requirements, determine the association relationships of the key fields according to the business entity types, use the determined association relationships to construct a dynamic SQL query statement, obtain the target data, and fill it into the target fields of the form scenario.

2. The customized adaptive data query and display method according to claim 1, characterized in that, It also includes the following steps: S5. Respond to the requirement changes of the business entity and change the configuration of the association relationships of the key fields; S6. Change the target fields that need to be brought out by the business entity in the form scenario.

3. The adaptive data query and display method customized for the project according to claim 1, characterized in that The specific steps in step S1 are as follows: S11. Standardize the naming rules and value ranges of the key fields through the data dictionary; S12. Bind the business descriptions of the key fields in the ERP system configuration to ensure the consistency of the meanings of the key fields.

4. The adaptive data query and display method customized for the project according to claim 1, characterized in that, The specific steps of step S2 are as follows: S21. Determine the candidate tables for configuring the association relationships according to the data table structures involved in each business entity; S22. Select the association tables from the candidate tables according to the requirements of each business entity, and configure the association fields and association conditions; S23. Configure the filtering parameters for the association conditions.

5. The customized adaptive data query and display method according to claim 4, characterized in that , It also includes the following steps: S101. Pre-define a field extension rule library in the ERP system and define the field type standards, type association mapping tables, and default association condition templates.

6. The project-customized adaptive data query and display method according to claim 5, characterized in that The specific steps of step S4 are as follows: S41. Respond to the form creation requirements of the business entity, and obtain the association relationships of the key fields according to the business entity type and form ID; S42. Generate the SELECT clause for the specified target fields, generate the FROM clause for the specified association tables, and generate the WHERE clause that combines the association conditions and filtering conditions to complete the construction of the dynamic SQL query statement; S43. After performing character escaping processing on the values of the key fields, pass them into the dynamic SQL query statement as variables through pre-compiled parameters; S44. Execute the dynamic SQL query statement to obtain the target data and map it to the target fields of the form scenario.

7. The customized adaptive data query and display method according to claim 6, characterized in that, Before step S42, it also includes the following steps: SS1. Determine whether the association relationships of the key fields are multi-level; If not, directly enter step S42; If so, enter step SS2; SS2. Deduce the subordinate associations through the field extension rule library, specifically as follows: Match the subordinate association tables according to the field types, apply the default association condition templates, and automatically identify the foreign key association fields; SS3. Recursively construct the dynamic SQL query statements at all levels; SS4. Merge the dynamic SQL query statements at all levels and enter step S42.

8. An adaptive data query and display system for project customization, characterized in that, It includes: A key field determination and meaning solidification module, which is used to determine the business meanings of the key fields of each business entity in the form scenario and solidify them in the ERP system configuration; An association relationship configuration module is used to configure association relationships for key fields according to the needs of each business entity; the association relationships include association tables, association fields, and association conditions; The export field configuration module is used to configure the target fields that need to be exported in the form scenario for each business entity; The query and display module is used to respond to business needs, determine the relationship between key fields according to the business entity type, use the determined relationship to build dynamic SQL query statements, obtain target data, and fill it into the target field in the form scenario.

9. An electronic device, characterized in that, The method comprises 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 method implements the steps of the project-customized adaptive data query and display method as claimed in any one of claims 1 to 7.

10. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, the steps of the project-customized adaptive data query and display method according to any one of claims 1 to 7 are implemented.

Images