Siebel Reports Guide > Customizing Siebel CRM Reports > Specifying the Siebel CRM Data That Report Templates Use >

Reducing the Amount of Data That Integration Objects Transfer

The number of integration components and integration component fields that you add can degrade performance, particularly in a report that includes a large amount of data.

It is recommended that you review and configure all business components and integration components; this is to prevent unnecessary scripting execution during report generation. It is also recommended to include only the fields in an integration object that Siebel CRM requires to run the report. A large integration object increases the time that the XMLP Report server component requires to get data through the Siebel Enterprise Application Integration (EAI), and it increases the size of the XML that the Oracle BI Publisher Server uses to run the report. If a report template includes logic to get, aggregate, or reference elements in the XML, then a large integration object can also affect performance when Siebel CRM displays the report.

To reduce the amount of data that integration objects transfer

• Create a separate integration object for each report.

  Do not create a single, large integration object that multiple reports use.

• Deactivate every integration component field that the report does not require.

  If you use the EAI Siebel Wizard to create an integration object, then it adds all business component fields to the integration component. You must deactivate fields that the report does not require after the wizard finishes running.

• Do not flag all business component fields as Force Active. When a business field is flagged as Force Active, this loads the business component field during each query. If a minimal number of fields are flagged as Force Active, this improves performance.