SAP CLM Eresource patch upgrade

Hello SAP Gurus
I am a basis administrator new to SAP CLM. Can any one give me a brief idea on how to upgarde SAP CLM Ereource patch from 5.1.8 SPS3 to 5.1.8 SPS4?
Thanks
Varun

Hi Varun,
You can upgrade your system by uninstalling the existing version, then check the NW(If deployed onto SAPNW) version and then again deploy the latest version which you want to deploy. After that you need to upgrade the DB schema.
Hope this helps
Regards
Naveen

Similar Messages

  • System Core Dumped after Oracle patch upgrade 9.2.0.6 to 9.2.0.8

    Hi,
    We are continously getting dumps on our BW Central instance server after we did an Oracle patch upgrade from 9.2.0.6 to 9.2.0.8.
    Following is our system environment
    SAP Release.............. "640"
    Application server....... "abci"
    Operating system......... "SunOS"
    Release.................. "5.10"
    Hardware type............ "sun4v"
    Database server.......... "abdb"
    Database type............ "ORACLE"
    Database name............ "ABP"
    Database owner........... "SAPABP"
    SAP kernel............... "640"
    Database version......... "OCI_920 "
    Patch level.............. "175"
    Following below is the Core Dump that is generated for any process chains that we schedule on our BW server
    Runtime Errors         SYSTEM_CORE_DUMPED
    Date and Time          14.04.2008 09:26:17
    ShrtText
         Process terminated by signal 11.
    What happened?
        The current ABAP program had to be terminated because the
        ABAP processor detected an internal system error.
        The current ABAP program "SAPMSSY2" had to be terminated because the ABAP
        processor discovered an invalid system state.
    What can you do?
        Make a note of the actions and input which caused the error.
        To resolve the problem, contact your SAP system administrator.
        You can use transaction ST22 (ABAP Dump Analysis) to view and administer
        termination messages, especially those beyond their normal deletion
        date.
    Error analysis
        An SAP System process was terminated by an operating system signal.
        Possible reasons for this are:
        1. Internal SAP System error.
        2. Process was terminated externally (by the system administrator).
                   Last error logged in SAP kernel
        Component............ "Taskhandler"
        Place................ "SAP-Server awci_ABP_00 on host awci (wp 5)"
        Version.............. 1
        Error code........... 11
        Error text........... "ThSigHandler: signal"
        Description.......... " "
        System call.......... " "
        Module............... "thxxhead.c"
        Line................. 9780
    How to correct the error
        The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
        contains a file called 'core'.
        Save this file under another name.
        If you cannot solve the problem yourself and you wish to send
        an error message to SAP, include the following documents:
        1. A printout of the problem description (short dump)
           To obtain this, select in the current display "System->List->
           Save->Local File (unconverted)".
        2. A suitable printout of the system log
           To obtain this, call the system log through transaction SM21.
           Limit the time interval to 10 minutes before and 5 minutes
           after the short dump. In the display, then select the function
           "System->List->Save->Local File (unconverted)".
        3. If the programs are your own programs or modified SAP programs,
           supply the source code.
           To do this, select the Editor function "Further Utilities->
           Upload/Download->Download".
        4. Details regarding the conditions under which the error occurred
           or which actions and input led to the error.
    Kindly help.
    Regards
    Sachin
    Edited by: Sachin N on Apr 14, 2008 12:26 PM

    No. If the environment would be wrong the system wouldn´t start up.
    Core dumps are in 99 % of the cases program errors (in the SAP kernel or in an interface (libdbora*)), misaligend accesses of data etc.
    If you encounter such an error have a look in the C-Stack. If you can´t see where the error is happening opening an OSS call. Most of those errors are fixed by installing the latest patches for the kernel and the database interface.
    Markus

  • 10.2.0.2 Patch Upgrade issue

    hi,
    SAP was installed on 10.2.0.1 (SuSe Linux Ent 10 ) . now i am applying patch upgrade to 10.2.0.2. when  i am  doing patch the below problem was occured,
    "Unable to create new central inventory at location /oracle/orainventory. A non empty inventory already exists at this location. Please select another location or clean the inventory at /oracle/orainventory."
    please help me on this issue
    Regards
    Ramesh

    Hai,
    Please check the oraInst.loc file has the correct entry or not.
    File oraInst.loc should have the entries similar to the below:
    inventory_loc=/oracle/SID/oraInventory
    inst_group=dba
    Check the permissions of this file as well, atleast the file should have read access to others.
    Also check the permissions of /oracle/SID/oraInventory, it should be owned by ora<sid> user and group dba.
    Regards,
    Yoganand.V
    Edited by: Yoganand Vedagiri on Feb 23, 2009 12:05 PM

  • SAP SCM 5.0 Upgrade

    Starting a forum thread for those of us who are upgrading to SCM 5.0    Please comment on the scope and/or challenges of your project.    Please post any advice.  
    Our upgrade project begins in January.   We will migrate from SCM 4.0 SP 18 to 5.0.    Integrated with R/3 4.6C and NetWeaver BI.  
    I expect our primary challenges will be the evaluation of existing customer exit logic.   Also we plan for several waves of integration tests.
    Regards,
    Mike

    We have just completed the prepare for 3.1 to 5.0.  I have taken my notes from a 3.0-4.1 upgrade and the most recent notes I have found and compiled them into the plan below.  So, basically... this is my best guess.  Good luck!!
    Pre-Upgrade     
    1) SAP GUI must be upgraded to 640 Patch 21     
    2) Run /SAPAPO/ADV_UPGRADE_50 program to check macro compatibility     
    PREPARE STAGE
    3) All transports in APQ must be released     Verification Only
    4) Run RSRV to check number ranges     Run RSRV
    5) Check number range for infoobject 0REQUID - OSS 961512
    6) Execute RSMDCNVEXIT Conversion to Consistent Internal Values - OSS 447341
    ALL STEPS IN PREPARE PROGRAM  - /SAPAPO/OM_LC_UPGRADE_50     
    7) Create number range interval for object IB_SYM_ID in 000 and 001 (SNRO - see note 203446)
    8) Allow multiple values for CDP data in 000 and 001     o1cl - see note 699162
    9) Run /SAPAPO/OM_CDP_41_PREP_CHECK     
    10)Run /SAPAPO/OM_CDP_41_PREP     
    11)Run /SAPAPO/PPM_UTC_PREPARE_DATA02 and convert all PPM's in 000 and 001     
    12)Run /SAPAPO/PPM_UTC_PREPARE_DATA01 and set status (yes) in 000 and 001     
    13)Backup DP Planning Area's
    14)Validate Planning Area backups
    15)Check SNP, DP, and PPDS job streams to make sure they completed successfully     
    16)Run consistency checks     OM17, /SAPAPO/TS_LCM_REORG & /SAPAPO/TS_LCM_CONS_CHECK
    UPGRADE
    17)Enter DDIC user for the RFC connection to BW     OSS 961512
    Basis performs upgrade     
    18)START CIF QUEUES     
    19)Check that user exits are active
    20)call transaction SPAU to adjust modifcations to repository objects     
    21)Regenerate IMG     click on binoculars in IMG and refresh
    22)Run /SAPAPO/RCIFRESTART to restart stuck queues     
    23)Run CIF_DELTA for some same plant \ prod's     
    24)Live Cache VALIDATION (Orders and Inventory) -  STO, Sales Orders Spot checking data against R/3 data
    25)Run program /SAPAPO/SCC_WORKAREA_ACTIVATE     OSS 621192 - Select "retain work area"
    26)Adjust \ recreate variants /SAPAPO/RLCDEL,  /SAPAPO/TS_PAREA_INITIALIZ     
    27)Adjust PA datasources - /SAPAPO/TS_PAREA_EXTR_DS_CHECK OSS 684929
    28)Activate delivered objects - /SAPAPO/TS_D_OBJECTS_COPY     OSS 684929
    29)Activate Infocubes - run report RSDG_CUBE_ACTIVATE     OSS - 588986 Choose Object Version D in section Infocube: Options.
    30)In Transaction SE11, check whether the 'Initial value' indicator is set for the MAINTPROG and USERAPP fields of the RSTSODS table - if it is not set, proceed as described in Note 914536.     OSS 906789
    31)run the RSSM_HASH_ENTRIES_CREATE report for all requests (using the corresponding parallel processing).     OSS 906789
    32)run the RSSTATMAN_CHECK_CONVERT_DTA and RSSTATMAN_CHECK_CONVERT_PSA reports (also using sufficient parallel processing). OSS 906789
    33)Activate update rules and transfer rules     use program RS_TRANSTRU_ACTIVATE_ALL for transfer rules
    34)Validate that R/3 and APO partner profile agreements are active (WE20)      
    35)Change partner profiles status to A (Active) in Classification tab(WE20)     
    36)Validate Remote infocube system assignments     RSA1
    37)Recreate Indexes and Stats on DP Planning Area backup infocubes RSA1
    38)Repair sourcesystems in APO and BW     RSA1
    39)Activate macros by running ZZZ_MACROS_CONS_CHECK     OSS 768433
    40)Validate validity dates for Time Horizon on the Storage Bucket Profiles, Resources, Planning Areas and Calendars     
    41)Delete timeseries on DP planning Area's
    42)Deactivate DP MPOS's     Taking Demand Planning Down
    43)Ensure that the fixing and locking functionality is set correctly for the DP planning areas before starting the restore
    44)Activate the Master Planning Object Structure (MPOS's)     
    45)Build Indexes and Stats for MPOS's     
    46)Re-build the variants for creating CVC's     
    47)Generate the CC's based off of the backup cubes     
    48)Build Indexes and Stats for MPOS     
    49)Create Time Series objects for PA (initialize planning area)      
    50)Turn off Livecache logging     
    51)Load DP planning area's from backup infocubes     
    52)Run planning area consistency checks,  /SAPAPO/TS_LCM_CONS_CHECK, /SAPAPO/TS_LCM_REORG     
    53)Turn on Livecache logging     
    54)Deactivate compatibility mode for macro books with yellow lights SCM 5.0 Upgrade Guide
    55)Convert the note anchor tables- /SAPAPO/TS_NOTES_CONVERT_40 with 'Check Note Anchors' option. OSS 588986
    56)If inconsistencies are found on the step above, then this program needs to be executed. /SAPAPO/TS_GEN_DOCTAB_CHECK      OSS 588986
    57)Run upgrade report for Lifecycle Planning /SAPAPO/RMDP_FCST_LC_UPGRADE     OSS 588986
    58)Create Variants for Proportional Factor Jobs, then execute the program and validate that they were created correctly.     
    59)Adjust existing planning board profile for PPDS      OSS 644295
    60)Update TLB - run /SAPAPO/TLBPRF_TRANS     OSS 707828
    61)Modify infoobjects 9AMATNR and 9ALOCNO to include med txt instead of short txt     RSA1

  • How to do patch upgradation in citrix server ?

    Dear all,
    How to do patch upgradation in citrix server (SAP B1 2005B PL41 to PL49) ?
    Whether i also need to do same in db server ?
    Jeyakanthan

    Hi Jayakanthan,
    Patch Upgrade is done on SAP Server only.After Completion of Patch 49 upgrade in SAP Server
    then open SAP B1 in server machine it start to upgrade DB after completed DB Upgrade
    In Citrix Server open the SAP B1 it start the upgrade process after completed
    restart the citrix server.
    There is no separate Patch instalation in citrix server.
    in Citrix server SAP client only installed so you can just open the
    SAP B1 in citrix server and other client machine also it automatically start to
    upgrade.
    *Close the thread if issue solved.
    Regards
    Jambulingam.P

  • Best Practice: SAPGUI Version and Patch Upgrades

    Hello -
    Does anyone have some thoughts/information on best practices relating to SAPGUI version and patch upgrades.
    Obviously, sometimes upgrades are forced upon us (e.g. 7.10 for Vista) and in other cases it may just be considered "nice to have".
    Either way - it always signifies regression test and deployment effort.  How do we balance the benefit and cost?
    Thanks, Steve

    Hi Steve,
    you're right for the first part, yes, we (usually) patch twice a year.
    Now for the rest
    An uninstall will only happen on release changes (6.20->6.40->7.10), i. e. about every 4-5 years as SAP releases them.
    Patches are applied to the installation server and the setup on the client will only update changed program parts. For example, upgrading 6.40->7.10 took about 10 minutes (incl. uninstall), applying patch 1 less than 5 minutes.
    I recommend, you read the "SAP Frontend Installation Guide - 7.10" which you find at SMP alias sapgui. Navigate to  Media Library - Literature. It explains setup of the installation server (sounds like a big thing, but ain't much more than creating a share), creating packages, applying updates etc.
    Peter
    Points always appreciated

  • Backup error after kernel patch upgrade

    Hi.
    I have a backup problem after the kernel patch upgrade.  I have SAP R3 4.6C on HPUX11.0 with an Oracle 8.17 database.
    I have upgraded kernel patch from 1655 to 2337.
    Afterward, I am getting following backup error:
    BR280I Time stamp 2007-11-06 09.29.01
    BR279E Return code from '/usr/sap/HAD/SYS/exe/run/backint -u HAD -f backup -i /oracle/HAD/sapbackup/.bdwnpztp.lst -t file_online -c': 2
    BR232E 0 of 115 files saved by backup utility
    BR280I Time stamp 2007-11-06 09.29.01
    BR231E Backup utility call failed
    Does anyone know how to correct this?
    Thank you.

    Hi Jun,
    backint is a link file that is in SAP kernel directory which links to the backup client on the server.
    eg:
    lrwxrwxrwx   1 root     other         32 Aug 13  2004 backint -> /usr/openv/netbackup/bin/backint
    As part of kernel upgrade process, the kernel is backed up, mostly on the disk before upgrading. Check if this link exists and recreate it in the kernel directory, if no backup was done, compare it with other systems to get the details of the backint link.
    Cheers,
    Nisch

  • Delta links on applying patches/upgrade.

    Hi,
    I have a basic question. What happens on applying patch/upgrade to the delta linked copies, when the source objects have been updated/upgraded with new SAP changes.
    Will the delta linked object properties get over written by new upgraded (or SAP patches) source objects.
    I have made delta links of the SAP delivered WPC IView container objects and using them in the custom pages. Lets say on applying a patch or upgrade, the orginal source objects are changed. Will those changes undo my changes on target delta linked objects.

    Hi,
    Copying to your namespace is possible but by that you loose all the advantages in the delta-link.
    What exactly are you copying Roles, iView, Pages everything?
    Adding additional delta link layer between the roles and SAP content is a wise step but copying everything will only dupplicate content and will not allow you upgrade safty with SAP features.
    Regards, Elisha
    PCD Team Leader
    SAP

  • Adjustment Modifications after Patch upgrade?

    Hello,
    Is it possible that the Modifications Adjustments (done in SPAU and SPDD and occured due to SAP_BASIS and SAP_ABA patches) be carried out after the patches upgrade?
    To be more clear, instead of Adjusting the Modifications while patch upgrade is in progress can i configure the patch upgrade in SPAM transaction someway that the Modification Adjustments is directly shown to the user upon their login after my patch upgrade?
    Regards,
    Vasu

    Hi Vasu,
    Yes you just need to transport the request to next system.
    Than you don't need to redo the adjustment.
    But some time due to incosystency between the system, you still get some object not adjusted after you apply the request, and for this you need to transport the object from your development or direct adjust.
    After 12 days than when you change  the object, SAP will ask you for the object key, and you need to request the key in SAP MarketPlace before you can change the object.
    Regards,
    Fendi Suyanto

  • SAP SRM Contracts Vs SAP CLM Contract

    Hi SAP Gurus,
    Can you guys please tell me the difference between SAP SRM Contracts and SAP CLM Contracts.
    In which factors SAP CLM serves better than SAP SRM??
    Why SAP CLM came into existence when we have SRM Contracts? What are the draw back and what is not achieved with SRM Contracts?
    Thanks in Advance

    Hello Sanjay
    There are many differences, SAP CLM Contract run in Sourcing and SAP SRM Contracts run in SRM.
    Advantages CLM Contracts:
    - Establish a contract as a result of a project
    - build the draft agreement from a template
    -   - Create your own folder structure to organize your contract attachments
        - Transfer quickly attachments between the different folders
    -   - Download easily multiple attachments with a single click
    - Administrator can create new customer fields (extensions) and customer tables (extension collections) for all      master agreements or specific master agreements
         - New customer fields are immediately available in the UI and as a search parameters 
          - All is done via configuration, therefore no upgrade issues
         - Generation of contract document out of master agreement
         - Template Library with approved legal contract templates for quick contract generation
         -  Possibility to provide end user with flexibility to modify the provided content from the template during contract creation
          - Adjust contract by adding or removing of clauses and sections to the content provided by the selected contract template
          - Multiple content options (alternative clause content) available to provide end user with controlled flexibility
          - Automated transfer of master agreement meta data into generated contact document
          - Creation and transfer of line item table into contract document
    -     - Creation of a unique barcode on the contract header
          - Contract negotiation with clause changes in MS Word are tracked in the contract repository
          - Change of meta data like Agreement Effective Date in MS Word possible and transfer back to master agreement in repository
          - etc
    The are the possibility to integrate CLM contract to SRM Contracts
    Regards

  • Patch upgrade in Source system ECC 6

    Hi,
    We are plannig Patch upgrade in the ECC 6 r/3 System. This is source system for BI7 (NW2004s).
    I want to know, we beibg a BI consultant
    1. What we need to check in ECC on patch upgrade.
    2. What precautions we need to take for better facilitating the patch upgrade in ECC 6
    3. Other related things.
    can someone please reply.

    Hi
    check patch level in BI system :---
    Logon to your SAP System
    SYSTEM>STATUS>Click the search buttion under SAP System Data
    Where you can find your patchelev.
    BI Content and Plug-in Information
    These are the links to get detailed information about BI Content and Plug-in.
    Check the release notes in this link:
    http://help.sap.com/saphelp_nw70/helpdata/en/bc/52a4373f6341778dc0fdee53d224c8/frameset.htm
    Dependencies of BI_CONT Add-Ons: Functional Correspondences
    https://websmp207.sap-ag.de/~sapdownload/011000358700007362962004E/func_corresp.htm
    Dependencies of BI_CONT Add-Ons: Technical Prerequisites:
    https://websmp207.sap-ag.de/~sapdownload/011000358700007362972004E/tech_prereq.htm
    BI Extractors and Plug-in Information:
    http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000682135&
    http://sap.seo-gym.com/copa.pdf
    http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
    /thread/178564 [original link is broken]
    Asset Mgt Data
    http://gnanamax.com/Documents/BI%207.0%20Functional%20Upgrade%20-%20Migration%20points.pdf
    /thread/507115 [original link is broken]
    Go to sap logon pad on the top left side of the logon pad u can see a small click option beside the logon gui for eg: sap logon710 or 640. click on that and select about sap logon there u can c the patch level, build, file name, file version etc,
    Hope it helps
    regards
    gaurav

  • Patch Upgrade - Urgent

    Hi Friends
    We are upgrading patches on our bw machines.We are on patch level 19.Now moving to 21.
    I just want to know what kind of testing do we need to do after patch upgrade?
    Please give me some thoughts with this regards.
    Regards,
    Chama.

    Hi,
    it is recommended that to use latest kernel patch and database patch if available,
    you need to perform this operation on first Development system than to QAS and PRD
    after applying such patch you need to check that sap server is start without problem, check for database,
    such tranasaction is tested by other people like functional/end user may run there tcodes and test it
    regards,
    kausahl

  • Patch Upgrade Process...

    Hi All,
    I have never done the patch upgrade for portal, so want to know the exact procedure.
    We are using EP 7.00 SP9.
    Actually we are facing issues in IE 7.0, so I want to upgrade my portal's patch to SP15 or more (as per SAPu2019s note 981710).
    1. Please tell me whether IE 7.0 will suit the portal 7.00 SP15 or not?
    2. Please give me the Procedure or Pdf or Guide for Patch upgrade.
    Thanks,
    Nikesh Shah

    hi Nikesh Shah,
    i have faced the same problem, but i have solved by the following procedure
    while download the support package stack from SAP service market place,
    you have to select the save as file then it will display two links one is right click to save this table as a CSV file  and another is right click to save this table as a XML file, then right click on XML and choose save target as default name is SPSTab and save this file and copy this file into ..../usr/sap/trans/EPS/in and start the JSPM and then check.
    note: the JSPM automatically first upgrade jspm and return to the JSPM screen, with the status message JSPM deployed, and the remaining components with the  status message NOT AT DEPLOYED, now again continue the JSPM to deployee the remaining components, in this list next JSPM pickup the kernel  and then remaining components to upgrade the system.
    i hope your problem may resolve.
    Thanks
    Bharathi ch.
    Edited by: Bharathi Ch on Aug 5, 2009 12:05 PM
    Edited by: Bharathi Ch on Aug 5, 2009 12:09 PM

  • Repository connect issue after MDM Patch Upgrade

    MDM Expert
    We recently upgraded our MDM patch from SP06 5.5.63.73 to SP06 5.5.65.91
    after patch upgrade we are not able to connect to repository.SAP is saying that we have wong NLS Character set.It should be 'UTF8' or 'AL32UTF8'
    We checked and found that we do not have character set as per SAP Recommendation but everything was working fine before upgrading the patch.As per SAP in new Patch MDM is lokking for Unicode Character set
    SAP is asking to create new DB Instance for MDM.
    If we create new instance for MDM then how we are going to use our existing repository.Our environment is clustered environment and name of MDM DB instance is also mentioned in cluster.We have to use same Instance name.We are also using oracle failsafe
    Creating new instance seems to be risky for Production environment.Currently we are applying the Patch in Sandbox Environment
    has anyone of you faced this problem while upgrading MDM patch, if yes then how you resolve the issue
    Please help
    Thanks
    Deelip

    Solution provided by sAP

  • Null Exception in Family Iview after Patch Upgrade

    Hello
    We have SAP XSS installed on our production portal.
    following was the composition.
    SAP_ESS  603 SP3 
    SAP_MSS  600 SP16 
    SAPPCUI_GP  603 SP3 
    recently we upgraded patch level to
    SAP_ESS  603 SP7 (1000.603.0.7.4.20110124060804) 
    SAP_MSS  600 SP18 (1000.600.0.18.0.20100830054638)  
    SAPPCUI_GP  603 SP7 (1000.603.0.7.0.20100914080506)
    as per the link [https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES]  and SAP note 1521297
    Backend patches remain the same  viz
    EA-HR Release: 604 ,level : 011
    Now when we try to test the Personal Information Iview it gives us the following error
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Access via NULL object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE
    Note: We have already implemented note no 1018036 which reports the above issue.Jcos are working fine , SSo is properly established and User remains valid.
    Thanks
    Surender Dahiya

    Hi,
    The logs from ST22 as as follows:
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
    caught in
    procedure "HRXSS_PER_CLEANUP" "(FUNCTION)", nor was it propagated by a RAISING
    clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component.
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
    Other ESS applications are working fine.Issue is in Family application.Server is also restarted after patch upgradation.
    Please suggest.
    Thanks,
    Surendra

Maybe you are looking for