XXL Export with Excel 2016

[former_member250966]

I have run into an issue with a Windows 10 box with Office 2016 and Gui 7.40.  We are trying to export a report with 70,000 lines.   SAP is giving me an error that the results are too large to export.  I know the earlier Excel versions had a 65,000 line limit roughly.  I am trying to export as XXL.  A PC with win 7 and office 2013 works with Gui 7.4.

If I export as XXL with under the 65,000 limit it works fine on the Win 10 box as well.  It is just a hard limit somewhere inside of either SAP or Excel.  I have verified that we have the SAP note that expands the limit for Excel 2007 and later.

Has anyone run across this by chance?  I am trying to figure this out before it gets rolled out company wide.  Excel doesn't seem to be running in Compatability mode either.

Thanks,

Pat

[AntonFarenyk]

Hi Patrick,

If export through 08 XXL option gives error PC020 then I’d recommend instead of spreadsheet choose local file and then excel format. I have exact same set-up as described Win10/2016/7.40 and just tested with 200K lines with a hundred of columns and it worked well. It could be veeeery long depending on CPU and RAM of particular machine but still works.

Regards

Anton

[former_member250966]

By exporting to local file, is it going to keep the XXL formatting?  I can export to xlsx fine.  It is just when it is in XXL formatting greater than 65536 lines.

[AntonFarenyk]

Local file in just one option and it works differently depending on report (standard or custom, ALV or not). The answer to your question will be to try with your report in your system to see if it changes formatting.

Alternatively, please check OSS  2141355

Title: Error PC020 occurs when you try to download data into Excel
Link: https://launchpad.support.sap.com/#/notes/2141355/E

[former_member250966]

I was able to List - File - Save as Excel which then puts it into a XLS format.  Which is totally different than the XXL format if you right click - select all - Spreadsheet - XXL format.  The main issue I am having is if you get the report to greater than 65536 and then export to XXL it will error.  Less than that number it will not.  I can export it fine in Excel 2013.

[AntonFarenyk]

Have you tried to implement the OSS 2141355?

[former_member250966]

Correct.  That OSS refers to Note 1429326 which we have version 24 implemented.  It isn't the latest but it should have support for 2007 and later versions of Excel.  This shouldn't be the issue as Office 2013 is able to export greater than this number successfully.

[AntonFarenyk]

I don’t know what is the difference of 1429136 version 24 vs actual one. With new Launchpad it’s not obvious to compare correction instructions, moreover CI 1433555 is nowhere to be seen in the list of CI in this note.

However, FM XXL_FULL_API does check Excel version in the register and  sets MAX_ROW_XXL_LIMIT = 65536  for certain XL versions. Debug in this FM and it may get you to the problem.

CALL METHOD CL_GUI_FRONTEND_SERVICES=>REGISTRY_GET_VALUE
           EXPORTING
               ROOT  = CL_GUI_FRONTEND_SERVICES=>HKEY_CLASSES_ROOT
               KEY   = 'Excel.Application\CurVer'
               VALUE = ''
           IMPORTING
               REG_VALUE = REGISTRY_LOOKUP2.
       IF REGISTRY_LOOKUP2 NE SPACE.      " Excel 5 or higher installed
         IF REGISTRY_LOOKUP2 EQ 'Excel.Application.5' OR
            REGISTRY_LOOKUP2 EQ 'Excel.Application.6' OR
            REGISTRY_LOOKUP2 EQ 'Excel.Application.7'.
           backup = stat.
           stat = 'C'.
*         Y7AK032156 - Max Limit Change  -Add Start
           MAX_ROW_XXL_LIMIT = 16384.
         ELSE.
           MAX_ROW_XXL_LIMIT = 65536.
*         Y7AK032156 - Max Limit Change  -Add End

Another (much longer) option would be set break-point at command message, get to your message and move up in stack from there.