A method, device, storage medium and electronic device for processing custom reports

Abstract

The present application discloses a method, device, storage medium and electronic device for processing custom reports. When a business query request is received, the preset dimension indicator data pre-configured in the database is queried to obtain the business dimension indicator data corresponding to the business query request in the database, the business dimension indicator data is spliced ​​by the preset splicing logic to obtain the custom report corresponding to the business query request, and the custom report is displayed by the preset display method. Based on the above, by pre-configuring the dimension indicator data related to the personalized report in the database, the dimension indicator data in the database is queried by the business query request, and the custom report corresponding to the business query request, that is, the personalized report, is obtained, and there is no need to re-develop the logic code of the personalized report, thereby improving the efficiency of obtaining personalized reports.

Description

Technical Field

[0001] The present application relates to the technical field of report processing, and more specifically, to a method, device, storage medium and electronic device for processing a custom report. Background Art

[0002] With the application of World Wide Web (web) management applications in the financial industry, especially in the Customer Relationship Management (CRM) system, futures companies need some customized reports to count the corresponding data of their businesses because of their different businesses.

[0003] At present, when developing these personalized reports, each time a personalized report is developed separately, the development work needs to be repeated. For some personalized reports with fixed logic, since each futures company uses a different number of report fields or a different field order, when developing personalized reports, the logical code of the personalized report needs to be redeveloped, which reduces the efficiency of obtaining personalized reports. Summary of the invention

[0004] In view of this, the present application discloses a method, device, storage medium and electronic device for processing a custom report, aiming to improve the efficiency of obtaining personalized reports.

[0005] In order to achieve the above purpose, the disclosed technical solution is as follows:

[0006] The first aspect of the present application discloses a method for processing a custom report, the method comprising:

[0007] When a business query request is received, the preset dimension indicator data pre-configured in the database is queried to obtain the business dimension indicator data corresponding to the business query request; the business dimension indicator data is used to represent the preset dimension indicator data corresponding to the dimension indicator query data in the business query request;

[0008] The business dimension indicator data is spliced ​​through preset splicing logic to obtain and display a custom report corresponding to the business query request.

[0009] Preferably, when a business query request is received, the preset dimension indicator data pre-configured in the database is queried to obtain the business dimension indicator data corresponding to the business query request, including:

[0010] When a business query request is received, obtaining dimension indicator query data in the business query request;

[0011] Matching the dimension indicator query data with the preset dimension indicator data pre-configured in the database;

[0012] When the dimension indicator query data is consistent with the preset dimension indicator data, the business dimension indicator data corresponding to the business query request is obtained.

[0013] Preferably, the splicing of the business dimension indicator data by a preset splicing logic to obtain and display a custom report corresponding to the business query request includes:

[0014] Determine input parameters corresponding to the business dimension indicator data and output parameters corresponding to the business dimension indicator data;

[0015] The input parameters and the output parameters are concatenated by using a dynamic structured query language SQL to obtain a concatenation result; the concatenation result is used to characterize the corresponding relationship between the input parameters and the output parameters;

[0016] Storing the splicing results in a database;

[0017] Based on the splicing results in the database, a custom report corresponding to the business query request is determined and displayed.

[0018] Preferably, the process of configuring preset dimension indicator data includes:

[0019] Obtain the business needs of various futures companies;

[0020] Extracting preset business indicators from the business requirements of each futures company; the preset business indicators are business indicators of the same business type in different dimensions;

[0021] The preset business indicators are configured in a database to obtain preset dimension indicator data.

[0022] Preferably, it also includes:

[0023] Perform custom modification operations on the preset dimension indicator data.

[0024] Preferably, it also includes:

[0025] Generate the front-end function corresponding to the custom report.

[0026] The second aspect of the present application discloses a device for processing a custom report, the device comprising:

[0027] A determination unit, configured to query preset dimension indicator data pre-configured in a database when a business query request is received, to obtain business dimension indicator data corresponding to the business query request; the business dimension indicator data is used to represent preset dimension indicator data corresponding to the dimension indicator query data in the business query request;

[0028] The splicing unit is used to splice the business dimension indicator data through a preset splicing logic to obtain and display a custom report corresponding to the business query request.

[0029] Preferably, the determining unit includes:

[0030] A first acquisition module is used to acquire dimension indicator query data in the business query request when receiving the business query request;

[0031] A matching module, used to match the dimension indicator query data with the preset dimension indicator data pre-configured in the database;

