Export a BO report to excel having more than 65500 rows

Post Author: noble
CA Forum: .NET
Please let me know what are the different options available to export BO report having more than 65500 rows to excel 2003.

Post Author: amr_foci
CA Forum: .NET
i think excel will not be able to handle all that records , you can devide your report into some tabs based on a specific condition for every tab, so when you export it to excel you will get many tabs as was exist in the the Business Objects report
good luck

Similar Messages

How to export or delivery report for Excel for more than one sheet in OBIEE

Hi Experts,
How to export or delivery report for Excel for more than one sheet in OBIEE 11g? (Every time, I can only see one sheet.)
Is it possibl to implement this requirement?
Thanks.

there are 2 oprions,
One is have your tow report in a single compound layout of analysis and keep the report in dashboard and give report links.
it will cath both your report.
Suppose your analysis are different.
Then you have the option of printing it to a PDF. on ritght top of Dashboard, Print - > Printable PDF.
you ca export to PDF no to excel.
mark if helps,
fiaz

Trouble with the SQL smt to :list tables having more than 1000 rows

Please I trying to list only tables having more than 1000 rows, but the sql stmt below doesn't work, can someone gives me a tips
select table_name from user_tables where table_name in ( select table_name from user_tables where rownum > 1000 ) : The result is no rows!
But I know that I have at lest 50 tables having more than 1000 rows
Thanks a lot for the help

If your tables are reasonably analyzed, then you can simply query:
SELECT table_name,
num_rows
FROM user_tables
WHERE num_rows >= 1000This will give you quite a reasonable estimate.
Otherwise you have to go for dynamic sql or use the data dictionary to help you generate suitable scripts ....

Can i create IN/UP/DE Trigger on a existing table having more than 2L rows

Hi All,
Can i create a INSERT/UPDATE/DELETE Trigger on a existing table having more than 2 lacs records ? if yes (is that works for only some kind of triggers? or for all ?). if not, tell me the reasons and limitations with guidelines.
Thanks in Advance.

Hi,
Sure; you can create new triggers for tables that already have rows. The type of trigger and the number of rows already in the table don't matter.
Try it. If the trigger works with a small table in your Development database, then there's no reason to expect it won't work on a larger table in your Production datbase.

Report More than 65000 rows

Hi Everyone,
I have a requirement to create report which will pull more than 65000 rows, I have added
<ResultRowLimit>95000</ResultRowLimit>
to instanceconfig file. Then I restarted the services and than ran the report. It is not pulling more than 65000 rows even now. Can you please let me know the procedure.
Thanks in Advance.

user12217794 also posted this (and has been told off) in the Java Swing forum
Populate more than 10000 rows in JTable returns Memory Exception
db

Can't export from ECC report to Excel 2010 with more than 65 K Rows

I see several posts about Excel 2007 and the 65K row limitation, but we are rolling out Office 2010 (Excel 2010) and find that it still will not allow download of more than 65,000 from an ECC report screen.
Excel 2010 is supposed to handle over a million rows, and user is receiving an error message that they can not do this.
Will SAP allow download to Excel 2010 of more than 65K rows?
Are there Excel settings, or GUI levels / settings we have to have ?
Ruth Jones

Details from the end User:
When you export line items from any detailed line item transaction in SAP that supports exporting to an excel format, SAP will only allow you to export 65K+ lines, equal to the number of line items that were available in the Excel 2003 format. If you have more than that many line, you have to download the file as u201Cunconverted.u201D While you can then open the u201Cunconvertedu201D file in excel, it is not properly formatted correctly, and may contain page headers and footers that need to be deleted. In Office 2007/2010, excel was extended to 1 million+ line items. When will SAP excel integration be upgraded to expand beyond the old 65K limit on number of exportable line items in excel format?
For example, transaction FBL3N is used to display line items in GL accounts. Line items are routinely exported for further analysis in Finance. GL accounts often have more than 65K line items. When you try to export these results to a spreadsheet format, you will get a message that the list is too large to be exported. However, if you select the unconverted format, you will be able to export the file. Here is an example: (Note that this is only one example with one transaction, there are many more SAP transactions that have this same issue.)
From the Menu, she if following the path List --> Export --> Spreadsheet
Receives the pop-up box entitiled: "Export List object to XXL", with words, "An XXL list object is exported with 71993 lines and 20 columns.   Choose a processing mode". Radio button choices of Table or Ptivot Table. She chose Table.
Then receives a message that (at the bttom of the page), List Object is too Large to be Exported.   Help says this is message PC020. But offers no further information.

