HCM-IdM integration in Enhancement Pack 4

Hello there
Are any of the BAdI's available for HCM delta extracts and better integration between IdM and SAP target systems put in HCM business functions that are not switched on by default once Enh. Pack 4 is implemented?
Best regards,
Anders

So far the answer seems to be no... ./Anders

Similar Messages

  • HCM - IDM Integration issues

    Hello Experts,
    I am working on the HCM & IDM Integration and I have done the configurations on HCM & VDS as per the Systems Landscape document.
    When I Run the export query from the HCM, The data is not coming to the staging area.
    I have turned on the Operational log trace and reran the query and found the following is logged in the logs. But it is not of much help to understand why the roll back is happening.
    Could anyone face such kind of error earlier ? Any thoughts on how to proceed further !!
    I am on IDM 7.2 SP7
    Thanks,
    Krishna.

    Hello Deepak,
    Thanks for your reply.
    Yes, I am using PERNR to calculate my MSKEYVALUE. But I believe in the current issue, it is not going to that stage at all.
    1. When we run the extract programme from HCM, VDS first writes the data to HCM_Staging_Area identity store to the MX_HCM_EMPLOYEE entry type.
    2. When this happens, based on the event tasks defined on MX_HCM_EMPLOYEE type attribute, the job "Write HCM Employee To SAP Master" will be triggered where the MSKEYVALUE is calculated and be written to Master ID store.
    In the current scenario,VDS is not writing the data to HCM_Staging_Area at all.
    When examined, the logs i got entry rejection as mentioned the screenshot in my initial post.
    ~ Krishna.

  • HCM IDM Integration

    I'm working on integrating HCM with IDM. I came across the following limitations in one of the documents i happened to glance.
    1. When replicating the data to the Identity Center from SAP HCM over the Virtual
    Directory Server, you can only use scheduled synchronization. You can not
    synchronize the data based on events. This is a limitation of SAP HCM.
    2. The delta mechanism is not pre-configured when importing the data from the SAP
    HCM system into the staging area in the Identity Center. A full load is always
    performed.
    Can someone suggest me ways to achieve this integration. Is there are document available?

    Hi Joel,
    in general, the delta mechanism is only availabe if you are using the Business Suite 6.0 Ehp4 and NW IdM 7.1.
    The documentation describes shortly which BADIs have to be activated to use the delta mechanism (usually you will modify the BADI implementation to catch changes of employee master records which are relevant for your IdM installation only):
    Retrieval of Employee-Related Data by SAP ERP HCM 
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/75/28be4785c247828834285cc3aefc11/frameset.htm
    If you are using this delta mechanism you can schedule the LDAP export with a short repetition period - as a result you get something like nearly event driven synchronization between HCM and IdM.
    Kind regards
    Frank

  • GRC -IdM integration (HCM IdM GRC IdM)

    Hi IdM & GRC Gurus,
    We want to implement a scenario where IdM (7.1) gets user data from HCM, followed by Workflow and SoD analysis in GRC (5.3) and Finally IdM performing the Provisioning (HCM > IdM > GRC > IdM), however I donu2019t see any documentation for this exact scenario. If SAP's direction is for IdM being provisioning solution and not GRC (CUP), the above scenario should be implemented. SAP documentation "SAP IdM Compliant Provisioning using GRC Access Control Configuration Guide. PDF" is similar but here GRC (CUP) is doing the final provisioning.
    I have following questions
    1     Which Framework should be imported in IdM to implement IdM - GRC integration, where IdM gets user data from HCM, followed by Workflow and SoD analysis in GRC and Finally IdM performing the Provisioning (HCM > IdM > GRC > IdM)?
    2     GRC Provisioning Framework (GRC 53 Provisioning Framework_Folder.mcc) that is available on SDN, is based on HCM to IdM followed by GRC conducting SoD analysis and provisioning. Can the same framework be used for a scenario where IdM does the provisioning in the last step (same as question 1)?
    3     "If answer to question 2 is yes? What are the changes/customization required to GRC Provisioning Framework (GRC 53 Provisioning Framework_Folder.mcc)? As per the limitations (page 37) mentioned in the document SAP IdM Compliant Provisioning using GRC Access Control Configuration Guide. PDF, ""It is not possible to only carry out a check for Segregation of Duties, without having the
    request provisioned to the GRC Access Control back-ends. It means that the Identity Center
    cannot just ask if a certain entitlement assignment is valid.
    If the request is approved, the accounts and role assignments will always be performed in
    the GRC Access Control back-end systems."" If this is true, how can we impliment HCM > IdM > GRC > IdM (IdM doing provisioning in the end)?"
    4     If GRC Provisioning Framework (GRC 53 Provisioning Framework_Folder.mcc) is implemented along with HCM framework (SAP Provisioning Framework_Folder.mcc) and HCM_Staging_Area_Identity store.mcc, which Identity Store should GRC Provisioning Framework be imported (HCM_Staging_Area OR SAP_Master)?
    Regards,
    Anurag

    Hi Joel,
    within the VDS you create a local user ('HR_USER') and you choose some password. Later while configuring the HCM system you use these credentials to define the connection from HCM to the VDS.
    Kind regards
    Frank

  • Enhancement Pack 2 impact on ESS for ECC 6.0

    We are planning to upgrade one of our systems (evaluation system) from EA-HR 600 to EA-HR 602 (Enhancement Pack 2 SP2)
    There's some ongoing ESS configurations (just ESS) on this evaluation system.
    What is the impact of an Enhancement Pack 2 import/upgrade towards the existing ESS configurations ?
    Has anyone experienced extensive 'overwriting of existing ESS configuration' or does the EnhP 2 introduces new functionalities leaving the existing configurations untouched ?
    Do ESS functional folks have to redo the bulk of their config ?
    Many thanks for any replies.

    Thanks Chris
    Still confused.
    Are you able to tell me what is the latest enhancement pack for ESS, the reason for asking is that I'm looking for more details on the new iViews as contained in Note 1048386 see below
    Thanks
    WB
    In the previous ESS Business Package (BP) version, the links for starting processes were provided in the workset Life and Work Events. With EhP2, the links for starting the processes are provided in the workset that the process belongs to thematically (for example, the process 'Change of Working Time' is provided in the workset 'Working Time'). The following list provides an overview over the processes available in the standard system and the worksets they are assigned to.
    Benefits and Payment
    o Company Loans
    o Membership Fees Sports Club
    o Status Overview
    Working Time
    o Change of Working Time
    o Status Overview
    Own Data
    o Change of Address
    o Personnel File
    o Status Overview
    Life and Work Events
    o Maternity Leave
    o Birth of a Child
    o Termination
    o Status Overview
    The available processes are integrated in the navigation of the ESS Homepage Framework.

  • Enhancement Pack 2 for ESS for ECC 6.0

    Can anyone provide me with document on the new functionality of Enhancement Pack 2 impact on ESS for ECC 6.0?
    Or where I can find this documentation?
    What areas of ESS & MSS does it cover?
    Thanks
    WB

    Thanks Chris
    Still confused.
    Are you able to tell me what is the latest enhancement pack for ESS, the reason for asking is that I'm looking for more details on the new iViews as contained in Note 1048386 see below
    Thanks
    WB
    In the previous ESS Business Package (BP) version, the links for starting processes were provided in the workset Life and Work Events. With EhP2, the links for starting the processes are provided in the workset that the process belongs to thematically (for example, the process 'Change of Working Time' is provided in the workset 'Working Time'). The following list provides an overview over the processes available in the standard system and the worksets they are assigned to.
    Benefits and Payment
    o Company Loans
    o Membership Fees Sports Club
    o Status Overview
    Working Time
    o Change of Working Time
    o Status Overview
    Own Data
    o Change of Address
    o Personnel File
    o Status Overview
    Life and Work Events
    o Maternity Leave
    o Birth of a Child
    o Termination
    o Status Overview
    The available processes are integrated in the navigation of the ESS Homepage Framework.

  • ActiveDirectory - SAP IDM integration in Identity Life cycle Management

    Hi Experts
    In our landscape SAP HCM is supposed to be  the  leading data source and SAP IDM takes identity information from SAP HCM.  From SAP IDM it will provision into Active directory and other third party systems, Sap systems.
    Here are the questions
    1) How  can we leverage on the investment on Active directory after  SAP IDM -Active directory investment ?  I mean after SAP IDM comes to a landscape,  Active directory will only be used to login to domain and for authentication if for java system Active directory have been set as user data source.  What are the other advantages of Active directory- SAP IDM integration as Active directory will not be leading data source and identity information will be in identity store.?
    2) After the user details are taken from SAP HCM system, will  the user record will be created in SAP IDM on Identity store ?  Is it where we actually assign the SAP IDM business role and the related technical role  to the  user? 
    3) Suppose if we assign a business role " employee " , will IDM actually create user id in all target system and assign all the technical roles? . Or we have to manually select each repository for target system in Identity center and  select the privileges and provision it ?  Will there be any automated feature that after assigning the business role to identity in identity store users and roles get automatically provisioned on all the target systems?
    Thank you in advance for your help.

    Hi Matt,
    Thank you very much.
    Only change we have is before approval it should go to GRC AC check all the compliance   and only after that it is approved and it should come back to SAP IDM  .
    I am actually looking for a tutorial which actually shows how you assign a business role and the whole procedure of SAP IDM automatically provisioning to target systems which you have just explained.  I suppose there is no such exact tutorial and I want to know how we can configure this on SAP IDM . Any  specific clues?
    Also  I am describing the exact steps that will follow . Correct me if I am wrong.
    1) User id will be created on AD with same user name and password as it is in Identity store. Will be assigned AD groups
    2) Create same user in Portal and make the user data source as AD and will assign the technical role portal as per the business role definition
    3) create same user in all abap systems and set abap database as user data source and assign the technical role needed as per the business role definition
    4) Create same user in third party systems  and with the privileges on their target systems as per the business role definition.
    With this provisioning stops. I suppose all the above steps will be automatically done by SAP IDM with no manual interaction required after final approval. Correct me if I am wrong.
    So some other information i wanted is
    1) When you assign business role at work flow,  how exactly SAP IDM  know about the target systems that user should be created and  assigned roles and made their authentication source.
    for eg:- for  a  business role "employee"  should get  access to ERP with role X,  AD with group Y, Portal with role Z.  So in work flow when business role employee is assigned  how SAP IDM will know that user should be created on to ERP with role X,  AD with group Y, Portal with role Z. Can you explain technically along with  detail steps? Or how exactly we configure a business role which knows the target systems and their techical roles.
    Thank you once again for the fabulous help . You/Matthew is a tremendous  help in understanding SAP IDM better.

  • Release notes for Enhancement Pack 3

    Hello; when will the Release Notes for Enhancement Pack 3 be available? It is due to come out of rampup very soon and the Release Notes are usually provided then.
    Many thanks.
    Nick Taylor
    EDS SAP Practice EMEA

    Hi Nicholas,
    the release notes are now available:
    Financials:
    http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000698482&
    HCM:
    http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000698507&
    Operations:
    http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000698485&
    Corporate Services:
    https://websmp110.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000698636&
    Industries:
    http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000698506&
    You can also use the central starting point:
    http://service.sap.com/erp-ehp
    Best regards,
    Christian.

  • 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

Maybe you are looking for