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

Similar Messages

Order blocked by user / Workflow error handling

Hi Folks,
I am getting this requirement quite often. Time to address it in a more efficient way than that I know.
The following is the requirement:
Workitem goes to approver. If the approver approves/rejects the workitem, there is a subsequent change in the sales order which is handled by BAPI in the next step. If the sales order is locked by some user, BAPI does not make change and throws an error.
Solution that I can think of:
The way it is handled right now is - if there is an error message from BAPI - the workflow is routed to a power user or an email message is sent to admin asking him to inform the right user.
This approach of mine does not sound correct. Can we actually throw error at the time when the approver tries to open the workitem itself (i.e. see if the transaction is being locked and if it is locked - throw an error and do not allow the approver to take action ).
Thanks,
aby.

Hi Folks,
I am getting this requirement quite often. Time to address it in a more efficient way than that I know.
The following is the requirement:
Workitem goes to approver. If the approver approves/rejects the workitem, there is a subsequent change in the sales order which is handled by BAPI in the next step. If the sales order is locked by some user, BAPI does not make change and throws an error.
Solution that I can think of:
The way it is handled right now is - if there is an error message from BAPI - the workflow is routed to a power user or an email message is sent to admin asking him to inform the right user.
This approach of mine does not sound correct. Can we actually throw error at the time when the approver tries to open the workitem itself (i.e. see if the transaction is being locked and if it is locked - throw an error and do not allow the approver to take action ).
Thanks,
aby.
Hi Aby,
If I understand this correctly, the sales order can be blocked by some other application during the approver's task?
Is the approval task a decision task, or a custom task? If custom, perhaps you could include some locking/unlocking code?
I suppose you could implement a before-method to check for a lock - but you aren't able to pass data back to the approval task from a before method. You could check for a lock in a separate task prior to the approval task, but there is no guarantee that the user would complete the task before someone else locks the object up again.
Another approach might be to check the results of the BAPI, and if it's throwing an 'Object locked' type of error, call it again. Of course, you would need to put some wait time in the BAPI, and also, you would need to ensure it does not go on waiting and trying forever. But nobody likes to admit they put wait steps into anything.
Just a few ideas to consider. I wonder if this problem is that persistent?
Sue

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 Handler Settings

Can anybody give me more insights about Error Handler Settings in CRM Middleware. Transaction SMW00.
I need to execute a custom function module, if the BDOC errors out. Also need to send an email message with details.
Any help would be appreciated.
Thanks!

HI
Error Handling Configuration SMW00
Different assignments of error actions are possible:
> Standard Error Action (valid for all messages)
> Error Action for a Specific BDoc Type
> Error Action for a Specific Site Type
> Error Action for Aborted Messages
> These four logical levels are used in reverse order to determine the error actions to be carried out. If no
specific error action has been assigned to a message, the least specific action (this means the default
action) starts.
> You can choose the following actions for a message:
> Workflow event: the start event SERVICEERROROCCURRED of object type MIDMESSAGE has
been prepared (the end event is SERVICEERRORFINISHED). This event triggers a work item of
standard task TS75110000 (MIDMESSAGE.ShowMessage).
As the event is executed, you can view the message and decide on what to do with it (Deletion,
Resubmission, Resume Processing with the next service).
> E-mail function:
> Customer function: Calls a customer function module.
Hope it helps

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

Idoc/ALE error handling, send to external email

Hi all,
I'm developing an IDoc inbound interface for purchase order create using PORDCR1. For the error handling functionality, I need to send an external email describing all of the validation error happened in user-exit EXIT_SAPFKCIM_002. Please kindly tell me how to cater the functionality. I won't use workflow because the error handling can't describe all the error, it just displaying the first error encountered. I also don't want to create any custom object since message type PORDCR1 is available. I think creating a custom FM is a possible way, but if there is another way, please tell me how.
Thanks,
Teddy

Hi Teddy,
A custom FM is the easiest and simple way.There may be other ways.
Regards,
Atish

Error Handling in IDoc

Hi Friends,
Can anybodytell me any procedure for Idoc error Handling (Restart and Recovery) of IDocs that occured in error status. What could be be the possible ways apart from BD87.Thanks in advance for ur gr8 help!!!

It really depends on they type of error.
For transactions that need data remediation, the preferred method of posting is via SAP Workflow (xaction So01 for the inbox).
For things that did not post due to missing config, etc. use BD87 (assuming the config now exists).
If you have specific questions post them and I will try to help.

ALE Inbound Error Handling

Hi
Here I have problem in setting up Error handling in outbound/inbound processing of Idocs in ALE....
Can any one please explain how to do it....
My requirement is, if ever idoc goes in to error then the user has to be intimated by mail in SAP Inbox.As per my knowledge it can be done through partner profile...if specify user name in partner profiles/post processing agent place.
My doubt is will it be same in outbound/Inbound?
Do i need to do anything other than specifying usernames in partner profiles?
What is the use of Idoc Administrator?
Please explain how to do that....
Awaiting your valuable answers...
Thanks
Suresh
Message was edited by: Suresh Babu Mannem

I think you also need to specify the "post processing agent" in your Partner profile - Message Type.
Check WE20.
In case you don't want to use organizational assignment then leave the task as it is as general task.
So only the user specified in "post processing agent" will be taken into consideration.
Here are the steps that you need to do for a complete error handling procedure ( but you can avoid organizational assignment if you just need to use User Name as receipient ):
I've taken it from F1 help on error handling:
Error Handling
In this section, you can make the settings for error handling:
Create organizational units and assign standard tasks
Maintain EDI administration ( Idoc administrator section on Xn OYEA or We40 )
Maintain error process code ( Xn OYEA or We40 )
Further you can check it using Verification Processing on OYEA / WE40 .
Errors are processed in the system in which the error occurred.
You can repost IDocs that were not posted (with status 51) using program RBDMANIN.
Requirements
ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
Workflow functions as follows:
A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
If an error occurs, the system determines:
1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
Activities
Create organizational units and assign standard tasks
Maintain EDI administration
Maintain error process code
If you used EDI communication in an earlier version, you can check the assignment of error process codes to the standard tasks.
Check names of the employees responsible in the partner profiles.

Error handling of Assignments in Workflow...

Similar Messages

Maybe you are looking for