How to export the dashboard reports for Excel in OBIEE 11.1.1.6.0?

Hi Experts,
How to export the dashboard reports for Excel in OBIEE 11.1.1.6.0?
For example:
Dashboard contains more than one report, and add one export button for downloading these reports for Excel.
Is it possible to implement this requirement?Thanks.

There is no direct option, you can try the following workaround.
Page Option -> Print -> Printable Html
Then File -> Save Page as
Choos Save as type as -> All files
File name as Report.xls
When you Open the xls file, if you get a pop up saying problem during load just omit it and proceed.
The report will open in excel.
Or save the page as html /mht and open it with Excel, this also will work.
Note: I have tested this in Mozilla
Thanks,
Vino

Not able to export web analysis report to excel smart view from workspace

Not able to export web analysis report to excel smart view from workspace.
Error :Web launch operation has been cancelled.
Can anyone help me to resolve this issues

I realized that I can put a block in WebI and then I can pull that in excel alongside of static header, after putting the question.
My interest to know whether it is by design in XI 3.0 or it is an issue. But by the replies it seems to me like it is by design.
@Anis: I can't go for header as part of Body. Because this report is viewed in Web by many other users. I can't have separate report for Live office, it is a restriction for me. If I use the header in body, it wont look good I guess.

Exporting a web report to Excel

Hi,
When I export a web report to Excel, it works fine. when I resave the same file as .xls file, the excel file size is reduced drastically (less than 1/10).
Why is this happening? Any way to reduce the file size in the first stage, that is down loading to Excel from web.
Thanks
Unni

Hi,
I don't understand what do you mean here. Do you mean we could not reduce size in the first time? We have exactly the same problem and the file size is about 20-40 MB. This size is too big to download by end user. It's excel file with .xls extension. When I open it by Excel and then try to Save As, it try to save as Web Page with *.htm extension. If I resave as a Excel Workbook format, the size is reduced to 3-4 MB. My question is the same as the other folk, how do I save it as Excel format with proper size the first time?
Thanks,
Yujun

ADF view, export excel does not export more than 65536 rows

as this is limitation of ms excel 2000, but not sure whether it is still limitation in using ADF view export excel feature.
in our table , there are more than 80k rows, when we click on export excel, it only get's 65536 rows
remaining rows are not exported.
please let us know if this is still open issue or fixed, also let us know which version if it is fixed.

Hi,
Yo have to use custom library Ex: Apachi POI
See
Re: ADF table data export to Excel

Export more than 70000 rows to excel in OBIEE 10G

Hi We are using
Office 2003 and need to export more than 70000 rows from OBIEE to excel.Is there any way?

Hi,
Refer the below link.
Re: Downloading / Exporting more than 65k records in Excel
Thanks,
Satya
Edited by: Satya Ranki Reddy on Apr 18, 2013 2:41 PM

Export from Discoverer to Excel more than 65K rows

Hi
I need to export data from discoverer to excel, in some cases it is more than 65K rows, does any body know if the file can be split in multiple files o worksheets in Excel?
Any help will be appreciate
Thanks
Vladimir

Russ
The short answer is I didn't know, as in any instance where my end users have wanted to extract large amounts of data they have done it from one sheet, I expected that Discoverer would just create the extra sheets for both but I wanted to know for sure, so I did a test.
I created a Disco workbook with two worksheets in it, the first one I called Monthly and it had 119,409 rows in it, the second I called Weekly and it had 299,775.
The first time I did the export I did it by hitting the Excel icon on the toolbar, it therefore only extracted the first worksheet (Monthly), when I opened the ensuing Excel file it had two worksheets in it, one called Monthly, the other called Monthly_1 and as expected, between the two sheets the had exactly the same number of fields as in the original disco sheet.
I then redid the extract going through the menu and chossing extract entire workbook, Discoverer then re-extracted the sheets. In the Excel file this time I had the same two monthly sheets as before and this time I also had weekly sheets, five of them. So I ended up with an Excel file with seven sheets containing all of the original data.
Cheers
Melanie