[0032] The second acquisition module is used to obtain the business dimension indicator data corresponding to the business query request when the dimension indicator query data is consistent with the preset dimension indicator data.

[0033] A third aspect of the present application discloses a storage medium, which includes stored instructions, wherein when the instructions are executed, a device where the storage medium is located is controlled to execute the method for processing a custom report as described in any one of the first aspects.

[0034] The fourth aspect of the present application discloses an electronic device, comprising a memory and one or more instructions, wherein the one or more instructions are stored in the memory and are configured to be executed by one or more processors to perform a method for processing a custom report as described in any one of the first aspects.

[0035] Through the above technical scheme, it can be known that the present application discloses a method, device, storage medium and electronic device for processing customized reports. When a business query request is received, the preset dimension indicator data pre-configured in the database is queried to obtain the business dimension indicator data corresponding to the business query request. The business dimension indicator data is used to characterize the preset dimension indicator data corresponding to the dimension indicator query data in the business query request. The business dimension indicator data is spliced ​​through the preset splicing logic to obtain and display the customized report corresponding to the business query request. Through the above scheme, the dimension indicator data related to the personalized report is configured in the database in advance, and the dimension indicator data in the database is queried through the business query request to obtain the customized report corresponding to the business query request, that is, the personalized report, and there is no need to re-develop the logic code of the personalized report, thereby improving the efficiency of obtaining personalized reports. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0037] Figure 1 A schematic diagram of the structure of a custom report processing system disclosed in an embodiment of the present application;

[0038] Figure 2 A flowchart of a method for processing a custom report disclosed in an embodiment of the present application;

[0039] Figure 3 A schematic diagram of a display interface of a custom report disclosed in an embodiment of the present application;

[0040] Figure 4 A schematic diagram of another display interface of a custom report disclosed in an embodiment of the present application;

[0041] Figure 5 This is an example diagram of the initially newly added modules disclosed in the embodiments of the present application;

[0042] Figure 6 A schematic diagram of the structure of a device for processing a custom report disclosed in an embodiment of the present application;

[0043] Figure 7 A schematic diagram of the structure of an electronic device disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0044] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0045] In this application, the terms "comprises", "comprising" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element.

[0046] From the background technology, it can be seen that when developing these personalized reports, each time a personalized report is developed separately, the development work needs to be repeated. For some personalized reports with fixed logic, since each futures company uses a different number of report fields or a different field order, when developing personalized reports, the logical code of the personalized report needs to be redeveloped, which reduces the efficiency of obtaining personalized reports.

[0047] In order to solve the above problems, the present application discloses a method, device, storage medium and electronic device for processing customized reports, which configures dimension indicator data related to personalized reports in a database in advance, queries the dimension indicator data in the database through a business query request, and obtains a customized report corresponding to the business query request, that is, a personalized report, without the need to redevelop the logic code of the personalized report, thereby improving the efficiency of obtaining personalized reports. The specific implementation method is described by the following embodiments.

[0048] The following first introduces the architecture diagram of a custom report processing system applicable to a custom report processing method and device of the present application, and specifically refers to Figure 1 As shown, the processing system of the custom report includes a client 11, a server 12 and a database 13. The client 11 includes a custom report module function, and the server 12 includes a dimension indicator maintenance and logic development function and a report front-end function.

[0049] The dimensional indicator maintenance and logic development functions are the core of the front-end function of automatically generating custom reports, because all fields and indicators of the automatically generated reports are pre-abstracted business data of various futures companies.

[0050] According to the indicator logic of each dimension indicator, the logic development and data landing are carried out. For example, the indicator of the customer day dimension generally includes the transaction data of the customer dimension, such as the end-of-period equity, the profit and loss of the day, the withdrawal amount, the deposit amount and other indicators. The corresponding indicator data generation logic is written in advance, and then the corresponding logic is executed through the daily task to generate the landing data of the dimension indicator. In addition, the dimension indicator supports expansion and modification. This part of the logic is executed on the server.

[0051] The custom report module function is to display and customize the selection and modification of the front-end based on the dimension indicators generated in the background. The report display is divided into search conditions and display fields, so condition indicators and display indicators can be added in the custom module. This part of the implementation is executed on the client 11.

[0052] The report front-end function is a module generated according to the custom report module function, and then the report front-end function is generated using the module generation function provided by the framework. This part of the front-end report generation function is executed on the client, and the part of the custom report back-end logic generation is executed on the server 12.

