Bookshelf Home | Contents | Index | Search | PDF

Planning an Upgrade to Siebel 7 > Planning an Upgrade > Assessing the Current Siebel Environment >

Reports Assessment

---

Use the guidelines in Table 5 to estimate the level of effort to migrate custom reports. Siebel standard reports are automatically migrated to Siebel 7 and do not need any changes.

Migration of custom reports includes validation of the fields used in a report, verification of access to the report from relevant views, regeneration of report metadata, and recompilation of the report executable in a new version of Actuate report designer.

The complexity of a custom report depends on the complexity of logic and report layout. Document your report customizations, and ask your report designer to review this information before migrating reports.

Table 5. Level of Effort for Custom Reports Migration

Effort	Number of Custom Reports	Complexity of Layout	Complexity of Logic	Person Days
Basic	Less than 5	Simple listing	None	Five
Low	5-10	Simple listing	None, totals	Five to 10
Medium	10-20	Master detail, cross tab	Rollup, totals, calculations	10 to 15
High	More than 20	Cross tabs, hierarchical, scripted/custom coded	Calculations, multi-currency, custom filters	More than 20

Person-day estimates in Table 5 assume that the report designer is familiar with Siebel technologies and is a trained user of Siebel Tools and Actuate report designers. Expect your report migration to take more time for complex layouts or complex reports that include custom methods on fields.

If you need to generate reports for analysis, conditional filtering, or aggregation on a large set of records (more than 500), consider using Siebel Analytics.

If your custom reports must be localized for a multilingual Siebel deployment, you need to perform additional steps. See Siebel Reports Administration Guide for instructions about how to migrate reports.

Bookshelf Home | Contents | Index | Search | PDF