1-step SC approval workflow - error awaiting approval

Hi all,
I am configuring 1-step SC approval workflow but it gives me the status as 'awaiting approval' when i click on check status of SC and the 'Manager'[user] doesn't receive the mail. can someone help me on this?
Regards,
roopesh

Hi Roopesh,
*) activate SAPCONNECT (Transaction SICF)
) Transaction SCON - define node SMTP (specify mail server, port, codepage, internet as supported address, "" as address area
*) define job for mail sending
*) assure that all users have e-mail in their master record
*) maintain domain using transaction SCOT.From menu -> Settings ->Default Domain. ( eg ibm.com )
*) In the attribute of person in organization structure FORWARD_WI should be 'X'
*)Schedule a report RSWUWFMLEC to send E-mail notification for new work item
this wil help
smita

Similar Messages

N Step BADI Approval Workflow Error in SRM 7.0

Hi,
I have implemented SC Workflow Approval based on line item(sequential approval). I implemented process controlled workflow for this using N step Badi. Necessasy configuration done for each level at schema. All steps are executed per line item and agents determined using N step Badi /SAPSRM/BD_WF_RESP_RESOLVER.
Even in SC after the document is ordered, in approval overview tab i see the all level sequence with approvers name for that line item.
But when approved by first approver, it doesnot move to the next level for approval and the SC is approved bypassing all approvers in the following levels.
For example, if there four levels of approvals for one line item. as soon as the first approver approves the SC is approved and in SC Approval Overiew tab that contained four level of approval in it is now reset to one level with SC marked as appproved.
Have anybody come across this error.
Not able to figure out why it is happening so... need some expert advice.
Thanks in Advance.

Hi Masa .. thanks for your reply.
Was on vacation so could not reply.
I have below settings in SRM for SC
Process Level definition should be like this.
Level Eva.ID ; Resolver Task ID Decision Type
100 L100 R100 40007953 Item-Based decision for Partial Doc.
200 L200 R100 40007953 Item-Based decision for Partial Doc.
300 L300 R100 40007953 Item-Based decision for Partial Doc.
I have implemented /SAPSRM/BD_WF_RESP_RESOLVER for R100.
for grouping we are using line item number ... so each line item is a group.
Below are issues that i am facing now.
For say 2 line item in a SC... with 3 level of approvals for each line item. I am not able to approve one line item in a sequence. For example: If for first line item, when I approve level one .. then the workitem doesnot move to 2nd approver's inbox for that line item. Now if second items (asssuming there are only 2 line items in SC) first approver has approved then i see all second level of approvers available for all line item.
In short system waits for all one level approvers to approver for all line item and when all the line items are approved at one level then the workitems are available for seconds level of approval.
Is this the standard behaviour?
As per our requirement we wanted one line item shoudl follow the approveral sequence without being dependent on other items approval.

Vendor Approval Workflow error

