Exception handling in IDOC using workflows

exeception handling in idoc using workflows
i. what will be the trigerring event in case of idoc ?
ii.will it be BOR -- IDOC<message_type >?
thanks in advance
naval bhatt

Hi Naval Bhatt,
it depends on what you would like to do, but there is an object IDOCAPPL, more information you find Objekttyp IDOC<MSGTYP>:
http://help.sap.com/saphelp_47x200/helpdata/en/04/92725546f311d189470000e829fbbd/frameset.htm
General how it works:
Objects, Events and Tasks to be Created
http://help.sap.com/saphelp_47x200/helpdata/en/78/2176d251ce11d189570000e829fbbd/frameset.htm
This is an example how the application should implement the exception handling in IDOC by using workflows.
Events for example:
- inputErrorOccurred
- inputFinished
Regards
Tibor

Similar Messages

How to implement Exception Handling error in IDoc to File and RFC to File

Hi,
We are implementing the two below scenarios :
1. IDOC to File
2. RFC to File
We have to implement the Exception Handling for the above two cases. Kindly could you provide the inputs to implement the Exception Handling for the above two cases.
Please provide the precious inputs to implement this.
Thanks,
Ramesh

Hi Ramesh,
The exception handling for idocs
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm
Exception handling in File to IDoc Scenario
For RFCs
Re: Passing SAP Exceptions to a sync SOAP Call
Error Handling when using RFC
Exception Handling while Calling RFC - BPM
handle exceptions in remote function modules
Regards,
Prateek

Re : How to Error Handling In Idoc /ALE.

Hi This is Arief ,
I tranfer the Data Through ALE from One Client To Other Client some of Data not Posted ......how check other client wither Data Posted or not ....
How to error Handling In IDocs.....pls Help me.......
Kind Regards
Arief .S

Hi
The exception handling for idocs
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm
Exception handling in File to IDoc Scenario
For RFCs
Re: Passing SAP Exceptions to a sync SOAP Call
Error Handling when using RFC
Exception Handling while Calling RFC - BPM
handle exceptions in remote function modules

Exception Handling Confusion!

I require the following very basic functionality from a function.
Create or Replace function fnc_get_col3 (a in number, b in number)
return number
as
begin
return select col3 from TAB1 where col1 = a and col2 = b;
end fnc_get_util;
My question is that can I use the regular exception handling (like 'No data found' and 'Too many rows') in above function when i am using the return and select statement in same line
OR do i have to recreate this function as
Create or Replace function fnc_get_col3 (a in number, b in number)
return number
as
abc number(5);
begin
select col3 into abc from TAB1 where col1 = a and col2 = b;
return abc;
exception
when no data found then
dbms_ouput.put_line 'No data found'
end fnc_get_util;
Thanks in Advance

