Siebel Reports Administration Guide > Getting Started > Additional Siebel-Actuate Reporting Issues >

Migration of Non-Actuate Reports

Previously designed custom reports in other reporting applications than Actuate accessed data either using a ODBC data source or an external file that is populated when the user navigates to a specific view in Siebel eBusiness Applications. However, such data access is useful only with client-side reporting and can not be used while running server-based reports in the Web Client. Further, report generation and viewing through the Web browser is easier and more convenient with server-based reporting, particularly for business users running the applications in the Web Client from anywhere. Therefore, all custom reports designed in reporting applications other than in Actuate should be redesigned and implemented using this guide with Siebel Tools and Actuate e.Reporting Designer Professional.

While running reports in the Web Client, data access for reports is possible through a custom Siebel-Actuate integration layer from Siebel business objects layer. The same configured business object layer provides data to both the Siebel application user interface and to Siebel report generation processes. Therefore, the business logic built around the underlying tables can be reused consistently across all reports enhancing the access of context specific data, and eliminating the need for high-maintenance SQL queries or custom code. Accessing data from Siebel business objects also enables convenient migration of custom reports and ongoing administration of visibility rules.


 Siebel Reports Administration Guide 
 Published: 18 July 2003