E-Sourcing - Contract Approval Process
I'm trying to develop a contract approval process with our Legal department using the E-Sourcing Contract Module and I don't see a contract approval process in the contract module. Does anyone know if the E-Sourcing Contract Module has a contract approval process similar to the RFx's approval process?
Please let me know.
Thank you,
Mauricio
Edited by: Mobirdies on Apr 19, 2010 11:56 PM
Edited by: Mobirdies on Apr 19, 2010 11:56 PM
Edited by: Mobirdies on Apr 19, 2010 11:57 PM
Hi,
TWE : Togethere Workflow Editor
It is an Editor to develop workflow in xpdl format, which E-Sourcing(ESO)/CLM application understands.
If you create/open exisitng Workflow Defination in ESO/CLM and from Toolbar click Edit Workflow, it will open in TWE !
Thanks,
Vaibhav
Similar Messages
-
Hi,
We are R12.0.6 Service Contracts.
We have a requirement wherein we want to skip the approval flow when a contract is created.
What are the options to achive this ? Is it going to be setups only or would it need code change ?
Thanks in advance
UtCHi UTC,
You can bypass the approval process but u will still have to go through the contract signing process. You can configure approvals manager to automatically approve contracts. Below are the steps
1. Log in with responsibility, Approvals Management Administrator and click on Administrator Dashboard
2. Change the Filter drop down to Transaction Type
3. Enter 'Service Contracts Internal Approval' and click Go.
4. Click the Update icon on the record returned.
5. Click Next until you get to the Mandatory Attributes section (Step 3 of 4).
6. In this page change AT_LEAST_ONE_RULE_MUST_APPLY to set the "Query / Value" to False.
7. Click Next until the end and save the changes by clicking Finish.
Any new contract created will now bypass the contract approval process but will still need to be signed. If you need to skip the contract signing step then I believe you will have to customize the work flow.
Hope this helps!
Thanks,
Sid. -
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 -
N-Level Contract Approval (workflow problem)
Hello friends,
We are using SRM 5.0 , ECS scenario.. My problem is related to N-level contract approval. I had activated workflow WS 14000148 for N-level approval.. In development system it is working fine but in production system I am facing following errors after first release of contract.
Executed Auction Error Message
Exception occurred Error when starting work item
000000008004
PROCESS_NODE Error when processing
node '0000000007'
(ParForEach index 000000)
CREATE Error when creating a
component of type 'Step'
CREATE_WIM_HANDLE Error when creating a work
item
CREATE_VIA_WFM Error within method
CL_SWF_RUN_WIM_FACTORY-
>CREATE_VIA_WFM
GET_WITYPE Unable to determine work item
type for step at node 0000000007
GET_TASK_HANDLE Error when loading task
WS14000085
FIND_BY_WFDWIZ Workflow definition of
task 'WS14000085'
cannot be Activated
Sub-workflow WS14000085 available in main workflow WS 14000075 which is deactivated. But problem is when I am trying to see workflow WS14000085 through SWDD in production, no workflow is there but same workflow I can see in Development system. Any expert have any idea why same workflow I can see in development but I am not able to see in Production system.
Thanks in advance.
Abhijeet PanseHi,
It looks workflow template is missing.
Please check the note 962488 "Workflow definition '&' not in version '&'".
1. Run the function module SWD_WFD_REPLICATE_FROM_9999 and copy it.
2. Re-activate the WF definitions in the transaction SWDD
3. Check Consistency in the transaction SWUD
Also check the sub workflow.
Regards,
Masa -
Customize approval process on AP payment cancellation
Dear all,
Is there any one ever add an approval process to the AP payment cancellation function? Could anyone pls share how you can achieve the customization? Our user requirement is there should be an approver to review the selected payment records for cancellation.
HYHi,
I feel there is one workaround for this issue, but evaluate this as per your requirement.
Enable Journal approval for Receivables Journal Source and periodically post the Journal entries of Receivables to General Ledger.
Ask the approver to approve the receipts in General Ledger. (Using drilldown functionality if required).
If there is any mistake the approver can always ask for reversal of Original receipt and direct the user to enter new one.
Only drawback is Sales Invoices should also be approved. These should be approved blindly.
Regards,
Sridhar -
Dear Experts,
I have a requriement from our company, that when opening vendor code, we want multiple release prococedure, means first sourcing team approve the vendor in system , then QA Team approve the vendor, then Supply chain team approve the vendor in the sytem, then finally the vendor should be approved by CEO. Then vendor is treated as active in sap.
How to achieve this, I have not seen such release procdeure for vendor, please suggest me some workaround, if there is no direct procedure.
My requirement is urgent.
Regards
IshuHi,
This is something not in standard SAP. The approval process of the vendor should be done internally by the management and not supported in SAP. There is only a transaction to create vendors either XK01, MK01 or FK01 all of which are single transactions. The person who creates vendor in your company can be restricted to use the tcode unless the internal approval process done by the management to create the vendor.
Other way is you can think of blocking the vendor which you donot want to use in the procurement activities, this will restrict unwanted vendors entering into the system even by accident.
Regards
Shiva -
Frame contract approval workflow
Hi,
once again I have a problem with a workflow.
I am facing following problem:
I am trying to create my own frame contract approval workflow (the standard doesn´t fullfill the requirements 100%).
When a frame contract is created, BUS2014 releasestepcreated event is raised.
When I change a contract, BUS2012 changed event is raised (there doesn´t exist any changed event for BUS2014).
The problem with that is, that my BUS2012 seems not to be able to handle frame contracts --> there is an error message.
Can anybody give me a suggestion how I can use a change event for frame contracts (want to have the same event like in BUS2012, but for BUS2014).
Many thanks for your help.
ChristophI tried already.
It was not working so I took a look in the event trace.
Following error message occurs.
Feedback after error.
Source (expression '&_EVT_OBJECT.PURCHASEORDER&') of binding assignment is not available.
I tried a test in 'swo1'. Give the frame contract as an instance to BUS2012 --> ' Object does not exist'.
I think that it is not working with this event.
Any other solutions? Is there a way to create a change event for BUS2014 (of course in ZBUS2014), which is triggered when the change event in BUS2012 is triggered? Where do I have to define this?
Thanks for your help,
Christoph -
Hi All,
I am facing issue with SCM document approval process. When I insert new Ad hoc approval path ,worklist is created for the Ad hoc approver but Notification email is not going.
Could some one has faced this type of issue before.
Please help to resolve this issue.
Thanks
KarthikMake sure that the transaction used for this approval has the event AdHoc Insert configured and that the channel is set to Both instead of Worklist. Off course also a notification template must have been assigned to this AdHoc Insert event.
To be found in
Main Menu > Enterprise Components > Approvals > Approvals >Transaction Configuration
See also
PeopleBooks > PeopleSoft Supplier Contract Management 9.1 PeopleBook > Configuring PeopleSoft Approval Framework for Use with Supplier Contract Management -
Reminder Need to Set for Contract Approval
Reminders need to be set for contract approval when no action has been taken.
The correspondent approver/group of approvers need to be informedHere is an approach that was designed by our functional team :
You create an approval group that has just one member and when delegation is required the contract admin can add a new user to that group. This will ensure that approval goes to the delegated user as well.
Of course, the delegated user should be removed from the group once he/she is no more needed.
It involves some manual work but this is an appropriate solution given the restricted functionality of SAP Sourcing in this case.
Members can share their views on this topic as well.
Thanks
Devesh -
RFQ Approval Process through Workflow
Dear experts,
We are on planning phase of RFQ release approval through SAP Workflow. There is an issue I would like to hear from your valuable thoughts.
When an RFQ is created, ME41, all individual bids are collected under a unique collective number. Once price maintain process is done through ME47 for all bidder, we would like to send all RFQu2019s, with necessary information, which are linked to a collective number in one e-mail even if there are tens of RFQu2019s linked a collective number, not one by one sending it as we do in PO workflow process.
Is it possible to realize this case within SAP standard approval process? Because so far I noticed that once fundamental customizing is done after price maintaining step RFQu2019s are send individually, one by one, to approvers.
CheersDear Melih,
I suppose you want to get approved the best offer in the bid. The best practice is to have a strong rules based on predefined criteria which quotation to be choosen by Purchasing. Then PO/contract/scheduling agreement/PIR can be maintained.
What we have done in our system is that the PO created goes for approval based on Chart of authority via Enterprise portal. A report, displaying the key figures from the RFQs in the bid, vendor evaluation scoring for each vendor, if available and some other data, is linked to the workflow item and displayed during approval process.
Regards,
Ognian -
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 -
Can we disable Archive step in Approval process
Guys,
I wanted to know if I can disable Archive step in the Approval process. Right now the issue is I do not want the people to Archive the document by mistake.
1) Is there a way to disable the Archive step?
2) Or is there atleast a way to restrict it based on roles?
Please help me.
Thanks a lot,
DeepakHi,
you cannot configure anything on the Approval process.
If you want to change something you need either modify the standard (if you get the source code) or develop your own process.
The only things you can try, if remove or restrict UI commands.
There are several UI command groups involved.
For example there is the StatemanagementMassGroup with the command statemanagement_archive_mass inside. This you could remove, so that in the layout sets where this group is used, the archive command is gone (e.g. AdminExplorer menu)
But the StatemanagementGroup command group is just a java class and references no commands. So you cannot get rid of the single archive command from the resource context menu. But maybe it is enough for you to remove the whole command group and do approval actions only from a mass menu.
I guess thats the only thing without developing which can be done here.
Regards,
Sascha -
It sounds CRAZY...but it's true and I proved it out over many tests...
We receive a .xlsx File from an outside vendor. If we simply move the file over to our processing Path and then try to source it and process it in SSIS, we get this error...
Exception from HRESULT: 0xC02020E8
Error at Data Flow Task [Excel Source [1]]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB Error has occurred.
Error code: 0x80004005
However, if we open the file and Save It and/or Save As to our processing library path, we can source the .xlsx File and process it accordingly.
Why is this? Is it because something funky is happening under the covers when the the vendor creates and saves the .xlsx File and then when we open and save it on our network it then cleans it up?
Is there anyway that we can get around this? I hate for the processing clerk to have to go through what seems like a meaningless task....but I cannot think of any way around this if we cannot source the original file. And a C# Edit Script using Microsoft.Interpol.Excel
is not possible because we are not allowed to put Microsoft Office on the Server where the SSIS Package will eventually reside.
Any thoughts...suggestions...etc...would be GREATLY appreciated.
Thanks for your review and am very hopeful (Holding my breath) for a reply and possible solution and answer to this strangeness.
ITBobbyP85First of all...THANK YOU ARTHUR!
You're probably sick and tired of seeing my posts out here on this.
We are running Microsoft Office 32-bit which is why I downloaded the 32-bit driver of Microsoft Access Database Engine 2010 from...
http://www.microsoft.com/en-us/download/details.aspx?id=13255
Sooooo I think what you're saying is that it is a Microsoft Office 2010 .xlsx File but utilizing the 32-bit Microsoft Access Database Engine 2010 only allows me to source as Microsoft Excel 2007.
Nowwww....this will run on a Server...soooo a couple of questions...
1.) Are you saying I need to use the 64-bit Microsoft Access Database Engine 2010 in order to process this file without having to open and Save it? Can I do that if we're running Microsoft Office 32-bit? Will I be able to source this on the Server because
we cannot install Microsoft Office 2010 on the Server where this SSIS Package will live and breathe.
2.) How can I tell which Microsoft Access Database 2010 Engine is on the server where this will eventually reside and run? 32-bit or 64-bit?
Welllll...maybe a 3rd question...
3.) Is there anyway to get around this driver dependency? Can I create a script to bulkcopy it and it would simply take what's on the server.
Now mind you...we DO NOT have Microsoft Office installed on our server where this will reside...a licensing issue...
So maybe now this explains my struggles with this damn file(excuse my French and frustration)...and why I was using a C# Edit Script to Open and Save the File until I then deployed it to the server and the Microsoft.Office.Interop.Excel DLL was not available
on the Server because we cannot install Microsoft Office on the Server.
Sooooo it seems as though I'm back at square one.
UGH!
Any additional help you can suggest or even if we can continue this "offline" would be GREATLY GREATLY appreciated.
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
Maybe you are looking for
-
I have a new 4g Iphone - Telstra (Australia) disabled my old 3g and enabled the 4g so the 3g is just enabled to show contacts and photos etc. I want to download my photos and contacts from the 3g. trouble is that my internet is dial up only at home
-
Outgoing Payment with Bank Charges
Most of the client wants to do payment (in/out) to have more than one charges in the same transaction. In SAP B1 2005B can have one bank charges a/c setting from incoming, but how is the process on outgoing. there's no bank charge can be selected. If
-
I've actually got three questions: I have been given a Mini, a dock, and a cable which attaches to the dock with a USB at the other end. When I plug the USB in the only thing that happens is a battery synbol comes up and a triangle icon with an excla
-
Hi there, I wanted to order a skype number but I have problem while processing to pay. Then I tried again and again by choosing new number but I didn't noticed that that it reserved the number and each time I failed, the payment status changed to pen
-
The pop up box only gives me the option to 1) download (which it won't, 2) ask me later, 3) x to close the box. Every day it comes back and I want to stop it.