Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
25Activity
0 of .
Results for:
No results containing your search query
P. 1
SAP Note 173814 OCS: Known Problems With Support Packages For

SAP Note 173814 OCS: Known Problems With Support Packages For

Ratings: (0)|Views: 5,725 |Likes:
Published by mbensa

More info:

Published by: mbensa on Dec 14, 2009
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

04/20/2013

pdf

text

original

 
01.12.2009Page 1 of 45
SAP Note 173814 -OCS: Known problems with SupportPackages for Release 4.6
 Note Language: EnglishVersion: 147 Validity:
Valid Since27.07.2007
Summary
Symptom 
This note provides information about problems that can occur when youimport Support Packages (formerly: Patches), such as Components SupportPackages (COP) or Conflict Resolution Transports (CRT).
Caution: This note is regularly updated to the latest status.Therefore always download the latest version from SAP Service Marketplace!
Under certain circumstances you must perform a SPAM update before you canimport a certain Support Package. A SPAM update sometimes requires that acertain R3trans or tp version is installed in your system. This note alsotells you when a new SPAM update, R3trans, or tp is required.Also note that due to the new Support Package Stack concept, dependenciesmay be defined between the various Support Package types (for example, R/3Support Package SAPKH46C46 requires the Basis as well as ABA SupportPackages SAPKB46C46 and SAPKA46C46). You will find details about theSupport Package stack concept and previously defined Support Package stackson SAP Service Marketplace at http://service.sap.com/sp-stacks.
 More Terms
OCS, SPAM, PATCH, SPAM UPDATE, CONFLICT RESOLUTION TRANSPORT, SUPPORTPACKAGE, 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, BSEG
Change history
- 27.07.2007: SAPKB46C55: It takes a very long time to refresh the TMS QAworklist.- 27.07.2007: SAPKE46CB9: Incorrect print screen when you print SAPscriptforms- 28.07.2006: SAPKE46CB1: Serious error in German settlement (componentPY-DE-NT-NI)- 17.02.2006: Generation error that can be ignored during a SPAM/SAINTupdate 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 (KernelRelease 4.6D) to import Support Packages or transports!
- 18.08.2005:
Oracle DB:
After you implement Note 864677, there is a riskof
data loss
when you import the Support Package.
You must take intoaccount Note 871846.
- 29.06.2005: SAPKH46C49, SAPKH46C50: Serious problems when processingmeasurement documents after importing the Support Package- 29.06.2005: SAPKH46C49, SAPKH46C50 - Activation error for various dataelements and tables (for example, FB_ICRC_CSTAT, FBICRC002A)- 12.05.2005: SAPKB46D40 - Serious error! All background jobs may be
 
01.12.2009Page 2 of 45
SAP Note 173814 -OCS: Known problems with SupportPackages for Release 4.6
deleted.
You must take into account Notes 715355 and 837691.
- 12.05.2005: SAPKB46C50 - Serious error! All background jobs may bedeleted.
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 toimport 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 modificationadjustment (Note 640609)- 24.09.2003: SAPKA46C25, SAPKA46C29 - Test import error in SAPKA46C29- 25.07.2003: SAPKE46C70: Potential DDIC activation error in structureP05_SIM_PAR- 25.07.2003: SAPKE46C21, SAPKE46C32: Potential DDIC activation error- 19.05.2003: SAPKH46C35: DDIC activation error for tables with referenceto DART- 19.05.2003: SAPKH46B37: DDIC activation error for tables with referenceto 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 Note596982- 21.03.2003: SAPKE46C36, SAPKE46C59: Test import error in SAPKE46C59- 20.03.2003: SAPKB46C30: DDIC activation error when importing into an SAPAPO 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 modeon 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 afterchange to sales order (Notes 578797, 621605)- 14.02.2003: SAPKH46C40: Update termination and incorrect statistics afterchange 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 orliveCache are used (Notes 545030, 588515)- 03.01.2003: SAPKB46D29: Required postprocessing work, if SAP DB orliveCache are used (Notes 545030, 588515)- 02.01.2003: SAPKE46C51, SAPKE46C61 - potential activation error for dataelement PC_B2A_BNDAT- 02.01.2003: SAPKH46B47:
Important!
Refer to Note 578964, if materialledgers (CO module) are used- 02.01.2003: SAPKH46C38:
Important!
Refer to Note 578964, if materialledgers (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 stepXPRA_EXECUTION
 
01.12.2009Page 3 of 45
SAP Note 173814 -OCS: Known problems with SupportPackages for Release 4.6
- 06.11.2002: SAPKH46C34: Error when importing application-defined objects- 06.11.2002: objects SAPKH46B43: Error when importing application-definedobjects- 06.11.2002: SPAM/SAINT Version 0029 - Version 0033: potential problemswhen 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 - appliesto 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 ofconversions and possible loss of data!- 21.08.2002: SAPKH46B44: Erroneous delivery of BSEG -> Danger ofconversions and possible loss of data!- 05.06.2002: SAPKH46C30: Important postprocessing work in case of modifiedBSEG or BKPF- 15.05.2002: SAPKH46C30: Incorrect update of volatility data in ReportRFTBFF20- 15.05.2002: SAPKH46B39: Incorrect update of volatility data in ReportRFTBFF20- 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 errorfor 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 inSAPLBTCH- 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.0CSystems- 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 onMS 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 entries

Activity (25)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
陳怡穎 liked this
Fermin Mendoza liked this
Barbro Johansson liked this
Singh 10 liked this
Mai Mèo liked this
Ítallo Alves liked this
Ihor Kuzil liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->