Export:Fields from include w/ suffix are not exported Part 2
[dns suffix] [makefile suffix] [primary dns suffix] [suffix]
- Export:Fields from include w/ suffix are not exported Part 2Symptom During the export from the ABAP ALV, the system ignores fields (components), for example: customer enhancement fields from Customizing). Other terms Export: XML, XSLTReason and Prerequisites This problem is caused by...
Symptom
During the export from the ABAP ALV, the system ignores fields (components), for example: customer enhancement fields from Customizing).
Other terms
Export:
XML, XSLTReason and Prerequisites
This problem is caused by a program error.
This note triggers the aforementioned problem only in conjunction with Note 1142446. You must therefore change the internal structure also. We have recently added the node “ATTRIBUTES”, which is used in ABAP only. We introduced a new version (2.6) for this purpose. The previous FIELDS node is no longer used in the new version when exporting.
The performance improvements in the xslts were already implemented here.
Solution
SAP NetWeaver 6.40
Import Basis Support Package 23.SAP NetWeaver 7.00
Import Basis Support Package 16.SAP NetWeaver 7.10
Import Basis Support Package 7.
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, refer to 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 changes to be madebeforeimplementing the correction instructions:
1. Start the workbench (transaction SE80).2. Choose “Edit Object” and switch to “Continue”.3. Open the transformation SALV_BS_XMLSTRUC_TO_ALVXML in change mode.4. Replace the entire source code of the transformation with the relevant source code in this note (see suffix).5. Save and activate the change.
Start the workbench (transaction SE80).
6. Choose “Edit Object” and switch to “Continue”.7. Create the following new transformations in the relevant packages:
Name: SALV_BS_XMLSTRUC_TO_ALVXML_V26
Short description: salv_bs_alvxml_to_xmlstruc
Type: Simple transformation
Package: SALV_BS_EXPORT
Name: SALV_BS_XML_FOR_ODS_V26
Short description: Transformation to ODS (Open Document Format)
Type: XSLT program
Package: SALV_BS_COMMON
Name: SALV_BS_XML_FOR_OFFICE2003_V26
Short description: Transformation WDALV to StarOffice
Type: XSLT program
Package: SALV_BS_COMMON
Name: SALV_BS_XML_MHTML_V26
Short description: Transformation to O2K for WDALV without subtotals
Type: XSLT program
Package: SALV_BS_COMMON
8. Replace the entire source code of the transformations with the relevant source code in this note (see suffix).9. Save and activate the change.
10. Maintain selection text XML_V04 in the report(optional)
Call transaction SE38.
Enter BCALV_SET_USER_FLAGS.
Choose ‘Change’.
Choose ‘Goto’ -> ‘Text elements’ -> ‘Selection texts’.
Create XML_V04 with the text “XSLT/XML Version 2.6″.
Call transaction SE38.
Enter SALV_TEST_EXPORT.
Choose ‘Change’.
Choose ‘Goto’ -> ‘Text elements’ -> ‘Selection texts’.
Create P_VERS03 with the text “Version 2.5″.
Create P_VERS04 with the text “Version 2.6″.