Solution : https://service.sap.com/sap/support/notes/173814 (SAP Service marketplace login required)
Key words :
OCS, SPAM, PATCH, SPAM UPDATE, CONFLICT RESOLUTION TRANSPORT, SUPPORT PACKAGE, CRT, FCS FINAL DELTA PATCH, FFDP LOAD_PROGRAM_LOST, SAPSQL_SELECT_WA_TOO_SMALL, SAPSQL_WA_TOO_SMALL, TLSYHPG, CANNOT_CREATE_COFILE, TEST_IMPORT, SAPKU20B06, RSDBRUNT, RSSYSTDB, SAPLBTCH, BW SUPPORT PACKAGE, BSEGChange history- 27.07.2007: SAPKB46C55: It takes a very long time to refresh the TMS QA worklist.- 27.07.2007: SAPKE46CB9: Incorrect print screen when you print SAPscript forms- 28.07.2006: SAPKE46CB1: Serious error in German settlement (component PY-DE-NT-NI)- 17.02.2006: Generation error that can be ignored during a SPAM/SAINT update in a 4.6B system- 06.01.2006: When you use the downtime-minimized import mode, you must use a minimum of the R3trans version from December 06, 2005.- 14.10.2005: Do not use R3trans with patch number 2130 (Kernel Release 4.6D) to import Support Packages or transports!- 18.08.2005: Oracle DB: After you implement Note 864677, there is a risk of data loss when you import the Support Package. You must take into account Note 871846.- 29.06.2005: SAPKH46C49, SAPKH46C50: Serious problems when processing measurement documents after importing the Support Package- 29.06.2005: SAPKH46C49, SAPKH46C50 - Activation error for various data elements and tables (for example, FB_ICRC_CSTAT, FBICRC002A)- 12.05.2005: SAPKB46D40 - Serious error! All background jobs may be deleted. You must take into account Notes 715355 and 837691.- 12.05.2005: SAPKB46C50 - Serious error! All background jobs may be deleted. You must take into account Notes 715355 and 837691.- 19.07.2004: Termination of the 'Move Nametab' step (Batch job RDDMNTAB) with a kernel with patch level 1857-1864. Do not use this kernel to import Support Packages!- 19.07.2004: SAPKH46C47: Settlement rules are not created or copied- 19.07.2004: SAPKB46C33, SAPKB46C44 - Test import error with SAPKB46C44- 23.10.2003: SAPKE46B77 - Conflicts with Add-ons- 24.09.2003: Problems with supposedly obsolete notes in the modification adjustment (Note 640609)- 24.09.2003: SAPKA46C25, SAPKA46C29 - Test import error in SAPKA46C29- 25.07.2003: SAPKE46C70: Potential DDIC activation error in structure P05_SIM_PAR- 25.07.2003: SAPKE46C21, SAPKE46C32: Potential DDIC activation error- 19.05.2003: SAPKH46C35: DDIC activation error for tables with reference to DART- 19.05.2003: SAPKH46B37: DDIC activation error for tables with reference to DART- 17.04.2003: SAPKB46B51: Delete temporary variants in periodic batch jobs- 17.04.2003: SAPKB46C43: Delete temporary variants in periodic batch jobs- 17.04.2003: Incorrect display in SPAU and SPDD when using Oracle 8.1.7 (Note 604377)- 17.04.2003: SAPKE46C68, SAPKE46C69 - Test import error in SAPKE46C69- 21.03.2003: Texts deleted after importing Support Packages -> see Note 596982- 21.03.2003: SAPKE46C36, SAPKE46C59: Test import error in SAPKE46C59- 20.03.2003: SAPKB46C30: DDIC activation error when importing into an SAP APO 3.0A System- 20.03.2003: SAPKB46D09, SAPKB46D26: Test import error in SAPKB46D26- 11.03.2003: SAPKH46C38: Import error on Informix- 25.02.2003: Import error when using the 'downtime-minimized' import mode on Informix and DB2- 24.02.2003: SAPKH46C32, SAPKH46C36 - Activation error for J_1BNFCHECK- 14.02.2003: SAPKH46B34: Cost collectors posted to may have been deleted (RE-RT-SC) (Note 582106)- 14.02.2003: SAPKH46C26: Cost collectors posted to may have been deleted (RE-RT-SC) (Note 582106)- 14.02.2003: SAPKH46B49: Update termination and incorrect statistics after change to sales order (Notes 578797, 621605)- 14.02.2003: SAPKH46C40: Update termination and incorrect statistics after change to sales order (Notes 578797, 621605)- 23.01.2003: SAPKH46C39: Errors in various transactions after the import (see Note 578178)- 03.01.2003: SAPKB46C40: Required postprocessing work, if SAP DB or liveCache are used (Notes 545030, 588515)- 03.01.2003: SAPKB46D29: Required postprocessing work, if SAP DB or liveCache are used (Notes 545030, 588515)- 02.01.2003: SAPKE46C51, SAPKE46C61 - potential activation error for data element PC_B2A_BNDAT- 02.01.2003: SAPKH46B47: Important! Refer to Note 578964, if material ledgers (CO module) are used- 02.01.2003: SAPKH46C38: Important! Refer to Note 578964, if material ledgers (CO module) are used- 02.01.2003: SAPKH46C38: Conflicts with the PI add-on- 21.11.2002: SAPKH46C36: Danger of converting cluster table REGUP!- 15.11.2002: Problems when continuing the import after rc 0006 in step XPRA_EXECUTION- 06.11.2002: SAPKH46C34: Error when importing application-defined objects- 06.11.2002: objects SAPKH46B43: Error when importing application-defined objects- 06.11.2002: SPAM/SAINT Version 0029 - Version 0033: potential problems when implementing user exits- 04.10.2002: SAPKB46C29, SAPKB46C32 - Test import error in SAPKB46C32- 04.10.2002: SAPKB46D18, SAPKB46D21 - Test import error in SAPKB46D21- 02.10.2002: Incorrect method display in modification adjustment - applies to all 4.6x Releases and all Support Package types- 02.10.2002: SAPKB46B26, SAPKB46B42 - Test import error in SAPKB46B42- 21.08.2002: SAPKH46C35: Erroneous delivery of BSEG -> Danger of conversions and possible loss of data!- 21.08.2002: SAPKH46B44: Erroneous delivery of BSEG -> Danger of conversions and possible loss of data!- 05.06.2002: SAPKH46C30: Important postprocessing work in case of modified BSEG or BKPF- 15.05.2002: SAPKH46C30: Incorrect update of volatility data in Report RFTBFF20- 15.05.2002: SAPKH46B39: Incorrect update of volatility data in Report RFTBFF20- 26.04.2002: SAPKH46C23, SAPKH46C31 - Activation error in Table RFPDO1- 26.04.2002: SAPKH46B39, SAPKH46B40 - Activation error in Table RFPDO1- 14.03.2002: Critical error in SPDD at SPAM/SAINT Version 0029 and 0030- 07.03.2002: SAPKE46C36 - Import error due to original object- 28.02.2002: SAPKB46C19, SAPKB46C29 - Test import error in SAPKB46C29- 13.02.2002: SAPKA46C25, SAPKA46C28 - Test import error in SAPKA46C28- 04.02.2002: SAPKH46C29 - Change of IDoc type FIDCCP02- 04.02.2002: SAPKH46B38 - New IDoc type FIDCCP02- 31.01.2002: SAPKE46C31, SAPKE46C32, SAPKE46C40 - DDIC activation error for SAPKE46C31 or SAPKE46C32- 18.01.2002: Notes to be considered when importing BW Support Packages- 10.01.2002: SAPKH46C16, SAPKH46C27 - DDIC Activation error for SAPKH46C27- 05.12.2001: SAPKB46C22 - Deadlock during import and syntax error in SAPLBTCH- 20.11.2001: SAPKB46B33 - Work process terminates after importing SP- 20.11.2001: SAPKB46C25 - Work process terminates after importing SP- 20.11.2001: SAPKB46D14 - Work process terminates after importing SP- 19.11.2001: SAPKH46C16, SAPKH46C19 - DDIC activation error for SAPKH46C16- 28.06.2001: SAPKH46C19, SAPKH46C20 Activation error for BAPIPARNR3- 29.05.2001: SAPKH46B28 - missing correction of report RKEVRK2O- 23.05.2001: SAPKE46B20, SAPKE46B30 - Test import error with SAPKE46B30- 21.05.2001: SAPKH46C15 - Test import error: original object R3TRFUGXXM02- 15.05.2001: SAPKE46C11, SAPKE46C21 - Test import error with SAPKE46C21- 14.05.2001: Problem with the CRM Support Package Managers in BBPCRM 2.0C Systems- 14.05.2001: SAPKB46C15 - Incorrect conflicts with add-ons- 14.05.2001: SAPKA46C15, SAPKA46C16 - Test import error with SAPKA46C16- 14.05.2001: Postprocessing after 4.6A and 4.6B Support Package import on MS SQL Server- 09.02.2001: Change history created- 09.02.2001: SAPKE46C16 - Error-ridden conflicts with add-ons- 09.02.2001: SAPKB46A25, SAPKB46A26 - Problems with RSDBRUNT, RSSYSTDB- 09.02.2001: SAPKB46B17, SAPKB46B18 - Problems with RSDBRUNT, RSSYSTDB- 09.02.2001: SAPKB46C08, SAPKB46C09 - Problems with RSDBRUNT, RSSYSTDB- 09.02.2001: SAPKB46D03, SAPKB46D04 - Problems with RSDBRUNT, RSSYSTDB- 09.02.2001: General recommendation on V3 update entriesSAP recommendationWe strongly recommend that you always implement the latest version of the SPAM update before you apply any other Support Packages.It is also a good idea to download the latest versions of executables tp and R3trans from a sapserv# application server (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.If you are using several application servers, make sure that profile parameter rdisp/bufrefmode is set to sendon,exeauto, and if you are using only one application server, make sure that the profile parameter is set to sendoff,exeauto. In addition, the TPPARAM parameter buffreset should be set to TRUE. Otherwise, you only have the option of executing the "/$sync" command to make the Support Package changes become effective.Also note that individual Support Packages in this release can also refer to Support Packages of other software components. For example, a prerequisite for application package SAPKH46B02 is basis package SAPKB46B02. A Support Package queue with SAPKH46B02 can therefore not be created if SAPKB46B02 is not available as well. You can detect such dependencies by selecting the New Support Packages function in Transaction SPAM. The "2nd predecessor" column can be filled there for certain Packages. You can also refer to the following notes:310892 Import prereqs f.Support Packages in Basis Rel.4.6A310934 Import prereqs f.Support Packages in Basis Rel.4.6A310956 Import prereqs f.Support Packages in Basis Rel.4.6C329242 Import prereqs f.Support Packages in Basis Rel.4.6D
Related Notes :
| 958559 | Contribution statements cannot be sent by e-mail |
| 906008 | Missing method implementation after Support Package import |
| 888595 | R3trans deletes too much data during the import |
| 848399 | Measurement docs: Problems after you implement Note 806624 |
| 837691 | Background jobs are deleted in unintentionally |
| 737876 | Syntax error QPRUEFLOS_WRITE_DOCUMENT twice in SAPLQPLU |
| 733135 | Settlement rule is not created or copied / 1 |
| 715355 | BP_JOB_SELECT: Optimizing the job selection |
| 691879 | Importing add-on Support Package 08 for IS-PSADIN |
| 684564 | Re-importing a SPAM/SAINT update |
| 640609 | SPAU incorrectly displays note corrections as obsolete |
| 621605 | Duplicate records with delta extraction for SD documents |
| 620723 | DDIC_ACTIVATION aborted in P05_SIM_PAR |
| 615285 | DDIC activation errors during support package application |
| 615168 | Jobs with temporary variant terminate after Support Package |
| 604377 | SPAU/SPDD: Deleted objects are determined incorrectly |
| 600326 | IMPORT_PROPER phase terminates with RC=0234 |
| 599909 | User not set in Support Package leads to termination |
| 596982 | Texts are deleted by Support Package |
| 588515 | Authorizations for database access in MaxDB/liveCache CCMS |
| 578964 | Subcontractor order: Incorrect component posting |
| 573338 | Problems with the REGUP table when importing SAPKH46C36 |
| 572266 | XPRA execution return code 0006 with Support Package import |
| 556972 | FAQ OCS: Recommendations for error scenarios |
| 547773 | SPAU: interface method names are truncated |
| 547613 | BSEG: Error in SAPKH46C35 and SAPKH46B44 |
| 531948 | IS-OIL / IS-MINE: CRTs for APPL Support Package 31-33 |
| 525276 | User-defnd BSEG flds not trnsfrrd after SP 30 import for 46C |
| 520293 | RFTBFF20:Volatility data updated into incorrect tables !!! |
| 515957 | Activation errors for the RFPDO1 table (AD857) |
| 488627 | Test import has failed for SAPKE46C36 |
| 486344 | Double version creation of Support Packages |
| 484015 | Importing BW Support Package |
| 460434 | ConnTrans successful but no data transfer |
| 459938 | FI ALE: new IDoc type of FIDCCP02 and segment extensions |
| 448402 | DDIC activation error during upgrade: missing data elements |
| 444747 | List interactions cause work process to restart |
| 432027 | Strategy for using SAP Support Packages |
| 410485 | OCS: Import stops although no errors occurred |
| 402972 | Import of Support Package deactivates user exits |
| 402644 | Additional actions after Hot/Sup. packs import in MSSQL sys. |
| 393630 | Support Package 15: error DT358 in FC01BASE and FC01LMDLST |
| 379608 | Incorrect R3TR FUGS object breakdown in version management |
| 378658 | OBJECTS_OBJREF_NOT_ASSIGNED |
| 366945 | Problems while importing Support Packages/RSSYSTDB |
| 360334 | DATA INCONSISTENCY in exch. rates after SPs 16-19 |
| 354387 | Conflicts when importing ABA Support Package |
| 329242 | Import prerequisites for Support Packages in Basis Rel. 4.6D |
| 325157 | Various syntax errors in the business partner |
| 324351 | Problems with BBP/CRM 2.0B and BBP/CRM 2.0B SR1 |
| 322153 | SAPKB46B13: SQLD_DOWNLOAD_SE11 does not fit in SQLD |
| 320377 | Syntax error in program SAPLRHWS |
| 315054 | SAPKU20B01: Support Package 1 for BBP / CRM 2.0B |
| 313451 | Error during import of basis Support Package 3 |
| 310956 | Import prerequisites for Support Packages in Basis Rel. 4.6C |
| 310934 | Import prerequisites for Support Packages in Basis Rel. 4.6B |
| 310892 | Import prerequisites for Support Packages in Basis Rel. 4.6A |
| 308120 | IS-HT Rel 4.61 and R/3 4.6B Add On Support Packages |
| 307588 | Documentation R/3 (HR) Support Package in Rel. 4.6C |
| 307584 | Documentation R/3 Support Packages in Rel. 4.6C |
| 307581 | Documentation ABA Support Packages in Rel. 4.6C |
| 307579 | Documentation Basis Support Package in Rel. 4.6C |
| 305553 | CC-ERROR: Data loss (addresses) after Support Package |
| 217206 | Function modules: Processing in SPAU not possible |
| 204134 | Termination in SPAM/CLM_FUNC_NUMBER_CHECK_AND_RENA |
| 191012 | Nametab inconsistency after time stamp update |
| 169942 | Differences Release 4.6A FCS - 4.6A final version |
| 154351 | Known problems during lang. import of patch texts |
| 146458 | R3TRFUGXX ... original object must not be replaced |
| 119738 | Problems during upgrade with Support Packages |
| 97621 | OCS Info: Online Correction Support (OCS) |
| 97620 | OCS Info: Overview of Important OCS Notes |
| 19466 | Downloading SAP kernel patches |