NW70 EHP1 Update Problem w/SPAM/SAINT

Hello,
We have followed the guide for NW 7.0 EHP to update our system from NW 7.0 SPS18. The kernel update appears to be successful, and system -> status tells us that we are on the 701 kernel.
However, we are having trouble in SPAM/SAINT. We've downloaded the latest 701/34 kernel and attempted to update spam, but once the update completes and we restart spam, it is still at 700/34 (not 701/34).
Furthermore, we are able to load the 701 support packs from EPS/in, however, they never appear in SPAM or SAINT, and therefore they cannot be added to a queue and applied to the system. SAINT complains that the components are "701" and basically are not appropriate to install in a "700" system.
Obviously we are missing something here in the update process. What does it take to get SAINT/SPAM to recognize the 701 support packs? We've read through many docs and notes and have had no success.
Thank you.

Thanks for your help so far.
We downloaded the NW7.0 EHP1 SP3 at this link: http://service.sap.com/sap/bc/bsp/spn/sps/index.do?pvnr=01200314690900000866
I followed the stack guide at this link: https://websmp207.sap-ag.de/~sapidb/011000358700000087932009E.PDF
The downloads are:
File ;Description ;Component Version ;Instantiation ;Instances
SAPK-70101INPIBASIS;PI_BASIS Support Package 01 for 7.01;PI_BASIS 7.01;;Application Server ABAP
SAPK-70102INPIBASIS;PI_BASIS Support Package 02 for 7.01;PI_BASIS 7.01;;Application Server ABAP
SAPK-70103INPIBASIS;PI_BASIS Support Package 03 for 7.01;PI_BASIS 7.01;;Application Server ABAP
SAPKA70101;ABA Support Package 01 for 7.01;SAP ABA 7.01;;Application Server ABAP
SAPKA70102;ABA Support Package 02 for 7.01;SAP ABA 7.01;;Application Server ABAP
SAPKA70103;ABA Support Package 03 for 7.01;SAP ABA 7.01;;Application Server ABAP
SAPKB70101;Basis Support Package 01 for 7.01;SAP BASIS 7.01;;Application Server ABAP
SAPKB70102;Basis Support Package 02 for 7.01;SAP BASIS 7.01;;Application Server ABAP
SAPKB70103;Basis Support Package 03 for 7.01;SAP BASIS 7.01;;Application Server ABAP
SAPKW70101;BW Support Package 01 for 7.01;SAP BW 7.01;;Application Server ABAP
SAPKW70102;BW Support Package 02 for 7.01;SAP BW 7.01;;Application Server ABAP
SAPKW70103;BW Support Package 03 for 7.01;SAP BW 7.01;;Application Server ABAP
igsexe_13-10003077.sar;Installation for SAP IGS integrated in SAP Kernel;SAP IGS 7.00;AIX 64bit;Application Server ABAP
SAPEXE_23-10006210.SAR;Kernel Part I (for Basis 7.01);SAP KERNEL 7.01 64-BIT UNICODE;AIX 64bit/#Database independent;Application Server ABAP
SAPEXEDB_23-10006211.SAR;Kernel Part II (for Basis 7.01);SAP KERNEL 7.01 64-BIT UNICODE;AIX 64bit/ORACLE;Application Server ABAP

Similar Messages

EHP1 installation problem "No matching SAINT package for 'PI_BASIS' found"

Hi everybody,
i want update an Netweaver 2007 (SP14), BI, Dual Stack system to EHP1 (SP 5).
I use this manual during this installation:
(Update to NetWeaver EhP1)
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/808c3535-e378-2c10-83b4-cff07abef8e3&overridelayout=true
I've get all necessary support packages and the xml-file, put it into EPS-INBOX (Page 18 and Page 21) but i get the message "No matching SAINT package for 'PI_BASIS' found".
I know this was an issue, if you have SPAM 0036 (Note 1387523), but i've updated allready to 0037.
Have somone an idea?
Thanks a lot.

Hi,
please compare the SCA files for PI_BASIS are located in EPS/in
-rw-rr   1 c2badm   sapsys    192917 Nov 9 18:05 K-70101INPIBASIS.SAR
-rw-rr   1 c2badm   sapsys    353557 Nov 9 18:05 K-70102INPIBASIS.SAR
-rw-rr   1 c2badm   sapsys    508062 Nov 9 18:05 K-70103INPIBASIS.SAR
-rw-rr   1 c2badm   sapsys    393073 Nov 9 18:05 K-70104INPIBASIS.SAR
-rw-rr   1 c2badm   sapsys   1222228 Nov 9 18:05 K-70105INPIBASIS.SAR
-rw-rr   1 c2badm   sapsys   54524280 Nov 9 18:07 K-701DHINPIBASIS.SAR
with the entries in your .xml file like this:
<caption>PI_BASIS 7.01</caption>
    <ppms-number>01200615320200010570</ppms-number>
    <runtime-type>ABAP</runtime-type>
    <name>PI_BASIS</name>
    <version>701</version>
    <vendor>sap.com</vendor>
    <support-package>
     <caption>PI_BASIS Support Package 01 for 7.01</caption>
     <name>SAPK-70101INPIBASIS</name>
     <vendor>sap.com</vendor>
     <ppms-number>01200615321100046953</ppms-number>
     <sp-level>000001</sp-level>
     <patch-level>0</patch-level>
     <archives>
      <archive-name>K-70101INPIBASIS.SAR</archive-name>
     </archives>
    </support-package>
    <support-package>
     <caption>PI_BASIS Support Package 02 for 7.01</caption>
     <name>SAPK-70102INPIBASIS</name>
     <vendor>sap.com</vendor>
     <ppms-number>01200314691100043507</ppms-number>
     <sp-level>000002</sp-level>
     <patch-level>0</patch-level>
     <archives>
      <archive-name>K-70102INPIBASIS.SAR</archive-name>
     </archives>
    </support-package>
and so on ...until SAPK-70105INPIBASIS
finally the AddOn Package:
<support-package>
     <caption>PI_BASIS 701 Upgrade</caption>
     <name>SAPK-701DHINPIBASIS</name>
     <vendor>sap.com</vendor>
     <ppms-number>01200314691100040643</ppms-number>
     <sp-level>0000</sp-level>
     <patch-level>0</patch-level>
     <archives>
      <archive-name>K-701DHINPIBASIS.SAR</archive-name>
     </archives>
    </support-package>
   </software-component>
Gerd

Using SPAM/SAINT for the first time (Many doubts and questions)

Hi all,
I'm newbie using SPAM/SAINT and SOLMAN.
I've mande a maintenance optimizer task for the SOLMAN system here in the company.
My actual installed components are:
SAP_ABA     700     0012     SAPKA70012     Cross-Application Component
SAP_BASIS     700     0012     SAPKB70012     SAP Basis Component
PI_BASIS     2005_1_700     0012     SAPKIPYJ7C     PI_BASIS 2005_1_700
ST-PI     2005_1_700     0006     SAPKITLQI6     SAP Solution Tools Plug-In
SAP_BW     700     0013     SAPKW70013     SAP NetWeaver BI 7.0
SAP_AP     700     0010     SAPKNA7010     SAP Application Platform
BBPCRM     500     0009     SAPKU50009     BBPCRM
BI_CONT     703     0005     SAPKIBIIP5     Business Intelligence Content
CPRXRPM     400     0009     SAPK-40009INCPRXRPM     SAP xRPM/cProjects/cFolders 4.00 (ABAP)
ST     400     0012     SAPKITL422     SAP Solution Manager Tool
ST-A/PI     01J_CRM500     0000     -     Application Servicetools for CRM 500 / 5
ST-ICO     150_700     0009     SAPK-15079INSTPL     SAP Solution Manager Implementation Cont
ST-SER     700_2007_1     0001     SAPKITLOM1     SAP Solution Manager Service Tools
I've made the search and found a lot of info.
Some kernel updates (I386 on my case), and my first question is: "How do I update this? Is it safe to be the first thing to be done?" Is it only copy to the Run directory (usr\sap\<SID>\SYS\exe\run)?
Also a component BC-FES-IGS has some updates, but I don't know what is this and how to update. (it says: Installation for SAP IGS integrated in SAP Kernel igsexe_16-10003071.sar)
All the rest (SAPK* files), seems to be normal patches that is possible to use spam to update them. Correct?
How to use SPAM/SAINT? What is used in one time, and on others? Do they do the same?
Regards,
Pedro
Edited by: Pedro Taveira on Aug 17, 2010 5:20 PM

