SAP R/3 форум ABAP консультантов
Russian ABAP Developer's Club

Home - FAQ - Search - Memberlist - Usergroups - Profile - Log in to check your private messages - Register - Log in - English
Blogs - Weblogs News

ALV Export Excel: Recommendations and known errors

Post new topic   Reply to topic    Russian ABAP Developer's Club Forum Index -> OLE2, Excel, WinWord
View previous topic :: View next topic  
Author Message

Joined: 01 Sep 2007
Posts: 1639

PostPosted: Wed Oct 17, 2007 7:37 pm    Post subject: ALV Export Excel: Recommendations and known errors Reply with quote

Note 358644 - ALV Export Excel: Recommendations and known errors

Generally, the ALV supports three ways of connecting to Excel:

1. XXL interface:
Menu path: List->Export->Spreadsheet

ALV Grid class (cl_gui_alv_grid):
Toolbar: Export->Spreadsheet

2. Local file in spreadsheet format:
List->Export->Local file->Spreadsheet

ALV Grid class (cl_gui_alv_grid):
Toolbar: Export->Local file->Spreadsheet

3. Excel inplace as of Basis Release 4.6C
Menu path: Views --> Microsoft Excel STRL+SHIFT+F7

ALV Grid class (cl_gui_alv_grid):
Toolbar: Icon Views --> Excel Inplace

Note the following restrictions:

1. XXL interface
The date appears in the internal format (yyyymmdd) during a download to an Excel file in the ALV. By starting the Report again you can change to the external dislay across the system. You must have implemented Note 316814 for Basis Releases 4.5, 4.6B and 4.6C or imported the corresponding Support Package for the Note.
Currency fields are displayed exclusively with 2 decimal places in Excel.
Quantity fields are output with their original field definitions (for example, with three decimal places)
The system sorts or groups the columns together according to characteristics and key figures
The prerequisite for a correct grouping is that at least one characteristic column is displayed in the ALV Grid.

A filter entered in the ALV is not taken into account in Excel.
Rows are sorted differently in Excel.
If you are using conversion exits, refer to Note 764272.
For technical reasons, the Excel export provided in the ALV cannot support the functions mentioned above.

You must use the R/3 dialog box to exit the Excel window (see Note 329797) to ensure that the connection between SAP R/3 and Microsoft Excel is closed correctly. It is not possible to open multiple Excel windows.

2. Local file in spreadsheet format:
The system copies all features of the ALV display, regardless of ALV List, ALV Grid Fullscreen or ALV Grid class. This process includes:

Control break
Column arrangement
Conversion exits
Currency formats
You must import the file into a separate Excel Sheet by using Excel tools.

3. Excel inplace
As of 4. 6C, you can display data in the inplace in almost the same way as in the Grid for ALV Grid Fullscreen and ALV Grid class. However, certain preconditions (for example Excel Templates) must be fulfilled for you to do this. Refer to Note 305900; this gives you the optimal solution for the existing disadvantages of the XXL interface and information about how to download into a local file.

Different Excel worksheets are displayed:
Format: The formatted output of the table in Excel
Header: Format + HTML header data for the ALV Fullscreen
Pivot: Data in Pivot format (cross table)
Sub1 to Sub10: n-level output of subtotal lines
RawData: Raw data without formatting
RawHeader: Raw header without formatting
In the Excel print dialog, you can choose "Selected pages". Then the system only prints the Excel sheet currently displayed.
The Excel print preview and Excel save functions do not work because Excel is running in the inplace.
The HEADER sheet is filled only if the application has filled the HTML header of the ALV Fullscreen using the REUSE_ALV_COMMENTARY_WRITE service function module. If "free" HTML was generated using the object reference of a dynamic document, this header cannot be mapped in Excel.

The application can of course decide which ALV function is considered to be useful. To do this, it can hide certain functions.

Internal note:
Note especially that deep structures are not supported during the export, and that it may be necessary to hide the function codes for the export, Word, ABC analysis and spreadsheet.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Russian ABAP Developer's Club Forum Index -> OLE2, Excel, WinWord All times are GMT + 4 Hours
Page 1 of 1

Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum

All product names are trademarks of their respective companies. SAPNET.RU websites are in no way affiliated with SAP AG.
SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver and any other are registered trademarks of SAP AG.
Every effort is made to ensure content integrity. Use information on this site at your own risk.