CN101887455B - Method and system for managing multi-version report data - Google Patents
Method and system for managing multi-version report data Download PDFInfo
- Publication number
- CN101887455B CN101887455B CN2010102159902A CN201010215990A CN101887455B CN 101887455 B CN101887455 B CN 101887455B CN 2010102159902 A CN2010102159902 A CN 2010102159902A CN 201010215990 A CN201010215990 A CN 201010215990A CN 101887455 B CN101887455 B CN 101887455B
- Authority
- CN
- China
- Prior art keywords
- version
- data
- report
- truncation
- report data
- 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
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method and a system for managing multi-version report data, wherein the method comprises the steps of: presetting a report version by a check sheet system, typing in check sheet data by a user according to the check sheet version; executing version definition related with a report of the check sheet data in a version definition and management module; and executing the storage of the multi-version report data through using the defined versions as intrinsic dimensions of the multi-version report data, wherein the versions correspond to application nodes. Therefore, by combining the system preset and the user definition, the invention ensures that the application nodes only use the versions of corresponding types, the user can only carry out any expansion on the type of the version, and the version is combined with the specific application node, the system controls a certain application node to only use the corresponding version, thereby ensuring the rightness of using the version from the program and avoiding the user use error of possible error input of a combined version, which is similar to the typing in of the check sheet.
Description
Technical field
The present invention relates generally to the reporting system field, more specifically, relates to a kind of managing multi-version report data method and system, the management that it presets release type through reporting system and is realized the multi-version report data by User Defined version number.
Background technology
The report datas that have a lot of covers in the reporting system, for example, for a certain unit, during report data; Can be divided into acquisition tables data, consolidated accounts data, summary sheet data etc. again; And combined data can be divided into difference and gathers data of bore or the like, and in addition, system can be thousand yuan, ten thousand yuan data for the table of unit is converted into amount of money unit with amount of money unit again; In the art, with this amount of money unit by unit transform thousands of unit, ten thousand yuan operation is called truncation.
For the ease of describing, in the art, with overlapping many versions that report data is referred to as report data more.For the many version problems of data, present reporting system does not have built-in solution, generally is to be solved through application scheme is flexible by the enforcement personnel.
Yet the problem of existing application scheme and existence is following:
(1) on form, add a dimension that is similar to " version ", report data just can the fractional dimension storage like this.Yet the problem that this scheme exists is; 1) strengthened amount of user effort; The value that all needs the typing version in the place of all input report data dimensions; Particularly having strengthened form collection personnel's workload, for the people of typing acquisition tables data, itself is need not know this notion of version; Owing to added this dimension of version, repeated to import version information when needing logging data; And 2) do not combine, cause the managerial confusion of report data easily with concrete the application, as when the typing acquisition tables data, if the value of version dimension mistake is input as the version of pooled data, the system identification this mistake of not coming out.
(2) set up some virtual units, with the data of virtual unit storage special version.Yet the problem that this scheme exists is: 1) when version increases, virtual unit can be multiplied, the unit's of causing system numerous and jumbled; And 2) the same a kind of scheme is the same; Because do not combine with concrete the application, the correctness of report data management can not get guaranteeing, by this scheme; The unit scope that a certain application node can be selected be in the unit system one among a small circle; How to guarantee that the user can not select this extraneous unit, can't do control, can only depend on operating personnel and not make a mistake from program.
Therefore, be badly in need of a solution, need the user to import the drawback of version value and the drawback that need set up huge unit system in the time of can avoiding data acquisition, to reduce user's workload.
Summary of the invention
In view of the foregoing, the invention provides a kind of managing multi-version report data method and system, be mainly used in collection, processing, storage and the analysis of report data.
According to an aspect of the present invention, the managing multi-version report data method may further comprise the steps: step S102, preset the acquisition tables version through reporting system, and the user comes typing acquisition tables data according to the acquisition tables version; Step S104 at version definition and administration module place, carries out the version definition relevant with the report form processing of acquisition tables data; And step S106, through defined version is carried out the storage of multi-version report data as the intrinsic dimension of multi-version report data, wherein, version is corresponding one by one with application node, and the acquisition tables data are sources of multi-version report data.
In technique scheme, alternatively, the managing multi-version report data method can also may further comprise the steps: utilize defined version to analyze the multi-version report data as analyzing dimension; And with defined version as the parameter in the figure selection formula, get the report data of indicated release in the multi-version report data, to carry out the mutual peek between version, wherein, analyze and peek can be applied to the report data of all versions.
In step S104, when report form processing is the report data aggregation process, gather the application node place in data; Definition is used for the bore that gathers that report data gathers, if reuse existing summarized version, then can directly specify this to gather the summarized version of bore; Otherwise at version definition and administration module place, define the summarized version that this gathers bore, and gathering the application node place; Based on the acquisition tables version and utilize summarized version, carry out gathering of report data, wherein; Gather to be divided into and freely gather and gather subordinate, and different gathering can share same version, summarized version is an already present summarized version in redaction or the reporting system; And the summarized results of report data is the acquisition tables data and is gathering when gathering subordinate that the summarized results of report data is stored as the edition data of acquisition tables data.
Alternatively, when report form processing is report data merging processing, set up the Merge Scenarios that is used to generate consolidated accounts at consolidated accounts application node place; At version definition and administration module place, based on the consolidated accounts versions of data of Merge Scenarios definition consolidated accounts, and at consolidated accounts application node place; Based on the pooled data version and utilize Merge Scenarios; Generate the consolidated accounts data, wherein, the pooled data version is divided into consolidated accounts version and adjustment form version; Consolidated accounts version and adjustment form version are corresponding one by one with Merge Scenarios, and the source of consolidated accounts data is the acquisition tables data.
Alternatively, when report form processing is handled for the version truncation, at truncation application node place; Definition is used for the truncation rule of version truncation, at version definition and administration module place, corresponding to truncation rule and Data Source version; Definition is corresponding to the truncation version of truncation data, at truncation application node place, based on the version and the truncation rule of source report data; Obtain required truncation version and carry out truncation by the truncation rule; Wherein, the truncation version is corresponding one by one with truncation rule and versions of data source, and the version in versions of data source is acquisition tables, summarized version or the pooled data version of acquisition tables data at least.
According to another aspect of the present invention, the managing multi-version report data system comprises: data acquisition unit is used for presetting the acquisition tables version and making the user come typing acquisition tables data according to the acquisition tables version through reporting system; Version definition and administrative unit are used to carry out the version definition relevant with the report form processing of acquisition tables data; And data storage cell; Be used for through defined version is carried out the storage of multi-version report data as the intrinsic dimension of multi-version report data; Wherein, version is corresponding one by one with application node, and the acquisition tables data are sources of multi-version report data.
Alternatively, this managing multi-version report data system can also comprise: analytic unit is used to utilize defined version to analyze the multi-version report data as analyzing dimension; And formula computing unit; Be used for the parameter of defined version as figure selection formula got the report data of indicated release in the multi-version report data, to carry out the mutual peek between version; Wherein, analysis and peek can be applied to the report data of all versions.
In version definition and administrative unit, when report form processing is the report data aggregation process, gather the application node place in data; Definition is used for the bore that gathers that report data gathers, if reuse existing summarized version, then can directly specify this to gather the summarized version of bore; Otherwise need define the summarized version that this gathers bore at version definition and administration module place, and gather the application node place; Based on the acquisition tables version and utilize summarized version; Carry out gathering of report data, wherein, gather to be divided into and freely gather and gather subordinate; And different gathering can be shared same version; Summarized version is an already present summarized version in redaction or the reporting system, and the summarized results of report data is the acquisition tables data and is gathering when gathering subordinate that the summarized results of report data is stored as the edition data of acquisition tables data.
Alternatively, when report form processing is report data merging processing, set up the Merge Scenarios that is used to generate consolidated accounts at consolidated accounts application node place; In version definition and administrative unit, based on Merge Scenarios, the consolidated accounts versions of data of definition consolidated accounts; And, based on the pooled data version and utilize Merge Scenarios, generate the consolidated accounts data at consolidated accounts application node place; Wherein, The pooled data version is divided into consolidated accounts version and adjustment form version, and consolidated accounts version and adjustment form version are corresponding one by one with Merge Scenarios, and the source of consolidated accounts data is the acquisition tables data.
Alternatively, when report form processing is handled for the version truncation, at truncation application node place; Definition is used for the truncation rule of version truncation, at version definition and administration module place, corresponding to truncation rule and Data Source version; Definition is corresponding to the truncation version of truncation data, and at truncation application node place, based on the version and the truncation rule of source report data; Obtain required truncation version and carry out truncation by the truncation rule; Wherein, the truncation version is corresponding one by one with truncation rule and versions of data source, and the version in versions of data source is acquisition tables, summarized version or the pooled data version of acquisition tables data at least.
Therefore, through the present invention, release type is by system intialization, and concrete version number is by User Defined.Combine with user-defined through system intialization; Guaranteed that application node can only use the version of corresponding types; The user can do any expansion to such version again, and version combines with concrete application node, and system has controlled a certain application node can only use respective version; Guarantee the correctness that version uses from program, possibly import the user's operating mistake that merges version when having avoided being similar to the acquisition tables typing in the prior art by mistake.
Description of drawings
Fig. 1 is the process flow diagram according to managing multi-version report data method of the present invention;
Fig. 2 is the synoptic diagram according to the managing multi-version report data of the embodiment of the invention;
Fig. 3 is the synoptic diagram according to the treatment scheme of the consolidated accounts version of the embodiment of the invention; And
Fig. 4 is the block diagram according to managing multi-version report data of the present invention system.
Embodiment
Below will combine accompanying drawing to describe embodiments of the invention in detail.
Fig. 1 is the process flow diagram according to managing multi-version report data method of the present invention.As shown in Figure 1, this method may further comprise the steps:
Step S102 presets the acquisition tables version through reporting system, and the user comes typing acquisition tables data according to the acquisition tables version;
Step S104 at version definition and administration module place, carries out the version definition relevant with the report form processing of acquisition tables data; And
Step S106, through defined version is carried out the storage of multi-version report data as the intrinsic dimension of multi-version report data, wherein, version is corresponding one by one with application node, and the acquisition tables data are sources of multi-version report data.
Alternatively, the managing multi-version report data method can also may further comprise the steps: utilize defined version to analyze the multi-version report data as analyzing dimension; And with defined version as the parameter in the figure selection formula, get the report data of indicated release in the multi-version report data, to carry out the mutual peek between version, wherein, analyze and peek can be applied to the report data of all versions.
In step S104, when report form processing is the report data aggregation process, gather the application node place in data; Definition is used for the bore that gathers that report data gathers, if reuse existing summarized version, then can directly specify this to gather the summarized version of bore; Otherwise at version definition and administration module place, define the summarized version that this gathers bore, and gathering the application node place; Based on the acquisition tables version and utilize summarized version, carry out gathering of report data, wherein; Gather to be divided into and freely gather and gather subordinate, and different gathering can share same version, summarized version is an already present summarized version in redaction or the reporting system; And the summarized results of report data is the acquisition tables data and is gathering when gathering subordinate that the summarized results of report data is stored as the edition data of acquisition tables data.
Alternatively, when report form processing is report data merging processing, set up the Merge Scenarios that is used to generate consolidated accounts at consolidated accounts application node place; At version definition and administration module place, based on the consolidated accounts versions of data of Merge Scenarios definition consolidated accounts, and at consolidated accounts application node place; Based on the pooled data version and utilize Merge Scenarios; Generate the consolidated accounts data, wherein, the pooled data version is divided into consolidated accounts version and adjustment form version; Consolidated accounts version and adjustment form version are corresponding one by one with Merge Scenarios, and the source of consolidated accounts data is the acquisition tables data.
Alternatively, when report form processing is handled for the version truncation, at truncation application node place; Definition is used for the truncation rule of version truncation, at version definition and administration module place, corresponding to truncation rule and Data Source version; Definition is corresponding to the truncation version of truncation data, and at truncation application node place, based on the version and the truncation rule of source report data; Obtain required truncation version and carry out truncation, wherein, carry out the version truncation of report data by the truncation rule; Wherein, the truncation version is corresponding one by one with truncation rule and versions of data source, and the version in versions of data source is acquisition tables, summarized version or the pooled data version of acquisition tables data at least.
Fig. 2 is the synoptic diagram according to the managing multi-version report data of the embodiment of the invention.Below will combine Fig. 2 that the function and the relation of each involved in multi-version report data processing module are set forth in detail.
The definition of version and management
The definition of version and management function are the centers of many version managements, are the function points of unique definition, maintenance release in the system, and all versions all must define, safeguard at this in the system.Each version is applied to an application node, and corresponding business rule.
The relation of itself and data acquisition: system can preset an acquisition tables version, is specifically designed to the acquisition tables typing.
Its with gather, the relation of merging, truncation: gather, the version of merging, truncation data need define at this, when the definition version, the user must select this version corresponding gather bore, Merge Scenarios, truncation rule etc.
The relation of itself and data storage, analysis, calculating: during data storage, with the version of definition a dimension, during analysis as the report data storage; Utilize version as the dimension of analyzing; During calculating, can be with version as the parameter in the formula, the version of the report data that appointment will be got.
Data storage
Through with the intrinsic dimension of version as report data, realized many storage of versions of report data, promptly its storage mode of the data of each version is the same, just the value of this dimension of version is different.
Many storage of versions of report data, the same with version management, be the basis of the many version managements of report data.
Data acquisition
Data acquisition is the source of all report datas, the acquisition tables storage of versions that using system presets.During user's typing acquisition tables data, need not import version information.
Itself and the relation that gathers: the acquisition tables version both can be the source version that gathers, and can be used as the purpose version that gathers again, and promptly the summarized results of acquisition tables can be used as the logging data of acquisition tables again.
Gather
Gather to be divided into and freely gather and gather subordinate.Different freely gather between can share same version.Different gathering between the subordinate also can be shared same version; Because in actual the use; Its acquisition tables data of certain some intermediate unit need be gathered by subordinate unit's acquisition tables data; Allow to quote the acquisition tables version so gather the versions of data of subordinate, gather like this after subordinate finishes, the acquisition tables data of intermediate unit have just generated automatically.
The relation of itself and version management: when gathering, need define earlier and gather bore, need gather bore then for this reason and specify a summarized version.Summarized version is set up in version management place, and can utilize this to gather bore and set up a redaction, or a summarized version that has existed (promptly utilizing other to gather the summarized version that bore is set up) in the cited system.
The relation of itself and data acquisition: the source of summarized results is the acquisition tables data, and when gathering subordinate, summarized results can be stored as the acquisition tables edition data again conversely.
Merge
The versions of data that merges module is divided into consolidated accounts and adjustment form version.The Merge Scenarios that each consolidated accounts or adjustment form version are corresponding different, different Merge Scenarioses does not allow to use same version, promptly is man-to-man relation between consolidated accounts version and the Merge Scenarios.Solve the user like this and gone out the problem that many covers merge the result.
The relation of itself and version management: during merging, need define Merge Scenarios earlier, define adjustment form and consolidated accounts version that should Merge Scenarios in version management place again, just can carry out the adjustment and the merging of form then.
The relation of itself and data acquisition: the source of consolidated accounts and adjustment form data is acquisition tables data.
Truncation
The truncation version is on the basis of other non-truncation versions, the version that goes out according to the truncation rule definition.During definition truncation version, select a non-truncation version earlier, select a truncation rule again.
The relation of itself and version management: need be at truncation node place definition truncation rule earlier, again in version management place, a corresponding truncation rule and a data source version define the version of the truncation data of correspondence.
Its with data acquisition, the relation that gathers, merge: corresponding truncation rule of truncation version and Data Source version, and the Data Source version can be acquisition tables, gather, merges version.
Data analysis
Because versions of data is visible to the user, during data analysis, can version be analyzed as dimension of report data.Support the data of all versions to analyze.
Formula calculates
Formula calculates and is supported in the mutual peek that reaches between the same version between the different editions, in figure selection formula, can define Release parameter, and the version that clearly will peek when formula calculates like this, is got the data of indicated release, otherwise got the data of current version.Support is to the calculating of peeking of the data of all versions.
Fig. 3 is the synoptic diagram according to the treatment scheme of the consolidated accounts version of the embodiment of the invention.As shown in Figure 3, concrete treatment scheme is following:
S302, newly-built Merge Scenarios (this operates in the consolidated accounts functional node and carries out, and Merge Scenarios is meant the one group of rule that generates consolidated accounts, comprises the counteracting template of merging scope, merging mode, application etc.);
S304, definition consolidated accounts version (this operate in version management place carry out, a newly-built consolidated accounts version needs to specify a Merge Scenarios, and this scheme must be not specify the Merge Scenarios that merges version);
S306 confirms the corresponding consolidated accounts versions of data of Merge Scenarios (through S304, the consolidated accounts version is defined out, and binds with Merge Scenarios, and the pooled data version that promptly this Merge Scenarios is corresponding is determined); And
S308 carry out to merge (the pooled data version that Merge Scenarios is corresponding be determined after, just can utilize this Merge Scenarios to carry out union operation, generation consolidated accounts data).
Fig. 4 is the block diagram according to managing multi-version report data of the present invention system 400.As shown in Figure 4, managing multi-version report data system 400 comprises: data acquisition unit 402 is used for presetting the acquisition tables version and making the user come typing acquisition tables data according to the acquisition tables version through reporting system; Version definition and administrative unit 404 are used to carry out the version definition relevant with the report form processing of acquisition tables data; And data storage cell 406; Be used for through defined version is carried out the storage of multi-version report data as the intrinsic dimension of multi-version report data; Wherein, version is corresponding one by one with application node, and the acquisition tables data are sources of multi-version report data.
Alternatively, this managing multi-version report data system 400 can also comprise: analytic unit 408 is used to utilize defined version to analyze the multi-version report data as analyzing dimension; And formula computing unit 410; Be used for the parameter of defined version as figure selection formula got the report data of indicated release in the multi-version report data, to carry out the mutual peek between version; Wherein, analysis and peek can be applied to the report data of all versions.
In version definition and administrative unit 404, when report form processing is the report data aggregation process, gather the application node place in data; Definition is used for the bore that gathers that report data gathers, if reuse existing summarized version, then can directly specify this to gather the summarized version of bore; Otherwise need define the summarized version that this gathers bore at version definition and administration module place, and gather the application node place; Based on the acquisition tables version and utilize summarized version; Carry out gathering of report data, wherein, gather to be divided into and freely gather and gather subordinate; And different gathering can be shared same version; Summarized version is an already present summarized version in redaction or the reporting system, and the summarized results of report data is the acquisition tables data and is gathering when gathering subordinate that the summarized results of report data is stored as the edition data of acquisition tables data.
Alternatively, when report form processing is report data merging processing, set up the Merge Scenarios that is used to generate consolidated accounts at consolidated accounts application node place; In version definition and administrative unit, based on Merge Scenarios, the consolidated accounts versions of data of definition consolidated accounts; And, based on the pooled data version and utilize Merge Scenarios, generate the consolidated accounts data at consolidated accounts application node place; Wherein, The pooled data version is divided into consolidated accounts version and adjustment form version, and consolidated accounts version and adjustment form version are corresponding one by one with Merge Scenarios, and the source of consolidated accounts data is the acquisition tables data.
Alternatively, when report form processing is handled for the version truncation, at truncation application node place; Definition is used for the truncation rule of version truncation, at version definition and administration module place, corresponding to truncation rule and Data Source version; Definition is corresponding to the truncation version of truncation data, and at truncation application node place, based on the version and the truncation rule of source report data; Obtain required truncation version and carry out truncation by the truncation rule; Wherein, the truncation version is corresponding one by one with truncation rule and versions of data source, and the version in versions of data source is acquisition tables, summarized version or the pooled data version of acquisition tables data at least.
In sum, through the present invention, the built-in support report data of system is by storage of versions; Need not solve through application scheme is flexible, and version number's User Defined, extendability is strong (if hope to preserve the different report datas that gather bore; Only need gather bore by these sets up version respectively and just can solve); In addition, since release type by system intialization concrete version number by User Defined, so combine with user-defined through system intialization; Guaranteed that application node can only use the version of corresponding types, the user can do any expansion to such version again.
In addition, the drawback that needs the user to import the drawback of version value and need set up huge unit system when having avoided data acquisition in the prior art through the present invention, thus improved amount of user effort.
In addition; In the present invention, version combines with concrete application node, and system has controlled a certain application node can only use respective version; Guarantee the correctness that version uses from program, possibly import the user's operating mistake that merges version when having avoided being similar to the acquisition tables typing in the prior art by mistake.
The above is merely the preferred embodiments of the present invention, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.All within spirit of the present invention and principle, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. managing multi-version report data method, it presets release type through reporting system and is realized it is characterized in that the management of multi-version report data by User Defined version number, may further comprise the steps:
Step S102 presets the acquisition tables version through said reporting system, and the user comes typing acquisition tables data according to said acquisition tables version;
Step S104 at version definition and administration module place, carries out the version definition relevant with the report form processing of said acquisition tables data; And
Step S106, through defined version is carried out the storage of said multi-version report data as the intrinsic dimension of said multi-version report data,
Wherein, the version of said multi-version report data is corresponding one by one with application node, and the said acquisition tables data source that is said multi-version report data.
2. managing multi-version report data method according to claim 1 is characterized in that, and is further comprising the steps of:
Utilize defined version to analyze said multi-version report data as analyzing dimension; And
Defined version as the parameter in the figure selection formula, is got the report data of indicated release in the said multi-version report data, with the mutual peek between the execution version,
Wherein, said analysis and peek can be applied to the report data of all versions.
3. managing multi-version report data method according to claim 1 and 2 is characterized in that, in said step S104, and when said report form processing is the report data aggregation process,
Gather the application node place in data, definition is used for the bore that gathers that report data gathers,
If reuse existing summarized version, then directly specify the said summarized version that gathers bore, otherwise, define the said summarized version that gathers bore at said version definition and administration module place, and
Gather the application node place in said data, based on said acquisition tables version and utilize said summarized version, carry out gathering of said report data,
Wherein, said gather to be divided into freely gather and gather subordinate, and different gathering can share same version,
Said summarized version is an already present summarized version in redaction or the said reporting system, and
The summarized results of said report data is said acquisition tables data and gathers when gathering subordinate said that the summarized results of said report data is stored as the edition data of said acquisition tables data.
4. managing multi-version report data method according to claim 1 is characterized in that, in said step S104, and when said report form processing is report data merging processing,
Set up the Merge Scenarios that is used to generate consolidated accounts at consolidated accounts application node place,
At said version definition and administration module place, based on said Merge Scenarios, define the consolidated accounts versions of data of said consolidated accounts, and
At said consolidated accounts application node place, based on said consolidated accounts versions of data and utilize said Merge Scenarios, generate the consolidated accounts data,
Wherein, said consolidated accounts versions of data is divided into consolidated accounts version and adjustment form version,
Said consolidated accounts version and said adjustment form version are corresponding one by one with Merge Scenarios, and
The source of said consolidated accounts data is said acquisition tables data.
5. according to claim 3 or 4 described managing multi-version report data methods, it is characterized in that, in said step S104, when said report form processing is handled for the version truncation,
At truncation application node place, definition is used for the truncation rule of version truncation,
At said version definition and administration module place, corresponding to said truncation rule and Data Source version, define truncation version corresponding to the truncation data, and
At truncation application node place, version and said truncation rule based on the source report data obtain required truncation version and carry out truncation by said truncation rule,
Wherein, said truncation version is corresponding one by one with said truncation rule and said Data Source version, and
The version of said Data Source version is the acquisition tables of said acquisition tables data, said summarized version or said pooled data version at least.
6. managing multi-version report data system, it presets release type through reporting system and is realized it is characterized in that the management of multi-version report data by User Defined version number, comprising:
Data acquisition unit is used for presetting the acquisition tables version and making the user come typing acquisition tables data according to said acquisition tables version through said reporting system;
Version definition and administrative unit are used to carry out the version definition relevant with the report form processing of said acquisition tables data; And
Data storage cell is used for through defined version is carried out the storage of said multi-version report data as the intrinsic dimension of said multi-version report data,
Wherein, the version of said multi-version report data is corresponding one by one with application node, and the said acquisition tables data source that is said multi-version report data.
7. managing multi-version report data according to claim 6 system is characterized in that, also comprises:
Analytic unit is used to utilize defined version to analyze said multi-version report data as analyzing dimension; And
The formula computing unit is used for the parameter of defined version as figure selection formula got the report data of indicated release in the said multi-version report data, with the mutual peek between the execution version,
Wherein, said analysis and peek can be applied to the report data of all versions.
8. according to claim 6 or 7 described managing multi-version report data systems, it is characterized in that, in version definition and administrative unit, when said report form processing is the report data aggregation process,
Gather the application node place in data, definition is used for the bore that gathers that report data gathers,
If reuse existing summarized version, then directly specify the said summarized version that gathers bore, otherwise define the said summarized version that gathers bore, and
Gather the application node place in said data, based on said acquisition tables version and utilize said summarized version, carry out gathering of said report data,
Wherein, said gather to be divided into freely gather and gather subordinate, and different gathering can share same version,
Said summarized version is an already present summarized version in redaction or the said reporting system, and
The summarized results of said report data is said acquisition tables data and gathers when gathering subordinate said that the summarized results of said report data is stored as the edition data of said acquisition tables data.
9. managing multi-version report data according to claim 6 system is characterized in that, in said version definition and administrative unit, and when said report form processing is that report data merges when handling,
Set up the Merge Scenarios that is used to generate consolidated accounts at consolidated accounts application node place,
Based on said Merge Scenarios, define the consolidated accounts versions of data of said consolidated accounts, and
At said consolidated accounts application node place, based on said consolidated accounts versions of data and utilize said Merge Scenarios, generate the consolidated accounts data,
Wherein, said consolidated accounts versions of data is divided into consolidated accounts version and adjustment form version,
Said consolidated accounts version and said adjustment form version are corresponding one by one with Merge Scenarios, and
The source of said consolidated accounts data is said acquisition tables data.
10. according to Claim 8 or 9 described managing multi-version report data systems, it is characterized in that, in version definition and administrative unit, when said report form processing is handled for the version truncation,
At truncation application node place, definition is used for the truncation rule of version truncation,
Corresponding to said truncation rule and Data Source version, define truncation version corresponding to the truncation data, and
At truncation application node place; Version and said truncation rule based on the source report data; Obtain required truncation version and carry out truncation by said truncation rule; Wherein, said truncation version is corresponding one by one with said truncation rule and said Data Source version, and the version of said Data Source version is the acquisition tables of said acquisition tables data, said summarized version or said pooled data version at least.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010102159902A CN101887455B (en) | 2010-06-22 | 2010-06-22 | Method and system for managing multi-version report data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010102159902A CN101887455B (en) | 2010-06-22 | 2010-06-22 | Method and system for managing multi-version report data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101887455A CN101887455A (en) | 2010-11-17 |
| CN101887455B true CN101887455B (en) | 2012-07-04 |
Family
ID=43073377
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010102159902A Active CN101887455B (en) | 2010-06-22 | 2010-06-22 | Method and system for managing multi-version report data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101887455B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103631764B (en) * | 2013-12-18 | 2016-09-14 | 用友网络科技股份有限公司 | Report design method based on extension mechanism |
| CN106021303B (en) * | 2016-05-05 | 2019-12-17 | 北京轻元科技有限公司 | system and method for continuously integrating report release |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1168026C (en) * | 2000-11-10 | 2004-09-22 | 思网科技股份有限公司 | Dynamic real-time data analyzing and processing system and method |
| US6785769B1 (en) * | 2001-08-04 | 2004-08-31 | Oracle International Corporation | Multi-version data caching |
| CN1477545A (en) * | 2002-08-19 | 2004-02-25 | 英业达股份有限公司 | Report automatic generatioin system and method |
-
2010
- 2010-06-22 CN CN2010102159902A patent/CN101887455B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN101887455A (en) | 2010-11-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104866599B (en) | The production method and system of Visual Report Forms | |
| US9590880B2 (en) | Dynamic collection analysis and reporting of telemetry data | |
| CN100451989C (en) | Software testing system and testing method | |
| US20120259812A1 (en) | Cooperative Naming for Configuration Items in a Distributed Configuration Management Database Environment | |
| EP2672397A1 (en) | Generating reports based on materialized view | |
| CN102096688A (en) | Method and device for generating data report | |
| CN108241529B (en) | Salary calculation method, application server and computer readable storage medium | |
| US20100205153A1 (en) | Data System Architecture to Analyze Distributed Data Sets | |
| CN109299074B (en) | Data verification method and system based on templated database view | |
| CN104113605A (en) | Enterprise cloud application development monitoring processing method | |
| CN109857649B (en) | Resource testing method and system | |
| Hammad et al. | Provenance as a service: A data-centric approach for real-time monitoring | |
| CN103577614A (en) | Data acquisition method and system oriented to SAP PI application integration platform | |
| CN111090803A (en) | Data processing method and device, electronic equipment and storage medium | |
| KR20160069978A (en) | Computer executable method of creating analysis data, apparatus performing the same and storage media storing the same | |
| CN101425070B (en) | Deadlock positioning method, deadlock positioning device and data system | |
| CN101887455B (en) | Method and system for managing multi-version report data | |
| US20130046866A1 (en) | Meter access management system | |
| CN111625532A (en) | Data blood relationship processing method and device, computer equipment and storage medium | |
| CN109117202A (en) | A kind of method and system that audit type configuration item is set | |
| US20150278739A1 (en) | Measuring utilisation of physical locations | |
| CN102331925A (en) | Fast software development platform | |
| CN103092617A (en) | High reliability workflow development method based on backup services | |
| US8869122B2 (en) | Extensible executable modeling | |
| CN109885472A (en) | Test and management method and system and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C56 | Change in the name or address of the patentee |
Owner name: YONYOU NETWORK TECHNOLOGY CO., LTD. Free format text: FORMER NAME: UFIDA SOFTWARE CO., LTD. |
|
| CP03 | Change of name, title or address |
Address after: 100094 Haidian District North Road, Beijing, No. 68 Patentee after: Yonyou Network Technology Co., Ltd. Address before: 100094 Beijing city Haidian District North Road No. 68, UFIDA Software Park Patentee before: UFIDA Software Co., Ltd. |