Hi Pedro,
Some kernel updates (I386 on my case), and my first question is: "How do I update this? Is it safe to be the first thing to be done?" Is it only copy to the Run directory (usr\sap\<SID>\SYS\exe\run)?
As SolMan is a dual stack machine, you can use JSPM to update the kernel. Another way is to extract the Kernel SAR files into the exe\run directory. It is a best practice to update the kernel before the support packages. Take a backup of the existing exe directories before you update the kernel and also pay good attention while downloading the kernel. you need to take care while choosing the correct version of the kernel (either 32 bit or 64 bit and ITANIUM or XEON). If you choose the wrong kernel, then ur SAP system will not come up.
Also a component BC-FES-IGS has some updates, but I don't know what is this and how to update. (it says: Installation for SAP IGS integrated in SAP Kernel igsexe_16-10003071.sar)
Extract the IGS SAR also along with teh kernel files.
All the rest (SAPK* files), seems to be normal patches that is possible to use spam to update them. Correct?
Yes!!! You may have to update the latest SPAM/SAINT (SAPKD700*) before updating the SP's.
How to use SPAM/SAINT? What is used in one time, and on others? Do they do the same?
Support Packs can be updated using SPAM and the add-on upgrades has to be done using SAINT.
Regards,
Varadharajan M

Which SPAM/SAINT for our System

Hi All
I want to apply SAP SP-Stack on our ECC6 System.
When I execute TX-SPAM I got following information
"Support Package Manager - Version 7.00 / 0023"
on service marketplace when I click "SAP SPAM/SAINT UPDATE" I have following options
SPAM/SAINT UPDATE 620
SPAM/SAINT UPDATE 640
SPAM/SAINT UPDATE 700
SPAM/SAINT UPDATE 701
SPAM/SAINT UPDATE 702
SPAM/SAINT UPDATE 710
SPAM/SAINT UPDATE 711
SPAM/SAINT UPDATE 720
SPAM/SAINT UPDATE 730
SPAM/SAINT UPDATE 800
Should I have to download
SPAM/SAINT UPDATE 700 OR SPAM/SAINT UPDATE 800
SPAM/SAINT UPDATE 700 is more likely because myversion is also showing 7.00 but where is the utilization of 8.00
regards
Syed Saifuddin

Hello Syed,
When I execute TX-SPAM I got following information
"Support Package Manager - Version 7.00 / 0023"
- Version 7.00 refers your system kernel release.
Should I have to download
SPAM/SAINT UPDATE 700 OR SPAM/SAINT UPDATE 800
- Since your system release is 700, you should download latest patch of SPAM/SAINT UPDATE 700.
Hope your query is answered.
Thanks,
Siva Kumar

SPAM/SAINT Version Updation Problem

hi,
I have installed ECC 5.0 and i have also updated the Kernel,
but when i go to update the SPAM/SAINT Manager Version it shows that it requires at least 0018 Version of the Support Manager.
Can any body please suggest that what is the process of upgrading the SPAM Manager and if there any downloads required to update the SPAM/SAINT Manager.
It's Urgent.....!
Regards,
Ashish
Edited by: Ashish Chugh on Feb 18, 2008 11:58 PM

Hi,
You need to download the patch for SPAM/SAINT upgrade.
Http://service.sap.com/patces --> Enty by application group --> Additional components --> SPAM/SAINT update --> SPAM/SAINT update <version>
Download the latest version.
Uncar in /sapmnt/trans at OS level. Go to SPAM and click support package --> import SPAM/SAINT update
Best Regards,
Srividya.R

Problem faced while update to spam/saint version 39 basis realease 700