Hi,
I tried (unsuccessfully so far) to turn on the standard workflow for Vendor approval (conveniently called: VendorApproval)
However when I try to change a vendor (thus triggering the workflow) I receive the following message:
op Fiatteringsproces (ID = VendorApproval, definitie-ID = ApproveVendors, ingangsdatum 2007-01-01, thread-ID 32) (18081,1056):1:1, Step nbr 1 (18081,1058) EOAW_CORE.ENGINE.DefStepInst.OnExecute Name:Activate PCPC:8036 Statement:114
Called from:EOAW_CORE.ENGINE.PathInst.OnExecute Name:Launch Statement:68
Called from:EOAW_CORE.ENGINE.StageInst.OnExecute Name:InnerLaunch Statement:206
Called from:EOAW_CORE.ENGINE.StageInst.OnExecute Name:Launch Statement:224
Called from:EOAW_CORE.ENGINE.AppInst.O
Aan dit bericht wordt een uitzondering gehecht zodat er een stapeltracering kan plaatsvinden.
The last sentence is something like: An exception is added to this message so stacktracing can occur (or take place).
Any thoughts on this?
What I have done so far:
- Added a row to PS_EOAW_IDS for: VNDR_AF_XREF (since there was no row
Thanks in advance for reading!

After some more trial and error, the error was caused by a user. After the user was removed from the list (user list was based on a query using a specific role), the workflow worked correctly.

Approval workflow error when creating a new custom entity in FIM 2010 R2

Hello,
i'm hoping somebody here can help, me i've been struggling with this for some time now. On a fresh FIM installation i create a custom entity named "Role" and add a few custom attributes.
I then create an approval workflow and MPR for normal users to create entities of type Role, but another user must approve this request. The other user has a working mailbox - i've tried firing an action workflow that sends a mail notification when someone
creates a new role and it is working fine. But, when i enable my approval workflow (the only field i changed from default is the approver) on the MPR, the workflow always failes with the message:
Error processing your request: The operation was rejected because of access control policies.
Reason: The server workflow rejected the operation.
Attributes:
Correlation Id: 750a558a-d3e4-4216-b16a-e76d79f011ec
Request Id: feaabbc9-dea4-49a3-8b29-65b77de6f8fd
Details: The Workflow Instance '04202cc0-14a3-410c-a3fc-2d6e5d25ebe6' encountered an internal error during processing. Contact your system administrator for more information.
I enabled tracing and this is what i found:
Microsoft.ResourceManagement Verbose: 0 : Creating WorkflowServiceHost for XOML Definition:\n<ns0:SequentialWorkflow ActorId="00000000-0000-0000-0000-000000000000" RequestId="00000000-0000-0000-0000-000000000000" x:Name="SequentialWorkflow"
TargetId="00000000-0000-0000-0000-000000000000" WorkflowDefinitionId="00000000-0000-0000-0000-000000000000" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/workflow"
xmlns:ns1="clr-namespace:System.Workflow.Activities;Assembly=System.WorkflowServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856
    ThreadId=8
    DateTime=2013-09-04T15:17:10.0496188Z
Microsoft.ResourceManagement Information: 1 : 1 : : Invalid Element 'ReceiveActivity.WorkflowServiceAttributes' found while deserializing an object of type 'Microsoft.ResourceManagement.Workflow.Activities.ApprovalActivity'.
    ThreadId=8
    DateTime=2013-09-04T15:17:10.1277486Z
Microsoft.ResourceManagement Information: 1 : 1 : : Invalid data found while deserializing an object of type 'Microsoft.ResourceManagement.Workflow.Activities.ApprovalActivity'.
    ThreadId=8
    DateTime=2013-09-04T15:17:10.1277486Z
Microsoft.ResourceManagement Verbose: 0 : A WorkflowRuntime is not available for this WorkflowDefinitionVersionKey '20'.
    ThreadId=8
    DateTime=2013-09-04T15:17:10.1277486Z
Microsoft.ResourceManagement Error: 3 : Workflow host activation failed for workflow definition id : 231457c6-d044-4cc7-839f-98e5cf88f514, version key: 20. Exception: Object reference not set to an instance of an object.   at Microsoft.ResourceManagement.Workflow.Hosting.HostActivator.ActivateHost(ResourceManagementWorkflowDefinition
workflowDefinition, Boolean suspendWorkflowStartupAndTimerOperations)
   at Microsoft.ResourceManagement.Workflow.Hosting.HostActivator.RetrieveWorkflowDataForHostActivator()
    ThreadId=8
    DateTime=2013-09-04T15:17:10.1277486Z
Microsoft.ResourceManagement Information: 1 : The service has updated the list of active hosted workflow definitions to sequence number '1'.
This happened on two separate FIM deployments, but both of them were set up in the same way. What am i missing here?
Thank you,
Martin

(...) What am i missing here? (...) - Sharepoint 2013 and probable bug in FIM related to it. Check this thread for workaround
and resolution:
http://social.technet.microsoft.com/Forums/en-US/1b76672d-1276-4c71-b9fc-5bb1fcb36877/event-id-3-with-approval-activity?forum=ilm2
Tomek Onyszko, memberOf Predica FIM Team (http://www.predica.pl), IdAM knowledge provider @ http://blog.predica.pl

PO Approval workflow error

I customized POAPPRV (PO Approval Workflow) and uploaded it successfully to DB. Now when I try to view the workflow for a new PO it gives following error
Failed Activity PO Approval Top Process (Custom)
Activity Type Process
Error Name WFENG_ACTID
Error Message 3121: Activity ID '185096' is invalid as of date '01-JUN-09'.
Error Stack Wf_Activity.InitCache(185096, 01-JUN-09) Wf_Activity.Info(185096, 01-JUN-09) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185096, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185097, ACTIVITY_PERFORMED) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 184483, #NULL) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 184483, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 184483, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 184481, N) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 184481, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 184481, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 184487, #NULL) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 184487, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 184487, 50) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185097, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185173, ACTIVITY_PERFORMED) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185466, #NULL) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 185466, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185466, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185470, F) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 185470, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185470, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185476, #NULL) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 185476, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185476, 50) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185173, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185112, Y) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 185112, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185112, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185171) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185428, #NULL) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 185428, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185428, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185424, N) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 185424, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185424, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185426, N) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 185426, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185426, 50) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185171, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185150, ACTIVITY_PERFORMED) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 185150, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185150, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185165, #NULL) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 185165, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185165, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185138, ACTIVITY_PERFORMED) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 185138, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 185138, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 185103, VALID_ACTION) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 184537, #NULL) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 184537, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 184537, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 184559, ACTIVITY_PERFORMED) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 184559, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 184559, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 184547) Wf_Engine_Util.Execute_Activity(POAPPRV, 27700-85826, 184547, RUN) Wf_Engine_Util.Process_Activity(POAPPRV, 27700-85826, 184547, 50) Wf_Engine_Util.Complete_Activity(POAPPRV, 27700-85826, 184545) Wf_Engine_Util.Execute_Activi
Any clue why this would happen would be appreciated. Thanks. Ash.

I faced the same error just now. it has been fixed by re-loading the wf..

PO error: Awaiting approval?

Hi,
I'm currently experiencing errors when I try to Process my PO (with the Purchaser role)? It sets the status to Awaiting Approval, even though there are not approvers required, when I check the approval tab?
I can see the PO in the Enter PO Response tab? But why do I need to do this??
We using ECS with SRM 5

Hi
<b>Please go through the following SAP OSS Notes -></b>
Note 659907 - Purchase order: Incorrect messages via approval
Note 1054044 - BBP_POC:- Professional Purchaser Unable to Change a PO
Note 909012 - PO Change: Error in version comparison for deleted items.
Do let me know. Hope this will help.
Regards
- Atul

Three State Approval Workflow Error

I have created one Task List. Add Three state approval workflow to it.
When i created New Task. It started workflow. But after couple of minutes it throws error "Error Occured". How to find error.
Please let me know. If you know any resolution for workflow error then also let me know.
Thanks in advance.

Hi,
Please go to the task list settings page, click Assigned to column and check "No" for "Allow multiple selections", then check whether the issue still exists or not.
Here are two threads for your reference:
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/9231b505-7e78-4e98-b6c0-02ad85b247c3/error-occured-three-state-workflow-multiple-selection?forum=sharepointcustomizationlegacy
http://social.technet.microsoft.com/Forums/sharepoint/en-US/5a9f37ea-40b4-494b-b4af-db15be9d91ff/error-occured-three-state-workflow?forum=sharepointgenerallegacy
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

OIM 11g Approval Workflow - Error

Hi All,
I have created a approval workflow (Operational) in OIM11g. Have deployed it as a soa-composite and registered with OIM. Till here everything went fine.
I have created an apporval policy, to assign to requests of a specific type of resource .
When the resource is requested, the approval workflows is gettign triggered,but the request goes to failed state.
I am getting any exceptions in the logs / on the console.
Has anyone encountered this kind of issue.
Vicky

vicky wrote:
Hi All,
I have created a approval workflow (Operational) in OIM11g. Have deployed it as a soa-composite and registered with OIM. Till here everything went fine.
I have created an apporval policy, to assign to requests of a specific type of resource .
When the resource is requested, the approval workflows is gettign triggered,but the request goes to failed state.
I am getting any exceptions in the logs / on the console.
Has anyone encountered this kind of issue.
VickyCheck your SOA server through the em and that should show you your request and the fault states and everything .. that should give you an idea on what is going wrong ...

OOTB Approval workflow and content approval

I have successfully utilized the OOTB Approval workflow to manage the content approval status for document libraries.
But when I attempt the same on a list (custom, links, announcements...etc)..... the approval goes through without a problem but the content approval status remains in "Pending" status.
Does the approval workflow NOT work for lists? (And only document libraries?)
I found this article that describes that the solution is to uncheck the "start this workflow when an item is changed":
http://support.microsoft.com/kb/2908491
...which is somewhat ridiculous and pretty much forces the user to have to initiate the workflow manually each time they change the item?
At any rate... I did what the article suggested and manually initiated the WF and the approval status still remains in pending mode.
Can someone help clarify this for me?
Thanks in advance

Please make sure that Publishing Approval Workflow feature is enabled in Site Collection Features. Otherwise their should be no issue.
Adnan Amin MCT, SharePoint Architect | If you find this post useful kindly please mark it as an answer.

SharePoint Designer 2010 approval workflow error revisited

Karen K started a question around:
Errors
were found when compiling the workflow. The workflow files were saved but cannot be run.And when I click on the "Advanced" button in the error message, I see this detailed error:
(0,
0) Activity 'ID4' validation failed: Property 'DurationUnit' has invalid value. Field type 'System.String' does not match with the expected type 'Microsoft.Office.Workflow.Actions.DurationUnit'.)
The full problem/solution is posted:
http://social.technet.microsoft.com/Forums/en/sharepoint2010customization/thread/332e49c6-6471-4374-9c9f-9bcf334f9c69
However,
I can't figure how to do step 2:
2. Select
the Action and click the “Advanced Properties”
ribbon control;
3. Find
the “DurationUnit” property in the properties
box, and click the “fx” link in the box;
Which
"Select the Action" am I looking for? I looked everywhere.
Help