[0053] The specific data interaction process between the client 11, the server 12 and the database 13 is as follows:

[0054] When the server 12 receives the business query request sent by the client 11, the server 12 queries the preset dimension indicator data pre-configured in the database to obtain the business dimension indicator data corresponding to the business query request in the database 13; the business dimension indicator data is used to represent the preset dimension indicator data corresponding to the dimension indicator query data in the business query request.

[0055] The process of configuring the preset dimension indicator data in the database of the server 12 is as follows:

[0056] The server 12 obtains various business requirements; the business requirements are requirements corresponding to the business types of each company.

[0057] The server 12 extracts preset business indicators from the business requirements; the preset business indicators are business indicators with the same business type in different dimensions.

[0058] The server 12 configures the preset business indicators in the database to obtain preset dimension indicator data.

[0059] Among them, the server 12 performs customized modification operations on the preset dimension indicator data.

[0060] The specific process of obtaining the business dimension indicator data corresponding to the business query request in the database 13 is as follows:

[0061] When the server 12 receives the business query request sent by the client 11, the server 12 obtains the dimension indicator query data in the business query request.

[0062] The server 12 matches the dimension indicator query data with the preset dimension indicator data pre-configured in the database.

[0063] When the dimension indicator query data is consistent with the preset dimension indicator data, the server 12 obtains the business dimension indicator data corresponding to the business query request.

[0064] The server 12 splices the business dimension indicator data through the preset splicing logic to obtain a custom report corresponding to the business query request.

[0065] The specific process of the server 12 splicing the business dimension indicator data through the preset splicing logic to obtain the custom report corresponding to the business query request is as follows:

[0066] The server 12 determines the input parameters corresponding to the business dimension indicator data and the output parameters corresponding to the business dimension indicator data.

[0067] The server 12 concatenates the input parameters and the output parameters through the dynamic structured query language SQL to obtain the concatenation result, and stores the concatenation result in the database.

[0068] The server 12 determines the custom report corresponding to the business query request based on the splicing result in the database.

[0069] The client 11 displays the custom report in a preset display mode.

[0070] In an embodiment of the present application, by pre-configuring dimensional indicator data related to personalized reports in a database, and querying the dimensional indicator data in the database through a business query request, a custom report corresponding to the business query request, that is, a personalized report, is obtained, and there is no need to re-develop the logic code of the personalized report, thereby improving the efficiency of obtaining personalized reports.

[0071] refer to Figure 2 FIG. 1 is a flow chart of a method for processing a custom report disclosed in an embodiment of the present application. The method for processing a custom report mainly includes the following steps:

[0072] S201: When a business query request is received, the preset dimension indicator data pre-configured in the database is queried to obtain the business dimension indicator data corresponding to the business query request; the business dimension indicator data is used to represent the preset dimension indicator data corresponding to the dimension indicator query data in the business query request.

[0073] In S201, the service query request may be obtained through the client or other data information sources. The method of obtaining the service query request is not specifically limited in this application.

[0074] The process of configuring preset dimension indicator data is shown in A1-A3.

[0075] A1: Obtain various business requirements; business requirements refer to the requirements corresponding to the business types of each company.

[0076] First, it is necessary to collect the business needs of various futures companies, extract the common business fields, and maintain the indicators and indicator logic required for each dimension in the Oracle database. If the specific business needs are distinguished according to different statistical dimensions, they include customer dimension, business department dimension, product exchange dimension, customer product dimension, capital account dimension, etc.

[0077] A2: Preset business indicators are extracted from business requirements; preset business indicators are business indicators of the same business type in different dimensions.

[0078] Preset business indicators, namely shared business fields, refer to the same business logic of different futures companies, such as customer end-of-period equity, transaction amount, transaction quantity, number of positions, and other same business fields. These with the same business logic can be abstracted as shared business fields.

[0079] For example, among the business demands of futures company A, futures company B and futures company C, the transaction amount demands of futures company A, futures company B and futures company C are extracted, and the transaction amount demands are the preset business indicators (common business fields).

[0080] A3: Configure the preset business indicators in the database to obtain the preset dimension indicator data.

[0081] Among them, custom modification operations are performed on the preset dimension indicator data.

[0082] Specifically, when a business query request is received, the process of determining the business dimension indicator data corresponding to the business query request based on the preset dimension indicator data pre-configured in the database is as follows:

[0083] First, when a business query request is received, the dimension indicator query data in the business query request is obtained.

[0084] The business query request is parsed to obtain dimension indicator query data in the business query request.

[0085] Dimension indicator query data is used to query the corresponding preset dimension indicator data in the database.

[0086] Then, the dimension indicator query data is matched with the preset dimension indicator data pre-configured in the database. When the dimension indicator query data is consistent with the preset dimension indicator data, the business dimension indicator data corresponding to the business query request is obtained.

[0087] S202: splicing the business dimension indicator data through a preset splicing logic to obtain a custom report corresponding to the business query request.

[0088] In S202, the generated custom report consists of three parts: input parameters (input parameters), output parameters (output parameters) and data sources.

[0089] Among them, the output parameter is the report display field.

[0090] The specific input parameter, output parameter and data source codes are as follows:

[0091] (1) Input parameters:

[0092]

[0093] (2) Output:

[0094]

[0095]

[0096] (3) Data source:

[0097] bindModule:

[0098] "m?xwl=Index_management / index_report / D_IDX_admin14990 / select",

[0099] iconCls:"seek_icon",

[0100] itemId:"seekBtn",

[0101] text:"query".

[0102] Generating a custom report under this path requires calling database logic to implement the call of the data source.

[0103] The specific database logic is as follows:

[0104] First, determine the input parameters corresponding to the business dimension indicator data and the output parameters corresponding to the business dimension indicator data.

[0105] Then, the input parameters and the output parameters are spliced ​​by using the dynamic structured query language SQL to obtain the splicing result, and the splicing result is stored in the database.

[0106] Among them, the business logic is spliced ​​through the pre-set dimension business indicator logic, and the output parameters are spliced ​​through dynamic SQL.

[0107] The logic is as follows: through the dimension indicators maintained in advance in the background, the business logic is spliced ​​by converting rows to columns. The source code is as follows:

[0108] selectrtrim(xmlagg(xmlparse(contentt1.bm_name||'.'||t.field_name||','wellformed)orderbyt.field_name).getclobval(),',')attributes

[0109] into v_sql_select

[0110] from cf_index.t_index_attrt

[0111] innerjoin cf_index.t_sql t1

[0112] ont.index_source=t1.table_name

[0113] andt.table_name=i_index_object

[0114] where t.index_attr_type = '0'

[0115] andt.index_source<>i_index_object.

[0116] The abstracted dimension business logic can be reused to improve report development efficiency and data utilization. The specific data of the dimension business logic is maintained in the indicator table, which stores the indicator name, indicator field name, indicator calculation process, indicator status, calculation formula, etc. of the dimension business logic.

[0117] The entire dynamic SQL serves as the database stored procedure of the custom report, that is, it generates the background database stored procedure.

[0118] The logic of the specific stored procedure is as follows:

[0119] 1) Splice the background SQL and use loop operations to logically splice the selected input parameter fields.

[0120] 2) Logically concatenate the selected output parameter fields.

[0121] 3) Splice the stored procedure query logic.

[0122] 4) Generate stored procedures for custom reports.

[0123] The specific logic is as follows, which is simplified according to the logic in the background:

[0124]

[0125]

[0126]

[0127] Finally, based on the splicing results in the database, the custom report corresponding to the business query request is determined and displayed.

[0128] Generate the front-end function corresponding to the custom report. The generated front-end function is the custom report, which can be used by business personnel for query.

[0129] S203: Display the custom report in a preset display mode.

[0130] The preset display methods are divided into search conditions and display fields, so you can customize the module to add condition indicators and display indicators.

[0131] What are the different fields required in business needs? Configure and maintain these different fields in the database. Different dimensional indicators are scattered under different statistical dimensions. Select the display fields for generating reports under different dimensions (such as the amount of positions sold).

[0132] In order to facilitate the understanding of displaying custom reports through preset display methods, Figure 3 and Figure 4 , give examples to illustrate.

[0133] Figure 3 In the , the preset dimension indicator data include daily dimension exchange table, product, underlying contract, monthly dimension customer table, monthly dimension sales department table, monthly dimension customer category table, monthly dimension exchange table, monthly dimension product table, daily dimension customer table, customer information table, branch, daily dimension sales department table, daily dimension product table, daily dimension customer product table and low-dimensional customer category table, etc. The preset dimension indicator data can be customized.

