Error handling on PO workflow

I have a custom Workflow for PO Release. i am using BAPI's to Release the PO from one level to other level.
when some one is opened the PO in ME22N, BAPI giving error and going for next level. How to handle this error.
I can send error message to user a mail and i can complete the workflow in case of error. But workflow will STOP abruptly in this case.
Is there any other solution.
Regards, Sri harsha

HI Rick,
Thanks for your Inputs.
Still i am in Confusing with word " Temporary" . I have Defined Exception for my method as you suggested. But i have not found any check box or option in method to choose for temp. Please tell me where i have to choose it as Temporary.
Or else If write just "exit_return 9006", will it consider as Temporary error.
Waiting for your inputs.
Regards, Sri harsha.

Similar Messages

Error Handling on OM Workflow.

Hi Guys, I have a question.
I have a requirement on OM sales order form, suppose an workflow errors out because of some missing data. If the users enters or corrects the data, Now he want the workflow to start by some action on form instead of waiting for sysadmin to do retry. he is asking because there might be a chance of delay by sysadmin in doing retry. I am wondering whether this is possible on the form. If possible, can someone suggest me a way to do that.
Thanks in advance.

HI Rick,
Thanks for your Inputs.
Still i am in Confusing with word " Temporary" . I have Defined Exception for my method as you suggested. But i have not found any check box or option in method to choose for temp. Please tell me where i have to choose it as Temporary.
Or else If write just "exit_return 9006", will it consider as Temporary error.
Waiting for your inputs.
Regards, Sri harsha.

Error handling of Assignments in Workflow...

Hi All,
How we do we automate assignment's error handling in Workflow.
For example: I have an assignment and that is part of my workflow.
If the assignment fails the workflow job status gets "Error" status --> How do we handle this by sending some notification or branch into success or failure?
Please feel free to revert to me.
thanks
Alexander.

Hi Alexander,
MDM Assignment is not like Validation based on which you can branch out your process based on the validation result.
Assignment will assign a value to the desired field based on the expression you write.
So you need to take care that your expression handles all the incoming records fully and does not fail.
Hope It Helped
Thanks & Regards
Simona Pinto

Error handling workflow not getting triggered

Hi all,
I'm creating a outbound IDoc. And for error handling workflow.. I created a organization structure in PPOME and assigned users. I gave this position number thus created in the partner profile in post processing permitted agent tab.
But when the Idoc is in error, this is not coming to my inbox.
Can someone please help me with this.. and let me know what went wrong.
Thanks in advance.

Here you need to be careful,
if the agent assignment is not maintained properly, there may be a chance everyone in the organization will get the item.
I hope you have created a single workitem for error handling. goto additional data-> agent assignment-> maintain. make sure the attribute is defined as general forwarding allowed. or you maintain the role/position/user/whatever.as the possible agents. still you dont get the result, debugging the default rule in the task ->default rule -> agent.
hope this helps.
with regards,
Sudhahar R

About ale error handling in workflow?

Hi,
can any one explian in detail ale error handling through workflow,its urgent for me.
Regards,
phani

Hi Srikanth,
follw the steps it will helpful u,
Pre-requisites.
It is assumed that the reader of this article has some knowledge in SAP workflow BOR objects and ALE Idoc process like process code, Partner Profile etc.
Description
Here, we will be discussing in details the Error handling of an Inbound Idoc through triggering an event, which in turn will be triggering a workflow attached to the workflow.
Steps:-
1.     Create custom BOR object with the events, Start and Stop event
2.     Create a workflow for the error handling, like generating a notification whenever an error occurred in the Inbound Idoc.
3.     Creation of Function Module and attachment with the Process Code
4.     Create the settings for the Inbound Process of the Idoc through the Process Code.
Creation of BOR objects. Go to the[http://www.****************/Tutorials/ALE/ErrorHandling/page3.htm] transaction SWO1.
Enter a name for the Object type and click CREATE button for creating the custom BOR object.
Enter the details required for creating the BOR objects...
Create the Key fields and events of the BOR object.
For creating the Key fields place the cursor on the Key fields and Click on the Create Button
Create events for triggering the workflow and stopping the workflow.
For creating the event place the cursor on the EVENTS and Click the create button like Key fields.
Create two events.
Enter the event name description etc and proceed further to create it.
Similarly create another event for ending the Workflow in the similar manner like that created earlier.
Now, Generate the BOR object through the generate button
Release the EVENTS and subsequently release the BOR object.
After the creation of BOR object
Create a workflow for the generation of notification whenever an error is reached in the Inbound Idoc.
Execute the transaction SWDD.
Click on the CREATE button for creating the workflow for error handling.
Choose the Step type to be inserted for the notification like here we are using Send Mail option for sending a mail to the user whenever any error occurred.
Activate the Workflow and test it whether it is working as per the requirement.
After the successful completion it is required to attach the workflow with the event.
Go to the Header section (Denoted by CAP).
Go to the Start Events TAB.
Enter the details of the event with which the workflow should be linked like the category, BOR object type and the event with which that should be linked.
Enter here the BOR object that has been created and give the name of event created for starting the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Generate the binding and click OK button to save the binding.
Click on Activate / deactivate button for activating the linkage.
After the successful linkage the following sign will appear on the workflow.....
This shows that the workflow has been linked to the event and it will be triggered whenever that particular event will be triggered.
After the creation and successful linkage of workflow with the event it is required it is required to generate a function module and attached it to the process code.
Go to SE37 transaction and copy a standard process code function module to a custom one. Do no delete any parameters from the function module as the SAP standard program itself is calling this.
In that function module do the required validation and whenever the validation fails set a standard parameter WORKFLOW_RESULT to 9999 from within the function module, otherwise normally proceed to set the status to 53.
After the creation of function module it is required to attach it to the process code and corresponding attached to the message type at the Partner Profile stage.
The process code is being created through the transaction WE42
Go to the change mode and click the New Entries button for creating new process code.
Enter the Process Code Name, description and choose the processing type as Processing by function module. Click on the extension button of Identification.
The details for the of the Process Code after clicking the identification button will be
Whenever idoc arrives into the Destination system then the standard SAP triggers the Process code attached to the Message type in the partner profile. The partner profile is being maintained in the transaction WE20.
Since, it is and inbound scenario so the message type and the corresponding process code will be maintained for the Inbound Parameters.
Click on Create Inbound Parameters button for creating new Inbound Message type and the corresponding message type.
Enter the process code for the corresponding message type.
Click SAVE button for saving the changes.
Whenever the IDOC arrives into the target system, it checks the partner profile and finds the corresponding process code. The process code is being linked with the function module through which the IDOC is required to be processed.
Regards,
Phani.

Outbound Idoc error handling through workflow

Hi,
I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
How this task can be triggered when outbound idoc error occurs in the system?
Kr,
Vithalprasad
Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

Hi,
Have a look
Outbound IDoc Error Handling via Workflow
Outbound idoc error handling through workflow

OUTBOUND- ERROR HANDLING USING WORKFLOW

Hi Gurus,
Can any one tell me about workflow & how to do error handling using WORKFLOW in OUTBOUND IDOC.Below are the points , Please check it & send me reply.
1.Value not found for Custom IDoc fields.
2. Partner Profile not maintained correctly.
3. Syntax error in IDoc.
4. IDoc ready for dispatch (ALE Service).
Regards,
Chiranjeevi.

Hi,
FOr most of your requirements, there is already std. SAP IDOC error Single-step tasks.
Have a look at WE46 transaction.
Also, if you go to SWO1 and search with "IDOC*", you will get all the BO's even.
It's pretty straightfwd. Also, in Partner Profiles, WE20, for each of the IDOC type, there is one "Post.Processing AGent", whom if you set up correctly, will be the person receiving this Errored IDOC mails.
Hope this helps
venu

ALE Error Handling with Workflow

Hi All,
I have some issues with using workflows with idocs:
In our process codes , the business object , start event for error handling and success event has been configured.
Now if the workflow_result is 0 then success event is triggered and if workflow_result = 99999 then start event is triggered.
I have two qquestons:
1. How are these events triggered as I did not find any code in the F.M> to triggerethem.
2. What is the purpose of End event.
Apart from this , is there any area where workflows can be used with IDOCS.
Thanks and Regards
Aman

Hi,
In case I am creating a custom F.M. to process idoc data then I can use the F>M> to create the event.
However In case the standard F.M. is being used and workflow_result is set to 9999 in it and I have consigured the start event to it,in that case I will not be able to use thie F.M> to trigger the workflow.
Thanks and Regards
Aman

IDoc error handling using workflows

Hi,
I have a requirement to generate IDocs in the Source system and process them in the target system. The IDoc message type is HRMD_ABA. And I am using standard processes to generate them and post them using PFAL and RBDAPP01 program respectively.
All this is working fine. But now I need to include error handling in the source and the target systems which would send mails to a User's Outlook mailbox whenever there is an error. I mean to say, we need more functionality than just monitor them through WE05 transaction.
Can any one tell me how this can be achieved. I have been looking into the program RSEIDOCA which would send workflows to SAP Inbox, but I need to send it to Outlook Inbox.
And I have heard that there is a workflow process which would help me to do this.
All your answers would be highly appreciated.
Thank you in advance,
Sid.

Hi,
First Step:
You have to maintain the e-mail-address in SU01 for required users.
Second Step:
SCOT Configuration
Third Step:
Depends on your SAP Version do configuration SWNADMIN
Or excuting the report RSWUWFML2 as the background job.
Thanks and Regards,
Prabhakar Dharmala

Error handling in Abap Class for SAP Workflow

Hi Experts,
I would like to know if we have an option in abap classes used in workflows to send errors to the workflow log. We can achieve this in BOR Object methods by using the EXIT_RETURN <CODE> var 1 var 2 to send the errors back to the workflow, but how is this achieved through methods from classes used in workflows.
Appreciate your quick responses,
Chaitanya

Just raise exceptions in the normal OO way. Any exception that is a subclass of CX_BO_ERROR should be automatically available in workflow. Use subclasses of CX_BO_TEMPORARY for temporary errors.

Error in transporting WF workflow task

Hello,
I face an error when moving WF workflow task from Dev to QA.
System is 4.0B.
The QA transport log shows (errors in bold):
Subsequent processing RH_ACTIVATE_PDOBJECT_AFTER_IMP for PDWS T started at 20:23:01
Time... 20:23:02 Run time... 00:00:01
Start activation of object WF 91000095 (client: 100) 202302
Error while activating
Time... 20:24:00 Run time... 00:00:58
Errors occurred during post-handling RH_ACTIVATE_PDOBJECT_AFTER_IMP for PDWS T
Post-handling RH_ACTIVATE_PDOBJECT_AFTER_IMP belongs to development class SP00
The errors affect the following R/3 components:
 BC-BMT-OM (Organizational Management)
In QA, the new version of the WF - created and activated in Dev - does not appear at all. I checked OSS Note 138411 - Collective note: PD Transports and OSS Note 88180 - Error during import postprocessing (Org.unit) but they didn`t help.
In Dev, the new version of the WF was saved and activated and manually inserted in a customizing request from tr. PFTC. The transport included object R3TR TDAT PDWS with entries for HRP, HRT and SWD_* tables, with records for the WF task.
Any help would be appreciated.
Thanks and regards,
Krisztian

Hi Ravi,
WS and TS tasks are recorded in changes, only the WFs and Ts are not. This is because some Personal Development objects are not to be transported, hence automatic transport connection for these is deactivated in IMG. Since WFs and Ts are considered as PD objects, the automatic transport is deactivated for them as well. For WFs and Ts manual transport is available in PFTC.
This is unfortunate but this is how it`s set.
On the other hand, version management is not something that works too well for workflows anyway (at least in 4.0B). You can`t see the differences in two separate versions like you would in a program. And in WFs and Ts you are able to generate versions just like for WSs and TSs for version management. So from my point of view manually transporting WFs and Ts are not the issue. But I may be wrong...
Nevertheless I activated automatic transport connection and did a change in Dev like that. The transport created was moved to Acc, but still same problem...
So I`m running out of clues.. maybe I just overlooked something...
Thanks
Krisz

Error handling while invoking TaskService

Hi All,
we are using SOA Suite 10.1.3.5
In one of the BPEL processes we are invoking TaskService. This invoke is the one that gets generated by default when a human task is used.
We are using Single Approver Participant type and the users of it are derived from Active Directory.To access Active directory we are using a username and password.The password got expired and so the bpel instance containing the human task got stuck at invoke Task Service. There was no exception thrown in the process instance.Now we are asked to implement a Retry logic whenever such a thing happens. But unable to proceed as there is no exception thrown in the console to catch it. Can you please tell me how to implement retry in this scenario? However the error is captured in opmn logs as follows:
ORABPEL-10509
User is not found.
User "L-DCNM-S-M91BXK9=" is not found in realm "AD".
Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
 at oracle.tip.pc.services.identity.ldap.LDAPProvider.lookupUser(LDAPProvider.java:648)
 at oracle.tip.pc.services.identity.ldap.LDAPAuthorizationService.lookupUser(LDAPAuthorizationService.java:127)
 at oracle.tip.pc.services.identity.ldap.LDAPIdentityService.lookupUser(LDAPIdentityService.java:110)
 at oracle.bpel.services.workflow.verification.impl.VerificationService.lookupUser(VerificationService.java:3014)
 at oracle.bpel.services.workflow.verification.impl.VerificationService.authenticateUser(VerificationService.java:365)
 at oracle.bpel.services.workflow.query.impl.TaskQueryService.authenticate(TaskQueryService.java:162)
 at oracle.bpel.services.workflow.query.ejb.TaskQueryServiceBean.authenticate(TaskQueryServiceBean.java:40)
 at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAs(Subject.java:396)
 at com.evermind.server.ThreadState.runAs(ThreadState.java:707)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:53)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
 at TaskQueryService_RemoteProxy_18b3fg8.authenticate(Unknown Source)
 at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:67)
 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
 at java.lang.Thread.run(Thread.java:595)
