Enhancement Pack level

Hi All,
How do i check the enhancement package level of my Netweaver 7.0. I need to ensure it is EHp2.. where do I check it. Any pointers is appreciated and rewarded... thanks very much

Hi
See this thread for more details: how to find which Enhancement pack we are on?
Btw, there is an EHP1 for NW 7.0 coming, but as you said it is not generally available yet.
Best regards, Michael

Similar Messages

How to see enhancment pack level.

Dear All ,
what is enhancment pack?To install new enhancment pack TX-SAINT will be used?How to see curent enhancement pack level?
Regards
Ashok

Dear All,
Its requirment in my company to to upgrade the enhancment pack.I work on patch but i m confused regarding enhancment pack.
Is both are same?Right now my basis patch level is SAPKB70015 Basis Support package 15 for 7.00 .Same with cross aplication componenet SAPKA70015 ABA SUPPORT PACKAGE FOR 15 FOR 7.00.
So i have to increse the patch level.
which TC we use for enhancement pack?
Regards
Ashok

Pack level

Hi,
How can we know the enhancement pack level on HR in ECC6.0 on unix/oracle.
Thanks

> How to find the enhancement pack level on HR in ECC6.0 on unix/oracle.
HR itself (SAP_HR) has (as of now) no enhancement packages. However, the extension "EA-HR" has some.
Check the version (of EA-HR):
600 without enh
601 with enh1
602 with enh2
etc.
Markus

Enhancement Pack

Hi,
Currently we are on release 700 with
SAP_ABA - SAPKA70020,
SAP_BASIS - SAPKB70020
PI_BASIS - 2006_1_700
SAP_BW - SAPKW70022.
We would like to upgrade to Enhancement pack 4 on only BI systems and
not other ERP systems, we would like to know what the chanllenges are
and is it possible for only BI system being on EHP4 and not other
systems?
Thanks,
Arvind

Hi,
As such there will be no issue if BI will be on EHP1 and ECC will not be on enhancement package. But as per my experience, you should have both system on Enhancement Package i.e. BI on EHP1 and ERP on EHP4 level.
Thanks
Sunny

Enhancement Pack vs Support Release

HI,
We recently installed ERP 6.0 SR3 and are now being told to install Enhancement Pack 3. My understanding was that SR3 contained EH3 bundled within it so if you downloaded the latest installation you did not have to also do the enhancement pack. Am I correct in this understanding or will I still need to install Enhancement Pack 3? What is the difference between SR3 and Enhancement Pack3?
Thanks
Edited by: Tom Brady on Nov 24, 2008 5:49 PM

SR3 implies a specific support package stack level, which is SPS 11 in this case. OSS note 774615 contains details about the contents. You would still need to install the Enhancement package separately as this adds new functionality that can then be activated. A support stack include corrections and code changes that normally take effect immediately.

Enhancement pack 1 - ABAP 7.0 Preview AS

Hi
Is it possible to install EhP 1 on the preview version of the ABAP stack? I wish to gain access to the new ?Flash Islands technology.
Cheers
Ian

Yes, it is. Enhancement Pack 1 is simply another SP level, so it is the same as doing a regular SP upgrade. You can follow Thomas' directions in these videos .
Apply Support Packages to the SDN ABAP-AS Sneak Preview
Regards,
Rich Heilman

SAP R/3 4.6 B Support pack level for AIX 5.2

Hi,
We have upgraded O.S version from AIX 4.3 to AIX 5.2. Here our environment is SAP R/3 4.6B and DB oracle 8.1.7.
My question: Do we apply any support pack to the system after support pack upgrade. Please find the below support pack level for our current system.
SAP_BASIS      46B           0054    SAPKB46B54
SAP_ABA         46B           0054    SAPKA46B54
SAP_APPL       46B           0054    SAPKH46B54
SAP_HR           46B           0000        -
ST-PI            2005_1_46B    0003    SAPKITLQC3
Please request the feedback.
Thanks & Regards,
Narayana Murthy.

Do we apply any support pack to the system after O.S upgrade ?
( Correction for the below posted mail)

PI 7.1 Enhancement pack 8: still error when referencing java class in xslt

Hi
I am getting an error in PI 7.1 EP 8 Repository when I try to use an xslt in which I make a reference to a java class. The error is:
Transformer Configuration Exception occurred when loading XSLT XCBL_invoice_stylesheet.xsl; details: Could not compile stylesheet
I use this xslt:
<xsl:template match="/" xmlns:util="dk.dongenergy.pi.mapping.Utilities_datetime">
          <html>
