Solman Stack SP20 to SP27 Update

Dear Experts,
We are going to upgrade solman 7.0 Ehp1 SP20 system to latest sp stack sp27, customer using this system as production for Change Request Management,
Does support package upgrade effect Change Request Management scenarios, after patch update are there any follow up activies for Change Request Management ?
Best Regards

Hi,
For sure as in any Stack installation on Solman you will need to apply central note and also run Solman_setup again but for specific changes in CHARM it is better if you get a Side effect report from Marketplace.
Regards,

Similar Messages

  • SCM SP Stack - Livecache 7.6 update

    Hi
    I have installed an SCM 5 on Windows 2003 64 Bit and MS SQL, I am looking to apply the latest Support Pack stack froim SP 7 to SP 9, I have downloaded the stack and followed the SP stack guide for updating the kernel, ABAP Support packs using SPAM and the JSPM for Java SP.
    As part of the SP stack download, it gave me the Livecache update, we are currently on 7.6.00, this looks like its the patch to 7.6.02, I cannot find any documentation for updating the Livecache in the SP guide documentation or in the SCM install guide, could anyone tell me where there is an SP update guide for Livecache from 7.6.00 or how to perform the update?
    Thanks.

    Hello All,
    -> The meaning of the version numbers changes as of Version MaxDB/liveCache 7.6.
         Please review the SAP Note 972785.
    -> If you would like to update the liveCache/LCA builds please review the
        "Matrix of released LCA builds for SAP LC/LCAPPS 5.0"
        & reference to the update SAP notes at
    service.sap.com/liveCache -> Release Information -> SAP LC/LCAPPS 5.0 - SAP liveCache technology 7.6
    And if you still have any unclear liveCache related questions I recommend you to create the OSS ticket to the component
    'BC-DB-LCA' or 'BC-DB-LVC'.
    If you have further questions/problems with liveCache/MAXDB please post them at
    MaxDB/liveCache forum: SAP MaxDB
    Thank you and best regards, Natalia Khlopina

  • Stacks issue after firmware update 1.2, won't fan anymore only grid.

    This issue was resolved when I updated to the 10.5.2 Leopard OS but now that I've updated the firmware with the most recent update yesterday the stacks function in the dock went back to just being able to show the grid format and when I choose the list format it comes up in a standard list (menu) view not the nice new fan view.
    Has anyone else had this issue yet? Has anyone been able to fix it? I can see from the install log that there were errors and it looks like they were specifically with the dock/stacks portion but I'm not code savvy enough to know how to fix them.
    Any help or suggestions would be greatly appreciated.

    Well, at the risk of insulting your level of expertise - is your Dock on the side instead of the bottom? There's no fan available with side-docked Docks, either in function or the popup menu.
    If that's not the case, try trashing the Dock's plist and see if that makes it behave.
    Please keep in mind we see many, many beginners or otherwise naive users asking questions which have simple answers, and no insult is intended when a suggestion is made that you've already tried; it's hard to assess a writer's knowledge level. When your original post said "and when I choose the list format it comes up in a standard list (menu) view not the nice new fan view" it made it hard to determine your level for 2 reasons: You referred to the "new fan view" which is not new in 10.5.2, the upgrade you said you just installed, and if you "chose the list format" why would you expect it to show you a fan view? That's probably why Bruce told you to select "fan view". It was probably just a less-than-perfect sentence on your part, but you might be able to see, in retrospect, that it sounded a little newbie-ish.
    Bruce tried to help you and we can only hope that your reaction does not make him hesitate to help someone else lest he get snapped at again!

  • Solman stack for windows 64bit

    Hello experts,
    I am trying to install SAP solution manager 7.02, Please tell me how to select the packages to install the solman in windows 2008 r2 with max db database. In the marketplace it shows n number of choices to download, which one should be downloaded. ??? and how will we integrate it with the sapinst ??

    Hello,
    Please read the guide named Media List SAP Solution Manager 7.1 SR1 available in http://service.sap.com/instguides > SAP Components > SAP Solution Manager > Release 7.1 > Planning. All you need is clearly explained.
    Regards,
    Nicolas

  • Stacks - unable to update applications

    After installing Leopard, I instantly created a couple of stacks of applications. After putting all my photo applications into one stack, I was unable to update Aperture. After trying to install the update, I received an error message stating that I didn't have 1.0 installed, which I did.

    I don't think this is necessarily a defect of Leopard. Under previous Mac OSes, Software Update wouldn't locate applications if they weren't in their folders of install (e.g., Pages, Keynote, and now Numbers should be in the "iWork" folder created by the iWork Installer, and the iLife applications need to be in the "Applications" folder where they are originally installed to be located, rather than being conveniently tucked away inside a user-created "iLife" folder).
    Another way to get the benefit of having a convenient Stack or Stacks AND having Software Update successfully locate your applications is to create your Stack folder(s) as desired and fill them with aliases of your applications. Of course, their icons will display the locator arrows on them when displayed from the Stack(s). Not sure if that'll bother you or not.

  • Automatic Transport Requests and Support Pack Stacks using CHaRM

    Hi Experts,
    Could you please give your valueable inputs on below Requriements :
    1. All Transports Requests needs to be Automatically moved from Solution Manager using CHaRM.
    2. Automatic Support Package Stacks needs to be updated using Solman - CHaRM
    would be helpful if any one could send the documentation on above requirements.
    Regards,
    Vijaysateesh

    Hi,
    >
    > 1. All Transports Requests needs to be Automatically moved from Solution Manager using CHaRM.
    Yes. You can schedule a periodic job (say for example daily 6M) to import all released transport requests from  QAS to PRD of a maintenance cycle/project. This is the task "Import Transport Request(Backround)" given in task list (tcode-SCMA) of a maintenance cycle.

    > 2. Automatic Support Package Stacks needs to be updated using Solman - CHaRM
    I haven't done this. But this is the  task "Import Support Package" given in task list (tcode-SCMA) of a maintenance cycle.
    I hope there is no specific documents for these. It's the same documents related to ChaRM.
    Regards
    Sanjai

  • Upgrade to SolMan 7.1 - LMSERVICE02* and "export regulation"

    During the generation of a queue for the upgrade to 7.1 I get the following error message in MOPZ:
    File download is subject to national export regulations
    File LMSERVICE02_0-20006622.SCA is subject to national export regulations
    LMSERVICE02_0-20006622.SCA is not pushed into download basket due toauthorization failure.
    No file is put in the "export" area of the download basket.
    Everything else can be downloaded and is working fine.
    This is on SolMan 7.0 EHP1 SP27.
    Markus

    > Interesting. Did you find a solution? Was is possible to download the file manually?
    No. I get an "authorization error" in the service marketplace. I have an OSS call open but nobody took it till now.
    > The time I upgraded Sol Man SP01 was available only. Did not have any problems with LMSERVICE01_0-20006622.SCA
    I guess the problem is somewhere in the backend.
    Markus

  • Stacking Images and Ratings: Bug or Feature?

    So, I went through my main library of images (7000+ NEF Raw files), and applied Star Ratings to some of the images, several(50+) of those got 5 stars.
    Later, I got the idea that it would be good to manually stack most of the images into what I would consider logical collections or stacks: command+K on a selected group.
    And this is where I'm consfused.
    I noticed today that a custom search that I created doesn't return all of the images that it should. Here's an example:
    I created a smart album that looks for .nef files with a 5 star rating; another one looks for .psd files with a 5 star rating.
    Anyway, many of the 5 star images no longer show up in this smart album, and it would appear that is related to those images being inside a stack that was manually created. Removing those images from a stack (as an experiment) brought them back into the smart album.
    So, I'm scratching my head. Is this supposed to work this way? Why wouldn't aperture "see" a 5 star image within a stack, even when that stack was manually created without regard to time/date/etc. Why are these images hidden from a smart album?
    I may be missing some fundamental point in the whole stacking concept.
    Has anyone else noticed this behavior?

    FOUND THE COMMON DENOMINATOR!!!
    "The built-in 5-star rating smart album does not work as it cannot find rated images inside stacks."
    As an update to my previous post, I have found the cause of the problem and a PARTIAL workaround. Still a pain in the neck though!
    The built in '5 star', '1 star or Better' and the 'rejected' smart folders actually DO work, PROVIDING (and here's the problem) the rated picture is the FIRST picture in the stack!!
    It only recognises the 1st image in the stack and NO others. This means that your rated image has to be the FIRST one in the stack.
    The problem is that if you have more than one rated image in the same stack, only the FIRST image is taken into account.
    This only applies to the built in smart folders provided at library level.
    All other smart folders that we create should have the 'ignore stack' checkbox checked to view all the images.
    Anyone got a thought on whether this is a feature or a bug?
    Spike

  • JDBC MS SQL Server driver catch SQLException on Update statement

    Hi,
    We change the driver for the BEA WebLogic Type 4 JDBC MS SQL Server driver
    driver=weblogic.jdbc.sqlserver.SQLServerDriver
    url=jdbc:bea:sqlserver://db_name:port_number
    since we use this driver we got an error when the application try to update a field date type with a NULL value.
    Before, we use this driver and we didn't have this error
    driver=com.inet.tds.TdsDriver
    url=jdbc:inetdae:ammtl1sqls01:1961
    The stack is:
    Failed to update - id [updateItemBranch] - parameterObject [xxx.domain.store.Item@b0237c].
    Cause:com.ibatis.common.jdbc.exception.NestedSQLException:
    --- The error occurred in com/gildan/ecrm/persistence/sql/Item.xml.
    --- The error occurred while applying a parameter map.
    --- Check the updateItemBranch-InlineParameterMap.
    --- Check the parameter mapping for the 'availableDate' property.
    --- Cause: java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driver
    Caused by: java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driver

    Carol Villeneuve wrote:
    Hi,
    We change the driver for the BEA WebLogic Type 4 JDBC MS SQL Server driver
    driver=weblogic.jdbc.sqlserver.SQLServerDriver
    url=jdbc:bea:sqlserver://db_name:port_number
    since we use this driver we got an error when the application try to update a field date type with a NULL value.
    Before, we use this driver and we didn't have this error
    driver=com.inet.tds.TdsDriver
    url=jdbc:inetdae:ammtl1sqls01:1961
    The stack is:
    Failed to update - id [updateItemBranch] - parameterObject [xxx.domain.store.Item@b0237c].
    Cause:com.ibatis.common.jdbc.exception.NestedSQLException:
    --- The error occurred in com/gildan/ecrm/persistence/sql/Item.xml.
    --- The error occurred while applying a parameter map.
    --- Check the updateItemBranch-InlineParameterMap.
    --- Check the parameter mapping for the 'availableDate' property.
    --- Cause: java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driver
    Caused by: java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driverHi. You should do two things:
    1 - Contact BEA support for the very latest versions of the weblogic drivers.
    2 - show us the actual jdbc code being called, and the full original stacktrace
    of the SQLException.
    Joe

  • Debugging - Wht is CALL STACK, OVERVIEW etc.

    Hi Experts,
    As am working with user-exits for VA01, VL01N etc., When I want to debug these VA01, VL01N tx, as we know, there is huge SAP code, so ,i guess, in this regard, <i><b>CALL STACK, OVERVIEW, Menu--->debugging updation</b></i> etc, helps to trace out our requirement!! so, pls, clarify that, in debugging mode,
    1) How Can I use CALL STACK or Wht is the role of it?
    2) How Can I use OVERVIEW or Wht is the role of it?
    3) How Can I use mENU-->Debugging Updation or Wht is the role of it?
    Thanq.

    Hi Srikhar,
    Please refer to the below chart for the uses and the roles of all the modes in debugging.
    Display Modes Available Using Pushbuttons
    Fields
    The scrollable field display contains the contents of up to eight fields. The contents of the three most important system fields are always displayed. This is the default display mode in the Debugger. See also:
    Processing Fields
    Table
    Displays the contents of an internal table. This mode allows you to display and edit the entries in an internal table. also:
    Processing Internal Tables
    Breakpoints
    A scrollable display containing up to 30 breakpoints. Next to each breakpoint is a counter. You can also delete breakpoints in this display. See also:
    Managing Dynamic Breakpoints
    Watchpoints
    You can set a watchpoint for a field so that the program is interrupted whenever the value of that field changes. This display mode contains a list of watchpoints, the fields and programs to which they are assigned, the current values of the fields, and the conditions upon which the watchpoint is activated. See also:
    Setting Watchpoints
    Calls
    This mode displays the current sequence of events, and the sequence of calls up to the current breakpoint. The last active call is displayed at the top of the list; previous calls are listed in reverse chronological order. When an event (for example, START-OF-SELECTION) concludes, it is deleted from the display.
    Overview
    This mode displays the structure of the program. It lists its events, subroutines, and modules, and shows which sections belong to which events. It also displays the section currently being processed.
    Settings
    This mode displays the current Debugger settings. You can change the settings by selecting or deselecting various options. For further information, refer to:
    Settings and Warnings
    In case you have any further clarifications,do let me know.
    Regards,
    Puneet Jhari.

  • Stacked image hidden from search

    Today I was missing an image from the catalogue. I knew it had to be there but I couldn't see it.
    I tried to import it again, but the import dialogue indicated that the image had already been imported. Yet, I couldn't see it in the folder where it should have been (all filters turned off, of course).
    I used the library search filter to search for the image using its file name (which I knew as I could see the file on the drive) but to no avail.
    Q: Where was the image?
    A: It was hidden in a stack.
    Yes, perhaps a rookie mistake (I just started using Lightroom), but does anybody else agree that the search for the filename should have unearthed the location of the image in the catalogue? Once I had the image unstacked, I could find it using the filename search.
    I don't think it would be practical for a user to unstack images first before they have a chance finding them through a search.
    I didn't submit this as a bug report because it may be a "feature" rather than a "bug". I invite others to share with me whether they also think it is a bug that stacked images are completely hidden from a search.
    N.B. I find it irritating that I cannot move stacks as a whole to a different folder or collection. What's the point of an aggregation if only the top image is moved/copied?
    The reason wny I mention this second issue here is that either a stack should be treated as a single entity (contained images are not found in searches and are moved with the top image) or it should be treated it as a lose connection between a sequence of images (only the top image gets moved and "connected" images are found through searches (library filters)).

    Hi,
    sdodds wrote:
     this is a BIG BUG in my mind. if I search for an image by name I don't care where it is, I should find it.
    This is rather a design issue that will not be fixed quickly, I'm afraid. In LR, the process of finding an image is tightly associated with the idea of showing it. And the very same code is used in all LR operations when it comes to display images in the Library module. If we want LR to "find" an image located in a collapsed stack, a different way of displaying the filtering results must be implemented.
    This is bothering me since the beginning. I also regularly have problems because of images hidden in a stack. For example, after I have edited a few images in a stack, the XMP files for those files are no longer in sync with the catalog (I have disabled automatic saving of XMP files for performance reasons). If I collapse the stack, hit Ctrl A to select all images in the folder and then Ctrl-S to update the XMP files, the XMP files corresponding to the images hidden in a stack will not be updated. I must remember to expand all stacks (or not collapse them) before doing this. Since we are unable to filter on this criteria (the XMP file status), this is obviously an inconsistent and misleading behavior.
    IMHO (as a former developer), this example demonstrates that there's something wrong in the LR design. The presentation layer (the code showing us the contents of the library) might be too strongly coupled with the data layer (or application layer), the code manipulating the library data. A common problem in software design. Mistakes made in this area during the design phase are difficult to fix because they are not "simple" bugs. They require changes in the program architecture.
    My two cents...
    Patrick

  • How to update JSPM ?

    Hi,
    i'm currently applying EHP1 SP23 for SAP Solution Manager. For the Java stack it is said that i should update JSPM to at least version 7.01.2.1.1. I've downloaded the stack and tried to update JSPM using "Select a package type to apply -> JSPM". Unfortunately he told me that there is no valid update after scanning /usr/sap/trans/EPS/in although i copied all the files + stack.xml into it. Especially JSPM06_0-20002796.SCA and JSPM06P_2-20002796.SCA. I've updated SDM separately but that didn't change anything. Already search OSS and Google but didn't find anything. Current JSPM version is 7.00.14.
    Any hints what's wrong ?
    Regards
    Update: I've installed the JSPM patch mentioned in Note 1145616; JSPM is now 7.00.14.3 but still no change. Deployment Tab -> JSPM shows no update found. Tried to update as Single Support Package as mentioned on help.sap.com but again no applicable update is found.
    Edited by: Wolfgang Pungartnik on May 26, 2010 10:59 AM

    Shitij,
    thanks for clarification.
    I was confused by guide "Update to SAP Solution Manager 7.0 EHP 1 Using SAINT JSPM". On page 17 topic 5 it says "On the Deployment tab page, select the Java Support Package Manager option and update the software component sap.com/JSPM to the target SPS level.".
    Since my target SPS level is 7.01 SP23 i thought i have to update JSPM to that level before applying the rest.
    Well i'm going for the complete stack in one try and see what happens.
    Thanks !

  • Solman and AccessDB

    Hello Team
    Currently we are using AccessDB to maintain contact details of Jobs in SAP environment.
    Could you please let us know if AccessDB can be migrated to solution manager and if yes please guide me to the  place where more details can be found
    .Also to waht other platforms AccessDB can be migrated to other that sharepoint.

    > Any note on using the zones/LDoms? If not, then I can go with normal installation.
    1178190 - SAP on Sun LDOMs
    870652 - Installation of SAP in a Solaris 10 zone
    Those notes don't explain how to set up the LDom or the zone, they explain that it's possible to do so. Those are operating system tasks, consult http://docs.sun.com.
    > Also one technicallity? the solman installation, I have not updated the oracle patch to 2.0( at present 10.2.0.1.0). bcos it never asked for the patch installation. So while ecc installation, I think the installation ask's for the patch cd? right??
    No.
    10.2.0.1 is NOT supported, I wonder why you were able to install SolMan. Read the installation guide, it tells you to
    - install Oracle when requested by sapinst
    - install the latest patchset (which is 10.2.0.4)
    - install the latest interim patches (as of now ~ 28)
    and THEN continue with sapinst.
    The same is true for ERP 6.0 installation. Sapinst will not ask for a database patch CD.
    Markus

  • Support Packs in Solution manager

    Hi,
    I have a query, when I am going to select patches through maintenance optimizer for solution manager I can see the source and target stack level at SMP and when I am putting the source stack(17) and the target stack as latest, solution manager 7.0 EHP 1-23 and going further for download it shows the support packs corresponding to release 701 but not to 700, as my current support pack level for solman is 16(release 700) and I can see there are support pack level up to 21 for release 700, I am confused why it is not taking account the remaining patches for 700 or can I switch directly to 701 and apply the support packs corresponding to release 701.
    Regards,
    Mridul

    Dear Mirdul,
    Check SAP note 1169247. In which it is mentioned that:
    ABAP stack requirements
          You can start the SAINT update from any Solution Manager 7.0 ABAP Stack.
    Java stack requirements
          A direct JSPM update to Solution Manager 7.0 Java Stack 18 and higher is not possible from some of the Java stacks. Therefore, proceed as follows: First, use the JSPM update to update the Java stack only to Solution Manager 7.0 Java stack 17 and then update to the relevant Solution Manager 7.0 Enhancement Package 1 Java stack.
          Take the numbering into account: Solution Manager 7.0 Java stack 17 contains NetWeaver 7.0 Java stack 16.
    Also, check point number 5 in that.
    I think now it will be clear.
    Thanks
    Sunny
    Edited by: Sunny Pahuja on May 13, 2010 6:10 PM

  • Could not stop SDM server. Cannot execute Java process for stopSDM with parameters 50018

    dear SAP
    i have a system Solman 7.1
    i'm upgrading Solman from SP04 to SP13 using SUM (SP12 patch 10) on windows 2012
    and i faced  error  during  Excution phase 5.6  in JAVA Stack.
    phase : Excution - Actual Update
    Error : An error has occurred during the execution of the Deploy software components step.
    Could not stop SDM server. Cannot execute Java process for stopSDM with parameters 50018. Return code condition success evaluated to false for process java.exe for action ACTION_STOP
    You can find more information in the files D:\usr\sap\SOL\SUM\sdt\log\SUM\DEPLOY-COMPONENTS_22.LOG and ProcessOverview.html.
    To troubleshoot the problem use the provided information. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following keywords:
    SUM??execute??component-deploy-700??deploy-components??com.sap.sdt.j2ee.services.servicesimpl.SDMService??class com.sap.sdt.j2ee.tools.sdmmanagement.OperateSdmException
    i try to restart server and killed sapstartsrv..  but the problem is not solved. 
    please let me know what i check more?
    D:\usr\sap\SOL\SUM\sdt\log\SUM\DEPLOY-COMPONENTS_22.LOG
    <!--LOGHEADER[START]/-->
    <!--HELP[Manual modification of the header may cause parsing problem!]/-->
    <!--LOGGINGVERSION[2.0.7.1006]/-->
    <!--NAME[D:\usr\sap\SOL\SUM\sdt\log\SUM\DEPLOY-COMPONENTS_22.LOG]/-->
    <!--PATTERN[DEPLOY-COMPONENTS_22.LOG]/-->
    <!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->
    <!--ENCODING[UTF8]/-->
    <!--LOGHEADER[END]/-->
    Apr 19, 2015 3:59:00 AM [Info  ]: Stopping SDM server...
    Apr 19, 2015 3:59:00 AM [Info  ]: AS Java process ID 11 has been started.
    Apr 19, 2015 3:59:00 AM [Info  ]:   Command line: D:\usr\sap\SOL\DVEBMGS00\exe\sapjvm_4\bin\java.exe -Xmx900M -Djava.ext.dir=d:/usr/sap/SOL/DVEBMGS00/SDM/program/lib;D:/usr/sap/SOL/DVEBMGS00/exe/sapjvm_4/jre/lib/ext -cp . -jar d:\usr\sap\SOL\DVEBMGS00\SDM\program\bin\SDM.jar shutdown Sdmguiport=50018 sdmHome=d:/usr/sap/SOL/DVEBMGS00/SDM/program logfile=D:\usr\sap\SOL\SUM\sdt\log\SUM\OperateSDM_60.LOG
    Apr 19, 2015 3:59:00 AM [Info  ]:   Standard out: D:\usr\sap\SOL\SUM\sdt\log\SUM\OPERATESDM_44.OUT
    Apr 19, 2015 3:59:00 AM [Info  ]: Process ID 11 has been started.
    Apr 19, 2015 3:59:00 AM [Info  ]: Waiting for process ID 11, name java.exe to finish.
    Apr 19, 2015 3:59:02 AM [Info  ]: Process ID 11, name java.exe has been finished, exit code 16.
    Apr 19, 2015 3:59:02 AM [Info  ]: Process ID 11, name java.exe has been terminated.
    Apr 19, 2015 3:59:02 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.j2ee.tools.sdmmanagement.OperateSdmException: Could not stop SDM server.
    Cannot execute Java process for stopSDM with parameters 50018.
    Return code condition success evaluated to false for process java.exe for action ACTION_STOP.
    Best regards..

    Could not stop SDM server. Cannot execute Java process for stopSDM with parameters 50018. Return code condition success evaluated to false for process java.exe for action ACTION_STOP
    Please follow the solution mentioned in the below link.
    Error During Deployment - Java Support Package Manager (OBSOLETE) - SAP Library
    regards,
    pavan

Maybe you are looking for