<2011-07-08 13:24:39,957> <ERROR> <eif_domain.collaxa.cube.services> <*::*> WorkflowService:: VerificationService.authenticateUser: error: Internal Error in Verification Service.
<2011-07-08 13:24:39,957> <ERROR> <eif_domain.collaxa.cube.services> <*::*> Internal Error in Verification Service for user L-DCNM-S-M91BXK9=. lookupUser
<2011-07-08 13:24:39,957> <ERROR> <eif_domain.collaxa.cube.services> <*::*> Check the underlying exception and correct the error. Contact oracle support if error is not fixable.
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> ORABPEL-30501
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*>
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> Error in authenticating user.
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> Error in authenticating and creating a workflow context for user AD/bpmadmin.
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> Check the underlying exception and correct the error. Contact oracle support if error is not fixable.
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*>
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.verification.impl.VerificationService.authenticateUser(VerificationService.java:387)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.query.impl.TaskQueryService.authenticate(TaskQueryService.java:162)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.query.ejb.TaskQueryServiceBean.authenticate(TaskQueryServiceBean.java:40)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at java.lang.reflect.Method.invoke(Method.java:585)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at java.security.AccessController.doPrivileged(Native Method)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at javax.security.auth.Subject.doAs(Subject.java:396)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ThreadState.runAs(ThreadState.java:707)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:53)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
<2011-07-08 13:24:39,958> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at TaskQueryService_RemoteProxy_18b3fg8.authenticate(Unknown Source)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at java.lang.reflect.Method.invoke(Method.java:585)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:67)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at java.lang.Thread.run(Thread.java:595)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> Caused by: ORABPEL-30504
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*>
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> Internal Error in Verification Service.
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> Internal Error in Verification Service for user L-DCNM-S-M91BXK9=. lookupUser
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> Check the underlying exception and correct the error. Contact oracle support if error is not fixable.
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*>
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.verification.impl.VerificationService.lookupUser(VerificationService.java:3018)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.verification.impl.VerificationService.authenticateUser(VerificationService.java:365)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> ... 28 more
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> Caused by: ORABPEL-10509
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*>
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> User is not found.
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> User "L-DCNM-S-M91BXK9=" is not found in realm "AD".
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*>
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at oracle.tip.pc.services.identity.ldap.LDAPProvider.lookupUser(LDAPProvider.java:648)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at oracle.tip.pc.services.identity.ldap.LDAPAuthorizationService.lookupUser(LDAPAuthorizationService.java:127)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at oracle.tip.pc.services.identity.ldap.LDAPIdentityService.lookupUser(LDAPIdentityService.java:110)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.verification.impl.VerificationService.lookupUser(VerificationService.java:3014)
<2011-07-08 13:24:39,959> <ERROR> <eif_domain.collaxa.cube.services> <*::*> ... 29 more
<2011-07-08 13:24:39,959> <ERROR> <oracle.bpel.services.workflow> <::> Internal Error in Verification Service.
Internal Error in Verification Service for user L-DCNM-S-M91BXK9=. lookupUser
Check the underlying exception and correct the error. Contact oracle support if error is not fixable.
ORABPEL-30504
Internal Error in Verification Service.
Internal Error in Verification Service for user L-DCNM-S-M91BXK9=. lookupUser
Check the underlying exception and correct the error. Contact oracle support if error is not fixable.
 at oracle.bpel.services.workflow.verification.impl.VerificationService.lookupUser(VerificationService.java:3018)
 at oracle.bpel.services.workflow.verification.impl.VerificationService.authenticateUser(VerificationService.java:365)
 at oracle.bpel.services.workflow.query.impl.TaskQueryService.authenticate(TaskQueryService.java:162)
 at oracle.bpel.services.workflow.query.ejb.TaskQueryServiceBean.authenticate(TaskQueryServiceBean.java:40)
 at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAs(Subject.java:396)
 at com.evermind.server.ThreadState.runAs(ThreadState.java:707)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:53)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
 at TaskQueryService_RemoteProxy_18b3fg8.authenticate(Unknown Source)
 at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:67)
 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
 at java.lang.Thread.run(Thread.java:595)