<B><xsl:text>Received: </xsl:text><xsl:value-of select="util:getCurrentDateTimeFormatted()"/>
I have imported the java archive successfully and it is working in XI 3.0 and it is working if I comment out the reference to the java class in the xslt.
the java class looks like this:
package dk.dongenergy.pi.mapping;
import java.text.SimpleDateFormat;
import java.util.Date;
public class Utilities_datetime {
*     public static String getCurrentDateTimeFormatted() {*
*          Date now = new Date();*
*          SimpleDateFormat formatter = new SimpleDateFormat("dd MMM yyyy HH:mm:ss");*
*         return formatter.format(now);*
We have applied enhancement pack 8 on PI 7.1 as suggewsted in this note, but that has not done the trick:
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_xi/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31333235363833%7d
Any suggestions?
BR
Mikael

Hi Raj
That gives me this error log:
<br/>
<br/>
javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.UnsupportedClassVersionError: Bad version number in .class file java.lang.RuntimeException: java.lang.UnsupportedClassVersionError: Bad version number in .class file at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:100) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1104.execute(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314) Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:664) at java.lang.ClassLoader.defineClass(ClassLoader.java:509) at com.sap.aii.ib.server.mapping.execution.MappingLoader.findClass(MappingLoader.java:184) at java.lang.ClassLoader.loadClass(ClassLoader.java:350) at java.lang.ClassLoader.loadClass(ClassLoader.java:295) at com.sap.engine.lib.xsl.xpath.JLBLibrary.<init>(JLBLibrary.java:33) at com.sap.engine.lib.xsl.xpath.LibraryManager.getFunction(LibraryManager.java:63) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:99) at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:51) at com.sap.engine.lib.xsl.xslt.XSLValueOf.process(XSLValueOf.java:77) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:249) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:249) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:249) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:273) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:470) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:438) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:395) at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:397) at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:239) at com.sap.aii.ib.server.mapping.execution.AbstractMappingTransformer.transform(AbstractMappingTransformer.java:174) at com.sap.aii.ib.server.mapping.execution.XSLTMapping.executeStep(XSLTMapping.java:79) at com.sap.aii.ib.server.mapping.execution.Mapping.execute(Mapping.java:60) at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:87) at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:54) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:139) at com.sap.aii.ibrep.server.mapping.exec.ExecuteIfMapCommand.execute(ExecuteIfMapCommand.java:33) at com.sap.aii.ib.server.mapping.exec.CommandManager.execute(CommandManager.java:43) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:40) at com.sap.aii.ibrep.server.mapping.MapServiceBean.execute(MapServiceBean.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46) ... 32 more javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.UnsupportedClassVersionError: Bad version number in .class file at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:100) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1104.execute(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314) Caused by: java.lang.RuntimeException: java.lang.UnsupportedClassVersionError: Bad version number in .class file ... 33 more Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:664) at java.lang.ClassLoader.defineClass(ClassLoader.java:509) at com.sap.aii.ib.server.mapping.execution.MappingLoader.findClass(MappingLoader.java:184) at java.lang.ClassLoader.loadClass(ClassLoader.java:350) at java.lang.ClassLoader.loadClass(ClassLoader.java:295) at com.sap.engine.lib.xsl.xpath.JLBLibrary.<init>(JLBLibrary.java:33) at com.sap.engine.lib.xsl.xpath.LibraryManager.getFunction(LibraryManager.java:63) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:99) at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:51) at com.sap.engine.lib.xsl.xslt.XSLValueOf.process(XSLValueOf.java:77) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:249) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:249) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:249) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:273) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:470) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:438) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:395) at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:397) at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:239) at com.sap.aii.ib.server.mapping.execution.AbstractMappingTransformer.transform(AbstractMappingTransformer.java:174) at com.sap.aii.ib.server.mapping.execution.XSLTMapping.executeStep(XSLTMapping.java:79) at com.sap.aii.ib.server.mapping.execution.Mapping.execute(Mapping.java:60) at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:87) at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:54) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:139) at com.sap.aii.ibrep.server.mapping.exec.ExecuteIfMapCommand.execute(ExecuteIfMapCommand.java:33) at com.sap.aii.ib.server.mapping.exec.CommandManager.execute(CommandManager.java:43) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:40) at com.sap.aii.ibrep.server.mapping.MapServiceBean.execute(MapServiceBean.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46) ... 32 more
Edited by: mikael lund on Oct 26, 2009 10:51 AM

Purchase requisition document type change after Enhancement pack 4

HI,
we have recently upgraded to enhancement pack 4, after which i am not able to change purchase requisition document type.
In change mode ME52N, the system is allowing to make change but when i goback and display the same PR again the change is not visible in change history also.
I am able to make other changes. facing the problem with change in document type only.
Regards,
Raghu

Hi,
One thing please note that once you select the document type and draft the PR and save the PR, you will get the doc number.
Once you get the document number you cannot change the PR document type .
The reason is document type is linked with number range so it cannot be changed because different seriers of document number is assined to differentdocument type.
And moreover document type is linked with the screen settings also. So I would request you to check the settings for each doc. type

How to Check Enhancement Pack of ECC system

