Not able to create users in identity system -OAM

Hi all,
I am new to OAM and trying to create users from identity system -OAM.
I have logged in as 'orcladmin', who is my 'Master Administrator' and 'Master identity Administrator'.
To create the user, I click on 'User Manager' tab and then 'Create user identity' tab but I get a message saying
"*You do not have sufficient access rights*."
Same message comes up when I try to create groups also.
Please guide me on how I can give these rights to 'orcladmin'.
It will be helpfull if you can specify some links where I can learn the basic consepts of OAM(identity system and access system).
Thanks in advance
Roopa

Hi,
Before you attempt to create a user, you would need to create a workflow in OAM Identity System.
Below is the link which will get you started -
http://download.oracle.com/docs/cd/E15217_01/doc.1014/e12489/workflow.htm#BABEFGAA
-- Pramod Aravind

Similar Messages

  • OIM 9.1.0.2 patch: not able to create user.

    Hi,
    After the 9.1.0.2 patch installation I am not able to create users. The following exception is thrown:
    DOBJ.THROWABLE_IN_SAVE
    Unhandled throwable java.lang.IllegalAccessError in com.thortech.xl.dataobj.tcUSR's save.
    help required..

    Hi,
    I am getting the same error and i have entity adapters on my USER's form.
    Please help.
    Thanks

  • Not able to create user defined field

    hi experts
    i am not able to create a user defined field through, 'user defined field management ' window,
    when i am selecting this window SAP B1 is hanging ,later i need to close the application .what should be the problem ,
    please help me to solve this issue
    thanks in advance
    ajith

    hi
    thanks for reply
    following is the my sap b1 version and PL
    SAP Business One 2007 B (8.60.035)  SP: 00  PL: 08  2007B_CORE_080709_0214
    yes i created user defined fields in employee  master records
    kind regards
    ajith

  • Not able to create user in NW UME

    Hi Experts, I'm having NW 7.1 CE EHP1 SP05 AS JAVA Engine and SAP MII 12.1 is running on NW. I'm having the Super Admin Role and trying to create the new user in UME,but I'm getting the error while doing so. The complete error trace is as below: "Error Creating the User". The complete log detail is as below: Error creating user [EXCEPTION] com.sap.security.core.wd.exception.UmeUiException: at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.handleThrowable(UmeUiFactoryCompInterface.java:3072) at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.createEntity(UmeUiFactoryCompInterface.java:349) at com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface.wdInvokeMethod(InternalUmeUiFactoryCompInterface.java:937) at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339) at $Proxy2071.createEntity(Unknown Source) at com.sap.security.core.wd.maintainuser.MaintainUserComp.saveModifications(MaintainUserComp.java:952) at com.sap.security.core.wd.maintainuser.wdp.InternalMaintainUserComp.saveModifications(InternalMaintainUserComp.java:689) at com.sap.security.core.wd.maintainuser.ModifyUserView.onActionSave(ModifyUserView.java:569) at com.sap.security.core.wd.maintainuser.wdp.InternalModifyUserView.wdInvokeEventHandler(InternalModifyUserView.java:550) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:72) at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:156) at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:91) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:514) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1547) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1361) at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154) at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35) at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127) at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95) at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114) at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:571) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:602) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:523) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:270) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:729) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:256) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:258) at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202) at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38) at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127) at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95) at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140) at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92) at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104) at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87) at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385) at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:425) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45) 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.NoSuchMethodError: com.sap.security.api.logon.ISecurityPolicyFactory.getSecurityPolicyByUniqueName(Ljava/lang/String;)Lcom/sap/security/api/ISecurityPolicy; at com.sap.security.core.jmx.impl.JmxModificationHelper.getSecurityPolicyFromAttributes(JmxModificationHelper.java:2531) at com.sap.security.core.jmx.impl.JmxModificationHelper.createEntity(JmxModificationHelper.java:1588) at com.sap.security.core.jmx.impl.JmxServer.createEntity(JmxServer.java:226) 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.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414) at javax.management.StandardMBean.invoke(StandardMBean.java:323) at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944) at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288) at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400) at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277) at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:340) at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340) at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330) at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:288) at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:813) at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330) at com.sap.security.core.jmx._gen.IJmxServer$Impl.createEntity(IJmxServer.java:534) at com.sap.security.core.wd.jmxmodel.JmxModelCompInterface.createEntity(JmxModelCompInterface.java:249) at com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface.wdInvokeMethod(InternalJmxModelCompInterface.java:788) at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339) at $Proxy2070.createEntity(Unknown Source) at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.createEntity(UmeUiFactoryCompInterface.java:347) ... 77 more
    Thanks in Advance Suresh

    Dear all,
    I was searching the community because I had this same error and there was no answer of how it was fixed. So I'm sending how I fixed today in a customer environment.
    1. Go to portal  http://<portal>/webdynpro/dispatcher/sap.com/tcsecumewdumeadmin/UmeAdminApp
    - select configuration
    - folder "sap system based in abap"
    - do the conection test
    If the test fails, log on in client 001 and change user SAPJSF:
    - assign role SAP_BC_JSF_COMMUNICATION (only this one) and one profile that has permission to RFC logon
    - you can change the password too
    STOP/START ABAP+JAVA
    Go again to the portal above and test connection again. The tests should now be OK.
    2. Go to portal  http://<portal>/irj
    - Log on with administrator user
    Now you should be able to create an user.

  • Not able to create users in portal.

    Hi all,
    Iam trying to create users in portal through User administration but the system says:
    "Current user has user creation permissions in the UME, but cannot create users in the back-end system (data source). The original and possibly untranslated message was: "No active writeable datasource found for user creation, check your Persistence Configuration.".
    I have tried creating in backend system and use in the portal , but the same user does not work there , it says Authentication failed.
    Iam using the admin user j2ee_admin having all the admin rights , i have done all the confuguration settings through this user id only.
    Please help.
    Regards,
    Akash

    Hi Akash,
    check if your data source configuration file is read-only in your ume properties. If it's read/write you may check in the ABAP backend if your communication user (per standard SAPJSF) has write-permissions.  He needs to have role SAP_BC_JSF_COMMUNICATION not SAP_BC_JSF_COMMUNICATION_RO
    see also note 905188
    Cheers,
    Anja

  • Not able to create users in OID through OIM

    HI,
    I am creating users in OIM and provisioning them to OID. The create user is working fine but provisioning is not working.
    The create user task is getting rejected with error message as :
    Response: Target Unavailable Error
    Response Description: Target server not available
    In the weblogic console its showing error as:
    INFO,24 Feb 2010 18:42:13,140,[XL_INTG.OID], Parameter Variables passed into co
    m.thortech.xl.integration.OID.tcUtilOIDUserOperations:createUser(S,S,S,S,S): are
    sContainerDN = ou=AGI(ENI UK Ltd),o=Shippers,dc=xoserve-apps,dc=com, sFirstName
    = testuser17, sLastName = testuser17, sUserDNParam = TESTUSER17,
    INFO,24 Feb 2010 18:42:13,156,[XL_INTG.OID],com.thortech.xl.integration.OID.uti
    l.tcUtilLDAPOperations : connectToAvailableOID() : SSL option is not selected in
    ITResource
    ERROR,24 Feb 2010 18:42:16,156,[XL_INTG.OID],===================================
    =================
    ERROR,24 Feb 2010 18:42:16,156,[XL_INTG.OID], ERROR in OID:connectToAvailableOID
    () CommunicationExceptionUnable to create Initial LDAP Context
    ERROR,24 Feb 2010 18:42:16,156,[XL_INTG.OID],===================================
    =================
    ERROR,24 Feb 2010 18:42:16,156,[XL_INTG.OID],===================================
    =================
    ERROR,24 Feb 2010 18:42:16,156,[XL_INTG.OID],10.224.29.51:389
    ERROR,24 Feb 2010 18:42:16,156,[XL_INTG.OID],===================================
    ERROR,24 Feb 2010 18:42:16,171,[XL_INTG.OID],com.thortech.xl.integration.OID.uti
    l.tcUtilLDAPOperations : disconnectFromLDAP() : : Unable to close LDAP Context.
    The context was probably not created, since it is null
    ERROR,24 Feb 2010 18:42:16,171,[XL_INTG.OID],===================================
    =================
    ERROR,24 Feb 2010 18:42:16,171,[XL_INTG.OID],===================================
    =================
    ERROR,24 Feb 2010 18:42:16,171,[XL_INTG.OID], ERROR in com.thortech.xl.integrati
    on.OID.tcUtilOIDUserOperations:createUser(S,S,S,S,S) NoInitialContextExceptionEr
    ror while connecting to target
    ERROR,24 Feb 2010 18:42:16,171,[XL_INTG.OID],===================================
    =================
    ERROR,24 Feb 2010 18:42:16,171,[XL_INTG.OID],===================================
    =================
    ERROR,24 Feb 2010 18:42:16,171,[XL_INTG.OID],com.thortech.xl.integration.OID.uti
    l.tcUtilLDAPOperations: Unable to close LDAP Context. The context was probably n
    ot created, since it is null
    ERROR,24 Feb 2010 18:42:16,171,[XL_INTG.OID],===================================
    =================
    Please help.
    Thanks in advance.

    Thank a zillion to both of you...
    It was connection problem. Somebody changed my OID's IP address.
    Now my users are getting provisioned.
    One more doubt how to give points to both of you. I dont know how to give points in this forum.

  • Not able to create R/3 source system in BW

    using sm59 when i go to R/3 and click on R3 logical name
    i get login screen , for r/3 if i give user id and name i am able to enter in r/3,
    What i should do so that i won't get this logon screen
    I have already done following according to posting in theis forum
    go to SM59 in BW in that select your RFC Destination in that Login / Security Tab in that Logon you / basis can can give the ALEREMOTE for back ground process we have create the ALEREMOTE , give the user name and password , language and Client and save it in the same way you can do it R/3 side.
    Answer would be rewarded by points
    Thanks in advance
    Srini--

    Before proceeding further, the following tests will confirm whether all entries in your RFC connections are correct and no issue.
    on R/3: test connection & authorization for your RFC connections
    SM59->R/3 Connection->select your R/3 RFC connection ->'Test connection'
    SM59->R/3 Connection->select your R/3 RFC connection ->'Test' menu ->'Authorization'
    Do the same for your BW RFC connection
    On BW: test connection & authorization for your RFC connections
    SM59->R/3 Connection->select your R/3 RFC connection ->'Test connection'
    SM59->R/3 Connection->select your R/3 RFC connection ->'Test' menu ->'Authorization'
    Do the same for your BW RFC connection
    If connection test and authorization tests are successfully; you can proceed with creating souce system.
    If failed, troubleshoot to see where the error is. Your Basis can assist with test connection failed and Security can assist with Authorization test.

  • Problem with Trusted Reconcilation, Not able to create USERS in Database

    .log file
    ERROR ExecuteThread: '11' for queue: 'weblogic.kernel.Default' XELLERATE.SERVER - Class/Method: tcRCE/createUserRecord encounter some problems: {1}
    java.lang.NullPointerException
         at com.thortech.xl.dataobj.util.tcAttributeSource.getAttrColumnName(Unknown Source)
         at com.thortech.xl.dataobj.tcRCE.createUserRecord(Unknown Source)
         at com.thortech.xl.dataobj.tcRCE.applyActionRules(Unknown Source)
         at com.thortech.xl.dataobj.tcRCE.checkDataSorted(Unknown Source)
         at com.thortech.xl.dataobj.tcRCE.eventPostUpdate(Unknown Source)
         at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
         at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
         at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
         at com.thortech.xl.dataobj.tcRCE.finishDataReceived(Unknown Source)
         at com.thortech.xl.schedule.jms.reconOffline.ProcessOfflineReconMessages.finishReconciliationEvent(Unknown Source)
         at com.thortech.xl.schedule.jms.reconOffline.ProcessOfflineReconMessages.execute(Unknown Source)
         at com.thortech.xl.schedule.jms.messagehandler.MessageHandlerMDB.onMessage(Unknown Source)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:400)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    XELLERATE.DATABASE - Class/Method: tcDataBase/rollbackTransaction encounter some problems: Rollback Executed From
    java.lang.Exception: Rollback Executed From
         at com.thortech.xl.dataaccess.tcDataBase.rollbackTransaction(Unknown Source)
         at com.thortech.xl.dataobj.tcDataObj.rollback(Unknown Source)
         at com.thortech.xl.dataobj.tcDataObj.doRollback(Unknown Source)
         at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
         at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
         at com.thortech.xl.dataobj.tcRCE.finishDataReceived(Unknown Source)
         at com.thortech.xl.schedule.jms.reconOffline.ProcessOfflineReconMessages.finishReconciliationEvent(Unknown Source)
         at com.thortech.xl.schedule.jms.reconOffline.ProcessOfflineReconMessages.execute(Unknown Source)
         at com.thortech.xl.schedule.jms.messagehandler.MessageHandlerMDB.onMessage(Unknown Source)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:400)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    My Recon Schedule task settings:
    OrganizationUnitName     vcdsOrganization
    TrustedSource     true
    Password     Dummy123
    Role     Consultant
    ITResourceName     vCDSLDAP User
    ResourceObjectName     vCDSLDAP User
    XLDeleteUsersAllowed     false
    UserContainer     o=VFUS,dc=people_test,dc=vodafone,dc=com
    Xellerate Type     End-User Administrator
    Organization     Xellerate Users
    IsIPlanetTarget     false
    Please, help me, i am in need for ur kind help.
    Thanks in Advance.

    Hi,
    the mostly probable right answer is part of Sandeep's post
    to be more precise, SAPJSF user has to have the SAP_BC_JSF_COMMUNICATION role only, as the role SAP_BC_JSF_COMMUNICATION_RO stands for Read Only (avoiding you to modify anoything in the Java UME onto the portal).
    But this is a security policy, do not change it without contacting your BC.
    Fabien.

  • Not able to create user.

    I am trying to create a user using wlst. I am getting the below exceptions.
    wlst Snippet :-
    cd('/')
    cd('SecurityConfiguration')
    cd( WLS_DOMAIN_NAME )
    print 'IN DOMAIN'
    cd('weblogic.security.providers.authentication.DefaultAuthenticator')
    print 'IN AFTER'
    cd('Security:Name=myrealmDefaultAuthenticator')
    if cmo.userExists('admin')==1:
    I am getting the below exception while running the above script. Your help is highly appreciated.
    javax.management.AttributeNotFoundException: com.bea:Name=vjrdomain,Type=SecurityConfiguration:weblogic.security.providers.authentication.DefaultAuthenticator
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
    at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
    at javax.management.remote.rmi.RMIConnectionImpl_1033_WLStub.getAttribute(Unknown Source)
    at weblogic.management.remote.common.RMIConnectionWrapper$12.run(ClientProviderBase.java:726)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.security.Security.runAs(Security.java:61)
    at weblogic.management.remote.common.RMIConnectionWrapper.getAttribute(ClientProviderBase.java:724)
    at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:878)
    at weblogic.management.scripting.BrowseHandler.regularPush(BrowseHandler.java:429)
    at weblogic.management.scripting.BrowseHandler.splitPush(BrowseHandler.java:149)
    at weblogic.management.scripting.BrowseHandler.cd(BrowseHandler.java:684)
    at weblogic.management.scripting.WLScriptContext.cd(WLScriptContext.java:196)
    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:597)
    at org.python.core.PyReflectedFunction.__call__(Unknown Source)
    at org.python.core.PyMethod.__call__(Unknown Source)
    at org.python.core.PyObject.__call__(Unknown Source)
    at org.python.core.PyObject.invoke(Unknown Source)
    at org.python.pycode._pyx16.cd$5(<iostream>:173)
    at org.python.pycode._pyx16.call_function(<iostream>)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyFunction.__call__(Unknown Source)
    at org.python.pycode._pyx15.f$0(D:\vjrdomain\bin\Deploy81.py:46)
    at org.python.pycode._pyx15.call_function(D:\vjrdomain\bin\Deploy81.py)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyCode.call(Unknown Source)
    at org.python.core.Py.runCode(Unknown Source)
    at org.python.util.PythonInterpreter.execfile(Unknown Source)
    at weblogic.management.scripting.WLST.main(WLST.java:131)
    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:597)
    at weblogic.WLST.main(WLST.java:29)
    Caused by: javax.management.AttributeNotFoundException: com.bea:Name=vjrdomain,Type=SecurityConfiguration:weblogic.security.providers.authentication.DefaultAuthenticator
    at weblogic.management.jmx.modelmbean.WLSModelMBean.getPropertyDescriptorForAttribute(WLSModelMBean.java:1415)
    at weblogic.management.mbeanservers.internal.SecurityInterceptor.getPropertyDescriptor(SecurityInterceptor.java:886)
    at weblogic.management.mbeanservers.internal.SecurityInterceptor.checkGetSecurity(SecurityInterceptor.java:575)
    at weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:298)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:279)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$5$1.run(JMXConnectorSubjectForwarder.java:326)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$5.run(JMXConnectorSubjectForwarder.java:324)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.getAttribute(JMXConnectorSubjectForwarder.java:319)
    at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1403)
    at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
    at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
    at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)

    This looks like online WLST.
    I don't believe this line is correct. cd('weblogic.security.providers.authentication.DefaultAuthenticator')
    When using online, perform a ls() to see what elements are available at each level. I believe there is a Realms and AuthenticationProviders layer between SecurityConfiguration and the default authenticator.

  • Not able to create J2EE user DDIC in portal

    Hi All,
    I am trying to configure the BI 7.0  system in EP 7.0. My systems are running on Windows 2003 32 bit edition. SP level is SPS11 & SP10
    I have configured the UME where datasource is ABAP system. After using the supportdesk tool I am getting the below three erros in the system.
    Import of Web Templates in active version will fail because the J2EE user DDIC is not properly mapped to an ABAP user other than DDIC Maintain a user mapping for J2EE user DDIC - see note 945055 for details
    Check could not be executed because retrieval of WebAS ABAP settings failed Check connectivity to WebAS ABAP and make sure the ABAP coding correction from note 937697 is applied in the latest version available
    Check could not be executed because retrieval of WebAS ABAP settings failed Check connectivity to WebAS ABAP and make sure the ABAP coding correction from note 937697 is applied in the latest version available
    To resolve these issues i tried to create user id DDIC in portal but I am not able to create it. It is giving below error
    A user with the specified logon ID already exists; choose a different, unique logon ID
    As it is trying to create this user id in ABAP datasource. Please let me know how to create DDIC in J2EE engine where ABAP is the datasource.
    Please help me resolve this issue.
    Thanks,
    Shambo

    Hi,
    In defaulttrace.trc I am getting the below errors
    #1.5#00055D4A98DC0061000004BC00001610000460FCEAE15F00#1232539295495#com.sap.ip.bi.preexecutionservices.PreexecutionservicesRfcService#sap.com/com.sap.prt.application.rfcframework#com.sap.ip.bi.preexecutionservices.PreexecutionservicesRfcService#Administrator#9873####403302b0e7b311ddbd4500055d4a98dc#SAPEngine_Application_Thread[impl:3]_27##0#0#Fatal#1#/Applications/BI#Plain###Exception caught: com.sap.ip.bi.base.exception.BIBaseRuntimeException: SAX Exception
    com.sap.ip.bi.base.exception.BIBaseRuntimeException: SAX Exception
         at com.sap.ip.bi.webapplications.runtime.preexecution.impl.PreexecutionDispatcher$DocumentAnalysis.createMutableDocument(PreexecutionDispatcher.java:93)
         at com.sap.ip.bi.webapplications.runtime.preexecution.impl.PreexecutionDispatcher.validateDocument(PreexecutionDispatcher.java:571)
         at com.sap.ip.bi.preexecutionservices.PreexecutionservicesRfcService.handleRequestForRSWR_PREEXECUTION_PROXY(PreexecutionservicesRfcService.java:109)
         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:324)
         at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.handleServiceRequestGeneric(BIServicesRfcDispatcherService.java:283)
         at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:177)
         at com.sap.ip.bi.portalrfc.services.BIRfcService.handleRequest(BIRfcService.java:235)
         at com.sapportals.portal.prt.service.rfc.RFCEngineService.handleEvent(RFCEngineService.java:341)
         at com.sapportals.portal.prt.service.rfc.PRTRFCBean.processFunction(PRTRFCBean.java:37)
         at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0_0.processFunction(PRTRFCRemoteObjectImpl0_0.java:118)
         at sun.reflect.GeneratedMethodAccessor299.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy119.processFunction(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:324)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:284)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
         at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:59)(:main:, row=1, col=59) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:59)
         at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
         at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
         at com.sap.ip.bi.webapplications.runtime.preexecution.impl.PreexecutionDispatcher$DocumentAnalysis.createMutableDocument(PreexecutionDispatcher.java:85)
         ... 28 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:59)
         at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1590)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1710)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
         at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
         ... 30 more
    #1.5#00055D4A98DC0061000004BF00001610000460FCEAE18738#1232539295511#com.sap.ip.bi.base.application.message.impl.MessageBase#sap.com/com.sap.prt.application.rfcframework#com.sap.ip.bi.base.application.message.impl.MessageBase#Administrator#9873####403302b0e7b311ddbd4500055d4a98dc#SAPEngine_Application_Thread[impl:3]_27##0#0#Error#1#/Applications/BI#Plain###A message was generated:
    ERROR
    Transformer exception while transforming BEx Web templates
    com.sap.ip.bi.deploytime.BISP2Jsp SAPXMLTransformer
    SAX Exception
    Transformer exception while transforming BEx Web templates
    com.sap.ip.bi.deploytime.BISP2Jsp SAPXMLTransformer
    SAX Exception#

  • Not able to create a message from satellite system

    Hello Everyone.
    We have been working on Solution Manager .We have managed with successfull installation,Uploaded required support packages,configured the system according to SAP Solution Manager Guide.
    Faced with some problem regarding support desk,we are not able to create a message from satellite system to Solution Manager.
    Note : Error Message related to this problem is ....
    <b>"Error in Local Message System : External number assignment, Enter notification num message was not Created."</b>
    Thanks in advance.
    Regards,
    Nimesh V . Master

    Hi, you need to check the number ranges for the notifications and make sure they are correct.  Look in the IMG of the SAP Solution Manager system for the instructions.  You also need to make sure that the Service Desk BC Sets are activated if you are NOT on 4.0 and SP Stack 09+.  In the later SPs much of this configuration from the IMG is automated in the wizard.

  • SRM: Create Contact Person Could not create user; contact your system admin

    Hi All,
    First, I am not sure this question should be posted here, or SRM General. From my point of view, here is more suitable.
    Our Problem:
    Activity "Create Contact Person With Reference" error with message:
    Step to reproduce:
    1. Login to SRM JAVA as super administrator
    2. Open tab "SRM Administration"
    3. Using the current query, search for Business-Partner no: 30000725
    4. Press "Create Contact Person with Reference"
    5. Fill all required fields, tick "Is contact person" checkbox
    6. Put: /SAPSRM/SUPPLIER as Role
    7. Save
    The following Message appear:
    Could not create user; contact your system administrator
    SPML Service error: Error reading request status.  Display Help
    Contact Person 2000000214 Created Successfully for BP 30000725  Display Help
    E-mail was sent
    The first error is intriguing. The username & password is created successfully in ABAP System (Our UME is in ABAP).
    QUESTIONS:
    1. What cause this problem? How to trace the error?
    2. We want the user have portal role automatically. How to achieve that?
    Thank you for any responses and helps.
    SRM ABAP Version:
    SRM_PLUS     700     0009     SAPKIBK209     SRM_PLUS for mySAP SRM
    SRM_SERVER     700     0009     SAPKIBKV09     SRM_SERVER
    SAP_ABA     701     0007     SAPKA70107     Cross-Application Component
    SAP_BASIS     701     0008     SAPKB70108     SAP Basis Component
    PI_BASIS     701     0007     SAPK-70107INPIBASIS     Basis Plug-In
    SRM JAVA Version:
    SRM JAVA: Release 7 SP Level 9.0
    BP SRM: Release 7 SP Level 9.0
    Edited by: Nur Agus Suryoko on Mar 11, 2011 11:36 AM
    Version information added

    Hi Fernando,
    Can you please tell me how you resolved this issue ??
    Regards,
    Adren

  • Not able to create new users or groups

    hi all,
    We have configured multiple LDAPs by changing XML file.
    But now we are not able to create new users or groups.It is giving error saying that "Adapter is configured as read-only"
    Can anybody help me out in this problem.
    Thanking You,
    Amol.

    For multiple LDAPs to work we have downloaded the Xml file namely "Flat hierarchy + Database "
    We made the necessary changes and then uploaded it.
    Now we want to create users or groups in portal-database and not in LDAP. But it is throwing error saying that "Adapter is read only". We suppose that it is trying to create users and groups in LDAP.
    So can anyone help us to create users or groups in portal-database.
    Thanking You,
    Amol.

  • Users are not able to create POs from PRs having Production Order (F)

    Hi Gurus
    Users are not able to create POs from PRs having Production Order (F) as creation indicator.
    Whenever we are trying to convert the PR to PO we are getting the error message "Requisition has different doc. type NB and item cat. >&<" based on the below OSS# 938154 condition for the creation indicator type F.
    Would you please investigate and advise what OSS notes are required to be able to use item category L (subcontracting) on a PO for a requisition generated from a network activity via Procurement Type = "Preliminary requisition for WBS element".
    Thanks,
    Sada.

    Hi Ajay & Andra
    Whenever we are trying to convert the PR to PO we are getting the error message "Requisition has different doc. type NB and item cat. >&<" based on the below OSS# 938154 condition for the creation indicator type  Production order (F).
    Our Business requirement as shown below.
    1).The problem - we currently have no way to "direct requisition" an item to be procured via      subcontracting - only itu2019s possible via MRP.
    2).These behaviors are inconsistent as the requisition process should not impact the procurement process.  Can we find a way to influence the creation indicator on the requisition so that it does not appear as a production order?
    Please suggest any alternate method for achieving this.
    Thanks & Regards
    Sada

  • Certen user is not able to create the sc using sepecific vendor

    Hi,
    User is not able to create the SC entering specific  vendor .
    This vendor is in maintained in SRM for one pur.org (I have checked in PPOMA_BBP).
    Then why he is not able to creating the sc using this Vendor

    whether user is belong to same region of the Vendor or different. Is there any enhancements you have like that.
    Please check those things.
    Hope this will help.
    Thanks
    Venkatesh P

Maybe you are looking for