RoyKim, it's simpler than you think, which is why it probably stumped you. This is all you do:
In SPD2010, click on the Workflows Site Object
Find your workflow and click on it to open the top-level settings page
Click edit workflow
This is the page where you perform the steps from that other thread
Single-click the row that says "Start Approval process on CurrentItem etc etc"
Then click Advanced Properties in the ribbon
Scroll down until you find DurationUnit
Click the fx button on the right and re-select Parameter: Duration Units as instructed
SharePoint Architect || Microsoft MVP ||
My Blog
Planet Technologies ||
SharePoint Task Force

2010 Review Approval Workflow Error - Outlook cannot open a new form

Hi,
I set up an Approval - SharePoint workflow on a document library list in a webpart. When the approver got the email and tried to approve from outlook, she received the following error. She has approved documets in the past for the same page.
Can anyome please help me troubleshoot this? So much appreciated!
Word Error:
Could not open. http://<site ulr> _layouts/formsResource.aspx?templateFile=http://<site url_catalogs/wfpub/Approval - SharePoint 2010/Review Approval_Task_1033.xsn
Outlook Error:
Outlook cannot open a new form. To open the file, access to the folliwng form template is required
http://<site ulr> _layouts/formsResource.aspx?templateFile=http://<site url_catalogs/wfpub/Approval - SharePoint 201o/Review Approval_Task_1033.xsn