Can't insert more than 8000 rows to excel via JOB

Hello,
I have SSIS package where I have two tasks.
File System task copies file (with header names) to destination folder.
Data flow task export data from table to copied Excel file. Select are simple "select * from table" without any filters.
There are about 100 000 rows in the table.
When I run this task through Visual studio everything works fine. Data to Excel file is exported.
When I run this package in JOB (Job Activity Monitor) the file is created but 0 rows is exported.
One interesting thing, that when I use select "select top 7000 * from table" 7000 rows is inserted but when I try to export more than 8000 rows then 0 rows is exported. The JOB generates 0 errors. In fact he tries to export. Because all the time
Excel's file "Date modified" is changing.
It seems like data is exported but the final "commit" isn't done. Anybody knows where could be a problem?

Out of curiosity I have had a go at reading 70K lines of data from a table in a sql server and exporting them to an excel 2007 file:
SSIS 2012 project deployment
2 project connections: sql database connection for source
and an Excel 2007 connection for destination:
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=F:\Data\Outbox\ExcelOut.xlsx;Extended Properties="Excel 12.0 XML;HDR=YES";
I have an empty excel 2007 file as template with header rows in the first sheet.
I test the project in VS 2012, ran without problems.
I set DelayValidation to true on package level, data flow level.
In data flow, excel distination, ValidataExternal metadata to False.
I deploy the project with the package to an Integration Services catalog on a SQL 2012 server (not my development machine)
I copy an empty excel 2007 file (with the headers in the first row) in the correct file location.
I execute the package from SSMS in the Integration services catalogs, with 32 bit checked.
The package runs without errors.
I can open the excel file and see 70K records.
Last thought: I have no NULL values in my data. Do you have null values after the first 7000 records? Or is one of the excel columns expecting numerical data where it suddenly finds alfanumeric after 7000 rows?
Another suggestion: if you run the package with SSMS from the catalog, you can set the verbose reporting mode on, does that tell you anything more?
Jan D'Hondt - SQL server BI development

Syntax issue when having more than 20 warnings

Hello,
when having more than 20 warnings in a compilation unit (package, procedure ...),
SQL Developer ( version 1.5.0.53)
doesn't always flag an error (like, for example, a misspelled local variable),
so instead of a compile-time error a runtime error is generated.
I tried to reproduce the situation and here is a simplified case where i've
encountered the same error.
Best regards
Alexander Andris, Prague
[email protected]
CREATE OR REPLACE
PROCEDURE PROC AS
l_arg1 pls_integer;
l_arg2 pls_integer;
-- declarations which issue PLW-07204 warnings ...( 20 or more ...)
cursor c1 is
select sysdate from dual
where trunc (sysdate) = trunc(sysdate);
cursor c2 is
select sysdate from dual
where trunc (sysdate) = trunc(sysdate);
cursor c3 is
select sysdate from dual
where trunc (sysdate) = trunc(sysdate);
cursor c4 is
select sysdate from dual
where trunc (sysdate) = trunc(sysdate);
cursor c5 is
select sysdate from dual
where trunc (sysdate) = trunc(sysdate);
cursor c6 is
select sysdate from dual
where trunc (sysdate) = trunc(sysdate);
procedure proc1 is
begin
null;
end;
BEGIN
l_arg_notdef := 42;
-- next line would not be displayed.
dbms_output.put_line (
'Error in SQLDev 1.5.0 - error on the assignment line not flagged '
|| ' by the compiler when preceded by > 20 warnings ...' ||
' (Error not shown in navigator.Same behavior also in SQLDev 1.21 ...).');
-- So, when lines 5 - 23 are commented out then line 31 is flagged as an
-- error (PLS-00201), otherwise not (runtime error only).
-- When working on a large package with more than 20 warnings and a lot of
-- code, to find an error like a misspelled local variable one would need to
-- a different IDE.Hope it is not difficult to fix this quickly ...
-- Details:
-- client platform: Windows XP
-- SQLDev: Version 1.5.0.53 Build MAIN-53.38
-- db.: Oracle 10.2 on Windows
END PROC;

Unfortunately, that's the intended behaviour.
After complaining about errors not being reported in previous versions, they did add the "Only first 20 issues are reported" warning, but unless you know that can happen, almost nobody will notice.
I keep advocating for reporting errors on top, next any warnings, until having used up the 20 spaces. If necessary, they could compile first with warnings turned off, then again with warnings turned on.
I don't think I ever put a request for this on the SQL Developer Exchange, so take a look there if you're up for it.
Also mind you can turn the warnings off yourself inside the preferences, so they won't bother (nor help) you again.
Regards,
K.

Not uploading more than 150 rows from Excel file to Internal table.

Hi All,
We have a Z program to upload initial stock from excel file to SAP using BAPI. The problem is we have defined row to '65536'. But it is not uploading more than 150 rows at a time. The piece of code is given below.
DATA : it_excel LIKE alsmex_tabline OCCURS 0 WITH HEADER LINE.
DATA: xcel TYPE TABLE OF alsmex_tabline WITH HEADER LINE.
DATA : gd_scol   TYPE i VALUE '1',
       gd_srow   TYPE i VALUE '3',
       gd_ecol   TYPE i VALUE '256',
       gd_erow   TYPE i VALUE '65536'.
PERFORM upload_excel_file TABLES   gt_out
                              USING   p_file
                                      gd_scol
                                      gd_srow
                                      gd_ecol
                                      gd_erow.
FORM upload_excel_file TABLES   gt_out
                                   "Insert correct name for <...>
                        USING    p_p_file
                                 p_gd_scol
                                 p_gd_srow
                                 p_gd_ecol
                                 p_gd_erow.
DATA : lt_intern TYPE kcde_cells OCCURS 0 WITH HEADER LINE.
DATA : ld_index TYPE i.
FIELD-SYMBOLS: <fs> TYPE ANY.
CALL FUNCTION 'KCD_EXCEL_OLE_TO_INT_CONVERT'
    EXPORTING
      filename    = p_p_file
      i_begin_col = p_gd_scol
      i_begin_row = p_gd_srow
      i_end_col   = p_gd_ecol
      i_end_row   = p_gd_erow
    TABLES
      intern      = lt_intern[].
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF lt_intern[] IS INITIAL.
    FORMAT COLOR COL_BACKGROUND INTENSIFIED.
    WRITE:/ 'No Data Uploaded'.
    EXIT.
ELSE.
    SORT lt_intern BY row col.
    LOOP AT lt_intern.
      MOVE lt_intern-col TO ld_index.
      ASSIGN COMPONENT ld_index OF STRUCTURE gt_out TO <fs>.
      MOVE lt_intern-value TO <fs>.
      AT END OF row.
        APPEND gt_out.
        CLEAR gt_out.
      ENDAT.
    ENDLOOP.
ENDIF.
ENDFORM.
Plz tell me, what is the problem here. I want to upload all the rows at a time.
Thanks,
With regards,
Rosaline.

Hi Rob, I confirm, you're nitpicking! :-D For information, I've noted a few SAP comments about releasing and released objects, for people who like reading: [SAP Library - Documenting and Releasing a Function Module|http://help.sap.com/saphelp_nw70/helpdata/en/d1/801f50454211d189710000e8322d00/frameset.htm], [Note 109533 - Use of SAP function modules|https://service.sap.com/sap/support/notes/109533], [Note 415983 - Modification/customer developments of SAP function modules|https://service.sap.com/sap/support/notes/415983]; Example of an unreleased BAPI -> [Note 577453 - Using BAPI BAPI_DELIVERYPROCESSING_EXEC|https://service.sap.com/sap/support/notes/577453]
Sandra

Export a BO report to excel having more than 65500 rows

Similar Messages

Maybe you are looking for