Hi Experts,
I want to check enhancement pack of My SAP R/3 ECC 6.0 system.
Where can i find this information can you please help.
In System --> Status --> in component version i can see "SAP ECC 6.0".
On click of the button provided below this component version , i can see following details:
SAP_ABA             700                     0011     SAPKA70011     Cross-Application Component
SAP_BASIS     700                     0011     SAPKB70011     SAP Basis Component
ST-PI             2005_1_700     0005     SAPKITLQI5     SAP Solution Tools Plug-In
PI_BASIS             2005_1_700     0011     SAPKIPYJ7B     PI_BASIS 2005_1_700
SAP_BW             700                     0011     SAPKW70011     SAP NetWeaver BI 7.0
SAP_AP             700                     0007     SAPKNA7007     SAP Application Platform
LCAPPS     2005_700                     0003     SAPKIBHD03     LC Applications (LCAPPS) 2005_700
SAP_APPL     600                     0006     SAPKH60006     Logistics and Accounting
from this information can you please help me identify my SAp R/3 ECC 6.0 system's enhancement pack version?
Regards,
Ashish Shah

SAP_APPL 600 No EHP
SAP_APPL 601 EHP1
SAP_APPL 602 EHP2
SAP_APPL 603 EHP3
SAP_APPL 604 EHP4
SAP_APPL 605 EHP5
SAP_APPL 616 EHP6
SAP_APPL 617 EHP7
Sorry if i am wrong....thats how i find it...i am an ABAPer.
Regards,
Vishnu

How to print company logo in Excel/ PDF after Enhancement Pack 1?

Hi all,
I realise this topic has come up time and time again but apparently this functionality has changed after Enhancement Pack 1 for BW....?
My problem is simple. I have a series of reports on our portal, formatted using the WAD, and there is a company logo on the reports. When exporting to PDF or excel, the logo disappears.
The SAP documentation states that the addition of the logo when exporting was not available previously, but it was planned, and seemed to imply that this would be possible in EHP1.
We have just applied EHP1 to our test system however I cannot find how to switch on this functionality or how to get the logo onto the exported reports. I can't find any documentation on how to do this.
Is anyone else using this after applying EHP1? Is anyone from SAP reading who can tell me where this functionality is??
Thanks!
Mischa

Thanks but this doesn't work. It works exactly as it did before the Enhancement Pack and doesn't automatically display the image.
So I guess I am missing something - my image is a bmp. file, will this work or should I save it as something else?
Are there any settings in the WAD (either in the Web Template itself or on the button to export) which I need to change to be able to display this logo?
Or are there any settings I need to make in the backend of BW after the application of the Enhancement Pack?
Any more ideas please?
Thanks
Mischa

How to find the enhance pack in my current system

Hi,
We have upgraded from 4.6c to ECC 6.00. How to find out the enhancement pack of my current installation.
Thanks in advance
Raman

Have a look into SPAM or System-Ststus
Any component which is be release 6.01 or 6.02 or anything higher then release 6.00 is showing or not, if it is showing then youy EHP has been installed for that components otherwise no EHP is installed.
Regards,
Subhash

RFx Response Submission Outside Firewall in SRM 7 Enhancement pack 1.

Dear Experts,
As you know, the bid response part has been moved to SUS in srm 7 enhancement pack 1 to enable the suppliers to respond to bid invitation from SUS system itself.
Does it mean that the suppliers cannot respond to bid invitation in SRM server directly or there is an option for customers to activate the customizing switch for that?
SUS system may not be used by all suppliers of a buyer.
Could you please throw some light on it?
Thanks and regards,
Ranjan

Hi Ranjan,
Option on if you want the bidder to create response in SRM or SUS is controlled in the transaction type with a field called Bid system
Here choose External supplier system or Internal SAP SRM system.
When you create an RFX you will have a field called Bidder system where you choose External supplier system or Internal SAP SRM system. This field be already populated depending on what is set in your transaction.
Here External supplier system will be your SUS (decoupled concept) and Internal SAP SRM system will be EBP (normal sourcing)
Regards
Sam

Has anyone gone from Netweaver 7.0 to Enhancment Pack 1 on a BW system ?

Would like to know how the change went for you ?   Problem areas ?
Were you using it with Business Objects and Webi, so did you see the improvements in MDX performance ?

Just for anyone's information.   We were told we had to use ERP Enhancement Pack 4 (containing Netweaver Enhancement Pack 1) as we also have SEM and FIN-BASIS components on our systems.
We had to go thru several notes and bypass error messages to get it in to our sandbox, but have it there now. Are starting to test the functionality.   I will post another question about activation for NW Enhp 1, as that is not clear. But I'm am considering this one closed.
Thank you

Enhancement Pack 4: Time Zone Soft Error

We are testing Enhancement Pack 4 in ECC 6.0. We have a few ship-to customer numbers that we use where we use the same cusomer number but update the address from order to order.
When we udpate the Region in the sales order to a region that is not in the current time zone, we get a "Time Zone EST (or whatever time zone is there) is not valid in country US (several possibilities)" soft error. This is not happening in Production or in any of our other test clients; only the client that we are testing Enhancement Pack 4 in.
We've searched config and can't find anything that may be causing this. We've also seen references to note 1505591 that would make this warning go away, but this note appears to be being reworked and is not available.
Does anyone have any suggestions? Thank you!

Execute STZGC in both the clients and compare whether the Time Zone EST is maintained for country US.
thanks
G. Lakshmipathi

Enhancement Pack level

Similar Messages

Maybe you are looking for