[0134] For example, in Figure 3 In the search results, select a pre-set dimension, such as the daily dimension customer table, and select business date, business department, customer number, and currency as search conditions (dimensional indicator query data).

[0135] exist Figure 4 , select Business Date, Sales Department, Customer Number, Currency, Premium Income, and Premium Expenditure as the report display fields (output parameters).

[0136] The default state of the newly added module is the initial state, refer to Figure 5 As shown, Figure 5 An example diagram showing the initial addition of modules.

[0137] Figure 5It includes functions such as adding, generating function points, modifying display and conditional pathogens, modifying function records, deleting, function number, function name, data source script, status, update date, updater and function path.

[0138] exist Figure 5 In the generated module, there are two states, the initial state and the generated function point. Only the initial state can generate a report. The "Generated Function Point" means that the report has been generated and cannot be generated again. Select the newly added custom module, call the module of the framework's automatic generation function to generate the front-end report function point, and place the generated report function in the specified directory.

[0139] According to the account permissions of the logged-in user, the generated functions can only be queried and used by the current account.

[0140] In an embodiment of the present application, by pre-configuring dimensional indicator data related to personalized reports in a database, and querying the dimensional indicator data in the database through a business query request, a custom report corresponding to the business query request, that is, a personalized report, is obtained, and there is no need to re-develop the logic code of the personalized report, thereby improving the efficiency of obtaining personalized reports.

[0141] Based on the above embodiments Figure 2 A method for processing a custom report is disclosed, and an embodiment of the present application also discloses a device for processing a custom report, such as Figure 6 As shown, the processing device for the custom report includes a determining unit 601 , a splicing unit 602 and a display unit 603 .

[0142] Determination unit 601 is used to query the preset dimension indicator data pre-configured in the database when receiving a business query request, and obtain the business dimension indicator data corresponding to the business query request; the business dimension indicator data is used to represent the preset dimension indicator data corresponding to the dimension indicator query data in the business query request.

[0143] The splicing unit 602 is used to splice the business dimension indicator data through a preset splicing logic to obtain a custom report corresponding to the business query request.

[0144] The display unit 603 is used to display the custom report in a preset display mode.

[0145] Furthermore, the determination unit 601 includes a first acquisition module, a matching module and a second acquisition module.

[0146] The first acquisition module is used to acquire dimension indicator query data in the business query request when a business query request is received.

[0147] The matching module is used to match the dimension indicator query data with the preset dimension indicator data pre-configured in the database.

[0148] The second acquisition module is used to obtain the business dimension indicator data corresponding to the business query request when the dimension indicator query data is consistent with the preset dimension indicator data.

[0149] Furthermore, the splicing unit 602 includes a first determining module, a storage module and a second determining module.

[0150] The first determination module is used to determine the input parameters corresponding to the business dimension indicator data and the output parameters corresponding to the business dimension indicator data.

[0151] The splicing module is used to splice input parameters and output parameters through dynamic structured query language SQL to obtain splicing results, and store the splicing results in a database.

[0152] The second determination module is used to determine and display the custom report corresponding to the business query request based on the splicing results in the database.

[0153] Furthermore, the determination unit 601 of the process of configuring preset dimension indicator data includes an acquisition module, an extraction module and a configuration module.

[0154] The acquisition module is used to obtain the business needs of various futures companies.

[0155] The extraction module is used to extract preset business indicators from the business needs of various futures companies; the preset business indicators are business indicators with the same business type in different dimensions.

[0156] The configuration module is used to configure the preset business indicators in the database to obtain the preset dimension indicator data.

[0157] Furthermore, the processing device for custom reports also includes an operating unit.

[0158] Operation unit, used to perform custom modification operations on preset dimension indicator data.

[0159] Furthermore, the processing device for custom reports also includes a generating unit.

[0160] Generates front-end functions corresponding to custom reports.

[0161] In an embodiment of the present application, by pre-configuring dimensional indicator data related to personalized reports in a database, and querying the dimensional indicator data in the database through a business query request, a custom report corresponding to the business query request, that is, a personalized report, is obtained, and there is no need to re-develop the logic code of the personalized report, thereby improving the efficiency of obtaining personalized reports.

[0162] An embodiment of the present application further provides a storage medium, which includes stored instructions, wherein when the instructions are executed, a device where the storage medium is located is controlled to execute the above-mentioned custom report processing method.

