Integration of Database Reporting with ERP Systems

• US 20080086495A1
• Filed: 10/10/2006
• Published: 04/10/2008
• Est. Priority Date: 10/10/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kiziltunc, Mehmet Kerem, Andersen, Claus Busk, Christiansen, Lars-Bo, Lisovaya, Julia
• Granted Patent: US 8,380,742 B2
• Time in Patent Office: Days
• US Class Current: 707/102
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Increased reporting capabilities from a database system may be available in a customer relationship system while functionality of the customer relationship management system is maintained.

Claims

1. A method of a customer relationship management system using a database system to create a report comprising:

selecting to run a selected report,

creating a report object based on selected report;

reviewing metadata of the report object to determine whether a request form for a database system;

if the request form is not needed, creating the selected report;

if the request form is needed, creating the request form using the metadata of the report object for the database system;

selecting a filter for the selected report;

determining tables in the database system needed using the metadata of the report object;

executing the database query on the database system to obtain report results;

creating the selected report using the report results from the database query.

2. The method of claim 1, wherein creating a report object further comprises:

creating a layout description file;

creating a subclass that contains report specific variables and triggers; and

creating a report metadata file.

3. The method of claim 2, wherein the layout description file is report definition language client (“

RDLC”

) file.

4. The method of claim 2, wherein the metadata file is an XML file.

5. The method of claim 4, wherein the metadata file contains at least one selected from a group comprising:

a report name,

a report caption,

a report permission,

a transaction mode;

a data items used in the report; and

fields of each data item.

6. The method of claim 5, wherein the data items used in the report include table views and links between the data items.

7. The method of claim 2, wherein creating the subclass comprises using a code generator to change the application language to C#.

8. The method of claim 1, wherein data is accessed from the database using a request form.

9. The method of claim 1, further comprising using a reporting runtime program to take report metadata and a subclass to generate a report dataset.

10. A computer readable medium comprising computer executable code for creating reports in a customer relationship management system using a database system wherein the computer executable code comprises code for:

selecting to run a selected report,

creating a report object based on selected report;

reviewing metadata of the report object to determine whether a request form for a database system;

if the request form is not needed, creating the report;

if the request form is needed, creating the request form using the metadata of the report object for the database system;

selecting a filter for the selected report;

determining tables in the database system needed using the metadata of the report object;

executing the database query on the database system to obtain report results;

creating a report using the report results from the database query.

11. The computer readable medium of claim 10, wherein the computer executable code for creating a report object further comprises:

creating a layout description file;

creating a subclass that contains report specific variables and triggers; and

creating a report metadata file.

12. The computer readable medium of claim 11, wherein the layout description file is report definition language client (“

RDLC”

) file.

13. The computer readable medium of claim 11, wherein the metadata file is an XML file and the metadata file contains at least one selected from a group comprising:

a report name,

a report caption,

a report permission,

a transaction mode;

a data items used in the report; and

fields of each data item.

14. The computer readable medium of claim 11, wherein the data items used in the report include table views and links between the data items.

15. The computer readable medium of claim 11, wherein creating the subclass comprises using a code generator to change the application language in C#.

16. The computer readable medium of claim 11, further comprising using a reporting runtime program to take report metadata and a subclass to generate a report dataset.

20. The computer executable code of claim 18, readable medium of claim 11, wherein the metadata file is an XML file and the metadata file contains at least one selected from a group comprising:

a report name,

a report caption,

a report permission,

a transaction mode;

a data items used in the report; and

fields of each data item.

17. A computer system comprising a processor for executing computer executable code, a memory for storing computer executable code and an input output circuit for communicating computer executable code, the computer executable code comprising code for:

selecting to run a selected report,

creating a report object based on selected report;

reviewing metadata of the report object to determine whether a request form for a database system;

if the request form is not needed, creating the report;

if the request form is needed, creating the request form using the metadata of the report object for the database system;

selecting a filter for the selected report;

determining tables in the database system needed using the metadata of the report object;

executing the database query on the database system to obtain report results;

creating a report using the report results from the database query.

18. The computer executable code of claim 17, wherein the computer executable code for creating a report object further comprises:

creating a layout description file;

creating a subclass that contains report specific variables and triggers; and

creating a report metadata file.

19. The computer executable code of claim 18, wherein the layout description file is report definition language client (“

RDLC”

) file.