can she open the approval form in web browser instead of Outlook?
According to the error message, it seems that the user does not have permission for the file http://<site url/_catalogs/wfpub/Approval - SharePoint 201o/Review Approval_Task_1033.xsn.
can she open see this file in SharePoint designer 2010? that is, open the site with SharePoint designer and navigate to All Files->_catalogs->wfpub->Approval - SharePoint 201o. If she can not see the file there, ask the workflow creator to publish
the workflow again. I had experienced strange issue in SharePoint designer 2007 and solved by check out all the workflow files and check in again
http://social.msdn.microsoft.com/Forums/en-US/sharepointworkflow/thread/b533cfa5-e858-4ff9-bd0d-96d19946b789.

OIM11g- Role Approval workflow Error

I am getting the follwing error message when I follow Custom Approval Process for Assign Role Scenario.Metalink article [1207077.1] Sample #8 Custom Approval Process for Assign Role Scenario
Prototype for invoking an OIM API from a SOA Composite
RTM Usecase: Organization Administrator
java.lang.reflect.InvocationTargetException
     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 oracle.iam.platform.OIMClient.loginSessionCreated(OIMClient.java:209)
     at oracle.iam.platform.OIMClient.login(OIMClient.java:136)
     at oracle.iam.platform.OIMClient.login(OIMClient.java:129)
     at orabpel.approvalprocess.ExecLetBxExe0.execute(ExecLetBxExe0.java:184)
     at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELxExecWMP.__executeStatements(BPELxExecWMP.java:42)
     at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:158)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2543)
     at com.collaxa.cube.engine.CubeEngine._handleWorkItem(CubeEngine.java:1165)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1071)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:328)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4430)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4361)
     at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:698)
     at com.collaxa.cube.engine.CubeEngineSecurityManager$2.run(CubeEngineSecurityManager.java:84)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:47)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:79)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.security.Security.runAs(Security.java:61)
     at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
     at com.collaxa.cube.engine.CubeEngineSecurityManager.performActionAsSubject(CubeEngineSecurityManager.java:67)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:551)
     at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:673)
     at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:293)
     at sun.reflect.GeneratedMethodAccessor1756.invoke(Unknown Source)
     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.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:94)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:81)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:112)
     at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105)
     at sun.reflect.GeneratedMethodAccessor859.invoke(Unknown Source)
     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.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
     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.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 $Proxy309.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39)
     at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:140)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:662)
