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

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.

How to get a dynamic receiver determination based on a table an SAP PI ABAP Stack

Hello folks,
currently I get stuck dealing with a problem about the receiver determination. Let me first describe the Problem: We are using to different SAP ERP- backend system in our test enviroment. But only of this systems is marked as current "actuall" test system. Every once in a while we need to switch between these two systems and mark the other one as the actual test system.
This is the point were it get's a little bit time consuming for me: We have about 50 interfaces were I need to change the receiver from test system A to test system B or vice versa. So I thought about creating a more dynamic way to determine the actual test system:
Therefore I have created a table on the ABAP stack of our PI (7.31 double stack) with just one field that holds the current test system. Now I would like to create a dynamic receiver determination where I call the RFC-function RFC_READ_TABLE. But how can I acess a table from the grapchical mapping of the pi which is stored on the PI?
Is there mybe another fundamental way to retrieve the actuall test system within the mapping?

You can go for enhanced receiver determination, where in you can determine the receiver system using a graphical mapping.
Now in that graphical mapping, use the standard function " RFC Look up" and make a call to bapi and get the actual receiver system.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40b64ca6-b1e3-2b10-4c9b-c48234ccea35?QuickLink=index&…
Step by Step guide to Explain Enhanced Receiver Determination - Application Server Infrastructure - SCN Wiki

How to receive an RFC message in PI ABAP stack from ECC

Hi mates,
I am involved in a scenario in which we want to receive a message in PI (ABAP stack) from ECC (ABAP stack as well).
We created a RFC destination (3) in sender system (ECC) so both stacks could be linked. However, we do not know how to receive this message once we are in PI Abap stack.
In sender system code, a call destination takes place, an this destination stands for the one destination i noted before.
BUT, as this RFC does not exist in PI, i wonder what steps have to be done in PI in order to be able to get the message from ECC.
Hope you guys can guide me through this. Any help
Thanks a lot in advance and best regards,
david

Hi Anand,
No no, i do not want to create any sender RFC Comm Channel.
What i want is to receive (by means of no PI adapter) a message in PI (abap stack) from ECC (abap stack), just by a RFC connection (type 3) between both systems.
I will try to explain in more detail what i want to achieve:
1) A standard SAP program is executed in ECC, at the end, a call destination is done.
2) This destination call, calls an RFC destination that points to PI (RFC dest in SM59, type 3)
(Until now, nothing is done in PI, there is no sender adapter, we just linked both ABAP stacks)
3) In ABAP stack of PI, we want to receive the message, make any transformations and send the target emssage to PI adapters
4) From that moment on, a ordinary PI integration is done.
So my question is, what kind of stepd so i have to perform to get the message from ECC in PI without creating any object in PI (ESR, ID, i mean). Just as if we wanted to receive a RFC message, lets say, in BI (abap side) from ECC.
Hope you got me this time.
Thanks a lot in advance.
Best regards,
david
Edited by: David de Miguel on Dec 27, 2010 11:48 AM

Integrating SAP ECC 6.0 with Microsoft Windows 2003 Active Directory

Hi Gurus,
We are planning to integrate our SAP ECC 6.0 with Microsoft Windows 2003 Active directory.
I have several questions on this:
1. Can i authenticate all the users from SAP
2. It is used only for user authentication or can it be also used for password authentication
ie user can login using his windows password?
3. While integration in SAP does a separate table or a field is created in database.
4.If a employee leaves a company than in SAP is it possible to lock & deactivate the user automatically.
Thanks in advance.
Regards,
Nihar