Why do you believe it is syntactically valid to return a value this way? The first function does not compile and cannot compile so there is no exception handling to discuss
SQL> create or replace function f1
2 return number
3 is
4 begin
5 return select count(*) from emp;
6 end;
7 /
Warning: Function created with compilation errors.
SQL> sho err
Errors for FUNCTION F1:
LINE/COL ERROR
5/10 PLS-00103: Encountered the symbol "SELECT" when expecting one of
 the following:
 ( - + ; case mod new not null <an identifier>
 <a double-quoted delimited-identifier> <a bind variable>
 continue avg count current exists max min prior sql stddev
 sum variance execute forall merge time timestamp interval
 date <a string literal with character set specification>
 <a number> <a single-quoted SQL string> pipe
 <an alternatively-quoted string literal with character set
 specification>
 <an alternYou would need your SELECT statement to select data into a local variable and to return that local variable as you are doing in your second implementation. It would not make sense, however, to have an exception handler that simply uses DBMS_OUTPUT to display a message-- you should only catch an exception if you can do something meaningful with it.
Justin

Exception handling in workflow

I've read few forums on exception handling in workflow, and tried working accordingly. Created a block and on normal branch, ive added "user decision" step, mail step...
On the other (exception) branch, ive sent a mail to HR informin tht workflow went in error.
My question is: Do i have to put "condition" step to check if email ID exists or not...or if agent is found or not, before i raise the exception? Is there no way the workflow detects any exception n incase its caught, it should raise it ?

Try some thing like this
1. Declare execption in the BOR method by using the button EXCEPTIONs on the application tool bar and raise it by using the Macro EXIT_RETRUN inside the method., By doing like this whe you attach this BOR method to the Activity step a separate outcome is created , and add what ever steps you wanna do in this step.

Steps for ALE/EDI error handling using workflow

Hi
I need to handle errors in outbound IDoc generation using workflow. Can you please let me know the steps to be used for this. Step-by-step answer would be appreciated.
Thanks

Seetha,
I have this already..
IDOCPACKET
Object type                         IDPKWMMBXY
End event                           MASSINPUTFINISHED
IDOC
Object type                         IDOCWMMBXY
Start event                         INPUTERROROCCURRED
End event                           INPUTFINISHED
Application object
Object type                         BUS2017
Start event

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

Handling outbound IDOC errors through workflow TS00007989

Hi,
I want to sent an notification e-mail to external mail box when an outbound idoc has an error status. This needs to be achieved through a workflow template.
I noted that there is a standard task TS00007989 in WE40 which is used for handling outbound idoc errors.
Moreover i couldnt find any trigerring events for the above task.
Can any one help me with a step by step guide for achieving this.
Regards,
Krishnakumar

Hi,
the single step task TS00007989 that you see is NOT TRIGGERED thru' any BO's event. It is created by the std. pgm RSEWFERR. If you go to the wflow log of the witem generated by it, you will see the Creator.
And you can control the activation / deactivation of these single step tasks for various inbound and outbound Error IDOC's thru' Transaction WE46.
If you want, create a single step task of your own and maintain that task here. But, you will ahve to know the exact BO like IDOCORDERS or IDOCEMBMAS etc. or look for events triggered by General IDOC objects like IDOCAPPL.
Hope this helps.
venu

Exception Handling In BPEL By using Catch Blocks or Fault Policies Or Both

I have a confusion regarding
Exception handling :
When Should i go for 1)Catch Block (Remote , or binding ) in bpel for exception handling .
2)Fault Policy , Fault binding.xml
Currently iam using catch blocks , but even fault policy is good , but can i use both...
Currently in My bpel ,when any error occurs i have to send a error notification by Email .
Currently i have exposed the email service which shuts emails and write a file with errored Message.
Hence if any error i will catch i in a parent BPEL, i will just invoke the above email, service .
So anybody can help me by giving the suggestion how to go for the best approach
Edited by: anantwag on Mar 23, 2011 6:31 AM

Currently in My bpel ,when any error occurs i have to send a error notification by Email .
Currently i have exposed the email service which shuts emails and write a file with errored Message.Seeing your use case I will suggest you to use fault handling framework (fault policy). Fault handling framework should be used where you need generic error handling framework which handles all the faults occured in any composite component. Generally BPEL catch block should be used to propagate error info/fault back to the client/to fault handling framework or to consume an error
Regards,
Anuj

Exception Handling (in Mapping) with out using BPM

Hello All,
We are on SP17. I have a simple flow involving XI
JMS -> XI (Message Mapping -> XSL Mapping) -> Mail
I would like to send an email if there is an exception in any of the mapping. But I don't want to use a BPM for this exception handling. How can I do it?
Thanks
Abinash

Hi Abinash,
yes you can! See these..
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
/people/sap.user72/blog/2005/02/23/raising-exceptions-in-sap-xi-mapping
All the best!
cheers,
Prashanth
P.S Please mark helpful answers

Exception handling in File to IDoc Scenario

Hi,
I have successfully configured File to IDoc Scenario. Now I want to include some exception handling which should be capable of create a mail to recipient when a mapping error occurs.
Can anybody help me out?
Regards,
Suraj Kumar

Hi Suraj,
A few points while creating ALERTS.
TESTING YOUR ALERT CONFIGURATIOn
go to se37 --> and execute the report RSALERTTEST. GIve your ALERT CATEGORY in this report. If your ALERTS are configured properly, then your Alert would be triggered and you can see the entry in ALERT INBBOX.
ALERT RULE
Make sure that in your Alert Rule, the option Suppress Multiple Alerts of this rule has not been seelcted.
Finally, if you are on SP14 and above check this note 913858 for alerts.
If you are below Sp14, then this blog can help you set the background processes needed.
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
No BPMis needed to trigger alerts in either case.
Do get back for any clarifications,
Regards,
Bhavesh

Triggering E-mail for failed outbound idoc (Without using workflow)

Hi Experts,
In my secnario Idoc to file, where any failures of Idoc( Inbound/Outbound ) at SAP R/3 side will generate and send Emails to the required group. How to do this without using Work flow. If anybody knws please help me out its very urget.
Regards,
venkatesh

Hi,
Create a Distribution list using SO23 and add Users whom to recieve messages.
Modify your Inbound function module to handle if idoc failed to post by calling the function module: SO_NEW_DOCUMENT_SEND_API1
Reward points if it is helpful.
Ashok

Use of raise in exception handling block