Hi
I am a SAP BASIS Administrator at fresher level.My spam/saint version was 22 when i applied SPAM/SAINT version 39 for SAP BASIS 700 , at first time it was not imported and struck at *Movenamespace with return code zero* phase and the import log showed error at IMPORT_PROPER phase,
But as described in the SAP note 822379 , i followed the instruction emptied the queue and imported the spam/saint version again
This time the import was completed and showed a green status. But next time when i wanted to apply SAP_BASIS 10 support pacake immediately it showed an runtime syntax error.
The error is as follows
Runtime Errors         SYNTAX_ERROR
Date and Time          02.03.2011 11:57:31
|Short text
|    Syntax error in program "CL_OCS_RT_ANALYSIS============CP ".
|What happened?
|    Error in the ABAP Application Program
|
|    The current ABAP program "SAPLSPAM" had to be terminated because it has
|    come across a statement that unfortunately cannot be executed.
|
|    The following syntax error occurred in program
|     "CL_OCS_RT_ANALYSIS============CP " in include
|     "CL_OCS_RT_ANALYSIS============CM002 " in
|    line 135:
|    "Die Transformation "RTA_TRAFO" hat keine aktive Version."
|    " "
|    " "
|    " "
|
|    The include has been created and last changed by:
|    Created by: "SAP "
|    Last changed by: "SAP "
|
|Error analysis
|    The following syntax error was found in the program
|     CL_OCS_RT_ANALYSIS============CP :
|    "Die Transformation "RTA_TRAFO" hat keine aktive Version."
|    " "
|    " "
|    " "
|Trigger Location of Runtime Error
|    Program                                 SAPLSPAM
|    Include                                 LSPAMU69
|    Row                                     364
|    Module type                             (FUNCTION)
|    Module Name                             SPAM_PROLOGUE
|Source Code Extract
|Line |SourceCde
334
| 335|*       and set default start options according to the new scenario
| 336|        CALL FUNCTION 'OCS_SET_DEFAULT_START_OPTIONS'
| 337|          EXPORTING
| 338|            iv_ocs_tool = lv_tcode
| 339|            iv_scenario = lv_scenario
| 340|            iv_save     = on
| 341|          EXCEPTIONS
| 342|            OTHERS      = 0.
343
| 344|*       inform the user about the scenario change
| 345|        MESSAGE i336(tn) WITH lv_inact_scenario lv_scenario
| 346|                         RAISING emergency_stop.
| 347|      ENDIF.   "sy-saprl(2) < '46'
| 348|    ENDIF.
| 349|*   activate all halt points for current transaction
| 350|    UPDATE patstop SET cont_step = off
| 351|                   WHERE ocs_tool = lv_tcode.
352
| 353|*   initialize the application specific checks
| 354|    UPDATE patcheck SET ret_code   = space
| 355|                        reason     = space
| 356|                        message    = space
| 357|                        ign_in_dia = off
| 358|                        ign_in_btc = off
| 359|                        queue_id   = lv_queue_id
| 360|                    WHERE ocs_tool = lv_tcode AND
| 361|                          active   = on.
362
| 363|*   collect some source data for the runtime analysis
|>>>>>|    CREATE OBJECT lr_rt_analysis
| 365|      EXPORTING
| 366|        iv_queue_id = lv_queue_id
| 367|      EXCEPTIONS
| 368|        others      = 99.
| 369|    IF sy-subrc = 0.
| 370|      CALL METHOD lr_rt_analysis->collect_conf_data
| 371|        EXPORTING
| 372|          iv_conf_group = 'ALL'
| 373|        EXCEPTIONS
| 374|          OTHERS        = 0.
| 375|      CALL METHOD lr_rt_analysis->save
| 376|        EXCEPTIONS
| 377|          OTHERS = 0.
| 378|    ENDIF.
| 379| ENDIF.                               "SY-SUBRC = 0
380
| 381|* (5) now start with the application:
| 382|* - set the OCS environment
| 383|* - read the settings
Can anyone please suggest a bolution on BASIS perspective

Hi all,
Not sure if this thread is still active at all, but just to be sure, and to close it once and for all
to solve this issue :
Icheck class CL_OCS_RT_ANALYSIS in TA SE24 and go to method GET_XML.
Search for RTA_TRAFO, jump to object via doubleclick and activate it.
Afterwards install the latest TP and R3trans tools from sapnet, and SPAM should be working again.
Best regards,
Menno van Rooij

Problem updating spam/saint

Hi all,
While updating spam/saint i m getting following error.
- Error in step: CHECK_REQUIREMENTS
- Reason for error: TP_CANNOT_CONNECT_SYSTEM
- Return code: 0212
Any idea how to resolve this. This system is connected to another system in tms , the latter being domain controller. The tp versions in these 2 sys are diff. Can this be the prob..
Any suggestion?
Thanks,
Ajith

