Approval Process with BB

Hi gurus,
My client needs approval crm activity with BlackBerry.
I have thought to create a custom web dynpro abap with 2 buttons approve & reject, when user select one or other button automatically approve or reject activity.
According to you is there any limit or warning about the solution?
I have to install something on BB?
How Can user enter with user and password?, Where Does the system checks the authentical data?
I'd like to know if the way is correct or there is another simply way ..and above all is there something I have no consider...
Thank you in advance
Vanessa..

Hi,
Yes, it should work. However this kind of application won't work in offline mode so you should ask the end users if this is a satisfactory solution.
You should also implement some kind of push so the user wont' have to check for new requests but will be notified when a new request awaits his/her approval. You can check RIM website for more information : http://us.blackberry.com/developers/platform/pushapi.jsp
Regards,
Pierre

Similar Messages

  • Req approval process with Purchasing groups

    Hi Gurus,
    Can anybody please help me with this. I need to setup the req approval process with purchaisng groups. how do i do that? The scenario is this: 1) A computer is requested and it is worth 1200 USD and the requestor puts the pur grp in the PR. since this is level 1 the email should only go to one person. ( The levels are 1000 -4999 - level1, 5000 - 9999 level2, 10000 and above level3). Can anybody please help me with this. Quick response is greatly appreciated
    thanks
    Anusa
    Edited by: anusha vemulapati on Mar 10, 2009 9:44 PM

    Hi,
    The steps are as follows:
    Create Characteristics & link to comm. structre (CEBAN for PR)
    Create Class & link to characteristic
    Create Release Groups & link to class
    Create Release Codes
    Release Indicator
    Set up strategies
    - Strategies & Codes
    - Prerequeirements
    - Status
    - Assign values for strategies
    Set overall / item for doc type (PR only)
    Create and allocate autorisation profiles
    You can see the same in SAP123.com with screen shots.
    REgards
    Ram

  • 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

  • Approval Process - Rejection

    Our customers needs an change of the Approval Process.
    I will describe the problem.
    In this company there is a Approval Process with two approver. For rejetion the codument both have to reject the document, because for the approve they needs onl one approver.
    So the problem is, then one of the approver is not in the office, the business process is interrupted. This and other customer from our site have very many Documents in the Approval Process.
    The needed change is, that only one of the approver needs for rejection of the Documents. In the moment the "Approve" State has a higher Priority than the "Rejection". That`s not the real in the life. When one has rejected the Document, the state of the Document has to be set to "Rejected". Example: If the two Approver are the sales director and the other one is the chief of the company. First the chief of the company had rejected the Document, the sales director is able to "approve" the Document. That`s not good.
    So we need a change in the Approval Process. In my eyes, their are three different or corrospodending ways to reech the goal
    1) The system set, that only 1 "Rejection" is needed for the "Rejection of the Document"
    2) For the "Rejection" we get also the possibility to define how many "Rejections" needs for change the state of the approval processs
    3) We get the possibility of a hierachie in the approval process, so that the chief of the company can not be overclocked from a other employee of the company (this way is only an additional for one of the other ones).
    Best regrads
    Jörn Pelikan
    CIB-Computer

    Hi Caroline,
    This is by design.  All approvers have to reject in case of rejection. You may create an alert in case of rejection to all approvers for quicker action.
    You may go through this:
    Rejected approval not working.
    Thanks,
    Gordon

  • Approval Process Completion Conditions for different stages

    Hi
    I have an approval process with 2 stages. The first stage has multiple approvers running in parallel. Only one user needs to approve for it to progress.
    In the second stage it needs to be approved by all users.
    I can set the completion conditions to complete after one person approves but this will also set it for the second stage. 
    Is it possible to have different completion conditions for each stage or im i better just having a second approval proccess action?
    Hope that makes sense and thanks

    Hi,
    According to your post, what do you mean “you have an approval process with 2 stages”?
    In SharePoint 2013 workflow, a workflow can add many stages into it, and a stage can add many same or different actions into it.
    So, each separate action you added in a workflow must be in a stage, will not be in two stages.
    If you want to make the workflow complete when one user approved the task process in a stage, I recommend that you can directly set the “Completion Criteria” option to “Wait for specific response” as below in the “Task Option” of the “Start a Task Process”
    action.
    If you want to make the workflow go to the second task process in the second stage when one user approved the task process in the first stage, I recommend that you can set the “Completion Criteria” option to “Wait for specific response” as below in the “Task
    Option” of the “Start a Task Process” action in the first stage.
    Then, you can set the “Completion Criteria” option to “Wait for all response” as below in the “Task Option” of the “Start a Task Process” action in the second stage.
    And, you can go to “Start Options” to check “Start workflow automatically when an item is created”, publish the workflow and test whether it works in your environment.
    The workflow is shown as below:
    Best Regards,
    Yumi Fu

  • Approval Process Not triggering?

    Hello,
    I have created a simple Approval process in which request should go to the Beneficiary manager through JDEVELOPER. I have also registered this Approval process with OIM.
    After that i have created two Approval policies..
    REQUEST LEVEL--
    This is Auto Approved.
    Approval Rule :: Template Name equals Provision Resource.
    Set Priority : 1 (Request Type=Provision Resource)
    OPERATIONAL LEVEL --
    Approval Process attcahed at this level.
    Approval Rule :: Template Name equals Provision Resource.
    When i am creating a request for a particular resource the request is getting assigned to XELSYSADM by default (as per the Developers Guide for OIM 11g, if no approval policy is attached with the template the default Approval process gets trigerred and the request gets assigned to XELSYSADM.)
    Can somebody help me by telling why the Default Approval process is getting triggered and not the one which i have attached at the Operational level?
    Am i missing Something?
    Thanks in Advance.

    As i have mentioned earlier, it is configured such that the appropriate approval process is triggered when a request for particualr resources is requested.
    There are multiple tasks in each one of the approval process.
    The approvals were triggering well 2 days ago and suddenly there seams to be a problem in the approval triggering.
    The approval process was not edited / updated for any of these resources. Wondering why suddenly OIM does not work well for the approval triggering???
    here the problem is none of the configured approval processes are triggering. Its not just one approval process but all 12 approval processes (including standard approval) are not triggering when the request is raised.
    Appreciate your help till now, please suggest me how to make OIM trigger the approvals again!
    Thanks

  • 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

  • What is the standard method to integreate with AME for the approval process

    I have developed a new OAF page and registered under Employee Self Service menu.
    What is the standard method to integreate with AME for the approval process.
    Appreciate your early response

    Any one used AME with the new OAF pages?
    Please share , how you use AME with OAF page

  • Post Write-off from Disputes with Approval Process

    Hi,
    we want to post write-offs using the dispute escalation process. before the write-offs are posted they need to go for approval. is there any functionality within dispute mgmt which can be leveraged to post write-off from the dispute with approval

    Hi,
    When you set up the escalation proces with reason code write off you can do it in two ways. Set up a Workflow for the approval process. Escalations are specifically meant for that. This is possible with the standard workflow.
    If you want to work w/o workflow. Then you can have the responsible person go into UDM_disputes query all specific escalation reason and e.g. change status or maybe create a different escalation reason. (E.g. Write off request/ Write off granted)
    You can check if you can change the roles that certain functions can only set certain reasons.
    Rgds,
    Richard

  • Need Help Configuring Membership Website with External Approval Process

    I am working on configuring a membership website for a group of scientist.  Here are the interesting requirements.  Any brainstorming would be helpful.
    1 - A prospective member applies online. Within the application the prospective member has to include a reference for previous work proving his qualifications and naming a reference to confirm the qualifications.  The prospective member has to include the reference's name and email address.   (Site visitor creats a new user-submitted webapp item, easy enough.)
    2 - The application needs to kick off a workflow to an external site visitor (someone who doesn't have a site login).  This reference needs to confirm of reject the prospective member's qualifications.
    3 - If the external site visitor approves the reference, then the membership director needs to be emailed of the approval.  This approval should then kickoff another approval process to ask the membership director for his approval.
    4 - If the external site visitor rejects the reference, then the membership directory needs to be emailed the rejection notification.  (If the reference rejects then there will be some sort of appeal process or ability to start over or submit a different reference.)
    5 - If the reference approves and the membership director approves, then the prospective member is notified and submitted an invoice to pay.  His memberhsip is not active until he pays.
    6 - Once the member pays, then he appears in the online directory.
    7 - The member will also be able to login and edit his profile as needed.
    That about sums it up.  Any ideas??
    THANKS!

    1. Do I need to connect the two base stations via an ethernet cable?
    OR
    Can I simply plug the second base station into a power outlet in any room, along with the external hard drive connected to it's USB port?
    Airport Utility would not even recognize the second base station unless it is using an ethernet LAN-to-LAN connection. (It would not recognize the second base station with WAN-to-LAN connection.)
    You basically have three choices here that will allow the second AEBSn to share the attached USB HDD:
    Wired: Interconnect the two AEBSns by Ethernet; reconfigure both base stations into a roaming network.
    Wireless: Configure both AEBSns for an extended network. Note: This is what Lowell Tuttman is referring to.
    Wireless: Configure the second AEBSn as its own wireless network. This would work but would require network clients to switch network to access the drive or access the Internet. Not really practical and not recommended.
    The following Apple Support link provides very detailed information on setting up either a roamng or extended network with multiple AirPorts.
    2. Since I don't really care about the second base station utilizing the internet connection, do I set it up in Airport Utility as "create a new wireless network"?
    This is the current setting and I have a steady green light. However, Time Machine does not recognize the disk.
    In the first choice I provided, the second AEBSn would be configured to both "Wireless Mode = Create a wireless network" and "Connection Sharing = Off (Bridge Mode)."

  • Approval process is skipping with update user

    Hi,
    I have approval process before updating a user (the oganization in which the user exists has approvers assigned to it). I am using the default Lighthouse Approval subprocess.
    But when i try to update a user, the workflow is going inside the "Lighthouse Approval" subprocess but the "getApprovals" activity (in the approval subprocess) is returning null. So the approval workitem is not being created.
    Can anyone help me out in this? Am i missing anything here.
    Thanks

    I belive the approvals only works for when someone is assigned the role, not when they are updated.
    Dana Reed
    Senior Identity Management Architect
    AegisUSA
    Denver, Co

  • N-step approval process for PO in SRM 7

    Here are a couple of questions I have regarding N-Step approval configuration for PO in SRM 7 Process Controlled Workflow:
    1) It's our business requirement that the last-change person of the PO is defined as the first approver in the chain. I tested with RR_EMPLOYEE and a hard-coded user BP number (my own), but got error "Strategy RR_EMPLOYEE did not determine any approver". Changing to any other user's BP number worked. So I am guessing the buyer himself can not be an approver. Since this is a business requirement, we wouldn't mind developing enhancement to work around this restriction. If you could point me to the place where this is checked, that would help me.
    2) I have set up the process level configuration as such:
    100     ZEV_PO_SL_APPR_001     PO  approval level 1     RR_EMPLOYEE     Specify Employee for Approval
    200     ZEV_PO_SL_APPR_002     PO  approval level 2     RR_MANAGER     Get Creator's Line Manager for Approval
    300     ZEV_PO_SL_APPR_003     PO  approval level 3     RR_MANAGER     Get Creator's Line Manager for Approval
    The corresponding expressions are simply checking against the PO total value, such as -
    0V_PO_POTOTALVALUE >= 0 AND 0V_PO_POTOTALVALUE < 1,000
    0V_PO_POTOTALVALUE >= 1,000 AND 0V_PO_POTOTALVALUE < 25,000
    0V_PO_POTOTALVALUE >= 25,000
    But when I checked the Approver list with a PO with total value > 50,000, only the first level is triggered and listed. And once approved, the PO went into "Ordered" status. But it should have gone through 3 levels of approval. I'd greatly appreciate it if you could point out what might have been wrongly defined in my configuration.
    Thanks!

    Hi,
      1) It's our business requirement that the last-change person of the PO is defined as the first approver in the chain. I tested with RR_EMPLOYEE and a hard-coded user BP number (my own), but got error "Strategy RR_EMPLOYEE did not determine any approver". Changing to any other user's BP number worked. So I am guessing the buyer himself can not be an approver. Since this is a business requirement, we wouldn't mind developing enhancement to work around this restriction. If you could point me to the place where this is checked, that would help me.
    SAP recently released the consultant OSS note to handle this issue.. when the release the SRM 7.0 , SC requestor or PO creator ( Buyer ) cant be in the approval list.. later on they release a OSS note to handle this issue.. 1551561\
    2) I have set up the process level configuration as such:
    100     ZEV_PO_SL_APPR_001     PO  approval level 1     RR_EMPLOYEE     Specify Employee for Approval
    200     ZEV_PO_SL_APPR_002     PO  approval level 2     RR_MANAGER     Get Creator's Line Manager for Approval
    300     ZEV_PO_SL_APPR_003     PO  approval level 3     RR_MANAGER     Get Creator's Line Manager for Approval
    The corresponding expressions are simply checking against the PO total value, such as -
    0V_PO_POTOTALVALUE >= 0 AND 0V_PO_POTOTALVALUE < 1,000
    0V_PO_POTOTALVALUE >= 1,000 AND 0V_PO_POTOTALVALUE < 25,000
    0V_PO_POTOTALVALUE >= 25,000
    But when I checked the Approver list with a PO with total value > 50,000, only the first level is triggered and listed. And once approved, the PO went into "Ordered" status. But it should have gone through 3 levels of approval. I'd greatly appreciate it if you could point out what might have been wrongly defined in my configuration.
    once you implement the OSS note Q1, you can build the custom RR resolver to handle this issue with in one process level.. but you have to implement the process level BADI as well.. please refer /SAPSRM/BD_WF_PROCESS_PO badi for more details
    Saravanan

  • 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

  • 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

  • How to use a pwa group in CREATE A TASK PROCESS in SPD 2013 for project server workflow approval process

    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:
      

Maybe you are looking for