Print      Open PDF Version of Online Help

Reports > Getting Started with Answers (Custom Reports) > About Limitations in Reports

About Limitations in Reports

The limitations of reports are listed in the following sections.

Custom Objects Reporting

Oracle CRM On Demand Answers provides comprehensive support for reporting custom objects. You can report on Custom Objects 1, 2, and 3 and their many-to-many relationship with accounts, contacts, opportunities, and service requests through specially dedicated subject areas. Use the Advanced Custom Objects subject area to report the relationship between Custom Objects 4-15 and other prebuilt objects including Custom Objects 1, 2, and 3. However, custom object reporting is currently supported only in real-time subject areas. It is not available in historical subject areas.

Description Text Limits

The Description text fields limit how much text can be printed in a report:

• If the character set uses single-byte characters, the first 2,000 characters appear if the total byte size is less than 4,000.
• If the character set uses multibyte characters, the first 1,000 characters appear if the total byte size is more than 2,000.

Maximum Number of Rows

The maximum number of records can appear as follows:

• Table view. For this view the maximum number of records that can appear is 10,000. This number also controls the number of rows that can be downloaded. However, it supports up to 65,000 rows when downloading CSV files or text files.
• Pivot table view. For this view the maximum number of records that can appear is 20,000, and the maximum number of populated cells (rows multiplied by columns) is 200,000. Excluded and hidden columns are not considered in this limit.
• Drop-down lists. The maximum number of values that can show in drop-down lists is 1,000. This number includes the drop-down lists in filter conditions and report and dashboard prompts.

Time Limit for Query Execution

Oracle CRM On Demand Answers provides optimal performance for queries and reports while balancing the performance of Oracle CRM On Demand. To minimize the negative effect of long-running queries or run-away queries on the overall performance of Oracle CRM On Demand Answers, a time limit has been enabled for both real-time and historical reports. Queries that exceed the time limit generate a Timeout error message. For information about specific timeout limits that are applicable to your instance of Oracle CRM On Demand, contact Customer Care. For all instances, the maximum query time cannot exceed 10 minutes for Reporting (real-time) subject areas and 180 minutes for Analytics (historical) subject areas. For information on optimizing query execution time, see About Report Performance and Optimizing Performance.

Multiselect Picklists

Multiselect picklist (MSPs) values are not supported in real-time reporting subject areas. They are supported in the historical subject areas for the following subject areas:

• Account
• Activity
• Contact
• Dealer
• Lead
• Opportunity
• Service Request

Column Filter Prompt in Combined Analyses

Column filter prompts provide general filtering of a column within a request. However, this column filter prompt is not available in combined analysis requests.

Book Visibility

When you select a book from the Book Selector in a historical subject area, it shows the records included in both the book and its subbooks. It is not possible to exclude records contained in subbooks in historical subject areas. Whereas in real-time reporting subject areas, it shows only the records associated with the current book, not the records associated with the subbooks.

Exchange Rates

If your company has more than one active currency, your company administrator must set up exchange rates for each currency. Changes made to exchange rates appear in reports after the nightly refresh of analytics data. A single exchange rate is determined for each month, and all transactions within the month use that rate.

Some record types have multiple date fields. Only one date field is used to determine the month's exchange rate. For asset currency conversions, the Purchase Date field determines the month used. For an opportunity, the Opportunity Close Date that is closest to the Exchange Rate Effective Date is used.

Localization Settings

If you change your default language, the reporting elements display in the newly selected language. However, the data in reports or dashboards depends on your company's default language regardless of your chosen language.

Date Support

Oracle CRM On Demand Answers supports date analysis of metrics through the date dimension for 20 years (2000 to 2020) for companies using calendar-quarter or standard, fiscal-calendar models. For companies using custom fiscal calendar, Oracle CRM On Demand Answers can support date analysis of metrics only for the years defined in Oracle CRM On Demand. If a record is created outside this period, you can still display this record as long as it is not analyzed through the date dimension.

Date dimensions are set up differently in analytic (historical) subject areas than in reporting (real-time) subject areas. In analytic subject areas there is only one date dimension (standard or canonical), and there might be one or multiple sets of metrics using different dates, so these metrics can be reported by any date within the desire range. In reporting subject areas, there are one or multiple date dimensions (role-playing) and only a single set of metrics, so these metrics can be analyzed using different date dimensions.

For example, consider the Opportunity History analytic subject area, which contains one date dimension (Close Date) and two sets of metrics. The default set of metrics, Opportunity Metrics, is based on the Close Date, but there is also another set of metrics, Opportunity Metrics by Open Date, to allow analysis of opportunities by an open date. However, the Opportunities Reporting subject area contains two date dimensions: Date Opened and Close Date, and one set of metrics (Opportunity Metrics). The advantage of using the date dimension of the analytic subject area is that it allows analysis of various related metrics for the entire period using any date within the desire range in a single report.

The following table summarizes the set up of the date dimensions between analytic and reporting subject areas.

Time Support

Dates and times shown in reports are displayed in the company's time zone, so that everyone using the report can view consistent data. It is possible to display dates and times in the user's time zone (for Reporting subject areas only) if the company administrator has enabled the User Time Zone Support for Reporting Subject Areas field and if this field is selected in the user's profile. Changing this setting affects only reports that you display and does not affect reports that other users display. When sharing reports, the date and time information that you see might be different from the information that others see.

User Quotas

User quotas are available for reporting in the following subject areas: Activities, Activity History, Opportunities, Opportunity History, Opportunity-Products, and Opportunity-Product History. You must be familiar with the following considerations when reporting user quotas:

• User quotas are related to your fiscal calendar definitions. If your fiscal calendar year uses 12 periods starting every July 1, then so does the user quotas. In reports, the user quota year is determined by the final period in the fiscal year. For example, if your fiscal year ends on June 30, 2011, then the user quota year 2011 is from July 1, 2010 through June 30, 2011.
• If your company changes the fiscal calendar definition, then you must delete and recreate user quotas if the quarterly and yearly roll-up of quota values for users must match the user quotas for Oracle Contact On Demand and Oracle CRM On Demand Answers. However, the user quota relation with the fiscal year in Oracle CRM On Demand Answers is still based on the year in which the last period of the fiscal year ends.
• User quotas are defined for the quota name, date (month or higher), and user. They are not defined at the opportunity level. If you try to report quota metrics and opportunity metrics with the opportunity dimension field, you might encounter ODBC errors. You might also encounter ODBC errors when the user quota is reported at a level of the dimension object that is lower than the defined level or the available level. For example, user quotas are defined at the month level. If you try to report at the date level, you might encounter an ODBC error.
• User quota metrics are always generated using Manager visibility regardless of the user’s visibility. Hence, it is not possible for users who are not company administrators to report user quotas along with opportunity metrics when their visibility is set to Team visibility.
• You might experience ODBC errors if you report user quota metrics with a nonconforming dimension. For example, user quota metrics are not defined at the opportunity dimension in the Opportunity History subject area, and hence, you might experience ODBC errors if you tried to report user quota and opportunity metrics along with the opportunity dimension fields.
• If you define more than one quota for a given year, the user quota values shown in reports is an aggregation of all quota types for that year. You must use the filter by metric feature if you want the report to show user quota values of selected quota types for that year. For example, if Service Quota and License Quota are two quota types for the fiscal year 2009, and you want only Service Quota to be displayed in reports when reporting opportunity revenue, then use the following filter-metric formula on the user quota value column:

  FILTER("Quota Metric"."QUOTA VALUE" USING (Quota."QUOTA NAME" = 'Service Quota'))