| Skriv ut Öppna PDF-version av onlinehjälpen

#### About Limitations in Analytics The limitations of reports are listed in the following sections. #### Description Text Limits The number of characters that can appear in the Description Extended field in a report is limited to a maximum of 1,999. However, in some cases, the limit is 1,000 characters. Oracle CRM On Demand determines how many characters can appear by calculating the number of bytes that are needed to store the first 1,999 characters of the text. Some characters require more than one byte of storage, for example, certain characters in the Chinese language. If the number of bytes required to store the first 1,999 characters is more than 4,000, then only the first 1,000 characters can appear. If the number of bytes required to store the first 1,999 characters is less than 4,000, then the first 1,999 characters can appear. For other Description fields, the maximum number of characters that can appear is also limited. The limit for these fields can be 255 characters, 1,000 characters, or 1,999 characters, depending on the field and the record type. #### Maximum Number of Records The maximum number of records that can appear is as follows: Table view. For this view, the maximum size for an analysis is 700,000 rows (maximum of 10,000 rows displayed at a time). If you attempt to display more than 700,000 rows, then Oracle CRM On Demand displays an error message about exceeding the maximum number of records. When downloading using the Excel, CSV, or Tab Delimited options under the Data export options, the maximum number of rows that can be downloaded is 700,000. When downloading using any other option (PDF, Excel, Powerpoint, or Web Archive (Mime HTML) under the Export options, or the XML option under the Data options), the maximum number of rows that can be downloaded is 65,000. 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 prompts, dashboard prompts, table view prompts, pivot table view prompts, and graph view prompts. #### Drop Target Limits The Layout pane in a view editor can contain one or more drop targets, depending on the view type. A drop target is an area where you place one or more columns to specify the position and purpose of the columns in the layout. The columns that you place in the Sections drop target divide a view into sections based on the different values in the columns. The following table shows the maximum number of sections that you can have for each type of view.
View Type | Maximum Number of Sections
--- | ---
Table | 1000
Graph | 25
Pivot Table | 1000
Treemap | 50
Simple Trellis | 10
Advanced Trellis | 25
#### Pivot Table View Limits The following limits apply to Pivot Table views: The maximum number of cells that can be displayed is 750,000. If this limit is exceeded at runtime, then an error message is displayed. In addition, the user who is running the analysis cannot export the results. The maximum number of records that can be returned by a query for processing is 40,000, and the maximum number of cells that can be populated is 150,000. If one or both of these limits are exceeded at runtime, then an error message is displayed. Depending on the option that was selected from the Data Viewing options in the Pivot Table properties, an error might be returned at runtime if a column that was added to the Columns drop target for the Pivot Table view returns more than 1,000 values. If the Content paging option was selected, then an error is returned and the user who is running the analysis cannot view or export the analysis. If the Fixed headers with scrolling content option was selected, then an error is not returned. The user who is running the analysis can scroll to view all of the content in the analysis. However, if the user wants to export the analysis, then the user must select one of the Data export options (Excel, CSV, Tab Delimited, or XML). If the user selects any other option, then the export file is empty. #### Catalog Page Display Limit The maximum number of objects that can be displayed in the Catalog page is 300, although more than this number of objects can exist in the catalog. If an object is not displayed on the Catalog page, then you can use the search functionality to find the object. In addition, you can save objects in folders and subfolders, to make the objects easier to locate. You can save all types of objects, including dashboards, in folders and subfolders. #### Time Limit for Query Execution Analytics 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 Analytics, 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 Real-Time Reporting subject areas and 180 minutes for Historical Analytics subject areas. For information on optimizing query execution time, see About Report Performance and Optimizing Performance. #### Multiselect Picklists In Historical Analytics subject areas, Analytics displays a multiselect picklist (MSP) field (up to 10 fields for each object) as a separate folder. Within these folders only the first 20 picklist values of the field and the concatenated MSP field value are available for reporting. Analytics supports the display of the concatenated MSP field values in the company’s default language. Analytics also displays two additional folders: Language Independent Code (LIC) folder: This folder exposes the MSP concatenated field values using the language independent codes (LIC) as stored internally in the database. Use these MSP values in filters for optimum performance. LIC folders are named with the object name and suffixed with the word (Code). For example, Account Multi-Select Picklist Fields (Code) and Activity Multi-Select Picklist Fields (Code). User Language folder: This folder exposes concatenated MSP field values in the user’s default language. User Language folders are named with the object name and suffixed with the words (User Language). For example, Account Multi-Select Picklist Fields (User Language) and Activity Multi-Select Picklist Fields (User Language). Multiselect picklist values are supported in the Historical Analytics and Real-time Reporting subject areas for the following objects: Account Activity Approver Asset Associated Contact Associated Opportunity Call Activity Campaign Contact Custom Object 01, 02 End Customer Event Final Approver Household Institution Invitees Last Approved By Lead Opportunity Opportunity Product Revenue Owned By User Primary Contact Product Quota Quote Sample Request Service Request Shared Address Solution User User Sign In History #### 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 The Book selector appears in the Reports and Dashboard pages and in reports embedded in record Homepages. You can use the Book selector to drill down into user books or custom books. If you have Full Visibility settings and are displaying an Historical Analytics subject area, you can exclude subordinates or subbooks in the respective book hierarchy by clearing the Include Sub-Items check box. The Book selector is not available for report previews. You cannot exclude sub-items from reports made from Real-time Reporting subject areas. You can clear the Include Sub-Items check box, but it has no effect on Real-time Reporting subject areas, it only affects Historical Analytics subject areas. NOTE: Several settings control your visibility to records in analytics. For more information, see About Visibility to Records in Analytics. #### 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 Analytics supports date analysis of metrics through the date dimension for 41 years (2000 to 2040) for companies using calendar-quarter or standard, fiscal-calendar models. For companies using custom fiscal calendar, Analytics can support date analysis of metrics only for the years defined in Oracle CRM On Demand. The exchange rate table supports only dates ranging from the year 2000 to the year 2040. If an analysis includes fields from more than one folder, then Oracle CRM On Demand might perform table joins that include the exchange rate table. In this situation, if a date is outside the range that is supported by the exchange rate table, then the record will be excluded from the results. Date dimensions are set up differently in Historical Analytics subject areas than in Real-time Reporting subject areas. In Historical Analytics 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 Real-time 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 Analytics 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 Real-time 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 Historical Analytics 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 Historical Analytics and Real-time Reporting subject areas.
Characteristic | Historical Analytics Subject Areas | Real-time Reporting Subject Areas
Date dimensions | One | One or multiple
Sets of metrics | One or multiple | One
#### 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 Real-time 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 Analytics. However, the user quota relation with the fiscal year in Analytics 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')) #### Custom Objects 01, 02, and 03 Associations You cannot report on the many-to-many associations between Custom Objects 01, 02, and 03 with the following objects in Analytics: Activities Assets Leads Products The many-to-many relationship is implemented only for Custom Objects 01, 02, and 03 and Account, Contact, Service Request, and Opportunity in Analytics. This many-to-many relationship is yet to be implemented between Custom Objects 01, 02, and 03 and Activities, Assets, Leads, and Products. However, you can report on the one-to-many relationship between these objects and Custom Objects 01, 02, and 03, using the Advanced Custom Objects real-time reporting subject area. You can display elements from the Activities dimension if you include an Activity metric in the report. #### Currency Conversion Limits If a currency value is entered using a currency that is not the company's default currency, then Analytics converts that value to the company's default currency for use in reports. Large values that are acceptable for input in one currency may exceed value limits when converted to the company default currency. When this occurs, the report generation cannot be completed. #### Related Topic About Custom Objects Reporting

Publicerat i Augusti 2022 | Copyright © 2005, 2022, Oracle och / eller dess dotterbolag. Legal Notices.