Caused by: javax.ejb.EJBAccessException: [EJB:010160]Security Violation: User: '<anonymous>' has insufficient permission to access EJB: type=<ejb>, application=oim#11.1.1.3.0, module=iam-ejb.jar, ejb=ClientLoginSessionService, method=loginSessionCreatedx, methodInterface=Remote, signature={java.lang.String,java.lang.String}.
     at weblogic.ejb.container.internal.MethodDescriptor.checkMethodPermissionsBusiness(MethodDescriptor.java:581)
     at weblogic.ejb.container.internal.BaseRemoteObject.checkMethodPermissions(BaseRemoteObject.java:111)
     at weblogic.ejb.container.internal.BaseRemoteObject.preInvoke(BaseRemoteObject.java:274)
     at weblogic.ejb.container.internal.StatelessRemoteObject.__WL_preInvoke(StatelessRemoteObject.java:41)
     at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:24)
     at oracle.iam.platformservice.api.ClientLoginSessionService_1nfafx_ClientLoginSessionServiceRemoteImpl.loginSessionCreatedx(Unknown Source)
     at oracle.iam.platformservice.api.ClientLoginSessionService_1nfafx_ClientLoginSessionServiceRemoteImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Login Successful
The request ID is 372
*This is +the error message from the Java Embedding task in the bpel.*
The bpel is going to the faulted state with the following errors.---------------------
<Nov 11, 2011 5:36:35 AM EST> <Error> <oracle.soa.bpel.engine> <BEA-000000> <The execution of this instance "100064" for process "ApprovalProcess" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK" >
<Nov 11, 2011 5:36:35 AM EST> <Error> <oracle.soa.bpel.engine> <BEA-000000> <The reason was The execution of this instance "100064" for process "ApprovalProcess" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK" . Root cause : null>
<Nov 11, 2011 5:36:35 AM EST> <Error> <oracle.soa.bpel.system> <BEA-000000> <Error while invoking bean "cube delivery": Exception not handled by the Collaxa Cube system.
an unhandled exception has been thrown in the Collaxa Cube systemr; exception reported is: "java.security.PrivilegedActionException: ORABPEL-02199
JTA transaction is not in active state.
The transaction became inactive when executing activity "100064-BpInv1-BpSeq2.6-2" for instance "100,064", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
The reason was The execution of this instance "100064" for process "ApprovalProcess" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK" .
Consult the system administrator regarding this error.
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.security.Security.runAs(Security.java:61)
     at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
     at com.collaxa.cube.engine.CubeEngineSecurityManager.performActionAsSubject(CubeEngineSecurityManager.java:67)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:551)
     at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:673)
     at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:293)
     at sun.reflect.GeneratedMethodAccessor1756.invoke(Unknown Source)
     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.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:94)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:81)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:112)
     at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105)
     at sun.reflect.GeneratedMethodAccessor859.invoke(Unknown Source)
     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.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
     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.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 $Proxy309.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39)
     at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:140)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:662)
Caused by: ORABPEL-02199
JTA transaction is not in active state.
The transaction became inactive when executing activity "100064-BpInv1-BpSeq2.6-2" for instance "100,064", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
The reason was The execution of this instance "100064" for process "ApprovalProcess" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK" .
Consult the system administrator regarding this error.
     at com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive(TransactionUtils.java:107)
     at com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive(TransactionUtils.java:67)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.checkIfTransactionIsActive(InvokeHandler.java:1346)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1048)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:586)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:130)
     at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:74)
     at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:158)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2543)
     at com.collaxa.cube.engine.CubeEngine._handleWorkItem(CubeEngine.java:1165)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1071)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:328)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4430)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4361)
     at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:698)
     at com.collaxa.cube.engine.CubeEngineSecurityManager$2.run(CubeEngineSecurityManager.java:84)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:47)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:79)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     ... 52 more