Caused by: ORABPEL-10509
User is not found.
User "L-DCNM-S-M91BXK9=" is not found in realm "AD".
Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
 at oracle.tip.pc.services.identity.ldap.LDAPProvider.lookupUser(LDAPProvider.java:648)
 at oracle.tip.pc.services.identity.ldap.LDAPAuthorizationService.lookupUser(LDAPAuthorizationService.java:127)
 at oracle.tip.pc.services.identity.ldap.LDAPIdentityService.lookupUser(LDAPIdentityService.java:110)
 at oracle.bpel.services.workflow.verification.impl.VerificationService.lookupUser(VerificationService.java:3014)
 ... 29 more
<2011-07-08 13:32:36,768> <INFO> <eif_domain.collaxa.cube.engine.dispatch> <CallbackInvokerMessageHandler::handle> Wait for 2 seconds before retrying callback for 992573-BpInv0-BpSeq3.286-6
<2011-07-08 13:49:02,501> <INFO> <eif_domain.collaxa.cube.engine.dispatch> <CallbackInvokerMessageHandler::handle> Wait for 2 seconds before retrying callback for 992588-BpInv0-BpSeq3.28-6
<2011-07-08 14:11:34,778> <INFO> <eif_domain.collaxa.cube.engine.dispatch> <CallbackInvokerMessageHandler::handle> Wait for 2 seconds before retrying callback for 992606-BpInv0-BpSeq3.288-6
<2011-07-08 14:43:16,839> <INFO> <eif_domain.collaxa.cube.engine.dispatch> <CallbackInvokerMessageHandler::handle> Wait for 2 seconds before retrying callback for 992650-BpInv0-BpSeq3.291-6
11/07/08 14:56:54 [MYDEBUG] admin user = null
<2011-07-08 15:06:49,877> <WARN> <eif_domain.collaxa.cube.ws> <WSInvocationManager::Failed to get callback ServiceName in wsdl> Failed get wsdl service definition.
Failed to get a WSDL service that support the portType "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskServiceCallback" in WSDL definition "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskService".
Please verify that WSDL portType "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskServiceCallback" is supported by a service in WSDL file.
<2011-07-08 15:06:51,574> <WARN> <eif_domain.collaxa.cube.ws> <WSInvocationManager::Failed to get callback ServiceName in wsdl> Failed get wsdl service definition.
Failed to get a WSDL service that support the portType "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskServiceCallback" in WSDL definition "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskService".
Please verify that WSDL portType "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskServiceCallback" is supported by a service in WSDL file.
<2011-07-08 15:06:52,427> <WARN> <eif_domain.collaxa.cube.ws> <WSInvocationManager::Failed to get callback ServiceName in wsdl> Failed get wsdl service definition.
Failed to get a WSDL service that support the portType "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskServiceCallback" in WSDL definition "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskService".
Please verify that WSDL portType "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskServiceCallback" is supported by a service in WSDL file.
<2011-07-08 15:06:53,154> <WARN> <eif_domain.collaxa.cube.ws> <WSInvocationManager::Failed to get callback ServiceName in wsdl> Failed get wsdl service definition.
Failed to get a WSDL service that support the portType "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskServiceCallback" in WSDL definition "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskService".
Please verify that WSDL portType "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskServiceCallback" is supported by a service in WSDL file.
<2011-07-08 15:06:53,872> <WARN> <eif_domain.collaxa.cube.ws> <WSInvocationManager::Failed to get callback ServiceName in wsdl> Failed get wsdl service definition.
Failed to get a WSDL service that support the portType "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskServiceCallback" in WSDL definition "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskService".
Please verify that WSDL portType "{http://xmlns.oracle.com/bpel/workflow/taskService}TaskServiceCallback" is supported by a service in WSDL file.