Hi Mastek,
You should be able to accomodate your needs with respect to integration of your AD accounts with SAP ECC ABAP. This can be done via LDAP connector configuration. The below has info on how to perfrom the configuration at a high level. You will have to integrate, and map certain user data. You may also want to do some LDAP Connector research:
[http://help.sap.com/saphelp_nw70/helpdata/en/10/1a063a15c611d4b61f0000e835363f/content.htm]
On the Java stack - you can also confugure UME to integrate/authenticate with AD:
[http://help.sap.com/saphelp_nw70ehp2/helpdata/en/12/7678123c96814bada2c8632d825443/content.htm]
Hope this helps!

Upgrading SAP ECC 6.0 NW 7.0 (ABAP) to SAP ECC 6.0 NW 7.4 (ABAP + JAVA)

Good Afternoon Gentlemen,
I need your help understanding what's involved on a upgrade we need to perform.
Right now we have a SAP ECC 6.0 with the following components:
SAP_BASIS       701                 0012    SAPKB70112
SAP_ABA          701                 0012    SAPKA70112
PI_BASIS           701                 0012    SAPK-70112INPIBASIS
ST-PI                  2008_1_700    0004    SAPKITLRD4
SAP_BS_FND    701                 0012    SAPK-70112INSAPBSFND
SAP_BW           701                 0012    SAPKW70112
SAP_AP            700                 0028    SAPKNA7028
WEBCUIF          700                 0012    SAPK-70012INWEBCUIF
SAP_APPL        604                 0012    SAPKH60412
SAP_HR            600                 0090    SAPKE60090
ST-A/PI              01N_700ECC   0000
All other components are 600 or 604.
My functional team agreed with the client a upgrade for components 7.4 in order to install SAP BPC.
In my understanding, the current version is a ECC 6.0 on a NW 7.0 EHP1 (ABAP) and since we're being asked to upgrade to components 7.4, we're going to upgrade to ECC 6.0 on a NW 7.4 (we can choose the EHP freely). Is this correct?
Can you also point me the direction for the right documentation in order to do this the smoother way possible?
I thank you all in advance.
Best Regards,
Pedro Gaspar

Hi,
This is SAP Business one system admin forum. Please find correct forum and repost your discussion to get quick response.
Please close this thread here with helpful answer.
Thanks & Regards,
Nagarajan

Upgrade SAP R/3 to ECC 6.0 , Java Stack Upgrade

Hi Experts
We are doing R/3 upgrade to ECC 6.0, we have done technical upgrade,Now we are planning to do Functional Upgrade. like
1. Java Stack
2. Integrated Planning
3.BI Accelarator
4.Data Transfer process
5.Web Reporting Portal
5.New BI content
6.Visual composer
7. Adminstration cockpit
8.New Authorization concept
9.Management Dashboards
Report Designer Etc Etc
At this moment I need to know at what stage we can go for java stack upgrade and what is the pre-requistes for that.
Please give me any links.docs or any previous thread which talk abt java stack will be helpful .
Thanks
Kiran

hope u have posted the same thread
Adding java stack In separate system
Ramesh

EHP4 upgrade question - ABAP Stack and EA-HR

Hi Experts,
My ABAP stack in the ECC system is at 7.01 SP3.
My EA-HR module is at 600 SP38.
We want to upgrade EA-HR to 604 (EHP4) so that we can benefit from some of the MSS functionality but the question is, what ABAP stack level do I need to be on? Is my current version ok or do I need to upgrade?
Can anyone shed light for me on this matter?
Best,
MM

Hi MM,
You can consult SDN Wiki using the following link:
http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOW%20TO%20GET%20RID%20OF%20SP%20STACK%20MISMATCH%20ISSUES
Hope it will be helpful,
Regards
Christine

Error in PHASE PREP_EXTRACT/PREIMP: Upgrade SAP R/3 4.7 to SAP ECC 6.0 EHP4

Hello,
I'm currently in upgrading a SAP R/3 4.7 system to a SAP ECC 6.0 EHP4.
Therefore I followed the Upgrade Guide from marketplace - installation- and upgrade guides - SAP ERP - SAP ERP 6.0 - SAP Enhancement Package 4 for SAP ERP 6.0 - Upgrade Guide SAP ERP including EHP4 SR1 - Unix on MaxDB.
I downloaded media from marketplace/swdc - Installations and Upgrades - SAP Application Components - SAP ERP - SAP ERP ENHANCE PACKAGE - EHP4 FOR SAP ERP 6.0 / NW7.01 - Upgrade.
I'm starting upgrade with upgrade master DVD 51036889_1 and      51036889_2.
Now upgrade breaks down in phase PREP_EXTRACT/PREIMP with error:
Severe error(s) occured in phase PREP_EXTRACT/PREIMP!
Last error code set: Single errors (code <= 8) found in logfile 'PREIMP.ELG'
PREIMP.ELG says:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
R3trans preimport and RETURN CODE in R710VPE.REX
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/REX/SYS/exe/run') or dbms_type ('ADA')"
Kernel is stored in /usr/sap/REX/SYS/exe/run and database is ADA (maxdb).
File R710VPE.REX says:
4 EPU201XBEGIN OF SECTION BEING ANALYZED
4 ETW000 R3trans version 6.13 (release 640 - 17.02.10 - 13:07:00).
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 07.03.2011 - 15:28:36
4 ETW000 control file: /usr/sap/REX/upg/abap/tmp/PREIMPTRANS.CTL
4 ETW000 > import
4 ETW000 > file='/usr/sap/REX/upg/abap/bin/R710VPE.SAP'
4 ETW000 > safeandslow=yes
4 ETW000 > buffersync =yes
4 ETW000 > commit     =1048576
4 ETW000 > importtruncated =yes
4 ETW000 R3trans was called as follows: R3trans -w /usr/sap/REX/upg/abap/tmp/R710VPE.REX -u 1 /usr/sap/REX/upg/abap/tmp/PREIMPTRANS.CTL
4 ETW000 active unconditional modes: 1
2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/REX/SYS/exe/run') or dbms_type ('ADA')"
4 EPU202XEND OF SECTION BEING ANALYZED
Can anybody help me out here?
Regards,
Julia

Hello,
I run 'R3trans -x' command, but there was no problem - connection to database was working.
Problem was following:
Before starting the sdt service on host, I set environment variables JAVA_HOME and LD_LIBRARY_PATH for sidadm. That's not neccessary and that was the problem. Without setting these variables it is working now.
Thanks,
Julia

Upgrading from SAP R/3 4.7 x200 to SAP ECC 6

Our company is planning to upgrade R/3 4.7 EXT 200 to ECC 6.0. We are planning to do the Unicode upgrade on the R/3 4.7 system then do the ECC 6.0 upgrade. Would this be an appropriate way to go about the upgrade? Has anyone done the Upgrade in this fashion, and have you experienced any big problems?

Hi,
as per my knowledge no need to do the uccheck in 4.7,in upgrade we r doing the uccheck in ecc6.0.
Upgrade means we r installing the new software.
The major stages of a technical upgrade can be
1.System preparation and stack level patch upgrade u2013 Basis Team
2.SPDD Phase u2013 ABAP and Functionals
3.Up gradation of the system u2013 Basis Team
4.SPAU Phase u2013 ABAP and Functionals
5.DBACOCKPIT for indexing u2013 ABAP TEAM
6.Issue resolution and error tracking u2013 ABAP and Functionals
7.Z programs corrections u2013 obsolete function modules and objects
Regards,
Madhu

BRF+ Upgrade from JAVA stack to ABAP stack. Tutorials Required.(Beginer)

Dear All,
We are Proceeding with and Upgrade on our JAVA based Stack to ABAP Stack of EHP6.
The new System extensivly uses BRF+ Techonolgy and SAP Workflows.
Could you please Provide certain Basic links to Start of with it? As of now its totally new CONCEPT to start with in coming time for us.
We have skill set avilable in ABAP developemnt,PI,Worklfows and other ABAP object but not so far in BRF+ concept.
If any Tutorails are avaialble then please share across.
PS: I have not been able to Procure " SAP Press Book Availability (BRFplus - Business Rule Management for ABAP Applications)"
Thanks a lot.
Regards
Vishal

Read the papers etc on the Business Rule Framework plus.
Especially take a look at the online training. But be careful with papers for NW 701. This is an old version and you may find stuff in there that is not relevant for you as you are on a much higher release.
There is also a paper that explains how BRFplus can be used in combination with SAP Business Workflow.
Why can't you get the BRFplus book? On the SAP Press page there is also an online version´

Upgrade of Sourcesystem SAP EHP3 SAP ECC 6.0 to SAP EHP4 SAP ECC 6.0

Hi,
I noticed there is a lot of questions on the testing procedures for BI side when Upgrading the source system from R/3 to ECC 6.0. But noticed there aren't many posts on when doing Ehancement Packs. But I believe the process would be more or less the same?
My project is doing an Upgrade of SAP EHP3 SAP ECC 6.0 Stack03 to SAP EHP4 SAP ECC 6.0 Stack07. BI Side is also upgraded, but I am more interested in the impact of the Upgrade's Source System (ECC) on BI.
I believe the amount of impact is less as compared to an upgrade from R/3 to ECC, but there still should be impact to BI somehow.
Basically, from what I have researched, there correct procedure is as below:
Pre-Upgrade
1 - Lock users in ECC
2 - ensure that the Delta queue is cleared in RSA7
3 - check the PI in ECC6.0 ( What is PI???)
3 - stop all loads from BW
Post-upgrade
1 - Check Source System connections
2 - replicate all data sources in ECC (when I do a check connection in RSA1 I get the message "No metadata upload since upgrade" which I believe is due to this step not done yet? Is it ok to replicate all datasources??)
3 - activate all rules thru program (RS_TRANSTRU_ACTIVATE_ALL. Is it ok to activate all transfer strucs?)
4 - run Init w/o Data Transfer for deltas
5- run and then check extraction for full & delta loads
Appreciate if I could your expert inputs on the procedures above? Maybe a more detailed step by step procedure or comments are most welcomed.
Thanks.

Additional information:
I start the upgrade from SAP ECC 6.0 with a dual stack.
SAP advised me to download the following file to start the upgrade
SAPehpi_68-10005800.SAR from the SMP
Download path: Browse our Download Catalog--> Additional Components --> Upgrade tools --> SAP EHPI Installer --> SAP EHP Installer 7.00.
Start the upgrade without the jce_policy_zip extension. This was written in note 1302772 .
Have more luck with it.

Java stack and ABAP stack in upgrading SP

Hi,
pls pardon if it appears silly question. I dont have much knowledge in Basis
I am on XI3.0 with SP 09 and upgrading SP to SP20 from SAP service market place.
How can I identify which is java stack and which is ABAP stack in evrery SP because Java stack can be directly upgraded to SP20 but ABAP stack has to be upgraded one by one (like sp 01..10..11..finally sp20).
Could you pls let me know, from the list of files how can I identify which is ABAP stack and which is java stack ? so that I can first update the ABAP Stack one by one and then move to javastack
thanks,
Dushanth

This was answered yesterday:
Upgrading SP 09 to SP 20

LDAP Configuration for ECC 6.0 ( ABAP Stack only)

Hi,
Can any one guide me with the steps for the LDAP Configuration for ECC 6.0 ( Abap stack only).
Some of my observations are....
I can see the LDAP Support in the Installation master at the following path.
1. Additional Software Life cycle Tasks --> Application Server --> LDAP Support.
But the prerequisites for this task is given as "You must have extended the LDAP schema for the sap data types before.".
When i am goint thru service market place i came across the following note.
Note 888848 - Notes on schema enhancement with RSLDAPSCHEMAEXT.
Thanks,
Tanuj

Dear All,
We are trying to configure the LDAP using with active directory . In the
step of "Synchronization of SAP User Administration with LDAP
Directory"when executing the report"RSLDAPSYNC_USER" we are facing one
error.
Please find the trace file and error screenshot in the attachment.Please help us on
priority.
Please find the Trace log in the below:
RFC destination : LDAP_LDAPSE-01
Tracelevel      :      8,704
F5: Shutdown F6: Clear list F7: Dump status F8: Refresh list
[Wed Jun 26 11:15:38 2013]
Slot 0 (WIPROTECH): >>> ldap_initU(host="abg-mumabc-dc1.abgplanet.abg.com", port=389)
[Wed Jun 26 11:15:39 2013]
Slot 0 (WIPROTECH): <<< ldap_initU() == <NOT NULL> := connected
Slot 0 (WIPROTECH): >>> ldap_set_option(version=3)
Slot 0 (WIPROTECH): <<< ldap_set_option() == 0
Slot 0 (WIPROTECH): >>> ldap_simple_bind_sU(dn="poornataad", password: not initial)
[Wed Jun 26 11:15:40 2013]
Slot 0 (WIPROTECH): <<< ldap_simple_bind_sU() == 0 := success
[Wed Jun 26 11:15:43 2013]
>>>>Required attributes table
Line    0: "CREATETIMESTAMP" (length 15)
Line    1: "MODIFYTIMESTAMP" (length 15)
Line    2: "SAPUSERNAME" (length 11)
<<<<Required attributes table
Slot 0 (WIPROTECH): >>> ldap_search_sU(base="CN=poornataad,CN=Users,DN=abgplanet,DC=abg,DC=com", filter="(&(OBJECTCLASS=user)(SAPUSERNAME=*))", scope=2)
Slot 0 (WIPROTECH): <<< ldap_search_sU() == 91
>>> ldap_msgfree()
<<< ldap_msgfree()
Slot 0 (WIPROTECH): >>> ldap_unbind_s()
Slot 0 (WIPROTECH): <<< ldap_unbind_s() == 0
Please find the error screenshot in the below.
Regards,
Dilip Sampath.CH
+91-9619735957.

Upgrade strategy for SAP ECC 6.0 SPS 12 to EHP4

Hi!
I would like to update a SAP ECC 6.0 system with EHP4.
I am on Windows 64 Bit with Oracle.
My current SP stack of SAP ECC 6.0 is 12.
What is the best timesaving approach to update SAP ECC 6.0 SPS 12 to EHP4?
a) to patch manually with SPAM/SAINT til SAP ECC 6.0 highest SPS (18?) and run SAP EHP Installer to upgrade to EHP4
b) to run SAP EHP Installer that updates SAP ECC 6.0 with highest SPS and upgrade the system to EHP4
Any helpful information will be very appreciated!
Thank you!

Hi Holger,
It's better to start upgrade with EHPI tool only so that downtime will be minimized instead of first doing via SAINT to highest SPS and then EHPI tool.
Also, while starting upgrade with EHPI tool, make sure of below thing:
1) Number of R3trans processes
2) Memory parameter optimization
Also. check SAP note 1143022
Check link: https://websmp201.sap-ag.de/~sapidb/011000358700000293582009E.PDF
Thanks
Sunny

SAP ECC ABAP STACK UPGRADE

Similar Messages

Maybe you are looking for