An internal exception has not been properly handled by the server.
Set the logging level for all loggers to debug, and resubmit your request again. The server log should contain a more detailed exception report.
Exception: java.security.PrivilegedActionException: ORABPEL-02199
JTA transaction is not in active state.
The transaction became inactive when executing activity "100064-BpInv1-BpSeq2.6-2" for instance "100,064", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
The reason was The execution of this instance "100064" for process "ApprovalProcess" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK" .
Consult the system administrator regarding this error.
Handled As: com.collaxa.cube.CubeException
ORABPEL-02199
JTA transaction is not in active state.
The transaction became inactive when executing activity "100064-BpInv1-BpSeq2.6-2" for instance "100,064", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
The reason was The execution of this instance "100064" for process "ApprovalProcess" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK" .
Consult the system administrator regarding this error.
     at com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive(TransactionUtils.java:107)
     at com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive(TransactionUtils.java:67)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.checkIfTransactionIsActive(InvokeHandler.java:1346)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1048)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:586)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:130)
     at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:74)
     at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:158)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2543)
     at com.collaxa.cube.engine.CubeEngine._handleWorkItem(CubeEngine.java:1165)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1071)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:328)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4430)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4361)
     at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:698)
     at com.collaxa.cube.engine.CubeEngineSecurityManager$2.run(CubeEngineSecurityManager.java:84)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:47)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:79)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.security.Security.runAs(Security.java:61)
     at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
     at com.collaxa.cube.engine.CubeEngineSecurityManager.performActionAsSubject(CubeEngineSecurityManager.java:67)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:551)
     at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:673)
     at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:293)
     at sun.reflect.GeneratedMethodAccessor1756.invoke(Unknown Source)
     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.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:94)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:81)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:112)
     at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105)
     at sun.reflect.GeneratedMethodAccessor859.invoke(Unknown Source)
     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.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
     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.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 $Proxy309.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39)
     at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:140)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:662)
>
<Nov 11, 2011 5:36:35 AM EST> <Error> <oracle.soa.bpel.engine.dispatch> <BEA-000000> <failed to handle message
ORABPEL-02199

Could you able to resolve the issue, I have same as it is exception with my test.
Thanks in advance for the help.

Budget Approval Workflow Error: FMBCS_WF_ROLE_BUDGET parameter: FMBCS

Hi All,
I am implementing BCS Standard workflow templates WS12300025/6 on ECC 6.0. When I test the workflow, i get the following error:
"Function module call up error: FMBCS_WF_ROLE_BUDGET parameter: FMBCS"
What could be the cause of this?
Please assist.
Thank you.
Robeth

Sudhir,
I have tried simulating the rule alone but I get the error message "Test not Executed".
I must admit I am new with Objects.   Which Object ID is not properly imported? When I define binding automatically, the following workflow and rule objects are generated,
Workflow          Rule
&ACTIVITY&    &ACTIVITY&
&BUS0050&    &BUS0050&
&LEVEL&        &LEVEL&
I have also tested the workflow without the rule using Tcode SWDD directly, the task is started ok but work item in the agent's inbox has decision box showing only one alternative (Cancel and keep work item in inbox) instead of two. In addition it does not show the attached pre-posted document.
When I run Tcode FMBB directly to trigger the workflow, the workflow is not triggered even though type linkage for event PREPOSTEDDOCCREATED has been activated.
I am puzzled by this. Please give me step and step and if possible give me the objects.
Thank yuo.
Robeth

OIM11g - Approval Workflow - Requester and Approver is same

Hi All,
I have a scenario where , requests are approved by a group. ( Resource Owners group).
and if anyone needs access to this resource, the members of the group will approve the requests.
What if any member of the "Resource Owners" groups raises a request on the same object ?? OIM functionally sends it to the group for approval, and it will become a self approval and is a conflict.
How to avoid this kind of scenarios.
Regards
Vicky
Edited by: vicky on Dec 7, 2011 5:18 AM

AFAIK I haven't seen any system property to stop this. SOA does not care about who the requester is and who are the approvers. The way Oracle has impletmented the identity service for OIM in SOA does not handle this. Seems there is no SOD checks. Open a SR which I believe should be taken as a ER.
Thus the workaround would be to get all the members of the approver group less the requester and assign to all the members. The member list should be comma seperated user ids.
HTH,
BB

PO awaiting approval - even if it is approved

the PO was still in awaiting approval but it is already approved. I ran the PO at SE37 BBP_PD_PO_TRANSFER_EXEC & BBP_PD_PO_TRANSFER_EXEC_V2 but it is still on awaitng approval status. There's no error appearing at the application monitor.

Hi,
Pleaes check once again if the PO is approved, check in inbox of the approver.
if it is already approved and still awaiting approval.
manually we can set the workflow status complete using the funcaiton module
SE37--> execute the FM BBP_PD_PO_STATUS_CHANGE_WF
IV_GUID -- enter the GUID of the PO
IV_STATUS -- 1
Execute .. Hope your problem will solve
Thanks
prasad s

1-step SC approval workflow - error awaiting approval

Similar Messages

Maybe you are looking for