XML APPROVAL PROCESS
Hello Experts,
I wonder if it is possible to enable approval process for a folder and all the folders that in it. i mean when i enable approval and set the steps the same approval process should be enabled. if this isn't possible then this is ridiculous because i will have to open all the folders and set the approval seperately. Plz help me with this.I m very thankful to u.
Any helpful answers will be regarded with points.
Hi Rajat,
I have never tried this.
But, must say its a good thought.
What I can say is : Try mapping a folder(having subfolders) to EP by making a File Repository Manager.
Now put a document in one of the sub folders and see what happens.
There can be two possibilities:
1)Either the FRM will recognize the document and will send for approval
2)Or it will not recognise the sub folders.
I am not in access to a EP server presently.
Please try this and reply back.
I hope it helps.
Regards,
Sumit
Similar Messages
-
Hi,
I am implementing XML forms with approval process.UI have created a news. and it goes to the folder /documents/news2
For Folder "News2" I have permission to one USER "Preeti " as approver.Everyone is Read access
Service Permissions that "Preeti" has Full control.and evryone "Unsubscribe only"I could not see option no service
Approval process has step of approving from user "Preeti"
I could now see the edit delete approval in the iview but for the authors and users with system admin role also the iView has option of Submit for approval and Skip approval.
Also I tried creating new user and for that the NEwsApproval iView does not show the link to create news.as shown in your fig.
So I want that the author only should see teh link submit approval and not skip approval.All other users even though a system admin but not a approver should not see that Submit approval.
Please request you to help me.Hi Preeti,
To see the 'New' link the user should have write access to that folder. Only then they can create xml items using the form.
If you dont want to show the skip approval link to any one including admin, you can advance copy the layout set "NewsExplorer" and remove the command from resource command group.
The approver also gets the submit for approval option and if he selects it, the document is sent to his own UWL for approval, if he is the only approver, otherwise sent to the next level approver.
Regards
Ramesh kotagiri -
OIM: Error while deploying Custom Approval Process for Self-Register
While deploying the Custom Approval Process for Self-Register, i am getting the following error in scac.log file
Nov 16, 2011 2:48:58 PM oracle.fabric.common.wsdl.SchemaManager isIncrementalBuildSupported
INFO: XMLSchema incremental build enabled.
Nov 16, 2011 2:48:58 PM com.collaxa.cube.CubeLogger info
INFO: validating "ApprovalProcess.bpel" ...
oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform.
at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
at oracle.integration.platform.blocks.WLSPlatformConfigurationProvider.<clinit>(WLSPlatformConfigurationProvider.java:44)
at oracle.integration.platform.blocks.FabricConfigManager.<clinit>(FabricConfigManager.java:155)
at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXpathFunctions(FabricXPathFunctionResolver.java:271)
at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXPathConfigFile(FabricXPathFunctionResolver.java:153)
at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.init(FabricXPathFunctionResolver.java:51)
at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.loadFabricXpathFunctions(BPELXPathFunctionNameResolver.java:57)
at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<init>(BPELXPathFunctionNameResolver.java:48)
at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<clinit>(BPELXPathFunctionNameResolver.java:44)
at com.collaxa.cube.lang.compiler.bpel.XPathExprValidatorVisitor.<init>(XPathExprValidatorVisitor.java:122)
at com.collaxa.cube.lang.compiler.bpel.AssignValidator.<init>(AssignValidator.java:89)
at com.collaxa.cube.lang.compiler.bpel.BpelParser.<init>(BpelParser.java:452)
at com.collaxa.cube.lang.compiler.bpel.BPELValidator.validate(BPELValidator.java:60)
at com.collaxa.cube.lang.compiler.BPEL1Processor.validate(BPEL1Processor.java:329)
at com.collaxa.cube.lang.compiler.BPEL1Processor.process(BPEL1Processor.java:153)
at com.collaxa.cube.lang.compiler.CubeParserHelper.compile(CubeParserHelper.java:47)
at oracle.fabric.bpel.bpelc.BPELComponentValidator.validate(BPELComponentValidator.java:40)
at oracle.soa.scac.ValidateComposite.validateComponentTypeServicesReferences(ValidateComposite.java:1117)
at oracle.soa.scac.ValidateComposite.doValidation(ValidateComposite.java:500)
at oracle.soa.scac.ValidateComposite.run(ValidateComposite.java:150)
at oracle.soa.scac.ValidateComposite.main(ValidateComposite.java:135)
Nov 16, 2011 2:49:00 PM CubeProcessGenerator compile
WARNING: classpath is: D:\JDev11g\Middleware\jdeveloper\jdev\extensions\oracle.sca.modeler.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.mediator_11.1.1\mediator_client.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.mds_11.1.1\mdsrt.jar;D:\OIMPS1\Middleware\oracle_common\modules\oracle.jps_11.1.1\jps-manifest.jar;;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\classes;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\classes;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\gen-classes;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\lib\oimclient.jar;D:\JDev11g\Middleware\oracle_common\modules\commonj.sdo_2.1.0.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel1-1-xbeans.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-common.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel_coherence_config.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-exts.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\thirdparty.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpm-analytics.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-thirdparty.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\wsif-binding.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-validator.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\monitor-rt-xbean.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\oracle.soa.bpmn.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\user-patch.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.thirdparty.jar;D:\JDev11g\Middleware\jdeveloper\uddi\lib\oracle.soa.uddi.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\bpm-infra.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\testfwk-xbeans.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-ext.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-scheduler.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\xmlunit-1.1.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-tools.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-xpath-exts.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle-soa-client-api.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.wls.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-client.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-was.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-wls.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.workflow_11.1.1\bpm-services.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.ext_11.1.1\classes
In scac_out.xml file following is the error message
<Fault>
<severity>error</severity>
<loc>/ns:composite</loc>
<line/>
<col/>
<file/>
<msg>
<![CDATA[SCAC-50012]]>
</msg>
</Fault>Hi,
I have run into the same problem with SOA 11.1.1.5 version. In my case after fixing the following two errors it seems to work fine.
If you have followed the guide, there must be some errors:
First the java code if copied then contains an extra enter value:
Instead of:
"try {
System.out.println("Prototype for invoking an OIM API from a SOA Composite");
System.out.println("RTM Usecase: Self Registration Approval by Organization
Administrator");"
Use the following:
"try {
System.out.println("Prototype for invoking an OIM API from a SOA Composite");
System.out.println("RTM Usecase: Self Registration Approval by Organization Administrator");"
The other error is that you should not use <BEAHOME>/oracle_common/modules/oracle.jps_11.1.1/jps-manifest.jar, but the <BEAHOME>/oracle_common/modules/oracle.jps_11.1.1/jps-api.jar in jdeveloper. After these the deployment to the application server works fine for me. -
Error provisioning a resource with custom approval process
Hi,
While trying to provision a resource with custom approval process, I get the following error:
<May 11, 2012 8:07:18 AM IST> <Warning> <oracle.wsm.agent.handler.wls.WLSPropertyUtils> <BEA-000000> <WLSPropertyUtils:getOperationName(),operation name is null>
<May 11, 2012 8:07:18 AM IST> <Warning> <org.eclipse.persistence.session.oim> <BEA-000000> <
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-12899: value too large for column "DEV_OIM"."REQUEST_APPROVALS"."APPROVAL_STATUS" (actual: 442, maximum: 32)
Error Code: 12899
Call: UPDATE REQUEST_APPROVALS SET APPROVAL_STATUS = ? WHERE (REQUEST_APPROVALS_KEY = ?)
bind => [com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.xmlsoap.org/ws/2003/03/business-process/}selectionFailure}
parts: {{
summary=<summary>XPath query string returns zero node.
The assign activity of the to node query is returning zero node.
Either the to node data or the xpath query in the to node was invalid.
According to BPEL4WS spec 1.1 section 14.3, verify the to node value at line number 251 in the BPEL source.
</summary>}
, 6]
Query: UpdateObjectQuery(oracle.iam.request.vo.ApprovalData@11e00d4b)
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:801)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:867)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:587)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:530)
at org.eclipse.persistence.internal.sessions.AbstractSession.executeCall(AbstractSession.java:914)
at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:206)
at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:192)
at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.updateObject(DatasourceCallQueryMechanism.java:715)
at org.eclipse.persistence.internal.queries.StatementQueryMechanism.updateObject(StatementQueryMechanism.java:430)
at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1141)
at org.eclipse.persistence.queries.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:84)
at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:287)
at org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:675)
at org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:589)
at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:109)
at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:86)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2898)
at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1225)
at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1207)
at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1167)
at org.eclipse.persistence.internal.sessions.CommitManager.commitChangedObjectsForClassWithChangeSet(CommitManager.java:233)
at org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:108)
at org.eclipse.persistence.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:3260)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1413)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1518)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.writeChanges(UnitOfWorkImpl.java:5499)
at oracle.iam.request.repository.ApprovalRepository.updateApprovalInstanceWithOutcome(ApprovalRepository.java:84)
at oracle.iam.request.impl.ApprovalManager.approvalInstanceComplete(ApprovalManager.java:111)
at oracle.iam.request.impl.ApprovalPolicyServiceImpl.updateApprovalResult(ApprovalPolicyServiceImpl.java:52)
at oracle.iam.request.api.ApprovalPolicyServiceEJB.updateApprovalResultx(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:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy351.updateApprovalResultx(Unknown Source)
at oracle.iam.request.api.ApprovalPolicyService_1nib43_ApprovalPolicyServiceRemoteImpl.updateApprovalResultx(ApprovalPolicyService_1nib43_ApprovalPolicyServiceRemoteImpl.java:462)
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.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:84)
at $Proxy184.updateApprovalResultx(Unknown Source)
at oracle.iam.request.api.ApprovalPolicyServiceDelegate.updateApprovalResult(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:597)
at Thor.API.Base.SecurityInvocationHandler$1.run(SecurityInvocationHandler.java:68)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(weblogicLoginSession.java:52)
at Thor.API.Base.SecurityInvocationHandler.invoke(SecurityInvocationHandler.java:79)
at $Proxy350.updateApprovalResult(Unknown Source)
at oracle.iam.request.workflowcallback.ApprovalCallBack.completed(ApprovalCallBack.java:28)
at oracle.iam.platform.workflowservice.ws.CallbackServiceImpl.callback(CallbackServiceImpl.java:98)
at oracle.iam.platform.workflowservice.ws.wls.CallbackService.callback(CallbackService.java:33)
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.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:92)
at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:74)
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:151)
at com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl.invoke(EndpointMethodHandlerImpl.java:265)
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:100)
at weblogic.wsee.jaxws.tubeline.FlowControlTube$FlowControlAwareTube.processRequest(FlowControlTube.java:155)
at weblogic.wsee.jaxws.tubeline.FlowControlTube$1.run(FlowControlTube.java:94)
at weblogic.wsee.jaxws.tubeline.FlowControlTube$1.run(FlowControlTube.java:92)
at javax.security.auth.Subject.doAs(Subject.java:337)
at weblogic.wsee.jaxws.tubeline.FlowControlTube.processRequest(FlowControlTube.java:91)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:373)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:524)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:255)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:208)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:310)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:223)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:124)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:79)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.am.agent.wls.filters.OAMServletAuthenticationFilter.doFilter(OAMServletAuthenticationFilter.java:260)
at oracle.security.am.agent.wls.filters.OAMValidationSystemFilter.doFilter(OAMValidationSystemFilter.java:133)
at oracle.security.wls.oamagent.OAMAgentWrapperFilter.doFilter(OAMAgentWrapperFilter.java:121)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.sql.SQLException: ORA-12899: value too large for column "DEV_OIM"."REQUEST_APPROVALS"."APPROVAL_STATUS" (actual: 442, maximum: 32)
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:74)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:135)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:210)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:473)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:423)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1095)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:205)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1040)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1379)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3568)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3694)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1508)
at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:172)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:792)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:867)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:587)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:530)
at org.eclipse.persistence.internal.sessions.AbstractSession.executeCall(AbstractSession.java:914)
at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:206)
at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:192)
at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.updateObject(DatasourceCallQueryMechanism.java:715)
at org.eclipse.persistence.internal.queries.StatementQueryMechanism.updateObject(StatementQueryMechanism.java:430)
at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1141)
at org.eclipse.persistence.queries.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:84)
at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:287)
at org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:675)
at org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:589)
at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:109)
at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:86)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2898)
at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1225)
at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1207)
at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1167)
at org.eclipse.persistence.internal.sessions.CommitManager.commitChangedObjectsForClassWithChangeSet(CommitManager.java:233)
at org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:108)
at org.eclipse.persistence.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:3260)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1413)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1518)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.writeChanges(UnitOfWorkImpl.java:5499)
at oracle.iam.request.repository.ApprovalRepository.updateApprovalInstanceWithOutcome(ApprovalRepository.java:84)
at oracle.iam.request.impl.ApprovalManager.approvalInstanceComplete(ApprovalManager.java:111)
at oracle.iam.request.impl.ApprovalPolicyServiceImpl.updateApprovalResult(ApprovalPolicyServiceImpl.java:52)
at oracle.iam.request.api.ApprovalPolicyServiceEJB.updateApprovalResultx(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:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy351.updateApprovalResultx(Unknown Source)
at oracle.iam.request.api.ApprovalPolicyService_1nib43_ApprovalPolicyServiceRemoteImpl.updateApprovalResultx(ApprovalPolicyService_1nib43_ApprovalPolicyServiceRemoteImpl.java:462)
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.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:84)
at $Proxy184.updateApprovalResultx(Unknown Source)
at oracle.iam.request.api.ApprovalPolicyServiceDelegate.updateApprovalResult(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:597)
at Thor.API.Base.SecurityInvocationHandler$1.run(SecurityInvocationHandler.java:68)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(weblogicLoginSession.java:52)
at Thor.API.Base.SecurityInvocationHandler.invoke(SecurityInvocationHandler.java:79)
at $Proxy350.updateApprovalResult(Unknown Source)
at oracle.iam.request.workflowcallback.ApprovalCallBack.completed(ApprovalCallBack.java:28)
at oracle.iam.platform.workflowservice.ws.CallbackServiceImpl.callback(CallbackServiceImpl.java:98)
at oracle.iam.platform.workflowservice.ws.wls.CallbackService.callback(CallbackService.java:33)
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.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:92)
at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:74)
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:151)
at com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl.invoke(EndpointMethodHandlerImpl.java:265)
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:100)
at weblogic.wsee.jaxws.tubeline.FlowControlTube$FlowControlAwareTube.processRequest(FlowControlTube.java:155)
at weblogic.wsee.jaxws.tubeline.FlowControlTube$1.run(FlowControlTube.java:94)
at weblogic.wsee.jaxws.tubeline.FlowControlTube$1.run(FlowControlTube.java:92)
at javax.security.auth.Subject.doAs(Subject.java:337)
at weblogic.wsee.jaxws.tubeline.FlowControlTube.processRequest(FlowControlTube.java:91)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:373)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:524)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:255)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:208)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:310)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:223)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:124)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:79)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.am.agent.wls.filters.OAMServletAuthenticationFilter.doFilter(OAMServletAuthenticationFilter.java:260)
at oracle.security.am.agent.wls.filters.OAMValidationSystemFilter.doFilter(OAMValidationSystemFilter.java:133)
at oracle.security.wls.oamagent.OAMAgentWrapperFilter.doFilter(OAMAgentWrapperFilter.java:121)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<May 11, 2012 8:07:18 AM IST> <Error> <oracle.iam.request.impl> <IAM-2050200> <Failed to create the request in the repository.>
<May 11, 2012 8:07:18 AM IST> <Error> <oracle.iam.request.impl> <IAM-2050050> <Exception thrown Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-12899: value too large for column "DEV_OIM"."REQUEST_APPROVALS"."APPROVAL_STATUS" (actual: 442, maximum: 32)
Error Code: 12899
Call: UPDATE REQUEST_APPROVALS SET APPROVAL_STATUS = ? WHERE (REQUEST_APPROVALS_KEY = ?)
bind => [com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.xmlsoap.org/ws/2003/03/business-process/}selectionFailure}
parts: {{
summary=<summary>XPath query string returns zero node.
The assign activity of the to node query is returning zero node.
Either the to node data or the xpath query in the to node was invalid.
According to BPEL4WS spec 1.1 section 14.3, verify the to node value at line number 251 in the BPEL source.
</summary>}
, 6]
Any idea how to resolve this ??
Thanks,Based on the error trace
Caused By: java.sql.SQLException: ORA-12899: value too large for column "DEV_OIM"."REQUEST_APPROVALS"."APPROVAL_STATUS" (actual: 442, maximum: 32)
you are inserting a value too large for REQUEST_APPROVALS.APPROVAL_STATUS column. It should contain values like COMPLETED, approved, rejected etc... Check your custom approval process again.
Regards
user12841694 -
Approval process monitor status turn to "Initiated" instead of "Pending", so awe is not routed
When I submit a transaction, after successful submission in approval process monitor the status has turn "Initiated" instead of "Pending". That's why it's showing "Not Routed" for the next approving person. So that worklist is not populated.
Please suggest me to resolve this issue.
Process Monitor as follows after submission:
Separation Approval Process (Stage)
Initiated (Monitor status)
Approval Routing from Unit HR (Path)
Not Routed (Step) Not Routed (Step)
Multiple Approvers Multiple Approvers
STATEHR ROLEUSER SEPARATION Central Hr
(Userlist) (Userlist)Looking at the error message "The Network Adapter could not establish the connection" , It appears hostname and port may be incorrect. Review the targets.xml under E:\oracle\product\10.2.0\db_1\SAP_solman_SDB\emd and
emoms.properties under E:\oracle\product\10.2.0\db_1\SAP_solman_SDB\config folder to make sure host ( sap_solman) and port (1527) are correct.
As far as setting the environment variables goes, you can go to control panel -> system -> advanced -> environment variables and set the ORACLE_HOME and ORACLE_SID
-Ramesh -
Approval process in update user workflow
Hi
I have read in the document Administrative Guide that by default, the approval process is set only for user creation. and the same does not work for update and delete operations on user, unless we customize the code.
Does any one of you have any idea as to what customization needs to be done for successful approval process for updates also. I have set approvers for resources.
Thanks
Bushra1. backup the existing Update user workflow as an xml file
2. Copy paste the same in the BPE.
3. Save the copy as a new object with a different name.
4. Edit the new workflow as follows:
4.1 Create new activity
4.2 In the new activity, add a variable with some name
4.3 create a new action, and let that action be a subprocess. For that subprocess, browse and choose 'Approval' as the action.
4.4 Add a argument as name=approvalForm and value=<name of approval form>
4.5 Include argument user=$(user), etc. (Check the original approval workflow to see what the names of the arguments are)
4.6 For return to=name of the variable declared, from=approved
4.7 Add a 'isTrue' condition for the variable declared.
5. Make the appropriate transitions, and ur ready to go.
Let me know if this helps. I can post some skeleton code tomorrow. I need to work on it. Drop a line at [email protected] -
"Approval Process Overview" in ECC.
We have SRM 7.0 running in Classic scenario. We have a requirement to see the "Approval Process Overview" Log in the ECC Puchase requistion generated after the approvals are completed in SRM. (preferably at Header)
What are the options available for us to be able to do that ?
There is a Download XML in the Approval process Data field, Can it be changed to Download as Excel, and an excel file passed as an attachment to the Shopping cart and Purchase Requisition ?The intent behind this scenarios is to split the Approval process in two parts,
a) Part 1: SC Creator creates Shopping Cart and routes for approval on a Technical Basis. Once all technical approvals are completed and Shopping Cart is approved a PR is created with Release Strategy in ECC.
b) Part 2: Financial approver would approve the PR in ECC on the basis of Amount against release strategy. The requirement is for the financial approver in ECC to have visibility on who has Technically approved the Shopping cart without loging into SRM.
Once the financial approver validates that the Shopping cart was approved by a set of people, he goes ahead and releases it in ECC for further processing.
Our challenge is to get the approval lprocess overview from SRM to ECC. -
Approval process creation steps using JDeveloper in OIM 11g R2
Hi,
Please help me to create approval process creation using JDeveloper and how to use the approval process in OIM provision in OIM 11g R2.
Thanks in Advace,
srinirefer developer's guide to get the detailed steps. http://docs.oracle.com/cd/E27559_01/dev.1112/e27150/request.htm#BABFFJDH
Also refer OBE tutorial http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/oim/oim_11g/Custom_Approval_Process_for_Resource_Request/custom_approval_process_for_resource_provision.htm#t3
There will be slight changes in the steps as this OBE is for 11gR1.
High level steps:
Create a new application using the following command
ant -f <OIM_HOME>/server/workflows/new-workflow/new_project.xml.
It will be created in OIM_HOME/workflows/new-workflow/process-template/ directory
Openthe .jws file in jdeveloper and edit the default human task and add whatever logic is needed.
Then deploy the composite after which you need to create an approval policy and link the SOA composite created
Edited by: Durgaprasad on Apr 24, 2013 1:55 AM -
Approval Process through mail in OIM
Hi,
I need your views for the best way to meet this requirement:
Let's say a user is provisioned to a resource and resource has been configured with a approval process. The System Administrator 'xelsysadm' approval has been set to auto-complete so that step of approval is done automatically and the approval goes to the main approver of the resource. Now i require to send the requests generated in last 30 minutes only which are meant for an approver by grouping them and then sending them in a mail in HTML format to take further action.
Please do reply by your views on how to implement this.
ThanksThanks for the idea,
I need your help as i am facing issues in implementing it.
For Initializing the Factory Class with a Digital Signature i used this code
ConfigurationClient.ComplexSetting config = ConfigurationClient.getComplexSettingByPath("Discovery.CoreServer");
final Hashtable env = config.getAllSettings();
tcSignatureMessage moSignature = tcCryptoUtil.sign("xelsysadm","PrivateKey");
tcUtilityFactory m_utilFactory = new tcUtilityFactory(env, moSignature);
and updated the xlconfig.xml file as such
<KeyStore>
<Location>.xlkeystore</Location>
<Password encrypted="true">JfDl5Dgc48/6pVaOHW+6Qg==</Password>
<Type>JKS</Type>
<Provider>sun.security.provider.Sun</Provider>
</KeyStore>
<Keys>
<PrivateKey>
<Alias>xell</Alias>
<Password encrypted="true">JfDl5Dgc48/6pVaOHW+6Qg==</Password>
</PrivateKey>
</Keys>
But on executing the code this error is displayed:
com.thortech.xl.crypto.tcCryptoException: KeyStore File : .\config\xl.keystore missing.
at com.thortech.xl.crypto.tcCryptoHelper.loadKeyStore(Unknown Source)
at com.thortech.xl.crypto.tcDefaultSignatureImpl.initKeyStore(Unknown Source)
at com.thortech.xl.crypto.tcDefaultSignatureImpl.sign(Unknown Source)
at com.thortech.xl.crypto.tcCryptoUtil.sign(Unknown Source)
at com.reconciliation.UserReconciliation.connect(UserReconciliation.java:49) (this is line tcSignatureMessage moSignature = tcCryptoUtil.sign("xelsysadm","PrivateKey"); of the code)
What i observed is that the keystore file it is searching for .\config\xl.keystore is not there as it is .xlkeystore in config and the same is mentioned in the config file also.
Can you please tell me in what step i am wrong or if there is anything that i am missing.
Thanks -
Approved invoices can not be edited - Approval process
Hi Experts -
I have recently raised an incident with SAP about Approval process - the complete message and support reply is as follows - but i believe we need a change in the approval process - if the approval required is only one but you have defined two people (Either or OR) in the approver list - the system should allow the document to be edited if one of the approvers reject it.
please let me know and i believe we need a change in design - unless otherwise a solid reason is given to justify the existing design
10.07.2009 10:32 Description (English) by SRS Manian
We have created approval procedure for all the invoices which are entered into the system., The
'Accts' user enters the invoice into the system - the invoice comes for approval to 'Manager' user.
When the Manager opens the invoice via Alert window - he/she wants to modify certain information
(lines as well as Sales person) and approve it.
The invoice which gets opened from the alert window - does not allow the user 'Manager' to modify at
all. All the information on the invoice are greyed out.
The system should allow the user 'Manager' to modify the information. Since the manager has full
authorization to the system.
10.07.2009 10:35 Info to Reporter by SAP
Dear Partner/Customer,
We have received your inquiry and are currently processing it.
You will be contacted with a solution or an update as soon as possible.
For further details regarding the phase your message is in at the
moment please refer to:
http://service.sap.com/%7Esapidb/011000358700000575782007E
Kind regards,
SAP Business One Product Support
10.07.2009 10:59 Reply to Reporter by SAP
Dear Manian,
Thank you for contacting us.
When the originator sends the document for manager's approval, note that the at that stage, the document is still in the 'Approval Process'. This is because the system is waiting for the 'Manager' to 'Approve or Reject' the document. Hence, looking at the Document, it is still in 'Draft - Pending' Status.
When the document is in 'Draft-Pending' Status, the document is not available for editing, because the system considers that it is still in the waiting process. In your case, the manager cannot edit t he document.
To amend the document, an action is required from the approver either to reject it first. Once rejected, it can be amended and re-sent for approval.
I have checked our knowledge base and noted that there is an article which describes the approval process. Please refer to the Expert on Phone Wiki Article (March 2009) with title: Why a draft documen t in an approval process cannot be modified by the originator?
The link will provide the explanation:
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=88735894
I have also attached Notes 1321234 and 1111431 for your reference.
Best regards,
Lorna Real
Support Consultant
Product Support for SAP Business One
SAP Ireland
10.07.2009 11:59 Reply to Support Center by SRS Manian
Thanks for the reply. The scenario is when the Manager receives the
document for approval, he wanted to edit and add it. Your reply (and
documentations) states that it needs to be rejected first before it is
available for editing. When it is gets rejected - the person who
orignated the document gets an alert and he can edit it. Here the
Manager must get an alert so that he can edit the Rejected document.
When the 'manager' rejects the document, and goes back to the alert
window to open the document - it is still greyed out !!
How does the 'manager' reject the document and edits it ?
regards
Manian
10.07.2009 12:11 Reply to Reporter by SAP
Dear Manian,
If after the Manager rejects it and still the document is not editable (greyed out), it means that the document may still be in the 'Approval Process'. When it is greyed out, what is the status of the document in the header? Does it say 'Rejected' or 'Pending'?
If it is still in 'Pending' mode, please verify the number of 'Approvers' set in the 'Stages' tab of the 'Approval Template - Setup' window. If there is more than one user listed as 'Approver', and o nly 1 approval is required, the system provides an opportunity to other 'Approvers' to approve or reject the document. If in your case, the number of approvers is 2, and manager 'rejected' it, the sys tem still keeps the document in Pending status as it waits for another approver's decision to reject or approve it.
Also, verify the number of 'Approvals' required. If the number of 'Approvers' who have not rendered their decision is greater than or equal to the 'Approvals' required (e.g. approvers - 2, required ap provals - 2) the system keeps the document within the approval process. This is to allow the other 'Approvers' to decide on the document.
I hope this clarifies the behaviour. If you can provide us a step by step screenshot of the issue, this may help us to provide a more accurate response.
Best regards,
Lorna Real
Support Consultant
Product Support for SAP Business One
SAP Ireland
10.07.2009 12:28 Reply to Support Center by SRS Manian
Hi:
The status of the document in the Header says 'Pending' and the status
below the document number says 'Suspended' - it is not showing as 'Draft'
Regards
Manian
10.07.2009 12:42 Call to Customer / Partner by SAP
Performed on: 10.07.2009 10:41:59 (UK)
Contact person: SRS Manian
Status of discussion: Customer not reached
Subject:
Called the partner but currently engaged on another line.
Would like to hold a webex.
10.07.2009 12:42 Reply to Reporter by SAP
Dear Manian,
I'm trying to call you but there was no response on your mobile.
When the header says 'Pending', then it means the document is still within the approval process. Please check the Approval Template and see the number of approvers and the number of approvals require d.
The number of approvals and approvers may be greater than 1. In this case, the system waits for other approvers to approve or reject the document. Once all the approvers have rejected the document, th en the document will be released and available for editing.
Best regards,
Lorna Real
Support Consultant
Product Support for SAP Business One
SAP Ireland
10.07.2009 18:11 Reply to Support Center by SRS Manian
Hi:
Thanks for the reply - i tried this and found out the following:
1 - In the approval templates - we had mentioned number of approvals
required as '1'.
2 - in the number of approvers - we had mentioned two users
Though the template requires only one approvals (Either or OR) the system
expects both of them to approve or reject -
Can u please let me why is this behaving like this - or is this is the
way it is designed ? - if this is the way it is designed - i beleive it
is wrong - weneed to give a solution to the customer
regards
Manian
11.07.2009 05:52 Reply to Reporter by SAP
Dear Manian,
Thank you for the information. The behaviour is a current system definition documented as per Note 1321234. I have attached the said Note for your reference. When only 1 approval is required and there are 2 or more persons are allowed to approve the document, the document does not get automatically rejected when 1 person 'rejects' it. The system waits for other approvers to render their decision b ecause a person may still approve or reject the document.
The design is not an application error. If you would like to change this design, please post your requirement in our SAP Business One Product Development Collaboration
forum. You can find the forum in this link:
/community [original link is broken]
The forum is beingmoderated by members of the Solution Management team specialized in certain areas, according to the folder you are in. Partners can impact the design of specific features by posting suggestions and feedback at this forum. Kindly refer to Note 1028874 which describes more on the above process.
As the request will be handled through another process, we kindly request that this support message be closed.
Thank you for your understanding.
Best regards,
Lorna Real
Support Consultant
SAP Product Support for SAP Business One
SAP Ireland
11.07.2009 09:02 Reply to Support Center by SRS Manian
Hi Thanks for the reply - however, the solution given doesnot address the
problem we are beingfaced with our client
Is there a Development Request we can raise so that this problem is
addressed in future
I am going ahead and confirming this Message though
regards
Manian
11.07.2009 10:04 Reply to Reporter by SAP
Dear Manian,
Thanks for the information. I understand the customer's requirement. As previously mentioned, please log a development request in this link:
/community [original link is broken] This is from Note 1028874.
Unfortunately,we at the support centre does not have access to the list of development requests. Hence, kindly follow the process in Note 1028874.
I'm sending the message back to your side for confirmation.
Best regards,
Lorna Real
Support Consultant
Product Support for SAP Business One
SAP Ireland
SAP Notes
Number Short text
0001035200
Issue can be solved via existing documentation
0001111431
Deleting rejected draft documents.
0001167635
Maintenance Policy (L)
0001321234
Status of a document rejected within the Approval Process.Hi Gordon - thanks for the reply - i am sorry i never realized that the message i raised could be messed up like this - the following is a clear message with some paragraphs:
Hi Experts - I have recently raised an incident with SAP about Approval process - the complete message and support reply is as follows - but i believe we need a change in the approval process - if the approval required is only one but you have defined two people (Either or OR) in the approver list - the system should allow the document to be edited if one of the approvers reject it. please let me know and i believe we need a change in design - unless otherwise a solid reason is given to justify the existing design
SRS Manian We have created approval procedure for all the invoices which are entered into the system., The 'Accts' user enters the invoice into the system - the invoice comes for approval to 'Manager' user. When the Manager opens the invoice via Alert window - he/she wants to modify certain information (lines as well as Sales person) and approve it. The invoice which gets opened from the alert window - does not allow the user 'Manager' to modify at all. All the information on the invoice are greyed out. The system should allow the user 'Manager' to modify the information. Since the manager has full authorization to the system.
Reply to Reporter by SAP Dear Manian,
Thank you for contacting us. When the originator sends the document for manager's approval, note that the at that stage, the document is still in the 'Approval Process'. This is because the system is waiting for the 'Manager' to 'Approve or Reject' the document. Hence, looking at the Document, it is still in 'Draft - Pending' Status. When the document is in 'Draft-Pending' Status, the document is not available for editing, because the system considers that it is still in the waiting process. In your case, the manager cannot edit t he document. To amend the document, an action is required from the approver either to reject it first. Once rejected, it can be amended and re-sent for approval. I have checked our knowledge base and noted that there is an article which describes the approval process. Please refer to the Expert on Phone Wiki Article (March 2009) with title: Why a draft documen t in an approval process cannot be modified by the originator? The link will provide the explanation:
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=88735894
I have also attached Notes 1321234 and 1111431 for your reference. Best regards, Lorna Real Support Consultant Product Support for SAP Business One SAP Ireland 10.07.2009 11:59
Reply to Support Center by SRS Manian
Thanks for the reply.
The scenario is when the Manager receives the document for approval, he wanted to edit and add it. Your reply (and documentations) states that it needs to be rejected first before it is available for editing. When it is gets rejected - the person who orignated the document gets an alert and he can edit it. Here the Manager must get an alert so that he can edit the Rejected document. When the 'manager' rejects the document, and goes back to the alert window to open the document - it is still greyed out !! How does the 'manager' reject the document and edits it ? regards Manian
Reply to Reporter by SAP
Dear Manian, If after the Manager rejects it and still the document is not editable (greyed out), it means that the document may still be in the 'Approval Process'. When it is greyed out, what is the status of the document in the header? Does it say 'Rejected' or 'Pending'? If it is still in 'Pending' mode, please verify the number of 'Approvers' set in the 'Stages' tab of the 'Approval Template - Setup' window. If there is more than one user listed as 'Approver', and o nly 1 approval is required, the system provides an opportunity to other 'Approvers' to approve or reject the document. If in your case, the number of approvers is 2, and manager 'rejected' it, the sys tem still keeps the document in Pending status as it waits for another approver's decision to reject or approve it. Also, verify the number of 'Approvals' required. If the number of 'Approvers' who have not rendered their decision is greater than or equal to the 'Approvals' required (e.g. approvers - 2, required ap provals - 2) the system keeps the document within the approval process. This is to allow the other 'Approvers' to decide on the document. I hope this clarifies the behaviour. If you can provide us a step by step screenshot of the issue, this may help us to provide a more accurate response.
Best regards,
Lorna Real Support Consultant Product Support for SAP Business One SAP Ireland
Reply to Support Center by SRS Manian
Hi: The status of the document in the Header says 'Pending' and the status below the document number says 'Suspended' - it is not showing as 'Draft'
Regards
Manian 10.07.2009 12:42
Reply to Reporter by SAP
Dear Manian,
I'm trying to call you but there was no response on your mobile. When the header says 'Pending', then it means the document is still within the approval process. Please check the Approval Template and see the number of approvers and the number of approvals require d. The number of approvals and approvers may be greater than 1. In this case, the system waits for other approvers to approve or reject the document. Once all the approvers have rejected the document, th en the document will be released and available for editing.
Best regards,
Lorna Real Support Consultant Product Support for SAP Business One SAP Ireland
Reply to Support Center by SRS Manian
Hi: Thanks for the reply - i tried this and found out the following: 1 - In the approval templates - we had mentioned number of approvals required as '1'. 2 - in the number of approvers - we had mentioned two users Though the template requires only one approvals (Either or OR) the system expects both of them to approve or reject - Can u please let me why is this behaving like this - or is this is the way it is designed ? - if this is the way it is designed - i beleive it is wrong - weneed to give a solution to the customer
regards
Manian
Reply to Reporter by SAP
Dear Manian,
Thank you for the information. The behaviour is a current system definition documented as per Note 1321234. I have attached the said Note for your reference. When only 1 approval is required and there are 2 or more persons are allowed to approve the document, the document does not get automatically rejected when 1 person 'rejects' it. The system waits for other approvers to render their decision because a person may still approve or reject the document.
The design is not an application error. If you would like to change this design, please post your requirement in our SAP Business One Product Development Collaboration forum.
You can find the forum in this link:
/community [original link is broken]
The forum is being moderated by members of the Solution Management team specialized in certain areas, according to the folder you are in. Partners can impact the design of specific features by posting suggestions and feedback at this forum.
Kindly refer to Note 1028874 which describes more on the above process.
As the request will be handled through another process, we kindly request that this support message be closed. Thank you for your understanding.
Best regards,
Lorna Real Support Consultant SAP Product Support for SAP Business One SAP Ireland
Reply to Support Center by SRS Manian
Hi Thanks for the reply - however, the solution given does not address the problem we are being faced with our client Is there a Development Request we can raise so that this problem is addressed in future I am going ahead and confirming this Message though
regards
Manian
Reply to Reporter by SAP Dear Manian,
Thanks for the information. I understand the customer's requirement. As previously mentioned, please log a development request in this link:
/community [original link is broken]
This is from Note 1028874.
Unfortunately, we at the support centre does not have access to the list of development requests. Hence, kindly follow the process in Note 1028874. I'm sending the message back to your side for confirmation.
Best regards,
Lorna Real Support Consultant Product Support for SAP Business One SAP Ireland -
Approval process (Release strategy of scheduling agreement)
Hi,
Recently we are trying to implement the approval process of scheduling agreements.
Client requirement is when ever there is a change in price irrespective of the following
1. Retrospective price change in any line item
2. Current price change in any line item
3. Future price updation in SA in any line item
4. New addition of line item
the system should trigger the release process (i.e. Approval process).
Our idea is to design the approval process based on document type and net value of SA. Based on which trigger should happened. But when we test it we find the following issues.
1. Trigger is not happening for future date price change or price for new period as the net value of SA is based on validity time.
Becuase the net value change will happen only on that onwards..
Also we are not using any cumulative pallned values in agreements.
Any can suggest the best solution to over come this..or Any user exit is avaliable to handle this issue.
regards,
K.Sundaresan.Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this -
MM Approval Process and email notifications
Hello All,
I am looking for a concrete answer to the following MM/ workflow questions?
1. My Client wants approval process flow: purchaser to Line manager to Head of department to Finance to Material owner.
Is this a 'z' table and development is required to acheive this. Can we do the above process thought the classification system? Please give me more details.
2. How can the client get approval process notifications in email? Again, is this a development? Please give me details.Hi,
1. My Client wants approval process flow: purchaser to Line manager to Head of department to Finance to Material owner.
Is this a 'z' table and development is required to acheive this. Can we do the above process thought the classification system? Please give me more details.
This requirement will be fillfilled by PO Release procedure provided by SAP..
This is pure configuration.
2. How can the client get approval process notifications in email? Again, is this a development? Please give me details.
For this you have to setup Workflow...Consult with your Workflow Consultant.
Utsav -
I am working on a Project Server 2013 workflow. I am creating this using Sharepoint Designer 2013. In this workflow I am using approval process at one stage. I have created a security group SalesManagers in PWA. I want to use this group for workflow approval
process. I want all users of this group get approval tasks.
For this I used START A TASK PROCESS activity in the SP Designer. I clicked on
this user and created task process. But here I could not find SalesManager group which I created in PWA. I was only able to find the users. I can also see
Administrators for PWA . But couldnot find SalesManager or any other security group created in pwa.
Can anyone suggest how I can get the security group created in pwa.NBDevelopment,
I believe SPD only recognizes the SharePoint Groups and not the project server security groups.
The Administrators for PWA, and few other groups like Project Managers for PWA etc., are synced SharePoint Groups with the security groups, which is why they show up in SPD.
You could create a SharePoint Group for the Sales Managers group and use that in SPD.
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:
-
ITEM tab in the Approval Process overview IN srm 7.0 AND EP 7.1
Hi Friends,
I am working in SRM 7.0 with EP 7.1..
1 . I have to remove 'ITEM' tab in the approval process overview screen which is apprearing in Portal. approval process overview screen will be appeared when 'Display / Edit Agents' Button in the Header level of the Shopping cart screen.
2 . Remove Approval Process overview tab in the detail screen of the shopping cart.
Any idea
John.Hi Masayuki,
Thank you for your quik reply.
can you please explain little bit more on this..
2. tab
Easy way is right click, User Setting -> Hide Tab. or User Setting -> More.. Remove display tab
I tried this option but this is each user setting , Can we make this centerlized?
or
Go to SE80 Webdynpro and change the visible property.
I know the webdynpro for this tab but to change this visible property do I need have access key( Core modification ) or any other way to do such as enhancement spot?
John.
Edited by: John peter on Jul 10, 2009 11:16 AM -
ITEM tab in the Approval Process overview
Hi Friends,
I am working in SRM 7.0 with EP 7.1..
1 . I have to remove 'ITEM' tab in the approval process overview screen. approval process overview screen will be appeared when 'Display / Edit Agents' Button in the Header level of the Shopping cart screen.
2 . Remove Approval Process overview tab in the detail screen of the shopping cart.
Any idea
John.Hi Masayuki,
Thank you for your quik reply.
can you please explain little bit more on this..
2. tab
Easy way is right click, User Setting -> Hide Tab. or User Setting -> More.. Remove display tab
I tried this option but this is each user setting , Can we make this centerlized?
or
Go to SE80 Webdynpro and change the visible property.
I know the webdynpro for this tab but to change this visible property do I need have access key( Core modification ) or any other way to do such as enhancement spot?
John.
Edited by: John peter on Jul 10, 2009 11:16 AM
Maybe you are looking for
-
Unable to connect Firefox can't establish a connection to the server at www.google.com. The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer's network connection.
-
I am using ABAP query using LDB. I want to fetch the record(current) within a particular dates for the corresponding pernr. But when i gives validity dates it fetches all the record for the particular pernr. Actually our requirement is to display onl
-
ORA-01017 invalid username/password on execution of process flow
Hi, there are one or two similar issues mentioned in the foum but none are resolved I think. Basically we have target repositories setup with a single user (not the schema owner) used for the location credentials eg. REP1_LOCATION pointing to schema
-
My Ipad had a hard time picking up wifi when i 1st bought it. Now after a couple of months has stopped picking up wifi.
-
Lightroom 2, Keywording and searching
I am not sure if I am missing a step... but when I started updating keywords some older photos. I placed in Zoo Atlanta, Zoo, and Apes. I synched the keywords and tried to use the search feature. TEXT - ANY SEARCHABLE FIELD - CONTAINS ALL and then I