1. Designing with Reports for Oracle Enterprise Performance Management Cloud
  2. Differences between Reports and Reports Imported in Excel

C Differences between Reports and Reports Imported in Excel

This topic will help you understand the differences between Reports and Reports exported to, or imported into, Excel.

  • Report Designer enables you to define border formatting Styles using a combination of Border Style and Border Width properties. Border Style can be Solid, Dotted, Dashed, and Double. Border Width may take value 1 to 5. When imported in Excel, border styles are mapped as follows as Excel does not support different width settings:

    Reports Excel

    Solid, Width_1

    Thin

    Solid, Width_2

    Medium

    Solid, Width_3, Width_4, Width_5

    Thick

    Dotted, any width

    Dotted

    Dashed, Width_1

    Dashed

    Dashed, Width2, Width3, Width_4, Width5

    Medium_Dashed

    Double, any width

    Double

  • If a cell is defined with font color = Transparent, it cannot be supported in Excel. A workaround in Reports would be to use the 'Replace Text' property and set the replace text to an empty value.

  • Row banding is not supported when a report is imported to Excel.

  • Prefix/Suffix Alignment: % should not be combined with other characters or space. Such formatting may result in the numeric value appearing incorrect in Excel. When Prefix is aligned, Excel places the prefix character at the leftmost edge of the cell. Extra space may appear after positive numbers if a negative suffix is provided, the positive suffix is not provided, and align suffix is set.

  • If there are multiple grids in a report stacked vertically, with different column widths, then the column widths in Excel for the exported report are based on the column widths in the topmost grid in the report. As a result, the remaining grids may not line up the same or may have different column widths when compared to the report in the web. This is because, in Excel, column widths remain constant for all rows in a spreadsheet.

    Similarly, if there are multiple grids in a report arranged horizontally, with different row heights, then the row heights in Excel for the exported report are based on the row heights in the leftmost grid in the report. As a result, the remaining grids may not line up the same or may have different row heights when compared to the report on the web. This is because, in Excel, row heights remain constant for all columns in a spreadsheet.

  • When indention is specified in Cell Properties, the size of the indent is defined by the report designer in inches or centimeters, depending on the formatting user preference that is set (for example: "0.25" will indent "inch"). When the report is downloaded to Excel, the equivalent indent is attempted to be created in Excel. The indent in Excel is accomplished by calculating the width of a space character in the "standard font and font size"

    For more information, see Microsoft Troubleshooting page.

    The different ways of calculating the amount to indent may not be identical between Reports and Excel. This may result in the text in a cell wrapping in the Excel document when it was not wrapping in report preview (PDF or HTML). It may also result in the column width of the Excel document not being wide enough to display the values in the cells in that column, for example: Excel may show "#" for the cell values because the cell value is too large to display in the cell.