Basis Errors and Solutions

Symptom

You configure a Web Dynpro ABAP ALV list and use cell variants for one or several columns. When you export to Excel, the system does not display the information that is displayed in the Web Dynpro ABAP ALV list for these columns.
ALV cannot export columns that contain cell-based information to Excel.
Implementing this note ensures that these columns are not exported to Excel.

Other terms
Web Dynpro ABAP ALVConfiguration model:
CellVariants, cell variantsExport:
XML, XSD
Reason and Prerequisites

This problem is caused by a program error.
Columns that contain cell variants are removed from ALVXML and are no longer exported to Excel.
Test:
Execute the Web Dynpro component SALV_WD_TEST_TABLE_CV. In the configuration table for cell variants, configure the following: In the cell variant column for the row CARRID, select the “TextView” (with constant) entry. In the cell variant field name column, select the “CellVariant” entry for the rows CONNID, FLDATE, and PRICE. Now export to Excel. The column CARRIS should be correct. CONNID, FLDATE, and PRICE should not exist and the system should issue three warning messages for these in the Web Dynpro application.

Solution
SAP NetWeaver 6.40
Import Basis Support Package 25.SAP NetWeaver 7.00
Import Basis Support Package 20.SAP NetWeaver 7.01
Import Basis Support Package 5.SAP NetWeaver 7.02
Import Basis Support Package 2.SAP NetWeaver 7.10
Import Basis Support Package 9.SAP NetWeaver 7.11
Import Basis Support Package 3.

Exception:
Certain applications, for example, SRM 6.0 Support Package 02 (Note 1048612), require a certain SAP NetWeaver Support Package. You must check for these prerequisites before you import the specified SAP NetWeaver Support Package.

In urgent cases, you can implement the correction instructions as an advance correction.
Before you do this, see Note 875986 for information about transaction SNOTE.
Before you implement the advance correction (if it is available and you want to implement it), see Note 875986. It contains current corrections that refer to the SAP Note Assistant and prevent problems during an import. After you implement the composite SAP Note, you must call transaction SNOTE again.

————————————————————————
|Manual Pre-Implement. |
————————————————————————
|VALID FOR |
|Software Component SAP_BASIS SAP Basis compo…|
| Release 700 SAPKB70016 – SAPKB70019 |
| Release 710 SAPKB71006 – SAPKB71008 |
| Release 711 SAPKB71101 – SAPKB71103 |
| Release 701 SAPKB70101 – SAPKB70104 |
| Release 702 Until SAPKB70201 |
————————————————————————
Caution: You have to perform this manual pre-implementation step manually and separately in each systembeforeyou import the Note to implement.
Call transaction SE91.
Enter the message class SALV_BS_MSG and choose “Change”.
On the “Messages” tab page, navigate to message number 201.
Enter the following message short text for message number 201: “Column ‘&1′ contains cell variants and cannot be exported.” and set the “Self-explanat’y” indicator.
Choose “Message class -> Save”.