[0163] The present application also provides an electronic device, whose structural diagram is as follows: Figure 7 As shown, it specifically includes a memory 701 and one or more instructions 702, wherein the one or more instructions 702 are stored in the memory 701 and are configured to be executed by one or more processors 703 to execute the one or more instructions 702 to execute the above-mentioned custom report processing method.

[0164] For the aforementioned method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the order of the actions described, because according to the present application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0165] It should be noted that each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the embodiments can be referred to each other. For system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0166] The steps in the methods of the embodiments of the present application can be adjusted in order, combined, and deleted according to actual needs.

[0167] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations.

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

[0169] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for processing a custom report, characterized in that: The method comprises: When a business query request is received, the preset dimension indicator data pre-configured in the database is queried to obtain the business dimension indicator data corresponding to the business query request; the business dimension indicator data is used to represent the preset dimension indicator data corresponding to the dimension indicator query data in the business query request; The business dimension indicator data is spliced ​​by a preset splicing logic to obtain a custom report corresponding to the business query request; Display the custom report in a preset display mode; The step of splicing the business dimension indicator data by a preset splicing logic to obtain a custom report corresponding to the business query request includes: Determine the input parameters corresponding to the business dimension indicator data and the output parameters corresponding to the business dimension indicator data, wherein the output parameters are report display fields; concatenate the input parameters and the output parameters through the dynamic structured query language SQL to obtain a concatenation result, and store the concatenation result in a database; determine the custom report corresponding to the business query request based on the concatenation result in the database; The process of configuring the preset dimension indicator data in the database includes: Obtain various business requirements; the business requirements are requirements corresponding to the business types of various companies; extract preset business indicators from the business requirements; the preset business indicators are business indicators with the same business type under different dimensions; configure the preset business indicators in a database to obtain preset dimension indicator data.

2. The method according to claim 1, characterized in that When a business query request is received, the preset dimension indicator data pre-configured in the database is queried to obtain the business dimension indicator data corresponding to the business query request, including: When a business query request is received, obtaining dimension indicator query data in the business query request; Matching the dimension indicator query data with the preset dimension indicator data pre-configured in the database; When the dimension indicator query data is consistent with the preset dimension indicator data, the business dimension indicator data corresponding to the business query request is obtained.

3. The method according to claim 1, characterized in that Also includes: Perform custom modification operations on the preset dimension indicator data.

4. The method according to claim 1, characterized in that: Also includes: Generate the front-end function corresponding to the custom report.

5. A processing device for a custom report, characterized in that: The device comprises: A determination unit, configured to query preset dimension indicator data pre-configured in a database when a business query request is received, to obtain business dimension indicator data corresponding to the business query request; the business dimension indicator data is used to represent preset dimension indicator data corresponding to the dimension indicator query data in the business query request; A splicing unit, used to splice the business dimension indicator data through a preset splicing logic to obtain a custom report corresponding to the business query request; A display unit, used to display the custom report in a preset display mode; The splicing unit includes a first determination module, a storage module, and a second determination module; The first determination module is used to determine the input parameters corresponding to the business dimension indicator data and the output parameters corresponding to the business dimension indicator data, wherein the output parameters are report display fields; The storage module is used to splice the input parameters and the output parameters through the dynamic structured query language SQL to obtain the splicing result, and store the splicing result in the database; The second determination module is used to determine and display the custom report corresponding to the business query request based on the splicing result in the database; The process of configuring the preset dimension indicator data in the database includes: Obtain various business requirements; the business requirements are requirements corresponding to the business types of various companies; extract preset business indicators from the business requirements; the preset business indicators are business indicators with the same business type under different dimensions; configure the preset business indicators in a database to obtain preset dimension indicator data.

6. The device according to claim 5, characterized in that The determining unit comprises: A first acquisition module is used to acquire dimension indicator query data in the business query request when receiving the business query request; A matching module, used to match the dimension indicator query data with the preset dimension indicator data pre-configured in the database; The second acquisition module is used to obtain the business dimension indicator data corresponding to the business query request when the dimension indicator query data is consistent with the preset dimension indicator data.

7. A storage medium, characterized in that: The storage medium includes stored instructions, wherein when the instructions are executed, the device where the storage medium is located is controlled to execute the method for processing a custom report according to any one of claims 1 to 4.

8. An electronic device, characterized in that: The system comprises a memory and one or more instructions, wherein the one or more instructions are stored in the memory and configured to be executed by one or more processors to execute the method for processing a custom report as claimed in any one of claims 1 to 4.

Images