________________________________________________________________________
Number 672651
Version 25 vom 22.07.2005
Status Released for Customer
Set on ,22.07.2005
Language EN Caution: Translation Not
Current!
Mastersprache DE
Short text OCS: Known problems with Support
Packages in Basis
Rel.6.40
Responsible SAP AG
Component BC-UPG-OCS
Online Corr. Support
(Tools:Supp.-Pack.,
________________________________________________________________________
Long text
Symptom
This note
provides information about problems that may occur while you
import Support
Packages for ABAP components.
Caution: This
note is updated on a regular basis. You should therefore
always download
and read the latest version from the SAP Service
Marketplace.
Occasionally, you
may have to perform a SPAM/SAINT update before you can
import a certain
Support Package. The SPAM/SAINT update may in turn
require you to
install a specific R3trans or tp version in your system.
This note will
also tell you when you need to perform a SPAM/SAINT
update or import
a new R3trans or tp version.
You should also
bear in mind that dependencies may exist between various
Support Package
types due to our new Support Package stack concept (for
example, BW
Support Package SAPKW35001 requires Basis and ABA Support
Packages
SAPKB64001 and SAPKA64001). Refer to the SAP Service
Marketplace at
http://service.sap.com/sp-stacks for detailed information
about the Support
Package stack concept and the Support Package stacks
that we have
defined to date.
In addition, some
Basis Support Packages may require an SAP kernel with
a certain minimum
patch level. Currently there are no interdependencies.
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
-JUN.29.2005:
SAPKH50007: Serious problems when processing measurement
documents after
you import the Support Package.
- JUN.29.2005:
SAPKB64012, SAPKB64013: Duplicate key error during main
import (Table RSMPTEXTS)
- JUN.29.2005:
SAPKB64011: Creating new indexes for table CDHDR may take
too long.
- MAY.12.2005:
SAPKB64012 - Serious error! All background may be deleted
in certain cases!
You MUST refer to notes 715355 and 837691
- MAY.12.2005: Problems
with the buffer synchronization if you use a
6.40 kernel and
an IBM DB2 database (refer to note 841938)
- APR.06.2005:
SAPKB64011: Serious error in the Workbench Organizer
after the import
(see note 816523)
- APR/06/2005:
SAPKB64011: After you import the Basis SP, BSP services
are deactivated
in the Internet Communication Framework
- APR/06/2005:
SAPKW35011: Serious error and import termination when you
import into a
system on a DB2/DB4/DB6 or Informix database
- APR/06/2005:
SAPKB64001, SAPKB64010 - Test import error with
SAPKB64010
- MAR/10/2005: Do
not use R3trans with patch level 62 to import Support
Packages (as of
February 11, 2005)<Z1 Char>
- MAR/10/2005:
Runtime error ASSIGN_LENGTH_0 during DDIC activation -
note 743408
- MAR/10/2005:
SAPKB64004: Error in the after-import method execution
(AFTER_IMP_CHDO)
- NOV/29/2004:
SAPKB64001, SAPKB64009 - Test import error with
SAPKB64009
- NOV/04/2004:
SAPKGPHC03, SAPKGPHC02: DDIC activation error (see Note
780475)
- NOV/04/2004: SAPKGPAC02:
Errors that can be ignored in the DDIC
activation
- NOV/04/2004:
SAPKE50002 - requires the Support Packages #01 of all
software
components contained in the SAP ERP Central Component 5.0
- NOV/04/2004:
SAPKH50001, SAPKH50002 - test import error with
SAPKH50002
- NOV/04/2004:
SAPKB64004, SAPKB64009 - Test import error with
SAPKB64009
- NOV/04/2004:
Database error ORA-02168 on Oracle systems with activated
'Automatic
Segment Space Management (ASSM)'
- NOV/04/2004:
Basis Support Packages with systems on MS SQL Server:
Library
dbmssslib.dll should have the minimum patch level lib_dbsl_16
(Note 731265)
- JUL/14/2004:
Termination of the 'Move nametab' step (background job
RDDMNTAB) for a
kernel with patch <Z1 Char>level 22-23. Do NOT use this
kernel to import
Support Packages.<Z1 Char>
- JUL/14/2004:
SAPKA64003, SAPKA64004 - Test import error with
SAPKA64004
- JUL/14/2004:
SAPKA64004: Errors that can be ignored in the ABAP
generation
- JUN/23/2004:
SAPKH50001: Errors that can be ignored in the ABAP
generation
- JUN/23/2004:
SAPKGPAC01: Errors that can be ignored in the DDIC
activation
- JUN/09/2004:
SAPKB64003: Errors that can be ignored in the DDIC
activation of the
SXIVERIDT_EXTENSION table
- JUN/09/2004:
SPAM/SAINT Version 0015: Support Packages are missing in
the Support
Package browser
- MAY/14/2004:
SAPKB64001, SAPKB64002 - Test import error with
SAPKB64002
- APR/14/2004:
SAPKB64002: potential loss of customer-specific alert
classifications
- APR/05/2004:
Note initially released for customers
- OCT/20/2003:
Note created
SAP
recommendation
We recommend that
you always import the latest version of the SPAM/SAINT
update before
importing any other Support Packages.
In addition, you
should download the latest versions of the tp and
R3trans
executables from the SAP Service Marketplace (refer to Note
19466 for more
information).
V3 update
entries: Process all V3 update entries before importing
Support Packages.
Otherwise, you may no longer be able to update the
entries after the
import if changes to the interface structures of the
V3 update modules
were delivered with the Support Packages.
Ensure that the
rdisp/bufrefmode profile parameter is set to
sendon,exeauto if
you are working with several application servers, and
to
sendoff,exeauto if you are only working with one application server.
In addition, set
the buffreset TPPARAM parameter to TRUE. Otherwise, you
can only execute
the "/$sync" command to activate the Support Package
changes.
Reason and
Prerequisites
The problems are
usually caused by program errors or the Support Package
type.
Solution
1. SPAM/SAINT updates
o
Symptom: Various errors can occur while you are importing the
SPAM/SAINT update:
-
LOAD_PROGRAM_LOST
-
LOAD_TEXTPOOL_LOST
-
SAPSQL_SELECT_WA_TOO_SMALL
-
SAPSQL_SELECT_TAB_TOO_SMALL
-
SAPSQL_WA_TOO_SMALL
-
DDIC_STRUCLENG_INCONSISTENT
These errors occur because the source
code of the Support Package
manager is modified while you are
performing the import.
LOAD_PROGRAM_LOST and LOAD_TEXTPOOL_LOST
occur when the system
tries to load the ABAP load or text
elements back into the local
buffer but encounters a different
version in the database.
SAPSQL_SELECT_WA_TOO_SMALL,
SAPSQL_SELECT_TAB_TOO_SMALL,
SAPSQL_WA_TOO_SMALL, and
DDIC_STRUCLENG_INCONSISTENT occur if the
SPAM/SAINT update changes the SPAM/SAINT
data structures.
Solution: The errors are eliminated if you
restart the Support
Package Manager (Transaction SPAM) and
continue to import the
SPAM/SAINT update.
o
SPAM/SAINT Version 640/0015
Symptom: Not all the Support Packages
available in the system are
displayed in the Support Package browser
(for example, Support
Packages for the SAP_BW or PI_BASIS
component).
Solution: This is a simply a display
problem - the Support
Packages can be included and imported in
a Support Package queue
without problems.
The problem is solved in SPAM/SAINT
Version 640/0016.
2. All Support Packages
o
Termination of the 'Move nametab' step (background job RDDMNTAB)
Symptom: When you import Support
Packages with a kernel with
patch level 22 - 23, the "Move
nametabs" or "Activation of
inactive runtime objects" import
step terminates (in the
IMPORT_PROPER phase) with return code
0012. This error is fatal
when you are importing Basis Support
Package because the system
then has an inconsistent status.
Solution: Do not use a kernel with patch
level 22 - 23 to import
Support Packages. Install a kernel with patch level 24 or
higher!
If the corrected kernel is not yet
available, you have the
alternative option of setting the MAB=0
parameter in the
transportation tool configuration of the
Transport Management
System (Transaction STMS) to avoid the
error (see also Note
753627).
If you have already encountered the
error while importing Basis
Support Packages, this inconsistent
status can only be solved by
SAP Support. Open a message under the
BC-UPG-OCS component.
The problem is not quite as serious if
you are importing other
Support Packages and you can continue
the import in the Support
Package Manager. In this case, the
import is continued without
problems.
o
ORA-02168 on Oracle systems with activated 'Automatic Segment
Space Management (ASSM)'
Symptom: While importing Support
Packages, the system terminates
in the phase IMPORT_PROPER. The database
error, "ORA-02168:
invalid value reported for
FREELISTS" appears in the
corresponding log.
This problem occurs only in Oracle
systems with activated
'Automatic Segment Space Management
(ASSM)'.
Solution: To avoid the error, implement
the corrections described
in Note 627246 before importing the
Support Package.
If the error has already occurred,
correct the incorrect table
entries in the tables TATAF and
DDSTORAGE, as explained in
sections 2.a) and 2.b) of the note.
o Runtime
error ASSIGN_LENGTH_0 during DDIC activation
Symptom: If Japanese is set as the
system language, DDIC
activation may terminate with runtime
error ASSIGN_LENGTH_0 in
certain cases.
Solution: The problem is solved with
Basis Support Package
SAPKB64001. If the problem occurs while
you are import Support
Packages, follow the solution notes into
note 743408.
o
Problems with patch level R3trans 62 (as of February 11, 2005)
Symptom: If you use R3trans with patch
level 62 (see R3trans -v)
when importing Support Packages, the
import may terminate during
DDIC activation or during after import
methods execution. The
logs contain error messages of the
following type:
LANG DTEL * Object information could not
be imported
LANG TABL * Object information could not
be imported
or
Object "..." "..."
has not yet been imported successfully
Solution: Do not use the R3trans with
patch level 62 to import
Support Packages (as of February 11,
2005)!
If you have already encountered these
errors, it is no longer
sufficient to change the R3trans. In
this case, contact SAP
Support (component BC-UPG-OCS).
o Using a 6.40 kernel with a
database from the IBM DB2 family
Symptom: If you are using a 6.40 kernel
on a database from the
IBM DB2 family and you import Support
Packages, problems may
occur with the buffer synchronization in
certain cases.
Solution: Refer to note 841938 and use
only the kernel and
transport tool versions specified there.
3. Basis Support Packages (SAP_BASIS component)
o
All Basis Support Packages
Symptom: With systems on MS SQL Server,
the system may terminate
in the phase IMPORT_PROPER during the
main import (see Note
731265).
Solution: Use a DbSL (dbmssslib.dll)
with minimum patch level
lib_dbsl_16.
o
SAPKB64001 - SAPKB64002
Symptom: If you import Basis Support
Packages SAPKB64001 and
SAPKB64002 together in a queue, an error
occurs with Support
Package SAPKB64002 in the TEST_IMPORT
step. The following error
message appears in the test import log
of SAPKB64002:
Function SWW_WI_COMP_EVT_RECEIVE_INTERN
(SWW_SRV 10) cannot be
entered in the existing function group
((SWWA 61))
Transport the entire function group.
Solution: You can ignore this error by
choosing 'Extras'->'Ignore
test import errors'. This error no longer occurs during
subsequent imports.
o
SAPKB64001 - SAPKB64009
Symptom: If the Basis Support Packages,
SAPKB64001 and
SAPKB64009, are imported together into a
queue, an error occurs
in the TEST_IMPORT step in Support
Package SAPKB64009. In the
test import log for SAPKB64009, there
are the following error
messages:
Function ECATT_DISPLAY_DOM_OR_XSTRING
(ECATT_REUSE 02) cannot be
entered in the existing function group
((ECATT_WEBDYNPRO 03))
Function SWW_EI_EVENT_RECEIVE
(SWW_SRV 04) cannot be entered
in the existing function group ((SWWA
31))
Solution: You can ignore these errors using
the menu command
'Add-ons'->'Ignore test import
errors'. The errors will then not
occur in subsequent imports.
o
SAPKB64001 - SAPKB64010
Symptom: When Basis Support Packages
SAPKB64001 and SAPKB64010
are imported together in a queue, an
error occurs in the
SAPKB64009 Support Package in the
TEST_IMPORT step. You find the
following error messages in the test
import log of SAPKB64010:
Function SWW_WI_COMP_EVENT_RECEIVE
(SWW_SRV 08) cannot be
entered in the existing function group
((SWWA 32)) Function
SWW_WI_COMP_EVENT_RECEIVE_IBF (SWW_SRV
09) cannot be entered in
the existing function group ((SWWA 62))
Solution: You can ignore these errors
using the menu command
'Add-ons'->'Ignore test import
errors'. The errors will then not
occur in subsequent imports.
o
SAPKB64002
Problem: In Basis Support Package
SAPKB64002, the delivery class
of the SALRTCATC table that contains
alert classifications is
changed. As a result, customer-specific
alert classifications
that were already created in the system
on Basis Support Package
Version SP0 or SP1 may be overwritten by
classifications
delivered by SAP when you import
additional Support Packages.
Solution: Proceed as described in Note
727149.
If you have not created any
customer-specific alert
classifications on Basis Support Package
Versions SP1 and SP0, no
action is required.
o
SAPKB64003
Symptom: In rare cases, importing Basis
Support Package
SAPKB64003 may terminate in the
DDIC_ACTIVATION phase. The
following message appears in the
activation log:
Table SXIVERIDT_EXTENSION (active
version) was deleted.
(Please check references)
Reason: When you delete DDIC objects,
the DDIC activation program
carries out unnecessary checks (see Note
742219).
Solution: You can ignore these errors -
they no longer occur when
you run the DDIC activation program
again. Therefore, continue to
import the Support Package queue.
o
SAPKB64004
Symptom: When you import Basis Support
Package SAPKB64004, a
termination may occur in after-import
method execution when the
method AFTER_IMP_CHDO method is
executed. The following messages
appear in the log:
Character string TEST is already used
for object ...
R3TR CHDO SADOCATTR was not imported
Errors occurred during post-handling
AFTER_IMP_CHDO for CHDO L
AFTER_IMP_CHDO belongs to package SZD.
The errors affect the
following components: BC-SRV-ASF-CHD
(Change Documents)
Solution: A general solution is available
in Basis Support
Package SAPKB64010 (see note 763795). To
avoid this error, Basis
Support Packages SAPKB64004 and
SAPKB64010 should be imported in
a queue.
If you have already encountered these
errors, contact SAP Support
(component BC-SRV-ASF-CHD).
o
SAPKB64004 - SAPKB64009
Symptom: If you import the Basis Support
Packages SAPKB64004 and
SAPKB64009 together in a queue, an error
occurs in Support
Package SAPKB64009 in the step
TEST_IMPORT. The following error
message appears in the test import log
of SAPKB64009:
Function CCMSBI_COLLECT_LOCAL_MTE_DATA
(SCSM_BI_UTIL_FUNCTIONS
01) cannot be entered in the existing
function group
((SCCMSBI_UTIL_FUNCTIONS 01))
This error is repeated for 3 more
function modules from the
specified function groups.
Solution: You can ignore these errors
using the menu command
'Add-ons'->'Ignore test import
errors'. The errors will then not
occur in subsequent imports.
o
SAPKB64011
Symptom: After you import Basis Support
Package SAPKB64011,
services are deactivated in the Internet
Communication Framework.
During the access, the "HTTP
403" error appears with the error
text "Forbidden" or
"Service is not active".
The deactivation is a safety measure,
because new BSP nodes were
delivered with the Basis Support
Package.
Solution: Activate the services you need
as described in note
517484.
o
SAPKB64011
Symptom: After you import Basis Support
Package SAPKB64011,
serious problems can arise in the
Workbench Organizer (see note
816523).
Solution: Apply the solution from note
816523 or import Basis
Support Package SAPKB64012. To avoid the
error, import Basis
Support Packages SAPKB64011 and
SAPKB64012 together in a queue.
o
SAPKB64011
Problem: Basis Support Package
SAPKB64011 contains the new
database bank indexes for table CDHDR.
Since the table 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: Refer to Note 856624 and
proceed as described there
before importing the Support Package.
o
SAPKB64012
Symptom: After you import Basis Support
Package SAPKB64012,
background jobs are selected incorrectly
by the background system
administration tools. As a result,
background jobs may be deleted
by mistake.
Solution: You MUST refer to notes 715355
and 837691.
To solve the problem, import Support
Package SAPKB64013 or
implement the corrections in the latest
version of note 715355.
o
SAPKB64012
Symptom: A termination may occur while
you are importing Basis
Support Package SAPKB64012 during the
main import (phase
IMPORT_PROPER). The import log contains the following:
start import of
"LIMUCUADRSWIMEAN" ...
...
Table RSMPTEXTS: Duplicate record
during array insert occurred.
Reason: The error is caused by corrupt
entries in table
RSMPTEXTS, which have no other
functional effects upon the SAP
System.
Solution: Refer to Note 88656, section
29, and use the attached
allow file to ignore the error.
Basis Support Package SAPKB64013 deletes
the corrupt entries in
RSMPTEXTS.
o
SAPKB64013
Symptom: A termination may occur while
you are importing Basis
Support Package SAPKB64013 during the
main import (phase
IMPORT_PROPER). The import log contains
the following:
Table RSMPTEXTS: Duplicate record during
array insert occured.
Reason: The error is caused by corrupt
entries in table
RSMPTEXTS, which are deleted by Support
Package SAPKB64013.
Solution: The corrupt entries are deleted
successfully despite
the error message, and so you can easily
continue the import. The
error does not recur during the second
import attempt.
Recommended queues:
The following recommendations are based on
the remarks above:
SAPKB64001 - SAPKB640.. (highest Basis
Support Package available)
You can define shorter queues but you must
pay attention to the
split points.
These recommended queues are valid only if
you have not installed
any add-ons or do not have to include any
CRTs in the queue.
Otherwise, the creators of the respective
add-ons or the CRTs should
provide notes on optimal or permitted
queues!
4. ABA Support Packages (SAP_ABA component)
o
SAPKA64003 - SAPKA64004
Symptom: If the Support Packages
SAPKA64003 and SAPKA64004 are
imported together in a queue, an error
occurs in the TEST_IMPORT
step in Support Package SAPKA64004. The
test import log of
SAPKA64004 contains the following error:
Function MDM_FSBP_MAP_PROXY_TO_DDIC
(MDM_FSBP_TEST_MAPPINGS 02)
cannot be entered in the existing
function group
((MDM_FSBP_TEST_PR_CS_MAPPIN 02))
Transport the entire function group.
Solution: You can ignore this error by
choosing 'Extras'->'Ignore
test import errors'. This error no longer occurs during
subsequent imports.
o
SAPKA64004
Symptom: If the ABAP/Screen generation
is activated, an error may
occur during the ABAP/Screen generation of
SAPKA64004. In the
generation log you will find:
Program UKCNNNMM: Syntax error in line
000171
Key field 'KEY01' has been used more
than once. This is not
allowed . .
Solution: This syntax error disappears when
the SAP_APPL Support
Package SAPKH50002 is imported. To
complete the import of the
current queue with SAPKA64004, ignore
the generation errors by
selecting the menu option 'Extras' ->
'Ignore generation errors'
and continue importing the queue. Alternatively, you can
implement the corrections from Note
741674.
Recommended queues:
Based on the comments above, we can
provide the following
recommendations for ABA Support Package
queues:
SAPKA64001 - SAPKA640.. (highest
available ABA Support Package)
You can define shorter queues but you
must pay attention to the
split points.
These recommended queues are valid only
if you have not installed
any add-ons or do not have to include
any CRTs in the queue.
Otherwise, the creators of the
respective add-ons or the CRTs
should provide notes on optimal or
permitted queues!
5. BW Support Packages (SAP_BW component)
You will find information on the BW Support
Packages in note 695423
and in the related notes linked there. You
must also always read
these notes before you import BW Support
Packages.
o
SAPKW35011
Symptom: When you use a DB2/DB4/DB6 or Informix database, an
error occurs in the 'Activating inactive
runtime objects' step
(Move nametabs) when you import the BW
Support Package
SAPKW35011. You find the following error
message in the log for
this step:
Retcode 1: SQL-error -614-SQL0614N The
index or index extension
"RSCRMAT_EMAIL_T~0" cannot
be created or altered because the
combined length of the specified
columns is too long.
SQLSTATE=54008" in DDL statement
for "RSCRMAT_EMAIL_T"
You will find further information and
details in note 827915.
Solution: To prevent this error, Support
Package SAPKW35011 must
be imported together with BW Support
Package SAPKW35012.
If this is not possible, you cannot
pro-actively prevent the
error, rather it can only be eliminated
after it has appeared
(refer to note 827915). In this case,
you may not import the BW
Support Package in a queue with the
Basis or ABA Support
Packages, unlike the general stack
recommendations!
6. Application Support Packages (SAP_APPL
component)
o
SAPKH50001
Symptom: If the ABAP/Screen generation
is switched on, an error
can occur during the ABAP/Screen
generation of SAPKH50001. In the
generation log you will find:
Program /ISDFPS/RIIFLO15, Include
MIHIXF10:
Syntax error in line 000391
Field 'G_FULL_TREE' is unknown.
It is neither in one of the specified
tables nor defined by a
'DATA'
Program SAPMFCX1, Include
MF05AFK0_KONTO_PRUEFEN:
Syntax error in line 000048
Field 'FIREVDOC' is unknown.
It is neither in one of the specified
tables nor defined by a
'DATA'
Solution: These syntax errors disappear
if the EA-APPL SAPKGPAC01
Support Package is imported. To complete
the importing of the
current queue with SAPKH50001, ignore
the generation errors using
the menu option 'Additions' -> 'Ignore
generation errors' and
continue to import the queue.
o
SAPKH50002
Symptom: You want to import the Support
Package SAPKH50002, but
the queue-calculation fails.
Solution: Check whether all the Support
Packages #01 of the
software components contained in SAP ERP
Central Component 5.0
have already been imported, or are at
least available in the
system. These form the prerequisite for
the Support Package
SAPKH50002, and must be imported
irrespective of whether you
actively use the relevant software
component or not. Note 746576
contains more detailed information.
o
SAPKH50001 - SAPKH50002
Symptom: If the Support Packages
SAPKH50001 and SAPKH50002 are
imported together in a queue, an error
occurs in Support Package
SAPKH50002 in the step TEST_IMPORT. In
the test import log of
SAPKH50002, the following error message
appears:
Function FC_COI_SYSTEM_USAGE_GET (FC06 32)
cannot be entered
in the existing function group ((FC17
04))
Transport the entire function group.
Solution: You can ignore this error by
choosing 'Extras'->'Ignore
test import errors'. This error no longer occurs during
subsequent imports.
o
SAPKH50007
Symptom: After you import Support
Package SAPKH50007 due to an
error in the Support package, serious
errors may occur when you
process measurement documents.
Solution: Implement the corrections from
Note 848399, or import
Support Package SAPKH50008 as soon as
possible.
Recommended queues:
The following recommendations are based on
the remarks above:
SAPKH50001 - SAPKH500.. (highest available
SAP_APPL Support Package)
You can define shorter queues but you must
pay attention to the
split points.
These recommended queues are valid only if
you have not installed
any add-ons or do not have to include any
CRTs in the queue.
Otherwise, the creators of the respective
add-ons or the CRTs should
provide notes on optimal or permitted
queues!
7. HR Support Packages (SAP_HR component)
o
SAPKE50002
Symptom: You want to import the HR
Support Package SAPKE50002,
but the queue calculation fails.
Solution: Check whether all the Support
Packages #01 of the
software components contained in SAP ERP
Central Component 5.0
have already been imported, or are at
least available in the
system. These form the prerequisite for
the Support Package
SAPKH50002, and must be imported
irrespective of whether you
actively use the relevant software
component or not. Note 746576
contains more detailed information.
8. Support Packages for EA-APPL 500 application
extension
o
SAPKGPAC01
Symptom: Under rare circumstances, the
importing of the
SAPKGPAC01 Support Package can terminate
in the DDIC_ACTIVATION
phase. The following message appears in
the activation log:
FBICRC01020-RPROC is used in aggregate
EF_FBICRC01020
(Deletion is not allowed)
Reason: When you delete DDIC objects,
the DDIC activation program
carries out unnecessary checks (see Note
742219).
Solution: you can ignore these errors.
They no longer occur when
the DDIC activation program is run
again. Therefore, continue to
import the Support Package queue.
o
SAPKGPAC02
Symptom: In rare cases, the Support
Package SAPKGPAC02 import may
terminate in the phase DDIC_ACTIVATION.
The following message
appears in the activation log:
Table V_RMXT_TRIAL_HD could not be
activated
(W- Included search helps RECNCNA
and RESCSUA both use hot
key A)
Solution: you can ignore these errors.
They no longer occur when
the DDIC activation program is run
again. Therefore, continue to
import the Support Package queue.
Recommended queues:
The following recommendations are based on
the remarks above:
SAPKGPAC01 - SAPKGPAC.. (highest available
EA-APPL Support Package)
You can define shorter queues but you must
pay attention to the
split points.
These recommended queues are only valid if
you have not installed
any add-ons or do not have to include any
CRTs in the queue.
Otherwise, the producers of the relevant
add-ons or CRTs should
provide information on optimal or permitted
queues.
9. Support Package for Application Extension
EA-HR 500
o
SAPKGPHC02, SAPKGPHC03
Symptom: Depending on the content of the
EA-HR Support Packages
SAPKGPHC02 and SAPKGPHC03, serious
activation errors may occur
during import.
Solution: It is essential that you read
Note 780475 before
importing the EA-HR Support Packages,
and import at least the
Basis Support Package SAPKB64004
beforehand.
Activation errors of the type:
Structure
"TPHOTEL_PROPERTY_DESCRIPTION35" is part of a cycle
can by solved by reactivating the DDIC.
Recommended queues:
The following recommendations are based on
the remarks above:
SAPKGPHC01 - SAPKGPHC.. (highest EA-HR
Support Package available)
You can define shorter queues but you must
pay attention to the
split points.
These recommended queues are only valid if
you have not installed
any add-ons or do not have to include any
CRTs in the queue.
Otherwise, the producers of the relevant
add-ons or CRTs should
provide information on optimal or permitted
queues.
________________________________________________________________________
Valid releases
Software
component Release
from to
SAP_BW Business Information Warehouse
350 - 350
SAP_BASIS SAP Basis component
640 - 640
SAP_ABA SAP Application Basis
640 - 640
________________________________________________________________________
References to related
notes
Number Short text
____________________________________________________________
856624 Indexes for table CDHDR (SAPKB62050/51,
SAPKB64011)
848399 Measurement docs: Problems after you
implement Note 806624
841938 DB2/DB4/DB6: Buffer synchronisation between
dw, tp & R3trans
837691 Background jobs are unintentionally deleted
828554 Incorrect BW MDMP check when upgrading to
Basis 6.40
827915 RSCRM - applying SP11 dumps -
RSCRMAT_EMAIL_T
816523 Termination when a user logs on: "No
authorization"
788623 Additions to upgrade on SAP SRM Server 5.0
SR1
788218 Add. info. on upgrading to SAP ERP Central
Component 5.0 SR1
780475 Risk of activation errors with EA HR 500
Support Package 3
775047 Add. info. on upgrading to SAP Web AS 6.40
SR1
753627 Applying Support Packages and/or applying
transports aborts
746576 SAP ERP Central Component 5.0:
Installation/upgrade with SP1
743408 Runtime error ASSIGN_LENGTH_0 in XPRAS_UPG
phase
742219 Error deleting Ddic objects
741674 EC-EIS: Error in generation template
UKCNNNMM: Double key
731265 BindInputParams: the parameter is incorrect
727149 Alert classifications deleted by Support
Package
726147 SRM 4.0 Installation: Composite Note
715355 BP_JOB_SELECT: Optimizing the job selection
695423 BW 3.5: Information on Support Packages
689574 Add. info. on upgrading to SAP ERP Central
Component 5.00
684406 Additional information on upgrading to SAP
SCM 4.1
672652 Known problems with transaction SAINT in
Basis Release 6.40
661640 Add. info. on upgrading to SAP Web AS 6.40
627246 Error when you create new objects.
ORA-02168
517484 Inactive services in the Internet
Communication Framework
211077 Exchanging target release kernel during
upgrade
88656
R3trans: Composite SAP note on "duplicate key"(as of 4.0)
________________________________________________________________________
Comments
Post a Comment