Hi,
You didn't say what system you using ? Anyway, go into SM59 and find the RFC connections used for TMS(usually two) under ABAP connections, try do a connection test, is it successful ? ..if not check technical settings are correct.
See note 96907 for further troubleshooting.
Nelis

Error in spam/saint update TP_CANNOT_CONNECT_SYSTEM TP_INTERFACE_FAILURE

Dear All,
while i am updating spam / saint in saint t code I am facing an error TP_INTERFACE_FAILURE and reason for the error is TP_CANNOT_CONNECT_SYSTEM
the error details are
The installation was stopped, since an error occurred during the phase
CHECK_REQUIREMENTS, which the Add-On Installation Tool is unable to
resolve without your input.
After you have corrected the cause of the error, continue with the
import by choosing Continue in the queue display.
The following details help you to analyze the problem:
    -   Error in phase: CHECK_REQUIREMENTS
    -   Reason for error: TP_CANNOT_CONNECT_SYSTEM
    -   Return code:
    -   Error message: TP_INTERFACE_FAILURE
Notes on phase CHECK_REQUIREMENTS
n this phase the system checks the various requirements for the add
nstallation. The following are reasons why this phase may fail:
   TP_CANNOT_CONNECT_TO_SYSTEM: tp cannot log on to the system
   database.
   Check the action log (in the menu, choose Goto -> Action Log). Y
   may be able to use the detailed tp error message in this log to
   identify and remove the cause of the error.
   QUEUE_NOT_EMPTY: There are still OCS requests in the transport
   buffer which are not completed. You can show these requests with
   following tp command:
   tp SHOWBUFFER <SID> -DSOURCESYSTEMS= TAG=SPAM
   These requests have to be completed or deleted from the buffer
   before you can continue importing the queue.
o   CANNOT_DROPBUFFER: tp cannot delete old, incompletely processed
     Support Packages from the tp buffer.
     Check the action log (in the menu, choose Goto -> Action Log). You
     may be able to use the detailed tp error message in this log to
     identify and remove the cause of the error.
The Add-On Installation Tool requires that the Change and Transport
System (CTS) be configured correctly. For more detailed information,
read the online documentation available from Help -> SAP Library ->
mySAP Technology Components -> SAP Web Application Server -> BC Change
and Transport System .
A list of the most important SAP Notes for Online Correction Support
(OCS) is available in SAP Note 97620, which is updated regularly.
please help me, its very important to complete this job i am in a critical position
Thanks
Senthil

Dear,
Please refer these links,
tp_cannot_connect_system
Problem loading a package in the SAINT transc. (TP_CANNOT_CONNECT_SYSTEM)
Regards,
R.Brahmankar

Error in Spam / saint update TP_STEP_FAILURE and DDIC_ACTIVATION

Dear All,
While updating spam/ saint update I am facing this error
Details of Error:
The installation was stopped, since an error occurred during the phase
DDIC_ACTIVATION, which the Add-On Installation Tool is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Continue in the queue display.
The following details help you to analyze the problem:
    -   Error in phase: DDIC_ACTIVATION
    -   Reason for error: TP_STEP_FAILURE
    -   Return code: 0008
    -   Error message: tp step A, return code
        0008
Notes on phase DDIC_ACTIVATION
In this phase the system activates the imported Data Dictionary objects.
This phase may terminate for several reasons:
o   TP_INTERFACE_FAILURE: The system was unable to call the tp
     interface.
o   TP_FAILURE: The system was unable to execute the tp program. For
     more information, see the SLOG or ALOG log file.
o   TP_STEP_FAILURE: The system was unable to perform the tp step DDIC
    activation successfully. To see the cause of the problem in the
    activation log, choose Logs.
    If you import two or more OCS packages in one installation queue,
    and activate the Data Dictionary objects in the incorrect sequence,
    this can cause errors. In this case, the activation errors disappear
    if you repeat the activation run. To do this, choose Continue.
The Add-On Installation Tool requires that the Change and Transport
System (CTS) be configured correctly. For more detailed information,
read the online documentation available from Help -> SAP Library ->
mySAP Technology Components -> SAP Web Application Server -> BC Change
and Transport System .
A list of the most important SAP Notes for Online Correction Support
(OCS) is available in SAP Note 97620, which is updated regularly.
Please help me
Thanks
Senthil

