CN110298023B - Report splicing method and system - Google Patents
Report splicing method and system Download PDFInfo
- Publication number
- CN110298023B CN110298023B CN201910599892.4A CN201910599892A CN110298023B CN 110298023 B CN110298023 B CN 110298023B CN 201910599892 A CN201910599892 A CN 201910599892A CN 110298023 B CN110298023 B CN 110298023B
- Authority
- CN
- China
- Prior art keywords
- report
- spliced
- line
- row
- item
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/174—Form filling; Merging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/177—Editing, e.g. inserting or deleting of tables; using ruled lines
- G06F40/18—Editing, e.g. inserting or deleting of tables; using ruled lines of spreadsheets
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a report splicing method and a report splicing system, wherein the method comprises the following steps: determining a row key of a row item to be spliced in the target report according to a query condition input by a user, wherein the row key is used for representing the data attribute of the row item to be spliced; acquiring the data content of the line items to be spliced according to the line keys; and generating a spliced report according to the data content of the line items to be spliced. According to the application, the user can automatically acquire the data content corresponding to the row item to be spliced according to the row key determined by the query condition by directly inputting the query condition, so that a spliced report is generated, the process of manually selecting the fields by the user is omitted, the operation flow of the user is simplified, the time cost and the labor cost are greatly saved, the working efficiency is further improved, and the accuracy is improved compared with that of the manual operation mode by automatically acquiring the data content corresponding to the row item.
Description
Technical Field
The application relates to the technical field of data analysis, in particular to a report splicing method and system.
Background
In actual work, banking staff often needs to select required fields from different reports to form a new report for subsequent data comparison or analysis and other works, so that how to quickly and accurately acquire required fields and corresponding contents from different reports is the basis for performing data comparison or analysis operation.
Because the existing report software or report tool cannot realize the function of splicing any field of any report into one report, at present, when a banking staff splices the report, the banking staff usually needs to manually select required fields from several or tens of reports to form a new report, but the process of manually selecting the fields needs to waste a great deal of time cost and labor cost, the working efficiency is low, errors are unavoidable due to manual operation, and the accuracy of the spliced report is difficult to ensure.
Disclosure of Invention
The embodiment of the application aims to provide a report splicing method and system, which are used for solving the problems that the manual selection of fields in a report and the splicing work efficiency are low and the accuracy is difficult to guarantee in the prior art.
In order to solve the technical problems, the embodiment of the application adopts the following technical scheme: a report splicing method comprises the following steps: determining a row key of a row item to be spliced in a target report according to a query condition input by a user, wherein the row key is used for representing the data attribute of the row item to be spliced; acquiring the data content of the line item to be spliced according to the line key; and generating a spliced report according to the data content of the line items to be spliced.
Further, before determining the row key of the row item to be spliced in the target report according to the query condition input by the user, the method further includes: setting a corresponding row key for each row item of each report, wherein the row key at least comprises: the report name of the line item attribution report, the report date of the line item attribution report, the mechanism number of the corresponding mechanism of the report and the dimension field value corresponding to the line item.
Further, after setting the corresponding row key for each row item of each report, the method further includes: storing the data content of all the line items in a preset database, and storing the corresponding line keys of the line items as the main keys of the line items in the preset database.
Further, after the storing the corresponding row key of the row item as the main key of the row item in the preset database, the method further includes: and acquiring all data fields of each row item, and configuring each data field in all data fields as a secondary key of the row item.
Further, the query conditions include at least: the method comprises the steps of determining a report name of a target report to which a line item to be spliced belongs, a report date of the target report to which the line item to be spliced belongs, a mechanism number of a mechanism corresponding to the target report, and a dimension field value corresponding to the line item to be spliced.
Further, the query conditions further include: the field to be spliced is any field in all data fields of the line item to be spliced; when the query condition includes the field to be spliced, after the data content of the line item to be spliced is obtained according to the line key, the splicing method further includes: acquiring the data content of the field to be spliced from the data content of the line item to be spliced according to the field to be spliced; and generating a spliced report according to the data content of the field to be spliced.
The embodiment of the application also provides another technical scheme: a report stitching system, comprising: the row key determining module is used for determining row keys of row items to be spliced according to query conditions input by a user; the content acquisition module is used for acquiring the data content of the line item to be spliced according to the line key; and the report splicing module is used for generating a spliced report according to the data content of the line items to be spliced.
Further, the method further comprises the following steps: the line key setting module is used for setting a corresponding line key for each line item of each report, wherein the line key at least comprises: the report name of the line item attribution report, the report date of the line item attribution report, the mechanism number of the corresponding mechanism of the report and the dimension field value corresponding to the line item.
Further, the method further comprises the following steps: and the preset database is used for storing the data content of all the row items and storing the corresponding row keys of the row items as the main keys of the row items.
Further, the query conditions include at least: the report name of the line item attribution report, the report date of the line item attribution report, the mechanism number of the corresponding mechanism of the report and the dimension field value corresponding to the line item.
The embodiment of the application has the beneficial effects that: according to the method, a user can automatically acquire the data content corresponding to the line item to be spliced according to the line key determined by the query condition by directly inputting the query condition, so that a spliced report is generated, the process of manually selecting the field under the user line is omitted, the operation flow of the user is simplified, the time cost and the labor cost are greatly saved, the working efficiency is further improved, and the accuracy is improved compared with that of the manual operation mode by automatically acquiring the data content corresponding to the line item.
Drawings
FIG. 1 is a flowchart of a method for splicing a report table according to a first embodiment of the present application;
fig. 2 is a schematic structural diagram of a system for splicing a newspaper table according to a second embodiment of the present application.
Detailed Description
Various aspects and features of the present application are described herein with reference to the accompanying drawings.
It should be understood that various modifications may be made to the embodiments of the application herein. Therefore, the above description should not be taken as limiting, but merely as exemplification of the embodiments. Other modifications within the scope and spirit of the application will occur to persons of ordinary skill in the art.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the application and, together with a general description of the application given above, and the detailed description of the embodiments given below, serve to explain the principles of the application.
These and other characteristics of the application will become apparent from the following description of a preferred form of embodiment, given as a non-limiting example, with reference to the accompanying drawings.
It is also to be understood that, although the application has been described with reference to some specific examples, a person skilled in the art will certainly be able to achieve many other equivalent forms of the application, having the characteristics as set forth in the claims and hence all coming within the field of protection defined thereby.
The above and other aspects, features and advantages of the present application will become more apparent in light of the following detailed description when taken in conjunction with the accompanying drawings.
Specific embodiments of the present application will be described hereinafter with reference to the accompanying drawings; however, it is to be understood that the disclosed embodiments are merely exemplary of the application, which can be embodied in various forms. Well-known and/or repeated functions and constructions are not described in detail to avoid obscuring the application in unnecessary or unnecessary detail. Therefore, specific structural and functional details disclosed herein are not intended to be limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present application in virtually any appropriately detailed structure.
The first embodiment of the present application provides a report splicing method, and a flowchart thereof is shown in fig. 1, and mainly includes steps S101 to S103:
s101, determining a row key of a row item to be spliced in a target report according to a query condition input by a user;
s102, acquiring data content of a row item to be spliced according to a row key;
s103, generating a spliced report according to the data content of the line items to be spliced.
In this embodiment, the line items to be spliced are line items that the user needs to splice currently, and may be any line or several lines in the target report, or may be different line items in different target reports, where the number of the line items is not limited, and the current actual splicing requirement of the user is determined.
The row key is a parameter used for representing the data attribute of the row items to be spliced, each row of row items to be spliced is provided with a unique corresponding row key, and the corresponding row items can be determined through the row key, so that the data content contained in the row items is obtained. Therefore, before determining the row keys of the row items to be spliced in the target report according to the query conditions input by the user, the method further comprises the step of setting the corresponding row keys for each row item of each report. Specifically, each row key corresponds to a unique row item, so as to prevent the same row key from being determined between two different row items, and when the row key is set, the content of the row key at least includes: the method comprises the steps of attributing a report name of a report to which a line item belongs, a report date of the report to which the line item belongs, a mechanism number of a corresponding mechanism of the report, and a dimension field value corresponding to the line item. The row key in this embodiment includes a report name of a report to which the row item belongs in order to determine which report the current row item belongs specifically; in addition, the running water generated by the bank every day is different, so that the same line item can have different data contents under different dates for the same report, and the actual required line item needs to be determined according to the date of the report; the mechanism number of the corresponding mechanism of the report is used for determining which mechanism the current user wants to acquire to generate the report, such as a general line, an A area branch line, a B area branch line and the like, and the mechanism number can be the unique code of the mechanism or the MD5 value of the unique code of the mechanism; the dimension field value corresponding to the line item is used for determining a unique line item in the report, the dimension field refers to a field with a plurality of fixed values, for example, a frequency field, the fixed values of the dimension field include a date field, a month field, a quarter field, a year field and the like, the fixed values of the currency field include a RMB field, a dollar field, a british pound field, an Euro field and the like, the subject name field includes a fixed value of cash, business cash, a spare gold field and the like, and the line key of each line item includes all dimension field values to which the line belongs, so that unique line data can be determined without ambiguity.
It should be understood that, there is no sequence of combinations among the data attributes of each row item included in the row key, so long as each data attribute is included, and this embodiment provides a preferred sequence of combinations herein: the mechanism number of the corresponding mechanism of the report, the report name of the report with the line item attribution, the report date of the report with the line item attribution, and the dimension field value corresponding to the line item, in addition, the line key can also comprise a packet (schema) with the report attribution, such as a financial report, a performance report, and the like, and the value of the packet can be directly determined according to the report name of the report without the need of a user to input related query conditions.
When a user inputs a query condition, the related data attribute of the required line item to be spliced can be input to determine the line key corresponding to the line item to be spliced, so that the data content of the line item to be spliced is obtained. Specifically, the query conditions include at least the following: the method comprises the steps of obtaining a report name of a target report to which a row item to be spliced belongs, a report date of the target report to which the row item to be spliced belongs, a mechanism number of a mechanism corresponding to the target report, and a dimension field value corresponding to the row item to be spliced. And determining the row key corresponding to the row item to be spliced according to the query condition. In practical implementation, the user may manually input each item of content of the query condition, or may present options corresponding to each item of content of the query condition on the user interface, and determine the specific content of the query condition by clicking the options of the user, and it should be noted that all dimension field values of the corresponding row item are included in the row key, and then when the query condition is input, all dimension field values of the row item to be spliced should be input, so that only one row key can be determined, and only one corresponding row item is obtained.
Further, the data field is a field corresponding to a specific value, a plurality of data fields are generally included in one row of data, and only one or a plurality of data fields are needed in actual use, so that the query condition can also include a field to be spliced, the field to be spliced is any one field or any plurality of fields in all data fields of the row item to be spliced, and when the query condition includes the field to be spliced, after the data content of the row item to be spliced is acquired according to the row key, screening is further performed from the row item to be spliced according to the content of the field to be spliced, and only the data content corresponding to the field to be spliced in the row item to be spliced is acquired, so that a spliced report more meeting the actual user requirement and being concise is generated.
In order to ensure that the process of acquiring the corresponding line item according to the line key is convenient and quick and the result is accurate, in this embodiment, a preset database is used to store the data content of all the line items, and the line key corresponding to the line item is used as the main key of the line item and is stored in the preset database. When the method is actually used, the unique line item corresponding to the line key is searched in the preset database by using the line key determined according to the query condition, the line item is the line item to be spliced, and the data content of the line item is correspondingly obtained from the preset database. Preferably, the preset database in this embodiment may use an open-source keyword-value (key-value) to store the database HBase in columns, which saves space because the speed is very fast when the database HBase is queried under accurate conditions, and the database HBase stores a table suitable for storing data sparsely in columns.
Further, after the corresponding row key of the row item is stored as the primary key of the row item in the preset database, all the data fields of each row item can be obtained, each data field in all the data fields is configured as a secondary key of the row item, and when the query condition includes the field to be spliced, the data content of the field to be spliced can be directly obtained through the corresponding secondary key.
When in actual use, all original reports are respectively stored in a distributed database (ELK) developed based on an open source database PostgreSQL, and before the report is spliced by using the method for splicing the report provided by the embodiment, all row keys uniquely corresponding to all row items of all the reports stored in the ELK are required to be set; then using a data exchange platform to convert report data stored in the ELK into a structure which can be stored by the HBase, storing all line items of all reports into the HBase, and storing the line keys of all line items into the HBase together as main keys of the line keys; when the method is used, a user can select a target report to be spliced, the date of the report, a mechanism of the report and fields of a line item to be spliced as query conditions through a corresponding front-end interface, the line key determined by the query conditions is used for querying in the HBase to obtain the corresponding line item and specific data content of the line item, and finally, the display of the spliced report can be directly carried out on the front-end interface or the spliced report can be exported as an excel file for storage according to the requirements of the user.
It should be understood that the destination report may have two or more than two, and the splicing principle is that, in general, for each report, a row item of the same organization under the same day is selected as a row item to be spliced, so as to reflect business data of the organization in a certain day, and when the spliced report is generated, the same organization only correspondingly generates one piece of data in the same day, so that service personnel can conveniently compare and view the data, and the correspondingly generated piece of data can be displayed in a horizontal form in a row of a table or a vertical form in a column of the table. When the target report has a plurality of items, namely different query conditions are required to be input for a plurality of times to acquire the items to be spliced of different reports, a temporary storage can be set for temporarily storing the query conditions input by a user for a plurality of times, when the items to be spliced are acquired, the data contents of the corresponding items to be spliced are uniformly acquired from a database according to the query conditions in the temporary storage, or the data contents of the corresponding items to be spliced, which are respectively acquired according to the query conditions, are temporarily stored in the temporary storage, and when the report is spliced, the temporarily stored data contents are acquired from the temporary storage, and then the report is spliced.
According to the embodiment, the user can automatically acquire the data content corresponding to the line item to be spliced according to the line key determined by the query condition by directly inputting the query condition, so that a spliced report is generated, the process of manually selecting the field under the user line is omitted, the operation flow of the user is simplified, the time cost and the labor cost are greatly saved, the working efficiency is further improved, and the accuracy is improved compared with that of manual operation by automatically acquiring the data content corresponding to the line item.
The second embodiment of the present application provides a report splicing system, which can be deployed in a computer device, and is accessed by a user through a browser, and the structural schematic diagram of the report splicing system is shown in fig. 2, and mainly includes: the row key determining module 10 is used for determining row keys of row items to be spliced according to query conditions input by a user; the content acquisition module 20 is coupled with the row key determination module 10 and is used for acquiring the data content of the row items to be spliced according to the row keys; and the report splicing module 30 is coupled with the content acquisition module 20 and is used for generating a spliced report according to the data content of the line item to be spliced.
The row key is a parameter used for representing the data attribute of the row items to be spliced, each row of row items to be spliced is provided with a unique corresponding row key, and the corresponding row items can be determined through the row key, so that the data content contained in the row items is obtained. Therefore, before the line key determining module 10 determines the line key of the line item to be spliced in the target report according to the query condition input by the user, a process of setting the corresponding line key for each line item of each report through the line key setting module 40 is further included. Specifically, each row key corresponds to a unique row item, so as to prevent the same row key from being determined between two different row items, the row key setting module 40 at least includes: the method comprises the steps of attributing a report name of a report to which a line item belongs, a report date of the report to which the line item belongs, a mechanism number of a corresponding mechanism of the report, and a dimension field value corresponding to the line item.
It should be understood that, there is no sequence of combinations among the data attributes of each row item included in the row key, so long as each data attribute is included, and this embodiment provides a preferred sequence of combinations herein: the mechanism number of the corresponding mechanism of the report forms, the report name of the report forms with the line items, the report date of the report forms with the line items and the dimension field value corresponding to the line items.
When the user inputs the query condition, the relevant data attribute of the line item to be spliced can be input, so that the line key determining module 10 determines the line key corresponding to the line item to be spliced, and further the data content of the line item to be spliced is acquired through the content acquiring module 20. Specifically, the query conditions include at least the following: the method comprises the steps of obtaining a report name of a target report to which a row item to be spliced belongs, a report date of the target report to which the row item to be spliced belongs, a mechanism number of a mechanism corresponding to the target report, and a dimension field value corresponding to the row item to be spliced. And determining the row key corresponding to the row item to be spliced according to the query condition. In actual implementation, the user may manually input each item of the query condition, or may present options corresponding to each item of the query condition on the user interface, and the row key determining module 10 determines the specific content of the query condition by clicking the options of the user, where it should be noted that the row key includes values of all dimension fields of the corresponding row item, and then when the query condition is input, the values of all dimension fields of the row item to be spliced should also be input, so that only one row key can be determined, and only one corresponding row item is obtained.
Further, the data field is a field corresponding to a specific value, a plurality of data fields are generally included in one row of data, and only one or a plurality of data fields are needed in actual use, so that the query condition can also include a field to be spliced, the field to be spliced is any one field or any plurality of fields in all data fields of the row item to be spliced, and when the query condition includes the field to be spliced, the content acquisition module 20 acquires the data content of the row item to be spliced according to the row key, screens from the row item to be spliced according to the content of the field to be spliced, and only acquires the data content corresponding to the field to be spliced in the row item to be spliced, thereby generating a spliced report more in line with actual user requirements and conciseness.
In order to ensure that the process of acquiring the corresponding line item according to the line key is convenient and quick and the result is accurate, the embodiment further includes a preset database 50, which is respectively coupled to the line key determining module 10, the content acquiring module 20 and the line key setting module 40, and is configured to store the data content of all the line items, and store the corresponding line key of the line item as the main key of the line item. The preset database in the embodiment is an HBase database, and because the speed is extremely high during accurate condition query, and the table suitable for storing sparse data is stored in columns, the space is saved. Further, all the data fields of each row item may be stored in the preset database 50 as secondary keys of the row item, and when the corresponding query condition includes the field to be spliced, the content obtaining module 20 may directly obtain the data content of the field to be spliced from the preset database 50 through the corresponding secondary keys.
The report splicing module 30 is configured to splice the data content of the line item to be spliced acquired by the content acquisition module 20, generate a spliced report for service personnel to use, and finally output the spliced report, which can be directly displayed on a front end interface of the system or exported as an excel file for storage according to the requirement of a user.
According to the embodiment, the user can automatically acquire the data content corresponding to the line item to be spliced according to the line key determined by the query condition by directly inputting the query condition, so that a spliced report is generated, the process of manually selecting the field under the user line is omitted, the operation flow of the user is simplified, the time cost and the labor cost are greatly saved, the working efficiency is further improved, and the accuracy is improved compared with that of manual operation by automatically acquiring the data content corresponding to the line item.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.
Claims (5)
1. The report splicing method is characterized by comprising the following steps of:
setting a corresponding row key for each row item of each report, wherein the row key at least comprises: the report name of the line item attribution report, the report date of the line item attribution report, the mechanism number of the corresponding mechanism of the report and the dimension field value corresponding to the line item;
storing the data content of all the line items in a preset database, and storing the corresponding line keys of the line items as the main keys of the line items in the preset database;
acquiring all data fields of each row item, and configuring each data field in all data fields as a secondary key of the row item;
determining a row key of a row item to be spliced in a target report according to a query condition input by a user, wherein the row key is used for representing the data attribute of the row item to be spliced;
acquiring the data content of the line item to be spliced according to the line key;
and generating a spliced report according to the data content of the line items to be spliced.
2. The stitching method of claim 1 wherein the query conditions include at least: the method comprises the steps of determining a report name of a target report to which a line item to be spliced belongs, a report date of the target report to which the line item to be spliced belongs, a mechanism number of a mechanism corresponding to the target report, and a dimension field value corresponding to the line item to be spliced.
3. The stitching method of claim 2 wherein the query conditions further comprise: the field to be spliced is any field in all data fields of the line item to be spliced;
when the query condition includes the field to be spliced, after the data content of the line item to be spliced is obtained according to the line key, the splicing method further includes:
acquiring the data content of the field to be spliced from the data content of the line item to be spliced according to the field to be spliced;
and generating a spliced report according to the data content of the field to be spliced.
4. A report stitching system, comprising:
the line key setting module is used for setting a corresponding line key for each line item of each report, wherein the line key at least comprises: the report name of the line item attribution report, the report date of the line item attribution report, the mechanism number of the corresponding mechanism of the report and the dimension field corresponding to the line item;
the preset database is used for storing the data content of all the line items and storing the corresponding line keys of the line items as the main keys of the line items; storing all data fields of each row item as secondary keys of the row item;
the row key determining module is used for determining row keys of row items to be spliced according to query conditions input by a user;
the content acquisition module is used for acquiring the data content of the line item to be spliced according to the line key;
and the report splicing module is used for generating a spliced report according to the data content of the line items to be spliced.
5. The splicing system of claim 4, wherein the query conditions include at least: the report name of the line item attribution report, the report date of the line item attribution report, the mechanism number of the corresponding mechanism of the report and the dimension field value corresponding to the line item.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910599892.4A CN110298023B (en) | 2019-07-04 | 2019-07-04 | Report splicing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910599892.4A CN110298023B (en) | 2019-07-04 | 2019-07-04 | Report splicing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110298023A CN110298023A (en) | 2019-10-01 |
| CN110298023B true CN110298023B (en) | 2023-08-25 |
Family
ID=68030309
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910599892.4A Active CN110298023B (en) | 2019-07-04 | 2019-07-04 | Report splicing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110298023B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112131855B (en) * | 2020-09-30 | 2024-04-19 | 中国银行股份有限公司 | Bank certificate template generation method and device |
| CN112445873B (en) * | 2020-12-02 | 2024-03-26 | 深圳市镜玩科技有限公司 | List display processing method, related device, equipment and medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1588369A (en) * | 2004-09-06 | 2005-03-02 | 杭州恒生电子股份有限公司 | Relation type data base system and its search and report method |
| WO2014082198A1 (en) * | 2012-11-27 | 2014-06-05 | Nokia Siemens Networks Oy | Multiple fields parallel query method and corresponding storage organization |
| CN105843945A (en) * | 2016-04-08 | 2016-08-10 | 联动优势科技有限公司 | Report generation method and system |
| CN109471890A (en) * | 2018-10-16 | 2019-03-15 | 深圳壹账通智能科技有限公司 | Generation method, terminal device and the medium of report file |
-
2019
- 2019-07-04 CN CN201910599892.4A patent/CN110298023B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1588369A (en) * | 2004-09-06 | 2005-03-02 | 杭州恒生电子股份有限公司 | Relation type data base system and its search and report method |
| WO2014082198A1 (en) * | 2012-11-27 | 2014-06-05 | Nokia Siemens Networks Oy | Multiple fields parallel query method and corresponding storage organization |
| CN105843945A (en) * | 2016-04-08 | 2016-08-10 | 联动优势科技有限公司 | Report generation method and system |
| CN109471890A (en) * | 2018-10-16 | 2019-03-15 | 深圳壹账通智能科技有限公司 | Generation method, terminal device and the medium of report file |
Non-Patent Citations (1)
| Title |
|---|
| 智能报表生成系统的研究;程志蓉;《许昌学院学报》;20040330(第02期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110298023A (en) | 2019-10-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111192004A (en) | Method for displaying current to-do task and subsequent to-do workflow | |
| CN111177231A (en) | Report generation method and report generation device | |
| CN109144997A (en) | Data correlation method, device and storage medium | |
| US20090006472A1 (en) | Automatic Designation of XBRL Taxonomy Tags | |
| CN104217276A (en) | Rule-based automatic auditing method and system | |
| CN110795524B (en) | Main data mapping processing method and device, computer equipment and storage medium | |
| CN110298023B (en) | Report splicing method and system | |
| CN106294478A (en) | The data processing method of data warehouse and device | |
| CN110716951A (en) | Label configuration method, device and equipment convenient to configure and storage medium | |
| CN104112004A (en) | Method for intelligently copying data on user interface | |
| CN111382279A (en) | Order examination method and device | |
| CN110879939A (en) | Method and device for generating response document | |
| US9208194B2 (en) | Expanding high level queries | |
| KR102184048B1 (en) | System and method for checking of information about estate development plan based on geographic information system | |
| US10269079B2 (en) | Determining local regulatory filing workflow through user contribution | |
| CN112184419A (en) | Method and device for providing service for customer | |
| KR102463120B1 (en) | Patent document searching server providing user customized flle name generating function when dowloading document and patent document searching method using thereof | |
| CN114372189A (en) | Processing method and device of user-defined report, storage medium and electronic equipment | |
| CN109542890A (en) | Data modification method, device, computer equipment and storage medium | |
| CN106126633B (en) | Processing method, the device and system of noble metal data | |
| CN110264357B (en) | Account moving processing method, device, equipment and computer readable storage medium | |
| CN109508185B (en) | Code review method and device | |
| CN110858214B (en) | Recommendation model training and further auditing program recommendation method, device and equipment | |
| CN112380321A (en) | Primary and secondary database distribution method based on bill knowledge graph and related equipment | |
| US20150242913A1 (en) | Enterprise price quote generation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |