HR Abap in upgrade

hi friends,
can anyone tell me how hr dynamic, hr infotype and hr scema get impacted while upgradation.
thanks

Hi
Check these two blogs
SAP Upgrade Conflicts -1
SAP Upgrade Conflicts -II
Regards
Pavan

Similar Messages

  • Issue in portal after abap stack upgrade

    Hi,
    Except travel and expenditure, everything is working fine after abap stack upgrade.  we have restarted abap and portal 3-4 times, we use abap ume. we are  getting error:
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 18:57_27/02/12_0004_16184750
    defaulttrace:
    \#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
    System:    &\#39;SAP_LocalSystem&\#39;,
    Attribute: &\#39;client&\#39;.
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         ... 29 more
    #1.5 #00144FF922BF006B00000028000021AF0004B9F256577D3A#1330350388639#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#J2EE_ADM_EDJ#73##ERPDEV_EDJ_16184750#J2EE_ADM_EDJ#d2df5090614511e1cbb100144ff922bf#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###07:16_27/02/12_0004_16184750
    [EXCEPTION]
    #1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
    System:    &\#39;SAP_LocalSystem&\#39;,
    Attribute: &\#39;client&\#39;.
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    #1.5 #00144FF922BF006A0000001E000021AF0004B9F25959F274#1330350439133#com.sap.mw.jco#sap.com/tcwddispwda#com.sap.mw.jco#ESSEMP2#288##ERPDEV_EDJ_16184750#ESSEMP2#907dd803614911e1968500144ff922bf#SAPEngine_Application_Thread[impl:3]_6##0#0#Info##Plain###[WD JCO API] WebDynproExtension.addClientPool(SAP_R3_SelfServiceGenerics_ESSEMP2_EN_useSSO_(J2EE16184700)ID1578814350DB10044082816827940554End_9513223) with lang 'EN' and languages vector {EN,EN}#
    #1.5 #00144FF922BF0062000016D7000021AF0004B9F26C7D264E#1330350760207#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736980#Plain###Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF0062000016D9000021AF0004B9F26C7D286A#1330350760208#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736980#Java###Error! Request failed due to failure of child requests#1#Request failed due to failure of child requests#
    #1.5 #00144FF922BF0062000016DB000021AF0004B9F26C7D2DAC#1330350760209#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Java###Request failed due to failure of child requests
    [EXCEPTION]
    #1#Request failed due to failure of child requests
         at com.sap.tc.cbs.server.dao.impl.Request.checkForFailedChildRequests(Request.java:494)
         at com.sap.tc.cbs.server.dao.impl.Request.capture(Request.java:398)
         at com.sap.tc.cbs.server.proc.RequestHandler.process(RequestHandler.java:138)
         at com.sap.tc.cbs.server.proc.RequestHandler.run(RequestHandler.java:121)
         at com.sap.tc.cbs.server.rt.threads.PerpetualRunnable.run(PerpetualRunnable.java:109)
    #1.5 #00144FF922BF006200001777000021AF0004B9F26FD235FC#1330350816114#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736988#Plain###            Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF006200001779000021AF0004B9F26FD23863#1330350816114#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736988#Plain###            Error! The following error occurred during request processing:The build failed due to wrong or incomplete arguments, passed to the build tool.
    Please check CBS service parameters against manual.#
    #1.5 #00144FF922BF006600001720000021AF0004B9F26FFE4EC5#1330350819004#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##f556c50a614411e19dc200144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 208,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736987#Plain###            Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF006600001722000021AF0004B9F26FFE50DC#1330350819004#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##f556c50a614411e19dc200144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 208,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736987#Plain###            Error! The following error occurred during request processing:The build failed due to wrong or incomplete arguments, passed to the build tool.
    Please check CBS service parameters against manual.#
    #1.5 #00144FF922BF005F0000179B000021AF0004B9F2714FA0E9#1330350841110#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736989#Plain###Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF005F0000179D000021AF0004B9F2714FA2FC#1330350841111#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736989#Java###Error! Request failed due to failure of child requests#1#Request failed due to failure of child requests#
    #1.5 #00144FF922BF005F0000179F000021AF0004B9F2714FA854#1330350841111#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Java###Request failed due to failure of child requests
    [EXCEPTION]
    #1#Request failed due to failure of child requests
         at com.sap.tc.cbs.server.dao.impl.Request.checkForFailedChildRequests(Request.java:494)
         at com.sap.tc.cbs.server.dao.impl.Request.capture(Request.java:398)
         at com.sap.tc.cbs.server.proc.RequestHandler.process(RequestHandler.java:138)
         at com.sap.tc.cbs.server.proc.RequestHandler.run(RequestHandler.java:121)
         at com.sap.tc.cbs.server.rt.threads.PerpetualRunnable.run(PerpetualRunnable.java:109)
    cbs.5:
    #1.5 #00144FF922BF006E00009D0900000EEE0004B9E196C2E0E9#1330278454976#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF006E00009D1100000EEE0004B9E196C49580#1330278455088#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF006E00009D1900000EEE0004B9E196C664FD#1330278455207#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF006E00009D2100000EEE0004B9E196C81B65#1330278455319#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF00310000000000000DA90004B9F0155B9416#1330340708455#/Applications/CBS/Administration##com.sap.tc.cbs.service.CBSFrame#######SAPEngine_System_Thread[impl:5]_82##0#0#Info#1#com.sap.tc.cbs.service.CBSFrame#Java###Starting CBS service on node ...#1#16184750#
    Pls suggest

    Hi James Bond
    From the exception above, it can be seen that the AppIntegrator iView is trying to run on the "SAP_LocalSystem" where it should be running on a "real" backend system.
    Please check what is the System alias in this iView and make sure it points on a backend system which has the same alias in the Portal System landscape.
    Hope that helps,
    Robin Hood.

  • What is the role of an abaper in upgradation project from 4.7 to ecc6.0?

    Hi anybody pls forward  any documentation and ppts to understand the upgradation project
    What is the role of an abaper in upgradation project from 4.7 to ecc6.0?
    what we have to check and we have to upgrade give some guidance
    thanks in advance.

    Hi,
    check the below link..
    http://www.thespot4sap.com/upgrade_guide_v2.pdf
    reward if helpfu.
    Regards,
    Nagaraj

  • ABAP PROXY upgrade from XI 3.0 to PI 7.1

    Hi,
    We are planning to upgrade XI 3.0 to PI 7.1
    We have couple of interfaces with ABAP proxy, the SAP version is ECC Web AS 640.
    What factors do we need to take into account during this upgrade specific to Proxy development?
    Thanks
    Sachin K

    Hey,
    >We are planning to upgrade XI 3.0 to PI 7.1
    System  needs  64 bit OS for PI 7.1 , Will not support 32 bit OS
    Customer Adapters and Adapter modules have to be adjusted and redeployed
    Java Proxies have to be redeployed because JAVA JVM is installed during upgrade and JAVA JDK  not supported at all in PI 7.1
    >upgrade specific to Proxy development?
    For ABAP  Proxy Nothing, If the interfaces does not functions, The regeneration of proxy will do
    Cheers
    Agasthuri Doss

  • BW 3.5 Upgrade to 7.0 ( ABAP OO upgrade required ? )

    We are planning to upgrade from BW 3.5 to 7.0.
    Are we required to upgrade/modify all our ABAP code in the start routines/update rules/transfer rules to the new ABAP Object Oriented code ?
    Would it be possible to migrate all the 3.5 BW objects to 7.0 and leave the ABAP code alone.
    Going forward , we would like to use the new ABAP OO for future routines.
    Any documentation would be great !
    Thanks

    Our plan is do initially do a technical upgrade so that we can migrate all 3.5 objects to 7.0. So in this case we won't need to change the ABAP code.
    But once the technical upgrade is done, we want to leverage the new 2004s functionality (i.e. dataflow, transformations, new type datasources) . In this case we will start writing routines for these 7.0 objects in the new ABAP 00 code.
    I guess my question is can both types of ABAP code live simultaneously or do I  to convert the ABAP code in the 3.5 objects to the new ABAP OO.

  • SAP ECC ABAP STACK UPGRADE

    Hi Everyone,
    I am new to this fascinating world of BASIS and to this forum. This is my second post:
    The situation is I need to upgrade the ABAP stack of my ECC 6.0 (dual stack) system from patch level 14 to 17.
    Thus now, what are the things that I should need to consider, that is:
    Do I need any Kernel Upgrade, or individually the component upgrades will do?
    Any SPAM upgrade required?
    Please do reply and if you know any thread having the same question and solutions please give me the URL of it.

    Hi,
    1. For patching the system, ensure you have a complete backup of the system.
    2. Its safer and best to patch the kernel always before starting patching so that your tp and R3Trans are updated.
    3. Patch the tool SPAM to the latest level before starting the patching of the other components.
    4. Now you can patch the rest of the components either individually or put all of them in 1 stack and patch them at 1 go.
    For further info, refer to http://service.sap.com/instguides->SAP Netweaver-> < Release of your system>-> Maintainence-> SP guides.
    Rgds,
    Soujanya

  • XRPM - CPRXRPM - ABAP Version upgrade

    Hello all;
    The Abap version of CPRXRPM component is reflecting on 0008 at the back end if we check via SPAM.
    Whereas on the portal the same is being reflected as version SP02 under "About xRPM" details page. whereas the Java component is on SP07.
    Why is this discrepancy and will if affect any of the components functioning on the portal and other related components on higher patch level ?
    Also i am facing lot of issues wherein certain fields like external id, description etc are not reflected under portfolio mgmt > administration page. Due to which i am unable to save the portfolio item and proceed ahead.
    Are this issues related to ABAP version not upgraded.
    Finally how do i get the ABAP component to be reflected on portal with consistent patch level atleast with Java component ?
    Please revert back.
    Regards;
    Pratik

    Hey,
    >We are planning to upgrade XI 3.0 to PI 7.1
    System  needs  64 bit OS for PI 7.1 , Will not support 32 bit OS
    Customer Adapters and Adapter modules have to be adjusted and redeployed
    Java Proxies have to be redeployed because JAVA JVM is installed during upgrade and JAVA JDK  not supported at all in PI 7.1
    >upgrade specific to Proxy development?
    For ABAP  Proxy Nothing, If the interfaces does not functions, The regeneration of proxy will do
    Cheers
    Agasthuri Doss

  • ABAP/J2EE upgrade from 7.0 to EHP1...failed at START_J2EE_EP

    Hi experts,
    I'm currently running a dual stack upgrade from 7.0 to EHP1 SR1 on a 32bit windows system.  I'm using SAPup and Jup and I'm currently stuck on the Java step START_J2EE_EP the main clue I get from the logs is "Can't open shared memory administration (rc = 3)"......there's also another similar message with a different return code - " Can't open shared memory administration (rc = -107)"....
    I can't seem to find anything that has resolved the problem.
    Any help would be much appreciated.
    Cheers,
    JB

    Hi Martin,
    Thanks for the info.
    I basically changed the phase list xml file so that I could skip over this step as well as others that depended on waiting for the events from the parallel ABAP upgrade.
    So I was able to finish the uprade successfully.  But I tried to update the java stack with the latest support pack stack and it failed part way through.  Now my server0 won't start......I'll be posting the problem shortly in a new thread.
    Thanks again!
    JB

  • ABAP+JAVA Kernel Upgrade

    Hi,
    I am planning to deploy SPS12 against solution manager system (ABAP+JAVA).
    But I have one quick question on Kernel Upgrade unicode system..
    SPS 12 Minimum Kernel Patch level should be 102, we are at 95 (NW2004s/AIX 5.3)
    Please suggest me the best approach :
    1)))
    1. ABAP Kernel Upgrade
    2. IGS upgrade
    3. Import ABAP Support Packages
    4.Upgrade JSPM Patch
    5.Deploy Java support packages via JSPM
    2)))
    1.Upgrade JSPM Patch
    2.Kernel Upgrade using JSPM
    3.Deploy Java support packages via JSPM
    4.Import ABAP support packages
    I heard that JSPM can import ABAP support packages, is this true (for SPS12)??
    Please advice the best and quick approach at step by step at high level.
    Regards
    Srinivas

    Hello Srinivas,
    As of now, the JSPM cannot be used to apply the ABAP Support packages and it has to be applied separately using the SPAM/SINT. So, I believe the first option mentioned by you is the right way to go ahead.
    Regards,
    Anil K Kunapareddy

  • Upgrading a kernel in ABAP or Java - what is correct for 7.01 and 7.1

    There are a couple ways to upgrade a kernel  depending on ABAP or Java.
    I want to know what is the best safest and approved way to upgrade an ABAP kernel based on 7.01 and 7.1
    I don't want to miss with temporary softlinks because our consultant did that and forgot abut it, which cause a huge problem.
    This is a UNIX 64 bit OS.
    Thanks
    Weyland Yutani

    Hi,
    For doing ABAP kernel upgrade there plenty of resources available. You can refer the following guide for a comprehensive overview with step by step instruction of Kernel upgrade process :-
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70d8838d-cb8f-2c10-7ab8-d1504670fbb8?quicklink=index&overridelayout=true
    Just make sure to check the following points before starting the upgrade :-
    1) Take full backup of existing Kernel directory
       After taking full backup of old kernel directory, check the total no. of files in the backup kernel directory by #ls -al|wc -l & cross check same files exist in the orginal kernel directory. This should be done before starting actual kernel upgrade - just to ensure that after wiping out current kernel dir and then after applying new kernel if there is any issue & you have restore the old kernel then you are not missing any files.
    2) Check the softlinks in the existing kernel directory & keep a screenshot so that after kernel upgrade you can create those links.
    Use #ln -s <remote filesystems to be linked> <local file at Kernel directory>
        e.g :  3> ln -s a b
         sapsys 1 Aug 26 09:34 b -> a
        Thus if you wish then you can create those softlinks manually. This may be required for brtools, TSM etc related softlink depending on your scenario you can recreate the links.

  • Abaper role in Upgradation project

    Pls let me know the Role and Responsibilities of  ABAPER in Upgradation project.

    Murugesh,
    are we people here for only replying your qns?
    we all have own work at our desk also.it is not nesseccery for us to ans your qns.please dont say like this as you are saying.it is community you have to understand how can servive in community.please dont xpect here from anyone to spoon feeding to you.please support SDN.
    Go through this info.
    SAP Implementation:
    SAP Implementation is the whole of processes that defines a complete method to
    implement SAP software in an organization. It is based on best practices and case studies from various literature sources and presents a collection of processes and products that make up a complete implementation method to allow any organization to plan and execute the implementation of SAP (ERP) software. The SAP implementation process is made up out of four main phases, i.e. the project preparation where a vision of the future-state of the SAP solution is being created, a sizing and blueprinting phase where the solution stack is created and training is being performed, a functional development phase and finally a final preparation phase, when the last tests are being performed before the actual go live.
    ABAP Developer Role is to prepare the Technical Specification (based on a Functional Specification given by a Functional Consultant), build the code, Review the code and finally to prepare the Unit Test Cases. Sometimes ABAPer may be asked to do a technical research for an optimal solution.
    SAP Support:
    After a go live, the application needs a maintenance/support to resolve the issues/tickets raised by the users when using the application. Ticket is like a request for changes/bug fixing or a request for a new ABAP Developer Role includes bug fixing/change the existing code due to new requirements/build a new code etc.
    SAP Upgrade:
    SAP Upgrade is nothing but upgrading the software with a superior version which has got more advantages when compared to the earlier version.
    ABAP Developer Role is to go through transactions SPAU/SPDD to compare the old and new version of the change and finally need to activate the relevant one. Some times might need to work on SAP notes too.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d163a7-0301-0010-d9b0-98f692ea3c60
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
    Go through this link.I think you don't need any other doc.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/index.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
    https://websmp102.sap-ag.de/upgrade-bw
    please close this thread after giving mark.
    Rgds,
    Amit

  • Error while upgrading EP 7.0 SP6 to SP9 (in java stack)

    Dear All,
    We have EP 7.0 with SP 6 , OS = Win2k3 SP2, DB = Oracle 10.2 g.
    Upgrading it to Sp9 , we have downloaded dumps from service marketplace.
    Kernel & ABAP stack upgradation have been completed and the system is showing it clearly from status menubar.
    Now we are trying to upgrade JAVA stack from JSPM .At first we selected all the compnents to upgrade from level 6.0(6.2/6.3) to 9.00 but only sap.com/SAP_JAVASL comp got deployed.Other compnents were taking huge amount of time and in the status bar jmon process ids are only increasing one by one. (at one time it reaches to 50000 approx)
    So, we abort the process and tried to deploy one by one , in that case some components got deployed , these are sap.com/BASETABLES,sap.com/CORE_TOOLS,sap.com/JLOGVIEW.
    When we tried to deploy sap.com/SAP-JEE ,  it got deployed with warning (ultimately not happened) and dispatcher was in ACTIVE state(yellow) instead of running.So we abort the process and restart the cluster as well as reboot the system.This makes running the dispatcher.
    Then we tried to deploy sap.com/SAP-JEECOR . It was also taking huge time. So we abort this process also.But now we are facing some problem that is dispatcher is not up.We restart the cluster and reboot the system still the problem persists.
    note:There is no space problem
    **)disp+work.exe's status is Active instead of running
    **)Both msg_server & igsdw.exe are running
    **)From portal it is showing dispatcher is running but no server connected
    **)In JSPM log file one error msg is comming :
    service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    java.lang.AbstractMethodError: com.sap.security.core.server.ume.service.UMEServiceFrame.useTxManager()Z
    So how should we proceed as no further deployment is  possible as it needs dispatcher to be up.
    Any help will be highly appreciated in this regards.
    Regards,
    Souren

    Its a network issue

  • Upgrade only Java stack to Ehp1  (SAPehpi)

    Hi Gurus,
    We are currently on PI 7.1,   and is considering to upgrade to Ehp1 (primarily for IDoc packaging feature)
    and since the IDoc packaging feature is delivered thru a Sender IDoc adapter, which means this seats on the Adapter Engine already (Java stack)
    I saw the document for SAPehpi (Upgrading to Ehp1 for a PI 7.1 system) and if i understand it correctly there are two options,
    one  ABAP + JAVA upgrade    and the other is  JAVA only upgrade.
    So does that mean I can upgrade my Adapter Engine (AAE) to Ehp1 using the JAVA only upgrade option?
    My apologies in advance as i have no experience yet in upgrading 7.1 systems
    Thanks

    > So with that, if we stay on 7.1, then we don't have an option for IDoc packaging (IDoc package inbound to PI will be split into individual IDocs, then will have to use an integration process Collect to re-package it as 1) ?
    Even when you apply EhP1, you can use IDoc packaging only, if your sender system is also on SAP BASIS 7.1 EhP1 or SAP BASIS 7.0 Ehp1.
    So you should confirm this first.

  • Your opinion on:  BSP or Java Webdynpro or ABAP Webdynpro?

    Could you please give me your opinion on the business scenario we have here:
    We are implementing SRM 4.0 with backend R/3 4.6C, WAS 6.4 and Portal 6.0. SRM has its typical shopping cart applications mainly for procurement and the workflow trail displaying the approval. The client wants us to build a few custom forms on the web frontend of SRM (or may be in Portal). The idea is to store these forms and display when needed with the status info just like a shopping cart.
    <b>Now the requirements for these forms are as follows:</b>
    1. These forms will have multiple fields which need to have the F4 kind of help. (the F4 options will reside in SRM or R/3)
    2. The form should have some kind of a ALV grid  (autoexpanding feature) which will allow the user to put in multiple line items so that they could submit more items on one form.
    3. Users need to be able to attach a spreadsheet to the form which should not be editable once the form is submitted. The attached spreadsheet should be stored. (We are planning on using Archivelink Filenet for this)
    4. Upon submission, a workflow will be kicked off as per the defined Org structure for approval of the form.
    5. After submission, the user should be able to go and view the approval status of the form and also print the summary of the values that he entered in the form. (may be a smartform could be provided for this)
    We looked at different options to accomplish this task:
    <b>BSP:</b>
    Creating BSP pages and giving access as links to the user on the webfrontend of SRM. Now, if we go the BSP route, we need to develop in SRM as the R/3 4.6 c does not have BSP development capabilities. If we take this approach, I am not sure if all the above requirements (specially like attaching spreadhseets) will be met with BSP pages.
    SAP Webdynpro Java: 
    It seems that the Webdynpro is easier to use because of the graphical tools available. But the only problem if we go this route is that we will have to find a java guy.
    SAP Webdynpro ABAP:
    We currently have WAS 6.4. As per the documentation, the ABAP Webdynpro development tool is available from NW04s onwards. So, we are still not sure if we could use it. But, we want to push towards upgrading if necessary. Being an old time ABAPer, developing ABAP Webdynpro seems do-able. (i know it may not be that easy).
    Last but not the least, DIALOG Program:
    Creating a dialog program in R/3 or SRM seems fairly simple. Then, an iview could be created on the portal for this transaction, though at this point I am not sure how a spreadsheet could be attached and stored within a dialog program.
    The creation of the workflow may not be that bad after the original form is designed. The graphical display of the approval trail might be difficult, but we might get away with a report for that. For printing the details of the form, I guess I could develop a smartform and put out a button on the screen to print it out in the display view.
    Could you please give me your opinion /  best approach for accomplishing this task, keeping in mind the complexities of these new dimension products?
    Thanks
    Sri

    I would say that all four solutions to solving your tasks are technically feasible.  Here are some thoughts that I had however:
    First ABAP Webdynpro: it is true that ABAP webdynpro is only available with Netweaver04s.  04S is still in ramp-up which means that only a subset of the customer base is allow to implement it.  It will not become generally available until later this year (check the service marketplace for current release estimates).  That being said, it probably elimintes WDA as a possiblity for your project unless you are will to wait and to upgrade.
    However having worked with WDA for a while it is probably the best tool to custom develop what you describe.  It has excellent built-in F4 value help.  It also has a damn fine ALV grid implementation.  The spreadsheet could be just as simple as file upload in binary or your could try your hand at office integration.  Finally for the form you could use Adobe Interactive Forms which also has very nice integration into WDA. 
    Now to Dialog Programming: You could of course use dialog programming.  It seems a little bit of a waste to custom build something so large if WDA is in your near future.  There are obvious disadvantages (little OO structure, no MVC, etc).  You would have ALV grid, office integration and of course F4 help.  You could still use Adobe forms if you implement this on the 640 system.  However there are integration points with dialog and Adobe Interactive Forms.  You could still use printed forms however. If you did the dialog program on the 640 system, you could use the integrated ITS to expose it to the web.  The integrated ITS in my experience has quite nice performance although the look and feel remains just like the SAPGui.
    The Java Webdynpro route:  Well you hit the nail on the head - if you don't have a Java programmer already and you don't have the bandwidth to invest in learning Java, this can be a problem.  The Java Webdynpro environment is quite nice.  There are some things I like better than ABAP and some things that ABAP is defintely still better at.  However when it comes to heavy integration with an ABAP backend - ABAP Webdynpro is still the way to go.  Java Webdynpro does have a help feature (OVS), but it isn't "for free" or nearly as nice as the ABAP Webdynpro (perhaps it will get there some day).  That is one of the major advantages of WDA - its closeness to the business data brings several framework advantages like F4 and field help.  WebDynpro Java in 640 also doesn't have an ALV grid implementation.  I am sure that this is something both environments will eventually have, but right now ABAP has the advantage.  On the other hand, Webdynpro Java has equal support when it comes to office integration, file upload, and Adobe Forms support.  You would have a more difficult time integration SmartForms however.
    Finally we come to BSP.  Honestly if I were in your position I would probably choose BSP (unless you could wait for the ABAP Webdynpro upgrade).  You could build a nice MVC OO application using BSP (stateful or stateless).  The BSP product is mature and quite well documented thanks to SDN.  You have the BSP Extensions which when used in Design2003 use the Unified Renderer.  That means that your output will look nearly identical to the same UI elements in Webdynpro.  Also BSP supports portal integration (session management, eventing, and themes). 
    The downside to BSP is that it isn't a full framework (also one of its advantages).  You can insert all your own html and javascript (unlike webdynpro). But this also means that SAP doesn't delivery as many framework services.  For instance there is no ALV or Value Help.  There is no Office Integration or Adobe Forms integration.  There is some farily good Smart Forms integration.  Now the upside- many people have already hit these limitations and overcame them.  In the weblogs on SDN and in a certain SAP Press book (cough, cough) you will find out of the box solutions for many of these problems.  You can find ready to use solutions for Adobe Integration, Office Integration (using Microsoft Office Web Controls), and F4 help.  It will mean investing a little more time up front to get this "home grown framework" up and running - but it is perfectly feasible. 
    There is a learning curve to all these new technologies however.  This sounds like an abmious project.  I wouldn't want to try and tackle this project in any of these technologies if I was new to them.  With Webdynpro or BSP - consider giving yourself time to learn the environment and cut your teeth on some demo apps before jumping into such a huge development.

  • About upgradation

    hi,
        what is sap upgradation, and also please explain the role of an abaper in upgradation project,
    pls explain in detail.

    SAP comes with newer version based on the Business changes that happeneds over a period of time to keep upto date with the latest developments in the world of IT. Over a period of years they will stop the support for older version, currently the support for SAP R/3 4.6 C is till end of 2008/2009 after which it be comes a paid service if you do not upgrade your R/3.
    The role of ABAP in Upgrade mainly depends of change the exisiting code of all BDC prg as the screen names and Fields will be changed from Version to version.
    Compile all the prgs there may be some change in tables/field names which will result in syntax errors. etc...
    Please reward points if useful.

Maybe you are looking for

  • IPhone 5 no data

    Started 3 days ago. LTE was on, now no LTE,4G,or E is present on my phone. I do have full service. I tried turn on/off airplane mode. Reinserting SIM Card, Reseting Data settings. No luck so far..please help!

  • Empty messages in apple mail

    One of the email lists that I subscribe to frequently contains messages with images. It's a moderately high volume list with 20-30 messages per day. Inevitably, a few of those messages with attached images (according to the paperclip icon in the mess

  • IMovie 9 - can't open file

    I uploaded my HD movie to youtube, but now its not in imovie anymore.  I found it on the hard drive (.rcproject file) and moved it to my imovie projects folder on the hard drive.  If i open iMovie it does not show up in my projects.  If i just click

  • CC updates always mess up my lightroom and other programs!!!

    This is my third time that CC update mess up my Lightroom!!! I purchased Lightroom 5 several month ago. For 3 times, after the major updates, lightroom 5 require to re-purchased and messed up everything. Other apps too. I deleted them already. From C

  • Exit Code 24

    I have a new copy of Elements 9 which won't install. Instead I get this message: Exit Code: 24 Summary -------------------------------------- - 0 fatal error(s), 1 error(s), 0 warning(s) ERROR: Following Conflicting processes were running - block:She