Level of patches

as I can know the level of patches that I have?
Thanks

Hi Sanchez,
You can find out what patches (support package) you are on by doing the following:
1. From within your Sapgui, click on the top menu System and then status
2. A popup box appears, click on the magnifying glass icon button within the SAP System data section.
This will display all the support levels you are on for each component.  The one you probably are interested in due to this forum is:
BBPCRM     400     0008     SAPKU40008     BBPCRM
This reads you are on CRM release 4.0 and on support package 8.
Cheers
Andrew

Similar Messages

  • Error while loading data after level 17 patch

    Hi all,
    A week ago we had patch level 17 implemented on our SAP NetWeaver BI 7.0 system. Since then, we cannot load any data to some cubes using update rules. We get "Error when generating the update program" (Message no. RSAU484), status red while loading data.
    I tried activating the update rules
    We get te same error when loading data from a DSO into a cube.
    The strange thing is that it doesn't happen for all the objects in the system. We have troubles loading deltas from 2LIS_12_VCITM (delivery items), 2LIS_13VAITM (sales order items) and from a BI content DSO in assets accountng.
    Please if you have any idea or if this happend to you, i appreciate any suggestion.
    This is not an implementation, these processes are already live for months, and we didtn't have any problems before the patch..
    thanks,
    Andreea

    We ran into same issue & another one during our BI 7.0 SPS15/SP17 upgrade.
    The solution:
    1. Apply 2 notes:
    [Note 1146851 - BI 7.0 (SP 18): Error RSAU 484 when generating update|http://service.sap.com/sap/support/notes/1146851]
    [Note 1152453 - Termination generating InfoCube write program|http://service.sap.com/sap/support/notes/1152453]
    2. Then run program RSDD_RSTMPLWIDTP_GEN_ALL
    to generate the new programs for InfoCubes from the template RSTMPLWIDTP and cleans up the staging table RSUPDINFO per note 1152453.

  • SAP_APPL level 13 patch problem

    Hi experts,
    While applying SAPKH60013,
    It is getting stuck in
    Import phase 'TEST_IMPORT' (07.10.2008, 19:28:01)
    Abort the import due to an error situation (07.10.2008, 19:28:07)
    If ignore test errors
    It gets stuck in IMPORT PROPER phase.
    OUR OS is AIX5.3
    Our DB is Oracle 10.2
    Please help solve this problem
    With regards

    > If ignore test errors
    Did you check the error messages if they can be ignored? Not all can...
    > It gets stuck in IMPORT PROPER phase.
    Check the import logs:
    - SPAM
    - Goto - Import Logs - Queue
    then drill up to the "red error".
    Markus

  • How to determine 640/J2EE Startup Framework Binary Patch Level?

    Hi All,
    We are running BI ABAP with Java Add-in on WAS 640/SUSE/Oracle.
    In the ABAP world, there are many options for determining the current kernel patch level.  Disp+work -v, SYSTEM->STATUS, etc..
    How do I determine the patch level of the J2EE startup framework (ie: jlaunch, jcontrol, etc..)?  If I run these commands with '-version', I get a patch level of 0. From System Information, the Cluster Kernel Version is 6.40 PatchLevel 105424.313. 
    What I am trying to determine is if I have the binaries that map to the latest applied SP (18).  Do I need to download J2EERTOS18.SAR and apply the bits or has that already been done?  Or is the current patch level for the bits fro the J2EERTOS14.SAR file?  Etc...
    Any tips/suggestions?
    Thanks much,
    Greg

    Hi
    You can check the patch number like this;
    D:\usr\sap\FT0\SYS\exe\uc\NTI386>jlaunch -version
    Failed to reserve 1610612736 (0x60000000) bytes before loading DLLs (error 8).
    jlaunch information
    kernel release                700
    kernel make variant           700_REL
    compiled on                   NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10
    compilation mode              UNICODE
    compile time                  Jan 23 2008 20:42:28
    update level                  0
    patch number                  128                         <<< Here is the patch number>>
    source id                     0.144
    While regarding which file(s) to apply, please notice that the files you are not talking like
    J2EERTOS16_1, is part of the J2EE support package stack, which can be applied with JSPM.
    Regarding the kernel, you can alway refer to note 19466, and downlaod the lastest kernel from:
    http://service.sap.com/swdc
       Support Packages and Patches ->
       Entry by Application Group "
       SAP NetWeaver and complementary products"
       SAP NETWEAVER" SAP NETWEAVER 7.0"
       Entry by Component"
       Application Server Java
       ===> SAP KERNEL 7.00 64-BIT UNICODE
    Regards,
    Thunder

  • Why aren't patch changes part of the AU spec?

    I'm working with a Novation Remote25Sl and the new Automap 3 software with Logic. So far, it's kind of working. But kind of not... And it's brought up a question that's nagged me for a while now.
    Why is something as simple as "+/- patch" not a fundamental part of the AU instrument spec? I mean, shouldn't it be dang simple to map a midi controller so that when you're playing MiniMonsta, or the impOSCAR or FM8, etc, you can just hit buttons to go back and forth through the patches without having to grab your mouse?
    We're talking 1980's basic Midi functionality here folks... Anybody out there part of the AU developer community who'd care to comment? I swear, it would make software instruments so much more FUN if they could improve the "no mouse" experience.
    Um, please?
    Any workarounds Im missing? Yes, I know Logic's built in synths have key commands that be assigned to next/previous preset. I use'em all the time. But that's no good for 3rd party AU's. And as I say, wouldn't this be something you'd expect as part of the basic parameters for any instrument? Or do you think they deliberately left it out to discourage people from changing patches in the middle of a track, causing unpredictable CPU spikes, etc?
    Hmmmmm

    While I agree with you (the level of patch handling, although we have massive resources now, is in many other ways inferior to what we had when we were all using MIDI sequencers and hardware instruments) - speaking to instrument developers, realtime patch changing is generally regarded as a headache.
    This is why the favoured approach is to have multiple instruments loaded (eg how Mainstage does patches) and switch between instruments, rather than having one instrument switch patches.
    Now, for most of my instruments, I set them up with Logic settings, specifically so I can have keyboard/MIDI commands to switch patches - but there some instruments that can't be handled like this.
    I wish some DAW developer really took this whole patch/instrument management area for plugins and developed a top-modern, elegant and comprehensive solution.
    Ideally, in Logic please!

  • Java Support Pack Stack - what about additional patches?

    Hi Guys,
    I have applied Java SP stacks many times before so this is not a technical question as such.
    We download the entire SP Stack and apply it via JSPM. But this only updates the system to that stack with patch level 0. For instance, if I apply SP Stack 3, then all the components will have SP3 patch 0. SAP releases bug fixes from time to time in the form of additional patch files like SP3 patch level 1, 2, 3, etc. for individual components but these are obviously not part of the downloaded stack but need to be downloaded separately for each component.
    My question is, is it a good strategy to apply the entire stack as downloaded so this makes all the components to patch level 0 in that stack and then also download all of the latest patch files for each component within that SP level and apply all of them in the next run?
    So I think this should fix all the bugs that SAP has fixed using these patch files so this would save us a lot of time which usually goes wasted in encountering the bugs, finding solutions and maybe even going to SAP just to find out that the latest patch files are released which already contain these fixes.
    So, can someone tell me whether this is a good idea to do it this way? Or is there any downside to this?
    Thanks and Regards,
    Shitij Bagga

    Hi,
    You can apply eaither ways there woun't any problem.
    i mean you can apply directly patch with SP leve or apply the SP level with patch 0
    When ever if we apply the patch for any SP level, it over write all the file with patch file
    Thanks,
    Sreeni.

  • Patches...

    Hi all,
    We installed SAP BW 3.5 on linux ,when we checked --> system -status -component version we found patch levels as...from service market place we found out tht the latest ones ...
    Patch name     || system patch level || latest patch level
    SAP_BASIS -->          9                              21
    SAP_ABA -->             9                              21
    PI_BASIS -->              6                              10
    SAP_BW -->              9                               21
    BI cont -->                  0                               15
    My question is to upgrade to the latest patch level shud we install all the patches one by one for example for SAP_BW present patch level is 9 and latest is 21 ,so to go for latest patch level shud we install 10,11,12,13,...20,21 or is it sufficient if we install patch no 21.
    Pls suggest....its very urgeny
    Thanks all,
    Bob

    Hello Bob,
    You cannot installl Support Package 21 without SP 10-20 applied already or at the same time.
    It is recommended to apply SP according to the stack - multiple components in one run is fully supported. Check Note 672651 for known issues also.
    If you install BI 7.0, there would not be that many patches.
    Best regards,
    Victor

  • I think I did something weird with foundation/server patching

    We've built many SP sites over the last 3 years.  We're now moving in to 2013.  most of our sites are 2010.
    For the old sites, both myself and my colleagues were just learning on the fly how to deploy and patch.  Over the years we've gained a better understanding of both.
    Something I've done though in the past, i don't know how it affects the deployments and I was wondering if someone could shed some light on it.
    We used SharePoint server with internet, mostly.  When patching, we saw that there were two sets of patches, foundation and server.
    We didn't have a full understanding of both but now do.  They are stand alone products.  However, we though they were component levels of the same installation, and for years we've been applying both the foundation patches, and the server patches
    right behind that.  It's worked fine.  We've never received any errors about patching.
    Now that I know better, i'm only deploying server patches to the new 2013 deployments.
    I was asked to add a 3rd server to one of our old farms.  I ran in to a patching mismatch warning when trying to join the farm.  This made me think about how we patched foundation and server even though we're running server.  One of the warnings
    was that those foundation patches were missing.
    So I restarted and used the exact same patches and it worked fine.  Still, i'm wondering what the overall impact of our old patching methods has on the product?
    My hope is that everything in SP foundation is part of SP server, so the patches I made, assuming the same level of patching, only duplicated patching effort, and there are no technical drawbacks to having patched foundation then server on the same environment.
    Anyone know?

    Hi,
    There are some different patches for SharePoint, to better understanding the different patches, I think you can have a look at the following articles which contains the different patches in SharePoint.
    Hey! Should I install this SharePoint patch?
    http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=433
    For example, the “cumulative” part means if you install the August 2012 CU you don’t need install the June 2012 CU first.
    CUs are also cumulative in the sense that the SharePoint Server patch includes the patches for SharePoint Foundation.
    The Project Server CU includes the SharePoint Server and SharePoint Foundation patches as well. You only need to install the CU for the product you have.
    This is a welcome change from SharePoint 2007 where we had to stack the patches.
    Also, CUs contains the patches for all the supported languages which is why they’re so large.
    Thanks,
    Jason
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Jason Guo
    TechNet Community Support

  • Error Applying patch 6728000

    Hi All,
    I have applied the patch 6728000 to my EBS R12 linux and I got the following error:
    Checking if all jobs have their actual and symbolic arguments in sync....
    Done.
    Writing jobs to run to restart file.
    Reading jobs from FND_INSTALL_PROCESSES table ...
    AutoPatch error:
    Invalid status when reading existing table
    Worker 1 has status 'C'
    Telling workers to quit...
    All workers have quit.
    AutoPatch error:
    Error running SQL and EXEC commands in parallel
    Freeing includes hash table
    Freeing fixes hash table
    Freeing basedons hash table
    Freeing entities hash tableHow do I restart applying the patch?
    Do I need to rerun "adpatch" again?
    Thanks a lot

    Thanks again...
    I want to apply patch 7653364 and 8222387
    But it requires the ff:
    1. Required Code levels
    This patch requires additional code levels to have been successfully
    applied to your system before it can be applied. These code levels,
    as at the time that this patch was built, are listed below. Please check
    Oracle Metalink to determine if any of these have been superseded
    * R12.AD.A.delta.4
    * R12.ATG_PF.A.delta.4
    ==========
    How do I know if I have these already in my EBS R12 RUP6 ?
    Thanks a lot

  • Web Disparcher 7.41 patch 43 standalone  redirect not working

    Hello,
    I was hopping to find a solution posted here.  I am using standalone web Dispaterchers pointing to  two NW 7.40  backend systems. SAP Web Dispatcher with a 7.41 patch 43 version.
    w05adm 55> sapwebdisp -v
    SAP Web Dispatcher Version 7.41.0, multithreaded, ASCII, 64 BIT
    kernel information
    system name          =
    kernel release       = 741
    kernel make variant  = 741_REL
    DBMS client library  =
    compiled on          = Linux GNU SLES-11 x86_64 cc4.3.4
    compiled for         = 64 BIT
    compilation mode     = Non-Unicode
    compile time         = Jul 11 2014 23:31:22
    update level         = 0
    patch number         = 43
    source id            = 0.043
    Profile files in the attachment. Trace:
    WebSocketPlugInInit: WebSocket Plugin initialized
    [Thr 47418910971664] IcmAddHiddenService: Hidden service WEBSOCKET started
    [Thr 47418910971664] Started service HOST=WDhost.com,PORT=8100,PROT=HTTP,TIMEOUT=60,PROCTIMEOUT=60
    [Thr 47418910971664] Started service HOST=localhost,PORT=8100,PROT=HTTP,TIMEOUT=60,PROCTIMEOUT=60
    [Thr 47418761521920] SigISetDefaultAction : default handling for signal SIGCHLD
    [Thr 47418761521920] IcmCreateWorkerThreads: created worker thread 0
    [Thr 47418761521920] IcmCreateWorkerThreads: created worker thread 1
    [Thr 47418761521920] IcmCreateWorkerThreads: created worker thread 2
    [Thr 47418761521920] IcmCreateWorkerThreads: created worker thread 3
    [Thr 47418761521920] IcmCreateWorkerThreads: created worker thread 4
    [Thr 47418761521920] IcmCreateWorkerThreads: created worker thread 5
    [Thr 47418761521920] IcmCreateWorkerThreads: created worker thread 6
    [Thr 47418761521920] IcmCreateWorkerThreads: created worker thread 7
    [Thr 47418761521920] IcmCreateWorkerThreads: created worker thread 8
    [Thr 47418761521920] IcmCreateWorkerThreads: created worker thread 9
    [Thr 47418910971664] IcmWatchDogThread: watchdog started
    [Thr 47418918024976] Fri Aug  8 18:12:06 2014
    [Thr 47418918024976] *** ERROR => IcrAttachToServer('!DIAG') failed 4 [icrxx.c      4011]
    [Thr 47418918024976] *** ERROR => IcrAttachToServer('!DIAG') failed 4 [icrxx.c      4011]
    [Thr 47418918024976] *** ERROR => IcrAttachToServer('!DIAG') failed 4 [icrxx.c      4011]
    [Thr 47418918024976] *** ERROR => IcrAttachToServer('!DIAG') failed 4 [icrxx.c      4011]
    When I was open http://WDhost.com:8100/host1/sap/bc/gui/sap/its/webgui?sap-client=001 or http://WDhost.com:8100/host2/sap/bc/gui/sap/its/webgui?sap-client=001
    Service cannot be reached
    What has happened?
    URL call was terminated because the corresponding service is not available.
    Note
    The termination occurred in system with error code 404 and for the reason Not found.
    What can I do?Please select a valid URL. 
    HTTP 404 - Not found
    Your SAP Internet Communication Framework Team
    I tried to update the kernel patch level, but it did not help. I create logon group in my ABAP system.

    Your rules are wrong, if you want to match "/" you have to escape it meaning "\/". That said, you should rather have a DNS alias for each system in order to keep the setup lean.
    Edit: once you have the rule working, you will still either have to configure hostX in the backend as a virtual host or have other rules removing it from the URL. That said I don't think you need that level of complexity, better have distinct DNS aliases then there is no need for that complexity.

  • Output sound level from gramophone and from computer should be the same

    Dear friends,
    Why the output sound level isn't equal if we listen the LP directly from the gramophone (AUX1) or from the computer during the recording the track on the computer?
    We are using The E-MU 0404 USB 2.0 Audio/MIDI Interface:
    http://ixbtlabs.com/articles2/proaudio/emu-0404-usb.html
    http://www.emu.com/products/product.asp?product=10447&nav=features
    and we have connected E-MU with the (gramohone) speakers through the headphone output on the E-MU and turn the headphone level to the maximum, but the sound level is still lower from the same speakers.
    If we compare the track after the recording with the LP on the gramphone is the level of the sound the same/equal.
    So we need to have all three sound levels equal:
    -from the LP form the gramophone
    -from the computer during the recording
    -from our track on the hard disk after the recording
    Thank you for your answer.

    function(){return A.apply(null,[this].concat($A(arguments)))}
    Connecting loudspeakers to the headphone output on the E-mu sounds like completely the wrong thing to do altogether - you should
    only connect headphones to a headphone output, and nothing else at all.
    We will buy the cable as you mentioned and connect it in the line level (S/PDIF).
    function(){return A.apply(null,[this].concat($A(arguments)))}
    Almost certainly you will need to adjust the monitoring levels in Patchmix to get this the way you want it
    Then we will try to adjust the monitoring levels in Patch (I will report if and how did we manage it).
    Our equiptment is:
    ·       turntable Stabi Kuzma audio komponents ( http://www.kuzma.si/AmplioCMS2/public/EnterPublic.cms2?langId=60&request_locale=en_US )
    ·        Rotel Phono equalizer RQ-970BX,
    ·        Rotel Stereo integrated amplifaier RA-9858X
    ·       speakers JMlab Focal Daline 3.1 (nom. impendance 8 Ω, max. power 75 W)

  • SAP-BO BI 4.0 SP2 (Patch 7)...?

    Setting-up a new "Sandbox" server later this week on Windows Server 2008 (R2) - 64 bit OS.
    It looks like the current version I should be deploying is SAP-BO BI 4.0 SP2 Patch 7.
    Do I need to apply Patch 7 - or should I just use the regular SAP-BO BI 4.0 SP2 baseline for this Sandbox...?
    Normally, we only install full SERVICE PACK levels - not PATCH LEVELS.
    Thanks in advance for the advice.

    Hi Mark,
    You would need to install SP2 first followed by Patch 2.7, or Patch 2.8 which is due out today or tomorrow.
    If you can wait then you  could also align with Feature Pack 3 which is the equivalent of SP3, but that is planned for Q1 2012
    The following blog link also details SAP's patching policy.
    http://blogs.sap.com/analytics/2011/10/07/sap-businessobjects-bi-release-plan-update/
    I hope this is a very helpful answer to you.
    Kind regards,
    John

  • Kernel Patches  - currently at 640 patch # 304

    Hi everyone -  I'm having trouble fnding out what Kernal patches I need to upgade to and was wondering if someone could help me out.
    The last ones we installed were kernel part i and part ii (for basis 640) Q3 2008.
    I cant find my way through the support stacaks to find out what the latest is.
    We run on Tru64 UNIX 5.1B
    Does anyone happen to know this?
    Thanks so much for any replies
    disp+work information
    kernel release                640
    kernel make variant           640_REL
    compiled on                   OSF1 V5.1 1885 alpha
    compiled for                  64 BIT
    compilation mode              Non-Unicode
    compile time                  Oct 11 2009 20:11:15
    update level                  0
    patch number                  304
    source id                     0.304
    supported environment
    database (SAP, table SVERS)   610
                                  620
                                  630
                                  640
    operating system
    OSF1 V5.1

    http://service.sap.com/patches
    --> Browse our Download Catalog
    --> Additional Components
    --> SAP Kernel
    --> SAP KERNEL 64-BIT
    --> SAP KERNEL 6.40 64-BIT
    --> TRU64 64bit
    --> #Database independent
    Download here the latest available SAPEXE*.SAR (SAPEXE_347-20000200.SAR)
    choose your database, download the latest SAPEXEDB*.SAR (don't know your database so I can't give you a filename).
    This would update your kernel to patchlevel 347. If you want to use the very latest kernel go back to "#Database independent" and download all the files with a creation date later than SAPEXE_347*.SAR.
    Unpack first the stack files (SAPEXE.SAR, SAPEXEDB.SAR), then all the single files.
    If you use Oracle make sure you also download the BR*tools (DBATOOLS in the Oracle subfolder).
    Markus

  • SLD information about kernel level

    Hi all,
    does anybody know if and where the SLD captures information about the kernel levels (release, patch level etc.) of the registered SAP systems? I am not able to find those anywhere but I know information is at least
    to some degree contained in the SAP Support Packages.
    Thanks in advance!
    kind regards
    elmar

    thanks for the info,
    but actually I am well aware on how to browse the SLD for information. I am just unable to find
    the information about used kernel levels. So either this information is not present in the SLD
    or I am just unable to find it and looking in the wrong places. As a third possibility it might
    be some kind of configuration issue...
    thanks, regards elmar

  • GRC AC patch compatibility with higher RTAs

    Hi Experts,
    Please let me know if GRC AC having lower level patch is compatible with backend having higher level RTA patch or not.
    Example- Backend systems are upgraded to RTA patch 7(VIRSANH 7).
    But as we are having a lot of issues in ERM patch 7, we want ot keep our ERM Production system at pathc level 6 until a fix is released by SAP.
    Please let us know if there would be any issues or it will work fine if we connect GRC patch 6 system to Backend having RTA partch 7.
    Thanks & Regards,
    Sabita

    Hi Sabita,
    There is no backward compatibily supported by ABAP or JAVA versions of GRC today. So, I would recommend you to have ABAP and JAVA on same versions.
    Pursuing the scenario that you have mentioned may lead to some functionality issues.
    Harleen
    SAP GRC RIG

Maybe you are looking for