Hi,
i am having the same problem with SPAM
Error in phase: DDIC_ACTIVATION
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package SAPKA70012, tp step A, return code
0008
however i dont have the option to continue.. Please help
thanks

SUM - SPAM/SAINT 7.3 Update using SQL2012

Hi,
I installed a SAP NW BW 7.3 in Windows Server 2012 / SQL 2012 and I'm trying to update SPAM/SAINT via SUM, but this errors occurs:
1 ETQ359 RFC Login to: System="BWD", AsHost="atlas" Nr="00", GwHost="atlas", GwService="sapgw00"
2 ETQ232 RFC Login succeeded
4 ETQ010 Date & Time: 20140527175641
1 ETQ233 Calling function module "OCS_API_DELETE_QUEUE" by RFC
1EETQ235 Call of function module "OCS_API_DELETE_QUEUE" by RFC failed (error-status "3")
2EETQ360 RFC of "OCS_API_DELETE_QUEUE" failed:
2EETQ361 code/exception : 3
2EETQ362 key             : DBIF_RSQL_SQL_ERROR
2EETQ399 SQL error 515 while accessing table PAT05.
4 ETQ010 Date & Time: 20140527175641
1EETQ399 Last error code set is: RFC error system BWD nr 00 function 'OCS_API_DELETE_QUEUE' failed with code 3 key DBIF_RSQL_SQL_ERROR: SQL error 515 while accessing table PAT05.
1EETQ204 Upgrade phase "SPAMCHK_INI" aborted with severe errors ("20140527175641")
And generate these two short dumps:
1)
Category               ABAP Server Resource Shortage
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          27.05.2014 18:32:53
Short text
     SQL error 515 while accessing table "PAT05".
What happened?
     Database error text: "Cannot insert the value NULL into column
      'DDIC_ACT_SUBSET', table 'BWD.bwd.PAT05'; column does not allow nulls. UPDATE
      fails."
2)
Category               ABAP Server Resource Shortage
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          27.05.2014 18:45:59
Short text
     SQL error 515 while accessing table "PATHISTORY".
What happened?
     Database error text: "Cannot insert the value NULL into column 'DACT_SUBSET',
      table 'BWD.bwd.PATHISTORY'; column does not allow nulls. INSERT fails."
Can anyone help me?
I didn't find any SAP note, or documentation about this problem.
Thanks!
Marcello

Hi Reagan,
I read this note, but the solution is to re-install the application.
I will do this in last case.
Thanks!

Update SPAM/SAINT package for release 7.00 terminated

Hi All,
We have installed solman 4.0 on windows environment. when i tried to import spam/saint update, it got terminated in the phase IMPORT_PROPER.
Also, in SM50 it is showing on workprocess running for long and gets terminated. I also have run SGEN once my installation was over.
0 DIA 4028 Running Yes 649 SAPMS38L 000 DDIC Delete D010INC
can anyone suggest what the problems would be..
Thanks and Regards,
sailesh K

Hi
I have tried three times. In fact I also restarted SAP System by changing rdisp/max_wp_runtime to 0 as there were lot of short dumps with timeouts.
I notice that currently job RDDGEN0L is running at present.
Also,
1) Dialogue work process running Report SAPMS38L with action Delete on Table D0101NC (User DDIC).
2) BGD Work process Status On Hold Reasn RFC with report SAPLSDDD (User DDIC).
SPAM Status is "MOVE NAMETABS FINISHED WITH RETURN CODE 0". Import logs finished with error code 4.
Regards
Chandu
P.S : FYI I am opening another thread with the same message.

Spam/Saint update failed

Hello,
My current SPAM/SAINT version is 20.
I tried updating it to version 38.
But while updaing m facing a runtime error which is generating a short dump.
Short Text of dump is as follows:
Syntax error in program "CL_OCS_RT_ANALYSIS============CP
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSPAM" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
     "CL_OCS_RT_ANALYSIS============CP " in include
     "CL_OCS_RT_ANALYSIS============CM002 " in
    line 135:
    "Die Transformation "RTA_TRAFO" hat keine aktive Version."
    The include has been created and last changed by:
    *Created by: "SAP "    Last changed by: "SAP "*
