SAP Basis Tech Supports

Symptom
This note provides information about problems that can occur when you 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.
Caution: This note is updated regularly. Therefore, always download the latest version from SAP Service Marketplace!
This note also concerns problems of components based on NetWeaver 7.0 Enhancement Package.
You may have to carry out a SPAM/SAINT update before you can import a certain Support Package. In turn, a SPAM/SAINT update may require a certain R3trans or tp version to be installed in your system. This note also tells you if a SPAM/SAINT update, R3trans or tp is required.
Note also that, due to the new Support Package stack concept, dependencies can be defined between the different Support Package types (for example, BW Support Package SAPKW70001 requires Basis and ABA Support Packages SAPKB70001 and SAPKA70001). For details about the Support Package stack concept and previously defined Support Package stacks, see SAP Service Marketplace under http://service.sap.com/sp-stacks.
Basis Support Packages may also require SAP kernels with a minimum patch level. Currently, the following interdependencies exist:
SAPKB70014: Kernel 7.00, patch number 133
Other terms
OCS, SPAM, SPAM/SAINT UPDATE, CONFLICT RESOLUTION TRANSPORT, SUPPORT PACKAGE, CRT, LOAD_PROGRAM_LOST, SAPSQL_SELECT_WA_TOO_SMALL, SAPSQL_WA_TOO_SMALL, XPRA_EXECUTION, TP_FAILURE, TESTIMPORT, DDIC ACTIVATION
Change history
- 16.12.2008: Error in the DDIC activation program – see Note 1283197
- 16.12.2008: SAPKB70014, SAPKB70016: Syntax error in the class CL_SFW_SYSTEM_SETTINGS
- 16.12.2008: Test import errors that you can ignore are no longer listed in this note because, as ofSPAM/SAINT Version 0032, the system recognizes and ignores these automatically during the import. As ofSAPM/SAINT Version 0032, if the system reports test import errors, youcannot ignorethese and youmustexamine them.
- 16.12.2008: Queue calculation with EA-HR Country Legal Change (CLC) packages
- 16.12.2008: SAPKE60035: DDIC activation error for table T5J73T
- 16.12.2008: SAPKE60037, SAPKE60403: Generation error in the phase ABAP_GENERATION
- 15.12.2008: SQL Server 2008 database: Import error if dbsl-lib- is obsolete 19.11.2008: SAPKB70017: Termination of phase XPRA_EXECUTION with return code 0012
- 19.11.2008: SAPKB70013: Transaction SFW5 does not check the Support Package level
- 19.09.2008: SAPKB70011 – SAPKB70016: Prior to implementing the Support Package, see Note 1249184.
- 19.09.2008: SAPKE60031: Long runtime when importing a Support Package.
- 19.09.2008: SPAM/SAINT Version 0029: TP_FAILURE 0212 in Phase IMPORT_OBJECT_LIST
- 18.07.2008: When you import SAP_BW Support Packages, the BI Content is no longer available.
- 18.07.2008: Implementation of Notes 1086728 and 1142128 to prevent problems in SPAU
- 18.08.2008: Database DB2/DB6: SQL error -107 in the phase IMPORT_PROPER
- 18.07.2008: Database DB2 for AS400: tp terminates after the main import.
- 18.07.2008: Long runtime of the import phase CLEAR_OLD_REPORTS
- 18.07.2008: SAPKE60016 – SAPKE60021: Duplicate key error during the import
- 18.07.2008: SAPKE60026: TrueType fonts were deleted.
- 03.03.2008: You cannot import Support Packages after you have imported ERP Enhancement Packages
- 03.03.2008: SAPKB70010 Termination in the phase AUTO_MOD_SPAU
- 03.03.2008: To avoid syntax errors in classes after SPAU, implement Note 970837.
- 03.03.2008: To avoid DDIC activation errors, implement the corrections contained in Notes 791984, 1015068, 1022755 and 1113868.
- 03.03.2008: SPAM/SAINT Version 0026: Long running background job when you import Support Packages
- 03.03.2008: General note about errors in the phase XPRA_EXECUTION
- 03.03.2008:DB2/DB6:SAPKB70012: Error during the step DDIC Distribution (tp-step “S”) due to the table DB6PMSQ_DB
- 03.03.2008: SAPK-60204INEAHR: Error in the phase DDIC_ACTIVATION
- 03.03.2008: SAPKGPHD26: Error when generating ABAP
- 03.03.2008: SAPKE60024, SAPKE60025: Test import error in SAPKE60025
- 03.03.2008: SAPK-60010INISM, SAPK-60011INISM: Test import error in SAPK-60011INISM
- 10.12.2007: SAPKB70013: In transaction SFW5, the system displays incorrect switch values for business functions.
- 10.12.2007: SAPKB70014 requires kernel 700 patch level 133.
- 29.11.2007: SAPKB70014: Administrative activities in the web service configuration must be carried out.
- 07.11.2007: A system termination and standstill occur when you import Support Package SAPKB70013 after having implemented Note 1023163 (see also HotNews 1112065).
- 27.10.2007: SAPKA70012: Important: The system overwrites all field modification settings for the business partner category.
- 27-10.2007: SAPK-60009INECCDIMP: Implement Note 1070942 after you import the Support Package to prevent payroll errors.
- 27.10.2007: SAPKW70013, SAPKW70014/SAPKW70015/SAPKW70016: Test import error in SAPKW70014/SAPKW70015/SAPKW70016
- 27.10.2007: SAPKB70009, SAPKB70012/SAPKB70014: Test import error in SAPKB70012/SAPKB70014
- 27.07.2007: On MSSQL Server systems: The import step for the table conversion (tp step “N”) terminates with the runtime error SAPSQL_SUBQUERY_ILL_TABLE_TYPE.
- 27.07.2007: To avoid DDIC activation errors, implement the corrections contained in Notes 791984, 1015068, 1022755 and 1113868.
- 27.07.2007: SAPKB70013: It takes a very long time to refresh the TMS QA worklist.
- 27.07.2007: SAPKE60013: Incorrect print screen when you print SAPscript forms
- 27.07.2007: SAPKB70012: MS SQL Server database: Error when executing backup jobs
- 27.07.2007: SAPKB70012: ABAP generation errors during import into a CRM system
- 27.07.2007: SAPKB70011: After the import, implement the corrections contained in Note 1037232.
- 27.07.2007: SAPK-60008INISPSCA, SAPK-60009INISPSCA: Test import error in SAPK-60009INISPSCA
- 27.07.2007: SAPKGPAD07, SAPKGPAD08: Test import error in SAPKGPAD08
- 27.07.2007: SAPKGPHD04, SAPKGPHD09: Test import error in SAPKGPHD09
- 16.01.2007: SAPKB70011: Termination in the IMPORT_PROPER phase after the main import has been successfully completed
- 16.01.2007: SAPK-60006INISOIL, SAPK-60007INISOIL: Test import error in SAPK-60007INISOIL
- 21.12.2006: SAPKE60009: It may take a long time to create new indexes for the PPOIX and PPOPX tables.
- 21.12.2006: SAPKB70006, SAPKB70010: Test import error in SAPKB70010
- 27.10.2006: SAPKB70002, SAPKB70005, SAPKB70006: Syntax error in the Note Assistant and modification adjustment after the import
- 27.10.2006: SAPKB70005, SAPKB70008: Test import error in SAPKW70006
- 06.09.2006: SAPKB70009: Incorrect delivery -> Use the corrected version of the Support Package!
- 06.09.2006: Termination when importing in downtime-minimized mode on MS SQL Server
- 28.07.2006: SAPKH60005: DDIC activation error that can be ignored
- 28.07.2006: SAPKGPFD03, SAPKGPFD05: Test import error in SAPKGPDD05
- 11.05.2006: Serious error in the CRM SP Manager
- 11.05.2006: After you import SAPKB70006, table conversions terminate.
- 11.05.2006: SAPKB70002, SAPKB70004: Errors you can ignore in DDIC activation
- 11.05.2006: SAPKITL412: Error in phase XPRA_EXECUTION
- 11.05.2006: SAPKGPDD02, SAPKGPDD04: Test import error in SAPKGPDD04
- 11.05.2006: SAPK-60004INISUT: Runtime of phase XPRA_EXECUTION may be longer
- 11.05.2006: SAR archives cannot be loaded and unpacked using the function “Load from front end”
- 11.05.2006: SAPCAR error: format error in header
- 17.02.2006: SAPKH60003: Error in phase XPRA_EXECUTION
- 17.02.2006: SAPKE60002: Import prerequisites corrected
- 17.02.2006: SAPKH60001, SAPKGPHD02: Test import error in SAPKGPHD02
- 09.01.2006: Only import Application Support Packages after you import SAPKB70005 completely
- 09.01.2006: SAPKW70004, SAPKW70007: Test import error in SAPKW70006 and SAPKW70007
- 04.01.2006: SAPKA70006 Error during the execution of the after-import methods
- 04.01.2006: When you use the downtime-minimized import mode, youmustuse a minimum of the R3trans version from December 06, 2005.
- 04.01.2006: SAPKB70004 – Error during the execution of the after-import methods, if Java VM containers are activated
- 04.01.2006: SAPKW70003 – Import error on MaxDB 7.6
- 18.08.2005:Oracle DB:After you implement Note 865198, there is a risk ofdata losswhen you import the Support Package.You must take into account Note 871846.
- 12.05.2005: SAPKB70001 – Serious error! All background jobs may be deleted.You must take into account Notes 715355 and 837691.
- 24.02.2005: Note was created again
SAP recommendation
We strongly recommend that you always import the latest version of the SPAM/SAINT update before you import any other Support Packages.
We recommend that you download the latest versions of the tp and R3trans executables from SAP Service Marketplace (see Note 19466).
V3 update entries:Process your V3 update entries before you import Support Packages. Otherwise, there is a risk that you will no longer be able to update the update entries if changes in the interface structures of the V3 update modules are delivered by Support Packages. As of SPAM/SAINT Version 0024, the Support Package Manager checks whether there are any open orders and you are then informed of this.
If you are using several application servers, make sure that profile parameterrdisp/bufrefmodeis set tosendon,exeauto, and if you are using only one application server, make sure that the profile parameter is set tosendoff,exeauto. Otherwise, you only have the option of executing the “/$sync” command to make the Support Package changes become effective.
Reason and Prerequisites
The problem is generally caused by a program error or the Support Package type.
Solution
1.SPAM/SAINT updates
Symptom: When you import the SPAM/SAINT update, a range of different runtime errors may occur:LOAD_PROGRAM_LOSTLOAD_TEXTPOOL_LOSTSAPSQL_SELECT_WA_TOO_SMALLSAPSQL_SELECT_TAB_TOO_SMALLSAPSQL_WA_TOO_SMALLDDIC_STRUCLENG_INCONSISTENTRUNT_ILLEGAL_SWITCH
These errors occur because the source code of the Support Package Manager is modified by the import during the run. LOAD_PROGRAM_LOST 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.
Solution: None of these errors will occur again if you restart the Support Package Manager (transaction SPAM) and continue to import the SPAM/SAINT update.SPAM/SAINT Version 0026:
Symptom: When you import Support Packages with SPAM/SAINT Version 0026, the system schedules an unnecessarily long background job (SAPRUPGM). If you import several Support Package queues in succession, deadlocks may occur that block all background processes.
Solution: Implement Notes 1132422 and 1138351 to ensure an optimized runtime of the background job SAPRUPGM and avoid deadlocks.SPAM/SAINT Version 0029
Symptom: The import terminates in the phase IMPORT_OBJECT_LIST and the system reports the following error:
TP_FAILURE, 0212, could not access file as supposed
Solution: Delete the current queue and implement the corrections contained in Note 1232804. You can then redefine the queue and implement it.2.All Support PackagesSerious error in the CRM SP Manager
In CRM systems, you must use the specialCRM SP Managerto import Support Packages, since it provides some necessary special functions.
If you have imported queues in test mode using the CRM SP Manager, you must close the CRM SP Manager and restart it before you import a Support Package queue in standard mode. This is the only way to ensure that important internal statuses are initialized properly and that the import is correct and complete. For detailed information about this problem, refer to Note 810081.Oracle DB: Risk of data loss after you implement Note 865198
If you have implemented the correction instructions from Note 865198, make sure to take into account Note 871846 before you import the Support Package and, where necessary, revise the correction as specified in the note.Otherwise, data may be lost when you import the Support Package.Downtime-minimized import only with R3trans from December 06, 2005 (or later)
The downtime-minimized import mode in the Support Package Manager may only be used with an R3trans version from December 06, 2005 (or later). If you use an older R3trans version, ABAP Object methods may not be imported correctly. Note 906008 describes this phenomenon and the symptoms that occur.
As of Version 0020, the Support Package Manager checks whether the minimum R3trans version exists.”SAPCAR error: format error in header” when extracting an SAR archive
Symptom: When you unpack an SAR archive, the SAPCAR utility terminates with the error message “SAPCAR error: format error in header”.
Reason: The SAR archive was packed using SAPCAR Version 700. Since changes were made to the SAR archive format in this version, older SAPCAR versions can no longer unpack the archive (also refer to SAP Note 892842).
Solution: Use SAPCAR Version 700 or SAPCAR Version 640 patch level 4. These versions can process the new archive format (refer to SAP Note 892842).SAR archives cannot be loaded and unpacked using the function “Load from front end”
Symptom: You want to unpack an SAR archive using the function “Load from front end”. The system refuses the archive with the message “File ‘???.SAR’ is not a CAR or SAPCAR file’.
Reason: The SAR archive was packed using SAPCAR Version 700. Since changes were made to the SAR archive format in this version, and the archive format versions were also changed, the Support Package Manager does not recognize the file as a valid SAR archive.
Solution: SPAM/SAINT Version 700/0021 contains an adjustment to the new SAR archive format.
If the new SPAM/SAINT version is not yet available, unpack the SAR archive at operating system level using the SAPCAR utility. Note that you may require a new SAPCAR version (refer to the problem described above, or to SAP Note 892842).Termination when importing in downtime-minimized mode on MS SQL Server
Symptom: The program may terminate in the IMPORT_PROPER phase when you import Support Packages using the downtime-minimized import mode:
Phase: IMPORT_PROPER
Reason for error : TP_FAILURE
Return code: 0234
Error message : uncaught error -> function err_exit called
Solution: The error is corrected with the 700 kernel patch level 75.
Update your system to at least patch level 75, and then start importing Support Packages.Avoiding DDIC activation errors when importing Support Packages
To avoid DDIC activation errors when you import Support Package queues (especially long queues), you must implement the following notes BEFORE you implement the corrections.
791984″Simultaneous activation of view append and appending view”
1015068″Deleting and recreating dictionary objects”
1022755″Language import and deletion of dictionary objects”
1113868″Activation error due to an object that does not exist”
Alternatively, check whether you have already implemented this notes as part of a Basis Support Package.An error in the DDIC activation program causes cluster tables to be converted.
Symptom: When you activate DDIC objects, information in runtime objects may be lost in certain circumstances. As a result, cluster tables are converted. This is incorrect.
Solution: See Note1283197and implement the correction instructions specified in it before you import Support Packages.Termination of table conversion (tp step “N”) on MSSQL systems
Symptom: When you import Support Packages on MSSQL Server systems, the import step for the table conversion (tp step “N”) terminates. The job log of the associated background job RDDGEN0L contains the runtime error SAPSQL_SUBQUERY_ILL_TABLE_TYPE.
Solution: To avoid the error, implement the corrections contained in Note 1042435 before you import the Support Package.
If you have already encountered the error, proceed as described in Note 1042435.Procedure for termination in the phase XPRA_EXECUTION
Symptom: The importing of Support Packages terminates in the phase XPRA_EXECUTION with return code 0012. In the related import log, you are referred to the job log of the XPRA job, in which runtime errors (for example, SYNTAX_ERROR) are listed as the cause of the termination.
Solution: It is possible that the errors are caused by note corrections that were implemented before you imported the Support Packages and that were partially deimplemented when you imported the Support Package queue. You can correct such problems by performing a modification adjustment and by implementing the notes that are still valid (yellow or green traffic light in SPAU) again. The modification adjustment is already prepared at this point and it can be called easily in the Support Package Manager by choosing the menu path ‘Extras’->’Modification Adjustment’.
To avoid such problems when you subsequently import in the production system, you can include the modification adjustment transports that were created in the development system in the Support Package queue. For more information, see the online documentation of the Support Package Manager (’i’ button).You cannot import Support Packages after you have imported ERP Enhancement Packages
Symptom: You can no longer import the Support Packages relating to product ERP 600 after you have imported ERP Enhancement Packages. When you try to define a Support Package queue, the system displays the following error message:
OCS package … does not match the current software component vector
Solution: Due to several software components being upgraded to a new version, enhanced import conditions are necessary for Support Packages. Notes 1118803 and 1119856 describe how you can easily load these enhanced import conditions into your systems.Syntax error in classes after the modification adjustment of notes
To avoid syntax errors in classes after the modification adjustment, it is essential that you implement Note 970837 before you import Support Packages.Changes that are contained in obsolete notes are completely removed.
Symptom: After you import Support Packages, changes to Web Dynpro objects and enhancement objects are removed when you perform the modification adjustment.
Solution: Before you import Support Packages, implement the corrections from Notes 1086728 and 1142128 in your system.
If you already are in the process of performing the modification adjustment and the system offers Web Dynpro objects or enhancement objects for removal, cancel this process and open a problem message under the component BC-UPG-NA.Database DB2/DB6: Termination with SQL error -107 in IMPORT_PROPER
As of SAP NetWeaver 7.0 SR3 (SAP_BASIS Support Package 14), you can install systems on DB2/DB6 with the options “Row Compression” and “Deferred Table Creation”. In systems that have been installed with these two options, you must implement the corrections that are contained in Note 1126127 before you import Support Packages. Otherwise, terminations may occur in the phase IMPORT_PROPER due to SQL error -107.Database BD2 for AS400: Termination of tp after the main import
Symptom: When you import Support Packages, tp terminates after the main import is successfully performed (phase IMPORT_PROPER).
Solution: Follow the instructions that are contained in Note 1173174, and install a tp with Version 372.04.36 or higher.Long runtime of the phase CLEAR_OLD_REPORTS
Symptom: When you use the downtime-minimized import mode, the phase CLEAR_OLD_REPORTS has a long runtime.
Solution: In transaction SE11, create a non-unique index (for the table REPOSRC) with the name SPM using the fields R3STATE and PROGNAME (in this sequence). This index is delivered with Basis Support Package SAPKB70016 by default (see Note 1137503).SQL Server 2008 database: Import error if dbsl-lib- is obsolete
Symptom: For more information, see Note 1260968.
Solution: To avoid import errors in SQL Server 2008, you must upgrade the status of dbsl-lib to at least the status described in Note 1152240 before you import Support Packages. Dbsl-lib is available on SAP Service Marketplace and has the description lib_dbsl_<patch>-<xxxxxx>.sar. Note 19466 contains information on downloading kernel patches.3.Basis Support Packages (SAP_BASIS component)SAPKB70001
Symptom: After you import Basis Support Package SAPKB70001, the background system administration tools selects background jobs incorrectly. As a result, background jobs may be deleted by mistake.
Solution: You must take into account SAP Notes 715355 and 837691.
To solve the problem, import Basis Support Package SAPKB70002 or implement the corrections from the latest version of Note 715355.SAPKB70004
Symptom: When you import Basis Support Package SAPKB70004, an error occurs in phase XPRA_EXECUTION. In the log of the after-import methods execution, you find:
Installation of configuration VMC_TEST_APP/CACHE (0) has failed
Installation of configuration VMC_TEST_APP/TEST (0) has failed
Errors occurred during post-handling SVMCRT_TRANS_JCFG_AFTER_IMP for
JCFG L
The errors affect the following components:
BC-VMC (Virtual Machine Container)
Solution: Ensure that you use a kernel with patch level 18 or higher. If the error also occurs with a current kernel, refer to SAP Note 871402.SAPKB70002 – SAPKB70004
Symptom: If you import Basis Support Packages SAPKB70002 and SAPKB70004 together in a single queue, the import process may terminate in the step DDIC_ACTIVATION.
The activation log displays:
Activate index SXMSMSGINDLOG-001 (DDIC/17.03.06/05:49)
Table SXMSMSGINDLOG is not active in the ABAP/4 Dictionary
Index SXMSMSGINDLOG-001 could not be activated
Solution: Continue with the process of importing the Support Package queue. When you repeat the DDIC activation, the error no longer occurs and the objects are activated correctly.SAPKB70002, SAPKB70005, SAPKB70006:
Symptom: After you import the Support Package mentioned, syntax errors occur in the Note Assistant and in the modification adjustment.
Reason: This problem only occurs if you implement the corrections from Note 948389 in Version 0003 (or lower) before the import. Support Packages SAPKB70002, SAPKB70005, and SAPKB70006 partly undo the corrections, which leads to syntax errors.
Solution: You can prevent the problem in different ways:
1. Import the Support Packages mentioned together with Support Package SAPKB70009 in a queue.
2. Note 948389 should be implemented at least in Version 0004. As of this version, the corrections that build on each other are compatible, so no syntax errors occur after you import Support Packages SAPKB70002, SAPKB70005, and SAPKB70006. For this reason, check, whether Note 948389 is already implemented in Version 0004 (or higher). If this is not the case, download the latest version with the Note Assistant and implement it.
If you have already encountered the error, you can correct it by importing Support Package SAPKB70009. If this is not possible, contact SAP Support. In this case, log a Support message under component BC-UPG-NA.SAPKB70006
Symptom: After you import Basis Support Package SAPKB70006, table conversions terminate. The syslog contains error messages for the runtime error TSV_TNEW_PAGE_ALLOC_FAILED.
Solution: Import Basis Support Package SAPKB70007 as soon as possible, or implement the correction from Note 917999 using Note Assistant.
If the error occurs during the table conversion process when you import a Support Package, you must manually implement the correction from Note 917999, since Note Assistant is locked at this point.SAPKB70005 – SAPKB70008:
Symptom: If you import Basis Support Packages SAPKB70005 and SAPKB70008 together in a queue, the TEST_IMPORT step returns an error for Support Package SAPKB70008. The following error message occurs in the test import log of SAPKB70008:
Function TREX_BUILD_COMP_DESCR (TREX_UTIL_EXT 02) does not fit
into the existing function group ((TREX_UTIL 23))
Function TREX_FILL_ATTRDEF_BY_TABNAME (TREX_UTIL_EXT 03) does not fit
into the existing function group ((TREX_UTIL 25))
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.SAPKB70009
Symptom: If you import Basis Support Package SAPKB70009 in the same queue as other Support Packages, or if you import further Support Packages after successfully importing SAPKB70009, the import may terminate in phase XPRA_EXECUTION with return code 0012. The after import method log records that the process terminated with a runtime error after the after import method SRM_FILL_KC_TABLES_AFTER_IMP was started for SRHL objects.
Reason: For a short time (September 02, 2006 – September 05, 2006), a version of SAPKB70009 was available, which contained an incorrect implementation of the after import method SRM_FILL_KC_TABLES_AFTER_IMP. This is indicated by the EPS file name CSN0120061532_0024341.PAT in the downloaded CAR archive.
Solution:Do not use the incorrect versions of Support Package SAPKB70009!A corrected version has been made available and this can be recognized by the CSN0120061532_0024352.PAT EPS file.
If you have already encountered the error, implement Note 967821 to correct the incorrect after import method SRM_FILL_KC_TABLES_AFTER_IMP. This correction is also available in Basis Support Package SAPKB70010.SAPKB70010
Symptom: The importing of Basis Support Package SAPKB70010 terminates in the phase AUTO_MOD_SPAU because a syntax error occurred in program SAPLSEOK (”Field ‘NOTE_ASSISTANT_MODE’ is unknown”).
Reason: This problem occurs only if you implemented Note 1011608 before importing the Support Packages, and Basis Support Package SAPKB70012 was not part of the queue.
Solution: To avoid the problem, it is essential that you import the Basis Support Packages SAPKB70010 and SAPKB70012 together in the same queue.
If you have already encountered the problem, use the version management of the version to restore the include LSEOKTOP before you import Support Package SAPKB70010. This repairs the syntax error and you can continue to import the queue.SAPKB70006 – SAPKB70010
Symptom: If you import Basis Support Packages SAPKB70006 and SAPKB70010 together in a queue, the TEST_IMPORT step returns an error for Support Package SAPKB70010. The following error message occurs in the test import log of SAPKB70010:
Function TREX_EXT_GET_TRACE_FILE_LIST (TREX_EXT_TRACE 03)
does not fit into the existing function group
((TREX_EXT_ADMINISTRATION)
Function TREX_RFC_GET_TRACE_FILE (TREX_RFC_TRACE 01)
does not fit into the existing function group
((TREX_RFC_ADMINISTRATION 23))
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.SAPKB70011
Symptom: When you import Support Package SAPKB70011, the Support Package Manager may terminate in the IMPORT_PRPOPER phase with the DBIF_RSQL_SQL_ERROR runtime error. At this time, the main import of the entire Support Package queue has already been completed. The long text of the short dump informs you that the SQL error occurred during the access to the TMSCSYS table.
Solution: Call the Support Package Manager again and continue importing the Support Package queue. The error is corrected after the automatic recompilation of the ABAP Coding that is affected by the changes to the TMSCSYS table.SAPKB70011
Symptom: After you import Support Package SAPKB70011, errors occur when you generate classes in the enhancement framework.
Solution: Implement the corrections contained in Note 1037232 or import Support Package SAPKB70012.SAPKB70009 – SAPKB70012
Symptom: If you import Basis Support Packages SAPKB70009 and SAPKB70012 together in a queue, the TEST_IMPORT step returns an error for Support Package SAPKB70012. The test import log of SAPKB70012 contains the following error message:
Function “MEREP_CASCADE_DELETE (MEREP_RUNTIME 42)” does not fit
into the existing function group “(MEREP_RUNTIME_MASS 02)”
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.SAPKB70010 – SAPKB70012 (SAPKB70014)
Symptom: If you import Basis Support Packages SAPKB70010 and SAPKB70012 together in a queue, the TEST_IMPORT step returns an error for Support Package SAPKB70012. The test import log of SAPKB70012 contains the following error message:
Function SPCPC_I_BUILD_DEVICE (SPCPCCLI 04) does not fit into
the existing function group ((SPCPC 19))
Function SPCPC_I_DELETE_DEVICE (SPCPCCLI 05) does not fit into
the existing function group ((SPCPC 20))
If the Support Package SAPKB70014 is also in the queue, the same test import error occurs there.
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.SAPKB70012
Symptom: After you import Support Package SAPKB70012, jobs that were scheduled using DB13 or DBACOCKPIT terminate on MSSQL Server systems and the system issues the following error message:
function … expects parameter ‘@dbList’, which was not
supplied.?[SQLSTATE 42000] (Error 201). The step failed.
Solution: After you import the Support Package, you must delete DB13 jobs and then recreate them. The exact procedure is described in Note 1057855.SAPKB70012
Symptom: If ABAP generation is activated when you import Support Packages, ABAP generation errors may occur when you import Support Package SAPKB70012 into a CRM system. In the generation log, you find the following error messages:
Program CRM_SE30_CMP, Include RSAT0F01: Syntax error in line 000085
Field ‘TIME_T_EVENT’ is unknown. It is neither in one of the
specified tables nor defined by a ‘DATA’ statement
Solution: This program is not used. Therefore, you can use ‘Extras’->’Ignore generation errors’ to ignore this generation error and continue the import.SAPKB70012 (only on DB2/DB6)
Symptom: The importing of Support Package SAPKB70012 terminates in the phase IMPORT_PROPER with an error in the tp step “S”. The related log DS<YY><MM><DD>.<SID> displays the following error message:
2EEDA300 No active nametab exists for “DB6PMSQ_DB”
This error can occur only on systems that run on a DB2/DB6 database.
Reason: Depending on the system history, the table DB6PMSQ_DB may exist on the database, but no reference exists in DDIC.
Solution: If you have already encountered the error, delete the table DB6PMSQ_DB on the database.
To avoid the error, check whether the table DB6PMSQ_DB exists on the database but not in DDIC (SE11) before you import the Support Package. If this is the case, delete the database table.SAPKB70013
Symptom: If you implemented the corrections from Note 1023163, a termination may occur and the system may become unusable when you import the Support Package SAPKB70013.
Reason: When you import the Support Package SAPKB70013, the corrections from Note 1023163 are partially undone. This causes such a large inconsistency that the system becomes unusable.
If you import the Support Packages SAPKB70013 and SAPKB70014 in a queue, this error does not occur because SAPKB70014 contains all of the corrections from Note 1023163.
Solution: Proceed as described in Note 1112065:Beforeyou import Support Package SAPKB70013, implement Note 1023163 once again.
If the error has already occurred, use the transport attached to Note 1112065 to return the system to a consistent state.SAPKB70013
Symptom: After you import Support Package SAPKB70013, it may take a very long time to refresh the TMS QA worklist in the Transport Management System (transaction STMS).
Solution: Proceed as described in Note 1019572.SAPKB70013
Symptom: After you import Support Package SAPKB70013, the system displays incorrect switch values for business functions in transaction SWF5. As a result, you have the option of activating incompatible business functions or of switching to an incompatible business function set.
Solution: Implement the corrections contained in Note 1082597 or import Basis Support Package SAPKB70014.SAPKB70013
Symptom: After importing the Support Package SAPKB70013, the system does not check the software-logistic requirements of the affected software components when you activate a business function set in transaction Sfw5. For this reason, software components may be activated even if these do not have the required Support Package level. This may result in errors in the affected applications.
Solution: Implement the corrections contained in Note 1144412 or import Basis Support Package SAPKB70016.
If you activated business function sets in the Basis Support Package levels 13 to 15 in transaction SFW5, check the Support Package levels of the affected software components (ECC-DIMP, FI-CA, FI-CAX, INSURANCE, IS-CWM, IS-H, IS-M, IS-OIL, IS-PS-CA, IS-UT) Support Package Manager. The levels must be the same as for component SAP_APPL. Import the missing Support Packages if required.SAPKB70014
Note the following: Support Package SAPKB70014 provides new functions in the areas web service runtime, web service configuration and web service monitoring. To use these new functions, you must carry out several administrative activities. More information is available at:
http://help.sap.com -> SAP NetWeaver -> SAP NetWeaver 7.0 (2004s) -> Support Package Stack 14 -> System Administration -> Technical Operations Manual -> Administration of SAP NetWeaver IT Scenarios -> Enabling Enterprise Services
The information is also available in the document attached to this note.SAPKB70011 – SAPKB70016
Symptom: After you import the Support Packages SAPKB70011, SAPKB70012, SAPKB70013, SAPKB70014, SAPKB70015, and SAPKB70016, syntax errors occur in the class CL_GUI_ALV_GRID because corrections from notes have been partially overwritten. This may cause important Basis functions (such as the background systems) to no longer work.
Solution: Before you import the specified Basis Support Packages, see the information in Note 1249184.SAPKB70014 – SAPKB70016
Symptom: If importing a queue with the Support Packages SAPKB70014 and SAPKB70016 terminates after the main import in the phase IMPORT_PROPER, a syntax error occurs in the class CL_SFW_SYSTEM_SETTINGS. As a result, you can no longer call the Support Package Manager or the Add-On Installation Tool and the import cannot be continued.
Solution: Implement the solution options contained in Note 1281321.SAPKB70017
Symptom: When importing a queue that contains the Support Package SAPKB70017, errors may occur in phase XPRA_EXECUTION during the after-import-method execution for other Support Packages also in the queue. The relevant AIM logs contain a note regarding the termination of the batch job and the job log for that batch job contains a SYNTAX_ERROR as cause for the termination. The corresponding “SYNTAX_ERROR” contains
“CONTEXT” addition is not permitted for BAdI
“CLS_CHARACTERIZATION”
as cause for the error, which can be traced back to an inactive change in the BAdI CLS_CHARACTERIZATION.
Solution: Continue the import. During the first run of XPRA_EXECUTION, the BAdI CLS_CHARACTERIZATION was activated, so that the syntax error no longer occurs during a repeat run.
To prevent this error from the start, import Support Package SAPKB70017 together with Support Package SAPKB70018 in one queue.
Recommended queues:
Based on the remarks above, we recommend the following Basis Support Package queues:
SAPKB70001 – SAPKB700.. (highest available Basis Support Package).
You can define shorter queues but you must pay attention to the split points.
These recommended queues only apply if you have not installed any add-ons or do not need to incorporate any CRTs into the queue. Otherwise, you need instructions on optimal or permitted queues from those people who produce the add-ons or CRTs used.4.ABA Support Packages (SAP_ABA component)SAPKA70006
Symptom: When you import Support Package SAPKA70006 into an SAP ERP system or an SAP SRM system, an error occurs in phase XPRA_EXECUTION. In the log of the after-import methods execution, you find:
Post-import method SDOK_CONTREP_AFTER_IMP started for SIRS L
Table BDSCONT22 for document contents does not exist
Post-processing necessary when upgrade has been completed
Depending on the system environment, tables other than table BDSCONT22 or other additional tables can be specified as non-existent.
Solution: This message is a serious warning that editing can also be carried out after the Support Package queue is imported. You can continue with the import.
After you carry out the import, refer to SAP Note 725845 and eliminate the inconsistencies in the Content Repository.SAPKA70012
Symptom: After you import Support Package SAPKA70012, the system overwrites all field modification settings for the business partner category or resets them to the standard SAP settings.
Solution: Note 1107216 describes the cause of the problem and a solution. Take the actions described in this notebeforeyou import the Support Package.
If you have any questions about this problem, create a problem message under the component CA-GTF-BDT.
Recommended queues:
Based on the previous comments, we recommend the following for ABA Support Package queues:
SAPKA70001 – SAPKA700.. (highest available Support Package ABA)
You can define shorter queues but you must pay attention to the split points.
These recommended queues only apply if you have not installed any add-ons or do not need to incorporate any CRTs into the queue. Otherwise, you need instructions on optimal or permitted queues from those people who produce the add-ons or CRTs used.5.BW Support Packages (component SAP_BW)All SAP_BW Support Packages
Symptom: After you import SAP_BW Support Packages, all transformations of SAP BI Content are no longer available.
Solution: Implement the corrections from Note 1171293.
If the problem has already occurred in your system, create a problem message under the component BW-WHM-DST-TRF.
Symptom: When you import BI_CONT Support Packages, a DDIC activation error occurs because the component type /BI0/OITCTLSTCHG is not yet active.
Solution: Follow the instructions that are contained in Note 1152612.SAPKW70003
Symptom: When you import BW Support Package SAPKW70003 into a system that runs on a MaxDB 7.6, a termination may occur in phase IMPORT_PROPER. In the import log, you find the following error message:
sap_dext called with msgnr 1: db call info
function: db_xrtab
fcode: RT_MODIFY
tabname: RSZWBTMPDATA
len (char): 46
key: 0ANALYSIS_PATTERN D000
retcode: 1
SQL error -602 accessing : POS(1) System error:
AK System error: VAK507 5
Solution: Refer to SAP Note 864482 and update the MaxDB to at least Version 7.6.0 Build 15. Then continue to import the Support Package.SAPKW70004 – SAPKW70006, SAPKW70007
Symptom: If you import the BW Support Packages SAPKW70004 and SAPKW70006 or SAPKW70007 together in a single queue, the TEST_IMPORT step returns an error for Support Packages SAPKW70006 and SAPKW70007. The test import log for SAPKW70006 and SAPKW70007 contains the following error message:
Function RSO_GET_MASTER_DATA (RSTC_EXTR 03) does not fit
into the existing function group ((RSO5 01))
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.SAPKW70013 – SAPKW70014 (SAPKW70015, SAPKW70016)
Symptom: If the BW Support Packages SAPKW70013 and SAPKW70014 are imported together in a queue, an error occurs in Support Package SAPKW70014 in the step TEST_IMPORT. The test import log of Support Package SAPKW70014 contains the following error message:
Function RSDDTREX_INDEX_CHECK (RSDDTREX_CHECK 01) does not fit
into the existing function group ((RSDDTREX 06))
If BW Support Package SAPKW70015 or SAPKW70016 is also in the queue, the same test import error occurs there.
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.
Recommended queues:
Based on the remarks above, we recommend the following for BW Support Package queues:
SAPKW70001 – SAPKW700.. (highest available BW Support Package)
You can define shorter queues but you must pay attention to the split points.
These recommended queues only apply if you have not installed any add-ons or do not need to incorporate any CRTs into the queue. Otherwise, you need instructions on optimal or permitted queues from those people who produce the add-ons or CRTs used.6.Solution Manager Support Packages (ST, ST-*)SAPKITL412
Symptom: The phase XPRA_EXECUTION terminates when you import Support Package SAPKITL412. The job log of the background job RDDEXECL lists the runtime error CONNE_IMPORT_CONVERSION_ERROR as the cause of the termination.
Solution: To solve the problem, proceed as described in SAP Note 925688.7.Application Support Packages (component SAP_APPL)
Symptom: Due to an error in the basis layer of the SAP NetWeaver AS ABAP before Basis Support Package SAPKB70005, when you import Support Packages, the add-on conflict verification may not find all conflicts with installed add-ons and activated Industry Extensions. In other words, in this case, the Support Package Manager does not make one-hundred-percent sure that all necessary CRTs are in the Support Package queue.
Solution: Completely Import Basis Support Package SAPKB70005 into your system before you import Application Support Packages. Only in this way can you be absolutely certain that the Support Package queue is complete.
If you have not installed any modifying add-ons and have not activated any of the delivered Industry Extensions either (for example, IS-OIL, IS-H, IS-M, ECC-DIMP, …), you do not need to divide the queue in this way.SAPKH60003
Symptom: When you import Support Package SAPKH60003, the importing process stops in the phase XPRA_EXECUTION. The after-import method log contains the return code 0006 and the following error message:
BAdI implementation FMFG_CCR_VEND_NO_ARC must still be
migrated
Post-processing necessary when upgrade has been completed
Migrate implementation FMFG_CCR_VEND_NO_ARC using
transaction SPAU
Solution: Continue the import, it will finish successfully.
If you use functions of the Application Extension EA-PS, import the EA-PS of Support Package SAPKGPPD03. This imports the adjustments necessary for BAdI migration. Even if you have not modified any SAP objects from the EA-PS environment, the system prompts you to adjust your modifications in the phase RUN_SPAU. However, the SPAU list is empty, since the migration has been carried out by importing the EA-PS Support Package. Simply confirm the processing of the modification adjustment, and continue with the import.
You can prevent the error occurring in the XPRA_EXECUTION, and RUN_SPAU from stopping by importing the Support Packages SAPKH60003 and SAPKGPPD03 together in a queue.
If you do not use the Application Extension EA-PS, you can ignore the above error, further action is not necessary in this case.SAPKH60005:
Symptom: An error occurs in the DDIC_ACTIVATION phase when you import Support Package SAPKH600005. The activation log contains the following error messages:
Check table EKKO does not exist or has no key fields
Table MERE_OUTTAB1_ME49 could not be activated
The system may refer to other tables (MERE_OUTTAB2_ME49, MMPURUI_PR_STY) as impossible to activate, rather than table MERE_OUTTAB1_ME49. The log specifies check table EKKO as the cause of the problem for all of these problems.
Solution: Start the import process and repeat the DDIC activation. The error does not recur when you repeat the DDIC activation.
Recommended queues:
Based on the remarks above, we recommend the following for Support Package queues:
SAPKH60001 – SAPKH600.. (highest available Support Package)
You can define shorter queues but you must pay attention to the split points.
These recommended queues only apply if you have not installed any add-ons or do not need to incorporate any CRTs into the queue. Otherwise, you need instructions on optimal or permitted queues from those people who produce the add-ons or CRTs used.8.HR Support Packages (component SAP_HR)SAPKE60002
Symptom: The import prerequisites for the first version of the HR Support Package SAPKE60002 (PAT-file CSN0120061532_0022565.PAT) were not correct. If you import this version of the Support Package together with the SAP_APPL of Support Package SAPKH60001 in a queue, an incorrect importing sequence may result.
Solution: The import prerequisites were corrected. You can recognize the new version of the Support Package by the PAT file name CSN0120061532_0022713.PAT. Only use this version!SAPKE60009
Problem: HR Support Package SAPKE50026 contains the new database indexes for the PPOIX and PPOPX tables. Since the tables may contain a large number of entries, depending upon the application environment, it can take the system a long time to create the indexes on the database during the import process.
Solution: See Note 1012176, and follow the instructions mentioned in that notebefore the import.SAPKE60013
Symptom: After you import HR Support Package SAPKE60013, SAPscript forms that have their own TrueType fonts are no longer printed correctly. Instead of the customer-defined font types, other font types are printed, but these are formatted incorrectly (for example, some letters overlap each other).
Solution: Proceed as described in Note 1030460.SAPKE60016 – SAPKE60021
Symptom: When you import Support Packages SAPKE60016 and SAPKE60021 in a queue, a duplicate key error occurs for the table T7DEPBSXXAWE0A during the import.
Solution: Note 1074030 describes this and other problems. You require an R3trans with release date 16.06.08 or later.SAPKE60024 – SAPKE60025
Symptom: If the Support Packages SAPKE60024 and SAPKE60025 are imported together in a queue, the TEST_IMPORT step returns an error for Support Package SAPKE60025. The test import log of SAPKE60025 displays the following error message:
Function HRCCE_EXT_EMP_ATTR_CE (HRCCE_BI_CE 02) does not correspond with
the existing function group ((HRCCE_CALENDAR_FUNCTIONS 05)).
This error message recurs for two other function modules of the function groups HRCCE_BI_CE and HRCCE_CALENDAR_FUNCTIONS.
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.SAPKE60026
Symptom: After you import the HR Support Package, the following error is displayed when you execute the report RPCP01Q0/RPCPSPQ0:
Font Family ‘Arial’ is not maintained
Font Family ‘Arial_B’ is not maintained
Solution: The TrueType fonts were deleted by the HR Support Package; for more information, see Note 1132685.SAPKE60031
Symptom: It takes a long time to import the Support Package SAPKE60031. The import process hangs in the phase AUTO_MOD_SPAU for a long time.
Solution: Before you import the Support Package, implement Note 1236444 or import the Support Packages SAPKE60031 and SAPKE60034 together in a queue.SAPKE60035
Symptom: When you import the HR Support Package SAPKE60035, the phase DDIC_ACTIVATION terminates with an activation error. The activation log displays:
Table T5J73T could not be activated.
(Error- T5J73T-RETMF: The assignment for the field SPRSL
does not exist in the search help H_T5J73)
Solution: To avoid the error, import the HR Support Packages SAPKE60035 and SAPKE60036 in a queue.
If you have already encountered the error, proceed as described in Note 1265242.SAPKE60037, SAPKE60403
Symptom: When you import the HR Support Package SAPKE60037 or SAPKE60403, if automatic ABAP generation or screen generation is active, the system issues the following message in the phase ABAP_GENERATION:
Program HMXCEDT0_CE, Include RPCEDD09_CE_MX: Syntax error
in line 000473 ‘XBT-IBAN’ has already been declared.
Solution: See Note 1279262.
Recommended queues:
Based on the remarks above, we recommend the following for Support Package queues:
SAPKE60002 – SAPKE600.. (highest available Support Package)
You can define shorter queues but you must pay attention to the split points.
These recommended queues only apply if you have not installed any add-ons or do not need to incorporate any CRTs into the queue. Otherwise, you need instructions on optimal or permitted queues from those people who produce the add-ons or CRTs used.9.Support Packages for Application Extension EA-APPLSAPKGPAD07 – SAPKGPAD08
Symptom: If you import Support Packages SAPKGPAD07 and SAPKGPAD08 together in a queue, the TEST_IMPORT step returns an error for Support Package SAPKGPAD08. The test import log for SAPKGPAD08 contains the following error message:
Function REIT_GUI_TC_BASE_POPUP (REIT_GUI_TC_BASE_POPUP 01) does not
fit into the existing function group ((REIT_GUI_TC_BASE 02))
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.
Recommended queues:
Based on the remarks above, we recommend the following for Support Package queues:
SAPKGPAD02 – SAPKGPAD.. (highest available Support Package)
You can define shorter queues but you must pay attention to the split points.
These recommended queues only apply if you have not installed any add-ons or do not need to incorporate any CRTs into the queue. Otherwise, you need instructions on optimal or permitted queues from those people who produce the add-ons or CRTs used.10.Support Packages for Application Extension EA-HR 600General note about EA_HR CLCs
Symptom: In the Support Package Manager, if you want to calculate a queue for an EA-HR CLC, the queue calculator may include the entire SAP_HR Support Package in the queue instead of just the required SAP_HR CLC.
Solution: See Note 1279090 for solution suggestions.SAPKH60001, SAPKGPHD02
Symptom: If you import the Support Packages SAPKH60001 and SAPKGPHD02 together in a queue, the TEST_IMPORT step returns an error for Support Package SAPKGPHD02. You can find the following error message in the test import log of SAPKGPHD02:
Function HRF_READ_ORG_UNIT (HRF_READ_STARS 10) does not fit
into the existing function group ((HRF_READ_DIMS 10))
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.SAPKGPHD04 – SAPKGPHD09
Symptom: If you import Support Packages SAPKGPHD04 and SAPKGPHD09 together in a queue, the TEST_IMPORT step returns an error for Support Package SAPKGPHD09. The test import log of SAPKGPHD09 contains the following error message:
Function HR_ASR_GS_FLD_NAME_EXIT (HRASR00VGS 02) does not
fit into the existing function group ((HRASR00FSCN_SH 08))
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.SAPKGPHD26:
Symptom: If you import Support Package SAPKGPHD26 in a system with SAP_BASIS Support Package Level 0014, a generation error occurs if the ABAP generation is activated:
Program CL_LSO_CRP_FKK_HISTORY========CP, Include CL_LSO_CRP_FKK_HISTORY========CM008: Syntax error in line 000037
Method ‘REFRESH_DISPLAY_HISTORY’ does not exist.
Solution: If you have already encountered the error, ignore it by choosing ‘Extras’->’ ‘Ignore generation errors” and continue importing. Then import Basis Support Package SAPKB70015 to correct the problem completely.
To avoid the error, import Basis Support Package SAPKB70015 in advance or together with EA-HR SP SAPKGPHD26.
Recommended queues:
Based on the remarks above, we recommend the following for Support Package queues:
SAPKGPHD02 – SAPKGPHD.. (highest available Support Package)
You can define shorter queues but you must pay attention to the split points.
These recommended queues only apply if you have not installed any add-ons or do not need to incorporate any CRTs into the queue. Otherwise, you need instructions on optimal or permitted queues from those people who produce the add-ons or CRTs used.11.Support Packages for Application Extension EA-HR 602, 603, 604General note about EA_HR CLCs
Symptom: In the Support Package Manager, if you want to calculate a queue for an EA-HR CLC, the queue calculator may include the entire SAP_HR Support Package in the queue instead of just the required SAP_HR CLC.
Solution: See Note 1279090 for solution suggestions.SAPK-60204INEAHR
Symptom: The importing of Support Package SAPK-60204INEAHR terminates in the phase DDIC_ACTIVATION. In the activation log, you find that the table T706S could not be activated because the field NO_TAX_CHAIN was defined twice.
Reason: This error occurs only if you imported EA-HR 600 Support Package SAPKGPHD25 before you upgraded the component EA-HR to Version 602.
Solution: You can avoid the error by importing Support Package SAPK-60204INEAHR together with the subsequent Support Package SAPK-60205INEAHR in a queue.
If you have already encountered the error, proceed as described in Note 1130693 to correct it.12.Support Packages for Application Extension EA-DFPSSAPKGPDD02, SAPKGPDD04
Symptom: If you import Support Packages SAPKGPDD02 and SAPKGPDD04 together in a single queue, the TEST_IMPORT step returns an error for Support Package SAPKGPDD04. The test import log for SAPKGPDD04 contains the following error message:
Function /ISDFPS/ME_PM_MNTREL (/ISDFPS/ME_CA_FE 10) does
not fit into the existing function group
((/ISDFPS/ME_PM_MNTREL 01))
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.
Recommended queues:
Based on the remarks above, we recommend the following for Support Package queues:
SAPKGPDD02 – SAPKGPDD.. (highest available Support Package)
You can define shorter queues but you must pay attention to the split points.
These recommended queues only apply if you have not installed any add-ons or do not need to incorporate any CRTs into the queue. Otherwise, you need instructions on optimal or permitted queues from those people who produce the add-ons or CRTs used.
13.Support Packages for Application Extension EA-DFPSSAPKGPFD03, SAPKGPFD05:
Symptom: If you import Support Packages SAPKGPFD03 and SAPKGPFD05 together in a single queue, the TEST_IMPORT step returns an error for Support Package SAPKGPFD05. You can find the following error message in the test import log of SAPKGPFDO5:
Function FTI_LDB_GET_SWAP_DETAILS (FTI_LDB_RAPI 01) does
not fit into the existing function group
((FTI_LDB_GET_OTC_DETAILS 01))
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.
Recommended queues:
Based on the remarks above, we recommend the following for Support Package queues:
SAPKGPFD02 – SAPKGPFD.. (highest available Support Package)
You can define shorter queues but you must pay attention to the split points.
These recommended queues only apply if you have not installed any add-ons or do not need to incorporate any CRTs into the queue. Otherwise, you need instructions on optimal or permitted queues from those people who produce the add-ons or CRTs used.14.Support Packages for Industry Extension IS-UTSAPK-60004INISUT
When you import the Support Package SAPK-60004INISUT, the system executes an XPRA, which may result in longer runtimes for the phase XPRA_EXECUTION. See Note 924885 for detailed information.15.Support Packages for Industry Extension IS-OILSAPK-60006INISOIL – SAPK-60007INISOIL
Symptom: If you import Support Packages SAPK-60006INISOIL and SAPK-60007INISOIL together in a queue, the TEST_IMPORT step returns an error for Support Package SAPK-60007INISOIL. The following error messages are displayed in the test import log:
Function OIUREP_GET_RECENT_ROYHIST (OIUREP_ROY_HISTORY 05)
does not fit into the existing function group.
(OIUREP_ROY_REPORTING 09)
Function OIUREP_GET_RECENT_VOLHIST (OIUREP_ROY_HISTORY 06)
does not fit into the existing function group.
(OIUREP_ROY_REPORTING 10)
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.
Recommended queues:
Based on the remarks above, we recommend the following for Support Package queues:
SAPK-60001INISOIL – SAPK-600..INISOIL (most recent available Support Package)
You can define shorter queues but you must pay attention to the split points.16.Support Packages for Industry extension IS-PS-CASAPK-60008INISPSCA, SAPK-60009INISPSCA
Symptom: If you import Support Packages SAPK-60008INISPSCA and SAPK-60009INISPSCA together in a queue, the TEST_IMPORT step returns an error for Support Package SAPK-60009INISPSCA. The following error messages are displayed in the test import log:
Function FMCA_EVENT_2611 (FMCA_INV_EVENTS 01) does not
fit into the existing function group ((FMCA_CH 13))
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.
Recommended queues:
Based on the remarks above, we recommend the following for Support Package queues:
SAPK-60001INISPSCA – SAPK-600..INISPSCA (latest available Support Package)
You can define shorter queues but you must pay attention to the split points.17.Support Packages for Industry extension ECC-DIMPSAPK-60009INECCDIMP
Symptom: The Support Package SAPK-60009INECCDIMP contains an error that may cause a payroll error if you activate the industry extension ECC-DIMP.
Solution: Implement the advance corrections from Note 1070942 or import Support Package SAPK-60011INECCDIMP.
Recommended queues:
Based on the remarks above, we recommend the following for Support Package queues:
SAPK-60001INECCDIMP – SAPK-600..INECCDIMP (latest available Support Package)
You can define shorter queues but you must pay attention to the split points.18.Support Packages for Industry extension IS-MSAPK-60010INISM – SAPK-60011INISM
Symptom: If you import Support Packages SAPK-60010INISM and SAPK-60011INISM together in a queue, the TEST_IMPORT step returns an error for Support Package SAPK-60011INISM. The following error message is displayed in the test import log:
Function ISM_BUP_CCARD_READ_MEMORY (JGBPCC_READ 03) does not fit
in the existing function group ((JF11 02))
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.19.Support Packages for other Application Extensions and Industry Extensions
No further problems are known, so we are not yet providing any recommendations for split points; maximum queues are allowed.