Last version of support package manager

Hi,
where can I find the last version 0026 of Support Package Manager (NetWeaver 2004s) on Marketplace for downloading?
Thanks.
Regards
Stefan

Hi,
Check this Path for the same
service.sap.com>solution Details>SAP Netweaver-->Release specific information.
Regards
Seshagiri

Similar Messages

  • Maintenace optimiser, support package Manager, Support package stack

    HI all,
             Could you please enlighten me the differences among
    Maintenance Optimizer,support package Manager, Support package stack
    And the purpose and most importantly the documentation to be able to use them
    in case of implementation phase (In case of a fresh ECC 60 Production version)
    Thank you

    Maintenace optimiser is used in solution Manager to Approve the Patch that you need to download fron Service  market place
    Support package stack is the collection of patch for a release.
    Support package Manager is SPAM/SAINT used to apply support pack.
    If you want some thing else please revert back
    thanksd Rishi Abrol

  • How to deploy EAR on CE server using Java Support Package Manager

    Hello,
    I am using CE server where I want to deploy EAR file by using JSPM. I run this program in Drive:\usr\sap\CE1\J00\j2ee\JSPM\go.bat
    I have also put the EAR file into the inbox folder Drive:\usr\sap\CE1\SYS\EPS\in but still It does not show me any file to proceed further for deployment.
    Does any one has idea?
    Regards,
    NK

    Hi,
    The Java Support Package Manager is not able to deploy a single .ear file.
    If the *.EAR file is placed inside an SCA (Software Component Archive) then JSPM is able to deploy it.
    You have to create a .SCA from an .EAR file
    SAP note 1223957 contains an attachment (nwpacktool.zip) which can be used to create a .SCA file from the .EAR file.
    Gerd

  • How to import all Support Packages simulteneily support Package Manager EBP

    Can any body tel me how to apply all support package sumultanesoly by using support Package Manager EBP/CRM option in SPAM.
    I could not able to select all pactche at a time.It selecting one patch at a time only
    Regards
    G Sasikanth Reddy

    I solved my self by selecting highest level of patch so that its dependencies can also add to the queue.
    Regards
    Sasikanth Reddy

  • Support Package Manager for EBPCRM

    Hi,
    In CRM/EBP SAP systems there is used special 'Support Package Manager for EBPCRM' to implement Support Packages instead of standard transactions like SPAM/SAINT.
    I'm trying to implement more then one Support Package into the system however this is probably not possible. It seems that it is not possible to create import queue with more then one Support Package? Importing SPs one by one is very time consuming task. SO that's why I'm wondering about this special tool.
    Do you have similar functionality?
    BR
    m./

    Hi Jose,
    Yes I've put all the SPs into '\usr\sap\trans\Eps\in'. But 'Support Package Manager for EBPCRM' asks me for particular one while I'm going to import it. There is no such an functionality to use queue creation.
    BTW: I'm on SAP CRM 4.0 on WIN/MSSQL platform.
    BR
    m./

  • PAT file not shown in Support package manager

    Hi All,
    We had to create a custom BAPI to achieve an functionality in our product.
    We are doing this for the first time.
    As a standard procedure we followed the AAK (Assembly Add On ) toolkit to create the deploy-able.
    Finally in the consolidation system we could see the following PAT file created in the out directory.
    QA70020777848_0000002.PAT
    I copied the file to the in directory of the production SAP server where this needs to be deployed.
    I ran the transaction SPAM on the server.
    Load packages from Application server
    QA70020777848_0000002.PAT    SAPK-170COINCOMPANY1    @EB\QUpload Already Occurred@    0004    OCS file already exists in inbox. Upload not required.
    IT decompresses the file properly.
    Now the problem occurs ahead.
    IF i click on the New Support package nothing is shown visible .
    Am i missing any steps here.
    Regards
    Manoj

    Got the solution in fact it's not a solution it's just an awareness on how the disks are available in fail-over cluster manager.
    1) All the available disks are shown in fail-over cluster manager "storage".
    2) While installation it asks us to add available disks for SQL Server then add accordingly. (Ex: E:drive for data files and L:drive for Log files) 
    3) Once the installation is done you see those disks in MSSQL (SQL Server) group.
    Means when you click on Active node it should show you MSSQL (SQL Server) group in which you can find network name, network ip, E: & L: Drives, SQL Server and Agent services.
    Note: MSDTC and Quorum are also clustered disks which can reside (Preferably Active Node) in any of the nodes but automatically fail-overs to active node in case of any passive node failures.
    Regards,
    Kalyan
    Grateful to your time and support. Regards, Shiva

  • 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

  • CRM Support Package Manager - Add transport request to queue

    Hi,
    I'm applying CRM Support Packages with SP_MANAGER on the production system.
    I already applied these SP on the development system, I performed an SPAU adjustment, selected the corresponding transport request to use it on the production system, but SP_MANAGER didn't asked for this transport on the production system.
    How can I add the SPAU adjustment to the queue with SP_MANAGER ?
    Kind regards,
    Christophe

    Hi,
    That's why I opened this message: in step 1 of the procedure described by the link (http://help.sap.com/saphelp_nw04s/helpdata/EN/de/151042f664e12ce10000000a1550b0/content.htm), the system should ask for a transport request. This is not the case here, despite the fact that the correct setting is set in SPAM.
    Any other idea ?
    That's not a problem since I can use a workaround (import via STMS when the system asks to perform the adjustment), but I wonder why the system doesn't ask for a transport request in the case of a CRM system.
    Kind regards,
    Christophe

  • Upgrade Support  Package Manager Version 7.00/0026

    We are trying to update the SPAM from version 26 to 29 to accommodate the requirement of EHP4 upgrade.
    When we try to update the SPAM it just display's a message "SPAM/SAINT update SAPKD70026 has already been imported successfully"
    We did down load the latest spam from the service.sap.com and we tried to upload it from Application server as well as front-end desktop. We did not get any error. But the SPAM update just display this message and doe's noting.
    Thanks
    Osama

    It says SAPKD70026 is already there in effect and you current version is already 26, did you download and extract the latest version 29 as you are saying ?
    instead download and extract the latest version 33 or 35
    SAPKD70035 SPAM/SAINT Update - Version 700/0035 
    SAPKD70033 SPAM/SAINT Update - Version 700/0033 
    and I hope, you are trying to download as per correct release i.e. 7.00 spam/saint update 700 and that too ABAP version
    check the following link, and go to the marketplace link mentioned in the same page, and then click on download SPAM/SAINT update, you can also see the SPAM/SAINT update tutorial on the same page on marketplace
    and be noted that you are logged in the client 000 with a user copy of ddic or with user having sap_all and sap_new authorizations

  • Support Package Manager 6.20/0015

    I installed an IDES 4.7x200 SR1 System. In the TA SPAM the Support manager seems to be totally outdated (Version 15). In the ServiceWeb of SAP there are only Packages from 17 to 29 available (even with some steps missing). Can I install just the latest SPAM-Update (29)? If not, where can I get Version 16,18.. and so on?
    Thank you!

    How was this problem fixed? We are running into the same problem. Any help will be much appreciated.
    Thanks so much.
    Mario

  • How to find out version, support package, patchlevel of installed j2ee as

    Hello all
    We have PI 7.11 installed and I'd like to know what the support package and patchlevel of our installed j2ee application server is. We would like to post-install NWDI and need to know which are the right SCA-Files for us to download.
    Can anyone tell me where to find this information? I wasn't able to find it (maybe just didn't see it?)
    Thanks in advance
    Renaud

    Thanks Srikanth for your quick reply
    But which "help -> about" are you talking about?
    nwa? ConfigTool? Management Console? JSPM? SAPGUI Client? Elsewhere?
    From SAPGUI-Client I choose System -> Status and click on details button for SAP System data. Here I see:
    SAP_ABA     711     0000
    SAP_BASIS     711     0000
    PI_BASIS     711     0000
    ST-PI     2005_1_710     0003
    SAP_BW     711     0000
    But this is for ABAP stack only.
    In nwa I don't see any HELP -> About
    In nwa/sysinfo I don't see any HELP -> About
    In Config Tool I can see:
    Version: 7.1100.20081120163102.0000
    -> is this the j2ee as version including support package and patchlevel info or is this the version of the config tool itself?
    In JSPM / SDT in Help -> About I can see:
    Client Version 1.4.0
    Server Version 1.4.0
    Server Port 50418
    JSPM Service Version 1.0
    JSPM Host Name localhost
    JSPM Port 50417
    Unfortunately not what I'm searching for as well.
    In SAP Management Console in ? -> About I can see:
    Version:  7110, 21, 15, 51094
    Still not sure where to find the required infos... any other ideas?
    Kind regards
    Renaud

  • Best way to apply Support Packages to Solution Manager

    We have a single instance dual stack for SOLMAN 4 running. I want to apply Suppot packages, I need some suggestion what would be the best way to do this, the way I am thinking to proceed for this is -
    1. Do kernel and igs upgrade thru JSPM
    2. Apply ABAP Support packages and then,
    3. apply JAVA support packages
    Is it possible to apply ABAP support packages with JSPM?
    Any suggestion would be helpful

    Patch your abap stack first then the java...
    No, its not possible to pacth abap with JSPM (JAVA Support Package Manager)
    Regards
    Juan

  • Import Basis Support Package 7.00 error

    Hi All,
    I wanted to apply Basis support package 9 for release 7.00 for our solution manager 4.0 system.
    When i started, it gave an error in the phase ADDON_CONFLICT? stage.. The message is as below:
    Phase ADDON_CONFLICTS_?: Explanation of Errors
    Conflicts were found between the Support Packages that you want to
    import and the Add-Ons installed in the system. To guarantee the
    consistency of your system, the import is interrupted until all Conflict
    Resolution Transports (CRTs) for the listed Support Packages are
    included in the queue.
    To include the CRTs in the queue, proceed as follows:
    - Write down the Support Packages and Add-Ons that have conflicts.
    - Leave this screen by choosing 'Cancel' (F12).
    - Load the CRTs for the Support Packages with conflicts from the SAP
      Service Marketplace or request them from your Add-On supplier.
    - Define the extended queue again in the Support Package Manager.
    - Import the queue. The Support Package Manager executes all steps from
      the beginning.
    If the problem involves an SAP Add-On, see SAP Note 53902, which tells
    you which CRTs resolve the conflicts. Otherwise contact the supplier of
    your Add-On for details on how to proceed.
    The following contains a table of Support Packages for each Add-On for
    which conflicts were detected. The column 'Information on the Conflict
    Resolution' specifies how you can resolve a conflict. For more
    information, select the corresponding 'Information for the Conflict
    Resolution'.
    Conflicts Between Add-On ST 400 and Support Packages
    Software Component   Release      Support Package        Information on
                                                             Conflict Resolution
    SAP_BASIS            700          SAPKB70009             Include CRT
    Can anyone guide me how to proceed.
    Thanks,
    Sailesh K

    Hi Shailesh,
    You are employing one or more Add-Ons in your system, apply patches regularly and want to know how the consistency of your Add-Ons is guaranteed. The list of Add-Ons installed in your system is stored in table AVERS.
    During patch application the SAP Patch Manager (SPAM) checks for conflicts between patches in the queue and the installed Add-Ons. A conflict occurs if an object delivered in a patch is also delivered in an Add-On. If conflicts are detected, SPAM stops processing at step ADDON_CONFLICTS_? and asks the user to load the corresponding CRTs into his system. The attributes of such CRTs match the Add-On id, Add-On release and patch predecessor (i.e. the patch in conflict).
    The patch application can only resume if all CRTs are selected in the patch queue. To resolve a conflict SPAM does not check if the conflicting object is contained in a CRT. It suffices that the corresponding CRT has been selected in the patch queue. All conflicts raised by its patch predecessor(s) are then resolved in one go.
    CRTs were introduced to protect the consistency of Add-Ons during the application of patches, such as Hot Packages and Legal Change Patches (LCP). There are two types of CRTs:
    1. Conflict Resolution Transports (CRT)
    A CRT resolves conflicts between one patch and one version of an Add-On including all previous versions. Example:
    Consider a system where Add-On IS-X is installed. During the application of patches P1 and P2 SPAM detected conflicts between the patches and the Add-On.
    To resolve these conflicts two separate CRTs are required, CRT1 and CRT2. A consistent patch queue looks like this:
        P1
        CRT1
        P2
        CRT2
    SPAM will only let you resume the patch application if you redefine the patch queue containing all four patches. You can see the name of the patch for which a CRT resolves a conflict in the "Predecessor" field in the patch queue dialog.
    2. Collective Conflict Resolution Transports (CCRT) are similar to CRTs but resolve conflicts between several patches and an Add-On. Example:
    Consider the previous example but this time the conflicts between patches P1, P2 and Add-On IS-X are resolved not by two CRTs but by one Collective CRT (CCRT) CCRT1. A consistent patch queue looks like this:
    P1
    P2
    CCRT1
    SPAM will only let you resume the patch application if you redefine the patch queue containing all three patches. The CCRT is added at the end of its highest predecessor, here P2. You can see the highest predecessor for a CCRT in field "Valid to patch#" when you scroll the patch queue dialog to the right.
    Keep in mind that a CCRT describes a range of patches for which conflicts are resolved, with the lower limit being the predecessor and higher limit the highest predecessor.
    Cheers,
    Shyam

  • Support Package Problem

    Hi Experts,
      While applying the support package of BASIS (KB70012) and ABAP (KA70012) in SAP ECC 6.0.we get the following error.
    <i>The import was stopped, since an error occurred during the phase
    DDIC_ACTIVATION, which the Support Package Manager is unable to resolve
    without your input.
    After you have corrected the cause of the error, continue with the
    import by choosing Support Package -> Import queue from the initial
    screen of the Support Package Manager.
    The following details help you to analyze the problem:
        -   Error in phase: DDIC_ACTIVATION
        -   Reason for error: TP_CANNOT_CONNECT_SYSTEM
        -   Return code: 0230
       -   Error message: Cant create any process
    When I go through the command mode and type tp connect <sid> & tp connect <sid> pf=g:\usr\sap\trans\bin\ TP_DOMAIN_S10.PFL
    It’s give the following error.
    G:\usr\sap\trans>tp connect S10
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    This is tp version 372.04.04 (release 700)
    E-TPSETTINGS could not be opened.
    EXIT
    ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.
    Error in TPSETTINGS: transdir not set.
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0208
    tp finished with return code: 208
    meaning:
      error in transportprofil (param missing, unknown,...)
    G:\usr\sap\trans>tp connect S10 pf=G:\usr\sap\trans\bin\TP_DOMAIN_S10.PFL
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    This is tp version 372.04.04 (release 700)
    Connection to Database of S10 was successful.
    punesrv02\usr\sap\trans\tmp\C071023.S10 for transport: ALL: No such file or di
    rectory
    punesrv02\usr\sap\trans\tmp\SLOG0743.S10.LOC: No such file or directory
    PANIC --> exiting
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0212
    tp finished with return code: 212
    meaning:
      could not access file as supposed (see dev_tp or SLOG0743.S10 for more details
    Please help me.

    Hi Sateesh,
    It seems like your transport management system is not configured properly, Just check your CTS. is it configured properly.
    Check your transport directory too.
    when you imort a support patch it creates a file in this location. this message are co,img that means you transport directory is not configured properly.
    \punesrv02\usr\sap\trans\tmp\C071023.S10 for transport: ALL: No such file or di
    rectory
    punesrv02\usr\sap\trans\tmp\SLOG0743.S10.LOC: No such file or directory
    Regards
    Subhash

  • SOLUTION MANGER SUPPORT PACKAGES CRTs ERROR

    Hi all..
    System status: solution manager 4.0/MS SQL/Windows 2003/kernel-159/sapm 027/700/tp version:372.04.29
    When i am applying basis and abap patches(11) then i am getting CRTs error.
    the error message is-
    The import was stopped, since an error occurred during the phase
    ADDON_CONFLICTS_?, which the Support Package Manager is unable to
    resolve without your input.
    After you have corrected the cause of the error, continue with the
    import by choosing Support Package -> Import queue from the initial
    screen of the Support Package Manager.
    The following details help you to analyze the problem
        -   Error in phase: ADDON_CONFLICTS_?
        -   Reason for error: TP_CANNOT_CONNECT_SYSTEM
        -   Return code:
        -   Error message: TP_INTERFACE_FAILURE
    how can I remove this error? please help me urgently.
    thanks
    NANI

    Hi,
    You have to add extra addon (CRT) support pack with SAP Basis support pack. It is necessary for solution manager.
    Please can you tell me which support pack you are installing and what is your system version. (e.g SAP ECC 6.0 or SAP R/3 4.7 etc)

Maybe you are looking for

  • Multiline container table mod in ABAP WD

    Hi,    Looking for a quick guideline for macros/function modules to do the following:- 1] Read a multiline table into ABAP WD from workflow container 2] Append an entry to the table 3] Write the amended table into the workflow container. I have seen

  • Multiple Line Graph

    First off, thanks to kglad for the line graph function I started with, it has been a huge help. Now the step I'm trying to take is 2 fold. First, I'd like to graph more than one line segment on the graph. Right now I am graphing functions f1 and f2,

  • Reg: NFS connectivty at receiver file adapter

    Hi Friends I have a requirement to post files to a file system(3rd party) using NFS connection, the target path is in shared mode and I am able to access that path when i copy that path in RUN(local system). But when I have maintained the same in the

  • Backgroud task of a workflow set to status "ready"

    Hi all, We have a worflow working since some years ago and now suddenly one problem has started to ocurr... sometimes, one of the backgroud steps of this workflow is not processed in backgroud by WF-BATCH as expected but it remain in status "READY"..

  • Aperture doesn't start after Mountain Lion update

    Hi, I've been using Aperture 3 for a while without problems. It's the version that came out last before Aperture went into the app store (and the price was reduced). All updates have been installed since then without any problems. Today I got my new