Hi Stèphane,
You can use a Start Routine in Transfer or Update Rules that read the /BI0/Pxxxxx or /BIC/Pxxxxx Master Data table and delete all records where there is no corresponding value already stored.
You can also use /BI0/Sxxxxx or /BIC/Sxxxxx.
Ciao.
Riccardo.

Error handling for work item

Dear All,
     When I trigger my workflow from SWUE,the workflow containers must be populated with agent name.But it is populated only with 'US'.Please suggest.
     On the other hand, when I trigger my workflow from ME21N,the workflow goes into error.The error statement is "Exception occurred - Error handling for work item 000000954797".What is the problem?
    Please suggest the solution for which I will be grateful.
Thanks and regards,
S.Suresh

Dear ,
I use bus2012 as BOR and event as created.
When I create purchase order from ME21N,bus2012 is not triggering.Instead FREBUS2012 gets triggered which is a subtype of bus2012.
At SWETYPV,event linkage is activated only for BUS2012 and there is no entry at SWETYPV for FREBUS2012.
Though I configured the workflow with start events:BUS2012->created,why FREBUS2012 should trigger my workflow which is not seen in SWETYPV?How to override it?Please suggest.
There is no start conditions for my workflow.Whenever purchase order is created,this workflow should trigger.
So,the parameters passed between even to workflow are
&_EVT_OBJECT&    ->        &BUS2012&
&_EVT_CREATOR&   ->     & WFINITIATOR&
Thanks and regards,
S.Suresh

