on 04-23-2013 7:03 PM
Hello Basis Guys, this is just to let you know how I solved a problem when appying ABAP SP to one Solution Manager system:
I was applying SP and everything was going ok until COMPUTE_INT_PLUS_OVERFLOW dumps appeard during DDIC_ACTIVATION phase. According to Note 1678047 - COMPUTE_INT_PLUS_OVERFLOW I applied the following procedure:
Call Tx SE38 - SDB1FHDB
Select Source Code and Display
Switch to edit mode and replace:
limit-secindcnt = 2147483647.
with
limit-secindcnt = 1023.
I found some transport requests not released. SP could not continue because of this messages:
Message no. TW104
R3TRPROGSDB1FHDB was repaired in this system.
R3TRCLASCL_SISE_GW_ASSIST was repaired in this system.
So, according to http://scn.sap.com/thread/3327316 I reset the ‘Repair Flag' of those objects and released the requests.
After that it was possible to move on from DDIC_ACTIVATION phase. Then I was stuck in IMPORT_PROPER phase because of many SINTAX_ERROR dumps. Based on http://scn.sap.com/message/4963378 , I had to run command "tp R3I support_pack
system_id pf=E:\usr\sap\trans\bin\TP_DOMAIN_system_id.PFL" as follows for every Support P. in the SPAM queue:
C:\Users\ps2adm>tp R3I SAPKA70211 PS2 pf=E:\usr\sap\trans\bin\TP_DOMAIN_PS2.PFL
tag=SPAM
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
This is tp version 380.04.07 (release 720, unicode enabled)
This is R3trans.exe version 6.23 (release 720 - 31.10.12 - 20:12:06).
unicode enabled version
R3trans=>sapparam(1c): No Profile used.
R3trans=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
R3trans.exe finished (0004).
tp finished with return code: 4
meaning:
A tool used by tp produced warnings
tp showbuffer PS2 pf=E:\usr\sap\trans\bin\TP_DOMAIN_PS2.PFL
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
This is tp version 380.04.07 (release 720, unicode enabled)
PS2 buffer:
SAPK-70210INCTSPLGN | | |has already been imported completely.
SAPK-S7210INCTSPLGN | | |has already been imported completely.
SAPKB70211 | | |has already been imported completely.
SAPKA70211 | | |has already been imported completely.
However, I had to additionally create some Transport Requests from PS1 system (dev. system) and transport them from within O.S. level in PS2 (prd. system) to solve the SINTAX_ERROR dumps which did not allow me to apply SP totally. I did it for objects Function Module TMS_PM_READ_TP_PARAMETER, Program SAPLTMSP, Program SAPLTMSU.
These sintax errors were like this:
Category ABAP Programming Error
Runtime Errors SYNTAX_ERROR
ABAP Program SAPLTMSP
Application Component BC-CTS-TMS
Date and Time 03.04.2013 10:49:14
Short text
Syntax error in program "SAPLTMSP ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSTPA" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLTMSP " in include "LTMSPU11 in line 239:
"Field "GC_TMS_PM_VAL_OPMOD_UNKNOWN" is unknown. It is neither in one o"
"f the specified tables nor defined by a "DATA" statement."
and so on... The problem is that those sintax_error dumps did not allow STMS work properly.
I hope it helps you a lot.
Regards,
Freddy Torres
SAP Netweaver Consultant
Hi,
The note has just been
released:
1842611 Syntax error in function TMS_PM_READ_TP_PARAMETER
Can you please
apply solution 2 of the note on your system?
Regards,
Aidan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.