Below is the status of Import phase
SPAM/SAINT update is being processed
SPAM status: (Red)
Import phase:     PROLOGUE
Please help.
Thanks Deepak

I have similar problem, i have the following runtime error:
The following syntax error occurred in program
"CL_OCS_RT_ANALYSIS============CP " in include
"CL_OCS_RT_ANALYSIS============CM002 " in
line 13:
"Type "OCSRT_TOOL" is unknown"
I have create OSS-message and SAP reply;s:
Regarding your issue, please transport the class CL_OCS_RT_ANALYSIS
from other system in the landscape which is on the same release and
support package level and with the SPAM\SAINT update version as the
PRD system to the PRD system to resolve the syntax error.
Once the syntax error is resolved in the PRD the SPAM\SAINT update can
be continued in the SPAM to import the SPAM\SAINT update in the system.
For more information please refer the link specified below for
including the objects manually in the transport request.
http://help.sap.com/saphelp_nw70/helpdata/en/57/38e2864eb711d182bf0000e829fbfe/content.htm
I looked to the url, but still not understanding how to add it...can someone explain me how to export it?
Thanks,
Cheung

Problem with spam update

Hi,
I have some problem with SPAM update.
my SPAM version is 620/patch level is 23 on kernal 620.
I was upgraded my kernal from 620 to 640.
after that i downloaded the SPAM (SAPKD64023) from marketplace, and uncar that patch by using sapcar xvf. After that I went to transaction SPAM and selected option spam/saint update, then I am getting error called
*spam/asint update SAPKD62023 has already been imported successfully
*so please tell me how to update SPAM version from 620/23 to 640

Hi
I got your question to some level & from 4.7 onwards Basis Abap & Spam/Saint are segregated to one release.
so for ex- sapkb620**
sapka620**
sapkd620** & when it comes application
sapkh470**
sapke470**
from the above examples 620 indicates version release of Basis Abap & Spam/Saint
& 470 indicates Aplications & HR release
where as you can notice in 4.6b every thing is in on platform
sapkb460**
sapka460**
sapkh460**
sapka460**
Thanx & regards,
Rahul

SPAM/SAINT update error patch 23 - 640

Hi:
I´m recieving the following dump when updating SPAM/SAINT patch 23 under 640:
Syntax error in program "SAPLOCS_UI "
Error in ABAP application program.
The current ABAP program "SAPLSPAM" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
In program "SAPLOCS_UI ", the following syntax error occurred
in the Include "LOCS_UIU15 " in line 1:
"Function "OCS_DISPLAY_WITH_USER_BUTTON" not found in Function Library."
In program "SAPLOCS_UI ", the following syntax error occurred:
"Function "OCS_DISPLAY_WITH_USER_BUTTON" not found in Function Library."
Thanks a lot,
Armenta

Hii read modification adjustments in this document u will get a clear idea.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCUPGOCSSPAM/BCUPGOCSSPAM.pdf
Award points if useful

Support Package Manager: SPAM/SAINT Update

Hi,
I downloaded the SPAM/SAINT Update and executed it with SAPCAR in the directory of the Application Server Folder. The original file KD74053.sar (6767 kb) is still in the folder, but a new file 'signature.smf' (5 kb) appeared.
What is that one for?
Next, I think that I should be able to take a next step with transaction SPAM (Support Package --> Load Packages --> From Application Server), but it's 'blanked out' and not accessible.
What are the next steps and how do I really get the SPAM/SAINT update working, so I can proceed to my actual goal, the Support Package Update.
Thanks!

Hi,
To reset DDIC password you could go with
SQL> select bname from usr02 where mandt='000' and bname='SAP*'
If the user SAP* exists then delete the user with below command
SQL> delete from usr02 where mandt='000' and bname='SAP*'
Run the below command to verify whether user deletion was successful.
SQL> select bname from usr02 where mandt='000' and bname='SAP*'
SQL> commit;
After that login to client 000 with SAP* and password as pass
reset the password for user DDIC with SAP* user.
Thanks,
Gaurav

NW70 EHP1 Update Problem w/SPAM/SAINT

Similar Messages

Maybe you are looking for