Alerts and Error handling in BPM Async/Sync Bridge

Hello All,
I am developing an Async/Sync Bridge in BPM for sending a request from ECC webservice asychronously to a front end application synchronously using BPM Async/Sync Bridge. I get a response from the front end to PI and stays there.
It wont be send back to ECC. What are the possibilities of error handling required in this type of scenario.
Thanks
Deno

. I get a response from the front end to PI and stays there.
Then it should mean that the BPM design is faulty...did you have a send step at the end which closes the Async-Sync Bridge by sending the message to original sender?
In SXMB_MONI --> For BPM message processing there will be a link called PE...click it...check the graphic workflow...see till where the message has processed.
error handling
include your Sync send step whithin a Block....this block will have an Exception Branch....in this exception branch you can have your Exception handling logic...like raise alert, cancel process etc.
Regards,
Abhishek.

Receiver Feedback with no Error Handling (Input Design Requested)

Hi Community,
Today we have a pretty standard integration scenario that takes in flat files and converts them to Idocs for target SAP systems. We are looking to redesign the current IDoc interface (posts a customized FIDCC1) under the principle that IDocs in errors on target are always corrected by a change in the source, so essentially we want to report errors back to the source and completely delete the IDoc. I guess this looks like a synchronous call?, but I want to remain as loosely coupled for this. Since we also process these files in batches (i.e. each file contains 1 to many invoices), we would like to return the results back to the source based on each file. For example, the message back to the source (in email so a user can act on it, not a system) could be:
a) file failed because structure is incorrect (like an XSD type check).
or of the file makes it through XI,
b) list of invoices failed because xxx is incorrect and list of invoices that processed.
We are open to using proxies, any kind of IDoc error handling that could do this, workflows, status idocs, etc. Every option is on the table.
Thanks!
Peter

peter
if u are open to proxes then u might haveone interface that will send the data to proxy and thru proxy u update the idoc....if idoc goes fpor an error u can have another interface triggered that will update/delete the soruce data...for this u might need to pass the soruce files details to proxy and back

Error handling on PO workflow

Similar Messages

Maybe you are looking for