what is the use of raise in exception handling block for eg.
declare
a number;
b emp.empno%type;
begin
begin
SELECT empno INTO a FROM emp where 1=2;
exception
when others then
dbms_output.put_line('inner');
raise;
end;
exception
when no_data_found then
dbms_output.put_line('outer');
end;
output will be like below ..
inner
outer
PL/SQL procedure successfully completed.
my question is wht is the use of using raise in exception handing part, is there any specific reason we use in the development ????
Regards,
AAK.

In the first block, you do not raise you user-defined exception WHEN_NO_DATA_FOUND, but the predefined one, which is raised to the WHEN OTHERS exception handler.
Consider:
SQL> declare
2     a number;
3     my_err exception;
4     no_data_found exception;
5 begin
6     begin
7        select 1 into a from dual where 1=2;
8     exception
9     when no_data_found then
10        dbms_output.put_line(' In system defined');
11        raise my_err;
12     end;
13 exception
14     when my_err then
15        dbms_output.put_line('In User Defined');
16     when others then
17        declare
18           v_sqlerrm varchar2(100);
19        begin
20           v_sqlerrm := sqlerrm;
21        dbms_output.put_line(' In when others '||sqlerrm);
22        end;
23 end;
24 /
In when others ORA-01403: no data found
PL/SQL procedure successfully completed.
SQL> ed
Wrote file afiedt.buf
1 declare
2     a number;
3     my_err exception;
4     --no_data_found exception;
5 begin
6     begin
7        select 1 into a from dual where 1=2;
8     exception
9     when no_data_found then
10        dbms_output.put_line(' In system defined');
11        raise my_err;
12     end;
13 exception
14     when my_err then
15        dbms_output.put_line('In User Defined');
16     when others then
17        declare
18           v_sqlerrm varchar2(100);
19        begin
20           v_sqlerrm := sqlerrm;
21        dbms_output.put_line(' In when others '||sqlerrm);
22        end;
23* end;
SQL> /
In system defined
In User Defined
PL/SQL procedure successfully completed.
SQL>Note that in the second block, I deleted the declaration of the user defined exception NO_DATA_FOUND.
This is taken from the documentation:
Redeclaring Predefined Exceptions
Remember, PL/SQL declares predefined exceptions globally in package STANDARD, so you need not declare them yourself. Redeclaring predefined exceptions is error prone because your local declaration overrides the global declaration. For example, if you declare an exception named invalid_number and then PL/SQL raises the predefined exception INVALID_NUMBER internally, a handler written for INVALID_NUMBER will not catch the internal exception. In such cases, you must use dot notation to specify the predefined exception, as follows:
EXCEPTION
WHEN invalid_number OR STANDARD.INVALID_NUMBER THEN
    -- handle the error
END;You can read yourself :
http://download-uk.oracle.com/docs/cd/B19306_01/appdev.102/b14261/errors.htm
Regards,
Gerd

Avoid transaction roll back using exception handler

Hi everybody!
I've created a proxy service in OSB using a DB adapter for polling from a database table. I've configured the service to be transactional with same transaction for reponse. The proxy has a route node that routes to a business service created from a db adapter for storing the polled data. Insert table has a db trigger associated wich raises a custom exception in certain cases. I need to catch that exception in the route exception handler to avoid the full transaction to be marked rolled back. For this, I've setup a response with failure action in the handler.
After testing the service I realized that it's not working as expected as transaction is being rolled back when the trigger raises the exception (so registry is not marked as polled in source table).
Could anyone explain me which action should be taken to avoid a rollback when handling exception?
Best regards,
Daniel.

Hi Athhek,
If I set reply with success then both route node and system error handlers are executed. I get following response metadata
<con:metadata xmlns:con="http://www.bea.com/wli/sb/test/config">
<tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">1</tran:response-code>
</con:metadata>
and also following error reaches system handler:
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382050</con:errorCode>
<con:reason>
Expected active transaction, actual transaction status: Marked Rollback
</con:reason>
<con:location>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>
When I set reply with error only route node handler is executed but I still get
<con:metadata xmlns:con="http://www.bea.com/wli/sb/test/config">
<tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">1</tran:response-code>
</con:metadata>
Thank you.

May I use Exception Handling for validation ?

Hello All,
Can any one know about that may i use exception handling for validation in my report program.
Please if its possible then give me some Example...
Thanks.

Hi Niraj,
Exception is not at all raised or handled in the given example.
There are so many document available in the SCN regarding OO ABAP you can read that.
As far as validation of a field ( Selection screen ) of course we can do that but I don't see any advantage more over it will make your code unnecessarily complex.
Regards
Bikas

Exception handling in IDOC using workflows

Similar Messages

Maybe you are looking for