Problems can Occur: Support Package Manager to Import Support Packages for ABAP components
Here one can see the information about problems that can occur when we use the Support Package Manager to import Support Packages for ABAP components. On the initial screen of the Support Package Manager, choose the 'i' button to find more information about the Support Package Manager.
1. SPAM/SAINT updates
When importing the SPAM/SAINT update, various runtime errors can occur:
These errors occur because the source code of the Support Package Manager is modified by the import during the run.
CALL_FUNCTION_PARM_UNKNOWN, LOAD_PROGRAM_LOST, LOAD_PROGRAM_CLASS_MISMATCH, and LOAD_TEXTPOOL_LOST occur, if the ABAP load or text elements are to be loaded back into the local buffer, and there is a different version in the database.
However, SAPSQL_SELECT_WA_TOO_SMALL, SAPSQL_SELECT_TAB_TOO_SMALL, SAPSQL_WA_TOO_SMALL, DDIC_STRUCLENG_INCONSISTENT and RUNT_ILLEGAL_SWITCH occur, if changes are made on the SPAM/SAINT data structures with the SPAM/SAINT update.
None of these errors occur again, if you restart the Support Package Manager (transaction SPAM) and continue to import the SPAM/SAINT update.
2. All Support Packages - problems during ABAP Dictionary activation
- Avoidance of ABAP Dictionary activation errors during import of SPs
To avoid ABAP Dictionary activation errors when you import Support Package queues (especially long queues), you must implement the corrections delivered in the following SAP before you import the queues:
1963049 "Duplicate LANG or Switch Framework entries in mass activation" Alternatively, check whether these have already been implemented as part of a Basis Support Package.
- Avoidance of errors for handling of cluster tables
In certain circumstances (cluster table enhanced by industry enhancement), an error can occur during the handling of cluster tables. This results in activation errors during the ABAP Dictionary activation.
See SAP 1861585 and implement the correction instructions specified in it before you import Support Packages.
3. All Support Packages - problems in transport tools "tp" and "R3trans"
4. All Support Packages - problems during modification adjustment
5.All Support Packages - other problems
SQL error 7 in the import step MOVE NAMETABS
In an SAP HANA database, errors can occur when importing Support Packages due to inconsistencies between the database representation of tables and its ABAP Dictionary description.
SQL-error "7-feature not supported: cannot modify type of column table to column" in DDL statement for ""
To avoid these errors, always ensure the consistency between the database and the ABAP Dictionary. To do this, use the report RSDU_TABLE-CONSISTENCY described in SAP s 1925089 and 1756099.
If you encounter this error when performing the import, contact SAP Support.
Error in "Move Nametabs" import step due to missing CDS views
When you import Support Packages, the "Move Nametabs" import step terminates (in the phase IMPORT_PROPER) because CDS views cannot be created in the database because other CDS views are missing.
You must reactivate the missing CDS views, thus creating them in the database again. To do so, use the correction report specified in SAP 2023690. You can then continue by importing the Support Packages.
SQL error SQL1754N on DB6/DB2 LUW
During the creation of database objects in the "Move Nametabs" import step, the SQL error SQL1754N occurs in the database system DB6/DB2 LUW.
To prevent this error, implement the corrections from SAP 2035350.
Avoidance of unnecessary activations of BC Sets
To prevent unnecessary activations of BC Sets in the Switch Framework when importing Support Packages, refer to the specifications of SAP 2035728.
6. Basis 7.40 Support Packages (component SAP_BASIS 740)
SAPKB74001 - SAPKB74004
If you have implemented SAP 1895691, errors can occur in the transport system (Workbench Organizer, STMS) during and after the import of Basis Support Packages.
This problem is prevented if Support Package SAPKB74005 is included in the Support Package queue.
If this is not possible, you must deimplement SAP 1895691 before importing the Support Package queue.
After importing the Basis Support Package SAPKB74004, it can happen with the modification adjustment of ABAP Dictionary objects (in transaction SPDD) that the system displays hints about the adjustment that contain no corrections of ABAP Dictionary objects at all.
Refer to SAP 1910464 and import these corrections. You can also import Basis Support Package SAPKB74005 to correct this problem.
SAPKB74004 - SAPKB74008
When you import Basis Support Packages SAPKB74004, SAPKB74005, SAPKB74006, SAPKB74007, and SAPKB74008, the process terminates in the XPRA phase PRGN_AFTER_IMP_SUSO_SAP_ALL. See SAP 2043600 for more information about the trigger conditions.
Refer to SAP 2043600 before importing the support package!
7. SAP_GWFND 7.40 Support Packages
8. SAP_UI 7.40 Support Packages
9. SAP_ABA 7.40 Support Packages
10. PI_BASIS 7.40 Support Packages
11. SAP_BW 7.40 Support Packages
12. SCM 7.13 Support Packages
Following the implementation of Support Package SAPKY71305 in a system on a database system DB6/DB2 LUW, inactive standard SAP planning object structures can exist in the system.
Refer to SAP 2037827 and perform the steps specified there.